Greg Harvey 🌍That thing when a string of events collide to create an emergency. Always a head-scratcher. Luckily we were a team of three figuring it out, between us we got their quite quickly. If anyone has any ideas or has seen similar behaviour from #NGINX / #FUSE I'd love to hear from you:
https://gregharvey.gitlab.io/blog/posts/2026-06/multi-bug-headaches/
Dendrobatus AzureusThere was one annoying problem that I wanted to solve myself while playing with the MXLinux live installer.
There are various good reasons why the SquashFS is used.
I got odd error messages after a while with that file system, as it resided on a USB stick, which has of course its own file system which is not EXT4. The reason why explicitly state that is EXT4 is robust when it comes down to unclosed file systems / unfinished journaling writes, when your Computing system crashes for whatever reasons.
Extended Four just rolls back and then your file system is intact
The file system which is on the USB stick does not roll back when it is unmounted uncleanly.
It's the latter that damaged the ISO, in which of course the squash file system resides. The reason why the squash file system errors picked up later is because the files that I needed which were in the damage part of the ISO, only were accessed hours later after the initial boot
I got an interesting chicken egg situation, where I wanted to copy a new intact version of the ISO to the USB stick but was refused access to it by MX Linux Live.
For a reason still unclear to me I didn't think about booting from one of the other ISOs that I have there, which are tiny and also reside on the same USB stick.
Yesterday I had the logical idea to boot from one of those other ISOs.
That one is designed in a much friendlier manner, you are still allowed to access the boot USB stick. Then it was a matter of copying another version of the MX Linux ISO from another USB stick to the one where I boot from. This time I left the errored version of the ISO on the stick so that the fresh version was written to another area of the target USB stick, which obviously has file system errors that I cannot fix until it's totally unmounted. For that I need another stick which is not in the building.
The other ISO I used is Slitaz, a tiny Linux distribution which can reside totally in RAM
datenwolfAll I want is just a collection of #binutils, #GCC, #llvm+#clang, #glibc and #musl that are "free standing" / relocatable, which I can pack into a #squashfs image to carry around to my various development machines.
You'd think that for something as fundamental as compiler infrastructure with over 60 years of knowledge, the whole bootstrapping and bringup process would have been super streamlined, or at least mostly pain free by now.
Yeah, about that. IYKYK
Neustradamus :xmpp: :linux:#SquashFS 4.7 has been released (#SquashFSTools / #LinuxFS / #Linux / #FileSystem) https://github.com/plougher/squashfs-tools
Vori 
ajft [SEC=yferc ooxie]@unascribed the one thing I'd like to be able to do with #squashfs is generate a multi-part fs, with each chunk a max of, say, 100GB, then be able to mount them later without needing to manually cat them all back together. maybe I haven't looked hard enough, but I can't see a way to do that
André MachadoKlaus Knopper is a renowned German software developer, entrepreneur, and educator, best known for creating Knoppix, one of the first Linux distributions to run directly from a CD or DVD without requiring installation on a hard drive.
Read More: https://machaddr.substack.com/p/klaus-knopper-creator-of-knoppix
#Knoppix #Linux #Accessibility #Live #Distribution #Squashfs #OpenSource #Programming #Bio
Klaus Knopper: Creator of Knoppix and Open-Source Advocate
Klaus Knopper is a renowned German software developer, entrepreneur, and educator, best known for creating Knoppix, one of the first Linux distributions to run directly from a CD or DVD without requiring installation on a hard drive.
HabrКак пересобрать ядро для WSL2 и остаться в живых
Мы активно пользуемся WSL2 для того, чтобы открывать линуксовые коры в Visual Studio. Для обеспечения консистентности символов и коры мы монтируем squashfs образ, созданный в целевой системе. После очередного апдейта целевого дистрибутива, у нас всё сломалось - squash монтировался, но мог посередине файла выдать ошибку чтения, записав в dmesg что-то типа SQUASHFS error: xz decompression failed
AliveDevil
Ryan HamelRyan Does #NixOS - Part 7
I was able to generate the required files for #iPXE booting a #flake (#kernel + #initrd w/ #squashfs + iPXE script file), but kept running into issues with the kernel "unable to mount root fs" or "initramfs unpacking failed: invalid magic at start of compressed archive". What is weird is that https://github.com/nix-community/nixos-images/ when booted through netboot.xyz works just fine, if I grab the underlying kernel + initrd + iPXE script on MULTIPLE #systems , it fails with the latter message.
This is really boggling my mind as I thought there was data corruption happening, but I am more likely to believe something is happening within NixOS's #zstd compression, or with that building process.
I was able to generate the required files for #iPXE booting a #flake (#kernel + #initrd w/ #squashfs + iPXE script file), but kept running into issues with the kernel "unable to mount root fs" or "initramfs unpacking failed: invalid magic at start of compressed archive". What is weird is that https://github.com/nix-community/nixos-images/ when booted through netboot.xyz works just fine, if I grab the underlying kernel + initrd + iPXE script on MULTIPLE #systems , it fails with the latter message.
This is really boggling my mind as I thought there was data corruption happening, but I am more likely to believe something is happening within NixOS's #zstd compression, or with that building process.
