NSA: Please Turn off the Lights When You Leave. Nothing to See Here.

Linux Advocate Dietrich Schmitz shows how the general public can take action to truly protect their privacy using GnuPG with Evolution email. Read the details.

Mailvelope for Chrome: PGP Encrypted Email Made Easy

Linux Advocate Dietrich Schmitz officially endorses what he deems is a truly secure, easy to use PGP email encryption program. Read the details.

Step off Microsoft's License Treadmill to FOSS Linux

Linux Advocate Dietrich Schmitz reminds CIOs that XP Desktops destined for MS end of life support can be reprovisioned with FOSS Linux to run like brand new. Read how.

Bitcoin is NOT Money -- it's a Commodity

Linux Advocate shares news that the U.S. Treasury will treat Bitcoin as a Commodity 'Investment'. Read the details.

Google Drive Gets a Failing Grade on Privacy Protection

Linux Advocate Dietrich Schmitz puts out a public service privacy warning. Google Drive gets a failing grade on protecting your privacy.

Email: A Fundamentally Broken System

Email needs an overhaul. Privacy must be integrated.

Opinion

Cookie Cutter Distros Don't Cut It

Opinion

The 'Linux Inside' Stigma - It's real and it's a problem.

U.S. Patent and Trademark Office Turn a Deaf Ear

Linux Advocate Dietrich Schmitz reminds readers of a long ago failed petition by Mathematician Prof. Donald Knuth for stopping issuance of Software Patents.

Showing posts with label Udev. Show all posts
Showing posts with label Udev. Show all posts

Wednesday, May 8, 2013

Systemd: Got Choice?

by Dietrich Schmitz

I've been thinking over the whole systemd issue and have written several stories about it.

It seems to me that somehow a major tenet of Linux has been overlooked:



CHOICE

When exactly did choice go out the window?

I want to know why systemd is not an 'opt-in' configurable option?

Did I miss something?  No, I am afraid I didn't.

No, the whole situation has really been simmering in my mind and as I did more research on systemd, the only conclusion I can reach is that systemd is being foist upon us without a shred of consideration being given to 'choice'.

There is no recognition of or respect given to choice when a Distro simply removes sysvinit or any of the other fine initialization schemes in favor of systemd.

This represents a violation of a major tenet of Linux that I cherish and don't appreciate having simply taken away from me.  Choice is mine.  I can let someone else make a decision for me, or, I can seize control and decide for myself what is best for me.  Someone else has decided that systemd is best for everyone.  Well, guess what?  It isn't.  And you don't have to accept it.  There are still Distros which don't use systemd and some that actually do give you the option to use it.

As far as I am concerned, this is a grievous error and every user should protect their given right to choose what is best for their situation.

Making systemd an opt-in configurable choice should have been given top priority.

If you don't protect your right to choice, who else will?

Today, as a matter of principle, I am taking action on this issue and resolve to do something about it.  Taking choice away is wrong and elitist at best.

I will fill you in later in a follow up story.

-- Dietrich
Enhanced by Zemanta

Wednesday, May 1, 2013

Gentoo Team Isolates Udev from Systemd (eudev)

by Dietrich Schmitz 

I've written a series of articles centered around the development of a new middle-ware initialization daemon service called systemd.

In my last post, Systemd: An Accident Waiting to Happen, I shared the concerns of one Developer who wrote about why systemd should not be used in Linux.  I feel strongly that his concerns elucidated are valid and I strongly urge you to consider an alternative to using systemd.

Gentoo programmers announced on December 17, 2012 the fork of udev to eudev.  And over the last several months have arrived at a workable solution.

On their GitHub site they invite other Linux Community Developers to participate in enhancing the eudev project so as to assure it becomes fully compatible with their respective initialization service protocol.  Here is a passage from the text from the README file in their eudev repo:

