Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

59% Positive

Analyzed from 1381 words in the discussion.

Trending Topics

#kernel#driver#linux#drivers#still#mouse#bus#isa#https#code

Discussion (51 Comments)Read Original on HackerNews

bastawhizabout 4 hours ago
This is the kind of spring cleaning I crave. Deleting busted drivers that haven't worked in over a decade? Fantastic!

Some of this hardware likely has exactly zero users because the material it's made from can't possibly have survived. Look at the cord on the mouse in the photo: you might be able to plug it in, but I wouldn't bet money signal can still make it down the wire.

trollbridgeabout 4 hours ago
My bus mouse still works just fine; things built in the 80s tended to be pretty solid.

However, it would be hard pressed to find a machine with ISA slots with enough resources to run Linux 7.1 acceptably.

cestithabout 3 hours ago
There are still ISA slots in new systems with fairly modern processors and plenty of RAM, if you don’t mind buying specific models of industrial PCs for way too much money.

For $1100 or so you, too, could have a 4th generation Core i3 machine. https://www.rampcsystems.com/product/2-isa-slot

Or maybe you need 4 PCI and 9 ISA for some reason. DuroPC’s got you, if you can drop $1800 on a system with the same generation of processor. https://duropc.com/product/r810-4p9i-4

M95Dabout 3 hours ago
ISA slots are all identical. If you have one slot, you can multiply it to 100 slots just by connecting the wires.
dparkabout 2 hours ago
> things built in the 80s tended to be pretty solid

Survivorship bias. We built a lot of crap stuff in the 80s, too. Most stuff built in the 80s is probably in landfills now.

estimator7292about 3 hours ago
Most things.

Plastics and rubbers tend to not survive well a lot of the time just because of the chemistry. There's really no way around plastic embrittlement and rubber decomposing. You can prolong it with the right storage conditions, but those molecules are gonna break down sooner or later.

kube-systemabout 3 hours ago
The mouse in the photo was made somewhere between 1987-1993. I have computers older than that which work just fine.
kstrauserabout 2 hours ago
Same, but I didn't spend a lot of time putting my grubby hands on those computers.
FpUserabout 3 hours ago
My Z840 server I use for self hosting has both bus original IBM keyboard and bus mouse attached. Either works just fine.
xiphias2about 4 hours ago
Microkernels have lost the open kernel wars because of their speed problems, but this is a great example of a driver that should have been running in userspace a long time ago, just like how Windows has been moving in that direction.

Isn't Linux planning to do the same?

augusto-mouraabout 3 hours ago
I guess things are going into that direction naturally, but not officially. eBPF is helping with getting deep kernel aspects into userspace. And there's some ressurgence of out-of-tree graphics drivers, specially for gaming.

I believe userspace drivers are much more powerful and easy to build than 10 years ago, but it is not from a requirement from the kernel.

Who knows, maybe we will get a smaller (instead of bigger) kernel in 10-20 years

xiphias2about 2 hours ago
Luckily I'm not a kernel maintainer, but it seems like they don't have 10-20 years to make hard practical decisions. It's easy to get rid of old unmaintained drivers, but they have to solidify interfaces much more as it is getting exponentially easier to find and use bugs or any unspecified part of the kernel for attacking it.

There was a very interesting point when people who were creating Rust interfaces were asking hard questions about ownerships and lifetimes in driver interfaces from the C linux maintainers and they didn't really care to answer (just wanted to wish Rust away).

Now with AI these questions are getting practical. Fortunately big companies have big stake in keeping linux secure, so I'm not worried about it being addressed at least.

e12eabout 3 hours ago
> this is a great example of a driver that should have been running in userspace a long time ago, just like how Windows has been moving in that direction.

Hasn't windows (nt lineage) moved solidly in the opposite direction? Used to be you could reload/restart the video card ("GPU") driver if the driver crashed?

halter73about 3 hours ago
I think this conflates two different eras/layers. NT 4 famously moved the window manager/GDI/graphics subsystem into kernel mode, so that’s probably the “opposite direction” history. But modern GPU-driver recovery is WDDM/TDR, and it very much still exists: WDDM splits the display driver into user-mode and kernel-mode components, and TDR resets/recovers a hung GPU/driver instead of requiring a reboot.

https://learn.microsoft.com/en-us/windows-hardware/drivers/d... https://learn.microsoft.com/en-us/windows-hardware/drivers/d...

I also update NVIDIA drivers regularly on Windows 11 without rebooting, though that’s install-time driver reload rather than exactly the same thing as TDR.

