On Mon, 19 Jan 2009, Keith Edmunds wrote:
Google for "udev rules", which are a way of giving consistent names to (typically USB) devices, although the rules are also useful for other things, such as making sure Ethernet adaptors have a consistent ethx number.
Nice idea. But what was primarily troubling me was the potential for the following process, which would be done and dusted before udev runs:
- Boot computer with USB stick already plugged in - USB stick grabs id "/dev/sda", relegating hard drive to "/dev/sdb" - "resume=/dev/sda2" boot parameter from grub.conf kicks in - at best, second partition on USB stick doesn't contain a TuxOnIce image and system continues with a fresh boot - at worst, it's a maliciously crafted USB stick, which inserts an image into RAM that does untold nasty things to my computer - "root=/dev/sda1" boot parameter from grub.conf kicks in - at best, I get a root filesystem other than the intended one, which presumably won't contain /etc/init.d and therefore won't proceed with boot - at middling, it's a non-ext3 filesystem that won't mount and causes a kernel panic - at worst, it's a maliciously crafted USB stick etc etc...
Is any of this a possibility?