Interesting and technical article above systemd + trolling

[Head_on_a_Stick]

A double forking daemon with no pidfile can still be started by systemd though, providing this option is used in the unit file instead:
[Service]
Type=oneshot

This approach loses the monitoring / restarting benefits of systemd though.

This is not true.

In my Debian jessie system I use a custom unit file to start the wireless connection:

Code: Select all

[Unit]
Description=Wireless network connectivity (%i)
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device

[Service]
Type=oneshot
RemainAfterExit=yes

ExecStart=/sbin/ip l set %i up
ExecStart=/sbin/wpa_supplicant -B -i %i -c /etc/wpa_supplicant/wpa_supplicant.conf
ExecStart=/sbin/dhclient %i

ExecStop=/sbin/ip l set %i down

[Install]
WantedBy=multi-user.target

As you can see, it is "Type=oneshot" -- it makes all the usual journal entries and can be stopped and restarted normally with systemctl(1)

[Hralgmir]

Readahead has definitely been removed, Lennart explains here:
https://www.mail-archive.com/systemd-de ... 21693.html
Sadly I have only just heard of this so was unable to offer any assistance.
I can only guess that either they have become tired of the popularity of systemd or are using it to degrade the performance of older hardware as a result of pressure or financial incentives from other sections of the computer industry.
I think that it's possible to argue that systemd is written to dissuade everyone from simply copying so much of Fedora and go off and write their own distro's instead, if you look at it's monolithic entanglement with the rest of the RedHat desktop, paying no regard to existing package boundaries. Whatever their motives I don't see that it would be my first choice in future on my current hardware, although I thought I should give it a try for the moment as it is the default in Debian.
Could the dropping of optimised support for rotating HDD's give a clue that the Linux world is not going to become wholly tied to using systemd in future?
Regarding the restarting I had read that if a process is started as a forking daemon rather than using the one shot approach, if it failed to start or stopped running then systemd would register this fact and automatically try to restart it until a successful result was achieved. This caters for strange glitches that might happen at boot for example. Manually restarting is a different situation. But that is only my understanding from reading the systemd documentation and I could well be wrong as I am quite new to using it. Thank you for clarifying this.

[Head_on_a_Stick]

Yes, I would have to agree with you in respect of readahead, that is unfortunate.

EDIT: Of course, there are third-party alternatives that can replace it.

[oswaldkelso]

I have recently read some quit balanced posts on systemd but noticed that folks are becoming more cautious.

Anyway this sort of drew my attention.

https://ma.ttias.be/whats-new-systemd-2015-edition/

TBH I'm not sure if he is manic, like on speed or something. Maybe just work over-loaded is ill or just on drugs. ?

Maybe I'm just a more relaxed kind of guy

Anyway. This is what raised a few eye-browses.

The next thing is auditing, You know that auditing is this thing that NSA requires if you want to sell something to the NSA. It is a mess, an absolute disaster if you ask me. It has so many security holes it makes your system more insecure when you run it. But auditing in theory actually has nice functionality

...... yadda yadda yadda listen to the rest your self


form the link

auditing: implemented for when your application needs to be NSA approved (that appeared to be the main reason, Lennart himself said he's not a big fan of it). Can log all system calls made to /etc/passwd etc to the audit log. Auditing is integrated with journald, audit-tools to read the logs have been improved.

From my on pov the fad with Docker and containers is scary " I will store my data on the cloud stuff" You know it's safe and trustworthy etc etc

[Head_on_a_Stick]

https://ma.ttias.be/whats-new-systemd-2015-edition/

That sounds amazing o.O

Between all that luverly new functionality and pacman's new hooks, it looks like I may be wiping one of my OpenBSD laptops and moving back to TuxLand.

How's that for irony?

[oswaldkelso]

Ah of course. Arch Linux. The placebo distro of choice.

Saying that, if your going to jump ship again, there are a few interesting Arch styled disrtos. Here's my personal favs where people still cling on desperately to the the original "Arch way" long after that ship has sailed. After such terrible puns I guess I should at least mention Parabola.

http://www.obarun.org/
http://systemd-free.org/

I shall eagerly await the screen-shots

[Head_on_a_Stick]

people still cling on desperately to the the original "Arch way" long after that ship has sailed

*raises eyebrow* Really?

If you maintain that the adoption of systemd by Arch was in some way not consistent with the Arch Way, I would disagree with you.

However, that would appear to be decidedly off-topic so I will leave it at that.

[obarun]

hello,

creator of obarun stuff here

having a choice is difficult for the moment on linux communities, one option is building a linux system from a scratch. But it can be very difficult, not to make it, but to maintain it in the time. Arch offer un very great tools to make what do you want or your system i think about pkgbuild, pacman, makepkg, repo-add... those are beautiful and easy tools to configurate a system.

desperate, not, happy yes because you know it's work and can be much easier rather than building it from scratch

[geekosupremo]

From my on pov the fad with Docker and containers is scary " I will store my data on the cloud stuff" You know it's safe and trustworthy etc etc

From where I stand (which is the noob's corner) the container "fad" is kind of exciting. Consider the rise of Vagrant (and other similar projects/products) it is designed to help devs and designers work on a common code base. Then once complete move that code base as a package to their production system. Since the app/project they're making is contained, it is easy to duplicate it or just the parts of it that need extra bandwidth.

I'm no expert but that sounds really cool.

This seems like it could make life more simple for those that do virus testing or even pen testing. I might also be useful for end users as it will help block off "risky" apps, see the Qubes project. Granted this idea would rely on the systemd being secure, which is yet to be fully proven, but the idea sounds really good.

[Head_on_a_Stick]

see the Qubes project. Granted this idea would rely on the systemd being secure, which is yet to be fully proven, but the idea sounds really good.

Strictly speaking, the security of the Qubes system is dependent on the (Xen) hypervisor

[geekosupremo]

Well put HoaS! To that end the Xen system is currently better tested, as far as I know.

[oswaldkelso]

HOAS you right needs a new thread

Maybe two

[Hralgmir]

I hadn't previously tried using systemd readahead but gave it a try on 25/1/16:
[code$ sudo systemctl enable --system systemd-readahead-collect.service systemd-readahead-replay.service][/code]
I didn't notice the boot getting faster but thought perhaps it needed more configuration for non SSD hardware and left it to see if it gathered more info by itself.
A few boots later, 27/1/16 - the desktop inexplicably started booting to the Gnome Shell version when it was previously the Gnome Flashback.
Disabling readahead returned normal operation:

Code: Select all

$ sudo systemctl disable --system systemd-readahead-collect.service systemd-readahead-replay.service

Strange! It wants to decide what desktop I should use
Gnome is pretty flaky on my hardware so whether this would affect anyone else I don't know.