| 1 |
On 25/10/16 05:12 PM, Michał Górny wrote: |
| 2 |
> On Tue, 25 Oct 2016 12:01:06 -0500 |
| 3 |
> William Hubbs <williamh@g.o> wrote: |
| 4 |
> |
| 5 |
>> Title: Inportant fstab update |
| 6 |
>> Author: William Hubbs <williamh@g.o> |
| 7 |
>> Content-Type: text/plain |
| 8 |
>> Posted: 2016-10-28 |
| 9 |
>> Revision: 1 |
| 10 |
>> News-Item-Format: 1.0 |
| 11 |
>> |
| 12 |
>> If you are not using /dev/disk/by-* paths in fstab, you do not need to |
| 13 |
>> take any action for this news item. |
| 14 |
>> |
| 15 |
>> If you are, it is very critical that you update fstab AS SOON AS |
| 16 |
>> POSSIBLE. Your system will become unbootable in the future if you do |
| 17 |
>> not do so. |
| 18 |
> |
| 19 |
> I don't think this is a good way to start any text. You should start |
| 20 |
> with a short introduction on what's happening, when and how. |
| 21 |
> |
| 22 |
> Right now the news item sounds like the world is going to suddenly fall |
| 23 |
> apart for no specific reason. Reading it, I don't know what's changing, |
| 24 |
> and how to check if it impacts me already (i.e. if it's 'do not |
| 25 |
> reboot' kind of problem) and if it will impact me at all. |
| 26 |
> |
| 27 |
>> You need to replace the /dev/disk/by-* paths in your fstab with the |
| 28 |
>> equivalent information from the output of the blkid utility. |
| 29 |
> |
| 30 |
> This is at least unclear, if not misguiding. I read it as 'blkid will |
| 31 |
> give you fs info'. However, you're not telling me which of those |
| 32 |
> information I can use and how. I should also point out that blkid |
| 33 |
> supports multiple output formats. |
| 34 |
> |
| 35 |
> I think it would be better if you explicitly listed the thingies |
| 36 |
> supported by mount(1). |
| 37 |
> |
| 38 |
|
| 39 |
Reading mgorny's response, I'm wondering if a news item really makes |
| 40 |
any sense at all for this. What's being done here is essentially a |
| 41 |
warning/recommendation for users to act so they don't run into a |
| 42 |
problem that's sort-of already there (at least in ~arch)... |
| 43 |
|
| 44 |
Personally I'd rather see us go the other way, ensure udev settles |
| 45 |
before localmount runs, and maybe ewarn if /dev/disk/by-* is in fstab |
| 46 |
or something. Leave the migration away from these paths to general |
| 47 |
education of system setup, since they technically are valid, just not |
| 48 |
ideal. |
Archives