David Howells:
> I have to admit, I wouldn't have though of using romfs in this way... I've
> only thought of it in terms of initial installation before. One thing I'm
> uncertain of with it is how the kernel finds the romfs 'drive' on booting... I
> know it must be possible - after all, I've seen it when installing Linux from
> floppy or bootable CD-ROM.
>
It usually loads an initial RAM disk via LILO or loadlin.
> Hot swapping was one of the things I have in mind, but it's hard to test for
> me, as I have no hot-swapping hardware, and can't afford just to buy some to
> play with.
>
Me too, unfortunately.
> Thinking of SCSI, I also considered the possibility of making another
> configuration token describing bus/LUN etc., and binding high-level SCSI
> device drivers to low-level SCSI interface drivers by the same device/driver
> handling method. However, I'm uncertain as to the practicality of this idea,
> having not studied the SCSI drivers much.
>
SCSI IDs or LUNs don't change. Bus numbers might, but as soon as you have
suspend operation / resume operation routines for the drivers it should be
no problem to walk through the lists and just update all the bus bumbers.
Anyway, it might be a nice idea to have suspend/resume for LL SCSI drivers
because then you could tell it to suspend everything for a few seconds,
which means that hotplugging SCSI finally becomes possible; you need a 100%
quiet bus for that to be safe.
-- Matthias Urlichs | noris network GmbH | smurf@noris.de The quote was selected randomly. Really. | http://www.noris.de/~smurf/-- Augustine's Law Number XIX: Although most products will soon be too costly to purchase, there will be a thriving market in the sale of books on how to fix them. -- Norman R. Augustine, President and CEO, Martin Marietta- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/faq.html