public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Canonical place to list modules to load
Date: Fri, 19 Jun 2009 19:23:02 +0100	[thread overview]
Message-ID: <200906191923.14268.michaelkintzios@gmail.com> (raw)
In-Reply-To: <200906191008.55805.alan.mckinnon@gmail.com>

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

On Friday 19 June 2009, Alan McKinnon wrote:
> On Friday 19 June 2009 00:08:04 Neil Bothwick wrote:
> > On Thu, 18 Jun 2009 22:45:50 +0100, Mick wrote:
> > > Why did they *have* to move it to /etc/modules.autoload.d/kernel-2.6.
> >
> > They didn't, they moved it from there to /etc/conf.d where all the other
> > rc config files live.
> >
> > > I am still confused with the difference between /etc/rc.conf
> > > and /etc/conf.d/rc ...
> >
> > Then moved that one out of /etc/conf.d :(
>
> Lets not confuse the fellow with our awesome wit :-)
>
> Mick, it's a cleanup operation with openrc to get things a bit more sane.
>
> Unix let's you put config files any damn place you want them. So it's up to
> you to put them someplace sane. The recent trend is to use a structure like
>
> /etc/thing.conf
> /etc/thing.d/*
>
> The first one is used for global settings that affect the entire package
> (or system in this case as it's openrc).
> The second has individual files, one for each logical sub-section. Package
> managers can then update individual bits independently - trying to do
> updates to one massive file with sed is a distinctly non-trivial operation.
>
> With baselayout-1, the layout was a bit haphazard. baselayout-2 and openrc
> took the opportunity to tidy all this up.

Thank you for the explanation.

I am running stable x86 on all my boxen at the moment.  I guess I'll have to 
become accustomed to the new set up soon.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-06-19 18:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 14:21 [gentoo-user] Canonical place to list modules to load Harry Putnam
2009-06-17 14:31 ` Mark Shields
2009-06-17 14:47   ` Neil Bothwick
2009-06-17 18:29     ` Dale
2009-06-17 19:16       ` Neil Bothwick
2009-06-17 19:38         ` Dale
2009-06-17 20:13           ` Neil Bothwick
2009-06-17 20:36             ` Dale
2009-06-17 20:10     ` Mark Shields
2009-06-18 21:45       ` Mick
2009-06-18 22:08         ` Neil Bothwick
2009-06-19  8:08           ` Alan McKinnon
2009-06-19 18:23             ` Mick [this message]
2009-06-19 14:05     ` [gentoo-user] " Harry Putnam
2009-06-19 14:07   ` Harry Putnam

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=200906191923.14268.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@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