Originally posted by pingufunkybeat
View Post
Announcement
Collapse
No announcement yet.
Debian To Switch To Systemd Or Upstart
Collapse
X
-
Originally posted by RahulSundaram View PostObviously not. It is just open source code. Ubuntu developers have commit access to systemd repository and continue to use pieces from systemd sources like udev and logind without using systemd as the init system. They may fork logind in the future but there is no force involved here.
The post basically reads as: We swallowed udev and we can't await to make it not work anymore on anything but systemd.
Comment
-
Originally posted by Vim_User View PostObviously yes, they announced that and you are aware of that: http://lists.freedesktop.org/archive...st/006066.html
The post basically reads as: We swallowed udev and we can't await to make it not work anymore on anything but systemd.
Comment
-
Originally posted by RahulSundaram View PostYou are confused. eudev fork has nothing to do with Ubuntu. It is a Gentoo fork because they want to strip down compile time requirements to only the parts they include. Binary based distributions like Ubuntu don't care about that much.
I mentioned refusing patches and saying "If you don't like it, fork it" to people who simply wanted udev to BUILD. So that's one distro that got screwed for not using systemd. Because a harmless, simple patch was refused for no reason.
Comment
-
Originally posted by pingufunkybeat View PostWho mentioned Ubuntu? You mentioned Ubuntu in a Debian thread, and then went off on a tangent
I mentioned refusing patches and saying "If you don't like it, fork it" to people who simply wanted udev to BUILD. So that's one distro that got screwed for not using systemd. Because a harmless, simple patch was refused for no reason.
Comment
-
Originally posted by arti View PostI'm building right now a systemd version of Linux From Scratch and i realy doubt that it's going to be anymore complicated than using sysvinit
Though I'd recommend doing it in a VM if you're not already - diagnosing bootup problems is so much easier on a machine that can be rebooted in seconds, while keeping the docs open in a different window.
Comment
-
Hopefully they select systemd instead of some old-school mess of scripts.
Other init systems just don't work. Here is simple example with OpenRC:
Code:/etc/init.d/apache2 restart * Stopping apache2 ... [ ok ] * Starting apache2 ... * start-stop-daemon: /usr/sbin/apache2 is already running [ ok ]
Comment
-
Originally posted by ArneBab View PostOpenRC works well for Gentoo. Why do you call it capaign to say that the discussion misses a relevant system?
I use RHEL 6/ubuntu too in some clients of mine and everytime i have use upstart i feel like im handling old days HPUX or Caldera.
I mean the difference is big enough to inform my client's IT departments that for the next update they need a distro with systemd or it just won't work[thing that will help me remove around 7000 lines of code needed to deal with every sysV like nightmare out there + add amazing stuff like sandboxing/safe trackeable process spawn, engine switch when virtualized, focused logs, resource jailing, bullet proof child process clean, reliable subprocess spawn under demand(OMG), session integration(OMFG), timed tasks through dbus(no more f/d/g/h/u/j/k/l/cron lucky shots), self restart when crash + reliable logs through journald/dbus to send me back, 1 only one service file for any distro(with systemd ofc) OMG only 1 yes 1 i really mean 1 no tricks is realy really just 1]
i do admit tho systemd more important goodies are for devs or transparent to the user
Comment
-
Originally posted by jrch2k8 View Postwell as an gentoo user i admit openrc is sysV with nitro but after test systemd i just nuke openrc from my system entirely[just keep certain bashies needed for eselect that gentoo devs insist in keep them inside openrc instead of eselect ebuild]. the difference is just too huge to go back.
i do admit tho systemd more important goodies are for devs or transparent to the user
Comment
Comment