Oh okay, are you referring to the Amazon link in the description? That link is a generic affiliate link that just redirects to "laptop" but gives him a comission when someone buys something on Amazon after, it's not a specific product he sells on there.
It didn't happen in the US though, so I'm not sure why that's relevant.
I'm sorry, but what are you referring to?
It's also a lot easier to do so with Rust because you can easily statically compile it with the musl target so you don't even rely on the system's libc version.
Of course not, but then there's not really a point to using another Pi instead of your main machine, right?
The Raspberry Pi Zero has a 32-bit CPU, the newer big RPI's have 64-bit CPU's. Wouldn't that cause problems?
Interesting. Is that because the kernel can't load a a module as dylib (I don't know a lot about kernel development) or because dylibs are also somehow statically linked in Rust?
Numeric .xyz domains only cost $1 a year. They're not great for things like mail because they're often used by spammers (probably because of the price), but it's great for cheap signed DNS hostnames.
I point it to the server on my local network and use Wireguard to connect myself.
I must say, being able to create, build, and bootstrap your kernel and run it in a VM with 3 commands is pretty cool.
Our choice of the weak-copyleft MPL license reflects a strategic balance:
Commitment to open-source freedom: We believe that OS kernels are a communal asset that should benefit humanity. The MPL ensures that any alterations to MPL-covered files remain open source, aligning with our vision. Additionally, we do not require contributors to sign a Contributor License Agreement (CLA), preserving their rights and preventing the possibility of their contributions being made closed source.
Accommodating proprietary modules: Recognizing the evolving landscape where large corporations also contribute significantly to open-source, we accommodate the business need for proprietary kernel modules. Unlike GPL, the MPL permits the linking of MPL-covered files with proprietary code.
Wouldn't the LGPL also allow this?
Just take the string as bytes and hash it ffs
I'm planning on building a new home server and was thinking about the possibility to use disc spanning to create matching disk sizes for a RAID array. I have 2x2TB drives and 4x4TB drives.
Comparison with RAID 5
4 x 4 TB drives
- 1 RAID array
- 12 TB total
4 x 4 TB drives & 2 x 2 TB drives
- 2 RAID arrays
- 14 TB total
5 x 4* TB drives
- Several 4TB disks and 2 smaller disks spanned to produce a 4 TB block device
- 16 TB total
I'm not actually planning on actually doing this because this setup will probably have all kinds of problems, however I do wonder, what would those problems be?
I noticed that I only had 5 GiB of free space left today. After quickly deleting some cached files, I tried to figure out what was causing this, but a lot was missing. Every tool gives a different amount of remaining storage space. System Monitor says I'm using 892.2 GiB/2.8 TiB (I don't even have 2.8 TiB of storage though???). Filelight shows 32.4 GiB in total when scanning root, but 594.9 GiB when scanning my home folder.
Meanwhile, ncdu (another tool to view disk usage) shows 2.1 TiB with an apparent size of 130 TiB of disk space!
1.3 TiB [#############################################] /.snapshots
578.8 GiB [#################### ] /home
204.0 GiB [####### ] /var
42.5 GiB [# ] /usr
14.1 GiB [ ] /nix
1.3 GiB [ ] /opt
. 434.6 MiB [ ] /tmp
350.4 MiB [ ] /boot
80.8 MiB [ ] /root
23.3 MiB [ ] /etc
. 5.5 MiB [ ] /run
88.0 KiB [ ] /dev
@ 4.0 KiB [ ] lib64
@ 4.0 KiB [ ] sbin
@ 4.0 KiB [ ] lib
@ 4.0 KiB [ ] bin
. 0.0 B [ ] /proc
0.0 B [ ] /sys
0.0 B [ ] /srv
0.0 B [ ] /mnt
I assume the /.snapshots folder isn't really that big, and it's just counting it wrong. However, I'm wondering whether this could cause issues with other programs thinking they don't have enough storage space. Steam also seems to follow the inflated amount and refuses to install any games.
I haven't encountered this issue before, I still had about 100 GiB of free space last time I booted my system. Does anyone know what could cause this issue and how to resolve it?
EDIT 2024-04-06:
snapper ls only shows 12 snapshots, 10 of them taken in the past 2 days before and after zypper transactions. There aren't any older snapshots, so I assume they get cleaned up automatically. It seems like snapshots aren't the culprit.
I also ran btrfs balance start --full-balance --bg / and that netted me an additional 30 GiB's of free space, and it's only at 25% yet.
EDIT 2024-04-07: It seems like Docker is the problem.
I ran the docker system prune command and it reclaimed 167 GB!
view more: next ›
They probably don't have enough training data yet