1 |
On Sunday 22 Apr 2012 00:20:38 Florian Philipp wrote: |
2 |
> Am 21.04.2012 20:56, schrieb Mick: |
3 |
> > I am getting confused about the syntax that openrc is meant to follow ... |
4 |
> > |
5 |
> > One box of mine that uses modules ran some script at the time that I |
6 |
> > upgraded to openrc and it added my currently running modules into |
7 |
> > /etc/conf.d/modules. |
8 |
> > |
9 |
> > The syntax was like so: |
10 |
> > |
11 |
> > modules_2_6="${modules_2_6} cls_tcindex" |
12 |
> > module_cls_tcindex_args_2_6=" |
13 |
> > |
14 |
> > Things moved on and with newer kernel versions I went to update the file |
15 |
> > after |
16 |
> > |
17 |
> > I had a look at the documentation: |
18 |
> > http://www.gentoo.org/doc/en/openrc-migration.xml |
19 |
> > |
20 |
> > Well there is no ${modules_2_6} shown in the examples so I removed it |
21 |
> > from my /etc/conf.d/modules. The new syntax was now: |
22 |
> > |
23 |
> > modules_3_2="cls_tcindex" |
24 |
> > |
25 |
> > and guess what? No modules loaded at all when I reboot. :-/ |
26 |
> > |
27 |
> > |
28 |
> > I had to add ${modules_3_2} in there to get things going again. |
29 |
> > |
30 |
> > However 'echo ${modules_3_2}' on the CLI does not show anything. Can you |
31 |
> > please explain why this variable is needed for modules to load up again |
32 |
> > and why it is not shown in the documentation? |
33 |
> |
34 |
> I guess it is "modules_3" now. With the transition to 3.x, the numbering |
35 |
> scheme has changed and minor numbers change much more frequently. |
36 |
> |
37 |
> You can also simply use "modules=" unless you have a reason for |
38 |
> distinguishing between versions. At least, that's what I use here. |
39 |
> |
40 |
> Hope this helps, |
41 |
> Florian Philipp |
42 |
|
43 |
Thanks Florian, |
44 |
|
45 |
I did try: |
46 |
|
47 |
modules="cls_tcindex" |
48 |
modules_3="cls_tcindex" |
49 |
modules_3_2="cls_tcindex" |
50 |
modules_3_2="${modules_3_2} cls_tcindex" |
51 |
|
52 |
and only the last one actually loads. I don't understand how this works or |
53 |
what ${modules_3_2} does ... but following the documentation recommended |
54 |
syntax won't autoload modules at boot here. |
55 |
|
56 |
PS. Is there a way to check if a particular syntax will load *without* having |
57 |
to reboot each time I make a change? |
58 |
-- |
59 |
Regards, |
60 |
Mick |