Rick Stevens <ricks@xxxxxxxx> writes:
> The only way to ensure you're talking to the same drive is to use its
> UUID. Most filesystems and devices on Fedora now have UUIDs associated
> with them and most of the necessary utilities support it. For example,
> your /etc/fstab can specify a device either via device name (/dev/sda1),
> label ("LABEL=somelabel") or UUID ("UUID=weird-hex-string").
Thanks. I (at the /etc/fstab level) do use a label that goes with the
drive, mainly the lvm VG and LV names. The problem is that the lvm
mapper *internally* must still use the name that the drive had when the
computer first booted. It gets confused when the drive gets renamed at
runtime (long after boot).
> I sure wish there was a standard on the order in which things get
> scanned. Even network NICs vary. On Dell 1850s and 1950s, the PCI bus
> was scanned for NICs before the on-board stuff, so any PCI NICs got the
> first "ethX" numbers. The bigger 2850/2950 machines scanned the
> on-boards first. GRRRRR! It's enough to drive one absolutely mad at
> times.
Ditto. I have my machine dual ported and I'd really like eth0 to be the
internal ethernet and eth1 to be the external. (Some programs like
multicast progs seem to default to the first ethernet and it would be
nice for me not to spew packets towards the public internet.)
-wolfgang
--
Wolfgang S. Rupprecht
If the airwaves belong to the public why does the public only get 3
non-overlapping WIFI channels?
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
