Originally posted by hreindl
View Post
Announcement
Collapse
No announcement yet.
Systemd's Nspawn Lands OCI Runtime Support
Collapse
X
-
Originally posted by starshipeleven View PostNope.
Nope again.
You need a hard time to remove sysvinit or even OpenRC. It's a hard time to remove any core component of the system.
Sorry what? Are you seriously unable to remove Network Manager? It's as easy as zypper remove NetworkManager
I replaced it with ConnMan because it was not playing nice with VMWare (not playing nice as in "fucks up network access for the VMs"), but apart from that it's ok.
2) If you don find an agreement for the default init System, them the only Solution to fit us all,
Is to find a Standardized API, that could be made by all..
In this way, we would not have problems with systemd, we simply could ignore him, or any other in the System..
Off-course SysVinit should have adjustments to comply, like any other init out there, but maintain its simplicity..
In this way we would not even speak about this subject..
3) The crucial problem of Debian...
Debian is NOT Gnome, and those guys loosed the perspective( This one, for those who knows what I am talking about ).
Debian is a lot more used, or used to be, in the Datacenter, than as a desktop..
I Understand the desire of also bring Debian to the Desktop, because it can make a good system..
But if, The Intentional Bad Decisions, were not made,
We would not have this problem now..
I agree that is difficult for any core component, its precisely because of that, that should be Standardise a process, for everyone( to simplify it.. )
- Likes 1
Comment
-
Originally posted by tuxd3v View Post1) In relation to SysvInit, there should be there a agreement between all major players, at least,( not only the most corporate 1, now IBM ).
2) If you don find an agreement for the default init System, them the only Solution to fit us all,
Is to find a Standardized API, that could be made by all..
In this way, we would not have problems with systemd, we simply could ignore him, or any other in the System..
Off-course SysVinit should have adjustments to comply, like any other init out there, but maintain its simplicity..
- Likes 2
Comment
-
Originally posted by tuxd3v View Post
Hum...
I am not sure that you described linux..
Hurd and other {u,n}kernels perhaps..
- Likes 2
Comment
-
Look at Slackware, it's BSD style gives one init script to each runlevel - but it's still actually using SysV not BSD's RC.d.
But in "normal" SysV init basically each runlevel is given a subdirectory for init scripts.
​​​​​​Welcome to the maze of symlinked init scripts.
Why go easy way, lets spend thousands of man hours.. Lets replace half the GNU/Linux instead of considering existing alternatives..Last edited by aht0; 23 March 2019, 08:21 AM.
- Likes 1
Comment
-
Originally posted by pgoetz View PostI knew reading the comments would be a complete waste of time, but I read them anyway. OMFG, people. if you don't like systemd, use a distro (Slackware, Devuan, gentoo) that doesn't use it and stop bellyaching. Just once I want to read the comments on a systemd article and find useful technical information / experiences and not just the chicken clucking of a bunch of whiny bitches.
Comment
-
Originally posted by FastCode View PostThose useful technical information that you so crave can't come from me when my favorite IDE, debugger, compiler, runtime, .. only officially support the systemd-cancerd ridden distros. You people think that we're masochists and like to suffer?
- Likes 1
Comment
-
Originally posted by skeevy420 View Post
Someone did....but our blacklist doesn't actually work...
There's also the option of using a plugin like FoxReplace...it can make Phoronix fun...check out Gentoo's latest init system for example.
Comment
Comment