From owner-freebsd-current@FreeBSD.ORG Wed Sep 27 17:15:27 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5108716A403 for ; Wed, 27 Sep 2006 17:15:27 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BB2E43D55 for ; Wed, 27 Sep 2006 17:15:18 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from atlantis.dp.ua (localhost [127.0.0.1]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k8RHF9mT015428 for ; Wed, 27 Sep 2006 20:15:09 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Received: from localhost (dmitry@localhost) by atlantis.dp.ua (8.13.1/8.13.1/Submit) with ESMTP id k8RHF9K5015423 for ; Wed, 27 Sep 2006 20:15:09 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Wed, 27 Sep 2006 20:15:09 +0300 (EEST) From: Dmitry Pryanishnikov To: freebsd-current@freebsd.org In-Reply-To: <20060927164323.S40914@atlantis.atlantis.dp.ua> Message-ID: <20060927201233.L79847@atlantis.atlantis.dp.ua> References: <20060927164323.S40914@atlantis.atlantis.dp.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: mount -a doesn't obey "ro" in /etc/fstab X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2006 17:15:27 -0000 On Wed, 27 Sep 2006, Dmitry Pryanishnikov wrote: > will apply cleanly). I've noticed the something very new (and annoying) after > the upgrade: all filesystems listed in /etc/fstab with "ro" are still mounted > as R/W. Here is my /etc/fstab: > > # Device Mountpoint FStype Options Dump Pass# > /dev/ad0s3b none swap sw 0 0 > /dev/ad0s4a / ufs rw,sync 0 1 > /dev/ad0s4e /usr ufs rw 0 2 > /dev/ad0s3a /mnt3 ufs ro 0 0 > /dev/ad0s3d /mnt3/usr ufs ro 0 0 > Is this breakage well-known, or something new? I can confirm that this bug isn't brand new: CURRENT as of 20-Aug on my notebook already has it. So it's kinda "mature" (; Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE