From owner-freebsd-hackers Tue Dec 16 15:48:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA12276 for hackers-outgoing; Tue, 16 Dec 1997 15:48:04 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA12199 for ; Tue, 16 Dec 1997 15:47:49 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xi6Wp-0001G9-00; Tue, 16 Dec 1997 15:35:55 -0800 Date: Tue, 16 Dec 1997 15:35:48 -0800 (PST) From: Tom To: Karl Pielorz cc: hackers@freebsd.org Subject: Re: Compiling Kernels on remote machine & using 'wrong' versions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 16 Dec 1997, Karl Pielorz wrote: > Is there an easy way to Use the 'fast' machine to compile Kernels for the slow > machine (which is fairly quick at NFS) - if so - how? (for example the > slow machine appears as: Yes. Kernel source will build from any directory, so that directory could be anywhere. I build kernels on a development machine which is also an NFS server, so I just mount the "sys" directory on the clients, and do a "make install" to install. > Final question - I accidentally booted the 2.2.5 system with a 2.2.2 > kernel - it boots OK, and seems to run OK (yes, I can hear the screams of > 'Noooohhh!!' from here) - but is it really that bad - considering I don't > really care about the fate of the slow 2.2.5 machine? - That way I can > keep all my stuff on the 2.2.2 machine (which is nicely, safely stable & > remote) - and just run the 2.2.5 on 2.2.2 kernels... Why are you doing development on 2.2.2 in the first place? All the 2.2 systems are somewhat compatible, but various programs that poke around in kernel memory may die. Tom