Live data from Hacker News

Floppinux – An Embedded Linux on a Single Floppy, 2025 Edition

krzysztofjankowski.com

31–40 of 201 posts

Re: Floppinux – An Embedded Linux on a Single Floppy, 2025 Edition

#31
post #7

The persistence strategy described here (mount -t msdos -o rw /dev/fd0 /mnt) combined with a bind mount to home is a nice clever touch for saving space. I don't know if that's also true for data integrity on physical magnetic media. FAT12 is not a journaling filesystem. On a modern drive, a crash during a write is at best, annoying while on a 3.5" floppy with a 33mhz CPU, a write operation blocks for a perceptible am…

> If the user hits the power switch or the kernel panics while the heads are moving or the FAT is updating, that disk is gone.

This isn't true, I commented lower in the thread, but FAT keeps a backup table, and you can use that to restore the disk.

Re: Floppinux – An Embedded Linux on a Single Floppy, 2025 Edition

#32

Earlier quoted context omitted.

Controversial position: journaling is not as beneficial as commonly believed. I have been using FAT for decades and never encountered much in the way of data corruption. It's probably found in far more embedded devices than PCs these days.

If you make structural changes to your filesystem without a journal, and you fail mid way, there is a 100% chance your filesystem is not in a known state, and a very good chance it is in a non-self-consistent state that will lead to some interesting surprises down the line.

No, it is very well known what will happen: you can get lost cluster chains, which are easily cleaned up. As long as the order of writes is known, there is no problem.

Re: Floppinux – An Embedded Linux on a Single Floppy, 2025 Edition

#34
post #22
post #10

Over Christmas I tried to actually build a usable computer from the 32-bit era. Eventually I discovered that the problem isn't really the power of the computer. Computers have been powerful enough for productivity tasks for 20 years, excepting browser-based software. The two main problems I ran into were 1) software support at the application layer, and 2) video driver support. There is a herculean effort on the part…

> Computers have been powerful enough for productivity tasks for 20 years It baffles me how usable Office 97 still. I was playing with it recently in a VM to see if it worked as well as I remembered, and it was amazing how packed with features it is considering it's nearing on thirty. There's no accounting for taste but I prefer the old Office UI to the ribbon, there's a boatload of formatting options for Word, there…

Last true step change in computer performance for general home computing tasks was SSD.

Re: Floppinux – An Embedded Linux on a Single Floppy, 2025 Edition

#35
post #22
post #10

Over Christmas I tried to actually build a usable computer from the 32-bit era. Eventually I discovered that the problem isn't really the power of the computer. Computers have been powerful enough for productivity tasks for 20 years, excepting browser-based software. The two main problems I ran into were 1) software support at the application layer, and 2) video driver support. There is a herculean effort on the part…

> Computers have been powerful enough for productivity tasks for 20 years It baffles me how usable Office 97 still. I was playing with it recently in a VM to see if it worked as well as I remembered, and it was amazing how packed with features it is considering it's nearing on thirty. There's no accounting for taste but I prefer the old Office UI to the ribbon, there's a boatload of formatting options for Word, there…

I think MS Word was basically feature-complete with v4.0 which ran on a 1MB 68000 Macintosh. Obviously they have added lots of UI and geegaws, but the core word processing functionality hasn't really changed at all.

(edit to say I'm obviously ignoring i8n etc.)

Re: Floppinux – An Embedded Linux on a Single Floppy, 2025 Edition

#37

Did I misremember downloading Slackware to 12 floppies in 1997?

12‽ I'd swear the Slackware I downloaded was closer to 30+. On dialup. Via a VAX. Using FTP to go from internet to the VAX box, then Kermit from the VAX to the DOS PC using Procomm Plus. Write it all, start the install sequence, find out that the 18th disk was bad. Reboot. Rinse. Repeat.

X disks were X11. There were also the A,B, C etc disks.

Then there was the Coherent install, with massive manual on ultra thin paper with the shell on the front.

Re: Floppinux – An Embedded Linux on a Single Floppy, 2025 Edition

#39
post #10

Over Christmas I tried to actually build a usable computer from the 32-bit era. Eventually I discovered that the problem isn't really the power of the computer. Computers have been powerful enough for productivity tasks for 20 years, excepting browser-based software. The two main problems I ran into were 1) software support at the application layer, and 2) video driver support. There is a herculean effort on the part…

> There is a herculean effort on the part of package maintainers to build software for distros, and no one has been building 32 bit version of software for years, even if it is possible to build from source. There is only a very limited set of software you can use, even CLI software because so many things are built with 64 bit dependencies

That seems odd? Debian 12 Bullseye (oldstable) has fully supported i386 port. I would expect it to run reasonably well on late 32 bit era systems (Pentium4/AthlonXP)

Re: Floppinux – An Embedded Linux on a Single Floppy, 2025 Edition

#40
post #22
post #10

Over Christmas I tried to actually build a usable computer from the 32-bit era. Eventually I discovered that the problem isn't really the power of the computer. Computers have been powerful enough for productivity tasks for 20 years, excepting browser-based software. The two main problems I ran into were 1) software support at the application layer, and 2) video driver support. There is a herculean effort on the part…

> Computers have been powerful enough for productivity tasks for 20 years It baffles me how usable Office 97 still. I was playing with it recently in a VM to see if it worked as well as I remembered, and it was amazing how packed with features it is considering it's nearing on thirty. There's no accounting for taste but I prefer the old Office UI to the ribbon, there's a boatload of formatting options for Word, there…

It's wild to remember that I basically grew up with this type of software. I was there, when the MDI/SDI (Multi-Document Interface / Single-Document Interface) discussion was ongoing, and how much backlash the "Ribbon"-interface received. It also shows that writing documents hasn't really changed in the past 30 years. I wonder if that's a good or bad development.

With memory prices skyrocketing, I wonder if we will see a freeze in computer hardware requirements for software. Maybe it's time to optimize again.

Post reply on HN