HowTo: Speed up ubuntu boot process - the way you can feel it. [Archive] - Page 2

View Full Version : HowTo: Speed up ubuntu boot process - the way you can feel it.

Pages : 1 [2]

ciscosurfer

August 9th, 2006, 04:37 PM

What's the diff between GMT and UTC?
A bit more info on the differences (not related to *nix):
http://www.dxing.com/utcgmt.htm
http://ubuntuforums.org/newreply.php?do=newreply&p=900481

Well, it says he doesn't allow GUI editing of the rcS.d services (which are the Single User mode services), he still allows editing of all the other run level scripts.
rcS.d services are startup scripts -- they are executed once when booting the system, even when booting directly into single user mode.
rc1.d services are single user mode scripts.

rc0.d / K20bittorrent
rcS.d / brltty #ppl with special needs
rc0.d/K20festival 2,3,4,5 ###its for reporting something to CANONCIAL,cant remember what these are safe to remove. Leave the others as they are

bittorrent >> http://ubuntuforums.org/showthread.php?t=197127
http://packages.ubuntu.com/dapper/net/bittorrent

brltty >> Access software for a blind person using a soft braille terminal
http://packages.ubuntu.com/dapper/admin/brltty

festival >> Doesn't report anything to Canonical. It's a general multilingual speech synthesis system: http://packages.ubuntu.com/dapper/sound/festival

lennox

August 10th, 2006, 08:12 AM

There is a little typo in the Howto:

runlevel 2,3,4,5: in debain system, the multi-user env, may not may not include GUI. The same, processes under each of the corresponding dirs will be run. **Note** this is

ciscosurfer

August 13th, 2006, 06:21 AM

Bootime is now ~19 seconds for me =D>; Shutdown is now ~15 seconds! Hazzah! \\:D/

stanz

August 14th, 2006, 09:36 PM

Yeah...will there be a similar thread for the Dapper Drake release? :) It will be very useful...
Hi All...Has Mishal's question been answered?
I ask, cause I'm working on a 'Fresh Install' & have begun tweaking &
finding New & Different, files & such.
One new file ~ for ME - is a 'hdparm' script, in /etc/init.d.
In Breezy - I made mine...then with UpGrade - mine stayed...nothing new.
But this script, I can't figure out! Me no code braker.. :mrgreen:
- Would tweaking the new Dapper file, be better? or might be a Must?
- Switching won't be a problem?

Any advice for us?
Thanks in Advance....:rolleyes:

iamhugeinjapan

August 15th, 2006, 07:35 PM

also, here's a one line hack that worked good for me on breezy ... run startup scripts in parallel, merely by changing the startup script: /etc/init.d/rc

Changing the line:

startup $i start

to the following:

startup $i start &

from:
http://www.debian-administration.org/articles/199
http://www.hoeg.org/blog/2005/07/27/fast-booting-debian/

The code in the file appears to be different in Dapper as the referenced line does not appear. There is however a comment that appears a few times that says:
"# Run all scripts with the same level in parallel"

So maybe it's already doing it? If not can someone point out the relevant bit to change? Thanks

ardchoille

August 15th, 2006, 11:52 PM

This is one outstanding post! This information has helped me to get Ubuntu booting much faster. Thank you very much for taking the time to explain it all :)

LKRaider

August 20th, 2006, 12:01 AM

Very useful thread!

I also found this page: wiki.ubuntu.com/Teardown
it lists several shutdown and reset services (rc0 & rc6) that can be safely removed because they will be finished by the term signal in the same manner.

I also made a nice little script that disables/enables the rc0/6 services for me very easily. I just input a list of services (by their names, no need to know the KXX stuff) and it changes their state to either enabled or disabled (renames the initial K as per first post instructions) ^_^

I am thinking of developing it further with a GUI and all... we'll see :P

ashrack

August 20th, 2006, 04:49 AM

This TEARDOWN info is great. Should be the first post!!! As it makes certain options in the first post obsolete.

lassegs

August 29th, 2006, 08:40 AM

Hi

I just wanted to say thanks for this great howto!

KhaaL

September 3rd, 2006, 06:23 PM

You can also cut down the boot time by change the sleep time in the sleep calls in /etc/init.d . enter the /etc/init.d directory and do "grep sleep *". note the filenames who makes the sleep calls, then edit them in a text editor and decrease the time. To what I've heard, you can cut down the time to 1, even 0.5 seconds, and the system will boot without a problem.

WARNING! I haven't tested this yet, according to the article this shouldn't cause any problems. Keep in mind that this isn't a ubuntu specific hack.

Rodrigo

September 8th, 2006, 05:31 PM

Xcelent, thanks, Im goint to test it right away :D

geearf

September 9th, 2006, 10:31 AM

Hey,

just a small message to maybe warn some of you, i don't relly know how this will work when you will update to edgy and use upstart. There is a compatiblity between sysv and upstart, but is there one with initng ?

Jeff D

September 11th, 2006, 09:13 PM

Hi quick question, when I type "sudo sysv-rc-conf" into the terminal I'm getting "sysv-rc-conf: command not found" and I'm unable to procede any further. Any reason why this would be happening? Before my Grub/Windows failure a week earlier I had no problem editing the boot process!?! Thanks in advance.

ciscosurfer

September 12th, 2006, 12:11 AM

You need to install it firstsudo aptitude update && sudo aptitude install sysv-rc-confThen run it from a terminal like you tried to do before.

Jeff D

September 12th, 2006, 12:24 AM

Tried that to no avail, here's what I'm getting...after Reading package lists... "sudo aptitude update" runs properly.

jeff@jeff-desktop:~$ sudo aptitude install sysv-rc-conf
Reading package lists... Done
Building dependency tree... Done
Initializing package states... Done
Building tag database... Done
No candidate version found for sysv-rc-conf
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information... Done
jeff@jeff-desktop:~$ sudo sysv-rc-conf
sudo: sysv-rc-conf: command not found

i3dmaster

September 13th, 2006, 12:48 AM

niko7865

September 13th, 2006, 02:50 AM

I removed a few things from boot and can no longer boot to my k7-smp kernel. Once the GUI Login screen (gdm?) is displayed it everything but the mouse will hang indefinitly after 5 seconds. I'm fairly sure I changed everything back to how it was but I still can't get intothe k7 (386 works fine, on it now). Should I ry removeing and then reinstalling my k7-smp kernel? Is there anyway to revert back to my old boot up? (I'm a noob and didn't write down how everything was before I started changing crap)

Richardky

September 13th, 2006, 08:32 AM

thx for the nice guide my first post and a total newb ... was easy to follow ...no probs

Jeff D

September 13th, 2006, 10:31 PM

You will need to enable the universal repo in your sources.list file. Its under /etc/apt/sources.list.

Thank you kindly! That did it.

drakedog

September 14th, 2006, 01:14 PM

Nice Tips, tnks. But how can i speed up the Filechecking, or skip it on startup?

ciscosurfer

September 14th, 2006, 01:21 PM

@drakedog: this will help you >> http://ubuntu.wordpress.com/2005/10/12/tuning-the-filesystem-check-at-bootup/

obf213

September 15th, 2006, 05:00 PM

help. i changed only wht the guide told me to change, and now when i do a reboot my computer just shuts down. also, on shut down it doest go through the process of shutting down any of the processes any more. normally it would say stopping ....., then shutting down alsa, stopping bluetoothutils etc. now the usplash comes up it says something like "configureing usplash time out" then it says will now halt and closes down in like 4 seconds. the it wont restart. hellllp wht did i do. i used the pictures and set everything back to default (according to the picture) but it still persists

ijjz

October 2nd, 2006, 03:02 AM

Thanks for the easy way of editing some start up processes.

TFrog

October 10th, 2006, 09:56 PM

This HowTo is for those who complaint ubuntu boot-up speed is pretty slow but not willing to install any alternative tools to speed up. The way I use here is not the altimate solution by any means but it does make differences and it does work. Everything done below is by tuning the boot process itself and because everyone's computer might be different, there is a little risk that something below might break your system. Take your own judgment before you perform a change and always good to do a backup for the /etc dir.

**This HowTo is mainly for laptops and desktops, not for servers.**

Suggestions for this HowTo:
1. I hope you learn something from here but not just a simple copy. So please, **DO NOT** follow exactly what I did and copy to your box. Read the descriptions of services and use your own judgment to determine if you need to keep them on or not. For instance, I turned GDM off on mine to boot to console, but if you do not feel confortable to see console at all, you should keep GDM or KDM on to boot directly to GUI.
2. If you have a question about a boot up service and not really sure what it does, post a question here and see if anybody can help you. Ask before you do if you don't know. The bottom line to be safe is to leave a service on rather than turn it off if you do not understand.
3. If you see a boot up service that you have but not in here, let us know what it does just like what I did here - give some descriptions and suggestions on whether it should be on or off on a normal laptop or desktop environment.

Color reference : service I turned on
service I turned off

Screen shots contrib'ed by domino for the initial bootup settings. A great reference for those who mess up on runlevels... Thanks!!

Page 1:
http://img485.imageshack.us/img485/9814/14ub.th.png (http://img485.imageshack.us/my.php?image=14ub.png)

Page 2:
http://img485.imageshack.us/img485/4586/25cr.th.png (http://img485.imageshack.us/my.php?image=25cr.png)

I. Install a tool - sysv-rc-conf. It is a perl based boot process adjustment tool.

sudo apt-get update
sudo apt-get install sysv-rc-conf

It gives you a way to esaily config the boot process and runlevel configuration, but its not necessary if you want to do it manually by linking/unlinking the files... Its up to you.

II. Ok, that's all we need. Now let's fire it up by

