1 |
On 2016.10.25 22:52, Ian Stakenvicius wrote: |
2 |
> On 25/10/16 05:12 PM, Michał Górny wrote: |
3 |
> > On Tue, 25 Oct 2016 12:01:06 -0500 |
4 |
> > William Hubbs <williamh@g.o> wrote: |
5 |
> > |
6 |
> >> Title: Inportant fstab update |
7 |
> >> Author: William Hubbs <williamh@g.o> |
8 |
> >> Content-Type: text/plain |
9 |
> >> Posted: 2016-10-28 |
10 |
> >> Revision: 1 |
11 |
> >> News-Item-Format: 1.0 |
12 |
> >> |
13 |
> >> If you are not using /dev/disk/by-* paths in fstab, you do not need |
14 |
> to |
15 |
> >> take any action for this news item. |
16 |
> >> |
17 |
> >> If you are, it is very critical that you update fstab AS SOON AS |
18 |
> >> POSSIBLE. Your system will become unbootable in the future if you |
19 |
> do |
20 |
> >> not do so. |
21 |
> > |
22 |
> > I don't think this is a good way to start any text. You should start |
23 |
> > with a short introduction on what's happening, when and how. |
24 |
> > |
25 |
> > Right now the news item sounds like the world is going to suddenly |
26 |
> fall |
27 |
> > apart for no specific reason. Reading it, I don't know what's |
28 |
> changing, |
29 |
> > and how to check if it impacts me already (i.e. if it's 'do not |
30 |
> > reboot' kind of problem) and if it will impact me at all. |
31 |
> > |
32 |
> >> You need to replace the /dev/disk/by-* paths in your fstab with the |
33 |
> >> equivalent information from the output of the blkid utility. |
34 |
> > |
35 |
> > This is at least unclear, if not misguiding. I read it as 'blkid |
36 |
> will |
37 |
> > give you fs info'. However, you're not telling me which of those |
38 |
> > information I can use and how. I should also point out that blkid |
39 |
> > supports multiple output formats. |
40 |
> > |
41 |
> > I think it would be better if you explicitly listed the thingies |
42 |
> > supported by mount(1). |
43 |
> > |
44 |
> |
45 |
> Reading mgorny's response, I'm wondering if a news item really makes |
46 |
> any sense at all for this. What's being done here is essentially a |
47 |
> warning/recommendation for users to act so they don't run into a |
48 |
> problem that's sort-of already there (at least in ~arch)... |
49 |
> |
50 |
> Personally I'd rather see us go the other way, ensure udev settles |
51 |
> before localmount runs, and maybe ewarn if /dev/disk/by-* is in fstab |
52 |
> or something. Leave the migration away from these paths to general |
53 |
> education of system setup, since they technically are valid, just not |
54 |
> ideal. |
55 |
> |
56 |
> |
57 |
+1 |
58 |
|
59 |
Add udev-settle now. |
60 |
Have an advisory news item that says why its been done and what |
61 |
users can do if they don't like it or don't need it, and what will happen |
62 |
long term. |
63 |
At the same time, depreciate the use of udev symlinks in fstab. |
64 |
|
65 |
Some time later, remove udev-settle and have another news item. |
66 |
By now, users will have reacted to the first news item or sympathy |
67 |
can be minimal. |
68 |
|
69 |
In the interim, nothing should break because a news item was not |
70 |
read and acted on immediately. |
71 |
|
72 |
That's the important bit ... nothing breaks on user systems. |
73 |
|
74 |
-- |
75 |
Regards, |
76 |
|
77 |
Roy Bamford |
78 |
(Neddyseagoon) a member of |
79 |
elections |
80 |
gentoo-ops |
81 |
forum-mods |