As I sit here writing this tonight, I am totally amazed at the genuine stupidity of DistroWatch dot com. Some in the Linux world would have you believe that the writers at DW are all just an article/post away from a Pulitzer prize. Their statistics, when it comes to the “most popular” Linux distro available, based on a “Hits per day” method to gauge popularity, is about as accurate as any internet poll you’ll come across.
Many new to Linux hear of DW and truly believe it is Linux gospel. It is NOT! To bandy about a headline, “Community developments: The systemd project forks the Linux kernel”, that is such a hot button issue for Linux users today is totally irresponsible and, for me, conclusively proves they have zero credibility.
For those who come to their defense, claiming “Oh it was just an ‘April Fools’ joke, we are still in March! To post such an article with no disclaimer, no acknowledgement that it is comic relief, is not just poor editorial oversight, but truly poor judgement. For those in the land of make believe, pixie dust, and Yosemite Sam, (Ivan Gotyaovoitch?) look no further for what is “NOT” happening in the world of Linux than DW. DistroWatch must be fervent followers of PT Barnum, who is credited with coining the phrase, “There’s no such thing as bad publicity”.
The below post, as well as the one prior, was posted (by me) at the VSIDO forums on a thread there debating the direction Debian should go with a new init system. (I’ve made that a direct link to the thread in question) As this vote gets nearer, it is time for some alarm in the Linux community, and everyone should in some way try to make their voice heard. This is my way. It isn’t meant to offend anyone, truly. This is a serious issue that is about to happen and Debian should know how we feel about it.
Wow. What can I say that statmonkey hasn’t? Not much if anything at all…
At around the 40 minute mark in the first video posted above, when Steve Langasek starts in with the “what’s up with Debian and licensing”, I definitely threw in the towel on Upstart. Not that I hadn’t already, but when Canonical starts telling dev’s to send in their work, and don’t bother signing the CLA, and see what happens, that was it for me. I had read in a couple of different places on the net where some of Ian’s (Ian Jackson, former Canonical/Ubuntu dev) posts sounded like he was going to go for Upstart. I have to say after watching the above, that I don’t think you can read more
OK, my .00002 cents worth. (sorry for the lengthyness of this post, it touched a nerve maybe or something close)
First, what is the problem with sysvinit? OK, so systemd will do a complete userspace boot-up in 900ms. So what? Having personally tried systemd with VSIDO, I saw no ‘great’ benefits. OTOH, I have never tried Upstart. (does using Upstart mean using Mir/Unity?)
Second, when you mention Upstart, all that I can think of is “we’re Shuttleworth’d”…
And third, why do we have to have one, or the other? There are multiple choices now. (As Digit so aptly mentions above)
Back to boot speeds, I read one posters comment, (on one of the other forums) and I’m paraphrasing here, if my system takes 3 to 5 minutes to boot, but once booted it remains solid and has no issues, then I don’t care. Personally I think that the boot speeds that most people are talking about these days have more to do, generically, with UEFI than systemd. (yes, I know systemd drastically can reduce boot times, and have seen that with my own eyes) But, UEFI passes the boot off from the BIOS (read; slow) and directly to hardware, which, if your using an SSD, can seem instantaneous. So, in a server environment, IMO, boot speeds tend to be irrelevant. On a desktop (laptop) this becomes even more irrelevant. (unless of course, your James Bond, the earth is getting ready to explode, and you have to save the read more