a new setting rc_sys="" have been added to rc.conf, as understood mainly to detect and deal safely with various virtual server types, but the instructions are very sparse and unclear. # This is the subsystem type. Valid options on Linux: # "" - nothing special # "lxc" - Linux Containers # "openvz" - Linux OpenVZ # "prefix" - Prefix # "uml" - Usermode Linux # "vserver" - Linux vserver # "xen0" - Xen0 Domain # "xenU" - XenU Domain # If unset, the old automagic detection code will be triggered. Said old code # is deprecated and be removed not later than 2010/03/01. rc_sys="" There is no indication in thee instructions if the rc_sys needs to be set on the host node, the container or both. Instructions simply needs to be more specific and implicive, especially as getting it wrong can result in a non-bootable system (as understood from another bug). I just updated my system but don't dare to reboot until I'm clear on this. Also sort of funny updating on 2011/01/15 and be met with a message that the depreciated automagic detection will be removed no later than 2010/03/01 ;-) Reproducible: Always Steps to Reproduce: 1.Always 2. 3. Portage 2.2.0_alpha15 (default/linux/amd64/10.0/server, gcc-4.5.2, glibc-2.12.2-r0, 2.6.27-openvz-levitan.1 x86_64) ================================================================= System uname: Linux-2.6.27-openvz-levitan.1-x86_64-Intel-R-_Core-TM-2_Duo_CPU_E6750_@_2.66GHz-with-gentoo-2.0.1 Timestamp of tree: Sat, 15 Jan 2011 10:15:01 +0000 app-shells/bash: 4.1_p9 dev-lang/python: 2.6.6-r1, 2.7 sys-apps/baselayout: 2.0.1-r1 sys-apps/openrc: 0.7.0 sys-apps/sandbox: 2.4 sys-devel/autoconf: 2.68 sys-devel/automake: 1.10.3, 1.11.1 sys-devel/binutils: 2.21 sys-devel/gcc: 4.4.5, 4.5.2 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.4-r1 sys-devel/make: 3.82 virtual/os-headers: 2.6.36.1 (sys-kernel/linux-headers) Repositories: gentoo merc ACCEPT_KEYWORDS="amd64 ~amd64" ACCEPT_LICENSE="* -@EULA" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=native -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-march=native -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="assume-digests binpkg-logs distlocks fixlafiles fixpackages news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch" GENTOO_MIRRORS="http://mirror.switch.ch/ftp/mirror/gentoo/ http://gentoo.mirror.web4u.cz/ ftp://gentoo.mirror.web4u.cz/ ftp://gentoo.wheel.sk/pub/linux/gentoo/ rsync://ftp.fi.muni.cz/pub/linux/gentoo/" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="acl amd64 berkdb bzip2 cli cracklib crypt cups cxx dri fortran gdbm gpm iconv ithreads logrotate mmx modules mudflap multilib ncurses nls nptl nptlonly openmp pam pcre pppd readline session snmp sse sse2 ssl symlink sysfs tcpd truetype unicode urandom xml xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" PHP_TARGETS="php5-3" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="fbdev glint intel mach64 mga neomagic nouveau nv r128 radeon savage sis tdfx trident vesa via vmware dummy v4l" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
I did cover this in the migration guide already (did you check it before asking?), but I've added the following to the rc.conf: +# This should be set to the value representing what environment this file is +# PRESENTLY in, not what virtualization the environment is capable of. +# See the OpenRC migration guide for more details. And I've explicitly expanded the section in the migration guide. Lastly, why didn't you use the auto-detection command to ask what values were already in use on your system?
(In reply to comment #1) > I did cover this in the migration guide already (did you check it before > asking?), but I've added the following to the rc.conf: In fact no because I migrated quite some time ago but also because that page didn't use to change much back in the earlier days. I see now it has got some nice updates, great, and now I am aware it also has that function. I did search a lot though both on g.o and google. > +# This should be set to the value representing what environment this file is > +# PRESENTLY in, not what virtualization the environment is capable of. > +# See the OpenRC migration guide for more details. > > And I've explicitly expanded the section in the migration guide. > Yes that's great and I appreciate your reply and work. > Lastly, why didn't you use the auto-detection command to ask what values were > already in use on your system? > Probably because because it said the mechanism would be removed no later than 2010/03/01, that's more than 9 months ago so why bother... no actually I wasn't sure how to dig out the value from the environment and had no luck with searches there either. I'm just an infrequent sysop looking after 1 openvz box and don't have a touch with everything, so your work and assistance is very much appreciated, thanks.
i dont think removing the auto-detection code makes sense. we went good "out-of-the-box" behavior when possible. when it isnt possible, people can manually tune the value on their systems.
This may be getting into a discussion for another bug or for the ml, but I'll go ahead and reply here for now. (In reply to comment #3) > i dont think removing the auto-detection code makes sense. we went good > "out-of-the-box" behavior when possible. when it isnt possible, people can > manually tune the value on their systems. What you are proposing, in my view, creates an inconsistency. I think it is easier for us, and more consistent for the users, if we have everyone set the value of RC_SYS to whatever their system subtype is instead of saying that if you use certain subtypes you have to set it but we can detect other subtypes so you don't have to set it for them.
1. It's impossible to safely detect the LXC and Prefix types. 2. The other checks all rely on /proc being available, which while reasonable in most cases, is not possible during early boot. This means that keywords are broken during the early boot before /proc is mounted, since the auto-detection returns the wrong results then.
it isnt inconsistent. i'm not suggesting we attempt to do a 100% job with autodetection. but if we can often save people who accidentally overwrite their rc.conf or it is otherwise lost, then all the better. having a system not boot because correctly because of it is poor behavior. we have the code already, and it isnt a significant burden to keep or use it. we really dont gain anything by forcing everyone to manually select rc_sys.
