From: Tanstaafl <tanstaafl@libertytrek.org>
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 15:42:01 -0500 [thread overview]
Message-ID: <4EE7B899.8060402@libertytrek.org> (raw)
In-Reply-To: <20111213202136.05eba42b@digimed.co.uk>
On 2011-12-13 3:21 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Tue, 13 Dec 2011 14:50:06 -0500, Tanstaafl wrote:
>
>>>> Problem - on this VM, these files are named 'baselayout1.start' and
>>>> 'baselayout1.stop', NOT 'local.start' and 'local.stop'...
>>>>
>>>> Should I change these? Does it matter?
>>
>>> The names doesn't matter. Only the extension matters. You can even
>>> rename them to MickeyMouse.start and MinnieMouse.stop :-)
>>
>> Ok, thanks, renamed to local.start/stop...
>
> 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...
next prev parent reply other threads:[~2011-12-13 20:43 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 [this message]
2011-12-13 21:29 ` Neil Bothwick
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=4EE7B899.8060402@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--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