Mdv2009.1 takes ages to boot up

[Chitta Mandal]

The problem is system specific. Booting remains stuck
at "detecting new hardware" for a long time. There is
no feedback during regular boot up (the "unsafe" mode).

-C

[Norman Carver]

On Monday 22 June 2009 10:35:56 pm Chitta Mandal wrote:
> The problem is system specific. Booting remains stuck
> at "detecting new hardware" for a long time. There is
> no feedback during regular boot up (the "unsafe" mode).

Make it so that harddrake does not run at boot.
You can do this through the MDV Control Center
by going to System > Manage system services.
Uncheck "on boot" for harddrake.  I do this for
every install (along with several other services
that I do not want/need).  Why does it need to probe
your hardware at each boot?  I don't change hardware
that often.  :)
Norm

[jpb-5]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Le mardi 23 juin 2009, Chitta Mandal a écrit :
> The problem is system specific. Booting remains stuck
> at "detecting new hardware" for a long time. There is
> no feedback during regular boot up (the "unsafe" mode).
>
> -C
I had that when booting from a external (USB) drive, do you are in this case ?
FYI new kernels in 2009.1 seem to lessen the problem,

JPB

[Chitta Mandal]

On Tue, 2009-06-23 at 12:08 -0500, Norman Carver wrote:

> > The problem is system specific. Booting remains stuck
> > at "detecting new hardware" for a long time. There is
> > no feedback during regular boot up (the "unsafe" mode).
>
> Make it so that harddrake does not run at boot.
> You can do this through the MDV Control Center
> by going to System > Manage system services.
> Uncheck "on boot" for harddrake.  I do this for
> every install (along with several other services
> that I do not want/need).  Why does it need to probe
> your hardware at each boot?  I don't change hardware
> that often.  :)

It would be nice to have an option to start a daemon
such as harddrake, well after the system is up and running.
What happens if the "on boot" flag is unchecked? Does that
service not start up at all then?

-C

[Norman Carver]

On Tuesday 23 June 2009 03:35:22 pm Chitta Mandal wrote:
> It would be nice to have an option to start a daemon
> such as harddrake, well after the system is up and running.
> What happens if the "on boot" flag is unchecked? Does that
> service not start up at all then?

harddrake isn't something that runs all the time, just
a service that runs at boot to see if there is new hardware.
If you are going to install new hardware, simply set harddrake
to run at next boot, before you shut down that machine to
change the hardware.  No big deal.  Plus you can easily run it
whenever you want--it is what does hardware configuration
in the MDV Control Center:  Hardware > Browse and Configure.
Norm