On Tuesday 31 October 2006 9:36 pm, Silviu Marin-Caea wrote:
> On Monday 30 October 2006 17:53, Rasmus Plewe wrote:
> > If a fsck at boot time occurs
> > - kill the splash screen (usually the computer boots in 3 minutes, now
> > it's still unchanged after 10 minutes. Something must be broken.
> > Poweroff/on. Does still not boot. Damn Linux, doesn't work. Changing
> > OS because Linux doesn't work for me).
This is frighteningly true, here are 2 suggestions,
we probably need them both.
1) While an fsck is occurring in non-verbose startup mode
we need a message to that effect with a progress bar.
2) On shutdown; if a routine fsck WOULD happen next reboot,
the OS asks if the user minds converting the shutdown to a reboot.
The fsck can happen on a fresh boot but not when the computer is needed.
Once booted the system puts up a window a la Mac,
waits 2 minutes and shuts back down automatically.
With the fsck done, the next reboot happens normally.
How long does it have to take to boot Linux?
Solaris used to usually boot quickly, unless you touched /reconfigure,
then it would go through all the hardware detection.
Is anyone working on an "express boot"
that gets the system up quickly based on stored hardware configs?
With all the hotplug functionality we now have
hardware detection at boot is a bit unnecessary.
michaelj
PS: I'm sad about loosing reiserfs
--
Michael James [EMAIL PROTECTED]
System Administrator voice: 02 6246 5040
CSIRO Bioinformatics Facility fax: 02 6246 5166
No matter how much you pay for software,
you always get less than you hoped.
Unless you pay nothing, then you get more.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
