From: ruscook ozbike <ozbike@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Installer (Sabayon 3.4 Loop 1) can't detect s/w RAID disks / fails with /etc/fstab mount error
Date: Sun, 29 Apr 2007 13:31:16 +1000 [thread overview]
Message-ID: <46341184.2080702@gmail.com> (raw)
In-Reply-To: <4633DABF.6010009@ep.mine.nu>
Neil Walker wrote:
> Hemmann, Volker Armin wrote:
>> Sabayon is just gentoo with a different installer, correct?
>
> No, it's a binary distribution and a horrible mess.
>
>> So as long as you do your emerge sync && emerge -u world. you never
>> need to install a new version, right?
>>
>
> That is about the most dangerous thing you can do on Sabayon -
> virtually guaranteed to break the system. It uses a mix of stable and
> testing with a huge list of packages in /etc/portage/package.keywords
> with ~arch. :( Any attempt to update the system the Gentoo way will
> lead to a tangle of blocks, upgrades, downgrades, package masks, etc.
> that can take a long time to sort out. At least that was how it was
> when I tried it. :(
Obviously my view wasn't as sophisticated or detailed, but in essence,
being a newbie, I felt the risk of that was too great. Hence wanting to
use the newer version to upgrade some key packages.
I'm going to play with gentoo some in a vmware instance so I can get
some idea of this emerge/compiling thingy :-)
Russ
--
gentoo-user@gentoo.org mailing list
next parent reply other threads:[~2007-04-29 3:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4633C457.6040008@gmail.com>
[not found] ` <200704290014.21640.volker.armin.hemmann@tu-clausthal.de>
[not found] ` <4633DABF.6010009@ep.mine.nu>
2007-04-29 3:31 ` ruscook ozbike [this message]
[not found] ` <4633CF15.1090706@gmail.com>
2007-04-29 8:26 ` [gentoo-user] Installer (Sabayon 3.4 Loop 1) can't detect s/w RAID disks / fails with /etc/fstab mount error Philip Webb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46341184.2080702@gmail.com \
--to=ozbike@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox