public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Two issues with OpenRC/baselayout2 migration on a hosted VM
Date: Tue, 13 Dec 2011 13:03:06 -0500	[thread overview]
Message-ID: <4EE7935A.5080403@libertytrek.org> (raw)

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?

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"

?

Thanks,

Charles



             reply	other threads:[~2011-12-13 18:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 18:03 Tanstaafl [this message]
2011-12-13 18:26 ` [gentoo-user] Two issues with OpenRC/baselayout2 migration on a hosted VM Pandu Poluan
2011-12-13 19:50   ` Tanstaafl
2011-12-13 20:21     ` Neil Bothwick
2011-12-13 20:42       ` Tanstaafl
2011-12-13 21:29         ` Neil Bothwick
2011-12-14 14:29   ` victor romanchuk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EE7935A.5080403@libertytrek.org \
    --to=tanstaafl@libertytrek.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox