On the latest #ATPpodcast I heard @siracusa pronounce the HEIC image format as a word - "heek" [hiːk]. He is the first human I have heard pronounce it as a word. I feel like, for me, it will always be "H E I C".

There are several acronyms I treat this way, that I've heard others say as words, thinking about it.

PNG, SVG, BMP, IFF, SQL, URL, LED, GUI, PDF, PCMCIA (well...), etc.

I am old and set in my ways.

By the way, GIF is not on that list because I pronounce it as a word starting with a soft G, because that is how that is pronounced.

Symbolic links vs Hard links in Linux. What's the difference? Why would you use one over the other? What limitations do each have? If you'd like to know these answers, check out this episode of Red Hat's Into the Terminal.

https://www.youtube.com/live/qzMxDLT4cIU?si=teSlMjdRfg8bUJ0s

One Open-source Project Daily

Disk Usage/Free Utility - a better 'df' alternative

https://github.com/muesli/duf

#1ospd #opensource #cli #df #diskspace #diskusage #filesystem #freebsd #hacktoberfest #linux #macos #openbsd #terminal #tui #userfriendly #windows

Hey #nerds, when you write out your file names, how do you separate the words?

#boostswelcome

One Open-source Project Daily

Manage filesystem snapshots and allow undo of system modifications

https://github.com/openSUSE/snapper

#1ospd #opensource #fs #filesystem #snapshots #linux #suse #opensuse

Guess who accidentally nuked their system by shrinking the volume TO 30 GB, instead of BY 30 GB...?

Sembra non aver fine la telenovela di #bcachefs il #filesystem più famoso per le polemiche che per le performance.

https://www.miamammausalinux.org/2025/08/bcachefs-si-autoproclama-stabile-dalla-versione-6-18-del-kernel-linux-ma-probabilmente-non-ha-fatto-bene-i-conti/

@linux @opensource

Just migrated my #Linux LVM-based #NAS to #ZFS based. So much easier setup. I don't think I'm ever going back.

#linux #cs #computer #science #directory #fileSystem

Yesterday I extracted the contents of an initrd.img that came packaged in a Fedora distribution. From kernel.org I learned this mini-os can be used by the kernel during the bootup process.

I guess I could have mounted the directory to play with the tools it is configured with. But I realized I do not know the difference between a directory and a file system.

Please help me understand what is the difference between these two concepts.

"df(1)" output processing in "awk(1)" to fetch the #ZFS dataset from the #fileSystem mountpoint on #FreeBSD 14 …

df -t zfs --libxo=json,pretty /var/{cache/pkg,db} \
| awk '/"name":/ { gsub( "(^\"|\",?$)", "", $NF); print $NF }'
var-2/cache-pkg
zroot2/var/db

Does anyone have a better idea (besides parsing "zfs-list(8)" output)?

Ha! Simpler …

zfs list -H -o name /var/{cache/pkg,db}
var-2/cache-pkg
zroot2/var/db

Included in that is "sort -u" as bonus!

Eh, not quite https://freeradical.zone/@ax6761/114845144411769287 …

I wanted to store some #BorgBackup archives on an #exFAT disk so that any operating system (not just #Linux) could easily read it, but Borg needs a journaling #filesystem.

In theory, there isn't any reason why journaling can't be implemented on FAT but everybody probably doesn't consider it worth the effort.

#NTFS would work too, except some of the #Linux machines I run Borg on are running Debian Stable, whose old kernel lacks the ntfs3 driver.

Things I like about FreeBSD:

"You can tune a file system, but you cannot tune a fish."

is still listed as a bug in the tunefs man page on FreeBSD 14.3
I first saw it more that 30 years ago on SunOS that was BSD based at the time.

Found a handy CLI tool for Git >_

**git-statuses** — Display the status of multiple Git repositories in a clear, tabular format.

Scans directories recursively for Git repositories

Written in Rust!

GitHub: https://github.com/bircni/git-statuses