From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Two issues with OpenRC/baselayout2 migration on a hosted VM
Date: Tue, 13 Dec 2011 21:29:08 +0000 [thread overview]
Message-ID: <20111213212908.60674c68@digimed.co.uk> (raw)
In-Reply-To: <4EE7B899.8060402@libertytrek.org>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
On Tue, 13 Dec 2011 15:42:01 -0500, Tanstaafl wrote:
> > The files were named local.{start,stop} but the message you quoted
> > shows that these are no longer the case. The files you have are your
> > old baselayout1 local.* files moved from conf.d to local.d and given
> > a name that shows where they came from. The local part of the
> > filename is no longer relevant as the directory name makes their
> > purpose clear. Also, it means you can have more than one file,
> > instead of having to cram several unrelated steps into one script.
> >
> > Give them names that reflect their contents, it will make managing
> > them easier.
>
> Yes, but - I'm no longer on baselayout1, so that name is no longer
> accurate...
The name is accurate because it is telling you the file came from
baselayout1. The local.{start,stop} names are the deprecated names used
by BL1. Until you give them more meaningful names (which local.* are not)
baselayout1.* are the best names portage can give them for you.
--
Neil Bothwick
All right, set phasers to deep fat fry!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-12-13 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 18:03 [gentoo-user] Two issues with OpenRC/baselayout2 migration on a hosted VM Tanstaafl
2011-12-13 18:26 ` Pandu Poluan
2011-12-13 19:50 ` Tanstaafl
2011-12-13 20:21 ` Neil Bothwick
2011-12-13 20:42 ` Tanstaafl
2011-12-13 21:29 ` Neil Bothwick [this message]
2011-12-14 14:29 ` victor romanchuk
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=20111213212908.60674c68@digimed.co.uk \
--to=neil@digimed.co.uk \
--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