* [gentoo-user] Handbook missing portage unpacking
@ 2014-10-11 20:13 James
2014-10-11 20:37 ` [gentoo-user] " James
2014-10-12 15:43 ` Kerin Millar
0 siblings, 2 replies; 8+ messages in thread
From: James @ 2014-10-11 20:13 UTC (permalink / raw
To: gentoo-user
Hello,
I was just following the handbook for an amd64 install; I have
not looked at the handbook in a while. I downloaded the stage3
tarball and the portage-latest tarball at the same time, like I always
have done. The handbook give instructions for untaring the stage3, in
section 5, but not the portage tarball, or did I miss something?
Obviously I missed something, or is the portion of the handbook (amd64)
where you unpack the portage tarball, missing?
curiously,
James
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-user] Re: Handbook missing portage unpacking
2014-10-11 20:13 [gentoo-user] Handbook missing portage unpacking James
@ 2014-10-11 20:37 ` James
2014-10-11 21:25 ` Daniel Frey
2014-10-12 15:43 ` Kerin Millar
1 sibling, 1 reply; 8+ messages in thread
From: James @ 2014-10-11 20:37 UTC (permalink / raw
To: gentoo-user
James <wireless <at> tampabay.rr.com> writes:
> I was just following the handbook for an amd64 install; I have
> not looked at the handbook in a while. I downloaded the stage3
> tarball and the portage-latest tarball at the same time, like I always
> have done. The handbook give instructions for untaring the stage3, in
> section 5, but not the portage tarball, or did I miss something?
Well I see the emerge --sync takes care of installing a new portage.
It's been a while; but I remember downloading a portage tarball and
uppacking it?
oh well, we'll see.
No need to reply....
James
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Re: Handbook missing portage unpacking
2014-10-11 20:37 ` [gentoo-user] " James
@ 2014-10-11 21:25 ` Daniel Frey
2014-10-12 7:32 ` [gentoo-user] " Stroller
0 siblings, 1 reply; 8+ messages in thread
From: Daniel Frey @ 2014-10-11 21:25 UTC (permalink / raw
To: gentoo-user
On 10/11/2014 01:37 PM, James wrote:
> James <wireless <at> tampabay.rr.com> writes:
>
>
>> I was just following the handbook for an amd64 install; I have
>> not looked at the handbook in a while. I downloaded the stage3
>> tarball and the portage-latest tarball at the same time, like I always
>> have done. The handbook give instructions for untaring the stage3, in
>> section 5, but not the portage tarball, or did I miss something?
>
> Well I see the emerge --sync takes care of installing a new portage.
> It's been a while; but I remember downloading a portage tarball and
> uppacking it?
>
>
Yes, the last couple of times I did a fresh install portage took care of
installing it. I don't remember when this change actually happened though.
From memory (a very sketchy memory, I might add, so check before doing
it) the command was:
$ tar xvjf portage-latest.tar.bz2 -C /usr/portage
> oh well, we'll see.
>
> No need to reply....
>
Meh, I noticed this a while ago but didn't think to mention it. The docs
were already updated then.
Dan
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Handbook missing portage unpacking
2014-10-11 21:25 ` Daniel Frey
@ 2014-10-12 7:32 ` Stroller
0 siblings, 0 replies; 8+ messages in thread
From: Stroller @ 2014-10-12 7:32 UTC (permalink / raw
To: gentoo-user
On Sat, 11 October 2014, at 10:25 pm, Daniel Frey <djqfrey@gmail.com> wrote:
> …
> From memory (a very sketchy memory, I might add, so check before doing
> it) the command was:
>
> $ tar xvjf portage-latest.tar.bz2 -C /usr/portage
I'd have thought you'd download and unpack the portage-latest tarball using the emerge-webrsync command, and have no need to download or untar it manually.
Stroller.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Handbook missing portage unpacking
2014-10-11 20:13 [gentoo-user] Handbook missing portage unpacking James
2014-10-11 20:37 ` [gentoo-user] " James
@ 2014-10-12 15:43 ` Kerin Millar
2014-10-12 16:41 ` Rich Freeman
1 sibling, 1 reply; 8+ messages in thread
From: Kerin Millar @ 2014-10-12 15:43 UTC (permalink / raw
To: gentoo-user
On 11/10/2014 21:13, James wrote:
> Hello,
>
> I was just following the handbook for an amd64 install; I have
> not looked at the handbook in a while. I downloaded the stage3
> tarball and the portage-latest tarball at the same time, like I always
> have done. The handbook give instructions for untaring the stage3, in
> section 5, but not the portage tarball, or did I miss something?
It specifies that emerge-webrsync be used, automating the process of
fetching and extracting a portage tarball.
--Kerin
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Handbook missing portage unpacking
2014-10-12 15:43 ` Kerin Millar
@ 2014-10-12 16:41 ` Rich Freeman
2014-10-13 2:12 ` [gentoo-user] " James
0 siblings, 1 reply; 8+ messages in thread
From: Rich Freeman @ 2014-10-12 16:41 UTC (permalink / raw
To: gentoo-user
On Sun, Oct 12, 2014 at 11:43 AM, Kerin Millar <kerframil@fastmail.co.uk> wrote:
> On 11/10/2014 21:13, James wrote:
>>
>> Hello,
>>
>> I was just following the handbook for an amd64 install; I have
>> not looked at the handbook in a while. I downloaded the stage3
>> tarball and the portage-latest tarball at the same time, like I always
>> have done. The handbook give instructions for untaring the stage3, in
>> section 5, but not the portage tarball, or did I miss something?
>
>
> It specifies that emerge-webrsync be used, automating the process of
> fetching and extracting a portage tarball.
Correct. This is much more efficient than rsync when you're starting
from an empty tree, which was one of the reasons the old procedure
used to recommend using a portage tarball. emerge-webrsync works well
and is easier to use anyway.
--
Rich
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-user] Re: Handbook missing portage unpacking
2014-10-12 16:41 ` Rich Freeman
@ 2014-10-13 2:12 ` James
2014-10-13 2:28 ` Rich Freeman
0 siblings, 1 reply; 8+ messages in thread
From: James @ 2014-10-13 2:12 UTC (permalink / raw
To: gentoo-user
Rich Freeman <rich0 <at> gentoo.org> writes:
> Correct. This is much more efficient than rsync when you're starting
> from an empty tree, which was one of the reasons the old procedure
> used to recommend using a portage tarball. emerge-webrsync works well
I'll have to try this"websync" sometime. I always like toget distracted
and look at experimental, hardened, lilblue and many other tarballs just
out of curiousity....
thx to all that responded. It had been a while since I followed a handbook
install. I wonder when btrfs will replace ext......(just kidding...)
James
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] Re: Handbook missing portage unpacking
2014-10-13 2:12 ` [gentoo-user] " James
@ 2014-10-13 2:28 ` Rich Freeman
0 siblings, 0 replies; 8+ messages in thread
From: Rich Freeman @ 2014-10-13 2:28 UTC (permalink / raw
To: gentoo-user
On Sun, Oct 12, 2014 at 10:12 PM, James <wireless@tampabay.rr.com> wrote:
>
> thx to all that responded. It had been a while since I followed a handbook
> install. I wonder when btrfs will replace ext......(just kidding...)
>
Nothing prevents you from installing Gentoo on btrfs. It really isn't
anything different from installing Gentoo on any other filesystem. I
know at least a few of us run it. Or, if if you prefer zfs on linux
the maintainer is a Gentoo dev...
--
Rich
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2014-10-13 2:29 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-11 20:13 [gentoo-user] Handbook missing portage unpacking James
2014-10-11 20:37 ` [gentoo-user] " James
2014-10-11 21:25 ` Daniel Frey
2014-10-12 7:32 ` [gentoo-user] " Stroller
2014-10-12 15:43 ` Kerin Millar
2014-10-12 16:41 ` Rich Freeman
2014-10-13 2:12 ` [gentoo-user] " James
2014-10-13 2:28 ` Rich Freeman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox