From: Roy Marples <roy@marples.name>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Google SOC 2008
Date: Mon, 3 Mar 2008 15:58:47 +0000 [thread overview]
Message-ID: <5e985752b1fac3a18077ec0820d9751f@marples.name> (raw)
In-Reply-To: <20080303145320.GD7729@gentoo.org>
On Mon, 3 Mar 2008 15:53:20 +0100, Fabian Groffen <grobian@gentoo.org>
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?
I did this in OpenRC source
rm -rf /home/roy/pkg
make PREFIX=/home/roy/pkg PKG_PREFIX=/usr/pkg install
Create Gentoo style init script in /home/roy/pkg/etc/init.d for say boinc
export PATH=$PATH:/home/roy/pkg/bin:/home/roy/pkg/sbin
rc-update add boinc default
rc default
boinc started
>
>> 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.
>
> If a service such as PostgreSQL is killed (maybe a reboot?) does OpenRC
> then know it is not running any more? I guess it does, so that's good
> enough, IMO.
This needs to be done on startup
rc sysinit
rc default
Which is pretty much what we do in Gentoo anyway. Just ensure that the
sysinit
runlevel only runs once, as it will remove all state when run again.
Thanks
Roy
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-03 15:58 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
2008-03-03 16:04 ` Roy Marples
2008-03-03 15:58 ` Roy Marples [this message]
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=5e985752b1fac3a18077ec0820d9751f@marples.name \
--to=roy@marples.name \
--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