sudo sysv-rc-conf

and analyze each service one by one. **Note:** Some services I have here you might not have, perfectly ok. If some you have but I don't, then you will need to investigate on your own or ask here... But this HowTo should cover most of them...

Throw a littel bit of runlevel knowledge here before we start messing them up.... All the boot processes are executed in sequence as following:
runlevel S: the first runlevel in boot process. /etc/init.d/rcS script will be invoked to start and all the processes underneath /etc/rcS.d will be executed.
runlevel 1: the single user mode. All processes underneath /etc/rc1.d will be executed.
runlevel 2,3,4,5: in debain system, the multi-user env, may not may not include GUI. The same, processes under each of the corresponding dirs will be run. **Note** this is different than RedHat, SuSE, and other RPM based systems.
runlevel 0: computer shutdown.
runlevel 6: computer reboot.

ok, back to sysv-rc-conf:

1. acpi-support - You'd better leave it on the default runlevel. The default is 2,3,4,5.
2. acpid - The acpi daemon. These two are for power management, quite important for laptop and desktop computers, so leave them on. The default is 2,3,4,5
3. alsa - If you use alsa sound subsystem, yes leave it on. But if you have the service below, its safe to be off. The default is off when alsa-utils is on.
4. alsa-utils - On my system, this service supercedes the alsa, so I turn off the alsa and turn this on at S level. **Note**, I mean "turn off" is to remove all "X" at all runlevels. If you don't have it on your system, no problem. Just keep going. The default is S runlevel.
5. anacron - A cron subsystem that executes any cron jobs not being executed when the time is on. Most likely you've probably turned your computer off when a certain cron job time is ready. For example, updatedb is scheduled at 2am everyday, but at that moment, you computer is off, then if anacron service is on, it will try to catch up that updatedb cron... I turn it off cause it didn't turn my laptop off very offen, but its totally up to you for this one. The default is 2,3,4,5
6. apmd - This is the one that confused me a quite bit. I have acpid on already and what's the benefits of having apmd on too? If you computer is not that old which can't even support acpi, then you may try to turn this off. I did anyway. The default is 2,3,4,5
7. atd - like cron, a job scheduler. I turned it off. The default is 2,3,4,5
8. binfmt-support - Kernel supports other format of binary files. I left it on. The default is 2,3,4,5
9. bluez-utiles - I turned it off. I don't have any bluetooth devices. The default is 2,3,4,5
10. bootlogd - Leave it on. The default is S.
11. cron - Leave it on. The default is 2,3,4,5
12. cupsys - subsystem to manager your printer. I don't have so I turned it off, but if you do, just leave it on. The default is 2,3,4,5
13. dbus - Message bus system. Very important, leave it on. The default is 2,3,4,5
14. dns-clean - Mainly for cleaning up the dns info when using dial-up connection. I don't use dial up, so I turn it off. The default is S.
15. evms - Enterprise Volumn Management system. I turned it off. The default is S.
16. fetchmail - A mail receving daemon. I turned it off. The default is 2,3,4,5
17. gdm - The gnome desktop manager. I turned it off anyway since I get use to boot to console first. This is up to you if you want to boot directly to GUI. The default is 2,3,4,5
18. gdomap - Actually I have no idea why this one should on. I didn't see any other systems have this daemon, so I turned it off and I don't feel I lose anything. Any benefits to have it on a loptop or desktop? The default is 2,3,4,5
19. gpm - Mouse support for console. If you feel you'd better have a mouse on console, go turn it on at runlevel 1 and 2. That's all you need. The default is 2,3,4,5
20. halt - Don't change it. The default is 0.
21. hdparm - tuning harddisk script. I removed the 2,3,4,5 runlevel but add it to S runlevel. I feel that opening DMA, 32bit I/O, etc eariler will benefit the rest of the processes. Also I changed the original script to a very simple one that I made myself. I feel useless to put all those redundant checks if I know what I am doing. The configuration file is /etc/hdparm.conf. The default is 2,3,4,5
22. hibernate - If your system support hibernate, leave it on. Otherwise, its useless for you. The default is S.
23. hotkey-setup - This daemon setup some hotkey mappings for Laptop. Manufacturers supported are: HP, Acer, ASUS, Sony, Dell, and IBM. If you have a laptop in those brands, you can leave it on, otherwise, this might not have any benefits for you. The default is 2,3,4,5
24. hotplug and hotplug-net #activating hotplug subsystems takes time. I'd consider to turn them off. I did some changes in my /etc/network/interfaces file. Instead of mapping my wireless card during hotplug process, I set it up to auto. So I can turn them off. I've tested even I turned them off, ubuntu can still detect my usb driver, my digital camera, etc. So I think its pretty safe to turn them off. **Note** If you find your sound card doesn't work after turning hotplug service off, you can turn it back. Or edit /etc/modules file to add your sound card's driver module. Tested out the later one is faster. The default is S.
25. hplip - HP printing and Image subsystem. I turned it off. The default is S.
26. ifrename - network interface rename script. Sounds pretty neat but I turned it off. Mainly for managing multiple network interfaces names. Since I have a wireless card and an ethernet card, they all assigned eth0 and ath0 from kernel, so its not really useful for me. The default is S.
27. ifupdown and ifupdown-clean - Leave it on. They are network interfaces activation scripts for the boot time. ifupdown default is 0,6,S and ifupdown-clean is S.
28. inetd or inetd.real - take a look your /etc/inetd.conf file and comment out any services that you don't need. If there aren't any services there, then its very safe to turn them off. The default is 2,3,4,5
29. klogd - Leave it on. The default is 2,3,4,5
30. laptop-mode - A service to tweak the battery utilization when using laptops. You can leave it on. The default is 2,3,4,5
31. linux-restricted-modules-common - You need to see if you really have any restricted modules loaded on your system. Since I need madwifi ath_pci module, so I left it on. The restricted modules can be found from /lib/linux-restricted-modules. If you find that you are not using any of the restricted modules, then its ok to turn it off. The default is 0,6, and S.
32. lvm - I don't use it so I turned it off. Leave it on if you *DO* have lvm. The default is S.
33. makedev - Leave it on. The default is 2,3,4,5
34. mdamd - Raid management tool. I don't use it so I turned it off. The default is 2,3,4,5
35. mdamd-raid - Raid tool. If you don't have Raid devices, turn it off. The default is S.
36. module-init-tools - Load extra modules from /etc/modules file. You can investigate your /etc/modules file and see if there is any modules that you don't need. Normally, this is turned on. The default is S.
37. mountvirtfs - mount virtual filesystems. Leave it on. The default is S.
38. networking - bring up network interfaces and config dns info during boot time by scaning /etc/network/interfaces file. Leave it on. The default is 0,6,S
39. ntpdate - Sync time with the ubuntu time server. The default is S. QUOTED: "If you are dual-booting with Windows, it is probably a good idea to leave ntpdate on. Windows can only deal with the hardware clock set to local (not UTC) and Linux needs ntpdate to correct this, otherwise your clock will increase an hour everytime you boot into Linux from Windows." Thanks dejitarob for the update!! I don't have dual boot, so I turned it off, but if you have multiple systems, suggestion is to turn it on.
40. nvidia-kernel - I compiled the nvidia driver by myself, so its useless for me now. If you use the ubuntu nvidia driver from the restrict modules, just leave it on. The default is 1,2,3,4,5
41. pcmcia - Active pcmcia device. I changed it to start on 0,6,S runlevel instead of on each 2,3,4,5 cause I feel its better to have hardware device ready at first. Also, useless if you are using desktop which doesn't have pcmcia card. So in that case, turn it off please. The default is 2,3,4,5
42. portmap - daemon for managing services like nis, nfs, etc. If your laptop or desktop is a pure client, then turn it off. The default is 2,3,4,5,0,6,S
43. powernowd - client to manage cpufreq. Mainly for laptops that support CPU speed stepping technology. Normally, you should leave it on if you are configuring a laptop, but for desktop, it might be useless. The default is 2,3,4,5
44. ppp and ppp-dns - Useless to me. I don't have dial-up. The default for ppp is 2,3,4,5 and pppd-dns is S.
45. readahead - **Thanks mr_pouit!** It seems readahead is a kind of "preloader". It loads at startup some libs on memory, so that some programs will start faster. But it increases startup time for about 3-4 seconds. So, you can keep it... or not . **update**, I tested and I just didn't feel difference loading programs. So I decided to turn it off. If you have a reason to keep it on, please do so. The default is S
46. reboot - Don't change it. The default is 6
47. resolvconf - Automatically configuring DNS info according to your network status. I left it on. The default is S.
48. rmnologin - Remove nologin if it finds it. It wouldn't happen on my laptop, so I got rid of it. The default is 2,3,4,5
49. rsync - rsync daemon. I don't use it on my laptop, so turned it off. The default is 2,3,4,5
50. sendsigs - send signals during reboot or shutdown. Leave it as it is. The default is 0,6
51. single - Active single user mode. Leave it as it is. The default is 1
52. ssh - ssh daemon. I need this so I turned it on. The default is 2,3,4,5
53. stop-bootlogd - stop bootlogd from 2,3,4,5 runlevel. Leave it as it is. The default is 2,3,4,5
54. sudo - check sudo stauts. I don't see any good to run it everytime on a laptop or desktop client, so I turned it off. The default is S
55. sysklogd - Leave it as it is. The default is 2,3,4,5
56. udev and udev-mab - Userspace dev filesystem. Good stuff, I left them on. The defaults are all S runlevels.
57. umountfs - Leave it as it is. The default is 0,6
58. urandom - Random number generator. Might not useful but I left it on. The default is 0,6,S
59. usplash - Well, if you really want to see the nice boot up screen, leave it as it is. I just turned it off anyway. If you want to turn it off, you also need to edit /boot/grub/menu. lst file to comment out the splashimage line and get rid of the splash kernel boot option. The default is 2,3,4,5
60. vbesave - video card BIOS configuration tool. Its able to save your video card status. I left it on. The default is 2,3,4,5
61. xorg-common - setup X server ICE socket. I moved it from starting at runlevel S to runlevel 2,3,4,5. Since I don't need this if I boot to single user mode. This way it wouldn't occupy time during the initial booting. The default is 2,3,4,5
============ My bootup services end up here============

