After all these years on UNIX and Linux I do miss a good registry cleaning (as well as defragmenting!)
post
Well, that sucks. I'm not going through the whole video but just looking at what the legal filing said of his crime, I'm not entirely convinced he's reformed. He was a damn adware scammer.
And he's possibly back at it again... (Not sure if his new product is adware or similar)
While you're at it, degauss your monitor.
Hey, I'm a retired Microsoft engineer. Hey, did you know that DOS programs were actually pretty cool, I engineered the minimize buttons and Steve Balmer definitely didn't touch me inappropriately.
I know everyone is talking about defragging but the Windows registry is still a piece of junk core component on Windows we have to deal with, unlike NTFS getting away with being on an SSD.
regedit HKLM my ass
Remember these apps for Android?

I edited my registry and just deleted the entries and keys that were no longer relevant. Mostly by gut feeling. I sure do miss that old computer.
Did Linux ever defrag or do inodes make that irrelevant?
Fragmentation is mostly a non-issue with ext2/3/4. If you're filling drives to the brim with data usually accessed in sequence (a media library for example), you should still defrag occasionally to improve access times.
Edit: This assumes you're using physical harddisks. SSDs are not negatively affected by data fragmentation in any way that functionally makes a difference.
not inodes but the ext2 FS itself.
XFS and BTRFS do need to be occasionally defragged if you use them on a single HDD (non RAID).
NTFS got away with never updating itself due to the introduction of SSDs, which is why Windows had to be aggressively defragged on HDDs starting from the Win 8 era onwards.
inodes are just the id of a file entry on disk (e.g. NTFS has them, but calls them records)
There is still a need to defrag under *nix, but it's just really uncommon because you'll only get them when you update a file in-place, and most things don't do that under *nix. So you'll only see them in the common case with something like bittorrent downloads, and clients can still avoid that a lot of the time.
Ext tries to avoid it by trying to keep space open in front of the write sector, or finding a space when it commits to disk rather than up front. If that fails the file gets fragmented. If you don't have a lot of space available on the disk it's more likely to happen (though this is the case on Windows as well for a slightly different reason. It's why Windows used to recommend that you leave at least 10% free space on the disk). Larger files obviously more likely to fragment as well.
Fuck is a defrag?
Gather round the campfire youngsters, and let me regale you of a time when hard drives saved linearly and deletions eventually caused your hard drive to look like a Rubik's cube exploded, and so you defragmented it so it was all nice and tidy, like an unexploded Rubik's cube.
Source: going purely by the accompanying graphic when you defragged that sumbitch
The way hard drives work is when you store a file it is written to sectors, and each sector has a bit of data in the sector and file table to go "this sector, then that sector, then that next sector, etc, etc". Now as you add and delete files your files start to get into a couple of sectors here, one way over there, then three sectors over here, and so on, and all your files are like that. That means that your HDD's have to work way harder and slower to access those sectors. That is called File Fragmentation.
Defragmentation, or Defrag/Defragging is the act of moving those sectors so they are continuous and have little or no fragmentation. Better Defragging programs would also use the placement of the files on the disk to make the more important or more commonly used programs on the fastest to access parts of the disk and the slower programs at the slower to access parts of the disk.
It also often came with a popular display option of the work it has done vs what is left to do that you can find a simulation here https://defrag98.com/
Eventually Computers got so powerful and so mutithreaded that they could do this while the computer was running and doing other things and the one that came with the OS was just good enough for people to largely stop doing it manually. With modern SSD's though this is not necessary as they kind of do their own kind of defrag called TRIM.
Back in the day when hard drives were smaller, you'd easily find yourself using a major fraction of it. If you keep adding and deleting files of different sizes, using a drive fully gets complicated. You may cumulatively have the space for your new file, but you may not have enough space in a row, so it'll fail to write the file. Defragging was a really slow operation that moved all the free space to one side, so you can easily add new files. It's the digital equivalent of pushing all your hangers to one side in the closet.
It's not that saving the file would fail, but it would take longer to read because the stylus would have to read parts of it from wildly different locations on the drive. Defragmentation reorders everything so that the memory blocks for each of these files are next to each other so the stylus doesn't have to move as much.
Why is it no longer an issue with modern moving parts HDDs? Was it some sort of firmware related limitation?
Back in the day when hard drives were smaller, you’d easily find yourself using a major fraction of it
I find myself doing that now! My work machine in particular is very long-suffering on this front.
Something windows users had to do in the past because they bought a shit operating system
all 57 comments