[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] [PATCH] Machine dependent module path extension

On 02/12/13 21:42, Miro Kropáček wrote:
On Tue, Feb 12, 2013 at 10:19 PM, Alan Hourihane <alanh@fairlite.co.uk <mailto:alanh@fairlite.co.uk>> wrote: 

    But I want to be sure that introducing something like this doesn't
    leave us in a state of disrepair when the system goes hunting for
    files that are incorrect. We need failsafe options.
I don't know, how is that different from what we have today? Even with the strictly machine only directories nobody prevents you to copy there an improper module. If we want to play it safe, we should fix it on loader level, i.e. introduce something as mintlib does, cpu (machine) based check from header.
Right. It is the same to what we have today, but it shouldn't be is what I'm saying.
e.g. you have say an 030 mch directory that's clean, you can copy a module to your 060 mch directory and bang. You fallback to your 030 mch directory as it's good. If you copied the bad module to your shared directory bang goes both 030 and 060. 

Alan.