The Permission SlipIt always started this way. My wife would order me to clean up the mess. I would act reluctantly, making the men feel empowered. It wouldn't be long before she would order me to take it from the source, and the men would gleefully feed me without missing a beat.
ferricoxideAutomating the installation of a #Windows package that is really not designed for multi-user installation is decidedly un-fun. It's especially unfun when:
1. The
2. The
Ultimately had to kludge around the limitations by leveraging temporary #NTFS filesystem-junctions (what we, who normally only dick with #Linux, might call "symbolic links").
1. Create junction
2. Point the
3. Once the
4. Update the registry-entries that tell Windows where to find the application's uninstaller
The #Linux installation wasn't great, either, but the "installer" limitations were marginally less-kludgey to work around. The software doesn't come as an #RPM, so, it didn't come with any #SELinux rules (on the plus side of not being an RPM, I didn't have to worry if it used a signature or file-digest algorithms that weren't FIPS-compatible). Since the installation-targets are SELinux (and #FIPS!) enabled, had to add further logic to the automation to set up the proper SELinux contexts. We'll see how well that works, once the whitelist daemon is activated…
But still, "ugh. I hate Windows".
1. The
setup.exe doesn't prompt for a multi-user vs "self" install2. The
setup.exe absolutely refuses to install to paths with spaces in their name (you know, like C:\Program Files\<APPLICATION_NAME>Ultimately had to kludge around the limitations by leveraging temporary #NTFS filesystem-junctions (what we, who normally only dick with #Linux, might call "symbolic links").
1. Create junction
2. Point the
setup.exe at the junction-path3. Once the
setup.exe completes, nuke the junction-path4. Update the registry-entries that tell Windows where to find the application's uninstaller
The #Linux installation wasn't great, either, but the "installer" limitations were marginally less-kludgey to work around. The software doesn't come as an #RPM, so, it didn't come with any #SELinux rules (on the plus side of not being an RPM, I didn't have to worry if it used a signature or file-digest algorithms that weren't FIPS-compatible). Since the installation-targets are SELinux (and #FIPS!) enabled, had to add further logic to the automation to set up the proper SELinux contexts. We'll see how well that works, once the whitelist daemon is activated…
But still, "ugh. I hate Windows".
𝗣𝗠𝗝 ⚫so, der umbau mit den neuen HDDs ist fast abgeschlossen
ich hab jetzt 4 tage damit verschwendet herausezufinden weshalb #jellyfin nach dem kopieren aller medien von #ntfs nach #btrfs meine ganze library komplett neu einliest und alles dupliziert
#windows nutzt nur ctime, was allerdings der timestamp für metadata change ist, als creation time - in #linux ist es btime
und obwohl btrfs per virtiofs in der windows vm eingebunden ist und dort im explorer nur die ctime anzeigt, nimmt jellyfin trotzdem die btime
ja, ich weiss, ich hab ein xtrem weirdes setup - aber deshalb bin ich ja gerade am umbauen
aber halt step-by-step und nicht alles hauruck
#homelab
AskUbuntuHow to get information after a crash leading to initramfs prompt? #ntfs
Damian Yerrick@carlton @sethmlarson And does the consensus against symbolic links arise from inexperience? Windows didn't let unprivileged users create symlinks in NTFS until Windows 10 build 14972 in 2018, and even then only if developer mode is on. Instead, Windows desktop users' experience since 1995 has been with shortcuts, which operate at the shell level, not the file system level.
fosstopia 🇩🇪Linux Kernel 7.1 bringt neuen NTFS‑Treiber und räumt im Code auf https://fosstopia.de/linux-kernel-7-1-ntfs-treiber/ #Kernel71 #Linux71 #LinuxKernel #LinuxNTFSTreiber #NTFS
Marcel SIneM(S)US#NTFS-Treiber für #Linux 
: NTFS-3G schließt Rechteausweitungslücke | Security https://www.heise.de/news/NTFS-Treiber-fuer-Linux-NTFS-3G-schliesst-Rechteausweitungsluecke-11268864.html
: NTFS-3G schließt Rechteausweitungslücke | Security https://www.heise.de/news/NTFS-Treiber-fuer-Linux-NTFS-3G-schliesst-Rechteausweitungsluecke-11268864.html
GlitchyZorua 
#Linux 7.1 will have an optional new #NTFS Driver
fugahogeds更新されたよ、見に来てね!→ 【ダイジェスト】#Linux 7.1の土台が総改修 #NTFS ・ #KDE ・ #BSD ・音声基盤まで一気読み 週明けの目覚ましニュース 2026年4月20日(月) #News #OSS https://www.youtube.com/shorts/RFrVI7kKJ7k
【ダイジェスト】#Linux 7.1の土台が総改修 #NTFS ・ #KDE ・ #BSD ・音声基盤まで一気読み 週明けの目覚ましニュース 2026年4月20日(月) #News #OSS
Gabriele BiondoNew post on The Byte Architect:
**Filesystem Wars: Why Your Choice of Storage is Actually a Security Move**
This is not a “which filesystem should I use?” checklist. It is a walk through the ideas behind FFS, BFS, NTFS, ext4, ZFS, and APFS — and why storage design is never just about storage.
Crash consistency, journaling, soft updates, CoW, snapshots, encryption, space sharing: different filesystems solve different problems, and those choices shape reliability, usability, and security.
The real target, of course, is APFS.
Read it here: https://bytearchitect.io/macos-security/theory/Filesystem-Wars-Why-Your-Choice-of-Storage-is-Actually-a-Security-Move/
#macOS #Apple #APFS #ZFS #ext4 #NTFS #ReverseEngineering #InfoSec #CyberSecurity