@erkin What do these do?
SIGINFO is a kill signal that is triggered with ^T (like how ^C triggers SIGINT) that makes the process spit out information.
A particular program that would greatly benefit from it would be dd, which must be *externally* sent SIGUSR1 to make it print I/O status.
Unlike a hard link, it's not a separate file pointing to the same inode, but a special file pointing at a file pointing at an inode instead.
@erkin So hard links not dependent on being on the same FS and more compatible?
Not sure how they handle cross-filesystem links but that's the gist. Unlike hardlinks, firmlinks die if the original file is deleted.
@erkin Would they work on FAT32 or Windows?
@erkin Also finding it hard to find documentation on that.
I don't think any OS other than HURD implements it.
@erkin I meant documentation on it in general, HURD docs would work.
This page explains how HURD's filesystem concept works:
It's got rather novel features.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!