1 |
On Dec 14, 2011 1:06 AM, "Tanstaafl" <tanstaafl@×××××××××××.org> wrote: |
2 |
> |
3 |
> Hello, |
4 |
> |
5 |
> This is my first time dealing with a VM, and this one is being hosted on |
6 |
Linode... I'm fairly sure they use XenServer, but I'm still waiting for |
7 |
confirmation... |
8 |
> |
9 |
> 2 issues I have after updating: |
10 |
> |
11 |
> 1. First question |
12 |
> |
13 |
> Quoting from the Guide: |
14 |
> |
15 |
> "local.start and local.stop |
16 |
> |
17 |
> With OpenRC, /etc/conf.d/local.start and local.stop are deprecated. |
18 |
During the migration to OpenRC, the files are moved to /etc/local.d and |
19 |
gain the suffix .start or .stop. OpenRC then executes those in alphabetic |
20 |
order." |
21 |
> |
22 |
> Problem - on this VM, these files are named 'baselayout1.start' and |
23 |
'baselayout1.stop', NOT 'local.start' and 'local.stop'... |
24 |
> |
25 |
> Should I change these? Does it matter? |
26 |
> |
27 |
|
28 |
The names doesn't matter. Only the extension matters. You can even rename |
29 |
them to MickeyMouse.start and MinnieMouse.stop :-) |
30 |
|
31 |
> 2. Second question |
32 |
> |
33 |
> Quoting from the Guide: |
34 |
> |
35 |
> "System sub-types: Virtualization special cases |
36 |
> |
37 |
> In the early versions of OpenRC, we explictly detected multiple types of |
38 |
virtualization, and used that detection to note when certain init scripts |
39 |
should be skipped, using the keyword call in the depend functions. |
40 |
> |
41 |
> However, as of the 0.7.0 release, you are required to explicitly |
42 |
configure the sub-type using the rc_sys variable in /etc/rc.conf. The |
43 |
sub-type should be set to match the virtualization environment that the |
44 |
given root is in. In general, the non-empty rc_sys value should be within |
45 |
the virtual containers; The host node will have rc_sys="". |
46 |
> |
47 |
> Important: If you do not have any specific sub-type, please use the |
48 |
default of an empty string "". If the variable is unset, you will be given |
49 |
a warning and we will attempt to use the old detection algorithm. |
50 |
> |
51 |
> Note: If you do not know what value your system was using with the |
52 |
automatic detection, you should temporarily comment out the rc_sys variable |
53 |
and run the detection command, rc -S." |
54 |
> |
55 |
> Currently this is set to "", but according to the guide, since this is a |
56 |
VM, it needs to be explicitly set. rc -S simply reports: |
57 |
> |
58 |
> "li66-207 etc # rc -S |
59 |
> * WARNING: rc_sys not defined in rc.conf. Falling back to automatic |
60 |
detection" |
61 |
> |
62 |
> What should I set this to? Assuming that Linode is indeed using Xen, |
63 |
would it be: |
64 |
> |
65 |
> rc_sys="xenU" |
66 |
> |
67 |
> ? |
68 |
> |
69 |
|
70 |
AFAIK Linode uses Xen so "xenU" is correct. |
71 |
|
72 |
What I really want to know is what happens if we specify a 'wrong' rc_sys |
73 |
value... |
74 |
|
75 |
(I also want to know why 'rc -S' is so unhelpful, but not as much as the |
76 |
above.) |
77 |
|
78 |
Rgds, |