public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Haubenwallner <haubi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Google SOC 2008
Date: Mon, 03 Mar 2008 16:50:49 +0100	[thread overview]
Message-ID: <1204559449.6937.21.camel@salomon-22> (raw)
In-Reply-To: <20080303145320.GD7729@gentoo.org>

On Mon, 2008-03-03 at 15:53 +0100, Fabian Groffen wrote:
> On 03-03-2008 13:36:25 +0000, Roy Marples wrote:
> > On Thursday 28 February 2008 11:22:13 Roy Marples wrote:
> > > So the only thing left (aside from bug fixing) is to instruct OpenRC
> > > dependency
> > > code that it's in a prefix and to respect the noprefix keyword in services,
> > > or
> > > to provide dummy services.
> > 
> > This is now done.
> > 
> > I have OpenRC fully working in a prefixed non priviledged install on a NetBSD 
> > box.
> 
> Can you define how this is working?  Do you just have NetBSD and install
> OpenRC in /my/arbitrary/path, or do you have a full set of utilities
> under /my/arbitrary/path with OpenRC as one of them?
> 
> > The only question I have left is what mechanism resets service state, as the 
> > prefixed state dir needs will presist between reboots which isn't desirable.
> 
> startprefix could maybe start some sort of process that lives on,
> activated like keychain does, such that multiple startprefix invocations
> do not start the system all the time -- if that is desired at all. In
> a real scenario it may be just a hook from the host OS's start/stop
> mechanism to tell OpenRC in what state it should run.

Must admit not having looked at OpenRC yet - maybe I understood sth.
wrong, but:

+1 for registering OpenRC into host OS's specific init.d mechanism.

Here I'm doing so with distccd on ia64-hpux, having some (host OS
specific) script in (not yet gentoo-) prefix, understanding additional
'--install [name]' - or have a separate command for that.
This needs to be run as root once to register into host OS's init.d
mechanism.

For hpux fex this just is adding some symlinks:
/sbin/init.d/name -> /my/prefix/sbin/init.d/distccd
/sbin/rc3.d/S990name -> /sbin/init.d/name   # to start in runlevel 3
/sbin/rc2.d/K100name -> /sbin/init.d/name   # to kill for runlevel 2

When doing so with OpenRC's main process, it could integrate smoothly
with normal system reboot and start prefixed init.d scripts.

/haubi/
-- 
Michael Haubenwallner
Gentoo on a different level

-- 
gentoo-dev@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-03 15:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 18:32 [gentoo-dev] Google SOC 2008 joshua jackson
2008-02-26 23:13 ` Rémi Cardona
2008-02-26 23:28   ` joshua jackson
2008-02-27  2:57     ` Alec Warner
2008-02-27 10:46     ` [gentoo-dev] " Duncan
2008-02-27  8:42 ` [gentoo-dev] " Fabian Groffen
2008-02-27 10:46   ` Roy Marples
2008-02-27 12:29     ` Fabian Groffen
2008-02-27 13:56       ` Roy Marples
2008-02-27 14:21         ` Fabian Groffen
2008-02-27 21:04           ` Roy Marples
2008-02-28 11:22           ` Roy Marples
2008-02-28 11:25             ` Fabian Groffen
2008-03-03 13:36             ` Roy Marples
2008-03-03 14:53               ` Fabian Groffen
2008-03-03 15:50                 ` Michael Haubenwallner [this message]
2008-03-03 16:04                   ` Roy Marples
2008-03-03 15:58                 ` Roy Marples
2008-02-27 19:11         ` [gentoo-dev] MESA i965 SUPPORT PLEASE! Mateusz Mierzwinski
2008-02-27 19:47           ` Chris Gianelloni
2008-02-27 19:49           ` Chris Gianelloni
2008-02-28  7:37             ` Mateusz Mierzwinski
2008-02-28  9:58               ` Rémi Cardona
2008-02-27 10:50   ` [gentoo-dev] Google SOC 2008 Damian Florczyk
2008-02-28 16:02 ` Marius Mauch
2008-02-29 13:08 ` JoseAlberto
2008-02-29 17:24   ` Alec Warner
2008-03-02 15:58 ` Luca Barbato

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=1204559449.6937.21.camel@salomon-22 \
    --to=haubi@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