Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!warrane.connect.com.au!godzilla.zeta.org.au!not-for-mail From: bde@zeta.org.au (Bruce Evans) Newsgroups: comp.os.386bsd.questions Subject: Re: Locked File (even for root) FR2.0R ??? Date: 5 Feb 1995 21:19:09 +1100 Organization: Kralizec Dialup Unix Sydney - +61-2-837-1183, v.32bis v.42bis Lines: 19 Message-ID: <3h28mt$ej1@godzilla.zeta.org.au> References: <3guimq$1l8@mamnix.werries.de> NNTP-Posting-Host: localhost.zeta.org.au In article <3guimq$1l8@mamnix.werries.de>, Michael A. Meiszl <mam@werries.de> wrote: >How it happened, who knows? >But I managed to get a totally protected file by aborting a make install. >/usr/lib/libc.so.2.0 was readable, but not removeable, renameable or >writeable for anyone including root. libc.so.2.0 is always installed as immutable. >My last resort was hacking /sys/ufs/ufs/ufs_vnops.c and comment out the >IMUTUAL | APPEND clause within ufs_remove(). >... >But there must be a better way for root in singleuser mode to kill/remove >everything he likes... This way is named chflags. See chflags(1), ls -lo /usr/lib, and init(8) (stuff about securelevel). -- Bruce Evans bde@zeta.org.au