Nov. 15th, 2023

liam_on_linux: (Default)
I suppose it was a long time ago.

So...

The 80386DX was the first x86 CPU to be 32-bit and have an on-chip MMU. And nothing else: no cache, no FPU.

The FPU was a discrete part, the 80387DX.

Because OS/2 1.x didn't support the 80386, and so couldn't run DOS apps well, and so flopped, the 16-bit 80286 kept selling well. It ran DOS fast and it could run Windows 2/286 and Windows 3 in Standard Mode which was good enough. It could only address 16MB of RAM but that was fantastically expensive and it was more than enough for DOS and Windows 3.

So, because DOS still ruled, Intel made a cost-reduced version of the 80386DX, the 80386SX. This had a 16-bit data bus, so it could use cheaper 16-bit motherboards and 16-bit wide RAM, still limited to a max of 16MB. Still enough.

That needed a maths copro for hardware floating point, too: a different part, the 80387SX.

Then Windows 3 came along, which was also good enough, and started a move in PC apps to GUIs. Windows 3.1 (1992) was better still.

So Intel had a 2nd go at the 32-bit chip market with the 80486, marketed as the "486". This integrated a better 386DX-compatible CPU core with a few extra instructions, complete with MMU, plus a 387-style FPU, plus a small amount of L1 cache, all onto one die.

But it was expensive, and didn't sell well.

Also, all the 3rd party x86 makers leapt on the bandwagon and integrated the extra instructions into 16-bit bus 386SX compatible chips and branded them as 486s: the Cyrix and IBM "486slc" for instance. This ate into sales of the real 486.

So Intel came up with an ethically very dodgy borderline scam: it shipped 486s with the FPU disabled, calling them the "486DX" to reuse the branding that distinguished the 32-bit-bus models of 386 from the 16-bit-bus.

People don't understand stuff like bus widths or part numbers, as your post demonstrates, and I mean no offense. They don't.

So now there was a new model of 486, the 486SX with a disabled FPU, and the 486DX with it still turned on.

The "SX" model needed a new motherboard with a 2nd CPU socket that accepted a "floating point co-processor", called the "487", which was nothing of the kind. The "SX" was a lie and so was the "487 copro". The 487 was a 2nd complete 486 chip that disabled the original and took over.

But it reused the older branding, which is what you've remembered.

Later, briefly, Intel made a cheaper cost-reduced 486SX with a smaller die with no FPU present, but not many of them. The clock-doubled 486DX2 took over quite quickly and killed the 486DX and 486SX market.

Some commentators speculated that the 486DX vs 486SX marketing thing allowed Intel to sell defective 486s in which the FPU didn't work but if it did that was a tiny tiny number: a rounding error.

 
liam_on_linux: (Default)
This is an extremely broad question and it needs a tonne of context to give an unambiguous answer.
  • For what role?

    • Server...

      • Web server?

      • File server?

      • Print server?

      • Router/firewall?

    • Desktop?

      • General purpose desktop?

      • Gaming desktop?

      • Emergency recovery desktop?

      • App-specific desktop?

Alpine is lightweight because almost nothing is pre-configured for you and you must DIY... but saying that its origins are as a router distro repurposed to be general-purpose. It uses a different libc, which is a huge change. Every single app has to be recompiled to work with musl libc instead of glibc.

Open_WRT is lightweight because it's dedicated to running on routers.

CBL Mariner is lightweight because it's only for certain niche server VMs.

antiX is lightweight because it's a general-purpose graphical desktop but ruthlessly purged of heavyweight components, all replaced with the smallest lightest-weight alternatives.

Raspberry Pi Desktop is lightweight because it's an x86 version of a brutally pared-down Debian originally meant for a single-core Arm computer with 512MB of RAM.

Bodhi Linux is lightweight because it's Ubuntu but with all the desktop stuff removed, replaced with a forked old version of a very lightweight window manager and almost nothing else. Any functionality you want you must install.

Lots of different answers, lots of different use cases, lots of different strategies.

This is not a "yes/no" question. It's complex and nuanced.

Debian is not lightweight. Its strapline is "the universal operating system". It's a Swiss Army knife that can do anything and that's part of its definition.

You can make a lightweight install of it if you know what you're doing but ticking the box for a lightweight desktop and installing is not doing that.

Comparison: you see a lightweight sports motorcycle. It's green. You buy a Harley and paint it green and say "look mine is a lightweight sports bike now!"

Devuan is just Debian with systemd removed and openrc or sysvinit in its place. This is not a big sweeping change. It's equivalent to looking at the sports bike, seeing it has Bridgestone tyres instead of Dunlop, and swapping the tyres on the Harley to Bridgestone tyres.

It is a trivial change compared to a libc change. It's routine maintenance to change your tyres. You need to do it regularly anyway. It doesn't need the bike to be rebuilt.

It's not easy. It takes hours and skills and tools and so on but it's not sweeping.

Devuan has rebuilt a tonne of packages to remove dependencies on systemd and that's not trivial but it's still Debian. By and large you can download any Debian package and install it and it'll just work because most things never interact with the init daemon and it won't make a big difference.

A Swiss Army knife with a different axle that pivots a bit more smoothly and with less force is still a Swiss Army knife and only a knife expert will be able to even tell the difference.

It doesn't make it into a super-slim lightweight knife, like -- I know nothing about knives -- something like this.

You could disassemble a Victorinox and rebuild it into something like that but it's really hard and an amateur will end up with a broken pile of bits.

So the fact that people build lightweight distros out of Debian doesn't mean Debian is lightweight or that you can do it yourself. Think about it: if it was easy, lightweight remixes wouldn't exist! There'd be no point.

How do you tell if it's lightweight or not?

Look at how big the ISO file you download is.

4-5GB is big.

2-3GB is typical.

<2GB is small.

~1GB is tiny.

Run df -h and look at how much disk space it takes. Much the same applies.

Run free -h on a newly-booted machine and look at how much RAM it's using.

200MB is light in 2023.

Under 0.5GB is good.

0.75GB is OK.

Over 1GB is typical.

May 2025

S M T W T F S
    12 3
45678910
11121314151617
18192021222324
25262728293031

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated May. 19th, 2025 04:10 am
Powered by Dreamwidth Studios