Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#6776 - add custom commands to rc.sysinit and rc.shutdown

Attached to Project: Arch Linux
Opened by pajaro (pajaro) - Saturday, 31 March 2007, 21:38 GMT
Last edited by Aaron Griffin (phrakture) - Wednesday, 30 January 2008, 22:51 GMT
Task Type Feature Request
Category System
Status Closed
Assigned To Roman Kyrylych (Romashka)
Architecture All
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Something that i miss in archlinux is the possibility to execute commands in the sysinit and shutdown processes in states in which the hd is mounted readonly.

Now i have to edit the rc.sysinit and rc.shutdown files every time an upgrade appears.

It would be really good to be able to include files within the boot process setting files in rc.conf like you do with DAEMONS, but having others states:


these files could the same behaivour than daemons: a switch with "boot" and "shutdown" options, so that you don't need to create a a boot_pre_mount_rw trigger and a shotdown_post_mount_ro one, just a ro_state would be enough.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Wednesday, 30 January 2008, 22:51 GMT
Reason for closing:  Won't implement
Comment by Roman Kyrylych (Romashka) - Monday, 02 April 2007, 13:47 GMT
What's the purpose of checkfs daemon?
Comment by pajaro (pajaro) - Monday, 02 April 2007, 21:14 GMT
checkfs was just and example name.
Comment by Roman Kyrylych (Romashka) - Monday, 02 April 2007, 21:20 GMT
Doesn't matter. What this feature is useful for?
Comment by pajaro (pajaro) - Monday, 02 April 2007, 21:39 GMT
This feature is useful to add flexibility to boot and shutdown procedures.

In example, LVM, encrypted filesystems, raids, wouldn't need modification of the main files.

This would also keep rc.sysinit clean and simple.

Maybe this doesn't fit with the arch KISS philosophy, but i am not the one who has to evaluate it. As I see programming, having an structure similar to the one DAEMONS have applied to the whole boot and shutdown processes would be optimal.
Comment by Roman Kyrylych (Romashka) - Monday, 02 April 2007, 21:44 GMT
I'll take a look on this but cannot promise anything. :-P
Comment by pajaro (pajaro) - Monday, 02 April 2007, 21:50 GMT
Comment by Roman Kyrylych (Romashka) - Wednesday, 30 January 2008, 18:40 GMT
ugh, I've totally forgot about this. :(
Comment by Aaron Griffin (phrakture) - Wednesday, 30 January 2008, 19:06 GMT
It really sounds too debian-ish to me... most of this stuff is currently handled via mkinitcpio. What utility would we gain beyond what mkinitcpip already supports (lvm, encrypted root, etc)?
Comment by pajaro (pajaro) - Wednesday, 30 January 2008, 21:56 GMT
What i had in mind is to set fsck in the shutdown process so that i can allays turn on my computer quickly. I don't feel this need anymore.

Also, since i became more brave as a coder, I don't see anymore that this should be a feature request. Initiscripts get updated slow enough to adapt each release.

As I see it now, i should create my own initscripts and add them to aur. If they came to be good and widely accepted then it is when the feature request should be opened.

Thank you for your time :)