>From: rhealey@altair.helios.mn.org (Rob Healey)
>Date: Mon, 18 Dec 1995 20:36:29 -0600 (CST)
>
>> >Date: Sun, 17 Dec 1995 20:09:27 -0800
>> >From: Jonathan Stone <jonathan@dsg.stanford.edu>
>> 
>> >To build kernels, /usr/src/sys/arch/compile/ needs to have a read-write
>> >filesystem mounted on it.
>> 
>> We could replace each /usr/src/sys/arch/*/compile directory with a
>> symlink to /usr/obj/sys/arch/*/compile, instead.  Each
>> /usr/src/sys/arch/*/Makefile would need an obj: target to create the
>> link.
>> 
>	In a word: YUK! Symlinks are evil, evil, evil, evil, evil. union
>	mounts give the same functionality and you don't have to chase
>	symlinks all over god's creation if you need to move things.

I've never had a kernel panic because of a symlink.  I'm not sure the
same would be true for union mounts, if I were to use them.

I often use symlinks for my work (setting up netlists for simulation,
etc.).  They're not that bad if managed intelligently.
-- 
Mike Long <mike.long@analog.com>           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