Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
On Thu, Mar 27, 2008 at 10:48:58AM -0400, Mark Hertel wrote: > On 3/27/08, Brendan <[hidden email]> wrote: > > But Linux does this when you've shut it down correctly. Windows only does it > when you've screwed up by turning off the power instead of an orderly > shutdown. Two things: First, the usual criteria for deciding on whether or not to do a full fsck is either N mounts, or T days, since the last fsck. Second, if you want to change this behavior, you can. Useful things to try: - run fsck manually - run fsck automatically at shutdown time instead of startup time - use a journalling filesystem (ext3, xfs, jfs...) which will reduce fsck times immensely -dsr- -- Restore our Constitutional rights. http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Discuss mailing list [hidden email] http://lists.blu.org/mailman/listinfo/discuss
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |