The InfoMagic discs:
Disc 1: Slackware 3.0 and Debian 0.93R6
Disc 2: Red Hat 3.0.3 for x86
Disc 3: Archive of sunsite.unc.edu
Disc 4: GNU source archive from prep.ai.mit.edu
Disc 5: Archive of tsx-11.mit.edu
Disc 6: Demos and Red Hat 2.1 for Alpha
111–120 of 151 posts
The InfoMagic discs:
Disc 1: Slackware 3.0 and Debian 0.93R6
Disc 2: Red Hat 3.0.3 for x86
Disc 3: Archive of sunsite.unc.edu
Disc 4: GNU source archive from prep.ai.mit.edu
Disc 5: Archive of tsx-11.mit.edu
Disc 6: Demos and Red Hat 2.1 for Alpha
I ran Linux on a 486 DX for quite some time including providing shells to people on IRC. Don't run X and it's more than powerful enough.
A 486 can handle X just fine. 486's were our main X11 desktop machines at the office in the mid 90's (it has been the year of Linux on the desktop for me since 1995). The challenge is more that most modern X clients won't play well with a slow, memory constrained machine.
I remember when X switched from monolithic server to modular one. I had to buy new GPU because S3 I had wasn't supported. I have bought ATI.
Earlier quoted context omitted.
This is really cool, even if you didn't post I'm glad you mentioned it in a comment. :) I remember compiling Linux kernel on my Cyrix 486SX 25MHz (the one with a disabled-by-default L1 cache!) and it took an hour. Got it on a P60 and it was like 5 minutes. Good times.
Another one of my silly retro computing projects: https://github.com/teknoman117/m68k-fpga-bridge . I wanted to try and make an MMU for it, hence the 68010 specifically (which added some additional data to the bus error exception to allow restarting the failed instruction). I also managed to get someone on utsource to sell me a tray of 386EX33s for like $2 a pop so eventually I can make some 386 systems. I managed to…
I like retrocomputing too, but more virtually: https://jexer.sourceforge.io/evolution.html
I wanted to make a cycle-accurate 286 system once, just because it was such an interesting architecture. Protected mode, but 16 bit, and 16MB max RAM, but with segment:offset addressing. What's not to love about all of that?
One thing I would recommend that I didn't see mentioned is switching to the SLOB allocator in the kernel. It's more space efficient than SLUB or SLAB, but it is slower if you have a large amount of memory. (It's hidden unless you set CONFIG_EXPERT).
The main problem I bumped into for minifying a modern Linux kernel is that so much of the modern Linux ecosystem (systemd, OpenRC, runit, etc.) expects a lot of the networking stack to be enabled, along with cgroups, namespaces, etc. In order to get a minimal Gentoo i486 image to boot, I needed to turn a lot of things on in the tinyconfig kernel. Admittedly, it's hard to image a Linux/Unix system without some form of networking :)
Earlier quoted context omitted.
I really wish cities in the US had those kind of sprawling electronics markets. So cool and useful. Like if you just need a single SPDT switch instead of a 20 pack on Amazon… you can’t do that right now.
Fry's was the closest thing we had, and it was thinly spread at the best of times (particularly outside of California). It didn't really even make it into the pandemic; I remember walking into the Downers Grove, IL store in the Christmas 2019 season and feeling strange at how few cars there were in the parking lot. I walked in, and was shocked at the state of what was an obviously failing store that gave me the willi…
I've often wondered why those places disappeared but then you remember nobody really builds PCs or other electronic stuff except as a hobby and most people are running laptops that can't be upgraded anyway.
Dating myself here ... I ran Linux on my 386SX black and white LCD laptop (including X windows!) back in the early Slackware days 1992-1994. It was easier to do that back then than now... :) Oh,and a grad student friend of mine warned me in 93... "That Web stuff is addictive"... so I avoided it for another 3-6 months and stuck to FTP sites and a bit of gopher/WAIS. :)
> "That Web stuff is addictive" Prophetic declaration of the day. I'm envisioning a great hacker t-shirt: "That Web stuff is addictive... stick to FTP (a friend, 1993)"
Ran like a breeze on a 486DX-33 with 4 MB RAM, xeyes and all. Hard to be believe at the time - a UNIX in my own room! :-O
Earlier quoted context omitted.
Another one of my silly retro computing projects: https://github.com/teknoman117/m68k-fpga-bridge . I wanted to try and make an MMU for it, hence the 68010 specifically (which added some additional data to the bus error exception to allow restarting the failed instruction). I also managed to get someone on utsource to sell me a tray of 386EX33s for like $2 a pop so eventually I can make some 386 systems. I managed to…
These are so cool! :-) I like retrocomputing too, but more virtually: https://jexer.sourceforge.io/evolution.html I wanted to make a cycle-accurate 286 system once, just because it was such an interesting architecture. Protected mode, but 16 bit, and 16MB max RAM, but with segment:offset addressing. What's not to love about all of that?
Admittedly I didn't live through that time period, but reading about them, they are quite interesting. It seems that the main reason they were considered "brain-dead" was because you couldn't run 8086 native and 286 native software at the same time, and backwards compatibility and interoperability started becoming something people considered very important.
Interesting enough that I went and bought a static core 286 (the 25 MHz Harris one) to play with. Since it's a static core I can run it at whatever frequency I want, even if that is only a few hertz.
https://imgur.com/gallery/LKAh7fB https://gist.github.com/teknoman117/342b43db8b79652c1c91e78e...
Things to keep me sane during the pandemic isolation :)