From: Nelson Abramson <pogtal@erols.com>
To: beethoven@socal.rr.com
Cc: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Where's the best installation tree?
Date: Tue, 29 Feb 2000 21:28:18 -0500 [thread overview]
Message-ID: <38BC8042.49743B1C@erols.com> (raw)
In-Reply-To: 38BC1E00.5533BAFE@socal.rr.com
Richard Young wrote:
> Where can I find the best (most up to date and working)
> RedHat (or Yellowdog) installation tree on the internet
> to support the sawtooth G4. One that has up to date gcc,
> debugger, utilities, whatever....
Well, linuxPPC supports the g4, I am on one as we speak. If you purchase
(or burn) a linuxPPC 2000 cd, the X installer supports the sawtooths, or
you can use the redhat installer on linuxPPC 1999...
> So rather than using one of the old official releases
> does anybody have a FTP site I could get the tree from?
> Is there an equivalent tree for installation RPMS as there
> is for the kernel?
There are all of the ftp mirrors and the main sites, and you can get
software from the developers...if you don't want to wait till someone
builds an rpm. Every software has it's own developement cycles, some are
open and publicly invovled (like gnome for instance), others are more one
man shows....
> It would be nice to have a newer kernel also that runs
> properly on the sawtooth. I was previously using Ben's
> vmlinux.benh.15 kernel but there has been lots of talk
> about changes that have been made so I should
> probably use a newer kernel also.
Well......BenH's kernels are nice because they work for a wide range of
machines. Get linux installed, and then compile your own kernel...
HTH
--Nelson Abramson
--
Shouldn't people be arrested and persecuted for engaging in their
constitutional rights? http://www.opendvd.org
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
parent reply other threads:[~2000-03-01 2:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <38BC1E00.5533BAFE@socal.rr.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38BC8042.49743B1C@erols.com \
--to=pogtal@erols.com \
--cc=beethoven@socal.rr.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.