Comment Re:Retiring from IT in general seems like a good i (Score 4, Informative) 85
I can't say there's a single thing I enjoy about any of this any more. I think I understand why so many IT people retire early and take up farming.
I suspect it's going to be important but I wonder if these companies that are demanding it are being premature.
I remember when syntax highlighting came in. For a good while I disabled it as I found it distracting but over time I got used to it and now I prefer to have it on (although I'm still not greatly inconvenienced if I don't have colour)
I remember when LSPs became available. For a while I didn't bother but now I find it hard to work without one configured (in vim) although I do still resort to grep/sed etc, especially where the LSP doesn't work in some C++ where type deduction is hard.
And now LLMs. I use them via a web prompt and they can save considerable time where I'm looking something up. But they've also cost me considerable time where I've relied on the answer which, once I actually spent the five minutes reading the (long) manpage, was so obviously wrong that I'd be concerned about any programmers long term success and I'd certainly be trying to limit their access to any code that I'm responsible for!
I think more than anything it's this utterly absurd wrongness that they do with such verisimilitude that make them dangerous currently.
does unlink in debugfs update the free block list?
Yes, when you use unlink on a file in debugfs (or via any means in the Linux filesystem stack), it does eventually update the free block list -- but not immediately at the debugfs tool level unless explicitly committed or updated.
In debugfs specifically:
debugfs is a low-level filesystem debugger. It does not mount the filesystem or execute actions in real time the way the kernel does during normal operations.
If you run the unlink command in debugfs, it removes the directory entry, and depending on the inode's link count, it may also release the inode.
But to update the free block list, debugfs must explicitly free the inode and associated blocks.
In recent versions of debugfs:
unlink can update the block and inode bitmaps if used correctly and if the file has no other hard links.
But sometimes manual intervention (e.g., using clri to clear inodes or freeb to free blocks) is necessary in corrupted filesystems or after a crash.
Summary:
Yes, unlink in debugfs can update the free block list.
But this happens only if the file is fully unlinked (no hard links remain).
Remember that debugfs works outside the kernel, so changes are made directly to disk structures -- use with caution.
But:
man debugfs
unlink pathname
Remove the link specified by pathname to an inode. Note this does not adjust the inode reference counts.