1 |
On 5/25/06, Daniel da Veiga <danieldaveiga@×××××.com> wrote: |
2 |
> On 5/25/06, Lord Sauron <lordsauronthegreat@×××××.com> wrote: |
3 |
> > I've found (after much exploration) that there is a archive: |
4 |
> > /portage-20060123.tar.bz2 |
5 |
> |
6 |
> Simply a portage snapshot, maybe the one you used to install Gentoo in |
7 |
> the first place? Take a look at the date and tell me I'm wrong. |
8 |
|
9 |
Okay, the date is when I installed Gentoo. You're right. |
10 |
|
11 |
> > This has - to the best of my knowledge - all the ebuild headers or |
12 |
> > whatever for everything. I know I can un-tar this and all, however, I |
13 |
> > want portage to use it in its uncompressed state, just to speed things |
14 |
> > up. I'm not burning for hard drive space, so a little more speed |
15 |
> > would be great. |
16 |
> |
17 |
> Of course, it is a portage snapshot, it has a whole compressed portage |
18 |
> tree, used to install, or update portage when using alternative |
19 |
> methods for those (like me) that lack the capacity to use remote |
20 |
> RSYNC. |
21 |
|
22 |
Forgive my ignorance, but what is RSYNC? |
23 |
|
24 |
> > However, I have no idea where to start to try and configure portage to |
25 |
> > reflect a change like this. I've read the man pages for ebuild and |
26 |
> > emerge several times over without finding any hints, so I was thinking |
27 |
> > someone on this list would know. |
28 |
> |
29 |
> There's no "change" and there's no such feature. If you take a look at |
30 |
> /usr/portage, you'll notice that is has all "portage related" stuff |
31 |
> there, a snapshot is decompressed there when you install (correct me |
32 |
> if I'm wrong, but you installed using the Gentoo Installer, didn't |
33 |
> you? if you had a complete experience of Gentoo install, you would |
34 |
> know that by now, that's why I strongly advice new users to AVOID THE |
35 |
> INSTALLER). If you sync once in a while, it is updated. Portage is not |
36 |
> kept compressed. |
37 |
|
38 |
Yeah, well this new Gentoo user wouldn't have gotten past partitioning |
39 |
my hard drive without the installer. I know it does let less |
40 |
experience people - like myself - into the community of vastly more |
41 |
experienced Gentoo users, however, I also think it's been a great tool |
42 |
for learning more about Linux. |
43 |
|
44 |
> > I also think that there's another file, /metadata.tar.bz2, which I |
45 |
> > think is portage-related. If possible I'd like to uncompress that as |
46 |
> > well. |
47 |
> |
48 |
> Oh, this one was a good choice, metadata is used by portage, but if |
49 |
> you take a look at /usr/portage/metadata, it is uncompressed there |
50 |
> too, and that is what portage uses. |
51 |
|
52 |
So any portage slowness now is just because... yeah, I really should |
53 |
look into this, because I see no reason why portage should be running |
54 |
as slow as it is. |
55 |
|
56 |
> > I think this is the cause of a slow portage because everything takes a |
57 |
> > long time to start going, then it's just fine. It takes about as long |
58 |
> > to start going as it does to open the archive |
59 |
> > /portage-20060123.tar.bz2 - conincidence? I think not! |
60 |
> |
61 |
> But it is. That's because of caching, not because it uncompress |
62 |
> everything every time and compress it again later, that would be |
63 |
> stupid (forgive my language). |
64 |
> |
65 |
> > |
66 |
> > I also get the bonehead award: there was a new kernel sitting on my |
67 |
> > hard drive and just yesterday I found and installed it. It was |
68 |
> > remarkably easy to install! I loaded the configuration file from my |
69 |
> > old kernel and then just make && make install and it worked! I didn't |
70 |
> > even have to edit /boot/grub/menu.lst! Dang... I got done and said |
71 |
> > "that was easy." I think I'm really getting the hang of all this! |
72 |
> |
73 |
> You have run an "emerge -u world" and it got the kernel sources, you |
74 |
> have no special needs and so the default configuration fit your need, |
75 |
> compiling kernels is EASY, making them work, that's a hard one. |
76 |
|
77 |
It booted, so I'm perfectly happy. It's spitting out coldplug errors |
78 |
right now, so I'm going to be hammering out some more settings, but it |
79 |
still boots and runs just fine, so I can't complain. |
80 |
|
81 |
> You sincerely must be booting from your old kernel and your |
82 |
> /usr/src/linux link must be pointing at your old sources, else you |
83 |
> would have some problems and probably would have to recompile, |
84 |
> reconfigure some stuff, because after make and all, you should copy |
85 |
> the image to /boot and, if necessary, change the grub.conf (menu.lst) |
86 |
> to point at the right file. |
87 |
|
88 |
I ran make && make install. I'm absolutely positive I'm running the |
89 |
new kernel because I've looked in /boot and it's there, and I've |
90 |
looked to check which kernel is actually running and it's the new one. |
91 |
The symlink in /usr/src is still pointing to the old kernel because I |
92 |
haven't bothered to change that yet, but I'll do it very soon. |
93 |
Especially since I gave in and unmasked YaKuake. I love Yakuake! |
94 |
|
95 |
> See the Kernel upgrade guide at Gentoo.org for more info. |
96 |
|
97 |
I think I got it right the first time, which is ample reason for |
98 |
celebration as far as I'm concerned. |
99 |
|
100 |
-- |
101 |
========== GCv3.12 ========== |
102 |
GCS d-(++) s+: a? C++ UL+>++++ P+ |
103 |
L++ E--- W+(+++) N++ o? K? w--- O? M+ |
104 |
V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+ |
105 |
DI+++ D+ G e* h- !r !y |
106 |
========= END GCv3.12 ======== |
107 |
|
108 |
-- |
109 |
gentoo-user@g.o mailing list |