From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/190 Path: main.gmane.org!not-for-mail From: Hleil Liu Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: runit pblms on Mandrake Date: Thu, 17 Jul 2003 16:51:18 +0800 Organization: http://www.hleil.com Message-ID: <20030717165118.0139ae8a.hleil@yahoo.com.cn> References: <20030717031031.30483.qmail@web14402.mail.yahoo.com> <20030717140019.57d767fd.hleil@yahoo.com.cn> <20030717140548.2ec1a9e5.hleil@yahoo.com.cn> <20030717062520.GA24787@skarnet.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1058431832 14895 80.91.224.249 (17 Jul 2003 08:50:32 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 17 Jul 2003 08:50:32 +0000 (UTC) Original-X-From: supervision-return-428-gcsg-supervision=m.gmane.org@list.skarnet.org Thu Jul 17 10:50:29 2003 Return-path: Original-Received: from antah.skarnet.org ([212.43.221.114]) by main.gmane.org with smtp (Exim 3.35 #1 (Debian)) id 19d4T7-0003rN-00 for ; Thu, 17 Jul 2003 10:50:29 +0200 Original-Received: (qmail 25780 invoked by uid 76); 17 Jul 2003 08:51:50 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 25774 invoked from network); 17 Jul 2003 08:51:50 -0000 Original-To: supervision@list.skarnet.org In-Reply-To: <20030717062520.GA24787@skarnet.org> X-Mailer: Sylpheed version 0.9.3 (GTK+ 1.2.10; i586-pc-linux-gnu) Xref: main.gmane.org gmane.comp.sysutils.supervision.general:190 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:190 On Thu, 17 Jul 2003 08:25:20 +0200 Laurent Bercot 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!