Knoppix 8.5.0 Released
knopper.net
knopper.net
Like some commenters say, it was both a "safe" gateway to Linux, and a lifesaver when hard disks refused to work properly.
I got a lot done with that setup.
https://trends.google.com/trends/explore?date=all&q=knoppix,...
Booting off a live cd. The future in the early naughies.
Well maybe not the future, but cool, and very useful.
Nowadays many linux CDs/DVDs/USB sticks start by booting into a live system, and then offer you to install it.
Back in the days when Knoppix was popular, the major distros only had normal installers, so you needed a free partition for installation (or resize an existing windows partition to make room, which was very risky).
I don't remember how I first heard about Linux or Knoppix but I do remember those first magical moments using it. While I've had many influences Knoppix definitely was an early influence on my tech interests because it was so easy to start.
They still sell LinuxFormat at my local bookstore and it still comes with live disks. So it is only now becoming less relevant now that CD/DVD drives are becoming less of a thing.
No affiliation, I just think it's a cool free app and it's proven very handy for me loads of times.
Thanks for the tip!
But as most distros started providing this on their own, my need for Knoppix has completely disappeared, and last time I tried it, it appeared broken.
I guess you could say they are the victim of their own success, by popularizing live-CDs as a thing.
[0]https://en.wikipedia.org/wiki/Cloop [1]https://tracker.debian.org/pkg/cloop
Unfortunately ... if you let it ride much above 80% disk usage for very long (or less time the fuller it got) it would fragment bad and the performance just fell off a cliff bad.
I can't imagine why a fsck tool would dive into payload like that - do you have some more information about this bug, as I can't find reference to it. Most of my residual reiserfs boxes are VM's themselves, so I'm unlikely to hit it, but some mitigation would be comforting.
Yep exactly that. The whole reason it did it was that it sometimes needed to recover from a corrupted b-tree but it leaves enough markers around that it could rebuild the b-tree by scanning all the blocks.
https://en.wikipedia.org/wiki/ReiserFS#fsck
I can't find a better link at the moment, the lkml link on wikipedia is dead and it's hard to search for, but at the time it was well known for this kind of bug.
EDIT:
Until I learned about that bug (the hard way at first) the ability of it to rebuild itself after a problem like that was actually incredibly useful, it'd recover really nicely from a bad disk, finding just what it could manage to find.