Le Wed, 8 Dec 2010 02:46:24 +0100, Miklos Vajna <[email protected]> a écrit :
> On Wed, Dec 08, 2010 at 12:40:08AM +0100, Miklos Vajna > <[email protected]> wrote: > > That sounds nice, though a bit hard to implement - given that sysvinit > > and systemd conflicts with the /sbin/reboot and similar files. > > Ah, perhaps we could introduce a USE_SYSV_REPLACE, which would control the > replaces/provides/conflicts and the /sbin/reboot and similar symlinks. > That way if it's =y, then we have the current situation, if it's =n, > then you can do parallel installation, and systemd should depend on > sysvinit for the /sbin/reboot and similar commands. > > Is this what you thought about? > > Thanks. Hi, Yes I thinking use a USE_SYSV_REPLACE, for add it into current and don't replaces sysvinit by systemd and don't create this symlinks : Fln /bin/systemd /sbin/init Fln /bin/systemctl /sbin/reboot Fln /bin/systemctl /sbin/halt Fln /bin/systemctl /sbin/poweroff Fln /bin/systemctl /sbin/shutdown Fln /bin/systemctl /sbin/telinit Fln /bin/systemctl /sbin/runlevel We use sysvinit binary, after it's easy for user (and dev :p) to switch sysvinit to systemd or systemd to sysvinit. -- #--------------------------------------------------------------------------- # Bouleetbil # #--------------------------------------------------------------------------- # _ _ # (o)--(o) # /.______.\ # \________/ # ./ \. # ( . , ) # \ \_\\//_/ / # ~~ ~~ ~~ #--------------------------------------------------------------------------- _______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
