Slashdot Mirror


Historic Linux File Archive Created

jemagid writes "Ibiblio (nee metalab, nee sunsite) has rummaged through all the old CDs and old FTP archives we could find, to put together a beautiful picture of the early days of the Linux community: Historic Linux. The files include snapshots of the early Linux archives including sunsite.unc.edu and tsx-11.mit.edu, and early distributions such as MCC (Manchester Computing Center) and SLS (Softlanding Linux Systems), which were some of the first attempts to make Linux easy to install and use. The early RedHat releases are also included, as is early Suse, Debian, Slackware, and Blade. The early distributions ran on machines as small as 386's with 2-4 MB of RAM, so these could be fun ways to resurrect ancient hardware."

313 comments

  1. Uhh... by grub · · Score: 5, Insightful


    The early distributions ran on machines as small as 386's with 2-4 MB of RAM, so these could be fun ways to resurrect ancient hardware.

    I certainly hope no one intends on putting these old versions on the net lest they become a w4r3z server or DDoS drone..

    --
    Trolling is a art,
    1. Re:Uhh... by Anonymous Coward · · Score: 0

      Not really. Not only are these boxes too slow to do much damage, finding exploits that actually work will be rather difficult.

    2. Re:Uhh... by Anonymous Coward · · Score: 0

      Perhaps the Historic Linux Archive could add famous cracking scripts from days of yore.

    3. Re:Uhh... by thorgil · · Score: 0

      resurrect?!

      my 386 still runs...sometimes

      Victor 386SX 25MHz, 8MB RAM, 387 math processor, 200MB HD, SB16+ 2x CDROM, 48 channel I/O card)
      It rocks!

      --
      Warning: This sig contains a small bug. ==> *
    4. Re:Uhh... by Pieroxy · · Score: 5, Funny

      I actually managed - back in the good old days - to boot up a Linux on a 486 33MHz with 1MB RAM. The only problem is that I couldn't log in: it took the system more than 1 minute to prompt me for my password when I entered my nickname. As the timeout is set to 1 minute, I got prompted for my nickname again, without getting a chance of typing my password!!!

    5. Re:Uhh... by Anonymous Coward · · Score: 0

      Installing Those Old Versions Will Bring Back Those Old BBS's Too! Maybe I Can Give A Use To That Old Dumb Terminal In The Garage...

    6. Re:Uhh... by t0ny · · Score: 0, Troll

      I remember one of the big attractions to linux was supposed to be the ability to make use of old hardware (I have a 386 sitting around here, as well as a 486). Unfortunately, that was never the case from what I could tell- three years ago I tried installing two different distros, and almost fell thru the hole in my ass when it said installation would require over 1gb! If I need a bloated OS that only runs on new hardware, why bother learning a different OS? Its not like I have nothing better to do than go through an entirely new learning curve, especially since Im already at high expert level on MS's OS and products. This isnt really a rant, but for me, I dont see a compelling reason to even try it out, much less switch over.

      --

      Manipulate the moderator system! Mod someone as "overrated" today.

    7. Re:Uhh... by johnnyb · · Score: 3, Insightful

      "and almost fell thru the hole in my ass when it said installation would require over 1gb!"

      Then use a smaller dist. Considering that there are many the size of a floppy, I think you weren't looking hard enough.

      The point about Linux is that you can make it the exact size you need. If you have big needs, get a big dist and a big computer. If you have small needs, get a small dist and a small computer.

    8. Re:Uhh... by Anonymous Coward · · Score: 0

      I certainly hope no one intends on putting these old versions on the net lest they become a w4r3z server or DDoS drone..

      My first PC had a 20 Mbyte hard disk drive ... just enough space for 4-5 MP3's. That's going to be one impressive collectors set. Using a 4xCD-ROM is probably going to be slower than a 56K dial-up line.

    9. Re:Uhh... by sniggly · · Score: 1
      Too slow to do much damage? Take a 386 dx 40, put a linux kernel on it, and make it try to ddos a server you might have.. Or use it to spam your own email.. Youll be surprised.

      Back in the early 90 i knew someone in oz who ran linux on a 386 - he had a couple of accounts for friends and ran a website on it. Really nice. In fact it makes for a pretty ideal PC based firewall given that it consumes less power.

      Finding exploits that work will be SO EASY just check the sources for the nearest buffer overflow near you and youre off to the races.

      --
      Of those to whom much is given, much is required.
    10. Re:Uhh... by IM6100 · · Score: 2, Informative

      Put Slackware on those older machines. Just install the A, AP and D sections if you want a machine that can do basic development and compiling. Also the N section for networking. Be selective in what you install, use the 'menu' selection process to enable just the packages you want, and it will work great. I learned a lot of what I know about TCP/IP networking by having three or four Slackware boxes running on 386sx machines, with wobbly old 3C501 network cards. It was about 30 bucks worth of hardware even back then, and it worked great.

      --
      A Good Intro to NetBS
    11. Re:Uhh... by sniggly · · Score: 1
      Install rh9 or mandrake in minimal install. Many distributions have that option. You wont have a graphics desktop that way but XFree86 isnt really working on anything below pentium class cpus well anyway. Itll run but...

      There are many lightweight window managers for X. Maybe give it a test to install linux + X + fvwm95 on the 486 and see what kind of performance you get:) Theyre really good at being mailservers, firewalls or http servers (good relative to their spu speed :)

      --
      Of those to whom much is given, much is required.
    12. Re:Uhh... by t0ny · · Score: 1, Insightful
      Could someone with no linux skills set up a networkable linux box that boots off a floppy? IMHO, I would have to say a big *NO*.

      And as a matter of fact, I DID try a smaller distro: I tried out both LRP and some other one (forget the name). I had intended to set up the old 386 as a router, but couldnt get really anything at all to work, and especially the network cards.

      Thus, I tried a common distro- I believe it was Mandrake and Red Hat. However, since it has about a 150MB HD (if that), it wasnt even close to being able to work. And hell, if I need to spend money on a bigger HD to get the damn box to work, why dont I just go out and buy a router?

      (which is what I did).

      --

      Manipulate the moderator system! Mod someone as "overrated" today.

    13. Re:Uhh... by Anonymous Coward · · Score: 0

      I actually got Windows 95 to install on a 486 25MHz with 8MB RAM. Took two minutes to load WordPad.

      Seems Windows can beat Linux..

    14. Re:Uhh... by Anonymous Coward · · Score: 0

      Doubt that because 56Kb modem = 7 KB/sec max, where a 1X CDROM is 150KB/sec.

    15. Re:Uhh... by tzanger · · Score: 1

      Um, I'd say forget D entirely and just use Checkinstall and compile them stuff you need on a more modern computer so you aren't spending hours compiling on that 80386 with 2MB of memory.

    16. Re:Uhh... by Anonymous Coward · · Score: 0

      In 1996, I put Slackware on a 486 33 w/16 megs o' RAM.
      I ran XF86 on it too.

    17. Re:Uhh... by princewally · · Score: 1

      Wow, that's powerful. I have a 386 in my closet with 3 mb of RAM and a 42 mb hd.

      --

      -
      "Vengeance is fine," sayeth the Lord.
    18. Re:Uhh... by damiam · · Score: 2, Insightful
      Could someone with no linux skills set up a networkable linux box that boots off a floppy?

      Could someone with no specialized skills set up a networkable router box running any OS that boots off a floppy? Of course not. You try to do a specialized job, you need specialized skills.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    19. Re:Uhh... by Anonymous Coward · · Score: 0

      I used a 486 33MHz running Windows 95 as my main machine for 2 years. Before that, it ran Win 3.11.

      Both versions of Windows ran perfectly.

    20. Re:Uhh... by XO · · Score: 3, Informative

      FreeSCO (Free ciSCO .. not free SCO...) I didn't need any of my Linux experience to get a firewall/router up and running in about 30 minutes.

      I did use a lot of my experience with Linux when I got it installed onto hard drive, and turned my Tandy Sensation I into the web server and email server for my domain, though.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    21. Re:Uhh... by XO · · Score: 1

      Dude, my first computer with Linux was a 386sx/16 with 2MB RAM, 512K of which was not available. so, 1.5MB RAM on a 16MHz computer.. and I ran it through a SLIP connection to the Internet, and ran a MUD with it.

      Never bothered to try X on it (though this was the same hardware that people WERE running X on.. though mostly the people with the blinding speed 33 MHz 386's, and with at least -4- MB RAM) simply because downloading X at 2400bps was insane.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    22. Re:Uhh... by CentrX · · Score: 2, Informative

      Red Hat and Mandrake are pretty bloated, even their minimal installs. Try Slackware or Debian. The initial, basic installs are much smaller, and they try not to be bloated.

      --

      "The price of freedom is eternal vigilance." - Thomas Jefferson
    23. Re:Uhh... by t0ny · · Score: 1
      As far as what is commonly used in a business environment, would I be better off learning Slackware or Debian?

      Also, which one is more
      "newbie" friendly? Im not a networking newbie, so I have no problem dealing with routing, subnetting, or anything else, but I dont know linux.

      Actually, the reason I tried starting with Mandrake was I heard their documentation was good, and I also wanted to use Bastille.

      Never mind, I just answered my own question on that one by opening a window to Bastille's site. Thx for the advice.

      --

      Manipulate the moderator system! Mod someone as "overrated" today.

    24. Re:Uhh... by cscx · · Score: 1

      The answer, sadly, is OpenBSD. Small, fast, and secure.

    25. Re:Uhh... by Anonymous Coward · · Score: 0

      Wow, my mother stole a PC just like that from the local school!

    26. Re:Uhh... by fruey · · Score: 2
      Since when does 'username' get munged to become nickname? You been hanging out on IRC too long, friend.

      Oh, and the prompt is
      Distro name / kernel version / witticism
      Login:

      --
      Conversion Rate Optimisation French / English consultant
    27. Re:Uhh... by Anonymous Coward · · Score: 0

      I know, she showed it to me when I had her!

    28. Re:Uhh... by Daengbo · · Score: 1

      BBIAgent requires nothing. Just go to the web page, fill in the info about your computer and network, and download a router. That's it.

    29. Re:Uhh... by Anonymous Coward · · Score: 0

      yep and might as well dig up an old version of SciTech Display Doctor for Linux - circa 1999 while your at it. The latest version Scitech SNAP supports some old cards that came in these systems but requires XFree86 4.0.2 or later.

      http://www.scitechsoft.com/ftp/snap/linux/

    30. Re:Uhh... by CentrX · · Score: 1

      I would say Debian and Slackware maybe equal on the first count, with Debian probably edging out Slackware, as being more commonly used in a business environment. Compared to Red Hat, though, they're not used nearly as much. Debian is definitely more newbie friendly than Slackware. Some people find the Debian installation difficult, but in terms of the setup that you get out of it, Debian is far easier to maintain, and the software is stable and cohesively integrated with the rest of the system. Installing packages, or even upgrading the entire distribution (without rebooting no less) is handled by a comprehensive packaging system that makes it a breeze. There's plenty of documentation for Debian, and there's a debian-user mailing list you can find information about on the debian.org website. Depending on what you mean to do in a business environment, Slackware is good for learning how Linux fundamentally works. You can think of it as a sandbox with few package relationships and tools, so if you really want to be forced to learn Linux, go with that.

      --

      "The price of freedom is eternal vigilance." - Thomas Jefferson
    31. Re:Uhh... by Anonymous Coward · · Score: 0

      Oh you are no fun anymore

  2. Beautiful Picture? by Hayzeus · · Score: 4, Funny

    I remember trying to install from those same SLS diskette images downloaded from Rusty 'n Edie's at 9600 baud. It was not a pretty picture.

    1. Re:Beautiful Picture? by kaszeta · · Score: 5, Interesting
      I remember trying to install from those same SLS diskette images downloaded from Rusty 'n Edie's at 9600 baud. It was not a pretty picture.

      Indeed, I still have a whole shoebox of floppies that (if they can still be read) consist of the current Slackware version in 1993/94. I managed to get many a free meal in exchange for letting folks borrow the box to do a Linux install. Those were the days.

      Then again, I've got better museum pieces than that, including a 486 still running Debian 0.93R5 (that even made 666 days of uptime in '96 or '97 before a power outage took it out), although it doesn't really do much other than sit there. Doing anything with it stopped being the point a long time ago...

      But really, it's rather interesting that someone is still keeping these old dists around, it's interesting to see what happened when.

    2. Re:Beautiful Picture? by Hayzeus · · Score: 4, Interesting

      Yeah -- the early TCP stack was a disaster, and as I recall there were major problems with serial port handling. I used BSDI for my internet/UUCP/file server needs basically until linux kernel 1.2 came out, at which point I switched permanently over to Linux (Yggdrasil distro , I think).

    3. Re:Beautiful Picture? by RancidBeef · · Score: 1

      Cool! I still use as scratch disks some of the 50-odd disks I used to download the SLS distribution back in '93 or '94. Some of them are still labeled "SLS X3" or "SLS N2" or somesuch. I was just wondering the other day if these old distributions had been saved somewhere for historical curiosity.

      I still remember a good part of a Saturday I spend at work using four machines to format, ftp, and copy floppies. As I would finish starting an operation on the fourth machine, the first one would just be finished, so I'd repeat the cycle. I have to say downloading an ISO image today is much easier!

    4. Re:Beautiful Picture? by Havokmon · · Score: 3, Funny
      I remember trying to install from those same SLS diskette images downloaded from Rusty 'n Edie's at 9600 baud. It was not a pretty picture.

      Umm YEAH Beautiful Pictures!

      Apparently you weren't looking in the right section of Rusty 'n Edie's BBS ;)

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
    5. Re:Beautiful Picture? by dlosey · · Score: 1

      Umm YEAH Beautiful Pictures!

      Beautiful pictures, if you were lucky enough to have a 256 color CGI monitor! Back when in my youth, we had green screen monitors and black and white TVs. We thought that was 1337!

    6. Re:Beautiful Picture? by Havokmon · · Score: 1
      Beautiful pictures, if you were lucky enough to have a 256 color CGI monitor! Back when in my youth, we had green screen monitors and black and white TVs. We thought that was 1337!

      Aww dude.. you're embarrassing yourself.

      CGA = 4color
      EGA = 16color
      VGA = 256color

      Even if you had a 286, 640kb, and CGA - HP Deskjet's printed those pics just fine ;)

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
    7. Re:Beautiful Picture? by JUSTONEMORELATTE · · Score: 1

      Heh heh -- My employer at the time was fat-pipe connected and one of the Sun machines had a floppy drive.
      I downloaded the SLS floppies from tsx-11 over the course of a few days, then dd'ed them to a giant stack of floppies.
      When all was said and done, the cobbled-together 386 (with 387-16 co-pro! w00t!) had a whopping 4Meg of ram and a 120Meg hard drive, but it ran X windows, dialed in at 2400b via SLIP, and registered itself on the work network.
      NFS over dialup, on the other hand, wasn't that great of an idea.

      ps: Joe, if you're reading this, thanks for the memories and get back to work. *(slacker)*

      --

    8. Re:Beautiful Picture? by astyanax · · Score: 1

      He probably means Hercules graphics, was there an acronym HGA? :)

    9. Re:Beautiful Picture? by Havokmon · · Score: 1
      He probably means Hercules graphics, was there an acronym HGA? :)

      Was Hercules 256? I never had one..

      I first thought SGI.. that would probably be 256 ;)

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
    10. Re:Beautiful Picture? by Joheines · · Score: 1

      Hercules was black/white, but at 720x350 "HiRes".

    11. Re:Beautiful Picture? by kindbud · · Score: 1

      Term worked pretty good, if you could figure out the right escape sequences for your particular dialup shell account. Remember when having a Netcom shell account was cool?

      --
      Edith Keeler Must Die
    12. Re:Beautiful Picture? by technos · · Score: 2, Informative

      Perhaps the fellow meant MCGA? It was out on the market first, and if you bought an IBM name brand it was what you got.

      Quick rundown..

      MDA/Hercules = 2 colors, 720x360ish
      CGA = 4 colors, 160x200 usually.
      EGA = 16 colors, up to 640x350.
      MCGA = 256 colors, up to 720x400
      VGA = 256 colors, 320x200.
      SVGA, 256 colors, up to 1600x1200. Memory bound and all.

      Then there were the ones only computing professionals bought.

      RGBI = 16 colors, up to like 640x320.
      8514 = 256 colors, 1024x768.
      EGA-II = 64 colors, 640x400.
      XGA = 16 colors, 1024x768..

      Seem to remember another one around 1985-86, PGA, that was capable of doing 640x480x16bpp.

      --
      .sig: Now legally binding!
    13. Re:Beautiful Picture? by IM6100 · · Score: 1

      Hell, I have hardware of that vintage, well, it's Sparc hardware, that still does useful things. You stick your basic stuff on a NFS server on such a box. I do it with NetBSD, though.

      --
      A Good Intro to NetBS
    14. Re:Beautiful Picture? by Anonymous Coward · · Score: 0

      and don't forget:

      Amiga NTSC 640x400 Interlaced 60Hz 4096 Colors - 1984
      Amiga PAL 640x512 Interlaced 50Hz 4096 colors- 1984

      PeeCees really sucked back then. PeeCees: Double the price of their nearest competitor, so they were obviously better... consumers are REALLY STUPID.

    15. Re:Beautiful Picture? by tbuskey · · Score: 1

      Hercules 720x348 2 colors
      MDA text only
      CGA 4 colors 320x200
      VGA 640x480 x16(?) also Square pixels
      I think XGA could do 256 colors too
      PGA was about VGA era.

    16. Re:Beautiful Picture? by technos · · Score: 1

      Thought you could do evil tricks with the real IBM MGA boards to make them do graphics.. I know internally they were just drawing indivitual pixels to a framebuffer at least.. Happened to recall they had a res spec, so I peeked, saw it was the same as Herc (2 pixels diff) and lumped them.

      Yeah, goffed the CGA res.. Where I remembered that from is beyond me, may have been another CGA mode, heh, and xGA did indeed do 256 colors, from a 65K palette. But VGA I know was originally specced only for 320x200x256 or 320x240x256. Anything above that is not real VGA, but VESAs version of VGA.

      --
      .sig: Now legally binding!
    17. Re:Beautiful Picture? by XO · · Score: 1

      I used to have to UUENCODE the tar.gz images, download them using ASCII CAPTURE on my freaking TERMINAL PROGRAM at 1200 or 2400bps .. then UUDECODE them on my home machine, and go from there... LOL!!!!!!

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    18. Re:Beautiful Picture? by Anonymous Coward · · Score: 2, Insightful

      Back in the 386 days, computers didn't come with a whole heck of a lot. How do you download anything when you don't have a terminal program?

      I accidentally wiped out the hard drive on my 386-16. I had enough of a DOS install disk to reformat the drive, but that was about all. The only other thing I had was a modem and a (set of?) Quickbasic disk(s).

      So I ended up writing a very simple terminal emulator and a UUDECODER in QuickBasic, used that to download {COMMO}, and used {COMMO} to download enough stuff to get myself working again. (As a tangent to my tangent, Commo is probably the tightest, fastest comms program ever written, 100% in assembler and very, very customizable. Not sure if I ever registered it, I was very poor back then. Bad me.)

      But even that pain (took me a weekend to A) write the term program, and B) use that term program to find docs on UUENCODE, and C) implement a local uudecoder) is NOTHING compared to the pain of trying to get early Linux working. I installed an SLS distro in this same timeframe on the same computer, and it took me TWO WEEKS to get an XF86Config file that worked, and I hosed a monitor doing it. (It's possible I might not have tried X until Slackware, but I definitely did screw up a monitor, whether it was with SLS or with Slack.) The HOWTO was very very clear that I was doing dangerous things, so I blame nobody but myself.

      And I had it *easy* compared to the guys who went before me... I had HOWTOs! MCC and SLS were much better than what preceded them. (did any distros precede them? I don't even remember now.)

      I read an article, long ago, that claimed that at first, there were probably 100 people in the entire world who were technically able to install Linux; they improved it so that 1000 people could do it. Those 1000 improved it so that 10,000 people could do it, and so on -- to the point that my mom could probably install a modern distro, maybe with a little coaching.

      I am a bit ashamed to admit that, while I was able to install Linux in the SLS/kernel .8 or .9 timeframe, and was thus presumably in the tens-of-thousands-of-users range, I had no idea what to DO with it and couldn't improve it for the next generation; I was completely confused by Unix in general and had nobody local to learn from. It excited me, I could see the potential, but about all I could contribute was evangelism. I simply didn't know enough real Unix to be useful. I got it into some companies that wouldn't otherwise have looked at it, so I suppose I was able to help, a little, but I feel bad that I didn't do more.

      I think we forget to say 'thank you' often enough to all the guys who work so hard to make Linux better. It is AMAZING how far it has come; I now use Linux as my work desktop and am absolutely happy with it. I don't miss Windows at all. I still run XP at home, but mostly for games; eventually I'll bite the bullet and switch over to Linux as my main desktop. It wasn't until last year that I really thought Linux was a good replacement, but it's finally 'there' for me. It took 10 years, but it finally happened.

      I know it sounds a little hokey, but THANK YOU to all the devs who have made this possible. You are wonderful!

      I think I will post this as an A/C, since this looks so much like karma whoring. I'm dead serious (hit karma cap LONG ago), but I'll post as AC anyway, just in case.

    19. Re:Beautiful Picture? by Anonymous Coward · · Score: 0

      Almost right, but only the NTSC Amigas ahd 'colors'. The PAL variant had colours.

    20. Re:Beautiful Picture? by operagost · · Score: 1

      The 640x480 mode was the big selling point for VGA over MCGA. It's a real VGA mode. It's what made VGA machines useful for GUIs and MCGA machines not.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
  3. Great historical resource by TopShelf · · Score: 0, Troll

    I can't wait to see how Darl contributed his own special magic to Linux back in the day...

    NOT!!!

    --
    Stop by my site where I write about ERP systems & more
    1. Re:Great historical resource by ZorinLynx · · Score: 1

      I love the site, but it seems all the timestamps on the files have unfortunately been destroyed. {:(

      Everything is dated rather recently.

      I should drop them an email; maybe they can still fix this...

  4. This is great to see. by CrackHappy · · Score: 4, Interesting

    You know, it's always wonderful to see this kind of effort going into preserving some of the history of our technological society.

    It was great to browse through some of these pages and see how our community has changed. As a recent convert to Linux (Mandrake), it's very interesting to see how distributions have changed over the years.

    Great job!

    --
    1f u c4n r34d th1s u r34lly n33d t0 g37 l41d Capitalization really works: i helped my uncle jack off a horse
    1. Re:This is great to see. by RobotWisdom · · Score: 5, Interesting

      I hope to add direct links from my Linux timeline sometime soon.

    2. Re:This is great to see. by pmz · · Score: 3, Insightful


      It's interesting how the tools I take for granted are even older than I thought. This is perhaps the most significant reason UNIX works well, where the system was debugged in small modular pieces, because they had no choice. Sure, vi, for example, has some quirks, but it very rarely fails.

    3. Re:This is great to see. by Nailer · · Score: 1

      You know, it's always wonderful to see this kind of effort going into preserving some of the history of our technological society.

      Yeah, I thought spelling Red Hat that way was cool too ;^)

    4. Re:This is great to see. by XO · · Score: 2, Interesting

      I can tell you for sure, that 'vi' definitely predates 'unix system iii' which was the first one i used, several years before there was a linux.. in fact, all the GNU tools were available. I don't think the GNU people have written a single new tool in 20 years...

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  5. "...fun ways to resurrect ancient hardware." by Anonymous Coward · · Score: 2, Funny

    Ummmm, no,

    Let it go.

  6. Re:Obligatory SCO comment by Joey+Patterson · · Score: 0, Redundant

    Because SCO owns that file archive, or at least the OS that runs it.

  7. Re:Obligatory SCO comment by garcia · · Score: 4, Insightful

    unfortunately, this troll is worthless. SCO claims ownership of Linux code that includes SMP (in fact, they only can claim that code following 2.4.somethingorother is actually not GPL'd).

    If you are going to troll, at least be smart about it.

  8. This means by Trigun · · Score: 1

    I don't have to keep my old slackware install disks around anymore.

    Countdown to the Linus backup quote: 3, 2, 1, go.

  9. Bogus Linux by Anonymous Coward · · Score: 1, Interesting

    Remember that one? It eventually became Red Hat. Seriously.

  10. Re:Obligatory SCO comment by mopslik · · Score: 1

    unfortunately, this troll is worthless

    I'd say the same about SCO's claims in general.

  11. Modern distros on old hardware by i.r.id10t · · Score: 5, Interesting

    Modern distros on old hardware still work - I've got a 486sx33 laptop with 4mb ram (Toshiba Satellite 1910) that had Slack 7.0 and 7.1 on it. I upped the ram to 12mb and it now is a fairly useful machine with Slack 8.1 on it.

    --
    Don't blame me, I voted for Kodos
    1. Re:Modern distros on old hardware by admbws · · Score: 5, Informative
      Slackware recently dropped support for i386, as the ChangeLog explains (scroll down and look for the new GCC 3.3 packages):
      Added the following test packages that we're not ready to merge in yet:
      testing/packages/gcc-3.3/gcc-3.3-i486-1.tgz: This is GCC 3.3, compiled for
      a minimum CPU target of i486. Why i486 and not i386? Because the shared
      C++ libraries in gcc-3.2.x will require 486 opcodes even when a 386 target
      is used (so we already weren't compatible with the i386 for Slackware 9.0
      and nobody noticed :-). gcc-3.3 fixes this issue and allows you to build a
      386 compiler, but the fix is done in a way that produces binaries that are
      not compatible with gcc-3.2.x compiled binaries and which suffer a
      performance hit. To retain compatibility with Slackware 9.0, we'll have to
      use i486 (or better) as the compiler target for gcc-3.3. Therefore, it is
      time to say goodbye to i386 support in Slackware. I've surveyed 386 usage
      online, and the most common thing I see people say when someone asks about
      running Linux on a 386 is to "run Slackware", but then they also usually go
      on to say "be sure to get an OLD version, like 4.0, before glibc, because
      it'll be more efficient." Now, if that's the general advice, then I see no
      reason to continue 386 support in the latest Slackware (and indeed it's no
      longer easily possible). People with 386 machines aren't going to have the
      hard drive space for Slackware 9.1 in any case.

    2. Re:Modern distros on old hardware by MegaHamsterX · · Score: 1

      Hehe, too funny, I have the exact same machine with slack on it as well, how much harddrive space do you have on yours :-)

      Works great for minicom, I still use it frequently, mainly on the TiVo and Cisco stuff.

    3. Re:Modern distros on old hardware by volkerdi · · Score: 3, Informative

      Slackware recently dropped support for i386...

      This is true, but I suspect most of the packages would run on a 386 anyway (but haven't tested this, as the olde-original-slackware-devel-box is mothballed somewhere in the garage). Most of the kernels wouldn't boot on a 386 though, so you'd need to compile your own. The "lowmem.i" kernel is a notable exception.

      BTW, said "old development box": Packard Bell 386SX16/4MB. Glad I'm not using that anymore.

    4. Re:Modern distros on old hardware by Limburgher · · Score: 1
      I have an IBM 486 25 with 20MB ram and a 220 MB hdd running Slack 9.0, and that's with 40MB swap, so really only 180 usable MB hdd.

      It's where I write all my Perl.

      --

      You are not the customer.

    5. Re:Modern distros on old hardware by Crispy+Critters · · Score: 1
      "Modern distros on old hardware still work."

      With Redhat 9, the sound card and video card in my desktop don't work as well as they did with my RH4 distribution. Some days I am this close -->||<-- to reinstalling it.

      I have seen complaints that Linux users are too resistant to change. Well, it worked, and now it doesn't, so why did somebody change it? And yes, I have looked at some of the source code to try to find the problem, but there is no documentation in the code or explication of the code structure, so there is no way someone who isn't already up to his eyeballs in X could make sense of it.

    6. Re:Modern distros on old hardware by Cro+Magnon · · Score: 1
      This is true, but I suspect most of the packages would run on a 386 anyway


      Maybe the command-line stuff would, but it would sure be fun trying to run KDE or Gnome on a 386!
      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    7. Re:Modern distros on old hardware by Mr+Bill · · Score: 1

      I remember trying to get an early version of Slackware running on a 386SX16 with 2Mb of RAM. I let it boot for 2 days while it was thrashing the disks, before I killed it. With 4Mb it ran like a dream.

      I can't remember what version of Slackware it was, but I still have a bunch of the disks lying around. The odd times when I need a blank floppy and dig through my floppies to grab an old one I am always hesitant to grab one labeled A1 or N3... Instead I grab the 'Win95 boot disk' instead :)

    8. Re:Modern distros on old hardware by MadChicken · · Score: 1

      A dream back then.

      It would be fun to see it now, and note the reaction.

      I remember when IBM PCs working from floppies was "tolerable". No more, alas, no more.

      --
      SYS 64738 NO CARRIER
    9. Re:Modern distros on old hardware by Anonymous Coward · · Score: 0

      > my $os = random_os();
      > print "Netcraft confirms it, %d is dying!\n", $os;

      Well, if your sig is any indication, your perl is as crappy as the machine you're writing it on.

    10. Re:Modern distros on old hardware by CrosseyedPainless · · Score: 1

      Uh, the "resistant to change" part refers to you, still using the same sound card and video card you had when RH4 came out.

    11. Re:Modern distros on old hardware by IM6100 · · Score: 1

      KDE and Gnome aren't really 'fun' to run on any platform. They're just another Windows-wannabe and nothing cool.

      The Tab Window Manager is fun. There's even printed documentation for it, O'Reilly volumes 3 and 8. I've run TWM on a Macintosh SE/30, with a 2-bit (monochrome) 512x342 screen. Even FVWM adds too much 'eye-candy bloat' on such a display.

      The Mac was running NetBSD, of course.

      --
      A Good Intro to NetBS
    12. Re:Modern distros on old hardware by IM6100 · · Score: 4, Interesting

      The XFree86 folks decided awhile ago to start abandoning support of older video hardware. So, what ends up happening is that older video cards, that worked fine, start to quit working. I have a nice expensive (for the time) STB Video card that they abandoned awhile back. It uses the S3Trio64 chip. Most of the early S3 video cards are now abandoned by XFree86. It's ironic, because STB was one of the few PC Graphics card makers who were actual members of the X Consortium.

      We used to make fun of Microsoft for abandoning old hardware, and it used to be a pround rallying point for Linux folk that Microsoft 'gave free hardware to Linux' by abandoning support for it.

      Nowadays when I mention things like this about, for instance, Xfree86 abandoning old hardware, or the KDE/Gnome bloat making older machines useless, I get the same comments ("get new hardware!") from Linux zealots that we in the Linux community used to expect from the Microsoft zealots.

      Times sure change.

      --
      A Good Intro to NetBS
    13. Re:Modern distros on old hardware by foonf · · Score: 1

      I have a nice expensive (for the time) STB Video card that they abandoned awhile back. It uses the S3Trio64 chip. Most of the early S3 video cards are now abandoned by XFree86.

      Not true! As of 4.3.0 the Trio chipsets ARE supported. Yes, it did take a while for the driver to be ported to the new infrastructure, but it isn't abandoned. The DAC limitations listed don't apply to the Trio since they all have integrated DACs. Only the very old cards (of which I admit to having one, a VLB 805 card) are still unsupported.

      More to the point, you can install 3.3.6 on any modern Linux system in order to get support for this very old hardware, and you lose little except support for some newer extensions that would be good for little on ancient hardware anyway.

      --

      "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
    14. Re:Modern distros on old hardware by IM6100 · · Score: 1

      Whoah! Now you've cheered me up.

      --
      A Good Intro to NetBS
    15. Re:Modern distros on old hardware by dvdeug · · Score: 1

      Modern distros on old hardware still work

      To enable threading and C++, GCC 3.2 (3.x?) and beyond use i486 instructions. There's an option to compile it with only i386 instructions in 3.3, but that would break backward compatibility and is less efficent. So most everyone has dropped compatibility with 386s.

    16. Re:Modern distros on old hardware by IowaFarmer41 · · Score: 1

      How? I've got an IBM Thinkpad with 8 megs of RAM and 60 megs of HD. I'd love to have it running Linux. Sometimes the screen lights up ;-) Floppy drive, no CD-ROM. No ethernet. So, best way to do this?

    17. Re:Modern distros on old hardware by Anonymous Coward · · Score: 0

      Virtual TWM is even more fun. I use it all the time on my high-end workstation.

    18. Re:Modern distros on old hardware by Anonymous Coward · · Score: 0
      my $os = random_os();
      print "Netcraft confirms it, %d is dying!\n", $os;
      Firstly, you don't need round brackets on a function call even with parameters, let alone without. Secondly, I think you meant printf rather than print. But print "Netcraft confirms it, $os is dying!\n" would have done the job just as well. Variables are interpolated between "double" speech marks, but not 'single' speech marks. Thirdly, I think I've just been trolled. But I may as well post this anyway, since I've gone to the bother of thinking it and typing it.
    19. Re:Modern distros on old hardware by WWWWolf · · Score: 1
      I have a nice expensive (for the time) STB Video card that they abandoned awhile back. It uses the S3Trio64 chip.

      X11 abandoned Trio64? Noooooo! ::gnaws nails::

      My mother has my old machine (P166) that coincidentally has S3Trio64-based card.

      What will happen in... uh, 2010, when Debian releases next version of the distro with no support for this card? Will I have to convince my mother to buy a Mac? =)

      (Well, I'd certainly love to get that machine back one day to use as a firewall and file server...)

    20. Re:Modern distros on old hardware by ajs318 · · Score: 1

      Well, them's the breaks. Supporting old hardware with new software can hold you back. Sometimes you have to make a conscious decision to let go. Mandrake won't run on anything less than a Pentium. Getting it do so, while technically possible, would probably compromise other aspects of its usefulness. You have to make a decision: keep your feet on the ground, or spread your wings and soar. Nobody will actively disrespect you for your decision if you choose not to Get Higher, but you might find it a little lonely down there.

      On the other hand, it's Free software which means the old versions really never went away. You're Free to take the source code for drivers for old cards and port them to the new system. {Unlike proprietary software, where old versions simply are not available -- not legally, at any rate}. Same with the music industry; bands release an album that sounds different from their earlier stuff, fans whinge and say it's not as good as their older stuff, as though somehow something was stopping them listening to their old CDs. Um, best shut up NOW lest I give the BPI / RIAA any evil ideas.

      You basically have three choices. Pay for a ride, walk, or keep standing there with your thumb out and hope someone takes pity on you -- but nobody's ever going to feel sorry for you if they think you're doing the job for them. It's still more choice than you get with Closed Source {pay us for a ride, or stay at home}.

      --
      Je fume. Tu fumes. Nous fûmes!
    21. Re:Modern distros on old hardware by Anonymous Coward · · Score: 0

      I can't speak for XFree86, but my own project that involves driver support for a wide range of hardware occasionally has to toss out entire drivers. Things change in the core, and if a driver doesn't get updated to use it, it eventually breaks. If nobody fixes it, that means nobody cares enough to either do it themselves or find/hire/whatever someone to do it for them. So it gets removed from the tree.

      Sure, you can go back and use old versions, but then you're totally orphaned. The only long-term solution is to suck it up and convert the driver to the new API. This goes for any project. The original author may be long gone, or may not own that hardware any more. In some cases, you may be the only person who cares about having it work. Since you obviously own the hardware and can test changes on it, why not pitch in and help out?

    22. Re:Modern distros on old hardware by IM6100 · · Score: 1
      Well, them's the breaks. Supporting old hardware with new software can hold you back. Sometimes you have to make a conscious decision to let go.


      Wow. Condescension.

      "Nowadays when I mention things like this about, for instance, Xfree86 abandoning old hardware, or the KDE/Gnome bloat making older machines useless, I get the same comments ("get new hardware!") from Linux zealots that we in the Linux community used to expect from the Microsoft zealots."
      --
      A Good Intro to NetBS
    23. Re:Modern distros on old hardware by ajs318 · · Score: 1

      I really don't see your point. A 486DX2/66 isn't ever going to be able to run much more than Windows 95, and there's no way in hell anybody's going to try to get XP on it. But you can't get Windows 95 any more; therefore, your 486DX2/66 is useless. So Bill Gates would like you to think. The capitalists would love for your old hardware to crumble into dust as soon as you bought anything new. Of course, there are alternatives to Windows, and one such alternative is GNU/Linux. We still have old distributions available. Nobody in the Open Source community is complaining about this. It's one of the differences between Us and Them.

      There is a need for GNU/Linux to do useful and impressive stuff with modern hardware, and that is what the mainstream distributors are trying to fill. Keeping old hardware ticking is, and always will be, a niche market. It's simply not feasible to hold back development just for the sake of old machines running at 1/20 or even 1/50 the clock speed of today. Such machines can't handle demanding modern applications. Now, if only we could get the source code, we could maybe cut out some of that nasty bloat by dropping a few non-essential features. But, of course, the GNU/Linux community makes such a jealously-guarded secret of its source code .....

      I certainly think there is room for a "dino distro" that would do something useful with antique boxes. But it's a whole different sport and you cannot hold the mainstream distributors at fault. Nothing is stopping you from being a GNU/Linux distributor. In fact, I'll call you one. You're a distributor. Now you can lump yourself in with the others you're blaming. There - it's your fault.

      GNU/Linux has grown up. You'll find it less painful if you do likewise.

      --
      Je fume. Tu fumes. Nous fûmes!
    24. Re:Modern distros on old hardware by Crispy+Critters · · Score: 1
      "GNU/Linux. We still have old distributions available."

      Which are of little value if you care about security. Security is what drives the upgrade train. Old programs have known security holes. New programs require new compilers and libraries. If you use your machine on a network or over a modem, you can't go with old distributions.

      "It's simply not feasible to hold back development just for the sake of old machines running at 1/20 or even 1/50 the clock speed of today. Such machines can't handle demanding modern applications."

      Like emacs, LaTeX, X, squid, ppp, ftpd, sshd, xfig, xv, and mozilla? Sorry, they run great on a P200 (well, the lizard is marginal).

    25. Re:Modern distros on old hardware by WhiteKnight07 · · Score: 1

      P200? I'm running X 3.3.6, IceWM, Mozilla Firebird, Xmms, Abiword, ect... on a P120 Toshiba Tecra 500cdt laptop with 48 megs of ram and 96 megs swap running Vector Linux 3.2. Playing mp3/ogg files uses about 1/3 of the processor and page renders take a few seconds but its quite usable. At lest enough to post to /., do email, and act as an in car mp3/ogg player when on the go. These are all modern applications for a laptop and this old klunker does the job just fine.

      --


      We're going to make information free Mr. Anderson, whether you like it, or not.
  12. Memories... by tsa · · Score: 4, Interesting

    Slackware 3.1 is there to be found. That must be the second version of Slackware I installed. In that time I have a 25 MHz 486 with 8 MB of RAM, which was pretty fast considering the specs (I also had a 80 MHz AMD 486). Those were the days... Well I must say I'm glad we moved on :-)

    --

    -- Cheers!

    1. Re:Memories... by spaceyhackerlady · · Score: 1
      Slackware 3.1 is there to be found. That must be the second version of Slackware I installed. In that time I have a 25 MHz 486 with 8 MB of RAM, which was pretty fast considering the specs (I also had a 80 MHz AMD 486). Those were the days... Well I must say I'm glad we moved on :-)

      I honestly don't remember what my first version of Slackware was, except that it came on a CD in the back of the first edition of Slackware Unleashed, back in 1997. It worked fine on my 486/66 with 8 MB RAM. And it feels like so long ago...

      Only once did I try loading Linux on a 386. I had found a 386sx machine in a dumpster, powered it up, found that it worked, tried a Slackware kernel boot floppy (kernel 2.0.something), watched the system spontaneouly reboot part way through kernel initialization, turned it off and cannibalized it for parts.

      When I moved in July the do-I-bring-it-or-throw-it-out line was Pentium 233MMX. So all the old 486 and P90 motherboards went in the garbage. The P233MMX system served me well as a grad student. I did my thesis on it, in LaTeX, with Slackware (of course). Very nice.

      ...laura

    2. Re:Memories... by Xunker · · Score: 1

      Funny thing, I have the 4-disc Slackware 3.1 CD set still at home in my bookcase. I bought it at Hastings (a local book/music/software store) in 1996 because it was cheaper than one of the music CDs I wanted -- after all, 4 CDs for $12 is $3 a CD, and I couldn't beat that!

      It installed perfectly on my parents 386/25 with 4MB, and it is, to this day, the only time I've got X to run correctly on the very first try.. though I couldn't tell you how I did it.

      --
      Hilary Rosen's speech was about her love of money and her desire to roll around naked in a pile of money.
    3. Re:Memories... by subsolar2 · · Score: 1
      I honestly don't remember what my first version of Slackware was, except that it came on a CD in the back of the first edition of Slackware Unleashed, back in 1997. It worked fine on my 486/66 with 8 MB RAM. And it feels like so long ago...
      Similar thing here ... I think it was slackware 3.0 that I received with my copy of "Linux Unleashed" 2nd edition. Was running Win 3.1 on a 486-33 with 8MB RAM dual booting to linux on my second 420MB hard drive.

      Was fun ... played with it a bit but did not get serious till I started playing with Redhat 4.2 ... which I put on our first Intranet server at work. I don't think that term was even coined yet.

      - subsolar

  13. a fun way to resurrect ancient hardware... by stratjakt · · Score: 5, Interesting

    ... would be to put something new on it, something the designers of the time would never have concieved. Like the hacking community around the atari 2600 or colecovision, or getting the C64 internet ready with its own ip stack. Make it do something it wasn't meant to do.

    Running a 10 year old linux on a 10 year old computer is just as interesting as running DOS or Win3.0 on it, though only half as useful. (Mod me down if you must, but linux was still very much a toy for comp sci students back then)

    --
    I don't need no instructions to know how to rock!!!!
    1. Re:a fun way to resurrect ancient hardware... by leandrod · · Score: 4, Informative
      > Running a 10 year old linux on a 10 year old computer is just as interesting as running DOS or Win3.0 on it, though only half as useful. (Mod me down if you must, but linux was still very much a toy for comp sci students back then)

      Not really. While GNU/Linux was nowhere nearly as useful as it is today, it could already do things MS Windows can't do today. More importantly, it did so with decent performance and reliability and a compatible API, what means you probably can run much modern software there. Now try running modern software on MS Windows 3.0, or even finding old software to run on it...

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    2. Re:a fun way to resurrect ancient hardware... by appleLaserWriter · · Score: 2, Informative

      but linux was still very much a toy for comp sci students back then

      Linux had a very compitent TCP/IP stack, including SLIP and later PPP. Combine that with X11 and a Mosaic binary, and you had a fast and reliable Websurfer. Even at 14.4k bps.

      As for the biz side, in 1993 I replaced a big IBM RS6000/530 with a dual proc Pentium 100 running Linux. Since there were about 100 dumb terminals on the system, IBM wanted around $100k for an OS upgrade. The Linux box was roughly twice as fast as the aging IBM and cost less than $6k to put together.

      It wasn't until 1995 that I became a CompSci student, and found that completing my assignments was far easier than it would be on Windoze with Borland C or MSVC.

    3. Re:a fun way to resurrect ancient hardware... by Anonymous Coward · · Score: 0

      (Mod me down if you must, but linux was still very much a toy for comp sci students back then)


      Wait... what exactly has changed in the past 10 years?

    4. Re:a fun way to resurrect ancient hardware... by stratjakt · · Score: 0, Troll

      Well, today you can put a small all-but-useless motherboard in a ammo box, install linux, call it an "embedded system" and get it posted to /.

      --
      I don't need no instructions to know how to rock!!!!
    5. Re:a fun way to resurrect ancient hardware... by molarmass192 · · Score: 2, Interesting

      Assuming you're not trolloing, and it is a toy, then you'd better get busy and tell the NSA, US Army, US Navy, NOAA, LANL, Exxon, BP, Ford, Daimler-Chrysler, Citigroup, Morgan Stanely, Merrill Lynch, Caterpillar, Siemans, 3M, Home Depot, Fedex, Sony, Panasonic, Samsung, Sharp, Verizon, Oracle, IBM, Sun, HP, Dell, Cisco, Motorola, Novell, CA, and Borland among others because they obviously didn't get the same information you did.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    6. Re:a fun way to resurrect ancient hardware... by TrixX · · Score: 2, Interesting

      Running a 10 year old linux on a 10 year old computer is just as interesting as running DOS or Win3.0 on it, though only half as useful. (Mod me down if you must, but linux was still very much a toy for comp sci students back then)

      Wrong! I have a 33Mhz 486 DX w/8MB of RAM running two meters at my left. It runs Debian Woody 3 (no old distro) and XFree4. When I'm working w/someone else I boot it up and launch ssh or X remotely.

      I can use a GNOME2 session in that box w/o no problem (scrolling is a little slow, because of the old videocard, but it's very usable).

      I had no need to use an old distro. Debian worked out of the box; I optimized it a little removing VTs, disabling seervices and recompiling a custom 2.2 kernel, but it worked even w/o that.

    7. Re:a fun way to resurrect ancient hardware... by Read+Icculus · · Score: 1

      Too bad you weren't trolling. In my book that's preferable to being a total moron.

      --
      Anti-social? My code is just platform-specific.
    8. Re:a fun way to resurrect ancient hardware... by babyrat · · Score: 1

      in '93 and '94 I was doing all my Uni papers on Linux - I think it was Slackware, on a 486 33 with 8 MB RAM - sweet machine!

      I remember my 4th year project - a 4 MB paper on digital image processing for studying hydrogen bubble formation in the zinc electronwinning process, done in TeX (not LaTeX, just pure TeX). Floppy drive broke and I needed to get the postscript to the Uni network to print.

      Had trouble transferring via xmodem or zmodem, so I used 'cat' on each end of the connection to transfer it. I couldn't believe it worked...but I got it there and printed out just in time.

      It certainly wasn't a toy, and I was by no means a Comp Sci student...just someone who couldn't afford to buy software.

    9. Re:a fun way to resurrect ancient hardware... by IM6100 · · Score: 2, Funny
      Running a 10 year old linux on a 10 year old computer is just as interesting as running DOS or Win3.0 on it, though only half as useful.

      The ten year old Linux system probably has a C compiler on it and other development tools.

      The Windows 3.0 machine probably has Solitaire.

      I guess it depends on your priorities and what you want to do with the machine.
      --
      A Good Intro to NetBS
    10. Re:a fun way to resurrect ancient hardware... by andrewski · · Score: 2, Insightful

      It wasn't until 1995 that I became a CompSci student, and found that completing my assignments was far easier than it would be on Windoze with Borland C or MSVC.

      In stark contrast to today's world, where about the only think that 'programmers' learn at the University (in the first 2 years of CompSci, anyway) is either MS VC++ or CodeWarrior.

      A few years back I asked an instructor of mine if I could use GCC instead of MSVC++ for c coding and was asked 'what's gcc'...

      This is true at damn near any public university, unfortunately. Higher-level students are often given a choice of tools, but not until they've had their brains retarded by years of MSVC++ or Codewarrior...

    11. Re:a fun way to resurrect ancient hardware... by Peter+Simpson · · Score: 2, Interesting

      ... it could already do things ...

      And how! I remember installing Slackware on a 486/33 at work and blowing people away, running Linux with X11, logging into the Unix system and running the schematic capture tool remotely from an xterm :-)

      I was *supposed* to be running it under Win3.1 on the 486/33. Guess which was faster? Yup, Linux/X11. And guess which didn't crash or hang? Yup. That sold me. Unfortunately, my boss was less understanding (both technically and manager-wise) and was not at all amused with what I'd done. He left shortly thereafter.

      BTW, found a CD of Infomagic Linux dated 12/1993. Must have been one of the early dumps of TSX-11 or Sunsite, because I remember distinctly, loading 11 3.5" floppies to install that system.

      Thanks for the memories, Linus! We've come a long way since 1993.

    12. Re:a fun way to resurrect ancient hardware... by (startx) · · Score: 1

      are things really that scary EVERYWHERE, or are you just assuming everyone else's Univeristy is just like yours? Where I attend school, all C and C++ is taught using the GNU Compiler on Linux, or Sun's C compiler on Solaris. There is only one CS class that even introduces MS Visual Studio.

    13. Re:a fun way to resurrect ancient hardware... by Anonymous Coward · · Score: 0

      Voce pode nao achar softs modernos para o Win 3.0, mas o Word 2.0 roda rapido pacas no meu Athlon XP 2GHz!

    14. Re:a fun way to resurrect ancient hardware... by XO · · Score: 1

      Ah, yes, I remember the early days of Linux 0.99w/NET2+SLIP .. i remember my first real coding in linux was the constant hacking that I had to do every time the SLIP (this was all user mode then) driver crashed.. to get it back running, and keep it going for a little longer.. than having to do the exact same thing once someone got SLIP into the kernel.. ugh!!!

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    15. Re:a fun way to resurrect ancient hardware... by voxel · · Score: 0, Troll

      > While GNU/Linux was nowhere nearly as useful as it is today, it could already do things MS Windows can't do today.

      Yes, and MS Windows can do something Linux still can't do today, run Win32 software well. Don't even give me crap about WINE. WINE was crap in 1994 when I first looked at it, and it is crap now when I looked at it a few months ago. It was crap, is crap and will always be crap.

      Oh, and if you don't like my smart ass remark, well, Windows can do network IO completion ports for high performance networking. Linux is stuck with select/poll still, which means wake up the thread, go in a FOR LOOP to check each socket, then do something... SLOW. And Linus still has something up his but with BSD style completion ports.

      - Voxel

      --
      Modesty is one of life's greatest attributes
    16. Re:a fun way to resurrect ancient hardware... by danielrose · · Score: 1

      wasn't win 3.1 16 bit? therefore it also couldnt run Win32 apps, until windows 95 was released at least..
      of course i've been known to be wrong before =D

      --
      i hate pansy republicans
    17. Re:a fun way to resurrect ancient hardware... by Anonymous Coward · · Score: 0

      Win32s gave the ability to run some Win32 programs on Win 3.11.

    18. Re:a fun way to resurrect ancient hardware... by Anonymous Coward · · Score: 0

      I bet current WINE can run a hell of a lot more Win32 programs than Windows 3.11 with Win32s.

    19. Re:a fun way to resurrect ancient hardware... by Viol8 · · Score: 2, Interesting

      "Yes, and MS Windows can do something Linux still can't do today, run Win32 software well."

      And how well does Windows run linux binaries? Or any binaries for others systems for that matter? Oh thats right , IT DOESN'T!

      And don't give me crap about network IO completion , theres a lot more to network speed than that. And remember this is an OS that had multiuser
      logins and remote management (whooo , maan , so advanced!) trumpeted as a big deal by MS recently. I mean jesus , what cave have the techies at MS been living in the last 30 years??

    20. Re:a fun way to resurrect ancient hardware... by Mr.+Gus · · Score: 1

      Well, just for the sake of proving you wrong, I'd like to remind you of Win32s. It was Win32 extensions for Windows 3.1 (or maybe just 3.11+ & WFW).

      All I really remember about it was that I needed it to run Netscape or Mozilla or Trumpet Winsock or some silly internet-related thing around '94 or so. :) I don't think it was quite the same thing as being able to run regular Win32 apps...

    21. Re:a fun way to resurrect ancient hardware... by Overly+Critical+Guy · · Score: 1

      Yep. All for server use.

      Again, it's a computer science toy for people whose hobby is using an OS.

      --
      "Sufferin' succotash."
  14. heh by hyperstation · · Score: 1

    it's just like what we have now...except with no security fixes, lots of bugs, and sploits galore

  15. this is great and all.... by Anonymous Coward · · Score: 0

    but its a complete waste of time.

    1. Re:this is great and all.... by chef_raekwon · · Score: 1

      a complete waste of time.

      you mean the Monty Python movie, right?

      --
      We're like rats, in some experiment! -- George Costanza
  16. Linux Internet Archives by sfbanutt · · Score: 2, Interesting

    I actually have a 6 CD set from Yggdrasilof the 'Linux Internet Archives Winter 1996'. That's about the time when things were starting to become usable by mere mortals.

    --
    I've wrestled with reality for 35 years and I'm happy to say, I finally won out - Elwood P. Dowd
    1. Re:Linux Internet Archives by Dr+Caleb · · Score: 1
      I think I still have as well. And the 5 CD set from the year before. I'll have to dig the source for 'Abuse' out and recompile.

      I haven't played that in years...

      --
      "History doesn't repeat itself, but it does rhyme." Mark Twain
    2. Re:Linux Internet Archives by Anonymous Coward · · Score: 0

      Me too! I used to buy a new edition of the Yggdrasil cd's every 6 months (or so) at the UofToronto bookstore while I was a student. Those CD's were awesome, I remember just flipping through the directories looking for cool software, AND FINDING IT! I owe my honours bachelor's degree in computer engineering to those CD's, in a way.

    3. Re:Linux Internet Archives by Raphael · · Score: 1, Informative
      I actually have a 6 CD set from Yggdrasilof the 'Linux Internet Archives Winter 1996'.

      I still have single CD labeled "Yggdrasil GNU/Linux/X11 Fall '93". This is the oldest CD-based distribution that I have at home. Before that, I used the SLS floppies but I have recycled these floppies in the meantime.

      Saying that all Linux distributions had some rough edges in 1993 would be an understatement, but I was able to play with them on my old 486/33 with a mere 20 MB of disk space. The Yggdrasil CD had a nice option to install only the basic system on the hard disk and use the CD for the parts that didn't fit. Running X11 and emacs from the CD was painfully slow, but it worked. I could even do some real work on that crazy old stuff!

      --
      -Raphaël
    4. Re:Linux Internet Archives by dmaxwell · · Score: 1

      Abuse has been ported to SDL. You may want to dig up the current actively maintained version of Abuse rather than the old version. Nifty game, it has that Psygnosis feel to it.

    5. Re:Linux Internet Archives by buckminster · · Score: 2, Insightful

      I still have the Yggdrasil Fall 94 CD. It got me through a couple of UNIX courses. It was amazing at the time. It kept me from having to drive out to the computer lab or attempt a remote (VERY slow) connection via modem.

      Sure, these old distros had their rough edges, but consider the alternative. Does anyone remember the kind of hoops you had to jump through to get a Win 3.xx system online? Anyone remember Trumpet?

    6. Re:Linux Internet Archives by CausticWindow · · Score: 1

      Turrican!

      --
      How small a thought it takes to fill a whole life
    7. Re:Linux Internet Archives by Anonymous Coward · · Score: 0

      Trumpet Winsock! What *FUN*. I mean, wasn't it fun when your login scripts failed depending on if the PPP login text was "Login:" and not "login:" ?

      Honestly, the best thing Microsoft did was put a TCP/IP stack and dialer into the core of their OS.

      Of course, this is slashdot, and Microsoft shouldn't be allowed to bundle things with their OS if it means driving other companies out of business :P

    8. Re:Linux Internet Archives by smyle · · Score: 1

      You mean you didn't learn like the rest of us to use "ogin:" in your scripts? I started doing that as soon as I figured out why a script somebody else sent me (which caused me to do a double-take) used "assword:" in it.

      --

      Sleep is just a poor substitute for caffeine, anyway. -Bob Lehmann

    9. Re:Linux Internet Archives by Anonymous Coward · · Score: 0

      And when you go to a new ISP and it uses neither Login or login? (username comes to mind..)

      I was trying to make the point that forcing the user to pattern match based on text they would probably have never seen was downright stupid. :)

    10. Re:Linux Internet Archives by IM6100 · · Score: 1

      The Yggdrasil distros from that time period had some extremely annoying bugs, though. If you wanted to install 'the whole thing' on a system, which was the only way for a newbie to not end up in dependency hell, you could select 'only the binaries' in the menu. But the script was broken and it would still try to install all the source as well, overfilling the typical hard drive of the day (definitly overfilling the hard drive *I* could afford at the time.

      Looking back, it seems like Yggdrasil had early hopes of 'owning' the Linux market. They called their first release 'LGX' (for Linux-Gnu-Xwindow) and probably had 'rights' to that name.

      I was much happier when I figured out how to install Slackware from the Infomagic 'Linux Developers Resource' CD set. And the Slackware installation script/method is still my preferred method of installing a Linux system. Not as 'clean' as a base NetBSD install, but still no-muss, no-fuss. I can't abide by any installation method that throws fricking bitmaps up on your screen. Geez, is this Disneyland? I install NetBSD mostly through serial consoles on Sun boxes now anyway.

      --
      A Good Intro to NetBS
  17. Hardware by jargoone · · Score: 5, Funny

    The early distributions ran on machines as small as 386's with 2-4 MB of RAM"

    Damn! Time to upgrade again!

    1. Re:Hardware by Anonymous Coward · · Score: 0

      I came across a poor university student who was still using a 386... in 2000. May the computing gods help his soul (or visa versa).

  18. Re:Obligatory SCO comment by schon · · Score: 0, Offtopic

    SCO claims ownership of Linux code that includes SMP

    No, actually. SCO reps have said in interviews that the alleged infringing code goes back to 2.0, and possibly earlier.

  19. Re:Uhh... Really? by JiffyPop · · Score: 5, Funny

    I don't imagine there are many warez servers with 2MB RAM and 100MB free HD space... Besides that, I would think that as many versions as the underlying libraries have gone through that current cracking tools wouldn't know what to do with something so outdated.

    Maybe you should create an archive of old Linux cracking tools just to even the playing field?

  20. way back... by zapp · · Score: 4, Funny

    before ls had color?!?! ;)

    --
    no comment
  21. this would be much more interesting... by hyperstation · · Score: 2, Insightful

    ...in 10 or 15 years

  22. OLD school linux... by Moe+Yerca · · Score: 1, Informative

    Yeah, that's a great idea, I'll resurrect an old 386 with a 11 year old linux distribution, put it on the net, and watch all 11 years of security holes get exploited! yay!

    I don't recommend that anyone put any of those distro's on a network without a pretty restrictive firewall, but then again, I'm one of those idiots that run a crap load of boxen at home with no firewalls at all. Heck, my passwords are 3-5 characters, that should be secure enough!

    1. Re:OLD school linux... by Anonymous Coward · · Score: 0

      Bullshit.

      It'll be very very difficult to get an exploit that will work. Even if there's an exploit that has been in a program for a very long time and found recently (last 5-7 years), a lot of the shell code might depend on certain libc/glibc versions or ELF.

    2. Re:OLD school linux... by mahdi13 · · Score: 3, Funny
      I'm one of those idiots that run a crap load of boxen at home with no firewalls at all. Heck, my passwords are 3-5 characters, that should be secure enough!

      BR What was your public IP? ;-)
      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    3. Re:OLD school linux... by volkerdi · · Score: 4, Interesting

      Yeah, that's a great idea, I'll resurrect an old 386 with a 11 year old linux distribution, put it on the net, and watch all 11 years of security holes get exploited! yay!

      Doubtful. They'd actually have to THINK about how to attack old holes that have been patched for years. More likely your box will get hit by script kidz trying to exploit modern holes (like buffer overflows with Red Hat specific offsets) and your box will remain unexploited.

      Not that I recommend this, mind you, but there is a certain amount of security that you get from running an OS that nobody uses anymore.

    4. Re:OLD school linux... by fataugie · · Score: 1

      HA!
      I have you beat...I used to do the same as you, no firewalls and such, but would chat on IRC w/BitchX as root..Beat That!

      --

      WTF? Over?

    5. Re:OLD school linux... by deander2 · · Score: 0, Redundant

      Not that I recommend this, mind you, but there is a certain amount of security that you get from running an OS that nobody uses anymore.

      i think there is a name for that...

      "Security through Obscurity"

      ;-p

    6. Re:OLD school linux... by lmfr · · Score: 1
      Think? Why not just go to some archives or use google.

      Sure, some script kiddies won't bother to check the version of the daemons. Some don't even bother to check if it's the same software or OS!

      And I wouldn't put past some to just use every exploit they have on a target machine, no matter how old or for what services or operating system they are.

      And a dedicated attacker would have an easy target.

      But anyway, nothing stops anyone from installing those old distributions and then update the software to a more secure version. Kernel 2.0.x and 2.2.x are still maintained, and new packages, lighter and more secure than the old ones, have appeared.

      Regards,
      Luciano Rocha

    7. Re:OLD school linux... by volkerdi · · Score: 2, Funny

      Not that I recommend this, mind you, but there is a certain amount of security that you get from running an OS that nobody uses anymore.

      Like Slackware?

      Take that trolls, I beat you to it. :-)

    8. Re:OLD school linux... by johnnyb · · Score: 1

      Much better than the current school of thought -

      "Security through Plain Ignorance"

    9. Re:OLD school linux... by Anonymous Coward · · Score: 0

      I have 3 boxen of linux disks in my house were I ranch Moosen, I have many of them. Many munch Moosen.

  23. The REAL value of this... by DickBreath · · Score: 5, Insightful

    The real value of this is to have an archive of the entire development history and community. Out there in the open for all to see. Right there in front of God and everyone. It will help protect Linux from future SCO's.

    --

    I'll see your senator, and I'll raise you two judges.
    1. Re:The REAL value of this... by Anonymous Coward · · Score: 0

      God uses BSD.

    2. Re:The REAL value of this... by holzp · · Score: 1

      No, BSD has too many daemons...

    3. Re:The REAL value of this... by DickBreath · · Score: 1

      No matter what OS is preferred by God, He can still see a public record of the development of Linux. And so should everyone else.

      --

      I'll see your senator, and I'll raise you two judges.
    4. Re:The REAL value of this... by fucksl4shd0t · · Score: 2, Funny

      No, BSD has too many daemons...

      IN my house, with all the kids there and all, BSD stands for Big Shitty Diaper.

      --
      Like what I said? You might like my music
  24. Wow. by J3M · · Score: 1

    So RedHat has always been ugly! [grin]

    --
    Aych tea tea pea colon slash slash slash dot dot org slash
  25. In related news: Women don red hats and go wild by civilengineer · · Score: 3, Funny
    --

    New year Resolution: Don't change sig this year
  26. For god sakes!!! by Anonymous Coward · · Score: 0

    If you run any of these old distros on a system connected to the Internet, PATCH IT! Or yank it off the net. Some of these distros made swiss cheese jealous.

    1. Re:For god sakes!!! by Anonymous Coward · · Score: 1, Interesting

      What, you mean you didn't like sharing computer time with people via the snake, gonzo, and satan accounts?

      The sad thing is that there was a point when most of the people with access to the Internet would only use them for good. If they found a hole, they'd probably patch it up and leave a note in the motd. Now the world is overrun by lusers and everyone has to be armed to the teeth and completely distrustful of every other system out there.

  27. Clearly a hoax... by Anonymous Coward · · Score: 0
    why would a lizardwoman have tits? That's a mammilian trait.

    Now, if you get a contract with realdoll, let us know!

  28. Comment removed by account_deleted · · Score: 5, Interesting

    Comment removed based on user account deletion

  29. Re:Obligatory SCO comment by garcia · · Score: 0, Offtopic

    irrelevant. They released Linux kernel code under the GPL until Linux 2.4.x something. Whether they like it or not, they have agreed that anything prior to that will remain under the GPL.

  30. If you REALLY want to enable old hardware... by Sleepy · · Score: 4, Informative

    Don't mess with one of these old distributions. Seriously... things were broken in the old days, and often you had a bear of a time even figuring out what was wrong.

    And good luck getting any answers!

    If you want to go through the pain of this for HISTORICAL value... do so if you really really want to. Just don't put it on the net, ok? :-)

    If the intent is to squeeze some practical value out of an old system, then ignore these old distros and get something made for the job. One of the "Linux on a floppy" or "peanut" Linux distros would do nicely.

    A really fun exercise would be "porting" all of today's "modern" Bash scripts to run on an embedded or stripped-down system.. nothing works because everyone uses the newer Bash coding styles (while still specifying the script as /bin/sh grrr...).

    A system built around BusyBox and dietlibc is pretty minimal. Just expect to learn a lot of the "old" command switches, and other workarounds...

    1. Re:If you REALLY want to enable old hardware... by IM6100 · · Score: 1

      The 'Linux on a floppy' distros often have design aims counter to what a person with an older system wants to do.

      If a person has, say, a 386 box with 8 megs of RAM and a 340 meg hard drive, he does NOT want a floppy-based system designed to fit on 1.44 megs. He wants a full-service Linux system with C compiler, a GNU toolchain, etc.

      You can get that by installing an older Linux. The 'ancient' Linux distros being archived here are not the same thing, of course. Go for Slackware 3.6 or so for that old 386. At a minimum run kernal 1.2. Kernal 1.2.13 is a damned fine piece of work, one of the 'milestones' of Linux kernal history.

      --
      A Good Intro to NetBS
    2. Re:If you REALLY want to enable old hardware... by Sleepy · · Score: 1

      >a person has, say, a 386 box with 8 megs of RAM and a 340 meg hard drive

      I still do not see how my suggestion is less appropriate for really old systems.

      Either way, you're going to have some "extra work" during or after the install. You'll hit old distro bugs and you won't even be able to get basic newsgroup or IRC support for it. And in the end, you'll likely a possibly insecure system that I wouldn't even trust behind a firewall.

      Linux-On-A-Floppy, for your example, would be a starting point.

      A better choice, since you suggest a specific hardware platform, is Debian. It's *very* easy to get a base system running at 300 megs even on the latest versions (or it was a couple of years ago... I tried it!).

      Debian also provides boot-floppy images in half density and 5.25 inch disks. The tools to make these images are still maintained, so you could modify them if you have a really old setup no one makes images for.

      Plus Debian has "diet libc" and "busybox" packages so you can *really* slim down applications.

      Heck, I have a working Redhat 8.0 system that runs in 340 megs (OK, it's got 128 RAM but I'm positive it could handle 8 MB).

      I don't really know Slackware well to be fair to it, but I don't buy the arguments that older distros are more appropriate than new ones.

      Now, if we are talking XFree86 v4 drivers... that's another ballgame, but XFree86 3.x is still around and as far as I know it's compatible with 2.4x kernels (which run in 8MB).

  31. darn, no TAMU distribution by danimal · · Score: 1

    ah, those were the days. 13 3.5" floppies painstakingly downloaded and dd'd onto floppies with and AIX box.

  32. Snapshots are fine... by JasonMaggini · · Score: 0, Offtopic

    ...but to really remember stuff, ya gotta go with those mirror-image tattoos.

  33. Why no Yggdrasil Linux? by mTor · · Score: 4, Interesting
    That's a great page but I just noticed that they don't have any Yggdrasil Linux distributions. Yggdrasil was the very first Linux distribution I installed and I always get a warm feeling when I see anything related to it.

    Does anyone know where to find a comprehensive archive of Yggdrasil distributions?

    1. Re:Why no Yggdrasil Linux? by Anonymous Coward · · Score: 0

      I have Fall '94 on CDROM. Maybe I should put it up
      on bit torrent ;-)

    2. Re:Why no Yggdrasil Linux? by LinuxTek · · Score: 1

      Yggdrasil was not only my first linux distro, but the first one I could get on CD, which at the time, was the fastest way you could get info.

      I even think I have my old CD around.

      --
      Signatures are supposed to be funny?
    3. Re:Why no Yggdrasil Linux? by Anonymous Coward · · Score: 0

      I have their first beta release on CD...probably have the manual that came with it, too.

      Wonder if they'd like a copy...

    4. Re:Why no Yggdrasil Linux? by smyle · · Score: 1

      If you're not trolling, I'm sure the answer would be "hell, yeah!"

      --

      Sleep is just a poor substitute for caffeine, anyway. -Bob Lehmann

    5. Re:Why no Yggdrasil Linux? by Anonymous Coward · · Score: 0

      Anyone remember when the only copy of Yggdrasil's development version was stolen from Adam's car? I don't think I'm imagining this, but since I can't find a Google ref I'm going AC.

    6. Re:Why no Yggdrasil Linux? by Anonymous Coward · · Score: 0

      Nope...no trolling...it's sitting right in front of me(it took a bit to dig it out of the archive.) No manual or bootdisk though they both appear to be on the disk.

      Will have to look more into the submission process--have to fill out forms :P

      It's 360M and that X11R5-mit-contrib directory is huge! The disk is labeled 'Linux/GNU/X CDROM distribution Beta Test Release Yggdrasil Computing, Incorporated.'

  34. Re:Obligatory SCO comment by iggymanz · · Score: 1

    you're forgetting that SCO's attourney Mark Heise also now claim the GPL is "invalid". So they in fact do threaten earlier Linux distros with their PR campaign at least.

  35. Well... by msimm · · Score: 1

    Of course you'd have to apply security patches that would take you up to 2.4.22. ;-)

    --
    Quack, quack.
  36. fp! by Anonymous Coward · · Score: 0

    fp

  37. I went to Manchester by Anonymous Coward · · Score: 3, Interesting

    While I was there, Microsoft bunged a MASSIVE load of cash to Manchester computing centre.

    Sad really, they ripped out a load of perfectly good sun workstations in my department and put in (then-new) windows nt 4.0 workstation boxes. Nothing worked right after that, but at least MCC got to employ 3x its former staff. :-(

    I wondered why MS targeted MCC so completely (it wasn't until years later they started targeting the Oxbridge crowd) - they must have been out to kill GNU and Linux even then.

    1. Re:I went to Manchester by hughk · · Score: 1
      Manchester had a lot of history connected with computing and was responsible for a lot of new designs. Later they were responsible for an opem ARM core. Certainly their hardware efforts meant building a lot of expertise in low-level system design, i.e. for the writing of operating systems.

      The Cambridge Computer Lab was also on the Microsoft Hit List for similar reasons, but they were less hardware but more operating systems and networking (remember the Cambridge Ring was the forerunner of the token-ring).

      Whether or not either location was still relevant now is another matter, but their history gave them considerable clout in the since research councils which ran the funding and many of the senior academics 'moonlighted' on things like advising the government's procurement policy.

      From Microsofts viewpoint, this has been a very good investment.

      --
      See my journal, I write things there
    2. Re:I went to Manchester by sprouty76 · · Score: 1
      Actually, it was the Computer Science Department that has most of the history - The Manchester Computing Centre provided computing services to the rest of the University, and was a seperate department (although located in the same building).

      At one point, Manchester had the largest network of Suns in europe outside of Sun itself.

      --

      No, I don't want a free iPod

  38. Debian Archive.. by molo · · Score: 5, Informative

    For those that don't know, there is Debian Archive of older versions. I think ibiblio has this beat with 0.91 Beta though (Jan 94).

    -molo

    --
    Using your sig line to advertise for friends is lame.
  39. Re:Obligatory SCO comment by rwven · · Score: 0

    heh Linus himself said in his interview that he knows the guy who coded most of the SMP stuff... IMO this whole SCO thing has scam written all over it. The uppers in the company are selling off stock like crazy. What does that say to you? Question: If someone does compile in SMP support because they're not using it, how does sco have anything against them?

  40. hey, debian! by jesperht · · Score: 3, Funny

    Wow, and i wondered where they got all the stuff for stable/woddy...

    1. Re:hey, debian! by Anonymous Coward · · Score: 0

      my kingdom for a mod point!

    2. Re:hey, debian! by Anonymous Coward · · Score: 0

      LOL!

    3. Re:hey, debian! by Anonymous Coward · · Score: 0

      I have mod points. Now to decide ... is it insightful or informative?

  41. Huh? by Lumpy · · Score: 5, Informative

    The early distributions ran on machines as small as 386's with 2-4 MB of RAM, so these could be fun ways to resurrect ancient hardware."

    Hmm, I'm running 2.6 Rc1 right now on a 386 with 4mb ram...

    why do I need an old distro to run linux on really slow or old hardware??

    that has always been the magic of linux... pure scalability. and it takes 10 minutes to roll your own single floppy distro.

    --
    Do not look at laser with remaining good eye.
    1. Re:Huh? by stratjakt · · Score: 1

      it takes 10 minutes to roll your own single floppy distro

      If by "roll your own" you mean download a floppy distro and write it to disk, OK.

      I want to see you start from sources and build a floppy distro in 10 minutes. Even if you knew what to do step by step you couldnt do it.

      No more exaggerations!

      --
      I don't need no instructions to know how to rock!!!!
    2. Re:Huh? by Lumpy · · Score: 3, Interesting

      first off, there are GOBS of bash or perl scripts that can do it for you, secondly, there are gobs more embedded linux distros out there.

      and yes, even if I did go step by step from sources, I can get it done in 10 minutes. not a problem at ALL! the kernel, busybox and a couple of directories + /dev points and you are finished. gzip it and put it on a dos diskette with syslinux and you are done.

      --
      Do not look at laser with remaining good eye.
    3. Re:Huh? by RGRistroph · · Score: 1

      I second this post, after all I have done it. The hardest part about the 10 minute deadline would be compiling the kernel, but that takes about 2 minutes on the fastest machines these days.

    4. Re:Huh? by mlk · · Score: 1

      You could compile the Linux kernal on a 386 in under 10 mins... :)

      --
      Wow, I should not post when knackered.
    5. Re:Huh? by tzanger · · Score: 1

      Hmm, I must be doing something wrong... 2.2.something took about 4 hours to do on my 80386DX/33 (with copro!) with 8MB of memory (maxxed out on that old full-size DTK motherboard).

    6. Re:Huh? by mlk · · Score: 1

      That needed a question mark at the end, did'nt it.

      I was questioning his ability to compile the Linux kernal on a 386 in 10 mins (hell less than a few hours, it took my 486 3+ hrs).

      --
      Wow, I should not post when knackered.
    7. Re:Huh? by Anonymous Coward · · Score: 0
      Hmm, I'm running 2.6 Rc1 right now on a 386 with 4mb ram... why do I need an old distro to run linux on really slow or old hardware??

      Well, Debian stable is usually 2 or 3 years out of date so you're probably right. The next Debian stable version should include support for the brand spanking new Pentium Pro architecture.

      OK, I'm just kidding, I use Debian (unstable though). I just have to take a jab at it's slow release schedule. It's as bad as Duke Nukem Forever.

    8. Re:Huh? by Anonymous Coward · · Score: 0

      nobody said they compiled ON a 386.

      dual processor Opteron baby... latest kernel compiles in 1.2 minutes flat... I can get it under 1 minute without modules and unneeded crud in it.

  42. 9600 bps??!! by appleLaserWriter · · Score: 1

    I downloaded my SLS Linux .99pl12 distribution at 2400 bps over two days. When the download finished, I found that most of my floppy images had checksum errors.

    Fortunately, Jana publications imploded the next day, and started hemorrhaging CDs everywhere. I managed to get one and was up and running a few days later.

    At about the same time, I had a borrowed Sun 3/110 runing SunOS 3.x. It was fun to play with the big old sun, but even then Linux seemed much faster and more modern. It didn't hurt that Linux was running on my 486DX-50, while the Sun was a 68020 of some kind.

  43. Why do that ? by Billly+Gates · · Score: 4, Funny
    If you want a taste of old Linux then use Debian. Jeeze.

  44. Linux Pictures by akiaki007 · · Score: 3, Funny

    Anyone else see these pictures on the servers? hehehe, I wonder when these were taken.

    --
    "Time is long and life is short, so begin to live while you still can." -EV
    1. Re:Linux Pictures by advocate_one · · Score: 1
      Linus... He's a real guy... drinks beer... falls asleep in class...

      At least he doesn't dance and sweat profusely... or have a mugshot

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    2. Re:Linux Pictures by advocate_one · · Score: 1
      if you scrabbled around in that directory you will find the accompanying readme file for those gif files...

      Lars Wirzenius took them, but there isn't a date or location given. The date on the original files in
      ftp://nic.funet.fi/pub/Linux/doc/PEOPLE

      is 25th Feb 1993. So anytime before then.

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    3. Re:Linux Pictures by Phexro · · Score: 2, Insightful

      A quick USEnet search on Google shows that they were posted on c.o.l.a. at 1993-02-26 08:16:27 PST by Lars Wirzenius.

      I seem to remember that they were fairly widely distributed (on CD, the Infomagic set in particular) in the earlier days of Linux, along with two .au (Sun audio format, not Australia) files of Linus pronouncing "Linux" in English and Finnish.

    4. Re:Linux Pictures by CrosseyedPainless · · Score: 1

      Swedish, not Finnish. I had that set, too! :)

  45. Re:Obligatory SCO comment by Anonymous Coward · · Score: 0

    it's only invalid if they claim that all shrinkwrap licenses are. That would destroy most companies and their IP.

    I doubt that MS's lawyers would stand for it. I doubt MS would stand for SCO even mentioning something of the sort after all the money they gave them.

    Get real.

  46. Re:LinuS Pictures by akiaki007 · · Score: 1

    I mean Linus Pictures

    --
    "Time is long and life is short, so begin to live while you still can." -EV
  47. Comment removed by account_deleted · · Score: 2, Interesting

    Comment removed based on user account deletion

  48. Who needs that archive by wmaker · · Score: 1

    I still have copies of most of those in my cd case and diskette case :/ matter of fact, that 486 i have in my garage runs redhat 4 on it...

  49. Re:Obligatory SCO comment by Anonymous Coward · · Score: 0

    I doubt it. Such a historic archive, forming the input to a large cluster running a C parser or even a set of scripts based on "diff" and coupled to a rdbms, will be able to establish the origin of EVERY LINE OF CODE added to linux since day zero.

    SCO's claims could be PROVED full of shit. We could account for EVERY LINE.

  50. bastards by Anonymous Coward · · Score: 0

    the day I decide to download gentoo, and you fucker post links to ibiblio.

    thanks.
    bastards.

    1. Re:bastards by hyperstation · · Score: 1

      then use a mirror, genius...

  51. I have some old distros... by 'nother+poster · · Score: 1

    I wonder if the want them. I know I have an August 1994 Walnut Creek CD set. I might even have my old Yggdrasil Plug and Play CD and floppy somewhere. God, but I've been playing with this stuff way too long. ;)

  52. d00d by Anonymous Coward · · Score: 0

    I found this awesome warez server, ftp://127.0.0.1/

  53. Nee? Which language is that? by leandrod · · Score: 1

    Just because one is monoglot^H^H^H^H^H^H^H^Hanglophone it doesn't mean one shouldn't try to write accents when necessary... nee doesn't mean anything, the French word meaning born being nee in the feminine, masculine ne.

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
  54. The bad news: by mblase · · Score: 3, Funny

    By my rapid calculations, ibiblio.org now owes SCO some $756,000 and change.

    1. Re:The bad news: by Anonymous Coward · · Score: 0

      Hah, but I don't think that Linux was even at the point where it could possibly contain any SCO-copyrighted or patented material.

  55. In other news by Anonymous Coward · · Score: 0

    Internet archiving giant Ibiblio reports that downloads of Redhat 1.0 are still outpacing downloads of both FreeBSD 4 and 5 combined.

  56. Re:Nee? Which language is that? by stratjakt · · Score: 1

    Nee:

    as in "We are the knights who say nee"

    --
    I don't need no instructions to know how to rock!!!!
  57. Apple support? by tgburrin · · Score: 1

    Will any of the old distros run on my *NEW* apple I? Is there a software added backspace support?
    :-D

  58. hmmm.... by tekiegreg · · Score: 1

    Well that is a thought, it might be easier to trace SCO's "hidden" code that it claims is within Linux at the earlier versions, making it easier to trace fewer lines of source code. Then maybe we can remove all the code and SCO's lawsuit loses strength. Win or lose though, can't we just get all this SCO misery over with aready....

    --
    ...in bed
  59. Me, too! by don.g · · Score: 1

    I run Debian sarge on a 486sx25 Compaq Contura Aero, with 24MB of RAM (...which the thing isn't supposed to support) and an 810MB HDD. I used to use a 12MB 486sx33 Aero, with a ~250MB disk but it eventually died.

    No, I don't run X - but emacs, perl, g++, vgaspect and kismet (with SVGATextMode) all work.

    --
    Pretend that something especially witty is here. Thanks.
  60. Re:Uhh...they would need.. by gosand · · Score: 3, Interesting
    I certainly hope no one intends on putting these old versions on the net lest they become a w4r3z server or DDoS drone.


    Wouldn't they need a working TCP/IP stack for that? :-)

    --

    My beliefs do not require that you agree with them.

  61. Timeline of Linux devlopment by jbardell · · Score: 1

    Anyone know if there is a timeline anywhere containing the major distros (SLS, YGG, Deb, RH, Slack, etc) with a short list of their major features (ie Kernel ver, GCC ver, libC ver, etc)? If not, I might just have to D/L this stuff and whip one up. Let me know if anyone's interested.

    Also, setting up a box with one of these distros might be a good, albeit outdated, intro into security for the curious.

    1. Re:Timeline of Linux devlopment by orangesquid · · Score: 1

      It would be an interesting experiment to take a very-very-old distro and make it secure.
      It would be even cooler if someone wrote patches for all the exploits found in older code and put up a site where you could download patches and updates to ass-old versions of linux. I have a few ancient boxen which could afford that!
      I would love to see a timeline, though.

      --
      --TheOrangeSquid Is it any wonder things seem so awry? We swim in a sea of confusion and don't have to think to survive
  62. I can donate... by warpSpeed · · Score: 1
    My first Yggdrasil CD.

    Ahh, the fond memories of trying to find a SCSI card and CD disk drive that was supported. It ran on my third "real" machine, a 386-33 with 8 megs, may it RIP.

  63. Re:Nee? Which language is that? by leandrod · · Score: 1
    > We are the knights who say nee

    This one flew over my head...

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
  64. Wow!! by MadChicken · · Score: 1

    I found my first Linux distro! I had forgotten what it was. It was xdenu. That got me into Slackware, later on.

    Funny thing was, I copied fstab entries and LILO boot parameters *verbatim* off the 'Net (Gopher? Archie? I forget) and somehow... somehow... I got it up to a crosshatched screen with an "X" I could move around with my mouse. I figured it didn't work and scrapped it. Heh heh. That I got that far and didn't realize it still astounds me.

    This is a very cool library for us oldies.

    --
    SYS 64738 NO CARRIER
  65. Re:Obligatory SCO comment by schon · · Score: 1

    irrelevant

    Not to this discussion :o)

    You said that SCO is claiming ownership of SMP stuff (which is only true if you're talking about the IBM lawsuit). I was just pointing out that SCO has claimed (in interviews) that the alleged infringing code is for other, older, stuff.

    They released Linux kernel code under the GPL until Linux 2.4.x something

    That would be 2.4.13... and (while I agree with you about the GPL) I think that's irrelevant :o)

  66. Historic Linux? by Spudley · · Score: 2, Funny

    Historic Linux? Hmmm.... what should we call it?

    How about "Old Hat Linux" ? :-D

    -- ba-ching! --

    --
    (Spudley Strikes Again!)
  67. Slack 1.1.2 by supe · · Score: 1

    That brought a smile to my face. Still using slackware on a notebook. Doesn't seem that long ago!

    1. Re:Slack 1.1.2 by Skater · · Score: 1

      I use Slackware 9.0 on my Pentium 133 laptop, with 48 megs of RAM. It has KDE 3.1 installed.

      Yes, I can be VERY patient. :)

      --RJ

  68. Re:A quick comparison by Anonymous Coward · · Score: 0

    >Why would anyone willingly pay so much more money for so much less?

    Because Apple doesn't use PC Shits parts?

  69. Ahhh, the good old days. by bytor4232 · · Score: 1

    Ah, the nestalgia, I'm almost tearing up. I remember when I was putting together the Tucows Linuxburg site (now Tucows Linux, can't speak for the quality now, haven't been with Tucows for three years) I used to visit Metalab several times a day. Before Freshmeat there was only one place to get your gear kiddies. Real men used Metalab! How I miss those days. I went through every directory on Metalab to build Linuxberg! What a great site!

    --
    -- 4 8 15 16 23 42
  70. SCO Derived Linux Version by acousticiris · · Score: 1

    Wait a minute, I went looking through the archive and I didn't see this version of Linux that was derived from SCO Unix.
    I thought Darl said that all operating systems were derived from SCO Unix? Since this is undoubtedly the case (because Darl McBride said so, and he is a smart man) then this archive is incredibly incomplete...

    --
    "God is dead!" - Nietzsche
    "Nietzsche is dead!" - God
  71. Finally... by Nissyen · · Score: 1

    Finally the rpms I need to rebuild my redhat 4.2 distro.

  72. Re:Nee? Which language is that? by numark · · Score: 1

    Actually, it's "We are the knights who say ni".

    --
    Want Slashdot headlines on your site? Try SlashHead
  73. Re:Nee? Which language is that? by shepd · · Score: 2, Informative

    >Just because one is monoglot^H^H^H^H^H^H^H^Hanglophone it doesn't mean one shouldn't try to write accents when necessary... nee doesn't mean anything, the French word meaning born being nee in the feminine, masculine ne.

    When a foreign word is anglicized, it typically loses its accents. See resume (the paper kind), for example. If you don't like how english operates in general, I humbly suggest you don't use it.

    FYI: Nee is certainly a valid english word without the accents. Look it up before flaming next time. To REALLY bug you, noel requires no accent, also.

    --
    If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
  74. What sucks is by astyanax · · Score: 2, Informative

    that the date stamps are not preserved. I was looking at the old SLS distributions and all the date stamps say September 2003. You want to see 199[1234] for it to be really 3117 retro :)

  75. BSD historical archives? by stanwirth · · Score: 1

    This is interesting, because I was just searching for some old BSD archives the other day. The reason was, some NZ orgs have been threatened with patent infringment on "a system that encrypts/decripts to a database on a separate server" -- immediately I thought of the old practice of using Rot13 in combination with usenet news (net.jokes) to obfuscate potentially offensive jokes -- well, they didn't say how strong the encryption had to be in order to qualify as "encryption."

    The matter of concern was whether we could obtain evidence that this was being done prior to 1997 or so -- Rot13 was being used in conjunction with rn at least as early as 1983 -- I know, I used it -- but Google's net.jokes archives (a) don't go back that far, and (b) auto-decrypt the Rot13 jokes in its archives.

    So, while it's not a matter of burning importance at the moment, it would have been nice if I could have grepped out the source for an historical version of rn from, say, 4.2 BSD, to definitively prove that this technology existed long before the patent claim this org was being hit with. As it was, they took my word for it at the org, and heck if we have to dig out some old 1600 BPI tape to prove the point, guess that's what we'll have to do.

    This is why I think that the historical versions of Linux on the net is a really, really good thing, and wish that there were also 4.2 BSD, 4.3 BSD, Unix V6, SysIII and SysV historical sources available as well. Not only to invalidate SCO's claims, but a whole host of frivolous patent suits.

    1. Re:BSD historical archives? by Anonymous Coward · · Score: 1, Informative

      Ummmm... There are, I'm running a PDP-11 emulator with 2.11BSD on it. The 4.2 sources are available under caldera's ancient unix license.

      Also, the 4.4BSD-Lite2 sources are in the FreeBSD CVS tree.

      see: http://www.tuhs.org/

    2. Re:BSD historical archives? by stanwirth · · Score: 1

      Thank you!!!!

      ... who was that masked AC? I almost didn't get a chance to thank her!

    3. Re:BSD historical archives? by XO · · Score: 1

      So, by Google auto-decryptying the text contained on those old newsposts, it is now in violation of the DMCA.

      All your Google are belong to us.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  76. Redneck Linux? by MattW · · Score: 1

    I think it might be time to go digging for the redhat installer version which had Redneck as a language choice. Go easter eggs!

    "Y'all sure ya be wantin' to be overwritin' them thar partitions? Y'all won't be gittin' much data back off 'em after."

    1. Re:Redneck Linux? by Anonymous Coward · · Score: 1, Interesting

      it was one of the 5.x versions of RH that had the redneck language option. 5.1 or 5.2 I believe

    2. Re:Redneck Linux? by cant_get_a_good_nick · · Score: 4, Interesting

      Wasn't quite an easter egg; it was both out in the open, and had a use. That was there first version of their installer that supported multiple languages. At that time, they didn't have translators to do a polished second language, so they came up with Redneck. I always installed in Redneck, and put them thar shiny thing in that fancy cupholder tray.

      I doubt if "corporate" RedHat would do this now. I doubt if many folks shelling out $2500 for Linux would appreciate the beauty that is Redneck.

    3. Re:Redneck Linux? by Anonymous Coward · · Score: 0

      My recollection was that existed only for 5.0; I have all of those old versions at home, so I can check...

  77. Japanese woes. by Rank+Amateur · · Score: 1

    Interestingly, JE in the archives corresponds to Japanese -- it's replete with massive howtos on tweaking linux to work in a Japanese environment.

    I've used these howtos up until recently -- the pace of change in the Japanese environment has been glacially slow (but is catching up rapidly).

    Still, the Japanese software used by the major distros, such as RH and Mandrake, is substandard in comparison with what Microsoft and the commercial company Just Systems (included with the commercial portion of the RH distro in Japan) have to offer. In particular, the dictionaries for kanji-based words are insufficient -- words that pop up automatically in the commercial kanji programs aren't to be found in Linux yet!

    Wonder if the Korean and Chinese language users experience the same frustrations. It's about time that Linux is brought up to speed in Asian language groups.

    1. Re:Japanese woes. by iantri · · Score: 1

      For those of us who know little about Japanese+computers, could you explain what exactyly it is that you input Japanese kanji? It seems to me that it can't be incredibly convenient..

    2. Re:Japanese woes. by ashitaka · · Score: 1

      ...could you explain what exactyly[sic] it is that you input Japanese kanji

      Actually it can be very efficient. Remember a couple of kanji charcters can convey an entire phrase in English.

      Kanji is input using an Input Method Editor (IME). You type the pronunication of a character using either the regular english keys or the phonetic hiragana keys present on a Japanese keyboard. Pressing the space bar will present a list of characters that match that pronunication.
      You need to know the exceptions, for example, entering "tokyo" will not get you the right characters for the captial of Japan, you need to type "toukyou". (The o's are elongated)

      Modern commercial IMEs use learning and context analysis to allow entire sentences to be converted at a time. For example, typing "watashihaashitatoukyouheikimasu" ("I am going to Tokyo tomorrow") will get you the phrase correctly the first time on most if not all IMEs.
      A fast typist could input Japanese faster then the same English text. (No spaces!!)

      --
      If you don't want to repeat the past, stop living in it.
    3. Re:Japanese woes. by ashitaka · · Score: 1

      Very true, I had Japanese running in various forms on the earlier versions of Windows easier than itis to get it on Linux today. (Win/V anyone?)

      Maybe the big, Japan/China/Korea Linux effort will help...

      --
      If you don't want to repeat the past, stop living in it.
  78. All teary eye by tomstdenis · · Score: 1

    oh I remember back in the day I wrote applications for a 16Mhz 32-bit processor with 256KB of ram...... those were the days... sob sob...

    oh wait that was a last fucking week... It's called a gameboy advanced....

    Tom

    --
    Someday, I'll have a real sig.
    1. Re:All teary eye by tomstdenis · · Score: 1

      What are you in prison or something? My god go get your GED or find anything else to pass your time.

      Oh look, boohoo, you hurt my feelings. Look! a tear... oh wait no that's just me laughing.

      Tom

      --
      Someday, I'll have a real sig.
    2. Re:All teary eye by Anonymous Coward · · Score: 0

      Aw, Tom. Does this mean you don't love me anymore? I'm crushed.

    3. Re:All teary eye by tomstdenis · · Score: 1

      Oh you know I still loves ya. I'm just worried that all the time you spend bad mouthing what me and bubba does will gets in the way of yours edumication!

      Learn your abc's sonny!

      Tom

      --
      Someday, I'll have a real sig.
  79. Older hardware...but why would you want to? by Glowing+Fish · · Score: 1

    I suppose the Edmund Hilary justification works for making a 386 run linux. But at this point, there is really no economic reason to use that old of hardware. At this point the hardware you can get for free is late model pentiums or early pentium IIs.


    I suppose the other reason to use older hardware is because it is more stylish...but the 386s usually came in big big bulky boxes that weren't that attractive.


    There is enough old computer hardware out there that its not really even that original to do something with it...it is not clever, in the same way that retro kitsch like Smurf Dolls are no longer clever.

    --
    Hopefully I didn't put any [] around my words.
  80. Re:d00d IT'S BROKEN by Anonymous Coward · · Score: 0

    i got teh "Connection Could Not Be Established" error ur ftp is teh sux

  81. WHAT THE HELL IS UP WITH THAT NAME?!?! by Anonymous Coward · · Score: 1, Funny

    Who was the genius who came up with the name Yggdrasil? Did one of the developers have a 6-year-old crippled fetal-alcohol-syndrome dribbling drooling mess for a son?

    Developer Father: Hmmm, I need to think of a name for this new Linux...
    Barely Comatose Son: [suddenly and randomly] YGGDRASIL! [proceeds to drool copiously, spasm wildly]
    Developer Father: Eureka! I shall name it 'Yggdrasil', in honor of my retarded son, Billy. Thanks, Billy!
    Barely Comatose Son: GPPPPKKKLLLSKKSKKK SSSUUUUBUBULBLLLLL APBLE JOOZE
    Developer Father: [proudly] *sniff* Yes, apple juice! Apple juice!

    1. Re:WHAT THE HELL IS UP WITH THAT NAME?!?! by ak_hepcat · · Score: 1

      Apparantly somebody didn't do their fact checking, or read up on their Norse Mythology.

      Yggdrasil is the world tree, situated between heaven and hell.

      And I think my Ygg CD is from mar 92.
      I'll have to dig it out of the closet.

      --
      Support FSF: Stop thinking with your wallet, and think with your imagination. (cc/non-commercial)
    2. Re:WHAT THE HELL IS UP WITH THAT NAME?!?! by Viol8 · · Score: 1

      Its just amazing. It its not in English then americans just can't handle it.

    3. Re:WHAT THE HELL IS UP WITH THAT NAME?!?! by Anonymous Coward · · Score: 0

      Apparantly you are unable to handle the English language, so I suggest you stop being such a hypocrite.

    4. Re:WHAT THE HELL IS UP WITH THAT NAME?!?! by Anonymous Coward · · Score: 0

      Be fair. Not many people know much old Norse...

    5. Re:WHAT THE HELL IS UP WITH THAT NAME?!?! by Viol8 · · Score: 1

      It was a typo you muppet. And FYI its spelt "apparEntly".

    6. Re:WHAT THE HELL IS UP WITH THAT NAME?!?! by Anonymous Coward · · Score: 0

      Isn't it irritating when people complain about spelling/grammar and then use incorrect spelling/grammar?

      As for your excuse that it was a typo: "it is" is abbreviated as "it's" and the word "Americans" is usually capitalized. While you might claim that the latter is also a typo, you missed the former twice in the first post and once in the second.

  82. Re:A quick comparison by Anonymous Coward · · Score: 0

    but does it have a shiny apple logo on it?
    i mean, when i'm buying a machine, the first think i look for is aesthetics. i think to myself, "if i put this in my new beetle convertible (turbo, i might add) on the way home, will it detract from the styling of the car?" besides, no computer matches my studio as much as the g4 (those beige computers don't go with _anything_). when i'm not using my mac, i like to listen to music in itunes, and i don't know if amd can even use itunes. besides, steve jobs said that the new lickable interface is faster than windows because it is unix, and you can't just compare megahurts between pc's and powerpc's because it's a 64 bits computer (hence the power) but the non-power windows uses 32 bits only. if you do the math, you'll see that dollar for dollar, the g4 is much nicer looking and has a way cleaner interface than windows.

  83. Re:Nee? Which language is that? by scatterbrained · · Score: 1

    Strangely enough, there is a related rule:

    When a heavy metal band makes up a name, umlauts
    are allowed to be added to normally unaccented
    words

    --
    -- All that's left of me, is slight insanity, whats on the right, I don't know. -- Bob Mould
  84. New users by gustgr · · Score: 1

    That is an important achieviment. New users may download old distros and see how it works.

    It is easier to understand a simple code than a giant code, with huge modifications. That might be usefull to users who want to create their own distros/OS and don't know exactly from where to start.

  85. Pointless nostalgia by daveho · · Score: 2, Insightful

    I started out running Linux in January of 1994, using MCC on my 25MHz 486SX with 4 MB of RAM. I think the entire distribution was about 7 or 8 1.44 MB floppies, which I painstakingly downloaded using bitftp. (Yes, I was on bitnet. If you don't know what bitnet was, be very grateful).

    The machine was too underpowered to run X comfortably (although I did play around a bit with TinyX - made the machine swap like nobody's business); however, I hooked up my VT102 terminal in order to have separate vi and bash sessions. Just poking around trying to figure out what all of the Unix programs did was great fun. yacc? What the hell is that? The best part was gcc; my previous programming experience had been with Microsoft Quick C. Having a development system where my buggy programs didn't cause the entire system to crash was a beautiful thing.

    Anyway, those were good times, and it's nice to see that these old distributions are still around.

    1. Re:Pointless nostalgia by pe1chl · · Score: 1

      I started out running Linux in January of 1994, using MCC on my 25MHz 486SX with 4 MB of RAM. I think the entire distribution was about 7 or 8 1.44 MB floppies, which I painstakingly downloaded using bitftp.

      Well, I started in December of 1992, on a 33 MHz 486DX with 16MB of RAM. The distribution I used was called SNOW and was on about 25 floppies. It included X.

      In fact, X ran quite well on this machine, and with its 800 MB SCSI disk that soared at 2.5 Mbyte/s it was a high-end box for those days. It ran circles around the DEC VAX 6200 we had at work :-)

      I see little history from these days on that "historic" site... maybe if they are really serious about history I can upload them some old stuff.

    2. Re:Pointless nostalgia by fordboy0 · · Score: 1
      Well, I started in December of 1992, on a 33 MHz 486DX with 16MB of RAM. The distribution I used was called SNOW and was on about 25 floppies. It included X. In fact, X ran quite well on this machine, and with its 800 MB SCSI disk that soared at 2.5 Mbyte/s it was a high-end box for those days. It ran circles around the DEC VAX 6200 we had at work :-)
      All you bastards with your blazing fast boxen :) I started in Dec '93 with Slack 1.1.0 - kernel 0.99pl13 on a 386-40 (overclocked to 50!) with 8 megs of ram (I splurged), a 340mb WD Caviar (Splurged again) and a Spider Graphics vid card (Tseng or Trident I dont remember) capable of true color. Being a guy who was in the graphics arts business, it was a must to have true color :)

      I remember my first forage with partitioning for Slack and the wonder of being able to boot from the HD and boot into OS/2 (damn that 30 disc installation SUCKED!), while booting from floppy brought up Slack. Magic I say... I was able to get X up and running, but it was certainly not too usable, and I didn't have any idea what the hell I was doing (not that I'm much better now -lol). My greatest achievement was getting a serial terminal working (my company had a couple they threw away) and having two users at once (a geek friend and myself). Totally blown away :) Oh man, the memories. Sniff...

      My heart is soothed by glancing at my wifes box (har har) which is a nice silver modded case running Gentoo, but it still has a badly discolored yellow-brownish (many packs of smokes and late hours for that!) floppy from that old '386, it will always have the heart of that old machine :-)

      -FB

      --
      Ligaguinggligagiggagoogoogwillgo
  86. Ancient? by TwistedGreen · · Score: 1

    I wouldn't call a 386 ancient...

  87. Cdrom howto Circa 1994-1997 by the_archivist · · Score: 1

    Has anybody got my cdrom howto that was posted to the unix / linux forum on compuSpend during the yggdrasil era (it will be an embarrassing read), it even had my name on it (100025.1162 Dave Caroline) last time I checked years ago it had been downloaded 1200 times. Got a few emails asking for support (perhaps they coudn't read the howto!).
    I've lost the original but I have got a copy that I downloaded in 1997.
    So I don't know my original upload date to compuserve, does anybody know ?
    It was a bastard to get going because the howto's were on the cd and the lilo string was not obvious.
    Still got my cd's and an original Minix.

    --
    while(karma less_than enough_karma){karma++}
  88. Such an abomination to discontinue 386 support by Anonymous Coward · · Score: 0

    Many people (especialy developers like me) run the latest hardware with the latest distribution all-the-while having a virtual 386 emulator and making sure their application runs bug-free on the earlier versions of Linux and other operating systems. BOCHS is an example of a virtual 386 emulator, and I run RedHat 5.2 in BOCHS to make certain my code doesn't break anything. Yes, there are still many purposes for earlier Linux kernels; they are small footprint, not every computer runs at 1.6GHz and sucks 100 watts (Itanium2 comes to mind). Given the nature of Portable Desktop Assistant computing, many are based on the more efficient and simple 32bit 386 design and having lower power consumption with excessive uptime. I have a 486 100MHz PDA I've been building; it's homebrew, dimensions are 2" x 5" x 3", but it is more in-between a tablet computer and a PDA...but still...

  89. Re:Nee? Which language is that? by ironygranny · · Score: 1

    trust me, you're better off.

  90. Perhaps the most interesting application.... by BlabberMouth · · Score: 1

    of this database will be as a tool to trace the roots of all the code that is introduced into linux. This could be very instrumental in the IBM v. SCO case. This project should be expanded to show as much as possible the what has been added or removed from each version and who added or removed it. It may be tedious, but it definitely needs to be done in an age where linux is seeking wider commercial use.

  91. Re:Nee? Which language is that? by cant_get_a_good_nick · · Score: 1

    > > We are the knights who say nee

    > This one flew over my head...


    Monty Python's The Holy Grail

    Some supposedly scary knights that really only say "ni" (or nee, not sure how it's spelled) and people are supposed to run scared.

  92. Re:Nee? Which language is that? by leandrod · · Score: 1
    > When a foreign word is anglicized, it typically loses its accents.

    If it can gain a workable pronunciation without them, yes. But nee without accent becomes something like [ni:], which I not so humbly suggest isn't quite nice.

    About Reference.com, it isn't enough of an authority.

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
  93. Re:Nee? Which language is that? by Anonymous Coward · · Score: 0

    And resume without the accent is pronounced "ree zoom" and cafe without the accent is pronounced "cayfe", yet somehow we all live. Get over yourself.

  94. Re:Nee? Which language is that? by leandrod · · Score: 1

    Monty Python's The Holy Grail

    Thanks!

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
  95. Re:Obligatory SCO comment by Anonymous Coward · · Score: 0

    umm ... don't they kind of screw up the time here? I mean, modern systemV code in ancient linux? I would be interested to see what features that didn't exist in unixware 10 years ago (fun fact - modern sco OSes are only Unix95 compliant) were 'copied' to the linux of that time ...

  96. Re:Nee? Which language is that? by fucksl4shd0t · · Score: 0

    When a heavy metal band makes up a name, umlauts are allowed to be added to normally unaccented words

    Actually, that's just cheesy hair bands, like Queensryche, Motley Crue, and Motorhead.

    --
    Like what I said? You might like my music
  97. Re:Uhh... Really? by marko123 · · Score: 1

    I know a *ahem* friend who downloaded all the H/C/P/V stuff they could find onto floppy disks using their first connection to the internet.

    Now where did I^Hhe put them?

    --
    http://pcblues.com - Digits and Wood
  98. mini-linux by cbdavis · · Score: 1

    I still have a 486slc Mitac notebook running
    mini-linux. No CDROM, 80meg HD. Minilinux
    was a 4diskette linux. It keeps running - I
    dont have the heart to get rid of it.

  99. Old Distro for old hardware? by xchino · · Score: 1


    "The early distributions ran on machines as small as 386's with 2-4 MB of RAM, so these could be fun ways to resurrect ancient hardware.""

    Just to point out even new versions of Linux can still run on a 386. The distro requirements may be more strict, but I have a 386DX with a 450M HDD(from a 486SX) running an LFS firewall. Ok so it has 16MB ram instead of 2-4MB, but still, you don't need an old version of Linux to run old hardware.

    In my opinion this is one of the greatest benefits of Linux, and proves true the old saying "Hardware is only as obsolete as the software it runs"

    --
    Everyone is entitled to their own opinion. It's just that yours is stupid.
  100. Is that the oldest Linux you have? 1995? by Your+Average+Joe · · Score: 0

    Here is a sample of the CD-ROM's I have:

    (04/27/1993 04:37a 617 ANNOUNCE)
    SLS 1.02 is now available on tsx-11.mit.edu.
    It contains 99p9 source and image, and
    replacement boot disks a1.3 and a1.5.
    The new boot disks just fix a few of
    the custom install features. The network
    daemons are now not started until/if a
    NFS install is done. This should save
    some memory. Also, doinstall now prompts
    you to allow changing your IP address.
    A small error message on the tape install
    was also eliminated. Plus a number of
    other small items have been cleaned up.
    If anyone has any more suggestions for
    improvements, let me know. However,
    I will be away for the next 10 days,
    starting Wed.

    Peter

    (04/13/1994 03:38p 531 README)
    INSTALLATION DISKS DIRECTORY

    This is the directory under which can
    be found the disks needed to install
    Slackware Linux 1.2.0. You will need
    at least one bootkernel disk, and one
    root-install disk. Look in the subdirectory
    that corresponds with the size of your
    boot media (1.2 meg or 1.44 meg). The
    README files in the "bootdisks" and
    "rootdisks" sub-directories will give
    you more detailed information to help
    you choose which disks are best suited
    to your hardware.

    ---
    Good luck!

    Patrick Volkerding
    volkerdi@ftp.cdrom.com

    (07/20/1995 01:47p 2,833 README)
    Red Hat Commercial Linux
    Mother's Day + 0.1 Release 1995

    The contents of this CD-ROM are Copyright
    (C) 1995 Red Hat Software and others.
    Please see the individual copyright notices
    in each source package for distribution
    terms. The distribution terms of the
    tools copyrighted by Red Hat Software are
    as noted in the file COPYING.

    --
    Your Average Joe
  101. linux archive... (self plug) by int-21 · · Score: 0

    Nice to know someone else out there is doing this :)
    (i've had my little history archive since around 2001 or so Here
    (http://intra-net1.svcc.edu/linux for the Goatse wary)

  102. disturbing tought... by C0vardeAn0nim0 · · Score: 1

    the last line in SLS 1.2's README is "good luck".

    am i the only one here that finds disturbing when a software wishes good luck before the install begins ?

    --
    What ? Me, worry ?
  103. Re:Uhh... Really? by Anonymous Coward · · Score: 0

    or maybe some crack rocks for your pipe, dumbass.

  104. BSD archive = a graveyard by Anonymous Coward · · Score: 0

    Cos BSD is dead silly.

  105. RedHat 4.2 is historic?? by Anonymous Coward · · Score: 0

    I still have my boxed set here, and I still have it installed on one of my 486's!! lol

    I didn't think it was that historic?? I also have some even older versions of RedHat and Slackware here.

    Now I'm really feeling old... If those releases are historic, then I must be a dinosaur. :)

  106. Boot Floppy + RS232 by da5idnetlimit.com · · Score: 1

    If you can, get the nice little blue cable that came with Dlink (the soft) connect your laptop RS232 (or Printer slot, depending on you cable) and use them as communication device.

    Boot laptop with a floppy distro that includes a terminal and get busy on old literature on telnet and terminal emulation, and get a "server" on you big machine.

    This is how "primitive" networks where done.

    when you term from you laptop, you can "almost ftp" from one computer to the other.

    Best regards, indeed, as I'll enjoy the sight of someone else enjoying 115200 bauds on Com1 for data transmission of large (Mo+) files 8)

    --
    It takes 40+ muscles to frown, but only four to extend your arm and bitchslap the motherfucker
  107. BRU2000 by Anonymous Coward · · Score: 0

    BRU2000 is included in the Red Hat 5.0 directory, isn't this a commercial program included only for those who payd for the official cd?

  108. Re:Nee? Which language is that? by coinreturn · · Score: 1

    Even worse, nee (accented or not - it is a legitimate Scrabble word) means "born". Unless the site was born again (nee is listed twice), it should only have one nee. Note that "born again Christians" probably have two (k)nees.

  109. The SCO Info Minister speaks by Anonymous Coward · · Score: 0

    For the clueless, this supposed archive is another IBM plot to thwart SCO's intellectual property claims.

    The SCO Information Minister

  110. Old-timers subject by geschild · · Score: 1

    How can you tell if a topic is 'historical': You see replies modded up to +5 from users with ID# smaller than 50000. Heck, this is the first time I've noticed more than three replies from users with ID# smaller than 10000...

    --
    Karma? What's that again?
  111. Nyaah nyaah! by Anonymous Coward · · Score: 0

    What a lie. Even 386SX33's with 4MB were fast enough with windoz 95. I even ran a Redhat with 4MB on a 386SX10 and managed to run everything I liked.

  112. Toshiba's UNIX also ran in 4 MB (on a T-3100) by ivi · · Score: 1


    t/pix, I think (I own a legit copy, but
    haven't seen it for a long time... :-)

    3.5" FD-based

    Included devel sys [& maybe text proc'g?]
    was offered to developers with T-3100
    - upgraded to 4 MB RAM - at 50% Off

    (Disc'd cost: about US$ 3,000 for the lot)

    Didn't seem to be -quite- enough RAM...