SoylentNews is people
SoylentNews
posted by
janrinok
on Wednesday November 19 2014, @11:25AM
from the I-hope-we-don't-regret-this dept.
from the I-hope-we-don't-regret-this dept.
Ian Jackson's general resolution to prevent init system coupling has failed to pass, the majority vote deciding that the resolution is unnecessary. This means that not only will Debian's default init be systemd, but packages will not be required to support other init systems. Presumably, this means that using other init systems on Debian (without using systemd as a base) will not be possible without major workarounds, or possibly at all. It also leaves the future of Debian projects such as kFreeBSD unclear, as systemd is linux specific.
The vote results can be found here
The winners are:
Option 4 "General Resolution is not required"
This discussion has been archived.
No new comments can be posted.
Debian General Resolution to Prevent Init System Coupling Fails to Pass
|
Log In/Create an Account
| Top
| 179 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
"The subspace _W inherits the other 8 properties of _V. And there aren't
even any property taxes."
-- J. MacKay, Mathematics 134b
(Score: 2) by VLM on Wednesday November 19 2014, @02:05PM
I've been saying for awhile that "I" will make a doc trying to help refugees transition from linux to freebsd. In my infinite spare time aka its never happening beyond talking about it.
"someone" with more spare time than myself should create a wiki for ex linux users to translate into freebsd, or more likely a matrix of ex-debian people into freebsd and ex-redhat into openbsd or whatever as a 2-d matrix. I have the time to cut and paste my notes and add hyperlinks to the official docs. But not to run a wiki project.
The freebsd docs are good, but "we" are not their audience. I kid you not, they have cut and paste instructions for making a freebsd install flash drive from a freebsd command line. Thats useful for some people, but not experienced linux admins.
My biggest conversion problems have been "assumptions" about whats unified and what isn't, what has like 10 places to edit on one os vs one file here, what needs to be done in two places for WTF reasons, what is just plain weird and only documented in the deepest darkest pits (seriously, I shouldn't have to hit google multiple times all over the planet to set up X, even if for me as an experienced admin it was pretty easy, it was clumsy...) Oh and simple translation. I know where ldap.conf is on linux and I know where its been for a decade or so and I need a simple cheat sheet for freebsd.
Taking a tour of new features in *BSD is a side issue, maybe integrate it. Bhyve? Maybe. The mystery and miracle of ZFS? Maybe. The really cool jails system? Maybe. They don't fit directly into a transition guide, however. On the other hand, if you're gonna transition, best take advantage of everything there is to offer.
Yeah maybe in my infinite spare time this weekend. Maybe.
(Score: 2) by arashi no garou on Wednesday November 19 2014, @06:54PM
That's been my problem with trying out FreeBSD as a main OS, period: Time. I barely have any free time in the first place (free time meaning time outside of work and quality family time) so what little I have, I devote to more productive/entertaining things like learning Python and catching up on what little gaming I do. The migration back to Slackware from Crunchbang was fairly painless and quick; I have tons of experience using Slackware off and on for the past 15 years so it was a no-brainer. But FreeBSD is a different animal, that requires a heavy investment of time to learn all those little quirks and oddities (compared to GNU/Linux) that you wrote about above.
Speaking of, thank you for sharing! Just reading over it on my break at work has gotten my brain into the groove, so to speak. When I get home tonight (given enough time) I think I'll get started on really learning FreeBSD on bare metal, instead of the half-functioning VM rotting away on my main workstation.