#systemd — Public Fediverse posts

Init vs SystemD

This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.

From my perspective the author seems to have forgotten one important thing.

He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.

The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.

Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.

The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL

Never compare systemD with Init!

Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.

You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is needed

You should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.

Stop bitching about which system is better.

They are totally different.

Live with one of them or write your own

Init is Open Source
systemD is Open Source

Use the power, choose or fork your favourite

Sources:

https://en.wikipedia.org/wiki/Systemd

https://en.wikipedia.org/wiki/Init

https://linuxtldr.com/init-vs-systemd/

#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang

Init vs SystemD

This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.

From my perspective the author seems to have forgotten one important thing.

He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.

The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.

Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.

The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL

Never compare systemD with Init!

Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.

You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is needed

You should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.

Stop bitching about which system is better.

They are totally different.

Live with one of them or write your own

Init is Open Source
systemD is Open Source

Use the power, choose or fork your favourite

Sources:

https://en.wikipedia.org/wiki/Systemd

https://en.wikipedia.org/wiki/Init

https://linuxtldr.com/init-vs-systemd/

#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang

Init vs SystemD

This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.

From my perspective the author seems to have forgotten one important thing.

He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.

The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.

Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.

The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL

Never compare systemD with Init!

Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.

You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is needed

You should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.

Stop bitching about which system is better.

They are totally different.

Live with one of them or write your own

Init is Open Source
systemD is Open Source

Use the power, choose or fork your favourite

Sources:

https://en.wikipedia.org/wiki/Systemd

https://en.wikipedia.org/wiki/Init

https://linuxtldr.com/init-vs-systemd/

#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang

Init vs SystemD

This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.

From my perspective the author seems to have forgotten one important thing.

He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.

The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.

Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.

The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL

Never compare systemD with Init!

Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.

You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is needed

You should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.

Stop bitching about which system is better.

They are totally different.

Live with one of them or write your own

Init is Open Source
systemD is Open Source

Use the power, choose or fork your favourite

Sources:

https://en.wikipedia.org/wiki/Systemd

https://en.wikipedia.org/wiki/Init

https://linuxtldr.com/init-vs-systemd/

#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang

Init vs SystemD

This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.

From my perspective the author seems to have forgotten one important thing.

He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.

The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.

Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.

The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL

Never compare systemD with Init!

Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.

You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is needed

You should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.

Stop bitching about which system is better.

They are totally different.

Live with one of them or write your own

Init is Open Source
systemD is Open Source

Use the power, choose or fork your favourite

Sources:

https://en.wikipedia.org/wiki/Systemd

https://en.wikipedia.org/wiki/Init

https://linuxtldr.com/init-vs-systemd/

#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang

Nearly overwrote my obsidian vault today. So to solve that from ever being a problem -- I wrote a bash script to create an encrypted tarball of my vault, and included a systemd process to trigger it on boot.

#linux #systemd #bash #obsidian #tar #backup #security

automatisches #Backup von /home über den #systemd

https://raspithek.de/software/betriebsystem/automatisches-home-backup-ueber-systemd/

automatisches #Backup von /home über den #systemd

https://raspithek.de/software/betriebsystem/automatisches-home-backup-ueber-systemd/

automatisches #Backup von /home über den #systemd

https://raspithek.de/software/betriebsystem/automatisches-home-backup-ueber-systemd/

automatisches #Backup von /home über den #systemd

https://raspithek.de/software/betriebsystem/automatisches-home-backup-ueber-systemd/

Testing #bodem - #GopherProtocol server written in #Rust

* gopher://phlogqhspsjzcdubodidwc74pmc56hik2t3bhajwc47rg6snboia.b32.i2p:70 - #I2P
* gopher://[202:68d0:f0d5:b88d:1d1a:555e:2f6b:3148]:70 - #Yggdrasil
* gopher://[505:6847:c778:61a1:5c6d:e802:d291:8191]:70 - #Mycelium

Some note about how to setup this server in multi-net environment using separated #systemd services (Ukr):
http://[202:68d0:f0d5:b88d:1d1a:555e:2f6b:3148]/d/249

