
I agree, a graphical enviroment is much easier to work on even a manual install, I welcome the installer livecd even if i don't use the installer script myself. It doesn't mean good bye CLI, you still have bash at hand to do everything you did in console only, except with the advantages of X.dmartinsca wrote:All in all, i like the Live CD and would like to see it develop into a more all-around tool.
- You can still download a minimal install cd for gentoo 2006.0, just like previous versions.
- I think the entire reason for the livecd and graphical installer is to speed up the install process, not to make it easier.
- No one can argue against the fact that reading the handbook, or any other webpage for that matter, in colour, with the layout originally intended is far nicer/easier than trying to read the same page in a text based web browser.
- If you don't want a GUI or can't run one as heavy as Gnome then DON'T USE THE LIVECD!

i don't think that comment is based on reality.dmartinsca wrote:
- I think the entire reason for the livecd and graphical installer is to speed up the install process, not to make it easier.
My 2006.0 works just fine. Did you install it the traditional way?bjacobt wrote:AFter 3 days on installing gentoo 2006. I have decided to go back with 2005.1.
Gentoo 2006.0 sucks, it does not work. and it too slow. After compiling the whole system, my computer was slow and i am having tonnes of errors.

After a small discussion with my professor who had tried the LiveCD I decided to download the minimal CD and do it by the good old fashion way. However I have no way to try it yet since I'm waiting for new components to arrive and the laptop I'm working on is waiting for finishing complaint due to it's permanent quality issues (don't want to see anything with ACER label on it ever againkohno wrote:My 2006.0 works just fine. Did you install it the traditional way?





You run amd64 and say modest hardware? Guess we have differing opinions of modest, my Sempron (socket A 2500+. Yup, I still use socket A) quite happily chuggs away compiling stuff and it doesn't take that long, and its pretty slow compared to the slowest amd64 I've ever found (which is a socket 754 2800+).runningwithscissors wrote:2. Modest hardware (I usually never compile anything over 90-100MB)
My computer is even 1.6Ghz Pentium4, and I dont think its slow, and have compiled everything (Stage1) from source in my Gentoo setup..chrismortimore wrote:You run amd64 and say modest hardware? Guess we have differing opinions of modest, my Sempron (socket A 2500+. Yup, I still use socket A) quite happily chuggs away compiling stuff and it doesn't take that long, and its pretty slow compared to the slowest amd64 I've ever found (which is a socket 754 2800+).runningwithscissors wrote:2. Modest hardware (I usually never compile anything over 90-100MB)

chrismortimore wrote:You run amd64 and say modest hardware? Guess we have differing opinions of modest, my Sempron (socket A 2500+. Yup, I still use socket A) quite happily chuggs away compiling stuff and it doesn't take that long, and its pretty slow compared to the slowest amd64 I've ever found (which is a socket 754 2800+).
On the amd machine I am a little more adventurous with the compiling, though it is only an Athlon processor. Its got decent RAM (2 GB) But the x86 machine never finished compiling openoffice.org in 3 attempts, all of which were in excess of 14 hrs. That was before I discovered caching, by the way. Anyway, I hardly ever download large packages, except the installation CDs (dial-up, you know), so almost everything is compiled except for a few packages like openoffice.org and the userland utilities that came with the stage 3 files. And I keep the distfiles directory safe. In fact, the /home /var and /usr directories are on different partitions so that I an do a quick reinstall if I ever need to. Like recently, when KDE and GNOME became unusable and wouldn't work properly even after a recompile or even after an Xorg recompile.NTT wrote: My computer is even 1.6Ghz Pentium4, and I dont think its slow, and have compiled everything (Stage1) from source in my Gentoo setup..

bjacobt wrote:I know what I am talking about, and emerge -e system does not work for some reason, and keeps doing it from the begining all the time which is a total waste of my time.
Code: Select all
--emptytree (-e short option)
Virtually tweaks the tree of installed packages to contain
nothing. This is great to use together with --pretend. This makes
it possible for developers to get a complete overview of the
complete dependency tree of a certain package.

Ah ha, you have two machines? distcc is your friend, I use it when I compile stuff for my laptop. Although if stuff randomly stops working sounds like either your hard drive is breaking and is corrupting your data or your CPU is knackered and not processing thing correctly...runningwithscissors wrote:On the amd machine I am a little more adventurous with the compiling, though it is only an Athlon processor. Its got decent RAM (2 GB) But the x86 machine never finished compiling openoffice.org in 3 attempts, all of which were in excess of 14 hrs. That was before I discovered caching, by the way. Anyway, I hardly ever download large packages, except the installation CDs (dial-up, you know), so almost everything is compiled except for a few packages like openoffice.org and the userland utilities that came with the stage 3 files. And I keep the distfiles directory safe. In fact, the /home /var and /usr directories are on different partitions so that I an do a quick reinstall if I ever need to. Like recently, when KDE and GNOME became unusable and wouldn't work properly even after a recompile or even after an Xorg recompile.
Also, take care with etc-update - It tends to overwrite your config files if you dont look carefully. I tried dispatch-conf once, but it gave me diff outputs which i find totally human unreadable personally. So I got scared off by that, and still use etc-update (option "-3" - ask when to overwrite).runningwithscissors wrote:Like recently, when KDE and GNOME became unusable and wouldn't work properly even after a recompile or even after an Xorg recompile.

I didn't know about distcc back thendistcc is your friend, I use it when I compile stuff for my laptop.
I hadn't done an etc-update before KDE and GNOME were hosed. They were working fine and suddenly one day they started taking too long to start up (10 minutes to load the dektop). TWM was working fine (so there weren't any problems with X). I had even made a post about on this forum. Unfortunately, I failed to find an answer.NTT wrote:Also, take care with etc-update - It tends to overwrite your config files if you dont look carefully. I tried dispatch-conf once, but it gave me diff outputs which i find totally human unreadable personally. So I got scared off by that, and still use etc-update (option "-3" - ask when to overwrite).runningwithscissors wrote:Like recently, when KDE and GNOME became unusable and wouldn't work properly even after a recompile or even after an Xorg recompile.

I thought the whole point of Gentoo is you have the choice to do everything manuallyclickety wrote:Although the installer might be a nice idea, but i think that the whole point of Gentoo is to do stuff manually.