Hi *, (especially hermier, bouleetbil) On Mon, Dec 13, 2010 at 03:17:03PM +0100, Miklos Vajna <[email protected]> wrote: > > I likes the first idea. But I would only can choose sysvinit or systemd on > > boot. > > OK - I agree here. Sooner or later I'll polish up the systemd repo > enough to be able to merge it, then we'll have systemd in base, but > it'll be disabled by default and one will be able to test it using > init=/bin/systemd.
Big words - I think we're ready for this. ppc is not yet in sync, but that's all. What we need now is to test we are backwards compatible. If you want to help, just follow the instructions here: http://wiki.frugalware.org/index.php/Systemd#WIP_repo But do _not_ add anything to the kernel commandline. The expected result is really just that nothing breaks. Also, if you want to play, you can alter your kernel commandline and give systemd a try, but the main point is to test the sysvinit part of the changes introduced by the systemd repo. If nobody shouts and the repo gets in sync, I plan to merge the systemd repo on Monday. (Again, it's disabled by default, so it's not a huge change.) > And after a long enough testing period we can make it the default. Considering how critical component of Frugalware an init systemd is, and that we're soon at rc1, I don't think it would be a wise idea to change the default for 1.4. I also say this because we got some reports about some cgroups kernel bug (the cgroups feature is heavily used by systemd), which is already fixed in kernel-2.6.37-rcX, but we don't have that in -current yet. Of course if it's all OK, we can change the default right after 1.4 is out. Does this sound OK?
pgp7Mx3dIv9J0.pgp
Description: PGP signature
_______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
