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

[Alan Hourihane <alanh@fairlite.co.uk>]

On 02/12/13 22:13, Miro Kropáček wrote:
> On Tue, Feb 12, 2013 at 11:02 PM, Alan Hourihane <alanh@fairlite.co.uk 
> <mailto:alanh@fairlite.co.uk>> wrote:
>
>     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.
>
> This is is of course true but you realize that to fix that 'bang' 
> you'd need to
>
> a) switch your Falcon to 030
> b) enable 030 kernel, disable 060 kernel
> c) reboot into 030 kernel, fix it
>
> To me this doesn't seem any better than boot with CTRL, 
> rename/disable/copy_to_the_right_mch the improper module and reboot 
> again. And this works regardless of the path configuration, so I don't 
> know, IMO it's OK as it is.

Maybe. I'm thinking of inet4.xdd here as an example I've hit before. If 
you rely on networking and blew your 060 directory up because of a bad 
inet4.xdd I need to boot 030 mode and load a good inet4.xdd (because I 
overwrote the old one :-( ) and get networking back to copy a good one over.

Sure I should of backed the old one up, but hey, I'm human :-), but 
otherwise I'm off to floppy land to get one back.

And I use XBOOT to manage the switching so it's not as painful as you 
make out.

Alan.