A few days with Gentoo
I installed Gentoo as a little project last weekend, on my Dell Inspiron 1525. It took a fair old chunk of the weekend, and was a great deal of fun. I'm really happy with it so far.
Following through the Gentoo Handbook is great -- it's basically a hands-on tutorial to learn how various parts of Linux work. I wrote my very own /etc/fstab; I compiled a kernel for the first time; I battled with X for a bit; I did all kinds of things. It's a massive learning experience.
Despite using Linux since about 2001 I've never compiled the kernel before. I've never needed to -- I guess I was lucky enough to begin using in a time when for everyday use a quick Google and a bit of userland tweaking could fix most things. And nowadays in most distros you get a kernel with a kitchen sink compiled in, so I'm never really likely to need to compile a kernel for everyday use. I don't need to, but I want to, however, just for the sheer nerdy fun of it.
Going through menuconfig made me realise how much totally unnecessary stuff is compiled into a generic stock kernel. It was fun to recompile and get rid of all that cruft. In terms of performance/resources I don't think the bloat particularly matters; as far as I understand there's no real harm in having it all there as modules, and it's obviously useful to put it all in to cover all bases for a generic distro. But it's nice to get rid of junk!
I used genkernel first, based on the .config used for the CD image, to just get something that works. And it did to some extent. But X didn't work. So I tried to recompile the whole shebang myself and include all the i915 drivers. But then I got a kernel panic right at the start of boot. So I tried recompiling based on the .config for the kernel bundled on my Debian partition, where my crappy Intel graphics work just fine. But I still got kernel panics at boot. Eventually I clocked that you can use genkernel --menuconfig, getting all the nice working stuff from genkernel but tweaking to your own tastes. So I opted for my i915 bits as modules and away we went!
I really like portage and emerge. Compiling from source obviously does take much longer than just downloading a binary, but it's fun (if you like that sort of thing.) I must guiltily admit to having kind of liked watching compilation output fly through the terminal since I first started with Linux. But back then you had to hand resolve any dependencies, and for that Dante would have reserved a whole separate layer of hell if he'd had a computer. With emerge you get to see gcc in action, but all your dependencies are resolved for you! Heaven!
I will concede, though, that it can be a pain to wait for a program to compile when you just want it quickly. But I figure the wait-time will go down over time, simply by virtue of more and more libraries and whatnot having already been compiled and ready for use on my system.
As far as I've read, compiling to your chip's specific architecture, as Gentoo does, doesn't actually necessarily make amazing speed boosts. But who cares, it's fun. And I have to say Firefox was absolutely blisteringly fast when I installed it, but that could well just be because it's a fresh install without years of accumulated cruft in .mozilla.
I hear on the grapevine that USE flags are the best thing about portage/emerge, though I've not yet used the system long enough to know just why that is.
So overall I'm very happy with my lovely new Gentoo, chiefly because of all the stuff I've learnt in the process of using it. And I'm only about 5 days in, so here's to learning more.
Following through the Gentoo Handbook is great -- it's basically a hands-on tutorial to learn how various parts of Linux work. I wrote my very own /etc/fstab; I compiled a kernel for the first time; I battled with X for a bit; I did all kinds of things. It's a massive learning experience.
Despite using Linux since about 2001 I've never compiled the kernel before. I've never needed to -- I guess I was lucky enough to begin using in a time when for everyday use a quick Google and a bit of userland tweaking could fix most things. And nowadays in most distros you get a kernel with a kitchen sink compiled in, so I'm never really likely to need to compile a kernel for everyday use. I don't need to, but I want to, however, just for the sheer nerdy fun of it.
Going through menuconfig made me realise how much totally unnecessary stuff is compiled into a generic stock kernel. It was fun to recompile and get rid of all that cruft. In terms of performance/resources I don't think the bloat particularly matters; as far as I understand there's no real harm in having it all there as modules, and it's obviously useful to put it all in to cover all bases for a generic distro. But it's nice to get rid of junk!
I used genkernel first, based on the .config used for the CD image, to just get something that works. And it did to some extent. But X didn't work. So I tried to recompile the whole shebang myself and include all the i915 drivers. But then I got a kernel panic right at the start of boot. So I tried recompiling based on the .config for the kernel bundled on my Debian partition, where my crappy Intel graphics work just fine. But I still got kernel panics at boot. Eventually I clocked that you can use genkernel --menuconfig, getting all the nice working stuff from genkernel but tweaking to your own tastes. So I opted for my i915 bits as modules and away we went!
I really like portage and emerge. Compiling from source obviously does take much longer than just downloading a binary, but it's fun (if you like that sort of thing.) I must guiltily admit to having kind of liked watching compilation output fly through the terminal since I first started with Linux. But back then you had to hand resolve any dependencies, and for that Dante would have reserved a whole separate layer of hell if he'd had a computer. With emerge you get to see gcc in action, but all your dependencies are resolved for you! Heaven!
I will concede, though, that it can be a pain to wait for a program to compile when you just want it quickly. But I figure the wait-time will go down over time, simply by virtue of more and more libraries and whatnot having already been compiled and ready for use on my system.
As far as I've read, compiling to your chip's specific architecture, as Gentoo does, doesn't actually necessarily make amazing speed boosts. But who cares, it's fun. And I have to say Firefox was absolutely blisteringly fast when I installed it, but that could well just be because it's a fresh install without years of accumulated cruft in .mozilla.
I hear on the grapevine that USE flags are the best thing about portage/emerge, though I've not yet used the system long enough to know just why that is.
So overall I'm very happy with my lovely new Gentoo, chiefly because of all the stuff I've learnt in the process of using it. And I'm only about 5 days in, so here's to learning more.
