systemd
zfs
systemd | zfs | |
---|---|---|
524 | 724 | |
12,714 | 10,253 | |
2.0% | 1.2% | |
10.0 | 9.7 | |
2 days ago | 3 days ago | |
C | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
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.
systemd
- Systemd v256
- systemd v256
-
Debian's /Tmpest in a Teapot
It isn't cleaned up at boot IIRC. Unless you leave your computer off for 30 days and then come back [1] :).
But it shouldn't be too hard to write a relativly simple systemd.unit file that does that at boot. After all the main part would be `Requires/After=local-fs.target` and something like `ExecStart=bash -c 'rm -rf /var/tmp/*'` I think (you'd need to double check what exactly to do if you want to do this).
[1] https://github.com/systemd/systemd/issues/33162
-
Ask HN: Who wants to be hired? (June 2024)
Email: v[at]vda.io
Hi HN! I'm a Linux security engineer looking for work on Open Source software. I've done some security work in the Linux Kernel (containerization primitives), in systemd as well as some work on Secure Boot.
Notably I've implemented auto-enrollment of secure boot keys in systemd. See (https://github.com/systemd/systemd/pull/20255 & https://lpc.events/event/16/contributions/1259/).
Lately, I've been very interested in MicroVMs and minimizing the Linux Kernel attack surface.
Message me if any of that sounds interesting!
- It's always TCP_NODELAY. Every damn time
- Dlopen() Metadata for ELF Files
-
PoC to demonstrate root permission hijacking by exploiting "systemd-run"
No, the OP was not sent any harassment, the OP _did_ the harassment as it can be seen in the tweets. I mean, they are right there, just click on the links you shared. One of the OP's followers even openly called for the assassination of the project maintainer, and you have the galls to defend him? This is truly deranged stuff.
And again, there is no "vulnerability", there is simply a person that doesn't know how Linux works and has learned something new. Which again it's fine, nobody knows everything and we all learn new things everyday, it's just that normal and sensible people don't use that to make grand claims on social media and start harassment campaigns culminating in death threats.
Professional security researchers responsibly report real issues using the appropriate channels, such as defined at: https://github.com/systemd/systemd/security/policy this is not the work of a researcher, this is a grifter looking for self-promotion on social media.
-
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
zfs
-
ZFS Resilver on SMR Drives
Thank You.
... and yes - this is the problem with 'dedicated' SPARE drives - they just sit there unused and You never know if they will work when the time comes.
ZFS resolved that with DRAID where there are not 'dedicated' SPARE disks but 'spare block' spread across the disks:
- https://github.com/openzfs/zfs/wiki/dRAID-HOWTO/001b44728e1a...
- Unsuitable SSD/NVMe Hardware for ZFS – WD Black SN770 and Others
- OpenZFS 2.2.4 – Linux and FreeBSD – Advanced file system and volume manager
-
Ubuntu 24.04 LTS is so buggy you can't install the OS [video]
Be careful if you use ZFS-on-root, make sure not to snapshot bpool or it will brick your system and require a complete reinstall.
https://github.com/openzfs/zfs/issues/13873
-
Radxa's SATA HAT makes compact Pi 5 NAS
> The only non-junk PCIe3 option that's even advertised here recently is the overpriced WD Red SN700.
Those WD drives seem to have some real issues, at least with ZFS and btrfs. :(
https://github.com/openzfs/zfs/discussions/14793
- OpenZFS: Fix corruption caused by MMAP flushing problems
- ZFS: Some copied files are still corrupted (chunks replaced by zeros)
-
DiskClick: Ever wanted to hear Old Hard drive sounds
IMO the "next fs" is just zfs. They somewhat recently merged RAIDZ expansion feature https://github.com/openzfs/zfs/pull/12225 and make regular improvements. If no file system has what you need today, zfs will probably be the first one to have it "tomorrow," imo.
- OpenZFS bug reports for native encryption
-
A data corruption bug in OpenZFS?
https://github.com/openzfs/zfs/issues/15526#issuecomment-181...
> zpool get all tank | grep bclone
> kc3000 bcloneused 442M
> kc3000 bclonesaved 1.42G
> kc3000 bcloneratio 4.30x
> My understanding is this: If the result is 0 for both bcloneused and bclonesaved then it's safe to say that you don't have silent corruption.
What are some alternatives?
openrc - The OpenRC init system
zstd - Zstandard - Fast real-time compression algorithm
tini - A tiny but valid `init` for containers
7-Zip-zstd - 7-Zip with support for Brotli, Fast-LZMA2, Lizard, LZ4, LZ5 and Zstandard
inotify-tools - inotify-tools is a C library and a set of command-line programs providing a simple interface to inotify.
sanoid - These are policy-driven snapshot management and replication tools which use OpenZFS for underlying next-gen storage. (Btrfs support plans are shelved unless and until btrfs becomes reliable.)
s6 - The s6 supervision suite.
RocksDB - A library that provides an embeddable, persistent key-value store for fast storage.
earlyoom - earlyoom - Early OOM Daemon for Linux
snapper - Manage filesystem snapshots and allow undo of system modifications
supervisor - Supervisor process control system for Unix (supervisord)
zfsbootmenu - ZFS Bootloader for root-on-ZFS systems with support for snapshots and native full disk encryption