You are not logged in.
PKGBUILD - If you like it vote it
After the incompatibilities of finit-arc system I decided to resume the quick-init project.
The goal of the projects is to make a faster linux boot without any problems in full security without replace the original arch initscripts, but only replace of /etc/inittab. Then the initscrips is not removed from your system with this PKGBUILD.
WARNING!
If you have installed quick-init < 1.3-1 you must remove it and reinstall initscripts!
HOW IT WORKS
The reimplementation of init-scripts consists in the modification of the inittab runlevels and the start of system and Xorg without udev.
The first system level contains the creation of static devices necessary to boot system until fscheck. Then Xorg is started and in runlevel 3 it starts udev, swapon, all services etc...
Quick-init is almost fast than finit-arc. At the moment quick-init should be full compatible with your system, but it stay in experimental state.
OPTIMIZE FURTHER YOUR BOOT
If you want optimize your boot you can remove some lines from qinit.sysinit and qinit.multi. For example: lvm support, raid support, the load of modules...
FAST START X MODE (Xorg, Gdm etc..)
If you want start your gui fast you don't use a daemons like gdm becouse it starts in final part of the boot. You can use inittab or rc.local.
- INITTAB: read http://wiki.archlinux.org/index.php/Start_X_at_boot
- RC.LOCAL: Edit /etc/rc.local and insert command for start your login-manager, for example: /usr/sbin/gdm --nodaemon
At the moment fast start of X works 100% with:
- ATI chipsets with radeon driver
- Intel chipsets with i915 driver
- some nvidia chipsets
To know if fast start X mode works with your chipset you can try to start your X session without udev after qinit boot. To remove udev start edit /etc/qinit.multi. If X starts without udev, the fastest start will work, otherwise no
Suggestions:: you could use xorg-server-antidesktop: a light version of X server without Hotplug support. Then you can remove /etc/rc.d/hal start from qinit.multi and further reduce your boot time
My latest bootchart of quick-init on eeepc
Last edited by adriano (2009-09-22 00:20:45)
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline
Too bad it doesn't speed my system that much, tried to take out the udev part, but indeed X didn't want to start.
What else did you do to optimize your boot?
Offline
I edited the first topic with Suggestions for start X fast.
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline
works great for me ! thanks !
Offline
So do I just install this and reboot, or is there some other stuff I have to do?
I ask because last time I tried these scripts I couldn't boot, and I don't want to go through that again.
Offline
Have you read the first topic?...read please..
"WARNING!
If you have installed quick-init < 1.3-1 you must remove it and reinstall initscripts!"
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline
I want to keep HAL for hotplugging... so this wont be for me.
Offline
wow, that was fast!
I haven't boot charted yet, but seriously THIS IS FAST.
Last edited by platnumX (2009-05-15 23:19:53)
Offline
This didn't speed up my boot at all, and worse, didn't save my old inittab file. Luckily, I had an old inittab.pacnew file from January hanging around in /etc.
Jay
Last edited by jt512 (2009-05-16 00:01:26)
Offline
I know that quick-init dont save the current inittab but save a default copy. This becouse if you have installed a previous version of quick-init it saves the inittab (really quick-init tab), then the user lost the default inittab from his system.
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline
That was fast, but my cursor hangs. How can I fix this?
Last edited by mini (2009-05-16 08:56:43)
Offline
Is it for any type of system or just for the eeepc?
Arch x86_64 on HP 6820s and on HP nx9420. Registered Linux User 350155, since 24-03-2004
"Everyone said that it could not be done, until someone came along who didn't know that."
Offline
Is it for any type of system or just for the eeepc?
any system.
Offline
Adriano, I really think you should save the user's inittab (and not just the default inittab) on quick-init install. The way it is now, anyone who installs quick-init *loses* all the changes that may have been done in inittab. The fix is really easy: just use 'cp /etc/inittab /etc/inittab.user.save' in the install script of the quick-init package [and adjust the messages accordingly].
Also, the thing with leaving sd* devices in /lib/udev/devices after the uninstallation of quick-init is:
1) no pacman package should leave any cruft in the system directories after uninstallation, because this leaves files in the system that are not tracked by pacman (this is just a packaging standard for me, not a problem per se)
2) the possible problems come when the user adds or removes harddrives from the computer - then kernel may decide on different naming of the devices. That introduces a problem that udev can't react on this, since the nodes that are left behind are static. This is of course expected when one still uses quick-init (maybe you could include a script that regenerates the nodes with your package), but after the removal of quick-init users still can get unwanted behavior (and this shouldn't happen).
Offline
I want to keep HAL for hotplugging... so this wont be for me.
What's wrong with HAL and quick-init?
Proud ex-maintainer of firefox-pgo
Offline
Nothing it's wrong
to bender02
read my previuos post about inittab
Last edited by adriano (2009-05-16 17:42:37)
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline
to bender02
read my previuos post about inittab
In the arch packages' install script you can use two different functions: post_install and post_upgrade. The original user's inittab would be saved in post_install (then it's clear that quick-init is not on the system), and nothing would be saved in post_upgrade - that way you really keep the user's inittab saved.
Offline
ok I'll do it
thanks you for suggestion
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline
Nothing it's wrong
to bender02
read my previuos post about inittab
It seems to work fine, but while shutting down I've got message that stopping hal failed...
Proud ex-maintainer of firefox-pgo
Offline
wouldn't boot on my system... hung on checking filesystems... complaining that I should run a manual check... doing that did nothing...
if I uninstall quick-init with pacman is there anything else I need to remove to remove it fully from my system?
Offline
seems to be a great addition for me. Installed on Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz with Nvidia GeForce 9500 GT
My first time install brings bootchart time (with bootloader set-up) down from 22 secs to 10 secs.
Further attempted "tweaking" does not seem to improve on this though- if I really need , or am able, to .......................
I am not quite clear on :
"- INITTAB: Uncomment your preferred level in the /etc/inittab. The principal levels for login managers was written by me as comments".
I have tried uncommenting lines .Is it possible for further explanation ?
adding a line to RC.LOCAL does not seem to improve boot time. I appreciate my bootchart times are only showing timing up to login...............
"It seems to work fine, but while shutting down I've got message that stopping hal failed..."
I get the same message on shut -down as above. Everything seems to be working fine ,so is it a problem ?
good work adriano
regards
Last edited by pjnsmb (2009-05-17 05:02:03)
pjnsmb
Man is still the most extraordinary computer of all.
Kennedy, John F.
Offline
Duologic wrote:I want to keep HAL for hotplugging... so this wont be for me.
What's wrong with HAL and quick-init?
Nothing was wrong, It's just that he suggested to use X without HAL so it would boot faster, but I'm just not into that.
Offline
new 1.8-2 version updated with bender02 suggestions
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline
One more observation: the xorg runlevels shouldn't be :2345: but :5: only. i.e.:
xorg:5:respawn:/usr/sbin/gdm -nodaemon
instead of
xorg:2345:respawn:/usr/sbin/gdm -nodaemon
Otherwise, the standard kernel command line runlevel selection won't work; one would append a '3' in grub and still end up in X.
Offline
no, Xorg must start in runlevel 3 to start in background X
Quick-init UPDATED to version 1.9-1
Last edited by adriano (2009-05-23 11:01:13)
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline