1 |
On Wednesday 30 April 2008, reader@×××××××.com wrote: |
2 |
> Alan McKinnon <alan.mckinnon@×××××.com> writes: |
3 |
> >> I'd like to jump an 2006 install up to 2008. I've never made that |
4 |
> >> big an update without a fresh install. |
5 |
> > |
6 |
> > There's no such thing as a "2006 install". What does exist, is the |
7 |
> > collection of packages that were on the LiveCDs released in 2006. |
8 |
> > It's |
9 |
> |
10 |
> symantics... |
11 |
> |
12 |
> Here is the story behind my phraseology... I've tried 4-5 times to |
13 |
> build a vmware gentoo install hosted on vista home premium. Using |
14 |
> 2008 install media. |
15 |
> |
16 |
> I cannot seem to get past a kernel panic that appears to be expecting |
17 |
> an intramfs (You may remember this from a previous thread) After |
18 |
> hand rolling 3 different kernels and trying genkernal all.... its all |
19 |
> ended in the same kernel panic. |
20 |
|
21 |
Yes, I remember it well. |
22 |
|
23 |
> So.... tryin to slip in the back way I found a gentoo vmware |
24 |
> appliance online .. downloaded and fired it up on vista. It boots |
25 |
> and runs with no problems. Only thing is it is built on 2006 package |
26 |
> set. |
27 |
|
28 |
What kernel does it use? I would rather update that vm's kernel to the |
29 |
latest available and see if that boots properly. If so, move forward |
30 |
and update the rest of the system. I reason that kernel panics on boot |
31 |
concern only the boot loader and kernel and have nothing to do with |
32 |
user-space, so you should concentrate on the more relevant bits. |
33 |
|
34 |
I also think it's time to bring out the big guns with all the data. |
35 |
Could you reply and attach the vmware config files for the non-working |
36 |
vm, plus the .config file for that kernel in the vm? |
37 |
|
38 |
I strongly suspect you have a simple incompatibility between the |
39 |
hardware vmware provides that vm and how the kernel is configured. |
40 |
|
41 |
> One blockage that looks to be particularly troublesome is: |
42 |
> Portage blocking bash |
43 |
> |
44 |
> bash blocking portage. |
45 |
|
46 |
That's a nasty one and you quite rightly don't want to unmerge portage |
47 |
or bash. The trick is to do it in several stages: |
48 |
|
49 |
First look at portage: |
50 |
alan@nazgul /var $ eix -e portage |
51 |
[I] sys-apps/portage |
52 |
Available versions: 2.0.51.22-r3 2.1.1-r2 2.1.4.4 (~)2.1.5_rc5 (~) |
53 |
2.1.5_rc6 [M](~)2.2_pre3 [M](~)2.2_pre5 {build doc elibc_FreeBSD |
54 |
elibc_glibc elibc_uclibc epydoc linguas_pl selinux userland_Darwin |
55 |
userland_GNU} |
56 |
Installed versions: 2.1.5_rc6(10:57:02 PM 04/24/2008) |
57 |
(doc -build -epydoc -linguas_pl -selinux) |
58 |
alan@nazgul /var/portage/sys-apps/portage $ grep bash *ebuild |
59 |
portage-2.0.51.22-r3.ebuild:RDEPEND="!build? ( >=sys-apps/sed-4.0.5 |
60 |
dev-python/python-fchksum >=dev-lang/python-2.2.1 sys-apps/debianutils |
61 |
>=app-shells/bash-2.05a ) !x86-fbsd? ( !mips? ( |
62 |
>=sys-apps/sandbox-1.2.17 ) ) selinux? ( |
63 |
>=dev-python/python-selinux-2.15 )" |
64 |
portage-2.1.1-r2.ebuild: !userland_Darwin? ( |
65 |
>=app-shells/bash-3.0 ) ) |
66 |
portage-2.1.4.4.ebuild: >=app-shells/bash-3.2_p17 ) |
67 |
portage-2.1.5_rc5.ebuild: >=app-shells/bash-3.2_p17 ) |
68 |
portage-2.1.5_rc6.ebuild: >=app-shells/bash-3.2_p17 ) |
69 |
portage-2.2_pre3.ebuild: >=app-shells/bash-3.2_p17 |
70 |
portage-2.2_pre5.ebuild: >=app-shells/bash-3.2_p17 |
71 |
|
72 |
And look at bash: |
73 |
alan@nazgul ~ $ eix -e bash |
74 |
[I] app-shells/bash |
75 |
Available versions: 2.05b-r11 3.0-r12 (~)3.0-r13 (~)3.0-r14 |
76 |
3.1_p17 3.2_p17-r1 (~)3.2_p33 {afs bashlogger build minimal nls plugins |
77 |
unicode vanilla} |
78 |
Installed versions: 3.2_p33(10:01:41 PM 01/05/2008) |
79 |
(-afs -bashlogger -nls -plugins -vanilla) |
80 |
alan@nazgul /var/portage/app-shells/bash $ grep portage *ebuild |
81 |
bash-3.2_p33.ebuild: !<sys-apps/portage-2.1.4_rc1 |
82 |
|
83 |
Recent portages want any bash >=bash-3.2_p17, but you can't use the most |
84 |
recent bash (3.2_p33) as that blocks the portage you have. So, do it |
85 |
manually: |
86 |
|
87 |
1. emerge --nodeps bash-3.2_p17-r1 |
88 |
2. emerge --nodeps portage |
89 |
3. emerge bash |
90 |
4. emerge world |
91 |
|
92 |
The --nodeps is there to stop portage updating other stuff that |
93 |
conflicts with what you are trying to do. |
94 |
|
95 |
Once this is done, you will still have the python/python-updater blocker |
96 |
to deal with, but I seem to recall posting on that earlier |
97 |
|
98 |
|
99 |
-- |
100 |
Alan McKinnon |
101 |
alan dot mckinnon at gmail dot com |
102 |
|
103 |
-- |
104 |
gentoo-user@l.g.o mailing list |