Harry Putnam wrote: > Stroller <strol...@stellar.eclipse.co.uk> writes: > > >> Any time I spend messing with obscure kernel config options is time I >> could be spending reading a good book, instead [1]. >> Sorry, spending time configuring my kernel loses, as does this thread. >> > > I'm with you Stroller. > > Although I do have to admit and should admit since I'm OP on this > thread. If I had of inserted the .config from running kernel. I > would have been done on the first try.. The dozen or so questions were > nearly all no answers. A few didn't default the way I wanted so I didn't > accept the default... maybe two were like that. > > I fully agree with your point about what it really takes to `know' how > to configure a kernel. People get a little too much mileage from the > breezy ` I do it in 5 minutes' line. When all they really did was > move the .config file. > >
Maybe 20 minutes if you don't just move the .config tho. It's not that hard to do. Heck, the hardest part to me is finding out what chips is on cards and stuff. I usually do that before I but tho. I like the zoom feature on newegg for that reason. You can read what chips are on drive controllers and such. Then you know what drivers to use and whether it will work or not. I could probably config mine now in less than ten minutes since I know my hardware. Dale :-) :-)
