From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.ufw2.com([216.163.19.154]) (2942 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Tue, 29 Aug 2000 21:56:20 -0400 (EDT) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from [216.163.21.20] by gate.ufw2.com for speakup@braille.uwo.ca id UAA07480; Tue Aug 29 20:55:33 2000 Received: from hardb ([216.163.21.59]) by mail.ufw2.com (Build 101 8.9.3/NT-8.9.3) with SMTP id UAA00936 for ; Tue, 29 Aug 2000 20:56:10 -0500 Message-Id: <3.0.6.32.20000829210257.007b1e90@mail.ufw2.com> X-Sender: bharding@mail.ufw2.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 29 Aug 2000 21:02:57 -0500 Subject: Re: Stupid kernel question In-Reply-To: References: <3.0.5.32.20000829144121.007a53b0@ycardz.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: speakup@braille.uwo.ca From: Brent Harding List-Id: What's the deal of redhat and kernel any ways? Does redhat's kernel compiling differ from debian's or slackware's? I may soon be accessing a redhat site, so am wondering about some of these differences, I'm lost with debian and rc.d files, how to make things right, and no netconfig utility, if I use my base bootstrap to config network and do no more, on an existing system, could that work? At 02:20 PM 8/29/00 -0500, you wrote: >Actually, if you use the cp command it works just fine. That is what I >have been using. I don't think the howto specifies how to copy the file, >just to do so. So I have always used the cp command. And for the record, >you can name the new kernel any valid filename as far as I can tell. I >know I have gone to using names that mean something to me. I typically use >a date (8-11) for a general purpose kernel. If it is for a specific reason >I name it such again with a date. > >Redhat uses a softlink to make vmlinuz point to a kernel that is like >vmlinuz-2.2.14 (or whatever version of kernel is there). I find making a >softlink to just add more steps. I name it at will and add the entry to >lilo.conf. Then run lilo. This keeps the backup in place and ready for a >screw up. I have made kernels that didn't work. But by adding the entry to >lilo.conf and leaving what was already there exactly where it started has >always left me able to recover from my errors. > >Certainly there may be some textbook reason for certain conventions. But >they are at the heart conventions and not rules. Until someone gives me >some reason to name my kernel vmlinuz I can only guess it is so anyone >will know its name. But hey, lilo.conf will clear that mystery up so I >continue in my ways. > >-- >Kirk Wood >Cpt.Kirk@1tree.net >------------------ > >Seek simplicity -- and distrust it. > Alfred North Whitehead > > > >_______________________________________________ >Speakup mailing list >Speakup@braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > >