public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Detecting Baselayout2/openrc - no-symlink profiles leading to breakage
Date: Sun, 18 Jan 2009 12:39:21 +0300	[thread overview]
Message-ID: <1232271561.28710.70.camel@localhost> (raw)
In-Reply-To: <49726F21.8010004@gentoo.org>

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

В Вск, 18/01/2009 в 00:52 +0100, Friedrich Oslage пишет:
> Robin H. Johnson schrieb:
> > I'm raising this as an extension of bug 253076, but also because I see
> > the potential for danger.

> > As a long term solution, can we just consume an inode and have some file
> > like /etc/baselayout2?

What package will install this file? Also is it possible to save openrc
${PVR} inside this file? Version is required to introduce workarounds in
reliable way for openrc versions which does not work with openvz startup
scripts. Also why not call this files /etc/*openrc*?

> > To date, for an init script that has baselayout2-specific behavior, we
> > have had some variant of [ -e /lib/librc.so ] in the init script.
> >
> Why not teach /sbin/runscript it's own version? 

In some cases this will break with openvz. openvz container (CT)
start/stop scripts need to check openrc existence inside container and
depending on that generate either openrc or baselayout-1 configuration
files. This start/stop scripts work in host node (HN) environment and
since it's possible to have different versions of everything (e.g. libc)
in HN and CT /sbin/runscript will not work in some cases and thus break
networking and other things for CT.

-- 
Peter.

[-- Attachment #2: Эта часть сообщения подписана цифровой подписью --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-01-18  9:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17 23:07 [gentoo-dev] Detecting Baselayout2/openrc - no-symlink profiles leading to breakage Robin H. Johnson
2009-01-17 23:52 ` Friedrich Oslage
2009-01-18  7:17   ` [gentoo-dev] " Duncan
2009-01-18  9:39   ` Peter Volkov [this message]
2009-01-19 16:18   ` [gentoo-dev] " Santiago M. Mola
2009-01-20 13:20     ` Peter Volkov
2009-01-19  3:11 ` Donnie Berkholz
2009-01-19  6:13   ` Robin H. Johnson
2009-01-20 14:17 ` Matthias Schwarzott

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=1232271561.28710.70.camel@localhost \
    --to=pva@gentoo.org \
    --cc=gentoo-dev@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