From: Hleil Liu <hleil@yahoo.com.cn>
Subject: Re: runit pblms on Mandrake
Date: Thu, 17 Jul 2003 16:51:18 +0800 [thread overview]
Message-ID: <20030717165118.0139ae8a.hleil@yahoo.com.cn> (raw)
In-Reply-To: <20030717062520.GA24787@skarnet.org>
On Thu, 17 Jul 2003 08:25:20 +0200
Laurent Bercot <ska-supervision@skarnet.org> wrote:
> Why perform those steps at all ?
> Copying binaries into /sbin creates potential problems:
> - it breaks the rule of "/[s]bin and /usr/[s]bin belong to the OS
> and its native package manager"
> - it duplicates binaries
> - it is non-standard and non-portable.
>
yes.
> In other words, by copying binaries into /sbin, you're making your
> system less clean, more error-prone and more difficult to debug.
>
> There are two documented, supported, portable, whatever, ways of
> accessing the runit binaries: in /command and in
> /package/admin/runit/command. Isn't that enough ?
no,the reason is what you said below.the /package and /command directorys
may be not stay at root partition.Although we can think /pacakge/admin/*
as the basic system packages,but what about others?like /package/prog?
/package/host?Are they basic?So we have to take all the /package/*,at least
all the binaries under /package at root partition?
If put runit-init and runit into /sbin,we need not consider those.In stage 1,
runit do system init,mount other patitions,so stage 2 can use all the filesystems.
if stage 1 failed,it start an emergency shell.If stage 1 exit sucessfully,all
symbolic links work.So we can put /package anywhere,for me,I put it
another patition.
The problem is:after we upgraded runit,we should replace /sbin/init and /sbin/runit
with the new version,and these's two copys of runit and runit-init(/sbin/init).
> Using " init=/command/runit-init" within your bootloader will start
> runit-init as process 1 all right, and you don't have to copy it
> anywhere.
good idea,we dont need *replace* /sbin/init,thanks!But maybe I use
init=/sbin/runit-init in my /etc/grub.conf, :)
Regard!
next prev parent reply other threads:[~2003-07-17 8:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 3:10 Karthik M
2003-07-17 6:00 ` Hleil Liu
2003-07-17 6:05 ` Hleil Liu
2003-07-17 6:25 ` Laurent Bercot
2003-07-17 8:51 ` Hleil Liu [this message]
2003-07-17 12:33 ` Laurent Bercot
2003-07-17 16:30 ` Karthik M
2003-07-17 17:10 ` Lukas Beeler
2003-07-17 22:22 ` Karthik M
2003-07-19 1:43 ` Karthik M
2003-07-19 8:02 ` Lukas Beeler
2003-07-22 21:31 ` Karthik M
2003-07-22 21:40 ` Charlie Brady
2003-07-23 18:30 ` clemens fischer
2003-07-17 19:30 ` Stefan Karrmann
2003-07-18 10:17 ` Gerrit Pape
2003-07-19 17:25 ` Hleil Liu
2003-07-17 16:26 ` Karthik M
2003-07-18 10:20 ` Gerrit Pape
2003-07-18 16:27 ` Lukas Beeler
2003-07-21 10:01 ` some getties require setsid() (Re: runit pblms on Mandrake) Gerrit Pape
2003-07-21 10:13 ` some getties require setsid() Lukas Beeler
2003-07-23 17:03 ` clemens fischer
2003-07-23 17:23 ` Lukas Beeler
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=20030717165118.0139ae8a.hleil@yahoo.com.cn \
--to=hleil@yahoo.com.cn \
/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).