| 1 |
Dnia 26 października 2016 10:49:04 CEST, Joshua Kinard <kumba@g.o> napisał(a): |
| 2 |
>On 10/25/2016 13:15, William Hubbs wrote: |
| 3 |
>> On Tue, Oct 25, 2016 at 01:10:06PM -0400, Mike Gilbert wrote: |
| 4 |
>>> On Tue, Oct 25, 2016 at 1:01 PM, William Hubbs <williamh@g.o> |
| 5 |
>wrote: |
| 6 |
>>>> If you are not using /dev/disk/by-* paths in fstab, you do not need |
| 7 |
>to |
| 8 |
>>> take any action for this news item. |
| 9 |
>>>> |
| 10 |
>>>> If you are, it is very critical that you update fstab AS SOON AS |
| 11 |
>>> POSSIBLE. Your system will become unbootable in the future if you do |
| 12 |
>>> not do so. |
| 13 |
>>> |
| 14 |
>>> Err, what is changing that will make systems unbootable? |
| 15 |
>>> |
| 16 |
>>> I am fairly certain systems running systemd will continue to work |
| 17 |
>>> properly with either syntax. |
| 18 |
>> |
| 19 |
>> They probably will. |
| 20 |
>> |
| 21 |
>>> If this is about the udev-settle issue for OpenRC, I would urge you |
| 22 |
>to |
| 23 |
>>> reconsider that. |
| 24 |
>> |
| 25 |
>> There isn't anything to reconsider afaik. The problem is that |
| 26 |
>> /dev/disk/by-* are only created by udev/eudev, but the other syntax |
| 27 |
>> works regardless of which device manager you use, so this is the |
| 28 |
>safer |
| 29 |
>> route. |
| 30 |
>> |
| 31 |
>> William |
| 32 |
>> |
| 33 |
> |
| 34 |
>I take it us museum relics still using jurassic-era device names like |
| 35 |
>/dev/sd* or /dev/md* aren't affected by this? Cthulhu-forbid Linux |
| 36 |
>device |
| 37 |
>naming gets any more complicated than using UUID's. What's next, |
| 38 |
>saving the |
| 39 |
>serial numbers of discovered disks in an overly-complicated |
| 40 |
>key/value-based |
| 41 |
>non-SQL database format? |
| 42 |
|
| 43 |
Wait full you-know-who notices that disk device names are not predictable and fixes that. |
| 44 |
|
| 45 |
|
| 46 |
-- |
| 47 |
Best regards, |
| 48 |
Michał Górny (by phone) |
Archives