============ Some services from others================
62. adjtimex - This is a kernel hw clock time adjusting too. Normally, you shouldn't see this on your boot up list. In very rare case if you do see its on your boot up process, then there might be a reason why it is on, so better leave it that way. In my case, it is off.
63. dirmngr - A certification lists management tool. Work with gnupg. You will have to see if you need it or not. In my case, I turned it off. Default runlevel 2,3,4,5
64. hwtools - A tool to optimize irqs. Not sure what's the benefits of turning it on. In my case, I turned it off.
65. libpam-devperm - A daemon to fix device files permissions after a system crash. Sounds pretty good, so I left it on.
66. lm-sensors - If you matherboard has builtin some sensor chips, it might be helpful to see hw status via userspace. I ran it and it said "No sensors found", so I turned it off.
67. screen-cleanup - A script to cleanup the boot up screen. Well, turn on or off is up to you. In my case, I left it on. The default is S
68. xinetd - A inetd super daemon to manage other damons. In my system, the xinetd is managing chargen, daytime, echo and time (find them from /etc/xinetd.d dir), I care none of them, so I turned it off. If you do have some important services configured under xinetd, then leave it on.

III. Alter the /etc/inittab file
vi /etc/inittabthen comment out tty4,tty5, and tty6. Just leave tty1, tty2, and tty3. Three vts should be enough for a laptop or desktop user. Save the file.

IV. Ok, now, we can reboot our box and see how it goes. From what I've tested, before I got tons of services stopped, the whole process is about 85 secs to 90 secs to boot to console. (At that time, I also has samba and nfs services turned on which I shouldn't. Apparently, I turned them off too). After this change, the whole boot up process took about 50 secs. I have a P4M 1.8G CPU laptop. Some of the high-end desktops or laptops should take even less time.

**UPDATE**: speed up/clean system reboot or shutdown process.
1. start sysv-rc-conf by issuing:sudo sysv-rc-conf
2. ok, open your eyes and look very carefully for those SERVICES THAT DO NOT HAVE A "X" ON ANY RUNLEVELS (Any runlevel means 1,2,3,4,5,6, and S), write them down one by one. Don't make mistakes here. Double check after you've done. Thanks ice60 for wording recommendation!
3. quit sysv-rc-conf.
4. cd /etc/rc0.d - This is for the system shutdown process.
5. ok, now, ls K* will list all links starting from UPPERCASE letter "K". Compare with your list, change each of the filename containing the service name in your list to start from a lowercase "k". For example, in your list, you have ppp service (which means ppp is turned off at all runlevels), then you can do like: sudo mv K00ppp k00ppp. You just change the UPPERCASE K to lowercase k, keep the rest the same. Do this on all of the services in your list.
6. cd ../rc6.d - This is for the system reboot process.
7. ok, you should see similar things here too. So do the same thing here as you did on rc0.d.
8. Now, you reboot and shutdown process should be cleaned up and faster.

The explanation for what you did is pretty simple. The /etc/rc and /etc/rcS scripts run start on each link on each runlevel by scaning if it is starting with a UPPERCASE "S" and run stop on each by scaning if it is starting with a UPPERCASE "K". So for reboot and shutdown runlevels, the most thing we care is the "K" links cause for those services not running on all runlevels, its just not needed to stop them. They are not runing at all. If some day you want to turn some of the services back on, just change the lowercase "k" to UPPERCASE "K". That's all.

Anyway, it is not intend to work on servers, but I did try on one of my servers has 2.7G P4 and 1.5G mem. It brought the boot process down to 31 secs. I calc'ed it with my watch. Besides, this is with my ftp server and nfs server started on boot time.

**Note**
For all of those that having HAL failure problem, try this:
1. change acpi-support from S to 2,3,4,5
2. change acpid from S to 2,3,4,5
3. change dbus from S to 2,3,4,5
4. Reboot. Go to the console and do ps -aef|grep hald. If hald service is up, then your dbus subsystem is running fine now. Try it.

Great comments added by bodhi.zazen. Thanks!!
First we should make sure we are left with a bootable system and have backups.

Since we are changing our boot process:

Step 1- Make a bootable GRUB floppy.

http://www.linuxjournal.com/article/4622

Step 2- Backup
Is there any need to back up more then menu.1st, /etc/init.d, /etc/rcS.d, and /etc/rc*.c ( *= 0,1,2,3,4,5,6)?
mkdir /~/bakup.files
sudo cp -P /etc/init.d /~/backup.files
sudo cp -P /boot/grub/menu.1st /~/backup.files
sudo cp -P /etc/rc*.d /~/backup.files
Although a backup of /etc is nice, is it not overkill for this exercise?

Setp 3- Know you Ubuntu Root device (hda1, hdb1, hda2,) and kernel (the numbers in "vmlinuz").
Location of kernel is /boot

Step 4- Modify runlevels.
DO NOT MODIFY DEFAULT RUN LEVELS 0,1, OR 6
MODIFY ONLY 1 RUN LEVEL AT A TIME
RUN LEVEL "S" IS RUN AT EACH RUN LEVEL PRIOR TO OTHERS
ie as system boots (at default) the scritps in rcS.d are run first, then rc2.d

Therefore, if you disable a script in "S", enable the script in runlevel 2
This should guarantee your system will remain bootable to the default run level (2)

In Ubuntu the default run level is 2
Modify only 1 test run level at a time. Choose a custom run level (I will use 3 for the rest of this post, you can use 3,4, or 5).
After modifying the runlevel test without re-booting
sudo init 3
This will change to run level 3
Now check your system.
Problems? Return to default run level and re-configure run level 3
sudo init 2
No problem -> Boot from floppy
No problem, boot from floppy.
When booting (from diskette) to the default run level, the "kernel" line looks like:
kernel=/boot/vmlinuz-2.6.8.1-3-386 root=/dev/hda1 ro quiet splash
In menu.1st this looks like this:
kernel /boot/vmlinuz-2.6.8.1-3-386 root=/dev/hda1 ro quiet splash
To boot to run 3 (from GRUB diskette), add a "3" at the end of the line
kernel=/boot/vmlinuz.... root=/dev/..... ro quiet splash 3
Note: the number 3 was added at the end (without quotes)
time boot process.
If OK boot again from floppy (to default run level)
kernel=/boot/vmlinuz..... root=/dev/....
Note: no number 3 at the end of this line
time boot process
This is the default boot and you can measure any time savings.
booting from a floppy to compair apples to apples
If OK you can now change the default run level (or not)
There is more then 1 way to do this
My preferance is to leave the default runlevel unmodified
This leaves the default boot process as a future referance
Change the default boot level
sudo nano /boot/grub/menu.1st
add init=3 to end of line

kernel /boot/vmlinuz-2.6.8.1-3-386 root=/dev/hda1 ro quiet splash 3

Or create 2 Ubuntu titles, one for each run level.

OR

Edit /etc/inittab

Step 4- Modify shutdown scripts if desired.

This process should guide users through a logical process of modifying boot scripts without generating a non-bootable system. Backups were made "just in case" but really should not be needed.

Works great for Dapper. However, they've changed some things in Edgy Eft. Though quick to boot up it still holds the tty4, tty5, and tty6 open and I've yet to figure out where to turn them off in Edgy Eft. However, the rest of your how to works for Edgy even :D

emarkay

October 15th, 2006, 12:28 PM

Interesting.

How up-to-date is the first post (have all the changes in the following 27 pages been edited in?)

Would it be possible to get this into a document or an actual HTML page for easy printing?

Thanks!

CoffeeAddict

October 18th, 2006, 06:45 PM

Hello All,

I used this guide to speed up my boot process and mostly, it was fine.
The process is quite a bit quicker now.

Unfortunately, my network card doesn't seem to get activated on startup
anymore. If I start up network-admin and activate it, everything works fine, so it's not a huge deal, but it's still annoying. I don't really know what did this since I deactivated neither networking nor any kernel modules or pcmcia or anything. I did initally deactivated ppp and dns-clean, but I already tried reactivating it and that didn't help.

I only really deactivated bluetooth and raid support and cupsys and festival (a text-to-speech system).

Does anyone have an idea what could have caused this ( or how I can correct it, in any case) ? :-k

Thanks in advance,

CoffeeAddict

Malakia

October 20th, 2006, 05:17 PM

Can somebody please help me.I followed the guide exactly but when it restarts its says Alert! /dev/hda1 doesn't exist . Dropping to shell, where it goes into an ash shell. I can boot with recovery option but not reguarly. I have looked everywhere else and haven't found a solution.

Malakia

October 20th, 2006, 05:20 PM

Whatever the problem was the kink got worked out. Thanks anyway.

learning

October 27th, 2006, 10:33 PM

This made a big difference for me in edgy. Thank you!

domino

October 28th, 2006, 03:18 AM

I've only managed shave off ~3 seconds when trying this on Edgy. From 35 to 32. I don't think it make much difference trying this in Edgy unless Edgy has a totally different way to reducing boot time. I would like to get down to 15-20 seconds on a fresh install :).

jamescbjr

