Goings-on and Guidance about systemd

[GoOSSBears]

Howdy all on the start of this Labor Day Weekend, 2014,

What is the current state of the systemd discussion around the blogosphere??
(likely to be a fairly heated question)

Someone mentioned there was recent systemd discussion-activity on the mailing-list of the local SF-LUG (http://linuxmafia.com/mailman/listinfo/sf-lug), but I keep rcv'ing the timeout message of "The server at linuxmafia.com is taking too long to respond."

Could also use some very clear systemd guidance and/or links for fixing up two i386 Debian jessie/testing boxes that had systemd thrust upon them when doing a full 'apt-get dist-upgrade' process.

- I've already viewed the initsystem debate between good old SysV (which I'm fairly comfortable with) and systemd, see https://wiki.debian.org/Debate/initsystem/systemd
- A few weeks ago, there was a ranting Open letter to the Linux World on systemd by a Christopher Barry, see https://lkml.org/lkml/2014/8/12/459
- Have already scanned what I think are three other immediate and appropriate references to systemd; http://www.freedesktop.org/wiki/Software/systemd/, https://packages.debian.org/jessie/systemd and https://wiki.debian.org/systemd

The last (and ultimate) reference writes that "systemd is a system and service manager for Linux. systemd is compatible with SysV and LSB init scripts. It can work as a drop-in replacement for sysvinit. Systemd etc etc etc..."

If systemd can work as a drop-in replacement for sysvinit/SysV, then can't it also be dropped-OUT and the initsystem get reverted to SysV??

As written in the prenultimate reference above, "Installing the systemd package will not switch your init system unless you boot with init=/bin/systemd or install systemd-sysv in addition."

If true, then wouldn't it be practically possible to revert to my gold old SysV by first removing systemd-sysv and then swapping out the 'init=bin/systemd' for 'init=/bin/sysvinit' in the appropriate GRUB boot-manager kernel entry location??

Am groping around for straws here, and don't wish to so quickly fail an attempted SysV reversion from whatever systemd initialization is currently working -- and thus prevent the i386 Debian jessie/testing boxes from booting up.

Will keep a lookout for more helpful hints and links regarding systemd.
-A

--
Go Open Source Software Bears!


_____________________________________________________________
Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com
Join Linux Discussions! --> http://Community.LinuxWaves.com

[bloonoise]

systemd is undeniably the future of linux. Once you get comfortable with
it and its various commands ie; systemctl , journalctl etc.
its a very comfortable init system. There is a Sys5 dropin so they can
both run together if youre stuck in your ways. Working with
systemd is a breeze and a good fit. It still in rapid development but
is quite stable for the most part. It also has a gui but that is quite
lame. Its best worked with in CLI. It is well documented in Fedora,
Red hat, Gentoo, Arch, and freedesktop.org.
Don't be such a fuddy dud systemd rocks. Try it with a smile you'll like
it. If not you'll be left in linux dust!

Post by GoOSSBears
Howdy all on the start of this Labor Day Weekend, 2014,
What is the current state of the systemd discussion around the blogosphere??
(likely to be a fairly heated question)
Someone mentioned there was recent systemd discussion-activity on the mailing-list of the local SF-LUG (http://linuxmafia.com/mailman/listinfo/sf-lug), but I keep rcv'ing the timeout message of "The server at linuxmafia.com is taking too long to respond."
Could also use some very clear systemd guidance and/or links for fixing up two i386 Debian jessie/testing boxes that had systemd thrust upon them when doing a full 'apt-get dist-upgrade' process.
- I've already viewed the initsystem debate between good old SysV (which I'm fairly comfortable with) and systemd, see https://wiki.debian.org/Debate/initsystem/systemd
- A few weeks ago, there was a ranting Open letter to the Linux World on systemd by a Christopher Barry, see https://lkml.org/lkml/2014/8/12/459
- Have already scanned what I think are three other immediate and appropriate references to systemd; http://www.freedesktop.org/wiki/Software/systemd/, https://packages.debian.org/jessie/systemd and https://wiki.debian.org/systemd
The last (and ultimate) reference writes that "systemd is a system and service manager for Linux. systemd is compatible with SysV and LSB init scripts. It can work as a drop-in replacement for sysvinit. Systemd etc etc etc..."
If systemd can work as a drop-in replacement for sysvinit/SysV, then can't it also be dropped-OUT and the initsystem get reverted to SysV??
As written in the prenultimate reference above, "Installing the systemd package will not switch your init system unless you boot with init=/bin/systemd or install systemd-sysv in addition."
If true, then wouldn't it be practically possible to revert to my gold old SysV by first removing systemd-sysv and then swapping out the 'init=bin/systemd' for 'init=/bin/sysvinit' in the appropriate GRUB boot-manager kernel entry location??
Am groping around for straws here, and don't wish to so quickly fail an attempted SysV reversion from whatever systemd initialization is currently working -- and thus prevent the i386 Debian jessie/testing boxes from booting up.
Will keep a lookout for more helpful hints and links regarding systemd.
-A
--
Go Open Source Software Bears!
_____________________________________________________________
Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com
Join Linux Discussions! --> http://Community.LinuxWaves.com
_______________________________________________
BALUG-Talk mailing list
http://lists.balug.org/listinfo.cgi/balug-talk-balug.org

