From owner-freebsd-current Fri Apr 19 12:36:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA26907 for current-outgoing; Fri, 19 Apr 1996 12:36:08 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA26848 for ; Fri, 19 Apr 1996 12:36:01 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA08792; Fri, 19 Apr 1996 12:29:57 -0700 From: Terry Lambert Message-Id: <199604191929.MAA08792@phaeton.artisoft.com> Subject: Re: DEVFS and syslogd To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 19 Apr 1996 12:29:56 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG, julian@TFS.COM, ejc@nasvr1.cb.att.com In-Reply-To: <199604191752.TAA06829@uriah.heep.sax.de> from "J Wunsch" at Apr 19, 96 07:52:28 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Added options DEVFS in my kernel. Added a line at the end of my fstab > > "dev /dev devfs rw 0 0" everything seems to work except syslogd. When I boot > > I get the error "syslogd: cannot create /dev/log: operation not supported" > > Is this a known problem, did I do something wrong? > > It's a known problem. > > The clean solution would be moving /dev/log to /var/run/log, but this > will break binary compatibility for statically linked old binaries. > > Next to this, we could create it under /var/run/log, but maintain a > symlink to /dev/log for compatibility. Alas, devfs doesn't understand > symlinks yet either. Or register a portal to a dumb log concatenation program. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.