Well, it wasn't that many 3 1/2 disks:) Luckily the university had a computer lab next door to my dorm and I had to run back and forth with 5 floppies while installing the system:)
does anyone still have a copy of SLS laying around? It might be interesting to show to these newbies how far distributions have come...
We're now in the process of decommissioning our VAX 4000/200 running VMS 5.5-2. Up until March, it was fairly heavily used. Moved everything to Sybase on Linux 2.4.2.
Any thoughts on what to do with a 4000/200 with several (somewhat flaky) RA81/RA82 drives?
I apply that rule to all advertising. I got called by a telemarketer doing a survey of car ads on TV. I figured since I had just bought one, I'd take the stupid thing. After about 20 minutes of asking me inane questions like "which phrases do you associate with the following car companies..." they gave up in what seemed to be the middle. Apparently I wasn't enough of a slave to jingles as they were looking for.
Does advertising work? The older I get the more I think it doesn't.
Its actually quite useful. We've been doing this for years: We have a ton of external links from our site, and every week we get a list of pages which have had content that changed. Its handy for our content staff to determine when a linked site has changed dramatically...
We all saw the death of wordprocessing programs with the advent of the dedicated word processing machines...oh wait, that didn't come true.
General purpose machines are only going to be replaced by special purpose machines in places where a general purpose machine isn't "useful". In this case "useful"=="too complicated for your local boob to handle".
They're mostly used on bigger (physically) vaxen so you can start there. The ones here are for a VAX 4000/200 which is probably going to be decommissioned soon:(
I had a MicroVAX II which used an RA82 in a 19" rack. That is where I learned that you could
indeed fix them with a good socket set [2 drives
with different problems = 1 good drive]
Why Am I reminded of the Mad's invention of the karaoke machine which only played public domain songs, such as "baa baa black sheep", and "ave maria", to avoid paying royalties?
That's not so bad...we had to build a PDP-8 from scratch and then run DEC diagnostics on it to see if we got it right. The final exam consisted of the lab assistant breaking your machine in 5 or 6 ways and you had to fix it in 2 hours. Probably the most frustrating, but rewarding, class I ever took.
My wife wanted me to get one so she could help mow. She's got bad allergies and gas mowers kick up dust and pollen and she's pretty irratable after that. So, we went and bought one and it is pretty cool. Its not nearly as hard to push as the article makes it out, unless you're running over stick or cans or something.
People got tired of playing the expiring-license game on VMS. Looks like MS hasn't figured out that the only reason why people dropped VMS for their products was the cost of maintaining licenses...now with MS doing it, the world will migrate somewhere else...
Anyone else notice the breasts on the screenshot?
on
KDE 2.0 Final Released
·
· Score: 4
While checking out the 2.x screenshots I couldn't help but notice that the 3rd one down has a topless woman. I don't have any problems with it, but it does beg the "subliminal message" selling point: "if you like topless women, you'll love KDE!"
~567M is way too big for just the base
system! Ideally, a system like this would be setup like this:
Base System:
A small (loopback?) filesystem which autoconfigs hardware (or at least allows hardware settings to be saved to a floppy), mounts the thing to run-fs and exec's it
Thing to run:
A loopback filesystem on the CD which contains
all the necessary files for this application (I.E.
base configs, drivers, libraries, etc).
Build Tool:
A program that when given a directory, determines the library dependencies and packs it up into a loopback mountable fs.
Launch Tool:
This is basically the mount-exec part of the base system, but would run on any linux box. You could install the application's loopback filesystem to your hard disk and then run "./launch-me app.fs" to run the game/app/etc from your hard disk
This way the base OS (configuration, etc) is separate from the application, and provides a
consistant platform.
The filesystem is called Files-11. The format on the disk is ODS-2 or ODS-5 (depending on the version).
It is a nice feature, and it is only as space intensive as you want it to be. By default, there
is no limit to the number of backups, but using
set file/version_limit=2 foo.bar you can
limit it to (automatically) 2 versions on the disk. The count is always incremented...so you
can have foo.bar;32 and foo.bar;33 and when a
change is made, foo.bar;34 is created and foo.bar;32 is erased.
There's been times where this would be nice on unix. Didn't RMS put VMS-style versioning on the list reasons why a new OS was needed when the HURD first appeared?
Slashdot Mirror
Shouldn't someone post a copy of the goatse.cx picture with "DOJ" tatooed on his ass?
Well, it wasn't that many 3 1/2 disks :) Luckily the university had a computer lab next door to my dorm and I had to run back and forth with 5 floppies while installing the system :)
does anyone still have a copy of SLS laying around? It might be interesting to show to these newbies how far distributions have come...
I always thought SLS and Yggdrasil were prior to Slackware, or at least very close contemporaries.
Come to think of it, I'm pretty sure that Slackware was a modification of SLS.
Anyone remember? Does anyone have SLS disks anymore?
...and when the doctor said I didn't have worms anymore, that was the happiest day of my life.
- Ralph Wiggum, Windows Admin
Hell, I still call "Tru64 Unix" OSF/1. It drives the support people around here (who seem to get replaced every semester or so) nuts.
As far as clustering goes, looks like compaq is busy supporting work to bring it to linux as well:
http://bjbrew.org/cpq/ssic_linux/index.htm
We're now in the process of decommissioning our VAX 4000/200 running VMS 5.5-2. Up until March, it was fairly heavily used. Moved everything to Sybase on Linux 2.4.2.
Any thoughts on what to do with a 4000/200 with several (somewhat flaky) RA81/RA82 drives?
HP released EOL plans for PA-RISC in order to move everything to IA-64.
Am I the only one hoping that the Hammer series
whomps IA-64?
Does advertising work? The older I get the more I think it doesn't.
http://cm.bell-labs.com/cm/cs/who/dmr/odd.html
Hear hear!
There's been many times when I pasted a snippet of perl from somewhere into my program and ran it...only later did I fix the indentation.
Not to mention, not everyone writes software the same way, so what I think is properly indented may not match what others think
Its actually quite useful. We've been doing this for years: We have a ton of external links from our site, and every week we get a list of pages which have had content that changed. Its handy for our content staff to determine when a linked site has changed dramatically...
Yep, it did. But 3.5 (and 3.51) where dog slow, and in order to do that, they chose to move those modules into the kernel.
General purpose machines are only going to be replaced by special purpose machines in places where a general purpose machine isn't "useful". In this case "useful"=="too complicated for your local boob to handle".
It has to be exit. Exiting the program is an innovation, dammit! Not to mention that its needless bloat...which is also a Microsoft innovation!
I had a MicroVAX II which used an RA82 in a 19" rack. That is where I learned that you could indeed fix them with a good socket set [2 drives with different problems = 1 good drive]
- 622M capacity using 14" platters
- weighs 163 lbs
- can be used as a bench or footstool
- has a locking air-cylinder to hold up the 'hood'
- Can be repaired using tools from your garage.
- Sounds very much like a radial arm saw
3/4" high disk considered sturdy? What is the world coming to?Why Am I reminded of the Mad's invention of the karaoke machine which only played public domain songs, such as "baa baa black sheep", and "ave maria", to avoid paying royalties?
Yeah, the communication overhead is a bit much, but it is getting better.
That's not so bad...we had to build a PDP-8 from scratch and then run DEC diagnostics on it to see if we got it right. The final exam consisted of the lab assistant breaking your machine in 5 or 6 ways and you had to fix it in 2 hours. Probably the most frustrating, but rewarding, class I ever took.
It also makes a neat paper shredder...
People got tired of playing the expiring-license game on VMS. Looks like MS hasn't figured out that the only reason why people dropped VMS for their products was the cost of maintaining licenses...now with MS doing it, the world will migrate somewhere else...
Oh wait, wrong election. Sorry.
While checking out the 2.x screenshots I couldn't help but notice that the 3rd one down has a topless woman. I don't have any problems with it, but it does beg the "subliminal message" selling point: "if you like topless women, you'll love KDE!"
Base System:
A small (loopback?) filesystem which autoconfigs hardware (or at least allows hardware settings to be saved to a floppy), mounts the thing to run-fs and exec's it
Thing to run:
A loopback filesystem on the CD which contains all the necessary files for this application (I.E. base configs, drivers, libraries, etc).
Build Tool:
A program that when given a directory, determines the library dependencies and packs it up into a loopback mountable fs.
Launch Tool:
This is basically the mount-exec part of the base system, but would run on any linux box. You could install the application's loopback filesystem to your hard disk and then run "./launch-me app.fs" to run the game/app/etc from your hard disk
This way the base OS (configuration, etc) is separate from the application, and provides a consistant platform.
It is a nice feature, and it is only as space intensive as you want it to be. By default, there is no limit to the number of backups, but using set file/version_limit=2 foo.bar you can limit it to (automatically) 2 versions on the disk. The count is always incremented...so you can have foo.bar;32 and foo.bar;33 and when a change is made, foo.bar;34 is created and foo.bar;32 is erased.
There's been times where this would be nice on unix. Didn't RMS put VMS-style versioning on the list reasons why a new OS was needed when the HURD first appeared?