HOWTO: Reducing boot time in Ubuntu using InitNG

[Trigger|Debian]

Hi all!

For we have an outdated howto in this forum which is always found by the users I open this thread here.

For information how to install Initng on Ubuntu please read this wiki page: https://wiki.ubuntu.com/InitNG
When you find problems with Initng please open a ticket at http://initng.thinktux.net/ and I will try to solve it upstream.

Now try to reboot.
Last step: Tell me what happened.[/INDENT]

When you are running 0.5.5 or 0.6.0 please execute "sudo ng-update a system/modules/depmod system" - otherwise you will have problems with the volatile kernel modules.

NEWS
initng 0.6.0 and initng-ifiles is out. http://triggerit.tr.funpic.de/blog/?p=40 should give you all the Information you need.
Most important part: First install the initnng-ifiles package and afterwards the Initng package!

P.S: More Information will follow here...

[yanns]

Hi!

I'm using initng for bootin.g.

I am now testing it to start / stop services manually.

I tried "sudo ngstart daemon/vmware"
And the result is:

This terminal has 80 cols and 24 rows

 Next Generation init Control. version ( 0.5.5 )
 http://initng.thinktux.net
 Author: Jimmy Wennlund <jimmy.wennlund@gmail.com>

Starting service:


Warning, service "daemon/vmware" is in status: "DAEMON_FAIL_STARTING"


   [ERROR] -->> Service "daemon/vmware" was failed, but found.
Will not make an attempt to reset service state and try again


Trying to start "daemon/vmware" again ...

Starting service:

   [ERROR] -->> Failed to start service, "daemon/vmware" (DAEMON_WAITING_FOR_START_DEP)

   [ERROR] -->> Failed to start service, "daemon/vmware" (DAEMON_FAIL_STARTING)

$ sudo ngc -L
[...]
10:19:56 vmware                                : FREEING
10:20:06 deamon/vmware                         : FREEING
10:20:11 daemon/vmware                         : LOADING
10:20:11 daemon/vmware/vmnet                   : LOADING
10:20:11 daemon/vmware/vmnet                   : DAEMON_WAITING_FOR_START_DEP
10:20:11 daemon/vmware/vmnet                   : DAEMON_WAITING_FOR_START_DEP
10:20:11 daemon/vmware                         : DAEMON_WAITING_FOR_START_DEP
10:20:11 daemon/vmware                         : DAEMON_WAITING_FOR_START_DEP
10:20:11 daemon/vmware/vmnet                   : DAEMON_LAUNCH
10:20:11 daemon/vmware/vmnet                   : DAEMON_RUNNING
10:20:11 daemon/vmware/vmnet                   : DAEMON_RUNNING
10:20:11 daemon/vmware                         : DAEMON_LAUNCH
10:20:11 daemon/vmware                         : DAEMON_FAIL_STARTING
10:20:11 daemon/vmware                         : DAEMON_FAIL_STARTING
10:20:11 daemon/vmware/vmnet                   : DAEMON_FAIL_STARTING
10:20:12 daemon/vmware                         : FREEING
10:20:13 daemon/vmware                         : LOADING
10:20:14 daemon/vmware                         : DAEMON_WAITING_FOR_START_DEP
10:20:14 daemon/vmware                         : DAEMON_WAITING_FOR_START_DEP

I dunno what's happening...
(sudo /etc/init.d/vmware start is ok)

[Zeroangel]

Will the 386 deb package work with the 686 and K7 kernels?

[yanns]

Yes, it's working.
(tested with 686)

[Trigger|Debian]

Will the 386 deb package work with the 686 and K7 kernels?

Sure.
The Kernel has nothing todo with the user space in this case.

@yanns: IIRC the vmware script is completely broken. Maybe you want to open a ticket at http://initng.thinktux.net/

[zgerrz]

Is there any way to easily modify exactly what InitNG is loading at startup? Such as being able to configure which modules or loading through a config text file?

Also, to upgrade InitNG, could I just use sudo dpkg -i newInitNGversion to upgrade InitNG to the latest version, or have there been problems in upgrading this way? I'd rather not have to reconfigure my loading settings again after an upgrade.

[Trigger|Debian]

Modules loading has nothing to do with Initng directly. You want to have a look at /etc/modules for such things.
If you meant services and daemons: yes, for sure. Everything happens in /etc/initng. There are two runlevels by now. system.runlevel and default.runlevel. This are the files you want to edit. Normally you use "ng-update" (see man "ng-update") but you can also edit them by hand.

Yes, upgrading works via "dpkg -i ...". If you have a running Initng the next reboot can be broken sometimes because of an API change - but I think I have a solution for this with the next release.

[zgerrz]

Ok, now I understand a lot more about configuring InitNG, thanks.

You mentioned it's best to configure the default runlevel. Is it still OK to play around with the system runlevel? For example, I would rather not run ntpdate because if my internet is down, it still continues to attempt to synchronize with the time server anyway.

[ninocass]

is it possible to enable bluetooth;s sdpd to run on startup?

[zi99y]

Having some problems after installing version 0.5.5

When I boot up with the specified bootloader that I have changed for initng, it will crash 50% through bootup on the system/coldplug/scsi line.

I've tried all key combinations I can think of but the only thing I can do at this stage is press ctrl-alt-delete to shutdown/reboot.

Can anyone tell me where I can look for relevant logs or any other ideas for tracking down the culprit?

thanks