From owner-freebsd-current@FreeBSD.ORG Thu Oct 18 10:34:34 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C611CA9 for ; Thu, 18 Oct 2012 10:34:34 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 38C078FC0A for ; Thu, 18 Oct 2012 10:34:32 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA16849; Thu, 18 Oct 2012 13:34:29 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TOnQr-0003wY-2p; Thu, 18 Oct 2012 13:34:29 +0300 Message-ID: <507FDB33.10900@FreeBSD.org> Date: Thu, 18 Oct 2012 13:34:27 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121013 Thunderbird/16.0.1 MIME-Version: 1.0 To: Alexander Yerenkow Subject: Re: A little question about safe mode References: <507FB6C7.50402@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 18 Oct 2012 10:34:34 -0000 on 18/10/2012 12:11 Alexander Yerenkow said the following: > > > 2012/10/18 Andriy Gapon > > > > First, I see "safe mode" mentioned in the subject, but nowhere in the body of > the message? So, what's up with the safe mode? :-) > > > The single mode of course, which is forced :) Mistype, sorry. > > > on 18/10/2012 10:35 Alexander Yerenkow said the following: > > Hello there. > > I have problem here, and don't know if it's bug or "feature" :) > > If I prerare boot media (hdd, sd card,usb, etc) with FreeBSD, and NOT > > create there fstab, I see such behavior: > > > > 1. I need enter manually where from mount root (e.g. ufs:ada0s1a or > > ufs:ada0s1a rw) > > This is a feature. > You might want consider using options ROOTDEVNAME in your kernel. > > > Okay, then why little help there mentioning "rw" as an option? It's of bug in > help there, or in parsing mount options (rw is ignored). Again, it's a feature, "rw" is simply ignored. The help message is just trying to confuse you. > If I'm not fully clear - I can provide some screenshots. > > > > > 2. If I enter ufs:ada0s1a rw - I have / mounted in read-only anyway. <== Is > > this bug?... > > It looks like a feature. The low-level mountroot code always mounts / as r/o. > > It's supposed to be later remounted as r/w by rc.d/root script. > > > Yes, it's feature when it mounting with default parameters (e.g. with none). But > what about rw? This should be answered above. > > 3. If I try to make it rw, with commands > > mount -o rw -u /dev/ada0s1a / > > there is no errors, but root is still RO. > > This sounds like a bug. > Is there anything on the system console? > > > Nope, I'm already on console in single mode. > > > > 4. I can't umount / remount some elsewhere this disk, just to create fstab > > (it's already mounted and can't be updated). > > > > So, is this as-by-design, that you need "any other" media to boot, just to > > create fstab, or there is "rw" mode broken, or I just missed something? > > > > It's very disappointing to be able boot interactively into system, but have > > no way to "fix" fstab to make it non-interactively bootable :) > > You can try to create an md-based filesystem, mount it under /mnt and then > unionfs-mount it over /etc. > > > That's not solve problem that on my rootfs no fstab exists, so next boot will > bring me to same situation. You may try to edit /etc/fstab on top of unionfs and then see if you can remount the real root r/w. > If someone willing to help/debug with this thing - get any bootable media (like > live FreeBSD), and just rename/move/delete fstab file, and simply boot. There indeed appears to be a bug. Unfortunately, ENOTIME to dig into this. -- Andriy Gapon