2016-10-26 11:04 GMT+02:00 Michał Górny <[email protected]>: > Dnia 26 października 2016 10:49:04 CEST, Joshua Kinard <[email protected]> > napisał(a): > >On 10/25/2016 13:15, William Hubbs wrote: > >> On Tue, Oct 25, 2016 at 01:10:06PM -0400, Mike Gilbert wrote: > >>> On Tue, Oct 25, 2016 at 1:01 PM, William Hubbs <[email protected]> > >wrote: > >>>> If you are not using /dev/disk/by-* paths in fstab, you do not need > >to > >>> take any action for this news item. > >>>> > >>>> If you are, it is very critical that you update fstab AS SOON AS > >>> POSSIBLE. Your system will become unbootable in the future if you do > >>> not do so. > >>> > >>> Err, what is changing that will make systems unbootable? > >>> > >>> I am fairly certain systems running systemd will continue to work > >>> properly with either syntax. > >> > >> They probably will. > >> > >>> If this is about the udev-settle issue for OpenRC, I would urge you > >to > >>> reconsider that. > >> > >> There isn't anything to reconsider afaik. The problem is that > >> /dev/disk/by-* are only created by udev/eudev, but the other syntax > >> works regardless of which device manager you use, so this is the > >safer > >> route. > >> > >> William > >> > > > >I take it us museum relics still using jurassic-era device names like > >/dev/sd* or /dev/md* aren't affected by this? Cthulhu-forbid Linux > >device > >naming gets any more complicated than using UUID's. What's next, > >saving the > >serial numbers of discovered disks in an overly-complicated > >key/value-based > >non-SQL database format? > > Wait full you-know-who notices that disk device names are not predictable > and fixes that. >
that's easy just make fstab parser able to read the content of HWPATH=/sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1/dev ;-) > > > -- > Best regards, > Michał Górny (by phone) > >
