ruscook ozbike wrote:
Hemmann, Volker Armin wrote:
On Sonntag, 29. April 2007, ruscook ozbike wrote:
Hi all,
I realise this is the gentoo forum, but I've had this problem out on the
sabayon forum (which is not as busy as here) and got no feedback as yet.
So, I'mputting my question out here as well.
I just went to upgrade to 3.4 loop 1 (live/install DVD) and it won't
detect my existing Sabayon 3.3 installation.
Why do you want to install 3.4 if you have already a working installation?
Sabayon is just gentoo with a different installer, correct? So as long as you
do your emerge sync && emerge -u world. you never need to install a new
version, right?
So your problem is not a problem at all?
Thanks for the reply I admire your logic Hemman :-)
But as a new Sabayon/Gentoo user and one ONLY used to binary
distributions to date, I wanted to go up a version to get the latest:
a) gnome (2.81)
b) kernel (not so important)
As I'm not used to emerge/portage I'm not confident in upgrading these
in the "traditional" gentoo way, hence why an upgrade install would
give me new binary versions of these apps/suites - I thought in a
painless manner. 3 days later with no more insight I'm not so sure :-(
That aside, given the problems with the installer, what does concern
me is the potential for a crash to render the system "unusable" and
requiring a complete reinstall
I've just found some more info on the gentoo forum that *might* help:
http://forums.gentoo.org/viewtopic-t-555876.html
This is someone else's boot/install problem with gentoo, but it has
similar issues with /etc/fstab
" Good - it booted. That error probably means that your /etc/fstab is
incorrect.
Boot the liveCD,
*Code:*
mount /dev/sda3 /mnt/gentoo
and do
*Code:*
nano -w /mnt/gentoo/etc/fstab
to see and change your own fstab.
If it has entries like /dev/ROOT, /dev/BOOT and /dev/SWAP/ you need to
change the words in capital letters to the partitions.
So /dev/ROOT needs to become /dev/sda3 and so on.
While you are there, check the file system types too."
My /etc/fstab had /dev/ROOT in it but not /dev/BOOT. I'm guessing that
the installer in trying to setup the "real" /etc/fstab couldn't make the
transition from the meta names used above to the real raid names
required to install my system i.e. /dev/md0 and /dev/md1 for /boot and /.
As the installer aborts at this point, I don't know where/how to modify
this.
Does this seem to be on the right track????
--
Kind Regards Russell
==================
www.windsorcycles.com.au
bikes.no-ip.info
Linux user #369094
==================
