On Fri, Aug 04, 2000 at 08:14:59PM -0700, Mike & Tracy Holt wrote:
> > Follow the instructions on www.linux-mandrake.com/en/fupdates.php3
> > for the kernel update in 7.1. Those instructions work and work
> > *flawlessly*. I've used them to install two kernels from cooker
> > (2.2.17-0.12mdk and 2.2.17-0.16mdk) while keeping my 2.2.15 kernel
> > which is default from the installation as a "failsafe" kernel.
>
> Thank you, I found the directions through another persons post and have got
> my new kernel up and running now. I would like to ask if somehow we could
> get the procedure shortened however, it's quite a list of things to do for
> an rpm update? I don't know if this is possible, but it would be nice.
You're thinking of it in terms of an application again. It's not
just a "rpm update"... it's a kernel update. RPM can do many things,
but there are certain things it can't do. I, for one, would not want
anyone to automate building my kernel. I find the idea scary. When
my kernel gets updated, I want to know what's going on... there are
too many areas for error by throwing a bunch of commands into an RPM
post-install script and, quite frankly, I'd like to be able to boot
back into Linux once it's done.
If an application installed by RPM is messed up, it's easy to deal
with. Try cleaning up a kernel installation gone haywire and you'll
see how different it is.
I think that if the directions are clear and concise and easily
followed (and *work*) then the job is done. I mean, really... how
long did it take you to follow those instructions? Five minutes?
Possibly 10? You've got a working kernel now, correct?
I find that preferrable to someone attempting a quickie RPM hack to
try and accomplish the same thing, take 1 minute, and find I can't
boot back into the system.
--
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
// Danen Consulting Services www.danen.net, www.freezer-burn.org
// MandrakeSoft, Inc. www.linux-mandrake.com
1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD
Current Linux uptime: 1 day 22 hours 32 minutes.