October 29th, 2006, 06:42 PM

Can someone help me please, my pc stalls at boot up because I get disconnected from the systems message bus. I can not find the cause.](*,) My boot chart. Might help in diagnostic. Thanks In advance for any assistance.

daemon.log

Oct 29 09:07:56 -panama hcid[4577]: Got disconnected from the system message bus

messages

Oct 29 09:01:25 -panama kernel: [17179597.608000] IPv6 over IPv4 tunneling driver
Oct 29 09:07:56 -panama exiting on signal 15
Oct 29 09:09:44 -panama syslogd 1.4.1#18ubuntu6: restart.

paul6

November 1st, 2006, 12:56 AM

Does this guide still work with Edgy? Now that (I think) they have replaced Sysvinit with Upstart?

Azerthoth

November 2nd, 2006, 10:08 PM

Boot process is changed and the documentation for the changes is horrid. There is a README in the /etc/init.d/ section or somewhere further down that branch that referance a document on the debian website. Problem is it doesnt give any info for what init is calling on. No clue what they changed initab to ](*,)

TFrog

November 7th, 2006, 02:05 PM

I haven't seen any info on the Edgy boot process either. Bits and pieces of this "How To" do work but it's very little. Thus my request that this be updated.

elettronicha

November 7th, 2006, 02:15 PM

Indeed this how-to is unsuitable to Edgy, since Edgy replaced the init system with 'upstart' that's faster than the old init.

Sokraates

November 7th, 2006, 06:52 PM

Upstart in this early stage still relies on init-scripts. So this how-to still works (at least it does for me).

What errors or problems do you see when applying this how-to to edgy?

K.Mandla

November 12th, 2006, 06:16 PM

Does this guide still work with Edgy? Now that (I think) they have replaced Sysvinit with Upstart?
Yes. The services are rearranged into /etc/rc0.d/, /etc/rc1.d/, etc., with much of inittab arrayed into /etc/event.d/. You just need to track down the service and adjust it as you normally would.

civilian

November 18th, 2006, 04:20 AM

Works great for me, sped up boot time by a good 10 seconds. thanks a lot!.

i3dmaster

November 18th, 2006, 05:04 PM

The first thread has been updated and indicated that this customization is mainly for version before 6.10.

adka

December 2nd, 2006, 09:13 PM

thanks alot for the guide. Interesting to learn about the boot proccess

haxer

December 2nd, 2006, 09:18 PM

Sokraates

December 4th, 2006, 04:55 AM

Why even bother to boot it up? How many times are you rebooting? How often? I reboot werry often about 1/week at the most so why do i need to speed it up 10sec? what will i do in 10sec? Is there anything that you could do in 10sec wile waiting for you computer? Look at the tv for 10sec get an icecrimb paper opened ;)

I think some 10 or 20 pages ago we already had this discussion. Bottom line: There are a lot of people who reboot daily or even more often for various reasons, including saving power, being away from home most of the day etc.

Although now that you mention it, I should put the refrigerator next to my desktop-pc for easier access to icecream. Then I will revert all the changes I made to the boot-process so that I will have even more time to eat it. :D

But seriously, this How-to no longer feels as effective as before. Edgy already booted faster than Dapper and the optimizations did not gain me more than 2-3 seconds (I think from 29 to 27). Unfortunately I deleted my old bootcharts, but I think that I always saved about 10%-15% of the boot-time. The difference being, that vanilla Breezy took about 50 seconds to boot.

haxer

December 4th, 2006, 04:59 AM

I think some 10 or 20 pages ago we already had this discussion. Bottom line: There are a lot of people who reboot daily or even more often for various reasons, including saving power, being away from home most of the day etc.

Although now that you mention it, I should put the refrigerator next to my desktop-pc for easier access to icecream. Then I will revert all the changes I made to the boot-process so that I will have even more time to eat it. :D

But seriously, this How-to no longer feels as effective as before. Edgy already booted faster than Dapper and the optimizations did not gain me more than 2-3 seconds (I think from 29 to 27). Unfortunately I deleted my old bootcharts, but I think that I always saved about 10%-15% of the boot-time. The difference being, that vanilla Breezy took about 50 seconds to boot.

Sorry didnt know guess i was to late sorry.. erarum humunum est!

golem3

December 25th, 2006, 10:34 PM

worked for me. thanks. it seems that Ubuntu Edgy does not give a lot of the useless options on a clean install...I only had a few to turn off, such as Bluetooth.

ghostwriter

January 3rd, 2007, 04:08 PM

Sorry didnt know guess i was to late sorry.. erarum humunum est!

it's errare humanum est ;)

lotacus

January 15th, 2007, 08:51 AM

Does this honestly work? noticeably? I would LOVe an instant on system.

But i'm not complaining, it boots faster than Windows. Even shuts down faster. There are problems with hybernating and suspend, but that's not for this thread and i'm sure it's been discussed before.

To one of the posters who posted about why ppl would need to reboot, several cases for reboot as someone stated. Also alot of people have multiboot systems as myself, since there are things I do that requires Windows. .. Like play BF2142! LOL.

i3dmaster

January 15th, 2007, 05:37 PM

Yes, with the replacement of the old sysinit to upstart, it fundamentally addressed the majority of the long boot time issue. This thread wasn't originally prepared for upstart driven systems like 6.10+, so if you are 6.10 or +, then please refer to upstart related threads.

dothedorky

January 25th, 2007, 10:14 PM

I just wanted to say thank you. I tried this today and entire boot time took 24 seconds (and i left gdm on)

I also have a few services that were not on your or other's lists (i left them on because i wasn't sure)... I was wondering if you could help me figure out if i need them or not (cause im greedy, and a computer can never be too fast!)

here are the programs and the run levels they are on. (im a desktop user, with 6.06LTS) I ask about laptop-mode because i run a desktop computer, that i turn off every night...)

brltty s
lm-sensors s
festival s
laptop-mode 2,3,4,5
loopback s
mtab s
pcmciautil$ s
rc.local 2,3,4,5
rsync 2,3,4,5
screen s
stop-read$ 2
umountroot 0,6
x11-common s

berndwalterh

February 8th, 2007, 09:39 PM

Hi,

it seems that you have an error in your login feature of your forum. Everytimes if I want to stay logged in I´ll be automatically logged out within 1 minute.
I´ve already checked my firefox settings and they are all okay.

Do other members have the same problem?
_________________
homepage 1 (http://www.bproperties.info)
homepage 2 (http://www.webentrance.info)

lasder

February 11th, 2007, 12:09 PM

Fantastic job i3dmaster, it's a clear and good explained how-to :grin:

dothedorky

February 13th, 2007, 05:01 AM

*bumped*

still have a few programs i dont know if i need (or even what they are specifically for)

any help would be greatly appreciated.

kaczmarek

March 17th, 2007, 02:21 PM

Hi,

I was just wondering, why do some services need to be turned on multiple runlevels, eg. 2,3,4 and 5? What does this mean? Does that mean that these are re-run on each new runlevel? If that's true, why? A bit confused... :confused: :)

Thanks!

dannyboy79

March 19th, 2007, 08:03 AM

each run level is different so you would want the service to be available in each run level wouldn't you? here is an explaination ot run levels. http://www.networkclue.com/os/Linux/run-levels.aspx

Bill_Gates

March 23rd, 2007, 10:13 AM

Thanks for this guide.

shawnrgr

May 7th, 2007, 06:03 AM

Is this tip safe for Feisty?

dannyboy79

May 7th, 2007, 09:09 AM

it's safe for any linux version! it merely stops processes that you don't want to start at bootup and don't need.

housekid

May 28th, 2007, 07:47 PM

Thank you, thank you.
I have learned a lot, your the best!

linfidel

June 20th, 2007, 12:30 PM

Nice article, and lots of nice links. This is one of the first things I want to learn about in linux - how to control the startup, and what happens when, step by step.

Thanks to all the contributors.

macron1

June 29th, 2007, 04:05 AM

wow thanks man. this dramatically increased my bootup speed on a compaq presario v6000. just switched the ppp, bluetooth and the "readahead" (cant remember exact name) ones off. worked a treat.

st33med

August 21st, 2007, 08:59 PM

A program to disable: brltty.

Basically, it is for braille output devices in tty. If you're not blind, then disable this.

Yes

August 30th, 2007, 03:25 PM

Rui Pais

August 31st, 2007, 05:42 AM

I have three questions: 1) I have a bunch of duplicate processes, except that one of the duplicates ends with a '$'. Is it safe to delete processes that end in a '$'? 2) I have one process, 'nvidia-ke$'. I don't believe I have any nvidia hardware, so does that mean that it would be safe to delete that process? Or is there some other reason that it's running? 3) I don't have a file called /etc/inittab . I assume that this is because I'm using Feisty, and the file has since changed names. If this is the case, is there still a file in Feisty where I can disable tty4, 5, and 6?

Thank's for the great guide!

hi,

for 1)
the "repetead" ended '$' are just contractions of names that sysv-rc.conf do on long ones.
Be careful they are not repeated processes, but diferent ones.
As an example powernowd and powernowd$ are not the same thing. The second is powernowd.early, a name too long.
You can see the processes of each level by run (here for level 2):
ls /etc/rc2.d/

2) Never understamd that nvidia entry. It's not even useful for nvidia users (driver is loaded by xorg,conf), so even as a mvidia user i always turn that off.

