From: derosa <derosa@optonline.net>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Porting gentoo to the Alpha
Date: Wed Aug 29 16:20:02 2001 [thread overview]
Message-ID: <003901c130d8$9559bd00$14002a0a@wizard> (raw)
In-Reply-To: 20010828201517.D10510@cvs.gentoo.org
E3 that's the editor written in assembler right ?
I will just make vim part of the base system tarball for the alpha port,
other items will of course have to change also, no more grub or lilo, and I
will have to add milo for booting.
I will continue to play with the latest snapshots.
I also had an idea, for people stuck behind a nasty firewall, or no internet
connection, that want to build everything.
Have a special build cd, that has a 'snapshot' of the distfiles needed for a
build, and emerge system. And the snapshot from cvs equivolent to whats on
the disk. I have been using this method, on a couple of boxes at work, and
it seems to work well for me. I use the build cd as a base, and just add the
build tarball, and cvs tarball along with the distfiles.
Joe
> > I have recently set up an alpha machine running rh 7.1. I would like to
port
> > gentoo to the alpha chipset. My questions: Are there any parts of the
> > portage tree that are binary ? Would it make more sense to start from
rc6
> > build or rc5 build ?
>
> Um; the e3 editor won't work for you. That's a minor issue. Other than
that,
> you should be OK. Start with an rc6 build image in about a week.
>
next prev parent reply other threads:[~2001-08-29 22:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 14:05 [gentoo-dev] LHS Derek J. Belrose
2001-08-28 4:33 ` Karl Trygve Kalleberg
2001-08-28 16:18 ` [gentoo-dev] Porting gentoo to the Alpha derosa
2001-08-28 20:16 ` Daniel Robbins
2001-08-29 16:20 ` derosa [this message]
2001-08-30 6:12 ` Ben Lutgens
2001-08-30 9:55 ` Daniel Robbins
2001-08-30 6:10 ` Ben Lutgens
2001-08-30 16:08 ` derosa
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='003901c130d8$9559bd00$14002a0a@wizard' \
--to=derosa@optonline.net \
--cc=gentoo-dev@cvs.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox