On Wednesday 30 April 2008, [EMAIL PROTECTED] wrote:
> Alan McKinnon <[EMAIL PROTECTED]> writes:
> >> I'd like to jump an 2006 install up to 2008. I've never made that
> >> big an update without a fresh install.
> >
> > There's no such thing as a "2006 install". What does exist, is the
> > collection of packages that were on the LiveCDs released in 2006.
> > It's
>
> symantics...
>
> Here is the story behind my phraseology... I've tried 4-5 times to
> build a vmware gentoo install hosted on vista home premium. Using
> 2008 install media.
>
> I cannot seem to get past a kernel panic that appears to be expecting
> an intramfs (You may remember this from a previous thread) After
> hand rolling 3 different kernels and trying genkernal all.... its all
> ended in the same kernel panic.
Yes, I remember it well.
> So.... tryin to slip in the back way I found a gentoo vmware
> appliance online .. downloaded and fired it up on vista. It boots
> and runs with no problems. Only thing is it is built on 2006 package
> set.
What kernel does it use? I would rather update that vm's kernel to the
latest available and see if that boots properly. If so, move forward
and update the rest of the system. I reason that kernel panics on boot
concern only the boot loader and kernel and have nothing to do with
user-space, so you should concentrate on the more relevant bits.
I also think it's time to bring out the big guns with all the data.
Could you reply and attach the vmware config files for the non-working
vm, plus the .config file for that kernel in the vm?
I strongly suspect you have a simple incompatibility between the
hardware vmware provides that vm and how the kernel is configured.
> One blockage that looks to be particularly troublesome is:
> Portage blocking bash
>
> bash blocking portage.
That's a nasty one and you quite rightly don't want to unmerge portage
or bash. The trick is to do it in several stages:
First look at portage:
[EMAIL PROTECTED] /var $ eix -e portage
[I] sys-apps/portage
Available versions: 2.0.51.22-r3 2.1.1-r2 2.1.4.4 (~)2.1.5_rc5 (~)
2.1.5_rc6 [M](~)2.2_pre3 [M](~)2.2_pre5 {build doc elibc_FreeBSD
elibc_glibc elibc_uclibc epydoc linguas_pl selinux userland_Darwin
userland_GNU}
Installed versions: 2.1.5_rc6(10:57:02 PM 04/24/2008)
(doc -build -epydoc -linguas_pl -selinux)
[EMAIL PROTECTED] /var/portage/sys-apps/portage $ grep bash *ebuild
portage-2.0.51.22-r3.ebuild:RDEPEND="!build? ( >=sys-apps/sed-4.0.5
dev-python/python-fchksum >=dev-lang/python-2.2.1 sys-apps/debianutils
>=app-shells/bash-2.05a ) !x86-fbsd? ( !mips? (
>=sys-apps/sandbox-1.2.17 ) ) selinux? (
>=dev-python/python-selinux-2.15 )"
portage-2.1.1-r2.ebuild: !userland_Darwin? (
>=app-shells/bash-3.0 ) )
portage-2.1.4.4.ebuild: >=app-shells/bash-3.2_p17 )
portage-2.1.5_rc5.ebuild: >=app-shells/bash-3.2_p17 )
portage-2.1.5_rc6.ebuild: >=app-shells/bash-3.2_p17 )
portage-2.2_pre3.ebuild: >=app-shells/bash-3.2_p17
portage-2.2_pre5.ebuild: >=app-shells/bash-3.2_p17
And look at bash:
[EMAIL PROTECTED] ~ $ eix -e bash
[I] app-shells/bash
Available versions: 2.05b-r11 3.0-r12 (~)3.0-r13 (~)3.0-r14
3.1_p17 3.2_p17-r1 (~)3.2_p33 {afs bashlogger build minimal nls plugins
unicode vanilla}
Installed versions: 3.2_p33(10:01:41 PM 01/05/2008)
(-afs -bashlogger -nls -plugins -vanilla)
[EMAIL PROTECTED] /var/portage/app-shells/bash $ grep portage *ebuild
bash-3.2_p33.ebuild: !<sys-apps/portage-2.1.4_rc1
Recent portages want any bash >=bash-3.2_p17, but you can't use the most
recent bash (3.2_p33) as that blocks the portage you have. So, do it
manually:
1. emerge --nodeps bash-3.2_p17-r1
2. emerge --nodeps portage
3. emerge bash
4. emerge world
The --nodeps is there to stop portage updating other stuff that
conflicts with what you are trying to do.
Once this is done, you will still have the python/python-updater blocker
to deal with, but I seem to recall posting on that earlier
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
[email protected] mailing list
