[TriLUG] Re: reboot experience

[Ben Pitzer]

The current Debian Woody (stable) install does ask if you want to use ext2
or ext3 file systems during the install process.  I did that while
installing on a Ultra1 I have at work, and the ext3 file systems have been
fine thus far.  Of course, I also haven't had any crashes or hangs as yet,
which is pretty much par for the course in Debian's stable distro.  (I am
interested to know which Debian distro Mike is using that hung on him)  My
Debian Woody system at home is extremely stable, and only has an uptime
under 100 days thanks to the power outage (and if I'd have had enough
battery to keep it running for 30 hours, it would still be up).

Regards,
Ben Pitzer

---------------------------------------------

"Those that can give up essential liberty to obtain a little temporary
safety
 deserve neither liberty nor safety."
 --Ben Franklin--





> -----Original Message-----
> From: trilug-admin at trilug.org [mailto:trilug-admin at trilug.org]On Behalf
> Of James Manning
> Sent: Wednesday, January 15, 2003 1:42 PM
> To: trilug at trilug.org
> Subject: [TriLUG] Re: reboot experience
>
>
> > [Mike M]
> > Or did I just get unlucky this time?
>
> unlucky - most of the time it can fsck and recover on its own, this
> time it couldn't and rather than make a bad assumption, it wanted you
> to get involved.
>
> However, it's kind of also the "lack of consumer-oriented" since it's
> a result more of running a non-journalling filesystem (ext2) rather
> than something journalling-based (ext3, reiser, whatever) like most
> other distros targeted for consumers would have you run.
>
> Course, maybe Debian has an "upgrade your ext2 to ext3" path, I
> haven't checked.
> --
> James Manning <http://www.sublogic.com/james/>
> GPG Key fingerprint = B913 2FBD 14A9 CE18 B2B7  9C8E A0BF B026 EEBB F6E4
> _______________________________________________
> TriLUG mailing list
>     http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ:
>     http://www.trilug.org/~lovelace/faq/TriLUG-faq.html
>