home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!usc!cs.utexas.edu!torn!cunews!revcan!software.mitel.com!sharman!sharman
- From: sharman@Software.Mitel.COM (Richard Sharman)
- Newsgroups: comp.os.linux
- Subject: Re: The Third Degree
- Message-ID: <SHARMAN.92Aug16185517@sharman.Software.Mitel.COM>
- Date: 16 Aug 92 22:55:17 GMT
- Sender: sharman@Software.Mitel.COM
- Organization: Mitel. Kanata (Ontario). Canada.
- Lines: 15
- In-reply-to: torvalds@klaava.Helsinki.FI's message of 14 Aug 92 20:54:08 GMT
-
- Regarding inodes left around, Linus said:
- This can happen if you install a new version of a running program (like
- 'init') and reboot. The old 'init' is removed from the directory tree,
- but as it's still in use, neither the inode nor the blocks are actually
- reclaimed until the program is exited. And in many cases (like /bin/sh
- or init or update), the program is never exited until the reboot has
- happened. "fsck -a" should clear up the problem - or you should be more
- careful when rebooting with "deleted" programs still running.
-
- So, if one is installing a new init for example, what is the "proper"
- way to do it? Go ahead and then "fsck", kill init and reboot,
- or what? I don't quite know what the "being more careful"
- really means here.
-
- Richard
-