Tim wrote:
On Sat, 2007-05-05 at 05:36 -0700, Mick Mearns wrote:I always remove the disk labels and edit /etc/fstab to reflect this. #fdisk -l To find out if the disk is labelled and what: #e2label /dev/hda1 To blank it out: #e2label /dev/hda1 "" (that's empty quotes.)While I see quite a lot of usefulness in not using labels in the fstab file. Or, better still, customising them so your drive is unique from anything else that might get connected. I see no value in entering null ones onto the partitions, themselves. You can't relabel a swap partition (the one in question, in this thread) this way, a different technique is required (e2label is for ext2 or ext3 partitions). You probably have to run mkswap, again, unless someone knows of another technique to label an already set up swap partition. In the past, I'd replaced all fstab label parameters with device names, and all was fine, as far as booting was concerned. I hadn't tried resuming a hibernated system set up that way. You'd probably want to specify the resume partition, explicitly, some other way in the kernel parameters.
Hi, known issue. A "mkinitrd ..." solves the problem. -- Joachim Backes <joachim.backes@xxxxxxxxxxxxxx> University of Kaiserslautern,Computer Center [RHRK], Systems and Operations, High Performance Computing, D-67653 Kaiserslautern, PO Box 3049, Germany -------------------------------------------------- Phone: +49-631-205-2438, FAX: +49-631-205-3056 http://hlrwm.rhrk.uni-kl.de/home/staff/backes.html
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
