void-packages
systemd
void-packages | systemd | |
---|---|---|
671 | 517 | |
2,378 | 12,457 | |
1.1% | 1.2% | |
10.0 | 10.0 | |
1 day ago | 7 days ago | |
Shell | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
void-packages
-
Damn Small Linux 2024
I was looking for a lightweight OS to run on old Asus Eee PC 1005 HA, which uses a 32-bit Intel Atom N270 processor. I installed Void Linux (https://voidlinux.org/).
I may give DSL 2024 a try and see how it compares.
- Chimera Linux
-
When are we ditching systemd?
Linux Void
- Une nouvelle mise à jour de Systemd permettra à Linux de bénéficier de l'infâme "écran bleu de la mort" de Windows, mais la fonctionnalité a reçu un accueil très mitigé
-
How do I update one of these premade ESP32 boards?
My computer is running Void Linux and it has only a wired network connection. I can hook up my phone for USB tethering if I need to connect to the WiFi of the ESP32. How do I update the software without downloading some shady programs from filesharing site links on my system? I have the Arduino IDE and the esptool.py script installed.
- Linuxi kasutaja, mis distrot kodus kasutad ja millest see valik?
- I want to be a packager
-
Hyphens, minus, and dashes in Debian man pages
Classic "everyone is using the software wrong, but it's the fault of everyone, and not the software".
Some distros like Void seem to patch this out.[1]
From mandoc/mdocml's mandoc_char(7) [2]
In roff(7) documents, the minus sign is normally written as ‘\-’. In manual pages, some style guides recommend to also use ‘\-’ if an ASCII 0x2d “hyphen-minus” output glyph that can be copied and pasted is desired in output modes supporting it, for example in -T utf8 and -T html. But currently, no practically relevant manual page formatter requires that subtlety, so in manual pages, it is sufficient to write plain ‘-’ to represent hyphen, minus, and hyphen-minus.
Which is the common-sense thing to do.
Meanwhile, GNU projects become increasingly less relevant due to obnoxiousness like this.
In general the amount of wankery of "the correct hyphen" is staggering.
[1]: https://man.openbsd.org/mandoc_char
[2]: https://github.com/void-linux/void-packages/blob/20c66829134...
-
Thoughts on Void Linux?
So I was about to configure a new Archlinux build on my PC and came across Void Linux. I had already read about it a year ago but never researched it in depth. I know that is a Linux distribution made from scratch, with a different package manager and so on. Void Linux users or people who have tried it, what are your thoughts on it? Do you think the PM is easy to use? what about updates and bugs? what desktop or Tilling Window Manager do you use? could you tell me about it?
-
Question about python venv
Good news about dbus-next: https://github.com/void-linux/void-packages/pull/46760
systemd
-
Run0 – systemd based alternative to sudo announced
> 3. even `adduser` will not allow it by default
5. useradd does allow it (as noted in a comment). 6. Local users are not the only source, there things like LDAP and AD.
7. POSIX allows it:
* https://github.com/systemd/systemd/issues/6237#issuecomment-...
-
Systemd Rolling Out "run0" As sudo Alternative
> I for one love to type out 13 extra characters
FWIW, systemd is normally pretty good at providing autocomplete suggestions, so even if you don't want to set up an alias you'll probably just have to type `--b ` to set it.
> I wonder what random ASCII escape sequences we can send.
According to the man page source[0]:
> The color specified should be an ANSI X3.64 SGR background color, i.e. strings such as `40`, `41`, …, `47`, `48;2;…`, `48;5;…`
and a link to the relevant Wikipedia page[1]. Given systemd's generally decent track record wrt defects and security issues, and the simplicity of valid colour values, I expect there's a fairly robust parameter verifier in there.
In fact, given the focus on starting the elevated command in a highly controlled environment, I'd expect the colour codes to be output to the originating terminal, not forwarded to the secure pty. That way, the only thing malformed escapes can affect is your own process, which you already have full control over anyway.
(Happy to be shown if that's a mistaken expectation though.)
[0] https://github.com/systemd/systemd/blob/main/man/run0.xml
[1] https://en.wikipedia.org/wiki/ANSI_escape_code#SGR_(Select_G...
- Crash-only software: More than meets the eye
-
Systemd Wants to Expand to Include a Sudo Replacement
bash & zsh are supported by upstream: https://github.com/systemd/systemd/tree/main/shell-completio...
-
"Run0" as a Sudo Replacement
the right person to replace sudo, not: https://github.com/systemd/systemd/issues/6237
PS: https://pwnies.com/systemd-bugs/
-
Linux fu: getting started with systemd
https://github.com/systemd/systemd/issues/32028#issuecomment...
There are some very compelling arguments made there if you care to read them
-
Ubuntu 24.04 (and Debian) removed libsystemd from SSH server dependencies
Maybe it was because you weren't pointing out anything new?
There was a pull request to stop linking libzma to systemd before the attack even took place
https://github.com/systemd/systemd/pull/31550
This was likely one of many things that pushed the attackers to work faster, and forced them into making mistakes.
-
Systemd minimizing required dependencies for libsystemd
The PR for changing compression libraries to use dlopen() was opened several weeks before the xz-utils backdoor was revealed.
https://github.com/systemd/systemd/pull/31550
- Going in circles without a real-time clock
-
The xz sshd backdoor rabbithole goes quite a bit deeper
I find this the most plausible explanation by far:
* The highly professional outfit simply did not see teknoraver's commit to remove liblzma as standard dependency of systemd build scripts coming.
* The race was on between their compromised code and that commit. They had to win it, with as large a window as possible.
* This caused serious errors.
* The performance regression is __not__ big. It's lucky Andres caught it at all. It's also not necessarily all that simple to remove it. It's not simply a bug in a loop or some such.
* The payload of the 'hack' contains fairly easy ways for the xz hackers to update the payload. They actually used it to remove a real issue where their hackery causes issues with valgrind that might lead to discovering it, and they also used it to release 5.6.1 which rewrites significant chunks; I've as yet not read, nor know of any analysis, as to why they changed so much.
Extra info for those who don't know:
https://github.com/systemd/systemd/commit/3fc72d54132151c131...
That's a commit that changes how liblzma is a dependency of systemd. Not because the author of this commit knew anything was wrong with it. But, pretty much entirely by accident (although removing deps was part of the point of that commit), almost entirely eliminates the value of all those 2 years of hard work.
And that was with the finish line in sight for the xz hackers: On 24 feb 2024, the xz hackers release liblzma 5.6.0 which is the first fully operational compromised version. __12 days later systemd merges a commit that means it won't work__.
So now the race is on. Can they get 5.6.0 integrated into stable releases of major OSes _before_ teknoraver's commit that removes liblzma's status as direct dep of systemd?
I find it plausible that they knew about teknoraver's commit _just before_ Feb 24th 2024 (when liblzma v5.6.0 was released, the first backdoored release), and rushed to release ASAP, before doing the testing you describe. Buoyed by their efforts to add ways to update the payload which they indeed used - March 8th (after teknoraver's commit was accepted) it was used to fix the valgrind issue.
So, no, I don't find this weird, and I don't think the amateurish aspects should be taken as some sort of indication that parts of the outfit were amateuristic. As long as it's plausible that the amateuristic aspects were simply due to time pressure, it sounds like a really bad idea to make assumptions in this regard.
What are some alternatives?
AppImageLauncher - Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages
openrc - The OpenRC init system
ungoogled-chromium - Google Chromium, sans integration with Google
tini - A tiny but valid `init` for containers
gentoo - Official Gentoo ebuild repository
inotify-tools - inotify-tools is a C library and a set of command-line programs providing a simple interface to inotify.
nix - Nix, the purely functional package manager
s6 - The s6 supervision suite.
sway - i3-compatible Wayland compositor
earlyoom - earlyoom - Early OOM Daemon for Linux
xdeb - XDEB - Convert deb (Debian) packages to xbps (Void Linux)
supervisor - Supervisor process control system for Unix (supervisord)