This git repo is a fork of git://anongit.freedesktop.org/systemd/systemd with the aim of isolating udev from any particular flavor of system initialization. In this case, the isolation is from systemd. 
This is a project started by Gentoo developers and testing is currently being done mostly on OpenRC. We welcome contribution from others using a variety of system initializations to ensure eudev remains system initialization and distribution neutral.

This is an extremely important initiative as it relates to finding a solution that removes all dependency on systemd to so allow eudev to operate with Gentoo's OpenRC initialization routines.

Your participation is encouraged to increase the scope of compatibility of eudev to ensure their continued system initialization independent operation.    -- Dietrich

Enhanced by Zemanta

Sunday, April 14, 2013

Developer Dissatisfaction Looms with Systemd

by Dietrich Schmitz

Things seem to be moving along swimmingly with ongoing development surrounding systemd, at least as far as Lead Developer Lennart Poettering is concerned who has outlined the plans for moving the project forward with hopefully full upstream community participation in lock step.

Some of the dissenters have been quite vocal about having systemd 'forced' on them.  Countering that sentiment is the prevailing argument that developers don't have to use systemd.  +Fabian Scherschel opened a talkback thread regarding my Linux Advocates story Systemd: The New PulseAudio in a public Google Plus post made yesterday with this comment:

There is no controversy. Unlike PA, it was adopted when it was ready to be adopted and everybody seems to like it very much. With the exception of the Ubuntu people but that seems to be based on NIH alone. This is a completely different situation then PA.

Fuduntu Founder +Andrew Wyatt returned fire with this volley:

ConsoleKit + UDev + Syslog + DBus + Polkit + Sysinit + this + that.   RedHat Enterprise Systemd is the best product we've ever been force fed.  We are facing being forced to integrate it at Fuduntu because it's replacing so many core tools now that it's impossible to continue the project without it.
It seems fairly understandable that smaller Distro Teams are indeed resource-strapped and so cannot muster the resources to refactor their programs to by-pass the new systemd project's major structural changes.  The volume of work necessary to avoid systemd will effectively result in forcing the Developers to do just what Mr. Wyatt describes--be forced to use systemd.  I would add that the other alternative would be to 'end of life' a distribution.

That would be most unfortunate if that were to happen and the possibility of many fledgling Distros not being able to accommodate systemd to their own demise seems to be a distinct possibility.

Will a Linux Distribution 'consolidation' occur?  That remains to be seen and Linux Advocates will continue to follow this story closely.

The matter of personalities also, unfortunately, has caused some undue friction as systemd Lead Developer Lennart Poettering, also developer of PulseAudio, has a penchant for freely speaking his mind and this has been a source of conflict that might have been completely avoided had he exercised a large degree of self restraint, tact and diplomacy in making public statements.

In one such statement, Slashdot.org ran this story:

"In an interview with LinuxFr.org, Lennart Poettering speaks freely about his creations, PulseAudio, Avahi and systemd among other things. Naturally, what has stirred up most of the discussions online is Lennart's opinions on BSD. Following the recent proposal to make Gnome a Linux-exclusive desktop, Lennart explains that he thinks BSD support is holding back a lot of Free Software development. He says this while also taking a stab at Debian kFreeBSD: 'Debian kFreeBSD is a toy OS, people really shouldn't misunderstand that.'"
At this juncture, it's clear that systemd will not support kFreeBSD.  That appears to have not changed since the above story ran in 2011.

Debian's next operating system revision, is code named "Wheezy" (Debian 7.0).  An official release date has not yet been announced but the NewInWheezy page does confirm that systemd is included as an installable 'option'.

So, the tension is palpable and right under the surface is brewing dissatisfaction among the rank and file developers who must either deal a huge undertaking of refactoring code, packaging, etc., or cave in and simply implement systemd or worse simply perish.

The writing is on the wall.  Implement systemd or you are on your own, like it or not.

-- Dietrich
[Edit: 4/15/2013 9:00am GMT-5 This story just in confirms what I feared.  Fuduntu has been end of life'd.]

Enhanced by Zemanta