Re: [gentoo-user] Two issues with OpenRC/baselayout2 migration on a hosted VM

[Pandu Poluan <pandu@poluan.info>]

[-- Attachment #1: Type: text/plain, Size: 2527 bytes --]

On Dec 14, 2011 1:06 AM, "Tanstaafl" <tanstaafl@libertytrek.org> wrote:
>
> Hello,
>
> This is my first time dealing with a VM, and this one is being hosted on
Linode... I'm fairly sure they use XenServer, but I'm still waiting for
confirmation...
>
> 2 issues I have after updating:
>
> 1. First question
>
> Quoting from the Guide:
>
> "local.start and local.stop
>
> With OpenRC, /etc/conf.d/local.start and local.stop are deprecated.
During the migration to OpenRC, the files are moved to /etc/local.d and
gain the suffix .start or .stop. OpenRC then executes those in alphabetic
order."
>
> Problem - on this VM, these files are named 'baselayout1.start' and
'baselayout1.stop', NOT 'local.start' and 'local.stop'...
>
> Should I change these? Does it matter?
>

The names doesn't matter. Only the extension matters. You can even rename
them to MickeyMouse.start and MinnieMouse.stop :-)

> 2. Second question
>
> Quoting from the Guide:
>
> "System sub-types: Virtualization special cases
>
> In the early versions of OpenRC, we explictly detected multiple types of
virtualization, and used that detection to note when certain init scripts
should be skipped, using the keyword call in the depend functions.
>
> However, as of the 0.7.0 release, you are required to explicitly
configure the sub-type using the rc_sys variable in /etc/rc.conf. The
sub-type should be set to match the virtualization environment that the
given root is in. In general, the non-empty rc_sys value should be within
the virtual containers; The host node will have rc_sys="".
>
> Important: If you do not have any specific sub-type, please use the
default of an empty string "". If the variable is unset, you will be given
a warning and we will attempt to use the old detection algorithm.
>
> Note: If you do not know what value your system was using with the
automatic detection, you should temporarily comment out the rc_sys variable
and run the detection command, rc -S."
>
> Currently this is set to "", but according to the guide, since this is a
VM, it needs to be explicitly set. rc -S simply reports:
>
> "li66-207 etc # rc -S
> * WARNING: rc_sys not defined in rc.conf. Falling back to automatic
detection"
>
> What should I set this to? Assuming that Linode is indeed using Xen,
would it be:
>
> rc_sys="xenU"
>
> ?
>

AFAIK Linode uses Xen so "xenU" is correct.

What I really want to know is what happens if we specify a 'wrong' rc_sys
value...

(I also want to know why 'rc -S' is so unhelpful, but not as much as the
above.)

Rgds,

[-- Attachment #2: Type: text/html, Size: 3148 bytes --]