DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
At least for Jessie there will be compatibility with sysvinit scripts, so it should be possible to run Jessie as a sysvinit system, but soon afterwards likely that compatibility will be dropped in the then new testing, unless their will be a new decision to support multiple systems (or a GR overrides the CTTE decision).
That's mostly the result of a bigger question:
Is it still possible/useful to support everything inside a single distribution?
IMHO Debian would greatly benefit from a less modular design.
First of all. You're not some of those guys that think that eliminating The Bad you're really simplifying, are you?
In general to support everything is not a good strategy. That's why I like
Unix. But community driven development model falls in that state naturally, it's not the result of a strategy.
The issue here is that "to support everything" is not "to make everybody happy". In a world made of people that think and choose, perhaps. But in this world "to make everybody happy" is as easy as imitating big monkeys. Make Linux behave like Windows and everybody will be happy. That's the strategy we are suffering today.
First of all. You're not some of those guys that think that eliminating The Bad you're really simplifying, are you?
You guys stop talking about good vs. bad, that is not the point here, the point is design, more specifically a design with KISS, having each program do one thing but do it well, and be as loosely coupled as possible.
THe OS should implement various facilities like IPC and file ownership and make it easy to access network resources and implement security measures, but that is about it, everything else should be optional, configurable and the ability to choose between alternatives should exist.
In a nutshell this is it, and the UNIX design principles and philosophy have provided it for almost half a century.
systemd is a clear deviation from those design principles and a step in the wrong direction for all Linux.
You guys stop talking about good vs. bad, that is not the point here, the point is design
Please, read carefully and try to understand what the other said before quoting.
What you state has been said a hundred of times. Even the defenders of systemd know that. Why systemd wins anyway? Fashion. That's why any technical (or political) discussion about systemd is pointless.
First of all. You're not some of those guys that think that eliminating The Bad you're really simplifying, are you?
In general to support everything is not a good strategy. That's why I like
Unix. But community driven development model falls in that state naturally, it's not the result of a strategy.
The issue here is that "to support everything" is not "to make everybody happy". In a world made of people that think and choose, perhaps. But in this world "to make everybody happy" is as easy as imitating big monkeys. Make Linux behave like Windows and everybody will be happy. That's the strategy we are suffering today.
I mostly meant the black & white view on dependency coupling in the ctte debate (meaning I essentially agree with you on this)..
It's (IMO) neither desirable or necessary to have every single package in main for all architectures/kernels/user-cases.
Calling that "less modular" was bad usage of the English language from my side (apologies if that caused some confusion).
Please, read carefully and try to understand what the other said before quoting.
What you state has been said a hundred of times. Even the defenders of systemd know that. Why systemd wins anyway? Fashion. That's why any technical (or political) discussion about systemd is pointless.
I did, good vs. bad is purely abstract, furthermore writing shell scripts is neither that hard nor that time consuming as some people might have you think.
Your entire point was terrible, although I give you points for calling systemd the result of fashion.
I did, good vs. bad is purely abstract, furthermore writing shell scripts is neither that hard nor that time consuming as some people might have you think.
Your entire point was terrible, although I give you points for calling systemd the result of fashion.
Transparent. From now I'll agree with you in all to get more "vl23 points".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.