On 04/12/12 23:46, Alan Corey wrote:
I've just uploaded a small program I wrote for configuring a kernel
based on the devices found by doing a dmesg with a generic kernel. It
tries to detect whether you're running a generic kernel by looking at
uname output then runs dmesg via a pipe, copies over
/usr/src/sys/arch/i386/conf/GENERIC line by line, commenting out
devices it doesn't find in dmesg. It's only been tested with i386,
but was written under 5.0 and also tested under 4.7. I'm running both
kernels now. It's very generic C and hopefully has no dependancies.
Alan
http://ab1jx.webs.com/calcs/kr/index.html
Hello Alan,
Neat idea in theory, but actually horrid in the real world.
If we were on 486's with 32M ram as my ancient Compudyne's
were, it would make sense, and in fact I made SHRIMP kernels
for a while--
But then one day I was demoing OpenBSD to some people and
they wanted to see it run on their shiny new P3 Dell. Not having
a CD handy I moved the disk over to the Dell were it booted,
but couldn't get on the net.
I'd zapped out the 3com definitions on SHRIMP, to save space.
I did save space but I certainly didn't save face. I danced around
that as well as I could, but that and a few other incidents taught
me that trying to be "efficient" had costs. When I lost a web
server once I found an unused Dell and got the server up and
running again in about 5 minutes. Thinking about where I'd
have been with SHRIMP, I'd have lost more time, etc.
Moral: efficiencies today are not what they were in 1995 and
it just doesn't make sense to do that.
You get points for doing this, but this particular item isn't a
good thing to do.
--STeve Andre'
ps: you won't get any help from people here with a shredded
kernel, either.
