From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Can /package be a symlink?
Date: Thu, 24 Jun 2004 18:29:31 -0400 [thread overview]
Message-ID: <m37jtwio8k.fsf@asfast.com> (raw)
In-Reply-To: <m3n02sermk.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> Lloyd Zusman <ljz@asfast.com> wrote:
>> Well, does any part of runit use anything underneath /package before
>> disks are mounted?
>
> runit itself is in /package. [ ... ]
Upon further investigation, I see that on my system, runit is guaranteed
to get invoked after all disks have been mounted. That's because I
start it via /etc/rc.local, which is the documented recommendation for
FreeBSD. My /etc/rc causes mounts to be done before /etc/rc.local gets
run.
I guess that means that it's safe for me to make /package be a symlink
to a directory on a different filesystem.
> [ ... ] If the programs don't care if they're moved, you could copy
> the ones needed for booting into /sbin. Or use
> <URL:http://multivac.cwru.edu./fs/#tricks>.
Hmm ... I still need to peruse the info about this "fs" trick in more
detail, but after my quick scan of it, I get the gist of it.
If I ever switch to an inittab-like startup and want to use runit for
the majority of my daemons, I see how this trick would be very useful.
>> It's my understanding that /package is for building software only,
>
> The build directory is defined to also be the install directory. It's
> built in /package, and it stays in /package.
OK, I see.
Thanks for this info, and especially for the details about this "fs"
trick.
--
Lloyd Zusman
ljz@asfast.com
God bless you.
next prev parent reply other threads:[~2004-06-24 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 18:00 Lloyd Zusman
2004-06-24 18:05 ` Laurent Bercot
2004-06-24 18:10 ` Paul Jarc
2004-06-24 18:19 ` Lloyd Zusman
2004-06-24 18:29 ` Paul Jarc
2004-06-24 22:29 ` Lloyd Zusman [this message]
2004-06-25 1:50 ` Brian Reichert
2004-06-25 4:46 ` Lloyd Zusman
2004-06-24 19:57 ` Stefan Karrmann
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=m37jtwio8k.fsf@asfast.com \
--to=ljz@asfast.com \
/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;
as well as URLs for NNTP newsgroup(s).