Michael James <[EMAIL PROTECTED]> writes:

> 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.

Could you add those to the feature wishlist in our wiki so that it
does not get forgotten?

>
> 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

You're not loosing it - just the default is changed.  Feel free to
change it for your installs,

Andreas
-- 
 Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

Attachment: pgpe5icYxLhNF.pgp
Description: PGP signature

Reply via email to