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
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
|
Details
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!
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!
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.
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.
http://projects.archlinux.org/netcfg.git/tree/docs/index
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".