Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
As title mentioned, debian is splitting is splitting to debian and devuan. What should i do? As far as i know, a lot of packages only has 1 person, who talks to the developer, what happens if he goes, who will fix the package??
What makes you think Debian is splitting into two distributions? Devuan is planned as a fork of Debian. Have you heard of Ubuntu, Mint or any of the other two-hundred or so similar distros that are forks and derivatives of Debian? If Devaun becomes a reality, it will simply be another one.
It is very simple to stop using systemd as PID1 (init) in Debian jessie (and beyond) -- there are menu entries provided in the GRUB screen to select either systemd or SysVinit
Of course this will still leave systemd libraries on the system but as these are now dependencies for many common programs this seems like a sensible compromise to me.
I have no idea how to quote ranicus, where is the quote button?, but ubuntu and mint are mostly made by people from outside like they have a company. Devuan is mostly made by people from debian itself, i hear theres a fight and things got crazy, obviously since i newbie, so i dunno much, but i am afraid they may drop package, what should i do, i dunno enough programming to manage my own package. Other distro have a company so they can just allocate another guy, but debian is not a company, if no one takes the package or it is too difficult, it is abandoned.... They already drop bsd you know.<br>http://www.itwire.com/business-it-news/open-source/66034-systemd-again?-debian-drops-kfreebsd-as-official-architecture<br>
Devuan was founded by people outside of Debian that didn't want to participate in Debian and opposed the change to systemd as default init system. Only very few Debian developers are involved in it and it is was officially welcome as a Debian derivative by the Debian people.
Don't worry, nothing will change in Debian.
I don't see Debian dropping any packages. Debian will most likely continue as usual. If packages need to be modified to work without systemd, then that's Devuan's problem. Devaun will probably be setup like LMDE (Linux Mind Debian Edition), where most of the packages will come straight from Debian, but Devaun will provide it's own packages to provide a systemd free experience.
I have no idea how to quote ranicus, where is the quote button?, but ubuntu and mint are mostly made by people from outside like they have a company. Devuan is mostly made by people from debian itself, i hear theres a fight and things got crazy, obviously since i newbie, so i dunno much, but i am afraid they may drop package, what should i do, i dunno enough programming to manage my own package. Other distro have a company so they can just allocate another guy, but debian is not a company, if no one takes the package or it is too difficult, it is abandoned.... They already drop bsd you know.<br>http://www.itwire.com/business-it-news/open-source/66034-systemd-again?-debian-drops-kfreebsd-as-official-architecture<br>
If the quote button was a rattlesnake. You'd be dead already.
No. AntiX is not a company, but a state of mind, and we run without systemd if we so wish and are based off of Debian stable,testing,and unstable branch depending on user preferences.
I usually run a trial run off of usb first with persistence so I can get a feel for things. I also run full test installs on my older gear like I did with Slitaz cooking. To see if I was up to the task. Unfortunately. I became busy and did not give Slitaz
the time and my full attention. I had other commitments that dragged me away from a good try out.
So try running off of a external usb or sd card and have some fun.
Because learning something new. Plus. Keeping it. Can be fun.
They already drop bsd you know.<br>http://www.itwire.com/business-it-news/open-source/66034-systemd-again?-debian-drops-kfreebsd-as-official-architecture<br>
Skipped that when responding earlier: Debian has not dropped the GNU/kfreebsd flavor, it just doesn't get an official release, like several other flavors that share the same fate of being not up to par with officially released branches.
We discussed kfreebsd at length, but are not satisfied that a
release with Jessie will be of sufficient quality. We are dropping
it as an official release architecture, though we do hope that the
porters will be able to make a simultaneous unofficial release.
As title mentioned, debian is splitting is splitting to debian and devuan. What should i do? As far as i know, a lot of packages only has 1 person, who talks to the developer, what happens if he goes, who will fix the package??
Avoiding-systemd asks: Would it be possible to provide some analysis on distros that refuse to implement systemd and its friends? Many people, including myself, believe systemd is taking Linux in the wrong direction. It abandons simplicity and embraces a model of opacity and centralized control, while increasing dependencies and reducing freedom and choice. Being a dedicated Debian user for 20 years, I'm extremely saddened and disappointed that Debian has succumbed to systemd, and that I must now leave Debian to find a new simple yet elegant distro solution that does not implement systemd, and specifically, will never implement systemd as a philosophical decision.
DistroWatch answers: When systemd first appeared on the scene as an alternative init system I was optimistic. There was a lot of talk about starting services in parallel and improving dependency resolution during start up and greatly improving boot times. While systemd seemed a bit more complicated than other init technologies, I think most system administrators (and developers) could agree that older init systems could be improved upon.
Over the past few years the systemd project has expanded, absorbing other low-level components and adding large amounts of unwanted complexity. Despite the fact many popular distributions (including Fedora, Red Hat Enterprise Linux, openSUSE, Debian, Arch and Ubuntu) have decided to adopt systemd in favour of SysV or Upstart, some users have opposed the spread of systemd. The Boycott systemd website features a list of reasons as to why many believe systemd is poorly designed and implemented.
In an effort to be fair to systemd I did a web search for "benefits of systemd" which returned two relevant results. One was the systemd website with its mission statement and the other was the Don't Boycott systemd website which simply stated: "systemd is [a] symbol of big changes in Linux world. Many people talks [sic] about how bad they are. And that's all." Which isn't a compelling argument. Instead, for comments about the advantages and disadvantages of systemd we might look at the recent debate by Debian developers as to whether they should adopt systemd or not.
On to the question of who is not currently using systemd and who will not be adopting it in the future. At the moment Ubuntu and most of the Ubuntu community projects have not adopted systemd, though they plan to migrate to systemd in the future. The PCLinuxOS distribution has not adopted systemd and, so far as I know, has no plans to migrate to the new init software. Slackware Linux, CRUX and Gentoo Linux are all Linux distributions which are unlikely to adopt systemd as their default init system for philosophical reasons. (Gentoo does offer systemd as an alternative init technology for those who want it.)
Most open-source operating systems which are strictly opposed to adopting systemd are not Linux distributions, but rather flavours of BSD. The systemd project intentionally targets Linux exclusively and this makes it highly unlikely systemd will be ported to FreeBSD, PC-BSD, OpenBSD or NetBSD. In fact, the OpenBSD Foundation began work on software which will allow the operating system to avoid running systemd, but will enable OpenBSD to run applications which depend on systemd. However, since the original poster mentioned running the Debian distribution, I have a potential solution that might avoid any big changes. The Debian project maintains an official port that marries the FreeBSD kernel with GNU libraries and Debian's package manager. I have run this branch of Debian in the past in test environments and if you can get it running on your hardware it will offer the Debian experience as far as the installer and package managing are concerned and the kFreeBSD port of Debian is unlikely to adopt systemd.
While systemd has stirred up a lot of strong opinions, both in favour and against the new init system, I suspect most people running Linux desktop systems will not notice the difference when they switch to systemd. I run a different distribution each week and haven't noticed any practical difference between running a desktop distribution that features Upstart, SysV or systemd. The various distributions typically boot at about the same rate, tend to be stable and desktop users rarely need to interact directly with the init process. The only time I interact with systemd is when I'm running it on a server, something the majority of people don't do.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
