public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ben Lutgens <blutgens@sistina.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] problems with new install
Date: Wed Apr 18 10:36:01 2001	[thread overview]
Message-ID: <20010418113500.B7689@titanium.sistina.com> (raw)
In-Reply-To: <20010417221123.C16787@cvs.gentoo.org>; from drobbins@gentoo.org on Tue, Apr 17, 2001 at 10:11:23PM -0600

[-- Attachment #1: Type: text/plain, Size: 3380 bytes --]

On Tue, Apr 17, 2001 at 10:11:23PM -0600, Daniel Robbins wrote:
>
>Nice to meet you :)

Thanks!

>
>> >Did you extract the tarball using the "p" option? -->

Well this time I did, and still multilog is whining. It's gonna irritate me
untill I fix it, I rebooted into my running system as I need to copy my
modules for my kernel (LVM and GFS modules needed to mount my former root
partition so I can get to the iso of gentoo to mount it with the loop device
:-)

I love this stuff.


>> 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.

Well, I did use the p option this time so I'm assuming something happend
before I untarred it.

>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.

I have vim actually. I do need to get the kernel recompiled with reiserfs


>
>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:

can I take all this stuff off the iso I downloaded?


>
># 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.


This is all great stuff to add to the installation guide!

>
>> 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.			
>
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@gentoo.org
>http://www.gentoo.org/mailman/listinfo/gentoo-dev

-- 
Ben Lutgens		cell: 612.670.4789
Sistina Software Inc.	worl: 612.379.3951
Code Monkey Support (A.K.A. System Administrator)

Kernel panic: I have no root and I want to scream

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2001-04-18 16:35 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
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 [this message]
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=20010418113500.B7689@titanium.sistina.com \
    --to=blutgens@sistina.com \
    --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