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 from init.d scripts (summary of debate and plans from bug 270646)
Date: Sat, 13 Jun 2009 02:43:32 +0400	[thread overview]
Message-ID: <1244846612.11823.3107.camel@localhost> (raw)
In-Reply-To: <1244804029.11823.1336.camel@localhost>

On Monday 08 June 2009 10:00:23 Roy Marples wrote: 
> You would have to ask the VServer team, but my understanding was they
> needed to detect version of OpenRC in a container from the host before
> the container is started.

Eh, I lead everybody to astray due to wrong tests results. In reality
openvz does not needs this and probably every configuration that needs
to find out openrc version outside container or chroot can do things
like vzclt (basically chroot() with some magic to execute scripts from
host inside container). I haven't checked vserver scripts but they never
told they have any problems with this.

В Птн, 12/06/2009 в 14:53 +0400, Peter Volkov пишет:
> Is there any problem with /etc/openrc-version?

I don't think this is necessary any more.

-- 
Peter.




  reply	other threads:[~2009-06-12 22:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-07 19:59 [gentoo-dev] Detecting Baselayout2/OpenRC from init.d scripts (summary of debate and plans from bug 270646) Robin H. Johnson
2009-06-07 20:10 ` Samuli Suominen
2009-06-07 20:45   ` Josh Saddler
2009-06-07 21:31     ` Roy Marples
2009-06-07 22:33     ` Robin H. Johnson
2009-06-07 23:30       ` Josh Saddler
2009-06-07 22:02 ` Ulrich Mueller
2009-06-07 22:17   ` Robin H. Johnson
2009-06-07 23:00     ` Roy Marples
2009-06-08  0:11       ` Robin H. Johnson
2009-06-08  6:27         ` Ulrich Mueller
2009-06-08 10:00         ` Roy Marples
2009-06-08 10:22           ` Mike Frysinger
2009-06-08  7:45 ` Mike Frysinger
2009-06-08 10:12   ` Roy Marples
2009-06-08 10:19     ` Mike Frysinger
2009-06-08 10:35       ` Roy Marples
2009-06-08 10:38         ` Mike Frysinger
2009-06-08 11:03           ` Roy Marples
2009-06-08 11:27             ` Mike Frysinger
2009-06-08 12:58               ` Roy Marples
2009-06-08 23:23               ` Robin H. Johnson
2009-06-08 23:42                 ` Mike Frysinger
2009-06-09  0:44                   ` Robin H. Johnson
2009-06-09  0:54                     ` Mike Frysinger
2009-06-12 10:53                       ` Peter Volkov
2009-06-12 22:43                         ` Peter Volkov [this message]
2009-06-08 10:39       ` Joe Peterson
2009-06-08 10:45         ` Mike Frysinger
2009-06-08 10:54           ` Joe Peterson
2009-06-08 10:52         ` Roy Marples
2009-06-08 12:16 ` Mike Frysinger
2009-06-08 13:01   ` Roy Marples
2009-06-08 13:08     ` Mike Frysinger
2009-06-08 13:09       ` Roy Marples
2009-06-08 13:41         ` Mike Frysinger
2009-06-08 14:00           ` Roy Marples
2009-06-08 14:27             ` Mike Frysinger
2009-06-12 13:20               ` [gentoo-dev] Re: Baselayout2/OpenRC init.d Steven J Long
2009-06-12 18:34 ` [gentoo-dev] Detecting Baselayout2/OpenRC from init.d scripts (summary of debate and plans from bug 270646) Petteri Räty

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=1244846612.11823.3107.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