3) The instructions no longer apply for feisty. Try my suggestion here (http://ubuntuforums.org/showpost.php?p=2843862&postcount=3). You may want to read the full thread (http://ubuntuforums.org/showthread.php?p=2843708#post2843708) for others comments and alternatives.

dannyboy79

August 31st, 2007, 08:32 AM

hi,

for 1)
the "repetead" ended '$' are just contractions of names that sysv-rc.conf do on long ones.
Be careful they are not repeated processes, but diferent ones.
As an example powernowd and powernowd$ are not the same thing. The second is powernowd.early, a name too long.
You can see the processes of each level by run (here for level 2):
ls /etc/rc2.d/

2) Never understamd that nvidia entry. It's not even useful for nvidia users (driver is loaded by xorg,conf), so even as a mvidia user i always turn that off.

3) The instructions no longer apply for feisty. Try my suggestion here (http://ubuntuforums.org/showpost.php?p=2843862&postcount=3). You may want to read the full thread (http://ubuntuforums.org/showpost.php?p=2843862) for others comments and alternatives.

your link merely talks about a getty, are you saying that I can just move any process to a different folder and it won't run? ALso, whne you tried to link to the full thread, it's not the full thread, it's the same little 1 post thread. I am interested in this because I run feisty on an ancient laptop, and I am looking to get rid of ton's of stuff I don't need running which is slowing it down almost intolerable. Please help.

Rui Pais

August 31st, 2007, 08:57 AM

your link merely talks about a getty, are you saying that I can just move any process to a different folder and it won't run?
hi,
my suggestion was in sequence of Yes question, to prevent ttys from start. But yes, sysv-rc-conf it's just an frontend to do exactly that.
All boot "process" are just links under /etc/rc<N>.d/ to files under /etc/init.d/files. With a rename of SXX or KYY, with S fro start and K for kill amd XX, YY a number to indicate process order.
A smart trick.

ALso, whne you tried to link to the full thread, it's not the full thread, it's the same little 1 post thread. I am interested in this because I run feisty on an ancient laptop, and I am looking to get rid of ton's of stuff I don't need running which is slowing it down almost intolerable. Please help.

thanks for point me that. I just copied links from browser... something must failled. I will correct my post.

tech9

September 5th, 2007, 03:48 PM

yes, thanks for the post... it does help to understand what all these processes are doing:guitar:

nowshining

September 9th, 2007, 08:03 PM

thank you this has not only sped up the operating systems bootup process - far as I went it also sped up the loading of the Desktop and applications.. :) ty..

oh and it fixed many issues I was having with my connectiond to the net now pages load quicker.. :)

Salpiche

October 26th, 2007, 07:40 AM

is there an update or guide with the other services found on Feisty and Gusty that are not mention here?

TuxCrafter

October 26th, 2007, 02:26 PM

Hello all, i am searching for a updated list for gusty. I would like a list with only absolute necessary services to run ubuntu gusty safe with only a xserver. So without internet gdm alsa etcetera. It would safe me a lot of time else I have to go through all those services myself.

Cheers

nowshining

October 26th, 2007, 08:36 PM

TuxCrafter GDM is what u see when u log in - :) u know that Sign on screen.

TuxCrafter

October 27th, 2007, 03:30 AM

TuxCrafter GDM is what u see when u log in - :) u know that Sign on screen.

Sorry, I am not getting your point:-D. I startupuntil tty terminal. Then I login and execute startx (autostart)
I don't use GDM.

I need to be sure witch services are critical to create a stable system.

cherry316316

October 28th, 2007, 12:27 PM

when I got Hal problem, I tried doing by ur method, initially
all the settings were by default on 2,3,4 N 5.
so i didnt change anything , but it didnt work,
so I change those setting to "S"
and it worked smoothly ,

By chaning to S, I guess they start before Hal starts,
hence no problem I guess

Ux64

November 19th, 2007, 04:23 PM

Great list about services.

But after a lot of tuning, I got a strange problem.

Now when ever I press alt+ctrl+del or open "quit" menu, it takes about one minute to open up. I guess it's related to services that I have dropped out.

Any clues anyone? - Thank you!

213374U

November 20th, 2007, 12:14 PM

subscribed for use at home

NineseveN

November 21st, 2007, 09:37 PM

So, what is considered a decent or fast boot time anyway? My box runs 1 minute and 15 seconds from post to desktop, including selecting Ubuntu in GRUB and putting my username/password in. Is that good, bad, somewhere in between?

Ux64

November 26th, 2007, 10:39 AM

My Ubuntu boot time is total of 16 seconds.

TuxCrafter

November 26th, 2007, 10:46 AM

My Ubuntu boot time is total of 16 seconds.

Nice, mine boots ups in 30 seconds with a VIA C7 1.2GHz with complete desktop with panels (xfce), inclusive cups and alsa and network.

computer is a EN12000E

jwmislan

December 11th, 2007, 06:19 PM

Shutting off unneeded processes not only lessens boot time, it speeds up a running system.
Since unneeded processes were removed, there are more processor cycles available for
all the rest of the processes that are needed, thereby improving overall efficiency.

JWM

omega_user

December 15th, 2007, 09:24 PM

thank u very much. I'm still having a problem though that seems to be an elusive one for some people. The gnome-settings-manager causes the after login to the point where u can click on stuff last 10 seconds or more. very irritating, anyone know what's up?

Pelonchas

December 16th, 2007, 05:11 PM

I have some others , but i have bootclean too.
Do NOT enable bootclean, it mess up gdm startup, well bootclean it's not mean to run on boot.

BLTicklemonster

January 26th, 2008, 01:27 AM

Strangest thing just occured....

**Note**
For all of those that having HAL failure problem, try this:
1. change acpi-support from S to 2,3,4,5
2. change acpid from S to 2,3,4,5
3. change dbus from S to 2,3,4,5
4. Reboot. Go to the console and do ps -aef|grep hald. If hald service is up, then your dbus subsystem is running fine now. Try it.

I was having "Internal Error: Failed to initiate HAL" problems for the longest, but my settings were already 2,3,4,5 for the above mentioned entries.

So- being the experimenter that I am, I set all mine to S and rebooted, and voila, no more HAL problems.

Running Gutsy.

Hope this helps someone out there who is at wit's end like I was.

:)

chris4585

January 27th, 2008, 08:27 PM

then comment out tty4,tty5, and tty6. Just leave tty1, tty2, and tty3. Three vts should be enough for a laptop or desktop user. Save the file.

i didnt have the inittab file in /etc/ do i need to create it or install something?

dannyboy79

January 28th, 2008, 10:35 AM

they are located in /etc/event.d/. you can just remove the tty's that you don't want to run.

chris4585

January 28th, 2008, 02:48 PM

ah that makes sense, another thing i removed usplash from the sysv-rc-conf and when i booted up usploash appeared, what did i do wrong?

dannyboy79

January 28th, 2008, 02:51 PM

i think usplash is controlled via grub boot lines. check out /boot/grub.menu.lst file and remove the word "splash" from the end of your boot lines. that's just what I think and may not be totally correct. you can always put that splash on the end of your boot line back if that's not it.

chris4585

January 28th, 2008, 03:51 PM

this makes sense thanks, if i recall this was mentioned in the guide, i should of reread it, thanks

raoulteeuwen

February 2nd, 2008, 05:40 PM

TuxCrafter

February 2nd, 2008, 05:47 PM

I have an Acer Travelmate 4000 where i installed Ubuntu 7.10 Gutsy Gibbon on in a dual boot config with XP. I have tried several other Linux-flavors before (Xandros, Fedora, Open Suse etc), and Ubuntu is the slowest to boot! I did not tweak anything and i guess i have one of the elderly gibbons out there: takes more than 3 and a half minutes! I love open source, but this means i mostly boot into XP as it boots quicker... I guess i'm going back to some other Linux flavor and wipe Ubuntu from my HDD...

Ubuntu has the philosophy to work just get it working, this includes having a lot of system services running and starting during boot up. I agree this can take very long. Fortunately you can remove all those processes if you do not need them. You can also try fluxubuntu that will not use all those startup services by default and will be much faster.

thechilipepper0

February 21st, 2008, 05:03 AM

I have an Acer Travelmate 4000 where i installed Ubuntu 7.10 Gutsy Gibbon on in a dual boot config with XP. I have tried several other Linux-flavors before (Xandros, Fedora, Open Suse etc), and Ubuntu is the slowest to boot! I did not tweak anything and i guess i have one of the elderly gibbons out there: takes more than 3 and a half minutes! I love open source, but this means i mostly boot into XP as it boots quicker... I guess i'm going back to some other Linux flavor and wipe Ubuntu from my HDD...

i duno if i got you in time, but don't give up. my system used to take 3 1/2 minutes to boot up also. and then i ran across this http://ubuntuforums.org/showthread.php?t=580903&highlight=long+startup. it was the easiest two line edit ever, and i shaved 2 minutes off my boot. that is amazing to me.

anyway good luck.

raoulteeuwen

February 25th, 2008, 09:23 AM

Thanks thechilipepper0! That did shave off about 1 minute or more (just did it, timed it while watching tv (as i got used to taken it up a lot of time)). Did someone close to the developers tell them this? This should be a default option/behaviour since it makes such a difference?

Since i now see what Ubuntu is doing, i find every boot the DOS-partition is checked, taking about 45 seconds. Is this really necessary? I read somewhere it is, but since i'm dualbooting, i guess the FAT-partition gets checked often enough? Anybody?

I will give Ubuntu another try!

raoulteeuwen

February 25th, 2008, 09:55 AM

Found http://ubuntuforums.org/showthread.php?t=470726 ... Now my boot time from grub selection-screen till logon screen is about 45 seconds :-)!

puccaso

March 2nd, 2008, 01:56 AM

is there anyway of getting X/gdm/xdm to start up straight after boot

something like rhgb on fedora...

or anything... even a x-terminal!!!

Jason2gs

