From owner-freebsd-security Mon Sep 28 01:42:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29444 for freebsd-security-outgoing; Mon, 28 Sep 1998 01:42:38 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from rnocserv.urc.ac.ru (rnocserv.urc.ac.ru [193.233.85.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29189 for ; Mon, 28 Sep 1998 01:41:20 -0700 (PDT) (envelope-from anton@urc.ac.ru) Received: from urc.ac.ru (Belle.urc.ac.ru [193.233.85.55]) by rnocserv.urc.ac.ru (8.8.8/8.8.8) with ESMTP id OAA02065; Mon, 28 Sep 1998 14:36:19 +0600 (ESS) (envelope-from anton@urc.ac.ru) Message-ID: <360F4A82.2A2E8157@urc.ac.ru> Date: Mon, 28 Sep 1998 14:36:18 +0600 From: Anton Voronin Organization: URC FREEnet X-Mailer: Mozilla 4.5b1 [ru] (X11; I; FreeBSD 2.2.7-STABLE i386) X-Accept-Language: ru MIME-Version: 1.0 To: Allen Smith , freebsd-security@FreeBSD.ORG Subject: Re: Booting from NT ? References: <199809262242.PAA24523@usr04.primenet.com> <9809280220.ZM6404@beatrice.rutgers.edu> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Allen Smith wrote: > Question... what does happen if one has a R/O root filesystem, > including /dev, without DEVFS? I'm constructing a firewall computer > with a (switchable - a nice facility of some Seagate drives) hard > drive for root, a second writeable drive for /var and swap, and a /tmp > MFS. What problems am I likely to run into with /dev? I'd really > prefer not to have it as a symlink to /var/dev or some such... > > -Allen > > It needs to write /dev/console but it does this before mounting according to fstab. If you protect your hard drive it probably won't work. Try to just mount it with -ro option. Anton -- Anton Voronin | Ural Regional Center of FREEnet, | Southern Ural University, Chelyabinsk, Russia http://www.urc.ac.ru/~anton | Programmer & System Administrator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message