From owner-freebsd-current@FreeBSD.ORG Tue Oct 24 20:37:07 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 727D916A403 for ; Tue, 24 Oct 2006 20:37:07 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA6D443D53 for ; Tue, 24 Oct 2006 20:37:05 +0000 (GMT) (envelope-from lydianconcepts@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so1445240uge for ; Tue, 24 Oct 2006 13:37:00 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JXQwbSBHXCbXik/qFQpllMwLgdIrhFPkNXS/A5wkFyTllUFkgkuGnX49/RngNqzEwnPAtxoDszP9Olb/pInezHtJWSxNm+95YiXUL6MrTgWaEqa8o7MGj7qJlx1Alf3TjWyESePJpFQf3ZYEwGKL4fzxqADUpMGxhveMq5O3R9o= Received: by 10.78.128.15 with SMTP id a15mr9911723hud; Tue, 24 Oct 2006 13:37:00 -0700 (PDT) Received: by 10.78.197.4 with HTTP; Tue, 24 Oct 2006 13:37:00 -0700 (PDT) Message-ID: <7579f7fb0610241337u10eceb27pba6adf65ebf19dab@mail.gmail.com> Date: Tue, 24 Oct 2006 13:37:00 -0700 From: "Matthew Jacob" To: "Michiel Boland" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-current@freebsd.org Subject: Re: 'ro' option in fstab not recognized? 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: Tue, 24 Oct 2006 20:37:07 -0000 No, you're not stupid. This has been happening in 6 and -current for months now. I just haven't had time to figure out what got broken. You can fix it after mount by doing mount -u -o ro /usr/j/usr/local On 10/24/06, Michiel Boland wrote: > Hi. I must be extremely stupid. I have this in my fstab > > /usr/local /usr/j/usr/local nullfs ro 0 0 > > but /usr/j/usr/local still appears to be mounted read-write. > > Oh wait, I guess this is also already covered by PR 100164. > > Line 197 of sys/mount/mount.c explicitly adds an option "noro". > Looks to me like this makes it impossible to mount *any* file system > read-only, except by explicitly passing flags to mount. > Surely this is not what fstab was designed for? :) > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >