1 |
On Fri, Jul 31, 2015 at 05:29:37PM -0700, Patrick McLean wrote: |
2 |
> On Fri, 31 Jul 2015 17:28:03 -0500 |
3 |
> William Hubbs <williamh@g.o> wrote: |
4 |
> |
5 |
> > On Fri, Jul 31, 2015 at 11:57:59PM +0200, Peter Stuge wrote: |
6 |
> > |
7 |
> > What I'm asking about is whether anyone knows of a smoothe way to |
8 |
> > transition users from local/netmount to mount.<filesystem> |
9 |
> > dependencies, without breaking systems. If that doesn't exist, 1.0 |
10 |
> > will have to sit in p.mask until major packages catch up. |
11 |
> |
12 |
> You could make "localmount" and "netmount" scripts that |
13 |
> read /etc/fstab and generate "need" dependencies on the network or |
14 |
> local filesystems that exist in there. That should emulate current |
15 |
> behaviour with the new system. |
16 |
|
17 |
This is exactly what I'm thinking about. Researching this as I go, there |
18 |
are reasons to keep localmount and netmount around, but I want to |
19 |
rewrite them to depend on mount.*. |
20 |
|
21 |
There will still be a change in behaviour, because localmount and netmount |
22 |
never fail in the current setup, but they potentially will in the new setup |
23 |
based on whether or not one of the file systems they depend on fails to mount. |
24 |
|
25 |
I'm a bit concerned about trying to auto generate dependencies in them, |
26 |
for the same reason I'm concerned about auto generating dependencies in |
27 |
netmount as it currently stands. |
28 |
|
29 |
All of this processing would be in the depend() function, and would be |
30 |
run every time the OpenRC dependency cache is regenerated. The best way |
31 |
to process fstab is with the fstabinfo helper, but every time you run |
32 |
it, that is a possible full scan of fstab, and I worry that that would |
33 |
slow down dependency cache regeneration for servers with many file |
34 |
systems. If I don't use fstabinfo, I"m basically re-inventing the wheel |
35 |
and writing code in sh to parse fstab. |
36 |
|
37 |
Thoughts? |
38 |
|
39 |
William |