Post a Comment
maybe alias will help you here
alias unmerge emerge unmerge
It seems that most of the problems came from an
unwillingness to read the documentation.
Gentoo is all about learning. especially a stage 1 install which serves almost no purpose than learning about how the system was built.
For installing KDE you should have read the Desktop guide and if you were expecting a functional workstation on your first install then using the stage3 tarball and the prebuild binary packages is highy recommanded.
Gentoo is really easy to use, once you have done the nescesary reading, because if anything goes wrong you will know how to fix it.
The wonderful Gentoo community will welcome you back anytime.
- Jesse McNelis
that some people feel such an urge to embarrass themeselves publicly.
What was that supposed to be?
It all amounted to "I didn't read the documentation, I don't want to read the documentation, but I somehow feel the need to use a distro that requires reading documentation and I'll write an article about the experience."
Really, this is kindergarten.
ahhh but the elitists must attack back!!! How kindergarten! I do not think that the author was intending to attack Gentoo.
The killer of gentoo for me is automating updates over night. The thought of having everything compile on the fly for an automated update schedule makes me cringe.
I support Slack as well, a well built quality distro that pushes Security, Stability and Speed. Gentoo is fun to play with, I would not be able to justify it in a corporate desktop environment.
We use Slackware in the corporate desktop environment.
I used Redhat, Debian (Woody), Mandrake, Suse, Slackware, Gentoo, and -- lately -- Ubuntu, but I am returning to Arch. Finding the best blend between control over the OS and work hours invested is hard, but with Arch I manage. Give it a try if you consider experimenting again.
I think you hit on something really key here:
"Finding the best blend between control over the OS and work hours invested is hard."
Most of the opinions here (including mine) can be distilled to a "madlib" version of that statement:
"I (like/dislike) the ___ (distro/OS) because it (gave/did not give) MY DESIRED BLEND of ___ and ___."
Try to apply it yourself to some of the comments here. This does not make those opinions "bad" AT ALL. If anything it is a testament to the great number of choices we have thanks to the countless number of talented developers working on the many distros/OSes.
One problem that seems to pop up in these conversations is hostility often generated between users and/or sub-communities by knocking down anything different from our own favorite distro/OS (often subtly). I find this a bit frustrating, as it often breaks down the conversation very, very quickly.
One alternative is to listen well to the reasons why the distro/OS is liked, and how the specific "blend" is achieved. A step further might be to try it out and spend a bit of time in the community, getting to know the tricks of that specific distro/OS. In either case, we end up with more knowledge than we started with. That is unless we "think" that we have nothing to learn 
I agree with you. I have used some famous distribution like RedHat, Gentoo and Debian. I found out Arch is the best overall. The only drawback of Arch is that they haven't got enough packages as much as Debian and Gentoo. Although it is not for beginner, you don't need to be an Linux expert to install and use it. Certainly you learn a lot Linux from it.
Split builds are a god send for KDE. The present system can feel a little awkard to use, and I'm sure there could be better & room for improvement.
However, chances are even though the KDE & Qt teams deserve harems delievered to them, I would not choose to use it if I had to sit through a huge monolithic build.
And stuff I have to desire to see or use, i.e. kde-games etc.
I've tried prolly all the major distros, and I have to say I personally think gentoo is the best, as you have the most control over what you're installing of any of the systems I've used. Additionally, the author really should investigate portage. I think it would be very beneficial to him to realize that this article really was a big waste of time.
this sounds like my first shot at gentoo, when i figured i could get by skipping small sections of the install n get by, every install i followed after that was flawless, ya just have to MAKE SURE you know your system well, and read everything/be easy on use flags, its not really all that hard, just takes too long to maintain if your a bleeding edge junkie 
You obviously didn't look very hard. On Gentoo's homepage, on the right under the word "Documentation", is the word main index, that could be a good place to start.
Or if you actually read the handbook, the last page "Where do go from here?" provides links to the other documentation.
RTFM
KDE Howto
http://www.gentoo.org/doc/en/kde-config.xml
Nvidia Guide
http://www.gentoo.org/doc/en/nvidia-guide.xml
Alsa Guide (Sound Guide)
http://www.gentoo.org/doc/en/alsa-guide.xml
Xorg Guide
http://www.gentoo.org/doc/en/xorg-config.xml
Did I miss anything? You decide to do a stage 1, then you whine about long compilation times. That's your bad, not mine.
wow, way to give an impartial review. O_o
"I go back online (with a wired connection; the wireless isn't working yet) with links and search for how to fix my mouse and install KDE. Searching the Gentoo site was difficult, but Google found the Gentoo instructions easily. Hmm, so much for that great Gentoo documentation I've been hearing about."
On the left column of Gentoo.org is a link marked Documentation: Main Index, Which leads to a page with Desktop Documentation which has a whole section on installing KDE.
"I thought I'd be smart and "emerge kde" to get up and running. Wrong! That's not quite right - you have to 'emerge kde-somethingorother' to get it done right."
Actually that was correct, and if you checked the KDE docs on the gentoo site you would have noticed that. Why you would think this is incorrect is mysterious..
---
Near the end of your "review" you rant about how long gentoo took to install when you decided to go with a stage 1 installation -- the longest possible method. You could have had gentoo up and running in 40 minutes as well if you opted to use their cd install.
Then you go into a rant about how much you love slackware.
---
All I gathered from your "review" was that you didn't read the documentation, you are upset that you choose the longest possible method to install gentoo and it took longer then 40 minutes, and that you like slackware.
-- Jamie Conlon.
"I thought I'd be smart and "emerge kde" to get up and running. Wrong! That's not quite right - you have to 'emerge kde-somethingorother' to get it done right."
Actually that was correct, and if you checked the KDE docs on the gentoo site you would have noticed that. Why you would think this is incorrect is mysterious..
He is proably referring too emerge kde-meta which installs the split ebuild.
I agree with the reviewer one hundred percent. Gentoo will never be an operating system for the masses. It will only be popular by a few hard core geeks who enjoy tinkering, have lots and lots of time, and are probably unemployed.
I am also amused by Microsoft hiring one of Gentoo's founders. Now windows will get even more bleeped up.
Its all good.
Something else that continues to amaze me is how often Gentoo is recommended for newbies in linux forums.
NEWBIES - do not try Gentoo.
"It will only be popular by a few hard core geeks who enjoy tinkering, have lots and lots of time, and are probably unemployed."
Hardcore geeks? Definately. Umemployed? More like the guy you can't just fire because he wrote some magic Perl that look like /dev/random output to the uninitiated!
(Using gentoo, got a job, no Perl magic, unfortunately 
I agree with the reviewer one hundred percent. Gentoo will never be an operating system for the masses. It will only be popular by a few hard core geeks who enjoy tinkering, have lots and lots of time, and are probably unemployed.
I am also amused by Microsoft hiring one of Gentoo's founders. Now windows will get even more bleeped up.
Its all good.
Something else that continues to amaze me is how often Gentoo is recommended for newbies in linux forums.
NEWBIES - do not try Gentoo.
im not a fan of gentoo (if you want ports use freebsd), but this guy is either blind or really really unobservant. the one and only time i ever tried gentoo i had zero problems installing it or finding documentation. in fact documentation is the one thing i like about gentoo.
I use Slackware on an older laptop, but I do give this guy credit for trying Gentoo. Gentoo just isn't a good fit for me as I don't have the time to spare by waiting for it to compile all the apps from scratch. I realize I don't have to do it that way, but if I were to use gentoo, I'd rather do it the way it was designed. So in Slack, I will install the base of the distro and utils, then download and compile the sources for the extra apps (provided they aren't too big), then make a tgz file and install it that way. Keeps the system somewhat clean, and uninstalling apps is a heck of a lot easier that way.
That wasn't a review. That was an "I love Slackware and not Gentoo" rant. Declare it as such. There were so many problems that could have been avoided by reading the well-written install document. Especially the "blocking" bit. The documentation (and the make.conf file) specifically say that unless you want to get your hands dirty, do NOT unmask the unstable packages. Tsk tsk. So much for a fair review.
Summary: Slackware user finds that the distribution he uses and he is familiar with takes him less time to set up and gives him less headaches than a new one, which he has to learn.
Of course you're not learning Linux, you're learning Gentoo, the same way you had to learn Slackware once. Or you're going to tell me your Slackware knowlege applies universally to any other Linux distro? Given the results, I'd really say no.
Poor, poor article.
I switched from Slackware to Gentoo because I got sick of ./configure && make && make install. Even if any of the apt-like Slackware binary package managers had everything I wanted, I'd still be stuck with a build that's either bloated with features I'll never use or doesn't have some feature I want. USE flags are a good thing, Steve, and if you don't want to tweak them, the defaults are usually good. Also, any software that I install manually is independent of managed packages and requires manual updating.
Gentoo updates everthing, including core OS components, with one command. I'm running ~amd64 (the ~ means unstable) with hacks to expose even less stable software (xen and the latest GNOME), and of the >500 "packages" I have installed, only two currently fail to build from source. Another crashes occasionally unless I downgrade to the amd64 (stable) version.
Another complaint I have about Slackware is how easy it is to screw up dependencies during the installation. Gentoo has a rather slim base installation, and I only install dependencies as they're needed. With Slackware I always ended up installing libsomethingoranother because I was afraid programs would break if I didn't include it.
What I like about both Slackware and Gentoo is how they don't "customize" packages like GNOME on Fedora or Solaris, for example. They also don't provide non-standard GUI administration tools, so you're forced to learn "least common denominator" administration practices.
Hey, an intelligent reply! I thought this had devolved...
Anyway, thanks!
I agree that Gentoo can have more optimizations and you don't have to choose to do them. But then why choose Gentoo? Portage is supposed to be good but it didn't meet my expectations. Maybe my expectations were off but they were, nonetheless, my expectations.
And I don't mind doing ./configure; make; make install. I *feel* better about that. And it's standard.
I also agree about the Slackware installer, which is the biggest appeal of MiniSlack (or whatever it's called now) - it makes a minimum install without toasting dependencies. Then they went and made it a whole distro
That Gentoo doesn't do endless customizations on packages was the appeal for this Slacker. This usually keeps me away from "sanitized for your protection" distros like Fedora.
"I agree that Gentoo can have more optimizations and you don't have to choose to do them. But then why choose Gentoo?"
I do use them. I have my USE flags configured to exclude KDE and QT stuff, use GNOME and GTK as much as possible, build a minimalist seamonkey Mozilla, support everything but the kitchen sink with MPlayer, and more. What I originally meant was that you don't have to understand every USE flag to benefit from some of them.
"And I don't mind doing ./configure; make; make install. I *feel* better about that. And it's standard."
I know what you mean. I was skeptical at first, but Portage is just managing the standard process. If anything, I'm more aware of --enable-blah and --disable-whatever options to ./configure after configuring my Gentoo USE flags because it's usually a direct mapping. USE="-esd" adds --disable-esd to the configure parameters, for example. But I can't reasonably maintain everything manually. Even with important packages like MPlayer I tend to miss updates and forget configure parameters doing things the standard way.
Portage actually allows pretty much arbitrary hacking without much trouble. I can mask packages that give me trouble, unmask packages if I want to live dangerously, and set per-package USE flags (to not build the Bittorrent GUI, for example). The /usr/local/portage overlay allows me to use unoffical ebuilds for alternative kernel sources, for example, and bump version numbers for things like reiser4progs that the Gentoo devs don't always update quickly enough. If I only want a minor change, it's no more difficult than compiling from source the standard way. I do it all the time with metacity. "emerge metacity", ^Z it before it starts building, change a line in src/display.c to get my desired focus behavior, and fg to resume building.
Thanks for the tip about MiniSlack. I'll keep it in mind for installations that I don't intend to update and want to work without too much trouble.
Your reply was very helpful and clear. I had set a few USE flags but I kept wondering if I had to, if I would be better with or without them, etc. The Gentoo docs seem to encourage them. But "can" and "should" are different, and I never sat down to test the difference (not being one to believe what I'm told).
Portage is more appealing the way you presented it. I might still give Gentoo a chance on an old 450GX server I've got sitting around, just for kicks. (even though it seems the Gentoo community-at-large thinks I'm an idiot) <grinning, laughing>
OT below here
MiniSlack is now called Zenwalk, by the way. They're starting to fork instead of staying more derivative, but it's still pretty good. The goal is "one app for one task," and they do a fair job at sticking to that. I'm not in love with XFCE (it's default) but I like it well enough and it's easy to use.
Zenwalk has also introduced a package manager, but I haven't tried it (yet). Slackware's lack of a package manager is actually a GOOD THING, in my opinion.
Another alternative or "basic Slackware" I've liked is Slax. It's a bootable, or "live CD," but you can install it to the hard drive easily enough. It has a "modules" feature that's actually pretty cool. Slax found much more hardware than Gentoo, and it fits on a mini cd (sorry, couldn't resist the dig)! It also has a lot of nifty boot options, like loading everything to RAM and loading the GUI by default (which is a pretty snazzy combo). Better, you can build an .ISO with those options pre-configured. I keep a Slax CD with me most of the time; it's infinitely handy.
Well - I use Gentoo for my main system. I'm not a fanboy/zealot of Gentoo though. I use Ubuntu on my laptop because I just wanted a Linux system quick and easy. (Actually - I would run FreeBSD on my laptop but for the fact that my sound card is apparently unsupported. Bummer.)
Anyway - in reading this review, it sounded to me like this guy fell in love with Slackware a long time ago. He is a Slackware fanboy/zealot and tries other distros just so he can poo on them. He learned a long time ago how to do things one way - the Slackware way. And now he's afraid to learn anything new.
It sounds like he wanted a distro that would install everything "out of the box" and "just work" without having to know anything about setting up the X Window System, or configuring anything. That's not Gentoo. I could have told him that ahead of time and saved him a lot of trouble. Gentoo is more for people who want to know how things work.
If he wants an out of the box experience that just works, that's cool. I have no problem with that. I don't think of less of people who want that experience. There are times, such with my laptop, where that's what I want as well. But I'm not going to try Linux From Scratch on my laptop and then write an article complaining about how I had to do all these "wacky" LSF-specific steps that don't export to other distros just to get Linux up and going.
As far as "What are these USE flags all about?" - I guess he has never compiled a program from source. When you compile from source, you have options to include or exclude different compile time options. For me personally, the USE flags are probably the single coolest thing about Gentoo. I don't believe I'm necessarily getting a performance boost, but I know I'm excluding a lot of stuff that I'll never use when I compile a program with certain USE flags enabled, and others disabled.
The USE flags are a simple short cut to compiling everything from source with certain options enabled/disabled. As far as it being a Gentoo-only solution, yeah - sort of, I guess. But if you've compiled source code before, you understand exactly what it's doing and you THANK GOD it's doing it. It saves you a lot of monotonous work that would otherwise go something like:
Download source code
Download patches
Patch the source code
Read the README
Download any source code the original source code depends on.
Download patches for that source code.
Patch that source code.
Read the README
(Repeat until all dependencies have been met.)
Compile all source code dependencies.
Compile original source code.
Install original source code.
Or - use Gentoo and type "emerge <program>" to accomplish the same thing.
At the beginning of his article he told happy Gentoo users to go away. That's kind of funny. He should have took his own advice before ever trying Gentoo. As a Slackware zealot/fanboy, he should just use the One Thing he knows and be happy about it. Because until he's willing to actually learn something new, and actually take the time to read about something new, he's never going to be happy with another distro.
sounds like he wanted a distro that would install everything "out of the box" and "just work" without having to know anything about setting up the X Window System, or configuring anything. That's not Gentoo. I could have told him that ahead of time and saved him a lot of trouble. Gentoo is more for people who want to know how things work.
---Thats not Slackware either.... They guy is too used to how slackware works,, period
The back biters here are making no progress for Linux.
Just their childish egos. Grow up People.
never read such a trolling moronretarded contribution. im coming from slack also, and am quite happy with gentoo. i didn't downloaded any ISOs for 2 years and its still running and up2date.
this article reads like written by a microsoft executive which says: "you may be happy with linux, but i would recommend you our product, 'cause it just 'works'"
...
This is the worst article I've read! I didn't even get past the first page because of the poor consturction and grammar.
OSnews editors: Make your writers read The Elements of Style. It is available for free at http://www.bartleby.com/141/. It's a classic and basic guide to writing.
Language is about communication. How can you express yourself clearly if you don't understand the basic rules of language? I'm trying to be a preachy grammar teacher, but you should have a minimum level of professionalism in your writing for the sake of the readers.
Sorry for the typo. I don't spell check message boards, unfortunately. I do proof read and spell check a billion times when I'm writing an article that thousands of people will read and form their own opinions on. I have, in fact, written for Linux Journal, Newsforge, and OSNews so I know what I'm talking about.
"Your points are contradictory. Slackware DOES apply to other distros, Gentoo does not. This is why I had problems with Gentoo. Very little in Slack is custom - most of it is straight "out of the box."
Which part of the Slackware package management system applies to RedHat, Debian, Arch, etc...?
Slackware isn't the gold standard for the way of doing things. Debian is pretty different from Slackware. RedHat is pretty different from Slackware. And both of those have a larger install base than Slack.
If you want "the one true way" to do thing, you should use FreeBSD bro. That's it's greatest strength in my opinion. FreeBSD isn't just a kernel, it's a complete system. If someone makes a custom distro based on FreeBSD and totally mucks up the way things are done, it would be a valid complaint to say that their way isn't the right way. But with Linux, that just isn't the case. There is no one right way because there is no single distro that dictates how things are done. Whether you like that or not is a matter of opinion.
The, what you call, Slackware way is the UNIX way. And the Slackware pkgtools are nothing but a binary package install-tool, which is more or less "cd / && tar zxf <package> && ./install.sh. Which, again, is more similar to the traditional UNIX way than most other package managers.
There are tons of Slackware features liek this which actually help to make your skills portable, and usually these features have a good reason, too.
Now, paraphrasing Steve, if you don't like Slackware, I AM HAPPY FOR YOU. Shoo. But have the decency to at least bring reasonable arguments to the discussion. Proven procedures (like the UNIX way) are indeed not necessarily the end-all of everything, but new procedures are not even proven.
If you disagree with the "test", make your own, and publish it.
No, you did clearly not read the documentation.
Examples:
You chose a stage 1 install without knowing what it does, only then to complain about how long it took to compile everything.
You wrote the article without even knowing how to install KDE on gentoo, though there is very extensive documentation on the subject which can be found easily.
You still don't know what USE Flags are, though it is described in great depths in the gentoo documentation.
Conclusion:
You are an idiot!
I've already tried Mandrake(actual Mandriva), SuSe, slackware, freebsd and actually using Gentoo. My thoughts are, Mandrake, and Suse for beguining, learning linux. Slackware simple, and powerfull linux but we then start to understand what are conf files, and some other things that we need to do manually. Freebsd is good but lack of hardware support, total control, and we need to know a little of what we are doing.
Gentoo, we learn how linux works, it's not easy but gives you total control, and for god sake read the documentation, and stop saying i can do that or this...
Arch is also good, i've recently installed it to a friend of mine i have no idiea if it's good or not.
Gentoo maybe it's not to ordinary persons but now that i'm used to it i can't leave him, emerge myself!!
The speed boost is good...
How do you learn how Linux works because you install Gentoo?
Do a LFS system and then you know how Linux works. Do the ./configure; make; make install dance everytime, then you know how linux works.
Don't install Gentoo...Gentoo is scripted, you learn nothing but how to work with gentoo. If you want to learn linux, build it from scratch...otherwise you just learn how to use your distro.
I fear OSNews quality is going down,down,down in these times.
BTW it is the first time I see a Linux user thinking and behaving just like any clueless Windows user(*) "Hey,things-are-not-exactly-as-I-am-accustomed to? Do I have to read DOCS? My god, this system sucks!" And he is a long time Slackware user, not a newbie using Mandriva from 2 months.
If this means something about the Linux user base, it means something bad. I hope Linux catches on by creating more clever and educated users, not by lowering itself to meet the mind of retarded.
(*)-I don't mean all Windows users are clueless or lusers. I mean the author of the article looks like a clueless one.
(**)-Full disclosure: I'm a Gentoo user.