P.S. take a look at PR as last official commit is 6-years old

Testing #bodem - #GopherProtocol server written in #Rust

* gopher://phlogqhspsjzcdubodidwc74pmc56hik2t3bhajwc47rg6snboia.b32.i2p:70 - #I2P
* gopher://[202:68d0:f0d5:b88d:1d1a:555e:2f6b:3148]:70 - #Yggdrasil
* gopher://[505:6847:c778:61a1:5c6d:e802:d291:8191]:70 - #Mycelium

Some note about how to setup this server in multi-net environment using separated #systemd services (Ukr):
http://[202:68d0:f0d5:b88d:1d1a:555e:2f6b:3148]/d/249

P.S. take a look at PR as last official commit is 6-years old

Testing #bodem - #GopherProtocol server written in #Rust

* gopher://phlogqhspsjzcdubodidwc74pmc56hik2t3bhajwc47rg6snboia.b32.i2p:70 - #I2P
* gopher://[202:68d0:f0d5:b88d:1d1a:555e:2f6b:3148]:70 - #Yggdrasil
* gopher://[505:6847:c778:61a1:5c6d:e802:d291:8191]:70 - #Mycelium

Some note about how to setup this server in multi-net environment using separated #systemd services (Ukr):
http://[202:68d0:f0d5:b88d:1d1a:555e:2f6b:3148]/d/249

P.S. take a look at PR as last official commit is 6-years old

For those who use #Forgejo binaries, this is how I upgrade completely in 1 go.

https://blog.bakhai.co.in/post/upgrade-forgejo

#forgejo #upgrade #systemd

For those who use #Forgejo binaries, this is how I upgrade completely in 1 go.

https://blog.bakhai.co.in/post/upgrade-forgejo

#forgejo #upgrade #systemd

For those who use #Forgejo binaries, this is how I upgrade completely in 1 go.

https://blog.bakhai.co.in/post/upgrade-forgejo

#forgejo #upgrade #systemd

For those who use #Forgejo binaries, this is how I upgrade completely in 1 go.

https://blog.bakhai.co.in/post/upgrade-forgejo

#forgejo #upgrade #systemd

Kleiner Nachmittagstipp: `journalctl -p err -b` zeigt euch alle Fehler seit dem letzten Boot. Spart das wilde Scrollen durch endlose Logs und ist Gold wert, wenn mal wieder „irgendwas“ nicht funktioniert. ☕

Bonus: Mit `--since "1 hour ago"` schränkt ihr's zeitlich ein. Systemd kann ja nerven, aber journalctl gehört zu den Dingen, die ich nicht mehr missen möchte.

#Linux #systemd #FreieSoftware #Terminal

Kleiner Nachmittagstipp: `journalctl -p err -b` zeigt euch alle Fehler seit dem letzten Boot. Spart das wilde Scrollen durch endlose Logs und ist Gold wert, wenn mal wieder „irgendwas“ nicht funktioniert. ☕

Bonus: Mit `--since "1 hour ago"` schränkt ihr's zeitlich ein. Systemd kann ja nerven, aber journalctl gehört zu den Dingen, die ich nicht mehr missen möchte.

#Linux #systemd #FreieSoftware #Terminal

Kleiner Nachmittagstipp: `journalctl -p err -b` zeigt euch alle Fehler seit dem letzten Boot. Spart das wilde Scrollen durch endlose Logs und ist Gold wert, wenn mal wieder „irgendwas“ nicht funktioniert. ☕

Bonus: Mit `--since "1 hour ago"` schränkt ihr's zeitlich ein. Systemd kann ja nerven, aber journalctl gehört zu den Dingen, die ich nicht mehr missen möchte.

#Linux #systemd #FreieSoftware #Terminal

Kleiner Nachmittagstipp: `journalctl -p err -b` zeigt euch alle Fehler seit dem letzten Boot. Spart das wilde Scrollen durch endlose Logs und ist Gold wert, wenn mal wieder „irgendwas“ nicht funktioniert. ☕

Bonus: Mit `--since "1 hour ago"` schränkt ihr's zeitlich ein. Systemd kann ja nerven, aber journalctl gehört zu den Dingen, die ich nicht mehr missen möchte.

