From owner-freebsd-hackers  Sun Oct 20 18:40:37 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA10150
          for hackers-outgoing; Sun, 20 Oct 1996 18:40:37 -0700 (PDT)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA10145
          for <hackers@FreeBSD.org>; Sun, 20 Oct 1996 18:40:30 -0700 (PDT)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id LAA03697; Mon, 21 Oct 1996 11:39:51 +1000 (EST)
Date: Mon, 21 Oct 1996 11:39:50 +1000 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Julian Elischer <julian@whistle.com>
cc: hackers@FreeBSD.org
Subject: Re: Read-only root partition. [SYSLOG]
In-Reply-To: <326A99D7.167EB0E7@whistle.com>
Message-ID: <Pine.BSF.3.91.961021113749.548E-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk



On Sun, 20 Oct 1996, Julian Elischer wrote:

> 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..

What about putting /dev/log into /var/run?  Or another /var/ subdir  for 
the purposes of unix domain sockets (e.g. /tmp/msql.sock is another 
candidate)

Danny