March 3rd, 2008, 06:53 PM

Thank you :)

Where I failed was not benchmarking the original startup time. The current is three minutes and six seconds. How does mine rank with some your guys' boot times?

baracuda68

March 12th, 2008, 09:31 AM

III. Alter the /etc/inittab file
Code:
vi /etc/inittab
then comment out tty4,tty5, and tty6. Just leave tty1, tty2, and tty3. Three vts should be enough for a laptop or desktop user. Save the file.

On my Gutsy setup, I dont have "inittab"
Where else can I remove a couple of tty's?
getty uses 6 of them right now, xorg uses 1...

:twisted:

Rui Pais

March 12th, 2008, 03:52 PM

On my Gutsy setup, I dont have "inittab"
Where else can I remove a couple of tty's?
getty uses 6 of them right now, xorg uses 1...

:twisted:

Gutsy don't use that method.
i had previously suggest:
sudo mv /etc/event.d/tty6 /etc/event.d/_ty6
sudo mv /etc/event.d/tty5 /etc/event.d/_ty5
...
but roderick on post #350 (http://ubuntuforums.org/showpost.php?p=4637895&postcount=350) suggested a better way.

Please see bellow.

baracuda68

March 12th, 2008, 09:05 PM

Gutsy don't use that method. Do:
sudo mv /etc/event.d/tty6 /etc/event.d/_ty6
sudo mv /etc/event.d/tty5 /etc/event.d/_ty5
...for any tty you want to remove.
Thanks Rui Pais.
I tried your code, and it did change the filenames of the tty's that I wanted removed, but after a reboot, they still show up running, in " top " See screenshot. Any other ideas?
62425

Rui Pais

March 13th, 2008, 03:42 AM

Thanks Rui Pais.
I tried your code, and it did change the filenames of the tty's that I wanted removed, but after a reboot, they still show up running, in " top " See screenshot. Any other ideas?
62425