doctorpanglossabout 3 hours ago
No it's the opposite. WDDM and DirectX are constantly being updated and have been improving crash recovery of the GPU, updating its driver, power management, abstracting features like video encoding and storage DMA, among many things. In Linux it is taking ages, the first proposal for DRM to support 2010 era WDDM features was in 2021 and it still does not exist. Graphics is one of the few places some of Microsoft still innovates. Although not in the sense of having great code, they just put in the work to coordinate these changes from the handful of vendors. If only someone hosted more steak dinners for Linux.
clifflockedabout 4 hours ago
If anyone is curious, here is the actual commit that removed the drivers: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
dparkabout 2 hours ago
What the hell. Kernel.org is mining in my browser to “make sure I’m not a bot”?
midtakeabout 3 hours ago
Is this due to Mythos and other LLMs finding a bunch of obscure bugs or simply a precaution? If someone (a normie not a gentooman) wanted to run Linux on retro hardware how would they do it? Boot Debian Sarge?
CodeWriter23about 2 hours ago
The old-fashioned way, build your own kernel with the driver included.
flohofwoeabout 4 hours ago
Raises the question whether a bug in code that's never called actually exists ;)
advisedwangabout 4 hours ago
Code that is never normally used can sometimes still be gotten to run by an attacker, and therefore can still be a security risk.
M95Dabout 3 hours ago
But that code would have to be selected in menuconfig, compiled, and the module loaded. I assume that nobody does that for bus mice, and even if someone, by mistake, selects one of the drivers, that's 1 machine in a billion. Who would target that?

Same argument for any retro-tech. What hacker would spend hours/days to hack my bare-metal DOS box running Arachne + a packet driver just to mine bitcoins on a K6-2 for a couple of hours until I turn it off from the AT power switch (not button).

Someone1234about 3 hours ago
From my understanding, that isn't how drivers in Linux work. Nearly no kernels will have that code compiled into them because kconfig won't call for it. It is "opt-in", and it is so niche few Distros would have done so.

Linux only ships with a tiny sub-set of the drivers in the source tree.

rationalistabout 4 hours ago
mongolabout 3 hours ago
What is a bus mouse? Is it using the old PS/2 port?
mayamaabout 3 hours ago
VorpalWayabout 3 hours ago
The PS/2 connector is what came after that the bus mouse. Back then the mouse was connected to a specialised add-in card. Probably an ISA card if I remember correctly.
guzfipabout 2 hours ago
Damn, there goes Linux as my retro computing target.

Guess I’ll be porting dahdi to netbsd soon lol.

Tbf, I get why Linux is dropping all this stuff. I wouldn’t mind becoming a maintainer of smaller drivers myself, but I doubt I have the skill level.

mmoossabout 3 hours ago
> looking to remove old drivers due to the surge of AI/LLM bug reports

I wonder how OpenBSD's careful code quality and hygiene (maybe there's a better word) has affected its vulnerability to LLM bug finding. Did their approach pay off in this case?

shevy-javaabout 3 hours ago
This makes me sad.

Now, most will say "but why, 1995 is ancient history, no such hardware exists anymore". The thing is ... should Linux get rid of what is old? I understand you have a smaller kernel when you have less code, less cost to maintain, I get it. Still, I wonder whether this should be the only allowed opinion. Would it not be better to, kind of, transition into a situation where any hardware built in the future, would be supported? So in 2050, we'd not say "damn, computers from 2026 are obsolete now". We could say "no problem, linux is forever". Everything is supported. I actually would prefer the latter than the "older than 30 years, we no longer support it".

bigfishrunningabout 3 hours ago
> Would it not be better to, kind of, transition into a situation where any hardware built in the future, would be supported?

easier said then done -- the kernel's internal interfaces aren't static, they change often. The project has never committed to stabilizing it's driver api, so every driver takes non-zero work to maintain.

I would assume computers that are still running these old ISA mouses (mice?) probably are also running an older version of linux; and if they're running a new kernel then it'll be somebodys job to port the drivers forward. There's some likelihood this will end up maintained by someone out-of-tree, which is a nice way of saying "we've sent your dog to a farm upstate..."

sockaddrabout 2 hours ago
To add to this, as long as the diff representing the removal of the driver is kept in the git history it would be trivial for someone in the far future to say to an AI agent:

"Please take this linux source and patch the Bus mouse driver back in but match the new driver interface".

With code preserved in git history it's never actually "removed". It's just, disconnected.

jamesgeck0about 3 hours ago
That date feels a little bit late. The PS/2 devices that superseded the bus mouse started appearing around 1987. There were certainly still bus mice around in 1995, but they were thoroughly obsolete.
wang_liabout 2 hours ago
The real issue is that they don't have stable intra-kernel ABI/APIs. It should entirely be the case that technologies that are 10+ years old are stable and a clean abstraction layer can be created. You maintain the abstraction layer and all the things on the other side of it don't have to track random kernel changes. Things like this just keep working indefinitely.
whalesaladabout 4 hours ago
that pee stained microsoft mouse is really sending this home
thekid314about 4 hours ago
That's the next Apple Neo color for you.
cptskippyabout 3 hours ago
I'm sure that photo was chosen rather deliberately to garner support from a wide cross selection of grey beards.