In the 90s, I was running out of space on my 2GB Win95 machine. I decided to delete files. But I was not ready to part with my games which were consuming the bulk of the hard drive. I noticed every application folder had those .ini files and they were everywhere.

So I deleted them, and saved a few megs overall. Win win. Everything worked just fine... Until I restarted. That's doge.

▲ shagie 17 hours ago | parent | next [-]

Also in the 90s...

I remember they were HP Bobcats. We had two of them in a student lab and user directories weren't on a separate partition... so things filled up. And they kept getting filled up.

One of the people who ran the lab found that he could get back a couple of hundred kilobytes by running strip on all of the various things he wrote.

    find . -type f -executable -exec strip {} \;

... or something to that effect. It worked.

So he ran it in the root directory too and was pleased to find many megabytes more of space was available.

... Did you know that .so files are executable? ... And the kernel too?

Things that were statically compiled worked. But anything that was dynamically compiled failed. And when the machine was rebooted... it was really unhappy with being unable to find the linking information for the kernel.

Had to go beg a tape reinstall of the OS to get it working again.

(and then there was the story of the guy who bought a NeXT and thought that the "bin" guy was taking up too much space)

	▲	seanhunter 17 hours ago \| parent [-]
		With the default arguments in the 1990s strip wouldn’t strip “linking information” it would just strip debugging symbols. You wouldn’t have been able to debug a core dump say but dynamically linked binaries would have been totally fine.

▲ SirFatty 17 hours ago | parent | prev | next [-]

Until the last two words, I assumed you posted in the wrong story :-D

▲ CableNinja 5 hours ago | parent | prev [-]

Replace ini with himem.sys

"That takes up so much space!"

Worked until reboot. And thats the start of my dive into IT