*BSD News Article 61881


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!yarrina.connect.com.au!news.mel.connect.com.au!news.syd.connect.com.au!gidora.kralizec.net.au!not-for-mail
From: bde@zeta.org.au (Bruce Evans)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Problems with 2.2-960130-SNAP
Date: 13 Feb 1996 22:14:47 +1100
Organization: Kralizec Dialup Unix
Lines: 24
Message-ID: <4fprr7$oq8@godzilla.zeta.org.au>
References: <ngsxXaw@quack.kfu.com>
NNTP-Posting-Host: godzilla.zeta.org.au

In article <ngsxXaw@quack.kfu.com>, Nick Sayer <nsayer@quack.kfu.com> wrote:
>...
>2. Something has gone wrong with rshd -- it never exits after a job
>has completed. Substituting the 2.1.0-RELEASE rshd doesn't help any.
>This problem is really painful, since it's screwing up the backups
>(this machine is the tapehost).

This was caused by selecting on pipes being broken.  Replace kern/sys_pipe.c
with a current version.

>3. As part of the upgrade (I did it the hard way - don't hate me),
>the system steadfastly refused to remove /sbin-/init. What I did as
>part of the upgrade was 'mv /sbin /sbin- ; cd /usr/src/sbin ; make
>install'. Then I rebooted with a new kernel, then I tried to remove
>/sbin-. All of it went except /sbin-/init. I was finally forced to
>use clri to vaporise it. Does /sbin/init get some sort of special
>treatment?

Yes.  See the chflags man page and the output of `ls -lo /sbin'.  ld.so
and a few other files should also have been protected againsts removal
by ordinary rm.  Of course, `mv /sbin /sbin-' shows that this protection
is worthless.
-- 
Bruce Evans  bde@zeta.org.au