public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] problems with new install
Date: Tue Apr 17 22:12:01 2001	[thread overview]
Message-ID: <20010417221123.C16787@cvs.gentoo.org> (raw)
In-Reply-To: <20010417224047.A802@minime>; from blutgens@sistina.com on Tue, Apr 17, 2001 at 10:40:47PM -0500

On Tue, Apr 17, 2001 at 10:40:47PM -0500, Ben Lutgens wrote:

> >Hey!  A www.sistina.com (LVM) person trying Gentoo Linux!  Thanks ;)
> 
> That's right. I am sistina's Senior Sysadmin. :-)

Nice to meet you :)

> >Did you extract the tarball using the "p" option? -->
> 
> Doh! Ooops. 

daemontools is very picky about directory permissions, so that's why your syslog
was fried.  It's easy to forget the "p" option since it's normally not used when
extracting your typical source tarball.

> Which one, I'll try using vipw and vigr and try to login but I don't think
> it'll let me, something in pam's busted for sure. I you can post a fix on the
> website (A FAQ question?) that would be great. 

Unfortunately, I don't think you have "vi" at this point.  Try grabbing the
portage tree from your non-chrooted system, and then copy it to /usr/portage
under your chrooted system.  Then, add the CFLAGS that you want to
/etc/make.conf and then one quick hack -- copy wget from your real system to
/usr/bin on your Gentoo Linux system.  We forgot to add that to build.tbz2.
Then, create the /etc/resolv.conf and hosts files, and wget should then be
able to download from the chrooted environment.  At this point, Portage is
ready for use.

You're ready to merge gcc, binutils, flex and all that good stuff (look for
Achim's previous email for what needs to be remerged).  Use the emerge program:

# emerge foo-1.0.ebuild

To see what *would* be merged (without actually merging), use the --pretend option:

# emerge --pretend foo-1.0.ebuild

After merging the essentials (gcc, binutils, flex), make sure you merge the new
1.5 version of Portage in sys-apps.

Then, to install all essential packages on your system, type:

# emerge system

This will cause everything in /usr/portage/sys-* to be merged automatically -- and
in the proper order.  Nearly everything (if not everything) should compile cleanly,
though you may have a few problems since Achim is in the middle of upgrading to a
new readline on CVS.  Let us know your progress and we'll try to resolve any problems
you have.

After "emerge system" completes successfully, you should have a complete base Gentoo
Linux system.

> Well, I rather like the fact that it's mostly hands-on stuff, and if I can get
> the authentication thing straight I can hack the rest of it.
> 
> Ports man, I love it. Finally a distro with ports.

you should be able to simply rename /etc/pam.d/userpadd to useradd, and things should
work.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			



  reply	other threads:[~2001-04-18  4:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 20:22 [gentoo-dev] problems with new install Ben Lutgens
2001-04-17 21:10 ` Daniel Robbins
2001-04-17 21:14   ` Daniel Robbins
2001-04-17 21:42   ` Ben Lutgens
2001-04-17 22:12     ` Daniel Robbins [this message]
2001-04-17 23:07       ` Achim Gottinger
2001-04-18 10:22         ` Daniel Robbins
2001-04-18 10:45         ` Ben Lutgens
2001-04-18 10:36       ` Ben Lutgens
2001-04-17 22:13     ` Achim Gottinger
2001-04-17 21:12 ` Achim Gottinger
2001-04-18  9:47   ` Ben Lutgens
2001-04-18 10:25     ` Achim Gottinger
2001-04-18 10:56       ` Ben Lutgens
2001-04-18 11:09         ` Daniel Robbins
2001-04-18 12:01           ` Ben Lutgens
2001-04-18 11:18         ` Achim Gottinger
2001-04-18 11:21           ` Daniel Robbins
2001-04-18 12:05             ` Ben Lutgens
2001-04-18 12:04           ` Ben Lutgens
2001-04-18 11:30         ` Achim Gottinger
2001-04-18 11:58           ` Ben Lutgens
2001-04-17 22:10 ` Achim Gottinger

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=20010417221123.C16787@cvs.gentoo.org \
    --to=drobbins@gentoo.org \
    --cc=gentoo-dev@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