-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [EMAIL PROTECTED] wrote:
> Could it be assigning names (hda, hdc, sda, sdc, etc) differently at > different boots? It not only could be, that's what it was. I had to change hdc to hdg after the upgrade (both in the kernel boot line and in fstab, of course). Now here are the things I can't figure out for the life of me: Why do harddisk partition names magically change through a kernel update (2.4.17 -> 2.6.18)? How can I happily have rebooted the machine several times without having made those changes? All I recall is that sometimes the sytem wouldn't want to start until after a reboot. If this partition name changing is normal, shouldn't a dist-upgrade magically take care of this (both in the grub menu and in fstab)? After all, Linux amd Debian are trying hard to become a system suitable for non-fstab-and-grub-savvy people. BTW, to get the system to boot of course I first had to manually change the kernel options line in the grub boot screen. After that I didn't expect the system to get much past single-user because it would try to mount /usr from an invalid fstab entry (I have different partitions for /, /usr, and /home). To my surprise X came up with all bells and whistles, which of course means a working /usr. But when I tried to login, I didn't get far because /home wasn't mounted. This all seems as if, by some strange process, mounting the partitions under their old device names has not become impossible but highly unreliable after the etch upgrade. If anybody is interested, please let me know so I can supply details as soon as I'm back at my computer at home. Thanks, - --Dan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFvwr+GdM4FB223AcRAhHqAJwJBCgvlcPLk1NBPAAEVIURwmKVcQCfUhd4 wYIftgLFRs9xdnlm7F+3oFw= =92PG -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
