On Fri, 31 Oct 2003 22:46:27 +0100, "Jernej Zidar" <[EMAIL PROTECTED]>
responded thusly:
the name of the file is resolv.conf and not resolv.conf
without it the network won't work.
Okay.
--
The only fallacy is the inaction on our part to stave off the worst of
horrors, the stripping of persona
the name of the file is resolv.conf and not resolv.conf
without it the network won't work.
- Original Message -
From: "Graeme Donaldson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 31, 2003 6:19 PM
Subject: Re: [gentoo-user] Ap
On Fri, 31 Oct 2003 11:48:38 -0600, "Jeffrey Smelser"
<[EMAIL PROTECTED]> responded thusly:
On Fri, 31 Oct 2003 11:41:19 -0600, "Jeffrey Smelser"
<[EMAIL PROTECTED]> responded thusly:
>No, you should have read the error.. make.conf is suppose to be
>there and functional. Its not a documentation
> On Fri, 31 Oct 2003 11:41:19 -0600, "Jeffrey Smelser"
> <[EMAIL PROTECTED]> responded thusly:
> >No, you should have read the error.. make.conf is suppose to be
> >there and functional. Its not a documentation error as your
> trying to
> >convey.. This is a possible bug that needs to be addr
On Fri, 31 Oct 2003 11:41:19 -0600, "Jeffrey Smelser"
<[EMAIL PROTECTED]> responded thusly:
No, you should have read the error.. make.conf is suppose to be
there and functional. Its not a documentation error as your trying to
convey.. This is a possible bug that needs to be addressed...
Okay,
He did. It states he tried to run env-update several times, so he got back out of
chroot and moved make.conf, chrooted again and it works..
So, it sounds like make.conf was bad, but was trying to figure out what could be wrong
in the default make.conf that would do that..
> It's not an error.
No, you should have read the error.. make.conf is suppose to be there and functional.
Its not a documentation error as your trying to convey.. This is a possible bug that
needs to be addressed...
thats why I asked for the error. I presume you just assumed it was a documentation
error and didn
On Fri, 31 Oct 2003 12:22:06 -0500, "brett holcomb"
<[EMAIL PROTECTED]> responded thusly:
It's not an error. You need to do it before you chroot or you can't
get to the real /etc. You are copying the resolv.conf used with the
LiveCD boot to what will be your Gentoo install /etc. You don't run
On Fri, 31 Oct 2003 11:19:39 -0600, "Jeffrey Smelser"
<[EMAIL PROTECTED]> responded thusly:
What was the error??
Um, it's not resolve.conf (or at the very least not just resolve.conf)
that needed to be cp'd. You had to cp over make.conf as well.
Just before you are told to chroot to /mnt/gento
It's not an error. You need to do it before you chroot or
you can't get to the real /etc. You are copying the
resolv.conf used with the LiveCD boot to what will be your
Gentoo install /etc. You don't run env-update until after
you chroot.
1. copy resolv.conf
2. do whatever else
3. chroot
4
Joseph A. Nagy, Jr. said:
> Just before you are told to chroot to /mnt/gentoo, it says to cp
> /etc/resolve.conf to /mnt/gentoo/etc/
>
> I tried that several times and had errors with running env-update so I
> exited the chroot and decided to cp /etc/make.conf /mnt/gentoo/etc/,
> chroot'd again and
What was the error??
> Just before you are told to chroot to /mnt/gentoo, it says to cp
> /etc/resolve.conf to /mnt/gentoo/etc/
>
> I tried that several times and had errors with running
> env-update so I
> exited the chroot and decided to cp /etc/make.conf /mnt/gentoo/etc/,
> chroot'd again
Just before you are told to chroot to /mnt/gentoo, it says to cp
/etc/resolve.conf to /mnt/gentoo/etc/
I tried that several times and had errors with running env-update so I
exited the chroot and decided to cp /etc/make.conf /mnt/gentoo/etc/,
chroot'd again and ran env-update with no errors.
I
13 matches
Mail list logo
