Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!cs.utexas.edu!howland.reston.ans.net!Germany.EU.net!mamunx!not-for-mail From: mam@werries.de (Michael A. Meiszl) Newsgroups: comp.os.386bsd.questions Subject: Locked File (even for root) FR2.0R ??? Date: 4 Feb 1995 01:45:14 +0100 Organization: Meiszl Consulting Hamm Lines: 27 Message-ID: <3guimq$1l8@mamnix.werries.de> NNTP-Posting-Host: mamnix.werries.de 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. I only managed to move /usr/lib to something else, so moving the stuck file too. Even copies of the file remain "locked" :-( I found no utility to chmod it to "sane" permissions (since chmod also yielded "Operation not permitted"). My last resort was hacking /sys/ufs/ufs/ufs_vnops.c and comment out the IMUTUAL | APPEND clause within ufs_remove(). So I was able to remove the file. But there must be a better way for root in singleuser mode to kill/remove everything he likes... Any clues (other than my "brute force" method) ??? MaM -- +-------------------------+---------------+--------------+-------------------+ | /\/\ichael A. /\/\eiszl | Tomsonstr. 25 | D-59071 Hamm | Tel +49 2381 9880 | +-------------------------+---------------+--------------+-------------------+