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#11125 - [initscripts] Add/Disable Daemons via Bootloader

Attached to Project: Arch Linux
Opened by Bjoern Hiller (Zaphod) - Tuesday, 05 August 2008, 20:18 GMT
Last edited by Paul Mattal (paul) - Tuesday, 05 January 2010, 23:38 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas B├Ąchler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


Description: Add a kernel line in the bootloader for adding/disabling daemons

Files affected:
* /etc/rc.multi

A possible patch is attached.
This task depends upon

Closed by  Paul Mattal (paul)
Tuesday, 05 January 2010, 23:38 GMT
Reason for closing:  Won't implement
Additional comments about closing:  There's now a way to do this with netcfg, which has been deemed satisfactory by the original request submitter.

Go netcfg!
Comment by Jan de Groot (JGC) - Tuesday, 05 August 2008, 20:42 GMT
If I understand correctly, this allows to disable a specific daemon by appending a line in the kernel option list?

If so, I don't like the idea of abusing kernel/initcpio commandlines for the initialization of userspace. If you inserted a problematic daemon in DAEMONS, you'll have to boot in single user mode to get rid of it.
Comment by Bjoern Hiller (Zaphod) - Tuesday, 05 August 2008, 20:51 GMT
My idea was to create several grub entries to be started in different environments. E.g. I have to start some additional daemons (samba, cups) if I'm at university.

I don't think it's abusive to use kernel commandlines. NET=foobar (/etc/rc.d/net-profiles) and disablemodules (/etc/rc.sysinit) do the same.
Comment by Laszlo Papp (djszapi) - Saturday, 07 November 2009, 08:10 GMT
to reach single user mode to change those configurations is a short-period on arch, just some seconds :)
Comment by Aaron Griffin (phrakture) - Wednesday, 02 December 2009, 21:41 GMT
While this is WAY later, couldn't this sort of thing be handled by netcfg now? Netcfg can do crazy things based on the network you connect to
Comment by Paul Mattal (paul) - Tuesday, 05 January 2010, 01:45 GMT
It sounds like if you can rely on cuing off the network, netcfg should do it:

According to this doc, netcfg supports:
* Execution of commands before/after up/down

That should be sufficient to do anything you'd need.

I see the elegance of your suggestion, but agree with the division pointed out by JGC -- kernel arguments should configure the kernel, not userspace.

Let's have all comments in on this one by February bug day, otherwise we'll close it as "won't implement".
Comment by Bjoern Hiller (Zaphod) - Tuesday, 05 January 2010, 18:24 GMT
I'm fine with "won't implement" as this can be done by netcfg now (at the time of creating this bugreport netcfg was not able to do this).