Fink is highly over-rated (as is OSX). I am running Debian on a Ti PowerBook. Here are
a couple of install guides: http://people.debian.org/~branden/ibook.html
http://cattlegrid.net/~christophe/titanium/
HTH
John
-Original Message-
From: Jim Hickstein [mailto:jxh@;jxh.com]
Sent: Thursd
-Original Message-
From: Fierce Silver [mailto:fiercesilver@;yahoo.com]
Sent: Thursday, November 07, 2002 05:42 PM
To: [EMAIL PROTECTED]
Subject: Unidentified subject!
I'm having a lot trouble installing Linux on my ppc.
I'm stuck on the hard drive partitioning. I've read
your installat
-Original Message-
From: Hall Stevenson [mailto:[EMAIL PROTECTED]
> I have a friend at work that is interested in trying
> out Linux. The only problem that he has is that he
> has signed up for one of these 3 year contracts of
> MSN when he got his computer, so he's not really
> willing t
Since you didn't sign the temper tantrum below, I can only address you
as Moron. (This is also reinforced by your use of AOL)
Dear Moron,
This may be a waste of time since you seem to lack basic English reading
skills, but I'll give you the benefit of the doubt and try to explain.
This message i
Debian is not lagging behind Slackware. I don't understand your
complaint.
Everything available in Slackware 8.0 is available in sid. (and then
some)
I like both of them. My first distro was Slack 3.6, then I found hamm. I
have tried a couple different versions of RH and SuSE but I prefer
Debian o
I don't recommend doing this, but here is a forwarded message
Forwarded Message
--
According to incidents.org, for any machine that hits your webserver
with
X, you can telnet back to that machine on port 80 and get cmd line
access to that ma
I had the same problem. My modem used irq 4 under windoze and worked
perfectly. It sucked under Linux. I changed the irq to 2 by running
'setserial /dev/ttyS2 irq 2' as root and everything works great. You can
check your modem by running 'setserial /dev/ttyS2 -G'.
YMMV
John Gilger
-Original
This usually happens when you don't run 'make bzlilo' after compiling
your new kernal.
All I had to do when this happened to me was edit my /etc/lilo.conf file
to make sure everything was still the way I wanted it and run 'lilo'.
John Gilger
-Original Message-
From: Mike McGuire [mailto
1. Do you have a disk installed?
2. Did you add ppa or imm and parport_pc support when you compiled your
kernal? Or did you insert (insmod) those modules?
3. Does your sysstem recognize the zip drive on boot?
John Gilger
-Original Message-
From: Joern T. Larsen [mailto:[EMAIL PROTECTED]
9 matches
Mail list logo