Gentoo Archives: gentoo-dev

From: Ian Stakenvicius <axs@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: rfc: improve file system mounting and unmounting in OpenRC
Date: Thu, 06 Aug 2015 14:02:24
Message-Id: 55C368EA.8030606@gentoo.org
In Reply to: [gentoo-dev] Re: rfc: improve file system mounting and unmounting in OpenRC by Duncan <1i5t5.duncan@cox.net>
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA256
3
4 On 06/08/15 02:58 AM, Duncan wrote:
5 > William Hubbs posted on Wed, 05 Aug 2015 10:26:33 -0500 as
6 > excerpted:
7 >
8 >> It isn't localmount that would have the issue, but mount.*
9 >> because they are lexically after localmount, so you would end up
10 >> with localmount doing a mount -a then mount.* coming later trying
11 >> to mount file systems again that were mounted by localmount.
12 >
13 > But if localmount is a wrapper, then it pulls them in and they're
14 > already started (if they'll mount), just like they are now. You'd
15 > just have to have it still return success even if one of the
16 > wrapped mounts fails, in ordered to maintain compatibility.
17 >
18 > So coming later won't be a problem, if they're wrapped by
19 > localmount, because it will have already started them anyway, so
20 > they'll already be detected as started.
21
22
23 The problem with this though is that making localmount be a wrapper
24 for a dynamic list of services is likely going to be difficult,
25 because depend() would need to be filled in according to what the
26 mount.* services are that people would want -- so should only the ones
27 in the same runlevel be started, or should all the ones that match an
28 fstab entry be started; and then there's the cache issue due to the
29 fact that detection of the mount.* services will need to occur based
30 on the contents of /etc/init.d/ itself.
31
32 This is where the new system falls down IMO (as discussed in previous
33 emails) -- it's all fine and good to say "openrc can just do X in the
34 locamount service", but openrc doesn't actually have a nice way to do
35 this type of thing yet (afaik) without making changes to internals.
36
37
38 -----BEGIN PGP SIGNATURE-----
39 Version: GnuPG v2
40
41 iF4EAREIAAYFAlXDaOoACgkQAJxUfCtlWe1e5gEApmGThElPTFf+cNqBugVHC7KF
42 W0TnM+0lNjzS1/jwN+oBAKSfA+zd4JkZDOS/xfKKeTMqV9+dg0JtOQQWMAuQNsrN
43 =dY4B
44 -----END PGP SIGNATURE-----