1 |
Ok - anyone using a usb input device (me) would have to include hotplug |
2 |
before dm-crypt, I'm not enamored with that idea, and clearly omitting |
3 |
localmount isn't any better. |
4 |
|
5 |
It looks like the most robust solution is to fixup the .critical stuff |
6 |
so that it stops breaking 'before' and so forth. |
7 |
|
8 |
Is a fix planned? If not I'll have a go, but I don't want to implement |
9 |
anything the core team won't like the looks of, so I'd appreciate |
10 |
comments. |
11 |
|
12 |
Justin |
13 |
|
14 |
On Sun, 2004-02-29 at 18:25 +0200, Martin Schlemmer wrote: |
15 |
> On Sun, 2004-02-29 at 15:11, Justin Whitney wrote: |
16 |
> > Actually, it must come before as it provides things for localmount to |
17 |
> > mount (otherwise encrypted block devices). |
18 |
> > |
19 |
> > Turns out the issue is that by default localmount is present as a |
20 |
> > CRITICAL_SERVICES in /sbin/rc |
21 |
> > |
22 |
> > to work around the issue, I wrote out everything in CRITICAL_SERVICES |
23 |
> > minus 'localmount' > /etc/runlevels/boot/.critical |
24 |
> > |
25 |
> > did the trick. |
26 |
> > |
27 |
> > My dm-crypt ebuild will need this same functionality if users want to |
28 |
> > mount their encrypted block devices in any usable way during boot. I |
29 |
> > don't know how I'd do this in any kind of flexible way. |
30 |
> > |
31 |
> > Can some of the devs comment on a good way to set about this? |
32 |
> > |
33 |
> |
34 |
> That, or just add dm-crypt before localmount in .critical. |
35 |
> |
36 |
> |
37 |
> -- |
38 |
> |
39 |
> Martin Schlemmer |
40 |
> Gentoo Linux Developer, Desktop/System Team Developer |
41 |
> Cape Town, South Africa |
42 |
|
43 |
|
44 |
-- |
45 |
gentoo-dev@g.o mailing list |