Slackware Makes Linux Less Scary
Aaron W. Hsu
find it entertaining.
I have a friend who is working with me on a programming project. She had
never installed Linux on her system before, and since we were doing a lot
of UNIXy stuff, she decided she wanted to take the plunge. I installed
Slackware 13.0 on her laptop, through on some network drivers, some extra
applications I had from my machine for our work, and handed it over to her
with minimal training.
A month or so down the road, she has told me, "I used to be scared of
Linux, but now I am not scared any longer."
There you have it, Slackware for the beginner, and *not* scary her! Oh,
and she was running KDE, but is using many other non KDE programs.
Aaron W. Hsu
--
Of all tyrannies, a tyranny sincerely exercised for the good of its
victims may be the most oppressive. -- C. S. Lewis
bolta...@yahoo.co.uk
"Aaron W. Hsu" <arc...@sacrideo.us> wrote:
>There you have it, Slackware for the beginner, and *not* scary her! Oh,
>and she was running KDE, but is using many other non KDE programs.
I've been using Suse for years though I used to use slackware many moons
ago. I installed slackware 13 recently on my relatively new laptop and
apart from a couple of minor issues it Just Worked. I was very surprised
since although slackware was always very stable there used to be a lot of
manual setup left to do with drivers and the X server , USB devices etc.
It was pretty much plug and play and without the gigabytes of useless
cruft that comes with something like Suse. I'm very impressed so far.
B2003
Joost Kremers
> I've been using Suse for years though I used to use slackware many moons
> ago. I installed slackware 13 recently on my relatively new laptop and
> apart from a couple of minor issues it Just Worked. I was very surprised
> since although slackware was always very stable there used to be a lot of
> manual setup left to do with drivers and the X server , USB devices etc.
> It was pretty much plug and play and without the gigabytes of useless
> cruft that comes with something like Suse. I'm very impressed so far.
well, there's been a lot of effort put into automatic hardware detection and
configuration the past few years in the linux-world in general. udev and HAL
have come (HAL is apparently on its way out again, it seems), desktop standards
have improved, reducing the amount of wheel-reinventing, etc.
--
Joost Kremers joostk...@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)
barnabyh
> bolta...@yahoo.co.uk wrote:
>> I've been using Suse for years though I used to use slackware many moons
>> ago. I installed slackware 13 recently on my relatively new laptop and
>> apart from a couple of minor issues it Just Worked. I was very surprised
>> since although slackware was always very stable there used to be a lot of
>> manual setup left to do with drivers and the X server , USB devices etc.
>> It was pretty much plug and play and without the gigabytes of useless
>> cruft that comes with something like Suse. I'm very impressed so far.
>
> well, there's been a lot of effort put into automatic hardware detection and
> configuration the past few years in the linux-world in general. udev and HAL
> have come (HAL is apparently on its way out again, it seems), desktop standards
> have improved, reducing the amount of wheel-reinventing, etc.
>
>
About 2-3 years ago I would have recommended Mandriva, PCLinuxOS or may
be Zenwalk to newcomers. Now I recommend Slackware to everybody who's
interested. Just as Pat wrote, it is beginner-friendly as long as
*somebody knowledgeable* has set it up. The using part is pretty easy.
And compiling build scripts is not everybody's idea of fun.
Barnaby
--
5 years using Linux (full-time) - and loving it.
notbob
> And compiling build scripts is not everybody's idea of fun.
It's never been "fun", but what software installs have? I can
remember spending just as much time looking for that driver or lib
file on a M$ Windows disc after seeing "new hardware detected". With
the excellent Slackbuilds.org site doing the preliminary shakedown of
source files, it's pretty much painless, these days. A couple
buildscript checks, and maybe a minor edit, the only hassle is how
slow your computer is.
Slackware has always been fairly easy to deal with. provided one can
read and write with even a modicum of competence. If not, there's
always Apple.
nb
Mike Jones
I tend to agree with the sentiment here.
Though learning to tweak configs and hunt around a bit until familiar
with the layout and character of the system, Slackware has always made
sense whereas "My 1st Compyoota" stuff is actually designed to be obscure
and annoying (not to mention practically unsecurable). IOW, Slackware is
worth the effort to learn about, and M$ isn't.
I've never regreted dumping M$ and going Slack. Not once.
--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
Handover Phist
Yeah, but Slackintosh is only at ver 12.1.
--
I'm GLAD I remembered to XEROX all my UNDERSHIRTS!!
goarilla
> On 2009-11-09, barnabyh <inv...@address.org> wrote:
>
>> And compiling build scripts is not everybody's idea of fun.
>
> It's never been "fun", but what software installs have? I can remember
> spending just as much time looking for that driver or lib file on a M$
> Windows disc after seeing "new hardware detected". With the excellent
> Slackbuilds.org site doing the preliminary shakedown of source files,
> it's pretty much painless, these days. A couple buildscript checks, and
> maybe a minor edit, the only hassle is how slow your computer is.
>
pretty slow here :(
all the other pc's have died but maybe this time i should
buy and build my own instead of using handouts
cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 1
cpu MHz : 602.569
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov
pat pse36 mmx fxsr sse up
bogomips : 1206.25
clflush size : 32
notbob
> model name : Pentium III (Coppermine)
> cpu MHz : 602.569
That's smokin', dude.
Till I snagged a 1.5MHz P4 a couple mos ago, I was using a 322 celery
and a 450 PII. I finally upgraded, not because they were too slow for
Slackware, but because web browsers and websites using java/flash/etc
were getting more bloated and I couldn't view online vids. Find a
used P4 box. When my old CRT died, I got a great used NEC CRT and P4
Vaio, both for $40. That's cost effective. Many ppl actually have to
pay to dump these old rigs. Look around.
nb
Grant
My Internet facing http://bugsplatter.id.au/kernel/boxen/deltree/
~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 6
model name : Celeron (Mendocino)
stepping : 5
cpu MHz : 498.487
cache size : 128 KB
...
Plenty fast enough for a simple firewall and ftp/web server with
ssh terminal access -- I updated from a working p166 box simply
to get a better vim editing response on the terminal.
Grant.
--
http://bugsplatter.id.au
Henrik Carlqvist
> cpu MHz : 498.487
Almost 500 MHz, you are lucky! :-)
My DMZ below replaced an old 486 a few months back:
cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 5
model : 2
model name : Pentium 75 - 200
stepping : 11
cpu MHz : 132.635
fdiv_bug : no
hlt_bug : no
f00f_bug : yes
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8
bogomips : 264.60
> Plenty fast enough for a simple firewall and ftp/web server with
> ssh terminal access -- I updated from a working p166 box simply
> to get a better vim editing response on the terminal.
I think my p133 above works fine for its purpose (vpn and ssh access), it
wasn't because of performance problems the 486 was replaced.
However, I still have an old 486 as firewall. As it is running Linux
2.2.18 cpuinfo doesn't say how fast it is in MHz, but it has almost 50
bogomips. I would guess it is a 100 MHz 486DX, don't want to reboot just
to find out.
My fileserver runs on even older stuff:
balrog:~> rsh hydran
connect to address 192.168.43.6 port 543: Connection refused
Trying krb4 rlogin...
connect to address 192.168.43.6 port 543: Connection refused
trying normal rlogin (/usr/bin/rlogin)
Last login: Tue Aug 4 20:55:14 on tty1
Linux 2.0.30.
You have new mail.
Diplomacy is the art of saying "nice doggy" until you can find a rock.
hydran:~> cat /proc/cpuinfo
processor : 0
cpu : 486
model : DX/2
vendor_id : GenuineIntel
stepping : 5
fdiv_bug : no
hlt_bug : no
fpu : yes
fpu_exception : yes
cpuid : yes
wp : yes
flags : fpu vme
bogomips : 33.18
hydran:~>
If I remember right it is a 66 MHz 486DX, that would make sense with 33
bogomips if the 100 MHz 486 DX has 50 bogomips. This fileserver has been
running for many years, but is no longer really used. I think it is
running Slackware 3.1 with an upgraded kernel, there was no
/etc/slackware-version at those old versions of Slackware. I have to use
rsh to login to that machine, ssh wasn't introduced in Slackware until
version 8 if I remember right.
regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost
Mike Jones
I have only ever bought one machine new (or at least the parts of), and
this has been the worst box'o'junk I've ever had. The rest have all been
rebuilds of other people's chuckouts (and a few second hand bits from
market stalls), where dumping it on me was seen as more convenient than a
trip to the tip.
I love the look on people's faces when they realise I'm still running
what they threw out years ago, AND getting better performance from that
hardware than they're getting from whatever they bought to replace it. :)
notbob
> I love the look on people's faces when they realise I'm still running
> what they threw out years ago, AND getting better performance from that
> hardware than they're getting from whatever they bought to replace it. :)
Ain't it a hoot!
I bought my one and only new rig for $1800!!!! ...and that a bleeding
edge 225mmx. Looking back, I musta been outta my freakin mind.
(coulda bought something really useful, like an M1A1 or a beer tree).
Now, I take other people's cast offs and spend almost nothing. That's
TRUE recycling, not that pay-$10-to-ship-to-Mumbai kinda recycling.
Slackware: The GREEN Linux
(Take it, Pat, with my compliments ;)
nb
danube
> bolta...@yahoo.co.uk wrote:
>> I've been using Suse for years though I used to use slackware many
>> moons ago. I installed slackware 13 recently on my relatively new
>> laptop and apart from a couple of minor issues it Just Worked. I was
>> very surprised since although slackware was always very stable there
>> used to be a lot of manual setup left to do with drivers and the X
>> server , USB devices etc. It was pretty much plug and play and without
>> the gigabytes of useless cruft that comes with something like Suse. I'm
>> very impressed so far.
>
> well, there's been a lot of effort put into automatic hardware detection
> and configuration the past few years in the linux-world in general. udev
> and HAL have come (HAL is apparently on its way out again, it seems),
> desktop standards have improved, reducing the amount of
> wheel-reinventing, etc.
And I have spent a lot of effort getting all this automated hardware
detection out again. Setting up X was never more difficult. But now, it
all runs very smoothly, and I am running SL64
Mike Jones
I wonder what the ratio is between Slack on new hardware and Slack on
recycled\reclaimed boxen? The lifespan of hardware must be at least
doubled simply by switching from ™Barbiware to Slack, yes?
Aaron W. Hsu
>I wonder what the ratio is between Slack on new hardware and Slack on
>recycled\reclaimed boxen? The lifespan of hardware must be at least
>doubled simply by switching from ™Barbiware to Slack, yes?
That would be interesting to know. I am running Slackware on a Lenovo T500, which doesn't count for old hardware, I think. :-) I also have it running on a hosted machine that is an AMD Atholon of some kind or another.
Aaron W. Hsu
Auric__
I'm running 12.1 on a 1GHz AMD Athlon. (Multiboot: 12.1, 13, XP, DOS.) It's
my newest machine. Prior to that, it was a ~900 MHz Pentium III. Before that,
10.1 on a 333MHz Pentium II.
--
Misfortune: The kind of fortune that never misses.
Lew Pitcher
(not.m...@email.address) wrote:
> On Wed, 11 Nov 2009 22:02:15 GMT, Aaron W. Hsu wrote:
>
>> Mike Jones <N...@Arizona.Bay> writes:
>>
>>>I wonder what the ratio is between Slack on new hardware and Slack on
>>>recycled\reclaimed boxen? The lifespan of hardware must be at least
>>>doubled simply by switching from â„¢Barbiware to Slack, yes?
>>
>> That would be interesting to know. I am running Slackware on a Lenovo
>> T500, which doesn't count for old hardware, I think. :-) I also have it
>> running on a hosted machine that is an AMD Atholon of some kind or
>> another.
>
> I'm running 12.1 on a 1GHz AMD Athlon. (Multiboot: 12.1, 13, XP, DOS.)
> It's my newest machine. Prior to that, it was a ~900 MHz Pentium III.
> Before that, 10.1 on a 333MHz Pentium II.
I've found that Slackware runs on just about any hardware I throw at it. My
server /used to be/ a scavanged 486 but is now a scavanged 2Ghz Celeron. A
friend recently donated three old systems to me; I don't doubt that I'll
have Slackware up on at least two of them by the end of the week.
--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
Me: http://pitcher.digitalfreehold.ca/ | Just Linux: http://justlinux.ca/
---------- Slackware - Because I know what I'm doing. ------
steveski
> On November 12, 2009 09:49, in alt.os.linux.slackware, Auric__
> (not.m...@email.address) wrote:
>
>> On Wed, 11 Nov 2009 22:02:15 GMT, Aaron W. Hsu wrote:
>>
>>> Mike Jones <N...@Arizona.Bay> writes:
>>>
>>>>I wonder what the ratio is between Slack on new hardware and Slack on
>>>>recycled\reclaimed boxen? The lifespan of hardware must be at least
>>>>doubled simply by switching from â„¢Barbiware to Slack, yes?
>>>
>>> That would be interesting to know. I am running Slackware on a Lenovo
>>> T500, which doesn't count for old hardware, I think. :-) I also have it
>>> running on a hosted machine that is an AMD Atholon of some kind or
>>> another.
>>
>> I'm running 12.1 on a 1GHz AMD Athlon. (Multiboot: 12.1, 13, XP, DOS.)
>> It's my newest machine. Prior to that, it was a ~900 MHz Pentium III.
>> Before that, 10.1 on a 333MHz Pentium II.
>
> I've found that Slackware runs on just about any hardware I throw at it.
> My server /used to be/ a scavanged 486 but is now a scavanged 2Ghz
> Celeron. A friend recently donated three old systems to me; I don't doubt
> that I'll have Slackware up on at least two of them by the end of the
> week.
I'm running 13.0 on a dead badger I found at the side of the road . . .
:-)
--
Steveski
Mike Jones
Wouldn't you be better running Splatware on that?
notbob
> I'm running 13.0 on a dead badger I found at the side of the road . . .
Will it run x windows and fluxbox? If so, I want one!
nb
Auric__
> On November 12, 2009 09:49, in alt.os.linux.slackware, Auric__
> (not.m...@email.address) wrote:
>
>> I'm running 12.1 on a 1GHz AMD Athlon. (Multiboot: 12.1, 13, XP, DOS.)
>> It's my newest machine. Prior to that, it was a ~900 MHz Pentium III.
>> Before that, 10.1 on a 333MHz Pentium II.
>
> I've found that Slackware runs on just about any hardware I throw at it.
> My server /used to be/ a scavanged 486 but is now a scavanged 2Ghz
> Celeron. A friend recently donated three old systems to me; I don't
> doubt that I'll have Slackware up on at least two of them by the end of
> the week.
Most of my systems come from scavenging. My most recent finds are a cheap HP
printer/scanner/fax/whatever and three Compaq servers (80 lbs each! holy
crap!). Previous finds include a half-dozen Sparcs (still have one), some
ancient Macs (3 or 4 Mac 512k, 1 Mac 1MB -- second and third models ever), a
few PCs ranging from 386 to Pentium III, two Pentium laptops, a couple dozen
(!) ancient brick hard drives (20-50 MB each), and a couple of monitors.
...and that's just the crap I kept.
(The things I paid for include a slightly more-modern Mac (from 1992) and a
PIII system to replace the one I'm currently sitting at, the previously-
mentioned PII, which now runs Win2k (and is now my brother's). Cost me $20
each.)
--
There are different kinds of artistry. Yours repels me.
Keith Keller
I thought only VuDu Linux ran on dead badgers.
http://www.strangehorizons.com/2004/20040405/badger.shtml
In either case, I'd think running Slackware on any sort of dead animal
would make it more, not less, scary. Please try to stay on-topic in the
future.
--keith ;-)
--
kkeller...@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
Mike Spencer
steveski <stev...@invalid.com> wrote:
> I'm running 13.0 on a dead badger I found at the side of the road . . .
>
> :-)
Ah, well, I guess now I'll have to put you into my roadkillfile. ;-)
ObSlack: A Pentium-133 is fast enough to run Slack with X and a
window manager but no "desktop environment". A 486 is too slow for
reasonable responsiveness in X. I presently have Pentium (two Toshiba
laptops), PII and PIII in use. Two P4's are in setup to replace the
PII & PIII RSN, mainly to get better performance in mplayer.
--
Mike Spencer Nova Scotia, Canada
Zootal
"steveski" <stev...@invalid.com> wrote in message
news:7m2odhF...@mid.individual.net...
> Lew Pitcher wrote:
>
>> On November 12, 2009 09:49, in alt.os.linux.slackware, Auric__
>> (not.m...@email.address) wrote:
>>
>>> On Wed, 11 Nov 2009 22:02:15 GMT, Aaron W. Hsu wrote:
>>>
>>>> Mike Jones <N...@Arizona.Bay> writes:
>>>>
>>>>>I wonder what the ratio is between Slack on new hardware and Slack on
>>>>>recycled\reclaimed boxen? The lifespan of hardware must be at least
>>>>
>>>> That would be interesting to know. I am running Slackware on a Lenovo
>>>> T500, which doesn't count for old hardware, I think. :-) I also have it
>>>> running on a hosted machine that is an AMD Atholon of some kind or
>>>> another.
>>>
>>> I'm running 12.1 on a 1GHz AMD Athlon. (Multiboot: 12.1, 13, XP, DOS.)
>>> It's my newest machine. Prior to that, it was a ~900 MHz Pentium III.
>>> Before that, 10.1 on a 333MHz Pentium II.
>>
>> I've found that Slackware runs on just about any hardware I throw at it.
>> My server /used to be/ a scavanged 486 but is now a scavanged 2Ghz
>> Celeron. A friend recently donated three old systems to me; I don't doubt
>> that I'll have Slackware up on at least two of them by the end of the
>> week.
>
> I'm running 13.0 on a dead badger I found at the side of the road . . .
>
I tried it on a dead skunk, and although it booted the smell was just too
much...
Viagara let you down? Cialis just doesn't get you up? Load SlackWare on your
manhood, and you will never crash again!
Zootal
"Auric__" <not.m...@email.address> wrote in message
news:Xns9CC14F6739436au...@69.16.185.250...
I'm running 13.0 on a 1.2GHz, and a couple of 1.667GHz Semprons, FoxCon K7S
boards. Stable as a rock. And I run Slack 12.2 on my old Toshiba 1415 s173
laptop. Also works very well. Tried to get a wireless nic working with XP on
the laptop yesterday. Got tired of it blue screening on a regular basis
(thank you, Microsoft). Boot to slack, start KDE, solid as a rock. I wish I
had a dollar for each time Windows blue screens. In all the years I've been
running slack, the only time I've hosed it was when trying to get ATI
drivers to work. Other then that, it just runs and runs and runs without
crashing.
steveski
> On 2009-11-12, steveski <stev...@invalid.com> wrote:
>>
>> I'm running 13.0 on a dead badger I found at the side of the road . . .
>
> I thought only VuDu Linux ran on dead badgers.
>
> http://www.strangehorizons.com/2004/20040405/badger.shtml
Heh, yes - that's where I got it from (perhaps not that address but the
original document).
--
Steveski
Mike Jones
Ok. Somebody needs to do this one to get it out of the way.
"Badgers? We don' neeeed noh steeeenkin' badgers!"
There. Its done. Now we can all relax. %)
Dan C
>> I've found that Slackware runs on just about any hardware I throw at
>> it. My server /used to be/ a scavanged 486 but is now a scavanged 2Ghz
>> Celeron. A friend recently donated three old systems to me; I don't
>> doubt that I'll have Slackware up on at least two of them by the end of
>> the week.
> I'm running 13.0 on a dead badger I found at the side of the road . . .
Oh yeah? That's nothing!
Anybody can run it on a badger. They are very powerful.
I'm running a mail and web server on this salvaged equipment:
http://brandybuck.site40.net/pics/not-my-job.jpg
I think it's a double-striped possum. It's rock-solid stable.
--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he garotted another passing Liberal.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
Auric__
Weird Al rocks.
As it happens, I have a bunch of MS-DOS batch files in a directory called
"badgers". So I *do* need the stinking badgers...
--
( ) . o X o %%% ( ) -(-)- O O . %%%%%
^
YOU ARE HERE
[not to scale]
Mike Jones
As does Mel Brooks. :)
> As it happens, I have a bunch of MS-DOS batch files in a directory
> called "badgers". So I *do* need the stinking badgers...
There goes that theory then. D'oh!
Chick Tower
> I wish I had a dollar for each time Windows blue screens.
Sorry, Microsoft already patented that idea.
--
Chick Tower
For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net
Mike Jones
> On Thu, 12 Nov 2009 10:16:26 -0800, Zootal wrote:
>
>> I wish I had a dollar for each time Windows blue screens.
>
> Sorry, Microsoft already patented that idea.
http://www.pixelbeat.org/ms_mirth/
Peter Chant
>
> I'm running 13.0 on a dead badger I found at the side of the road . . .
>
Luxury.
notbob
> Luxury.
hassle
you want us to see something, zero in.
nb
Zootal
"Mike Jones" <N...@Arizona.Bay> wrote in message
news:pan.2009.11...@Arizona.Bay...
> Responding to Chick Tower:
>
>> On Thu, 12 Nov 2009 10:16:26 -0800, Zootal wrote:
>>
>>> I wish I had a dollar for each time Windows blue screens.
>>
>> Sorry, Microsoft already patented that idea.
>
>
> http://www.pixelbeat.org/ms_mirth/
That is just beautiful! And there are sooo many more out there in the real
world. I used to live in Vegas, and for a while at least the flight
information system at the airport was run on Windows. Walk through the
airport and you could find at least one blue screen somewhere.
You would think people would have learned by now not to use Windows for
anything important?
Mike Jones
Read up on the ED209 project from OCP. ;\
Peter Chant
Confused, I was referring to the four Yorkshire-man sketch.
Pete
notbob
> Confused, I was referring to the four Yorkshire-man sketch.
heh heh.... that cleared it up. ;)
nb
Eef Hartman
> I wonder what the ratio is between Slack on new hardware and Slack on
> recycled\reclaimed boxen? The lifespan of hardware must be at least
At home I'm still running two Pentium III machines (P3/800 and P3/1200)
with Slackware and most things they still run OK. I must admit they're
currently NOT running the newest releases.
My _very old_ 486dx2/66 now has been retired, but up to a year ago
it still was happily running Slackware (4.0).
My "fastest/newest" machine at home is an AMD Athlon 1800+ (throwaway
from the university), which is doing very fine with 12.2.
Probably in the Xmas period I'll be trying 13.0 on it (no 64-bit -
of course).
--
*******************************************************************
** Eef Hartman, Delft University of Technology, dept. SSC/ICT **
** e-mail: E.J.M....@tudelft.nl - phone: +31-15-278 82525 **
*******************************************************************
Mike Jones
> Mike Jones <N...@arizona.bay> wrote:
>> I wonder what the ratio is between Slack on new hardware and Slack on
>> recycled\reclaimed boxen? The lifespan of hardware must be at least
>> doubled simply by switching from ???Barbiware to Slack, yes?
>
> At home I'm still running two Pentium III machines (P3/800 and P3/1200)
> with Slackware and most things they still run OK. I must admit they're
> currently NOT running the newest releases. My _very old_ 486dx2/66 now
> has been retired, but up to a year ago it still was happily running
> Slackware (4.0). My "fastest/newest" machine at home is an AMD Athlon
> 1800+ (throwaway from the university), which is doing very fine with
> 12.2. Probably in the Xmas period I'll be trying 13.0 on it (no 64-bit -
> of course).
I've just recovered a "dead box" somebody had in their attic. They're a
bit miffed at how fast that old E-Machine goes compared to their
Barbieware infested quad processor box. (Smirk!)
Lew Pitcher
> I've just recovered a "dead box" somebody had in their attic. They're a
> bit miffed at how fast that old E-Machine goes compared to their
> Barbieware infested quad processor box. (Smirk!)
This is a lie. Nobody envies you anything since you are running an
obsolete OS on that machine.
LewPi...@LewPitcher.ca
--
Official Website -->> http://lewpitcher.ca/
Something to look at: -->> http://www.emusclemag.com/
Lonely in Brampton? -->> http://gaypros.meetup.com/cities/ca/on/brampton/
Peel HIV/AIDS Network -->> http://www.phan.ca/home.html
Mike Jones
> Mike Jones <N...@arizona.bay> trolled:
>
>> I've just recovered a "dead box" somebody had in their attic. They're a
>> bit miffed at how fast that old E-Machine goes compared to their
>> Barbieware infested quad processor box. (Smirk!)
>
> This is a lie. Nobody envies you anything since you are running an
> obsolete OS on that machine.
>
>
> LewPi...@LewPitcher.ca
Correction, /was/ "running an obsolete OS". The XP infestation found on
the HDD was wiped as the first job. Now its got Slackware on it, so its
now up to date and considered "repaired". :)