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."

65 of 313 comments (clear)

  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 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!!!

    2. 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.

    3. 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
    4. 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.
    5. 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/
    6. 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
    7. 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
  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 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)
    4. 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!
    5. 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.

  3. 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 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/
  4. "...fun ways to resurrect ancient hardware." by Anonymous Coward · · Score: 2, Funny

    Ummmm, no,

    Let it go.

  5. 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.

  6. 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 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.

    3. 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
  7. 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!

  8. 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 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
    4. 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.

    5. 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
    6. 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...

    7. 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.

    8. 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??

  9. 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 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?

  10. 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!

  11. 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?

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

    before ls had color?!?! ;)

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

    ...in 10 or 15 years

  14. 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 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
  15. In related news: Women don red hats and go wild by civilengineer · · Score: 3, Funny
    --

    New year Resolution: Don't change sig this year
  16. Comment removed by account_deleted · · Score: 5, Interesting

    Comment removed based on user account deletion

  17. 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...

  18. 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
  19. 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?

  20. 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.

  21. 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.

  22. 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.
  23. hey, debian! by jesperht · · Score: 3, Funny

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

  24. 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 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.
  25. Why do that ? by Billly+Gates · · Score: 4, Funny
    If you want a taste of old Linux then use Debian. Jeeze.

  26. 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 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.

  27. Comment removed by account_deleted · · Score: 2, Interesting

    Comment removed based on user account deletion

  28. The bad news: by mblase · · Score: 3, Funny

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

  29. 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.

  30. 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!)
  31. 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
  32. 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 :)

  33. 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. :-)

  34. 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.

  35. 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.