From: "Daniel Pielmeier" <daniel.pielmeier@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] OpenRC & baselayout-2 meets Gentoo
Date: Thu, 20 Mar 2008 15:34:53 +0100 [thread overview]
Message-ID: <6142e6140803200734s6d0eca63p92a4e127dd6e26a8@mail.gmail.com> (raw)
In-Reply-To: <47E271CF.2050107@gentoo.org>
2008/3/20, Doug Goldstein <cardoe@gentoo.org>:
> Roy Marples wrote:
> > On Thursday 20 March 2008 06:59:24 Josh Saddler wrote:
> >
> >> I'll be working on the migration guide with Cardoe (and possibly Roy, if
> >> we can tag-team him into submission). As much of a pain as migration
> >> will be, we'll definitely need a howto. Fun, fun.
> >>
> >
> > I already provide documentation with commands in example config files and man
> > pages that cover nearly every aspect on OpenRC and all it's commands.
> >
> > The nice thing about not being a Gentoo dev means I don't feel the urge to
> > write a migration how to. However, here's a really good primer.
> >
> > 1) Install OpenRC
> > 2) Review all updated files in /etc/conf.d/ and /etc/rc.conf [1] [2]
> > 3) If using a "volume" such as LVM, you'll find an appropriate init script
> > in /etc/init.d that you need to add to the boot runlevel.
> > 4) Carry on as normal [3]
> >
> > Thanks
> >
> > Roy
> >
> > [1] The case of variable names has been changed from UPPER to lower. This is
> > for a few reasons (removes confusion vs environment vars, looks nicer).
> > However, *existing* UPPER case vars should still work.
> > [2] Paludis users will need to ensure that the init scripts checkfs and
> > checkroot are removed. I don't care whose "bug" this is, but neither side
> > wants to fix it.
> > [3] A reboot is currently needed as for some reason state data isn't migrated
> > from baselayout-1. This is probably due to OpenRC being split from baselayout
> > and the code is pretty much the same here. Maybe some plucky Gentoo ebuild
> > dev can step up and fix it.
> >
> You missed the whole /etc/modules.autoload.d/* -> /etc/conf.d/modules
> but I already discussed that with Josh for the guide. ;)
> --
> gentoo-dev@lists.gentoo.org mailing list
>
>
Maybe the XSESSION variable disappearing from /etc/rc.conf and the
changed settings in /etc/conf.d/clock are worth consideration too!
Regards,
Daniel
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-20 14:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 5:19 [gentoo-dev] OpenRC & baselayout-2 meets Gentoo Doug Goldstein
2008-03-20 6:59 ` Josh Saddler
2008-03-20 12:12 ` Roy Marples
2008-03-20 14:16 ` Doug Goldstein
2008-03-20 14:34 ` Daniel Pielmeier [this message]
2008-03-20 20:13 ` [gentoo-dev] Re: [gentoo-core] " Mike Frysinger
2008-03-24 20:26 ` [gentoo-dev] " Doug Goldstein
2008-03-24 20:35 ` Josh Saddler
2008-03-24 20:47 ` Doug Goldstein
2008-03-24 21:08 ` [gentoo-core] " Mike Frysinger
2008-03-24 21:16 ` Doug Goldstein
2008-03-24 21:32 ` Mike Frysinger
2008-03-24 21:36 ` Doug Goldstein
2008-03-24 21:42 ` Mike Frysinger
2008-03-24 21:53 ` Doug Goldstein
2008-03-24 22:03 ` Mike Frysinger
2008-03-24 23:49 ` Doug Goldstein
2008-03-25 12:30 ` Mike Frysinger
2008-03-25 8:33 ` Roy Marples
2008-03-25 12:29 ` Mike Frysinger
2008-03-27 14:57 ` Doug Goldstein
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=6142e6140803200734s6d0eca63p92a4e127dd6e26a8@mail.gmail.com \
--to=daniel.pielmeier@googlemail.com \
--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