[Elizabeth K. Joseph]

Post by GoOSSBears
Will keep a lookout for more helpful hints and links regarding systemd.

I have to admit not really being up to speed with much of the latest
systemd discussions (all init systems work "good enough" for me, it's
not a great concern of mine), so it was really interesting this week
at DebConf to see a talk on "A glimpse into the future of systemd"
which talked about some of the features and future enhancements. Video
available on DebConf's talk archive:
http://meetings-archive.debian.net/pub/debian-meetings/2014/debconf14/webm/

[Scott DuBois]

Post by GoOSSBears
Howdy all on the start of this Labor Day Weekend, 2014,
What is the current state of the systemd discussion around the blogosphere??
(likely to be a fairly heated question)
Someone mentioned there was recent systemd discussion-activity on the mailing-list of the local SF-LUG (http://linuxmafia.com/mailman/listinfo/sf-lug), but I keep rcv'ing the timeout message of "The server at linuxmafia.com is taking too long to respond."

Not sure about that discussion, but spent the better part of the day
with linuxmafia yesterday and you should be able to resolve connections
shortly.

[GoOSSBears]

Thanks to a few helpful link-hints from another person and a bit of research on my own over the long holiday weekend, I became much more up-to-date of the goings-on of systemd.

InfoWorld came out last week with an OpEd by a Paul Venezia entitled 'Choose your side on the Linux divide', see http://www.infoworld.com/d/data-center/choose-your-side-the-linux-divide-248950 .

Apparently, the key developer of systemd is a Lennart Poettering, formerly of Red Hat, Inc. and the key developer for the new PulseAudio. Info came from one of the systemd resistance sites, http://boycottsystemd.org/ .

Lennart P published several tables justifying the use of systemd as the better initsystem of the existing ones (see http://0pointer.de/blog/projects/why.html .)

Lennart P both revealed his future systemd plans and coined the term "systemd cabal" in his blog post from yesterday, http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html .
A commentator with the username 'papaf' questioned after yesterday's blog post whether systemd is doing an "Embrace Extend Extinguish", see https://news.ycombinator.com/item?id=8251678 .

A PDF slide from a Lennart P presentation earlier this year also reveals his current plans for systemd, see http://0pointer.de/public/gnomeasia2014.pdf .

bloonoise wrote in this BALUG thread: "Once you get comfortable with it and its various commands ie; systemctl , journalctl etc. its a very comfortable init system. There is a Sys5 dropin so they can both run together if youre stuck in your ways."

On that, an up-to-date Debian User Forum thread entitled 'The future with Systemd' delves into some systemd matters, see http://forums.debian.net/viewtopic.php?f=20&t=116860 .
A comment there lists the commands I might want to use to temporarily drop-OUT systemd on my two i386 Debian jessie/testing boxes, see http://forums.debian.net/viewtopic.php?f=20&t=116860&start=60#p551985 . This drop-out shim requires that I use the Debian systemd-shim package
as described at https://packages.debian.org/jessie/systemd-shim .

While the SF-LUG linuxmafia connections issue gets resolved , I am certainly open to remaining on the lookout for more Goings-on and Guidance links about systemd. Even a few really good systemd HowTo's would greatly help.

--
Go Open Source Software Bears!


_____________________________________________________________
Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com
Join Linux Discussions! --> http://Community.LinuxWaves.com