Do you realize that you're telling the Gentoo x86 Release Coordinator that he's wrong about what constitutes a release in Gentoo? The "releases" in Gentoo are really nothing more than media refreshes. The new profiles may give you a slightly different set of default USE flags, but in most cases, you will get the exact same versions (the latest) when you 'emerge -uDN world'.
You people just don't get it. The pam-login/shadow blocker was not a bug. It was a fix for a bug. Dealing with blockers is a normal part of administrating a Gentoo system. If you can't handle it, go use Ubuntu.
Except that as another user noted above, there's a problem with the base install where PAM and shadow libraries conflict with each other (obviously there are packates from the stage tarball that depend on each?) and it was a problem in the 2006.0 release. Something like that should have been fixed for the 2006.1 release. I had a lot of "fun" getting around that problem (and a lot of wasted time!).
There was no "conflict". At some point in the past, pam-login had been broken out from shadow, and then it was decided it should be put back in. There was a blocker put in the newer version of shadow (with pam-login rolled back in) so you wouldn't have pam-login and shadow providing the same files at the same time. Blockers are a normal part of using Portage. This "fun" you speak of was simple to get around:
This was covered on the mailing lists, GWN, and forums. Don't blame Gentoo because you can't use the tools or read.
I mean basically "out of the box", you've just finished the install and you reboot into your new gentoo system only to find a PITA of a problem the minute you go to install a package or set of packages that depends on Pam or shadow. I still have the 2005.whatever release still running on my main linux box because of this (I was smart and tried 2006.x on a different system first.)
You mean you've never updated the box since you installed over a year ago? If you've updated world recently, congrats, you're running a 2006.x release on that box.
A weekend? With the installer, you can do a 10 minute (hardware permitting) install using a stage3 and the LiveCD's kernel/initrd/modules. And that was in vmware...
I purposely designed the GTK frontend to not be dumbed down. The purpose of the installer is not to make Gentoo easier to install but faster. Please direct all complaints to/dev/null.
Slashdot Mirror
Do you realize that you're telling the Gentoo x86 Release Coordinator that he's wrong about what constitutes a release in Gentoo? The "releases" in Gentoo are really nothing more than media refreshes. The new profiles may give you a slightly different set of default USE flags, but in most cases, you will get the exact same versions (the latest) when you 'emerge -uDN world'.
You people just don't get it. The pam-login/shadow blocker was not a bug. It was a fix for a bug. Dealing with blockers is a normal part of administrating a Gentoo system. If you can't handle it, go use Ubuntu.
I only have one thing to say to this....damn straight!
emerge -B shadow && emerge -C pam-login && emerge -1k shadow
This was covered on the mailing lists, GWN, and forums. Don't blame Gentoo because you can't use the tools or read.
You mean you've never updated the box since you installed over a year ago? If you've updated world recently, congrats, you're running a 2006.x release on that box.
A weekend? With the installer, you can do a 10 minute (hardware permitting) install using a stage3 and the LiveCD's kernel/initrd/modules. And that was in vmware...
I purposely designed the GTK frontend to not be dumbed down. The purpose of the installer is not to make Gentoo easier to install but faster. Please direct all complaints to /dev/null.