- This topic has 84 replies, 1 voice, and was last updated 7 months, 2 weeks ago by
.
-
Posts
-
-
Welcome to systemd general, where we talk about systemd and all of its great features, ask questions and help eachother out with its usage
systemd components:
>systemd-boot; boot manager that deprecates GRUB
>systemd-homed; user accounts manager
>systemd-logind; login manager
>systemd-networkd; network manager that deprecates NetworkManager
>systemd-nspawn; namespace container
>systemd-resolved; network name resolution that deprecates openresolv and resolvconf
>systemd-sysusers; complements homed in managing user accounts
>systemd-timesync; network time sync daemon
>systemd/Journal; journaling daemon
>systemd/timers; scheduler that deprecates cronResources:
>http://0pointer.de/blog/projects/systemd-docs.html
>https://freedesktop.org/wiki/Software/systemd/
>https://en.wikipedia.org/wiki/Systemd
>https://wiki.gentoo.org/wiki/Systemd
>https://wiki.archlinux.org/title/SystemdFeel free to ask any questions related to systemd, its usage or any issues you are encountering and we’ll do our best to help you out
For non-systemd related help visit[…]
,
[…]
or
[…]
-
>>systemd-sysusers; complements homed in managing user accounts
woke af scrotebrain-
It’s not wrong
-
-
systemdeez NUTS haHAAAAAAAAAAAAAAAA
-
SystemD’s various network tools: so good that Red Hat Enterprise Linux rejected all of them and sticks to good old NetworkManager & co!
Maybe it’s better to let the experts in networking stick to writing network software, and Poettering can stick to his toys, eh?-
RHEL has already announced that they plan to deprecate NetworkManager & co by the systemd echo system. They will plan to push it to fedora first though
-
https://bugzilla.redhat.com/show_bug.cgi?id=1650342
Sounds like RHEL rejected NetworkD as the utter shit it is.-
>links to 3 years old issue
lol
https://bugzilla.redhat.com/show_bug.cgi?id=1789146
networkd is coming to fedora and later RHEL-
lol glowies played themselves
-
>optional components
Nice try Leonard
-
-
if you read it, there is a lot of truth in that networkmanager exists and works well within the domain that EL actually supports. In terms of networkd, EPEL now has it for 8.
-
-
-
Why not just use wicd? It wasn’t that long ago LULZ recommend it. I guess nuLULZ are coomers that got her last year.
-
-
glowscrote.com
-
不名誉なプログラムシステムディー CVE-2012-1174 Delete Any Files コンピューターが破壊された CVE-2015-7510, CVE-2018-15688 Arbitrary State Insertion 状態注入 CVE-2017-9217 Buffer Overflow バッファオーバーフロー CVE-2017-9445 systemd-resolvd Remote Code Execution プログラムをリモートで実行する CVE-2017-15908 Denial of Service サービス拒否 CVE-2017-1000082 0-Day (ゼロデイ) Root Exploit コンピュータを好きなように実行させます CVE-2018-15686 Root Privilege Elevation (10.0 Critical Exploit!!) ルートアカウントの不適切なアクセス CVE-2020-13776 Root Privilege Elevation Again 特権の昇格 CVE-2019-6454 Kernel Panic カーネルパニック CVE-2020-1712 Arbitrary Code Execution 任意のコードの実行 CVE-2021-33910 Stack Exhaustion スタックのスペースが不足しました CVE-2021-40084 Denial of Service サービス拒否攻撃
-
This is the funniest freaking shit I’ve seen so far this week
-
Woke af.
-
kek
-
Get those moon runes off the board.
-
never stop posting
-
woke af
-
-
>poettpoettpoettpoettpoettpoett
-
systemd chad, is there a nixos way of describing udev rules or do I have to write to ${whatever}/lib/rules.d/
and yes, systemd-udevd is systemd so it’s on topic.
-
never described udev rules in nixos, but i guess that’s what you need
https://github.com/NixOS/nixpkgs/blob/8284fc30c84ea47e63209d1a892aca1dfcd6bdf3/nixos/modules/services/hardware/udev.nix-
>services.udev
ok, I feel like a scrotebrain for not even thinking of looking.
-
>extraRules = mkOption
>type = types.lines;We have all these rich object configs to do like object to ini, but we can’t have that for udev? I’ll just write my own I guess.
-
-
-
[…]
-
coming up next
>systemd-memoryd Memory allocator
>systemd-replicant Data replication, replaces RAID
>systemd-remoteaccess Replaces SSH
>systemd-blockd Replaces kernel block device drivers
>systemd-tedit Text editor
>systemd-vaxpass Manages health certificates
>systemd-greenpass Meters your electricity, water and meat consumption
>systemd-buttplug Unified audio system-
>>systemd-remoteaccess Replaces SSH
We already have remote PID1 https://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=2d1ca11270e66777c90a449096203afebc37ec9c#n1500-
holy fuck the nsa malware memes were true
-
This uses ssh. You are a scrote.
-
This. Anti-systemd schizos are pooping up the board
-
-
-
>systemd-ntd; NT subsystem for Linux
-
>systemd-systemd Distribution as a package (DaaP)
-
literally systemd-portabled
-
-
>systemd-showerd
-
-
Thanks, but I’m staying with Void.
-
You should migrate you a systemd distro friend, you will see how much better it is than other init systems.
-
Thanks, but I’m sticking with Upstart 🙂
-
Upstart is abandonware
systemd is has very active development, and plenty of features-
Upstart runs on every ChromeBook out there. It’s reached a good stable status, and doesn’t need to expand like systemd does, because Upstart is a lightweight event-woke af system which doesn’t need to do anything other than deal with services – you can plug in other event sources via its interfaces.
So if by ‘abandonware’ you mean "proven to work well on hundreds of millions of computers and continuing to work great to this day" then why would I want to run anything else?-
>"proven to work well on hundreds of millions of computers and continuing to work great to this day"
You mean "barely good enough to launch an instance of Chromium"?-
Yeah – like how systemd is barely good enough to launch GDM.
-
works on my machine
-
Upstart works on my ChromeBook
Listen sweetie, wait till you learn that A) there are many other services running on a ChromeBook, and many event sources which Upstart coordinates, and B) the web browser you’re writing from is also practically its own process manager.
Now cope, advocate of a glorified Chromium bootloader – after all, you spend most of your day in a web browser too.-
Reddit typed this post
-
Systemd is pure redditry. Just look at how /r/linux white-knights for systemd the moment someone criticises it. It’s like criticising a freaking Marvel superhero there,
-
>Just look at how /r/
stopped reading right there
go back to r*ddit and shill your abandoned init system over there scrote -
Cope cope cope you devious little systemd-shilling creature
-
There’s nothing to cope about
systemd works perfectly well and has all the features I want and more
what would I cope about? -
The lack of a downvote button has given you the illusion that here you are surrounded by like minded individuals.
-
-
-
Except GDM isn’t what manages the user’s other processes. That’s done by systemd, because systemd happens to be good at managing processes. Meanwhile Chromium is practically its own process manager. Now cope, advocate of a glorified Chromium bootloader.
-
-
-
-
-
-
>You should try this weed
>It’s safe, it won’t fuck up your brain
>Bro, just trust me, it’s safe
no, thank you-
trust me, install systemd, you won’t regret it
-
I don’t want no systemd on my machine.
-
-
-
-
Void is such a good linux distro
-
It would be even better if it had systemd.
-
-
Woke af
-
-
I like systemd because the boot process is very fast and it makes it very easy to manage services and choose which ones start on boot.
-
systemd has nice autocomplete.
systemctl ""
journalctl "" -
Looks cute. Is there any production-ready implementation of the SystemD suite or is it still Lenny’s toy project? Last time I tried it two months ago it sucked ass.
-
Sure anon, the latest version of Debian comes with systemd
Most desktop distributions include it out of the box as well.-
>Sure anon, the latest version of Debian comes with systemd
I have used Debian and several derivatives for fifteen consecutive years so far. It worked pretty good until they started adding systemd dependencies everywhere. I thought it was just teething issues so I tolerated them and reinstalled again and again until it became untolerable. Then I cut it some slack and thought it just was because it wasn’t the reference implementation of the SystemD operating system, so I tried CentOS and Fedora, but no luck. It’s still dogshit and I won’t pay for RHEL. The reference implementation is borken, I can’t afford the time to distrohop for a secondary implementation that manages to fix the borken defaults, and if I am going to pay for shit proprietary software I might as well use Windows.What a pity. I’ll stay on BSDland while SystemD blows over and the Linux kernel community finds a new operating system to distribute it. See you when Linux gets stable again I guess.
-
-
-
systemd maintenance guide:
1) delete sysemd-
>delete sysemd
>computer doesn’t boot anymore
That is, sadly, a very common experience on distros such as void or gentoo where systemd is simply missing and was replaced by amateur software-
>replace systemd with amateur software
Nothing of value would be lost-
Thanks, but I prefer my init system to be done by professionals.
-
Lennart is not a professional. If you want a professional init system, look to SMF.
Example of proper code documentation:
https://github.com/joyent/illumos-joyent/blob/master/usr/src/cmd/svc/startd/graph.c#L31Notice how code is explained throughout with illustrative comments. There are extensive error-checks. Meanwhile in systemd you have a lmao shitheap of uncommented cryptic code.
-
>Lennart is not a professional.
Lennart is a professional. He has decades of experience in programming advanced Linux related software (Avahi and Pulseaudio are two easy examples).
Not only that, but Lennart is not the sole developer of systemd. In fact, systemd is backed by multiple multi-billion dollar corporations, such as Red Hat, SUSE and others.-
He is not a professional, he is a bumbling amateur who doesn’t understand the importance of good software architecture and can’t even comment his code.
-
He is professional playing amateur.
-
-
-
Port SMF to Linux? Or is CDDL in the way?
-
-
>I prefer my init system to be done by professionals.
Then why are you using systemd?
-
-
-
-
-
also red hat shills FUCK OFF
-
systemd doesn’t deprecate any of the programs you claim it does. It provides lightweight alternatives.
-
Nothing stops you from using old, legacy software, but that doesn’t mean it’s not deprecated and hasn’t been replaced by something new, modern and faster.
-
-
More like systemPP
give me init or give me death -
>systemd components:
>systemd-boot; boot manager that deprecates GRUB
>systemd-homed; user accounts manager
>systemd-logind; login manager
>systemd-networkd; network manager that deprecates NetworkManager
>systemd-nspawn; namespace container
>systemd-resolved; network name resolution that deprecates openresolv and resolvconf
>systemd-sysusers; complements homed in managing user accounts
>systemd-timesync; network time sync daemon
>systemd/Journal; journaling daemon
>systemd/timers; scheduler that deprecates cron
how the fuck did this happen -
Why the fuck can’t a single distro agree on a canonical list of folders for placing user and system services files? In Mac OS X we have two spots: /Library/LaunchAgents and ~/Library/LaunchAgents. It’s pretty easy to tell which is system and user specific. Moreover, you can drop a plist pretty much wherever you want and enable it with launchctl, justify its full path. Meanwhile Debian and Arch have completely different approaches to installing services, and on top of that, the systemd manpage doesn’t make clear at all what directories are candidates for searching. Also, for some reason, systemd on my end doesn’t always load services I list as required in a given services. Yet manually invoking start on them will result in successes, so I know the services aren’t dying midway.
-
Why can’t proprietary systems like Windows and macOS agree with each other? On free software systems we all use systemd and Gnome
-
Actually, service supervision has been pretty stable and consistent on Windows NT since pretty much its existence. Moreover, OS X switched to launchd to overcome deficiencies in the usual BSD daemons like cron, inetd, and so on. It makes sense they disagree on some details because they have completely different kernels. What excuse do Linux distros using systemd have? Why must Arch insist on /etc/systemd/system but Debian wants you placing it elsewhere? This even violates the FHS, since /etc is not supposed to contain scripts that run executable files. Of course, nobody in Linux cares about FHS. That’s why the file heirarchy in Linux distros are all scattered compared to Illumos, BSD, and even freaking OS X.
-
-
>In Mac OS X we have two spots
I’m pretty sure if there were 50 different distributions of MacOS, there would be more than two spots
-
-
systemd is honestly easier to work with than any of the older init systems I have used. The one on openwrt is okay to but I’ve never had to write or configure anything.
-
bump
-
how many millions of lines now? 15?
-
fuck RedShat and fuck systemd
-
- You must be logged in to reply to this topic.