overview for Unsafe

Which LaTeX editor do you use? by Unsafe in c/latex@programming.dev

[-] Unsafe@discuss.online 2 points 8 months ago

Nvim. autopair.nvim let's you autoclose "begin[]" macros. Luasnip let's you create custom snippets for every macro you use. I also use Emmet LSP for inline svg.

COSMIC: The Road to Alpha by Unsafe in c/linux@lemmy.ml

[-] Unsafe@discuss.online 1 points 9 months ago* (last edited 9 months ago)

Not really. Best Foss projects do not always thrive. Git wasn't really better than mercurial. But it had happened to be published earlier, so it got wider adoption.

Minimal OPDS server? by Unsafe in c/selfhosted@lemmy.world

[-] Unsafe@discuss.online 2 points 9 months ago* (last edited 9 months ago)

It doesn't support OPDS-PSE, which is the most common way of tracking progress.

Minimal OPDS server? by Unsafe in c/selfhosted@lemmy.world

[-] Unsafe@discuss.online 2 points 9 months ago

It actually has a ui. But it looks minimal enough. I'll try it.

What is your favourite selfhosted wiki software and why? by Unsafe in c/selfhosted@lemmy.world

[-] Unsafe@discuss.online 1 points 9 months ago

Gollum. Hit integration is required if you value wiki content.

Termius alternative ? by Unsafe in c/selfhosted@lemmy.world

[-] Unsafe@discuss.online 2 points 9 months ago* (last edited 9 months ago)

ConnectBot is fine.

30

Minimal OPDS server? (discuss.online)

submitted 9 months ago* (last edited 9 months ago) by Unsafe@discuss.online to c/selfhosted@lemmy.world

8 comments fedilink

No calibre database integration
No web ui
No desktop app
Just the server, that scans the specified directory for books, displays them in the feed and saves progress.

Oil is oil guys by Unsafe in c/memes@lemmy.ml

[-] Unsafe@discuss.online 7 points 10 months ago

Fight for Americans' fit bodies! Stop illegal oil production!

Systemd is far from being perfect by Unsafe in c/linux@lemmy.ml

[-] Unsafe@discuss.online 1 points 10 months ago

Wayland is like Busybox runit. Xorg is like SystemD.

Beachpatrol: A CLI tool to replace and automate your everyday web browser (Wayland support) by Unsafe in c/linux@lemmy.ml

[-] Unsafe@discuss.online 2 points 10 months ago* (last edited 10 months ago)

It's really cool, when automation tools create more problems than they actually solve.

Linux Containers From Scratch in C by Unsafe in c/linux@lemmy.ml

[-] Unsafe@discuss.online 1 points 10 months ago* (last edited 10 months ago)

There is really no reason to implement extensively audited runC in C, but the Dev only has the journey, no goals.

What's your favorite music player on Linux? by Unsafe in c/linux@lemmy.ml

[-] Unsafe@discuss.online 4 points 10 months ago

Ncmcpp, MPV with scripts

Systemd is far from being perfect by Unsafe in c/linux@lemmy.ml

[-] Unsafe@discuss.online 2 points 10 months ago

the added difficulties of making it system agnostic did not compensated for the low user base

2003: Udev was launched, providing support for musl, non-systemd distros, and others.
2004: NetworkManager was launched, with Udev as a crucial dependency.
2006: Dbus was created without dependencies on distro-specific packages.
2009: Dbus becomes a dependency for NetworkManager.
2010: Red Hat introduces systemd, with core components including logind, journald, and timers.
2012: Developers made udev less compatible with old kernels, musl-based, and non-systemd Linux distros by merging it with systemd. You can find more information about this here: https://lwn.net/Articles/490413, https://lwn.net/Articles/529314/
2017: PipeWire was launched, with logind as a dependency.
2017: Reimplementations of the bus protocol called dbus-broker were launched. Its compatibility launcher requires systemd.
2020: After systemd had already been adopted by all major distros, systemd-tmpfiles gained the ability to be built as a standalone executable.
2022: WirePlumber was launched, with pipewire as a hard dependency.

Looks like Red Hat makes everything they can systemd-dependent. Including Gnome.

-81

Systemd is far from being perfect (discuss.online)

submitted 10 months ago by Unsafe@discuss.online to c/linux@lemmy.ml

40 comments fedilink

Systemd-init has a larger attack surface compared to runit, openrc, or sysVinit.
Systemd-logind relies on systemd, so we need to adapt it for non-systemD distributions to ensure compatibility with certain applications like GNOME.
Udev also depends on systemd.
SystemD is specific to Linux, which makes porting software to *BSD even more challenging. It's uncertain what the future holds, and there may be circumstances where Linux becomes unusable for you (e.g., compatibility issues with your laptop). Having a good alternative that doesn't require relearning everything is generally beneficial.
SystemD-based distributions often come with more than just "systemd-init." They include additional components like logind, resolved, networkd, systemd-timers, etc. However, many people still prefer using the alternatives they were accustomed to before systemd became popular, such as dhcpcd and cron. Consequently, having both sets of tools installed can increase the attack surface.