| 1 |
back in the day, this was why i went gentoo in the first place. i |
| 2 |
needed a better scheduler and compiling a new kernel off red hat for |
| 3 |
instance almost always broke other stuff. |
| 4 |
|
| 5 |
gentoo made my life easier. |
| 6 |
|
| 7 |
On 12 28, 08, at 7:32 AM, kashani wrote: |
| 8 |
|
| 9 |
>> |
| 10 |
> |
| 11 |
> I'll second what Hung said, getting your kernel right takes a bit of |
| 12 |
> time. |
| 13 |
> |
| 14 |
> However I'll add a few points. Back in the day I used to build |
| 15 |
> super stripped down kernels, but eventually realized it was kinda |
| 16 |
> ridiculous. Why spend almost thirty hours for almost no real world |
| 17 |
> gain other than driving yourself insane? It was almost worth my time |
| 18 |
> on a Sparc5 with 64MB, but today you're better off spending your |
| 19 |
> time cooking dinner and spending the $20 you saved vs the restaurant |
| 20 |
> on RAM. Well maybe you'd need to do that twice. :-) |
| 21 |
> On the other hand I learned a fair amount about what not to screw |
| 22 |
> with by ripping everything out. If you want to go that route, it'll |
| 23 |
> take you around a week to make almost all the mistakes. Realize this |
| 24 |
> will happen and then enjoy the process. I also recommend taking |
| 25 |
> notes or you'll keep repeating your mistakes. |
| 26 |
|
| 27 |
LOL yeah. this happened to me. |
| 28 |
|
| 29 |
> The other thing is don't get carried away in stripping things out |
| 30 |
> of your kernel. Need to mount and ISO, oops you removed loopback |
| 31 |
> support. Need to make your machine into a DHCP server, oops your |
| 32 |
> removed (gah I should remember this) sockets (i think). Need to use |
| 33 |
> OpenVPN, oops you removed tap/tun interfaces. The list goes on and |
| 34 |
> on. Yeah you can install those as modules once you figure out that |
| 35 |
> they are missing which can be frustrating when the errors aren't |
| 36 |
> very clear. |
| 37 |
> |
| 38 |
|
| 39 |
*nods* i do this too. i strip everything off--- hardware that i don't |
| 40 |
need but i do keep a lot of things turned on like FS stuff. if the box |
| 41 |
isn't a server, i turn on the networking stuff like tap/tun interfaces |
| 42 |
as modules. if the box is a server then it gets turned on. |
| 43 |
|
| 44 |
i also make sure that i turn a lot of FS on. even reiserfs. especially |
| 45 |
ntfs. etc. etc. you never know if you'll need those in the future. |
| 46 |
|
| 47 |
> My advice is take the middle path. Cut the complete crap out like |
| 48 |
> parallel ports, ISDN, and SCSI cards that aren't actually in your |
| 49 |
> system. Leave most of the rest alone for the most part unless you're |
| 50 |
> pretty sure you know what it is. As you get a bit more comfortable |
| 51 |
> and have a history of working kernels you can experiment more. |
| 52 |
> |
| 53 |
> kashani |
| 54 |
|
| 55 |
|
| 56 |
but yeah, really took a lot of time and learning and messing around. |
| 57 |
have fun! |
| 58 |
|
| 59 |
|
| 60 |
Cocoy |
| 61 |
www.twitter.com/cocoy |
| 62 |
"People who are really serious about software should make their own |
| 63 |
hardware" -- Alan Kay |
Archives