From owner-freebsd-hackers  Sun Oct 20 14:34:04 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA15955
          for hackers-outgoing; Sun, 20 Oct 1996 14:34:04 -0700 (PDT)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA15948
          for <hackers@freebsd.org>; Sun, 20 Oct 1996 14:34:01 -0700 (PDT)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.6/8.7.3) with SMTP id OAA12084 for <hackers@freebsd.org>; Sun, 20 Oct 1996 14:32:16 -0700 (PDT)
Message-ID: <326A99D7.167EB0E7@whistle.com>
Date: Sun, 20 Oct 1996 14:30:00 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: Read-only root partition. [SYSLOG]
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Ok so we've all looked at this before..
The main problem to haveing a read-only root filesystem would seem to be 
the pipe created by syslog in /dev.

/dev/log is a unix domain socket created when syslogd starts up.

Possible options include..

1/
adding a symlink to /var/log/syslog_socket.
this has a few problems.. while we can change all our programs
to use the new address, and binaries that are old can get there
via the symlink, but what about BSDI?
(and linux?) 
can we leave a symlink in /dev permanently?

Are we destined to have to support the symlink forever?
DEVFS can support symlinks

2/ 
should devfs support sockets directly?

3/
if the socket already exists in /dev in the r/o filesystem,
can not syslogd just use it?