Hi, I'm writing here - though this mail right now is probably just interesting for Hermier and Bouleetbil. :)
So - we started to remove rc.foo init scripts for lowlevel stuff where the functionality is already provided by systemd. I thought about this a bit more and it turns out removing rc.foo files right now is not a good idea. Here are the details: 1) The initial problem is that when the user installs systemd she should be able to reboot properly - think of remote boxes. So we _need_ the old scripts till the next reboot. 2) systemd supports having a unit _and_ a legacy init script for a service, and in that case it'll just use the unit without any problem. Example: our rc.modules is no longer needed, as systemd-modules-load.service already provides that functionality. Old action: we removed rc.modules. New action: ln -s systemd-modules-load.service /lib/systemd/system/rc.modules.service That also allows us to: - painless upgrade (see above) - we can introduce unit files in -current as they don't cause any problem To sum up: based on the above, sooner or later (but before merging it) I want to get rid of all rc.foo removals in the systemd repo. Does that sound reasonable? Thanks.
pgpUHXhhoRokG.pgp
Description: PGP signature
_______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
