You are not logged in.
Pages: 1
Offline
http://bbs.archlinux.org/viewtopic.php?id=69086
http://bbs.archlinux.org/viewtopic.php?id=69258
Compile your kernel with modules built in.
Offline
Check out this thread --> http://bbs.archlinux.org/viewtopic.php?id=69086&p=1
Netbook specific, but might give you ideas
Offline
Check out this thread --> http://bbs.archlinux.org/viewtopic.php?id=69086&p=1
Netbook specific, but might give you ideas
It is meant to work with notebooks too
Offline
In your case DHCP and HAL takes the most of time (and there is also the least activity of your system).
Solution: Background HAL daemon in rc.conf and background network daemon (put @ before hal and network).
Static IP address is also faster then DHCP, but if you are happy with DHCP then backgrounding network saves a lot of time.
Offline
In your case DHCP and HAL takes the most of time (and there is also the least activity of your system).
Solution: Background HAL daemon in rc.conf and background network daemon (put @ before hal and network).
Static IP address is also faster then DHCP, but if you are happy with DHCP then backgrounding network saves a lot of time.
Yep and probably a good idea to background all programs that are not depencies of other programs. I've background-ed ssh, hal, vsftpd, samba and some more.
Offline
What does it mean for the daemon to be "backgrounded"? I thnk I may have the wrong idea as I thought it to be for "less important" daemons, if you will. I have @ before a few of my daemons, here's mine from my rc.conf:
DAEMONS=(syslog-ng network portmap nfslock netfs @sensors @keytouch @openntpd sshd @lircd @crond alsa nfsd samba @timidity++ hal @vsftpd @noip mpd @cups gdm)
But I don't necessarily know if that makes sense or not? My boot is reasonably fast, never timed it but I only boot about once/month.
Offline
What does it mean for the daemon to be "backgrounded"? I thnk I may have the wrong idea as I thought it to be for "less important" daemons, if you will. I have @ before a few of my daemons, here's mine from my rc.conf:
DAEMONS=(syslog-ng network portmap nfslock netfs @sensors @keytouch @openntpd sshd @lircd @crond alsa nfsd samba @timidity++ hal @vsftpd @noip mpd @cups gdm)
But I don't necessarily know if that makes sense or not? My boot is reasonably fast, never timed it but I only boot about once/month.
Background those daemons, you don't need to be started before other daemon starts. E.g. syslog-ng should not be backgrounded since it can log mistakes when other daemon fails to start. That is also the reason why it is listed as first daemon. In fact you can background everything.
Btw I wonder how many daemons you have.
Offline
If you boot it in the background, it means that it starts the daemon and continues to boot other daemons. So you will be able to load several daemons at once.
Last edited by Frots (2009-04-16 16:08:48)
Offline
The best tip yet : Search the forums. There are many threads on the topic.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Read the wiki (its there for you)
option that might appeal;
http://wiki.archlinux.org/index.php/Twe … _boot_time (beware hacking files that don't get updated is risky)
http://wiki.archlinux.org/index.php/Fas … the_kernel (make sure you know fully use '/etc/mkinitcpio.conf' before you start removing modules willy nilly)
http://wiki.archlinux.org/index.php/ABS (compile everything with your cpu type in mind)
I personally try not to reboot my box, soo if its 5 - 20 seconds in Udev, who cares?
i just tweak/hack my box until im happy with the stability and speed then i leave it to it. Arch is teh best!
Last edited by gav616 (2009-04-16 18:41:04)
Offline
Pages: 1