Subject: Re: Defining the Machine Name in a Kernel Build
To: None <cjs@portal.ca>
From: Mike Long <mike.long@analog.com>
List: current-users
Date: 11/18/1996 01:18:08
>Date: Sun, 17 Nov 1996 21:25:43 -0800 (PST)
>From: Curt Sampson <cjs@portal.ca>
>Back in the days of 1.0, the name one was using for one's kernel
>used to be #define'd. (I discovered this when I thought it would
>be intelligent to name a kernel I used on several production systems
>PORTAL. :-)) I notice that this doesn't seem to happen any more.
>Why did we do this originally, and why did it vanish? (Well, I may
>know the answer to the latter question.)
This was a feature of old config, which Went Away in new config. If
you can find a copy of the old BSD 02.config doc, it states that this
was to support HOST-specific hacks in the kernel source. It's a bad
idea to #define the config name by default, as you found out. If you
really want to do this, it's easy enough to add an equivalent option
to your config.
--
Mike Long <mike.long@analog.com> <URL:http://www.shore.net/~mikel>
VLSI Design Engineer finger mikel@shore.net for PGP public key
Analog Devices, CPD Division CCBF225E7D3F7ECB2C8F7ABB15D9BE7B
Norwood, MA 02062 USA (eq (opinion 'ADI) (opinion 'mike)) -> nil