#Linux #systemd #FreieSoftware #Terminal

Kleiner Nachmittagstipp: `journalctl -p err -b` zeigt euch alle Fehler seit dem letzten Boot. Spart das wilde Scrollen durch endlose Logs und ist Gold wert, wenn mal wieder „irgendwas“ nicht funktioniert. ☕

Bonus: Mit `--since "1 hour ago"` schränkt ihr's zeitlich ein. Systemd kann ja nerven, aber journalctl gehört zu den Dingen, die ich nicht mehr missen möchte.

#Linux #systemd #FreieSoftware #Terminal

Lennart #Poettering hat mir den vergangenen #DigitalIndependenceDay unnötig schwer gemacht:

https://www.iromeister.de/digital-independence-day-mit-hindernissen/

#didit #diday #did_dut #systemd

Lennart #Poettering hat mir den vergangenen #DigitalIndependenceDay unnötig schwer gemacht:

https://www.iromeister.de/digital-independence-day-mit-hindernissen/

#didit #diday #did_dut #systemd

Seriously considering moving to a BSD as I watch Linux fall more and more to corporate influence.

#ageverification #systemd #redhat #ibm #linux #bsd #linuxfoundation

Seriously considering moving to a BSD as I watch Linux fall more and more to corporate influence.

#ageverification #systemd #redhat #ibm #linux #bsd #linuxfoundation

Seriously considering moving to a BSD as I watch Linux fall more and more to corporate influence.

#ageverification #systemd #redhat #ibm #linux #bsd #linuxfoundation

Seriously considering moving to a BSD as I watch Linux fall more and more to corporate influence.

#ageverification #systemd #redhat #ibm #linux #bsd #linuxfoundation

Seriously considering moving to a BSD as I watch Linux fall more and more to corporate influence.

#ageverification #systemd #redhat #ibm #linux #bsd #linuxfoundation

#systemd #gnu #linux

#systemd #gnu #linux

#systemd #gnu #linux

#systemd #gnu #linux

#systemd #gnu #linux

@ndreas once Podman/Docker add the corresponding support, this will work just fine, running containers inside nspawn:
https://github.com/systemd/systemd/blob/main/NEWS#L4573-L4599

#systemd #nspawn #docker #podman

@ndreas once Podman/Docker add the corresponding support, this will work just fine, running containers inside nspawn:
https://github.com/systemd/systemd/blob/main/NEWS#L4573-L4599

#systemd #nspawn #docker #podman

@ndreas once Podman/Docker add the corresponding support, this will work just fine, running containers inside nspawn:
https://github.com/systemd/systemd/blob/main/NEWS#L4573-L4599

#systemd #nspawn #docker #podman

@ndreas once Podman/Docker add the corresponding support, this will work just fine, running containers inside nspawn:
https://github.com/systemd/systemd/blob/main/NEWS#L4573-L4599

#systemd #nspawn #docker #podman

@ndreas once Podman/Docker add the corresponding support, this will work just fine, running containers inside nspawn:
https://github.com/systemd/systemd/blob/main/NEWS#L4573-L4599

#systemd #nspawn #docker #podman

@rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.

@rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.

@rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.

@rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.

@rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.

Oh... #systemd wird jetzt auch noch zum #docker oder #podman Ersatz... wer hätt's gedacht?!

Oh... #systemd wird jetzt auch noch zum #docker oder #podman Ersatz... wer hätt's gedacht?!

Oh... #systemd wird jetzt auch noch zum #docker oder #podman Ersatz... wer hätt's gedacht?!

Oh... #systemd wird jetzt auch noch zum #docker oder #podman Ersatz... wer hätt's gedacht?!

Oh... #systemd wird jetzt auch noch zum #docker oder #podman Ersatz... wer hätt's gedacht?!

Hmmm I hadn't seen
> systemd-analyze blame
and
> systemd-analyze critical-chain
before. Potentially useful for improving startup times on modern Linux systems ...
https://www.makeuseof.com/i-turned-off-one-background-service-and-my-linux-machine-finally-felt-fast
#linux #systemd