From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ycardz.com(server52.aitcom.net[208.234.0.31]) (1457 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Tue, 29 Aug 2000 15:45:58 -0400 (EDT) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from 2034.iadfw.net (2034.iadfw.net [206.66.13.175]) by ycardz.com (8.8.8/8.8.5) with SMTP id PAA24576 for ; Tue, 29 Aug 2000 15:45:57 -0400 Message-Id: <3.0.5.32.20000829144121.007a53b0@ycardz.com> X-Sender: davros@ycardz.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 29 Aug 2000 14:41:21 -0500 To: speakup@braille.uwo.ca From: Buddy Brannan Subject: Stupid kernel question Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" List-Id: Hi, OK, so I'm reading through the new Slackware book that's online as part of my campaign to study for LPI certification, and in the kernel section on building a kernel, it says to do (from the /usr/src/linux directory, after making a backup of the old kernel, system.map, and so on) cat arch/i386/boot/zImage > /vmlinuz (or bzImage, as the case my be) I never actually noticed the sequence of commands here, since my last step was always make install, which generally did the correct bit of magic to get the new kernel working. So...is there any particular reason you copy the kernel this way, rather than using cp instead? I'd really love to know if anyone can tell me. ... Thanks. -- Buddy Brannan, KB5ELV Email: davros@ycardz.com Voice mail: 877-791-5298 All opinions are all mine!