Arch Linux

KDE complains about audio devices, using quick-init it says they've been removed, although non-KDE applications can use my speakers.
With default initscripts everything works fine.

This is impossible becouse after upgrade you should lost anyway your original files.

I'll search another way to solve it.

The post-uninstall should say:

1. Restore inittab from inittab.pacsave (not inittab.original)
2. Restore rc.conf from rc.conf.pacsave

Upon installation, there should be some warning that rc.conf was changed. I think a better method would be to install inittab.new.qinit and rc.conf.new.qinit and let the user move them over, backing up their old files if they want. This would be more consistent with the Arch Way.

layout FIXED ;)

Could you set

# Setting console lang
/bin/loadkeys us

instead of "it" ? or something else ? With "it", my keyboard layout in console (tty) is a bit of a mess. With "us" it's OK.

In the latest version 1.11-8 I added 7 tty consoles, KDM should start from inittab now...I fixed loadkeys with $KEYMAP instead "it"

after the last update kdm doesnt start via qinittab and i have to put it in deamons list to make it work.
PS i have enable autologin via kdm.
How can i fix it?

you may want to put a note in the .install file that users may need to change the console language at the end of qinit.sysinit based on their keyboard layout.

Updated for new initscripts

Please review the dependency/makedepends, in current quick-init, I've tried.
It is safe to remove the following dependcy.
makedepends='gcc'
Because, there is no binary code require to make.

I guess, it is inspired from finit-arc

Sorry, after detail test, I found if my fstab put
/dev/disk/by-uuid/.... entry with noauto option, it can bootable.
After remote noauto, it can NOT bootable.

When I use UUID in /etc/fstab, the quick-init can not work, it forced me into root maintain mode.

Is it possible let me use UUID in /etc/fstab? all of the UUID partition is set options as 'noauto'.

@ adriano - I would still like to figure this out. So please get back to me either in here or in your forum thread. Thank you.

I have sda1 - sda6 in there if that is what you mean (I'm not sure if that is what you asked about)..... could it be from using UUID numbers in the fstab and the /boot/grub/menu.lst files?

check if your hard disk device nodes are in /lib/udev/devices

I keep getting an error when it attempts to mount my local file system. It stalls forever as 'BUSY'.

Updated
- Dependencies fixed

Updated
- Qinittab adjusted (X starts in runlevel 5)

for now not, but in future it will be :)

Is it replacing inittab necessery every update? Editing it every time is pain in the ass.... :)

Updated
- Network rules moved (qinit.multi)

Updated
- user's inittab file backup in post_install
- fixed rtc0

I opened official topic for bug reports
http://bbs.archlinux.org/viewtopic.php?pid=553231

BEFORE INSTALL 1.4 VERSION:
YOU MUST REMOVE PREVIOUS 1.2 VERSION FROM YOUR SYSTEM AND REINSTALL INITSCRIPTS

I added urandom and random devices in the list o qinit.sysinit
It is not necessary to remove sda devices in the post install, then they will stay in /lib/udev/devices. They not causes any problem there. I know that after quick-init remove I restore the default inittab file and not user's inittab. But I dont want remove the initscripts. It is dangerous!

DO NOT REMOVE THE ORIGINAL INITSCRIPTS!

Well, I've got an unbootable system that I'm going to have to use the live disk to recover. You should really consider making the package rely on init-scripts or something for those of us who already pacman -Rd init-scripts before installing quick-init. I totally didn't see any warnings telling me my system would be unbootable on last upgrade...

Also, could you also create the /dev/urandom node? It's good to have (although probably not 100% necessary, but you get warnings) for lvm and cryptsetup. Normally it's created by udev.
mknod -m 666 /dev/random c 1 8
mknod -m 666 /dev/urandom c 1 9

Adriano, since now you don't remove initscripts, it would be better not to use the default inittab.pacsave, but at the beginning of the post_install() in the .install file just copy the original (possibly modified by the user) inittab to inittab.save before you replace it by qinittab. Then you can just copy inittab.save to inittab on post_remove(). It would be also cleaner if you'd remove the created block devices in /lib/udev/devices in the post_remove().

Do not do pacman -Rd initscripts, just quick-init install alongside of it.
It is not bugfree, but it works realy fast!

Well, operation pacman -Rd initscripts
is not very safe for anyone, so one need to be very sure he know, what he is doing before actually do it :)

Be carefull!
There is a reports about broken system after removing initscripts, installing quick-init and reboot.
Some errors about qinit and qinit.multi missing and so on.

BEFORE INSTALL 1.4 VERSION:

YOU MUST REMOVE PREVIOUS 1.2 VERSION FROM YOUR SYSTEM

I don't want include them becouse quick-init don't replace initscripts, but only inittab.

Hi Adriano! You still reference rc.single and rc.shutdown from qinittab, so you might want to include the default ones to your package :)

Updated:
- Reduced verbose messages
- General revision of boot steps

Updated
- Makedepends added
- Loadkeys for console map added

thanks for your suggestion :)

Nice job adriano, thank your for provding this.
Just one note: packages "gcc" and "file" should be makedepends.

Updated
Maybe no problems with X now

excellent work! :-D

CHANGELOG
New full automatic post-installation script

SIMPLE INSTALLATION
1) Remove archlinux original initscripts with pacman -Rd option NOT -Rsn!!: sudo pacman -Rd initscripts
2) Install quick-init from AUR, manually or with yaourt.