1 |
On Thu, Jul 30, 2015 at 12:15:38PM -0400, Ian Stakenvicius wrote: |
2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
3 |
> Hash: SHA256 |
4 |
> |
5 |
> On 30/07/15 01:55 AM, Duncan wrote: |
6 |
> > Patrick McLean posted on Wed, 29 Jul 2015 15:35:02 -0700 as |
7 |
> > excerpted: |
8 |
> > |
9 |
> >> On Thu, 30 Jul 2015 01:11:30 +0300 Alon Bar-Lev |
10 |
> >> <alonbl@g.o> wrote: |
11 |
> >> |
12 |
> >>> On 29 July 2015 at 23:20, William Hubbs <williamh@g.o> |
13 |
> >>> wrote: |
14 |
> >>>> |
15 |
> >>>> so that there is a better idea out there of what I'm talking |
16 |
> >>>> about, the OpenRC github repository now has a mount-service |
17 |
> >>>> branch. |
18 |
> >>> |
19 |
> >>> But I still trying to figure out why do we need to keep fstab |
20 |
> >>> around. It is pure legacy. |
21 |
> >>> |
22 |
> >>> |
23 |
> >> On what planet is fstab pure legacy? Many utilities use it and |
24 |
> >> expect it to exist. For example the ability to do "mount /foo" |
25 |
> >> requires a properly configured fstab file (also mount -a). |
26 |
> >> |
27 |
> |
28 |
> I think there are two meanings of the word legacy here. |
29 |
> |
30 |
> #1, /etc/fstab on linux is not legacy, and I don't think anyone here |
31 |
> (except possibly for WilliamH as I can't actually tell from his |
32 |
> statements) has been calling it 'legacy' in this context. |
33 |
|
34 |
No, it was alonbl who called it legasy. If you look at how the script |
35 |
operates, it would not work without fstab. |
36 |
|
37 |
I simply asked, in response to alonbl, if it really was legasy. |
38 |
|
39 |
|
40 |
William |
41 |
|
42 |
> |
43 |
> #2, if openrc implements new system mounting which doesn't touch fstab |
44 |
> at all, then by definition /etc/fstab and init scripts that leverage |
45 |
> commands that use it exclusively (old localmount and netmount) are |
46 |
> legacy -- you have the legacy method, and you have the new method. |
47 |
> This is still in the openrc context though, and not in the overall |
48 |
> context of linux. Alon Bar-Lev's comments are definitely using legacy |
49 |
> in this context IMO, and he's right there technically would not be a |
50 |
> need for /etc/fstab on his system with openrc mounting things the new |
51 |
> way that has been suggested, so long as he doesn't intend to use any |
52 |
> tools or commands that expect /etc/fstab in userspace. |
53 |
> |
54 |
> Back to practical matters: |
55 |
> |
56 |
> SO, because /etc/fstab is not legacy (see #1), the new mount system in |
57 |
> openrc needs to be aware of and honour /etc/fstab contents. I've no |
58 |
> idea how to do this, to be honest, as it seems like a clusterfsck to |
59 |
> deal with properly. |
60 |
> |
61 |
> Technically we could require users using openrc from now on to make |
62 |
> symlinks for every mountpoint they want to have mounted at boottime, |
63 |
> but that's IMO an unacceptable amount of work for something that's |
64 |
> never been needed (and IMO never should be -needed-) on linux. As |
65 |
> such, IMO, /etc/fstab should not be turned into a legacy (see #2) |
66 |
> configuration file by openrc. |
67 |
> |
68 |
> -----BEGIN PGP SIGNATURE----- |
69 |
> Version: GnuPG v2 |
70 |
> |
71 |
> iF4EAREIAAYFAlW6TakACgkQAJxUfCtlWe2CNQEAmowci81PZYfRr2BJMLCusXEI |
72 |
> MiewLIGDmQqhUc1qnEcA/RrvacCqoBTYIzUzbYuxaUgD/4sdaGPZ70WZYupvIsIO |
73 |
> =Gr62 |
74 |
> -----END PGP SIGNATURE----- |
75 |
> |