Ooops, sorry. A rename it's not enough. They must be removed from event.d... try:
sudo mv /etc/event.d/*ty6 /etc/
sudo mv /etc/event.d/*ty5 /etc/
...

That should do the trick.

baracuda68

March 13th, 2008, 04:41 AM

Ooops, sorry. A rename it's not enough. They must be removed from event.d... try:
sudo mv /etc/event.d/*ty6 /etc/
sudo mv /etc/event.d/*ty5 /etc/
...That should do the trick.
OK.
What am I doing wrong?
I copy/paste the code into the console,for tty6,5,and 4,and check the /etc/event.d directory( in Konqueror) and they are gone!
But after a ctrl+alt+backspace, I check with "top"and, guess what? Still loading!! (see screenshot 2)

Now what?... 62451

baracuda68

March 13th, 2008, 04:49 AM

Nevermind my last post...
I did a clean reboot and it is just fine! They are gone!

Thanks!

Rui Pais

March 13th, 2008, 04:56 AM

OK.
What am I doing wrong?
I copy/paste the code into the console,for tty6,5,and 4,and check the /etc/event.d directory( in Konqueror) and they are gone!
But after a ctrl+alt+backspace, I check with "top"and, guess what? Still loading!! (see screenshot 2)

Now what?... 62451

uhmm thats weird...
why a forced restart of the X server (graphical) would load the extra consoles? and even without event.d/tty*?...

sorry i don't know why. Maybe restart X have that behaviour by default...

Thats an unusual thing anyway, restarting X server.
With a reboot the new consoles will be gone. It's just an issue that happen if you by some reason would need to force a restarts of X (not that those 3 extra consoles had any special load on a system anyway...)

edit: i read your second post only after i post this. Its ok then :)

roderick

April 2nd, 2008, 02:08 PM

Gutsy don't use that method. Do:
sudo mv /etc/event.d/tty6 /etc/event.d/_ty6
sudo mv /etc/event.d/tty5 /etc/event.d/_ty5
...
for any tty you want to remove.

Ooops, sorry. A rename it's not enough. They must be removed from event.d... try:

sudo mv /etc/event.d/*ty6 /etc/
sudo mv /etc/event.d/*ty5 /etc/

The init method used by Ubuntu is called Upstart. Please read this article for more information on Upstart: http://www.linux.com/feature/125977

Renaming or moving files to random locations on the system is NOT a good practice and can cause problems (Upstart should have a proper recommended practice for enabling and disabling events and services).

Note the following from the bottom of that page:

....Ubuntu does not include an inittab file and, by default, the Upstart init daemon (using the rc-default task) boots the system to multiuser mode (runlevel 2, the default runlevel). If you want the system to boot to a different runlevel, create an inittab file.

So, if you do not have an inittab file, the Upstart system will perform some predetermined defaults.

Now, as for disabling the individual ttys - deleting will work, but may not be the best course of action.

Instead, I would suggest editing the tty4/5/6 files and removing the line

start on runlevel 2

If you do this, then the ttys can still be started on runlevel 3. You can change this runlevel default (read the article quoted above) with an entry in /etc/inittab.

Also, if the Upstart package gets re-installed, new instances of the tty files could overwrite the ones you deleted (which is a possibility), so not deleting has a benefit as well..

Anyway, just my two cents.

Rui Pais

April 3rd, 2008, 03:43 AM

@roderick
Hi. Although i didn't had any problems (nor even deleted ttys come back after some update, a possibility that i was aware) yours suggestion it's definitely a much better approach.

Thanks for the correction.
Rui

jakupl

April 5th, 2008, 06:25 PM

wauw thanks. :popcorn:

fonsi2099

May 3rd, 2008, 12:32 PM

I'm using Hardy, does this way work for hardy too!

there are many contributions on this thread, can someone who understand the things do an explanation or a howto for Hardy?

Many thanks:guitar:
I work on AMD 64bit

krevuru

May 6th, 2008, 10:04 PM

Yes Please.
If the author can actually re-do his document for Hardy, it will very greatly appreciated.
I have been watching the UBUNTU 8.04 countdown since it was showing "112 days to go". And after installing UBUNTU 8.04 on all my machines and referring this to everyone in my family, I am finding it sort of slow in performance.
On doing
ps aux | more
I could not really understand much as to what was needed and what was not?
Luckily I came across your tutorial but then I was not sure if it would apply to Hardy as well.
A sincere note of thanks for the earlier post and another set in advance for its 8.04-version.

MedellinManDem

May 18th, 2008, 08:11 PM

Andre-D

May 22nd, 2008, 06:03 AM

jakupl

May 24th, 2008, 08:00 AM

Yes, please make a list for 8.04 as well, and collect all good tips in one place.

It's a pity, that a much smaller/leaner OS like Ubuntu/linux takes much longer time to boot up than a pile of bloatware (Windows)

It doesn't. If it does, then something is wrong. It should never take over a minute. mine is 27 sec.

King Louie

May 24th, 2008, 08:09 PM

I would also appreciate a summary of the speed up boot process suggestions for Hardy.

ForksHolder

July 8th, 2008, 09:04 PM

Cool! :D

Thank you very much for the hard work.

Xgamer

July 31st, 2008, 11:27 AM

Can I disable nvidia-kernel in boot process when I have Intel X3100 graphics? thx

unutbu

July 31st, 2008, 11:46 AM

I looked at /etc/init.d/nvidia-kernel, and since it all has to do with nvidia cards, my (unexpert) guess is yes, you can safely remove it from your boot process.

Moreover, if it for some reason you find booting without nvidia-kernel is a problem, you can re-insert it into the boot process by relinking

/etc/init.d/nvidia-kernel to /etc/rc2.d/S20nividia-kernel:

sudo ln -sf /etc/init.d/nvidia-kernel /etc/rc2.d/S20nividia-kernel

funnylife_ma

August 20th, 2008, 10:13 PM

Hi there,

Thank you for this great HowTo

Hicham

nbhat

August 31st, 2008, 04:31 AM

Thanks for the Howto!

I am on Hardy managed stop the following

atd, bluetooth,cupsys, dns-clean, pppd-dns

taurusx5

September 20th, 2008, 01:55 AM

I got 2 crucial questions:

1) According to the guide on disabling services, how do I disable a service on ubuntu 8.04? What runlevel(s) do I need to uncheck?

2) Will the guide work on ubuntu 8.04?

.

jakupl

September 20th, 2008, 10:40 AM

2) Will the guide work on ubuntu 8.04?

.

Yes it will :)

taurusx5

September 20th, 2008, 03:38 PM

SkonesMickLoud

September 20th, 2008, 07:01 PM

You know, it's remarkable how I keep asking the same question over and over again without an answer. It's either people on here are afraid to answer this question or they just simply don't know the answer. I'll ask it one more time, and hopefully, an intelligent and brave person will answer it:

1) According to the guide on disabling services, how do I disable a service on ubuntu 8.04? What runlevel(s) do I need to uncheck?

.

It's right there in the OP:

Throw a littel bit of runlevel knowledge here before we start messing them up.... All the boot processes are executed in sequence as following:
runlevel S: the first runlevel in boot process. /etc/init.d/rcS script will be invoked to start and all the processes underneath /etc/rcS.d will be executed.
runlevel 1: the single user mode. All processes underneath /etc/rc1.d will be executed.
runlevel 2,3,4,5: in debain system, the multi-user env, may not may not include GUI. The same, processes under each of the corresponding dirs will be run. **Note** this is different than RedHat, SuSE, and other RPM based systems.
runlevel 0: computer shutdown.
runlevel 6: computer reboot.

Do you have "sysv-rc-conf" installed?

taurusx5

September 26th, 2008, 09:31 AM

It's right there in the OP:

Do you have "sysv-rc-conf" installed?

Hi, SkonesMickLoud. Thanks for the response. And yes, I do have sysv-rc-conf installed. As I've mentioned in my posts, I have 8.04. Do you know of an updated guide on turning off services in 8.04? Thanks.

.

SkonesMickLoud

September 26th, 2008, 10:55 AM

Hi, SkonesMickLoud. Thanks for the response. And yes, I do have sysv-rc-conf installed. As I've mentioned in my posts, I have 8.04. Do you know of an updated guide on turning off services in 8.04? Thanks.

.

I've used the same guide in 8.04, and only ran into a few services that aren't mentioned in the guide. If you come across something like this, and don't know what the service does, you should leave it at the default setting. Most services can be googled, and you can make a determination from there.

uberdonkey5

October 3rd, 2008, 10:19 AM

just like to thank all those who posted here - boot speed is very important to me and I have shaved over 25% off my boot time (30 secs to 22 secs), whilst still allowing wifi etc (got rid of boot screen, which means can actually see whats going on, so its a bonus). Not bad for a newbie.

Here are before and after

P.S. any way to get rid of the scan disk that occurs occasionally? Is it useful? Should I increase the number of times it requires before checking or get rid of it completely?

unutbu

October 3rd, 2008, 11:25 AM

If you are interested in booting faster, you may also be interested in jdong's guide on readahead profiling: http://ubuntuforums.org/showthread.php?t=254263.

It doesn't work for everyone, but some report shaving 10 seconds off their boot time.

Regarding the disk scan that occurs occasionally:
I think Ubuntu sets up the partitions to be checked (fsck'd) every 22 boots by default.
How often you wish to fsck is a judgement call -- I do not know of any evidence to guide us in choosing what is best. It is probably not good to shut it off entirely, however.

It is possible to change the frequency of the checks this way:

sudo tune2fs -i 1m /dev/sda3

This sets the interval between checks to 1 month instead of every 22 boots. You may need to change /dev/sda3 to the correct device name for your partition(s).

sudo tune2fs -c 50 /dev/sda3

This sets the fsck to occur every 50 boots.

Type

man tune2fs

for more information.

uberdonkey5

October 3rd, 2008, 12:06 PM

...
It doesn't work for everyone, but some report shaving 10 seconds off their boot time.

Regarding the disk scan that occurs occasionally:
I think Ubuntu sets up the partitions to be checked (fsck'd) every 22 boots by default.
...

I'm not sure about the device name for my partition?! I know its listed at disk scan, but is there anyway to check? Infact, I added the gnome partition editor, and this seems odd, because I have dual boot, but it is only listing one partition (unallocated) at /dev/sda

i get this if I use sda3:

tune2fs 1.40.8 (13-Mar-2008)
tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda3
Couldn't find valid filesystem superblock.

so I assume this is wrong, and this

tune2fs 1.40.8 (13-Mar-2008)
tune2fs: Bad magic number in super-block while trying to open /dev/sda
Couldn't find valid filesystem superblock.

when I use sda (never had a bad magic number before :)

thanks
ud5

uberdonkey5

October 3rd, 2008, 12:21 PM

thanks unutbu! no need to answer, coincidently I rebooted (doing something else) and it did a scan, so I could see the disk was sda6

I've changed this. Its very useful, because I have a laptop, and use it for short periods frequently. Thus I was always pressing 'esc' on the scan disk anyway! Well, once a month seems more sensible for me, and with the splash screen gone I am forced to wait when it eventually does want to scan, which is probably better!

starscalling

October 28th, 2008, 09:03 PM

very interesting... going to have to look at this closer ;)

HellMind

November 8th, 2008, 12:24 PM

cl0ckwork

November 8th, 2008, 02:50 PM

This thread was a total waste of my time.
I'm only looking for a simple guide just saying WTF every services does
A short description but complete so I can decide If I want to load it or not

It's incredible that isn't documented anywhere

wow. way to be a jerk. :mad:
just google the proscesses that you are unsure about.
obviously, a list of services is not going to be in a thread titled HowTo: Speed up ubuntu

there are lists out there, i know ive found them.

sorry for the rant and no links but its a thing you use once and dont need anymore.
and honestly, this guide did a lot more than the proscess list did

there is some info out there about changing how things load using the rc*.d files in /etc/ but that may get a little complicated for you :D

SkonesMickLoud

November 8th, 2008, 06:08 PM

bluemm

November 27th, 2008, 12:24 AM

thanks for the tips!

steveydoteu

November 27th, 2008, 06:47 AM

133794m3r

November 29th, 2008, 08:31 PM

jakupl

November 29th, 2008, 08:34 PM

Ok i followed your guide perfectly and it has disabled my auto login feature i had.. now it takes me 43 seconds to boot up instead of 38 so... thus it's actually increased the boot time by 5 seconds! and also i couldn't figure out how to remove that grub splash screen if i could remove that plus renable my autologin feature i could probably save a few seconds..

To remove the splash screen, do:

sudo cp /boot/grub/menu.lst /boot/grub/menu.lst.bak
gksudo gedit /boot/grub/menu.lst

You will see a line like this near the bottom:

title Ubuntu 8.10, kernel 2.6.27-7-generic
uuid a459dc22-9c50-4dad-8345-f46455524732
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=a459dc22-9c50-4dad-8345-f46455524732 ro quiet splash

I usually remove "ro quiet splash", but just removing "splash" will do.

klhtaar

March 16th, 2009, 10:24 AM

First of all thanks for a very nice guide!
But I've found some questions I'd like to be answered. Could you please help me?
I haven't found any information if I can disable these services and what are they meant for:
console-$
gdm
hal
halt
keyboard-$
killprocs
loopback
nullmailer
policykit
powernowd
powernowd$
procps
pulseaudio
rc.local
samba
screencl$
stopread$
udev-fini$
ufw
umountroot
winbind
wpa-ifupd$
x11-common
xserver-x$

Also I wonder if I can disable hddtemp will it harm my laptop?

Can i disable these two if I'm using an advice with PROFILE boot from one of the howto guides?
readahead
readahead$

And last but not least despite the guide I have off this one stopboot$
Should I enable it?

So, I hope this thread isn't dead and I'll get desired help here. Thanks in advance!

unutbu

March 16th, 2009, 01:58 PM

Hi klhtaar, welcome to ubuntuforums.
I don't know the answer to all your questions, but here are a few:

Note: when running sysv-rc-conf and see a $ at the end of a service name, the full service name has been truncated. You can find the full service name by looking in /etc/init.d.

gdm -- If you use Ubuntu (as opposed to Kubuntu or Xubuntu), your login screen is gdm.
If you don't run this service then you are sent to a terminal (console) login prompt.
You probably don't want to disable this service.

hal -- When you plug in an external USB device (camera, mass storage, etc.), hal is the service which automounts the device.
You probably don't want to disable this service.

killprocs -- this service is only run when you enter single user mode (runlevel 1)
You probably shouldn't change this.

loopback -- a quote from /etc/init.d/loopback: "brings up the loopback (127.0.0.1) network device so that DHCP and other such things will work"
You probably don't want to disable this service.

policykit -- When you click System>Admin to alter system settings, the app you are running may use policykit to determine if it should let you, as a normal user, to change those settings. You do not want to disable this service.

powernowd -- this service allows you to control cpu speed. If you have no need to control the CPU scaling governor, you could disable this service.

procps -- allows you to configure certain kernel parameters at boottime. I'm not sure what would happen if you disabled this. Maybe nothing, but I'm not sure.

pulseaudio -- The current version of Ubuntu, Intrepid, uses pulseaudio as its sound server. It can do neat things like control the volume of multiple apps individually, while they all make sounds. If you disable it, I think individual apps should still be able to control the speakers, just not all at once.

rc.local -- If you like to add scripts to tell your machine to do certain things at boot time, this is a convenient service to have enabled. If you don't have any such need, you could disable this.
Even if you disable this, you would still be able to run scripts at boot time using the newer upstart system.

samba -- samba allows you to share files with Windows machines. You can disable this if you don't have this need.

screen-cleanup -- removes stale screen named pipes on bootup. I'm not entirely sure what happens if you disable this. Among other things, it removes a file called /var/run/screen. I imagine if you don't run this service, the /var/run/screen file may grow larger and larger... not good.

readahead and readahead-desktop and stop-readahead -- don't disable these if you plan on booting with the profile boot option. The profile boot option is used (usually only once) to help configure the machine to boot faster. See http://ubuntuforums.org/showthread.php?t=254263 for how this is done.

udev-finish -- This is part of the udev system. udev creates mount points for devices. When you plug in a USB flash drive for example, udev is involved. I don't think it is a good idea to disable this.

ufw -- starts the firewall. The default firewall does not block anything. I'm not sure, however, what would happen if you disable this service.

umountroot -- this script mounts the root filesystem read-only at shutdown or upon reboot. Not doing so can lead to filesystem corruption. Don't disable this.

x11-common -- sets up certain directories used by X11. If you use X, as most users do, as the underlying server for a graphical desktop environment, do not disable this. Without X, you would be running Linux from a text console.

xserver-xorg-input-wacom -- this is only needed if you have a wacom device (a wacom graphics tablet, for example). You can disable this one if you don't have a wacom device.

stop-bootlogd and stop-bootlogd-single -- by default neither of these services is run at any runlevel. Neither of these are useful unless you enable the bootlogd service.
bootlogd is useful if you want a record of the (error) messages your machine prints to the console during boot. See http://wiki.debian.org/bootlogd and http://www.digipedia.pl/man/bootlogd.8.html. You don't need this unless you are trying to debug some problem on your machine which happens at boot time.

Regarding "vi /etc/inittab": Ubuntu is migrating to a new startup system called "upstart".
Because of this, Ubuntu no longer ships with an /etc/inittab file. Nowadays, to disable tty4, tty5, tty6, you could change "start" to "stop" in /etc/event.d/tty4, /etc/event.d/tty5, and /etc/event.d/tty6.

klhtaar

March 16th, 2009, 02:50 PM

unutbu, thanks lad!
Your information was very useful for me and now I also know where to read a description of service. Thanks to you!
Now I've completed this guide and going for a restart. Hope It'll be OK.

kurrupted

March 24th, 2009, 11:37 AM

Hi guys,

My friend showed me this program a while back and i'd forgotten all about it.

I thought i'd give it a bash and see how things went.

i've easily shaved 10-15 seconds off my boot time so i'm really pleased and i'm sure i can get a few more if i actually investigate what some of the other programmes are...

Thanks a lot for all the help.

Jay.

VladNistor

March 28th, 2009, 02:27 AM

Great How-to!

I took 17 seconds off my Jaunty Beta boot. As a note, disabling readahead increases my boot time by about 4 seconds for some reason.

Grub-2-loginscreen is now 23.44 secs. I'll get ext4 on my system partition soon and that will probably cut it even more.

Thanks!

--Vlad

AtheistBlog.org (http://www.atheistblog.org)

Yashiro

March 30th, 2009, 09:04 AM

Just something I felt the need to post since a Hardy system that's been rock solid since release recently developed a networking problem.
I had used these tweaks a long time ago and run a --profile boot every few months.
All had been fine until a few days ago. After running a profile from the kernel line (which worked fine previously)
caused the machine to randomly fail to get a DHCP address on boot.

I'd recently used the readahead tweak mentioned here.
http://ubuntuforums.org/showthread.php?t=254263

Re-adding the --background switch to S01readahead fixed it completely.
This issue is very timing specific and may not even appear on some machines and networks.

If you start init.d/networking a few milliseconds later, as S60, it works fine.
Or you could run /etc/init.d/networking restart at a much later point, and again, it was fine.

So, if you have connectivity issues using anything but 'roaming mode' in Network Manager this is a possible reason why it fails. And something to bear in mind when you tweak your machine.

unutbu

March 30th, 2009, 10:03 AM

Thanks for the info, Yashiro.
Where exactly is the --background switch added?

Yashiro

March 30th, 2009, 10:49 AM

Read the first post of this thread (http://ubuntuforums.org/showthread.php?t=254263). The switch exists bt default unless you alter it. So unless you've already performed that tweak before there's nothing to worry about.

unutbu

March 30th, 2009, 01:19 PM

Read the first post of this thread.

Thanks Yashiro, I think you must be referring to this thread: http://ubuntuforums.org/showthread.php?t=254263

Yashiro

March 30th, 2009, 07:19 PM

Yeah you are right, my error. I've linked to it in my previous posts to clarify.
I was reading both threads simultaneously I guess. :)

ashmew2

April 15th, 2009, 04:05 PM

Nice Thread! Keep up the good work. :D

chika.tambun

May 2nd, 2009, 01:17 PM

according to the super parent of this thread

$ sudo update-rc.d -f anacron apmd apparmor atd bluetooth cups dns-clean hotkey-setup kdm laptop-mode NetworkManager pppd-dns readahead readahead-desktop rmnologin rysnc samba ufw uml-utilities usplash remove

coldReactive

May 14th, 2009, 02:17 PM

Most of the stuff listed here I do not have at all.

In fact, I don't even have a /etc/inittab file.

My boot time upon fresh install was about 30 seconds.

But now that I've installed a few things, it's at 35 seconds.

59. usplash - Well, if you really want to see the nice boot up screen, leave it as it is. I just turned it off anyway. If you want to turn it off, you also need to edit /boot/grub/menu. lst file to comment out the splashimage line and get rid of the splash kernel boot option. The default is 2,3,4,5

no splashimage entry in my menu.lst in 9.04

TFrog

June 17th, 2009, 09:39 AM

I have used this and one other page to speed up boot time in Kubuntu since Edgy. Though still applicable even today with Jaunty to a certain extent, it would be nice to see this updated to the newer versions of Ubuntu/Kubuntu. With this and one other page, I've trimmed down my boot speed to just 23 seconds in Jaunty Jackalope. If I weren't loading Virtualbox up at boot, I'm sure I'd see sub 20 seconds in boot. Can't wait to see if Ubuntu is able to go for what they want in Karmic Koala. That might even bring my boot time down on this old laptop to about 15 seconds though they are shooting for 10 seconds.

capoli

July 23rd, 2009, 03:09 AM

Hi,
This profile switch has just screwed up my booting. Instead of the slow, but reilable 33sec till login screen and 1 minute full boot time, the HDD waits about 1 minute at the very beginning. The light is on, but doing nothing. Now I have 2 minutes boot up :((
Can I undo somehow that profile stuff??

Just something I felt the need to post since a Hardy system that's been rock solid since release recently developed a networking problem.
I had used these tweaks a long time ago and run a --profile boot every few months.
All had been fine until a few days ago. After running a profile from the kernel line (which worked fine previously)
caused the machine to randomly fail to get a DHCP address on boot.

I'd recently used the readahead tweak mentioned here.
http://ubuntuforums.org/showthread.php?t=254263

Re-adding the --background switch to S01readahead fixed it completely.
This issue is very timing specific and may not even appear on some machines and networks.

If you start init.d/networking a few milliseconds later, as S60, it works fine.
Or you could run /etc/init.d/networking restart at a much later point, and again, it was fine.

So, if you have connectivity issues using anything but 'roaming mode' in Network Manager this is a possible reason why it fails. And something to bear in mind when you tweak your machine.

jocko

July 25th, 2009, 08:11 AM

capoli

August 2nd, 2009, 11:40 AM

I did only once first. I can see in dmesg about 40 sec delay:
[ 6.121601] kjournald2 starting. Commit interval 5 seconds
[ 6.121611] EXT4-fs: delayed allocation enabled
[ 6.121613] EXT4-fs: file extents enabled
[ 6.121758] EXT4-fs: mballoc enabled
[ 6.121763] EXT4-fs: mounted filesystem with ordered data mode.
[ 47.948781] udev: starting version 141
[ 48.012917] irda_init()
[ 48.012930] NET: Registered protocol family 23
[ 48.016682] nsc-ircc 00:0c: activated

You should only boot once with the profile switch. It collects information of which files are read during that boot and makes sure they are loaded into memory before they are needed. That one boot will be very slow, but all boots after that should be a little bit quicker than before.

known

August 22nd, 2009, 12:26 PM

Excellent thread.
Is it possible to include the description of services as tool tips in sysv-rc-conf?

cimbaeth

August 24th, 2009, 08:43 AM

thanks

known

August 24th, 2009, 11:24 AM

Somebody please give me the list of minimal services required in sysv-rc-conf for a laptop meant only for browsing internet with swiftfox at home. I am running HARDY (kubuntu) with LXDE.

RAM is 256 MB
CPU is celeron
Internet speed is http://www.speedtest.net/result/311981447.png

TIA

munkeh

September 3rd, 2009, 06:43 AM

Thanks to i3dmaster, so many years ago.
Using Ubuntu 9.04 there's the GUI tools in >System>Administration>Services, to switch off some of the services originally mentioned. sysv-rc-conf had a few more though and was easy to use (as close to a GUI as you can get in a terminal?)
For all levels, on a stand alone desktop connected to t'internet, I switched off;

anancron
atd
apport
bluetooth
avahi dae$
brltty
dns-clean
laptop-mo$
nfs-common
nfs-kerne$
pcmciauti$
ppdns
rmnologin
rysnc
sysklogd.

Before I did anything I did check that I won't need any of the services. Everything seems fine computer booting and switching off with no problems. A little bit quicker, especially shutdown. (Did do what i3dmaster said about K to k in /etc/rc0.d & rc6.d)

Also deleted tty4, tty5 & tty6 from /etc/event.d. They have not appeared back yet although there have been rumours they may with certain updates?

So thanks again to everyone who's put advice in on this.

known

September 6th, 2009, 01:56 AM

anancron
atd
apport
bluetooth
avahi dae$
brltty
dns-clean
laptop-mo$
nfs-common
nfs-kerne$
pcmciauti$
ppdns
rmnologin
rysnc
sysklogd.

Thank you munkeh.
That was quite useful.

varsamakos

October 21st, 2009, 02:15 PM

thank you munkeh.
That was quite useful.

+1 :)
Thanks !

-jay-

November 4th, 2009, 11:34 PM

nice guide very useful

do you happen to have a updated guide for 9.04 ?

Nephtali

November 5th, 2009, 08:42 AM

Glad to find this topic boys !

As there is for about 4 years of discussion I would like to know if the original post is still up to date or if some modifications have been added later ?

What's the deal with upstart today ? Can we still use the method as described 4 years ago ?

Thanks for your answer.

disorientedminds

November 5th, 2009, 02:55 PM

Good work on this guide. I tried this on my HP mini 100 with Ubuntu 9.10 and my boot time increased by 4 sec. :D

akhe

November 7th, 2009, 08:19 PM

Please, can you describe the way to speed up boot for 9.10 Karmic? because I am little bit afraid to do this because it is really old article for 6.10... or tell me differencies or show me thread where is this for 9.10

Thanks!

Labello

November 7th, 2009, 09:09 PM

i would recommend to install the boot-up-manager:

sudo apt-get install bum
sudo bum

and then i always disable _everything_ except:
hal,gdm,dbus,avahi-daemon(pulseaudio, filesharing over network),policykit,preload,cups(printing)

the first three mentioned are the most important!