From owner-freebsd-current@FreeBSD.ORG Thu Oct 18 09:25:54 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 35D49456 for ; Thu, 18 Oct 2012 09:25:54 +0000 (UTC) (envelope-from mueller23@insightbb.com) Received: from mail.insightbb.com (smtp1.insight.synacor.com [208.47.185.23]) by mx1.freebsd.org (Postfix) with ESMTP id EAD8F8FC18 for ; Thu, 18 Oct 2012 09:25:53 +0000 (UTC) X_CMAE_Category: 0,0 Undefined,Undefined X-CNFS-Analysis: v=2.0 cv=ZYCfx7pA c=1 sm=0 a=Dm9TOXL4taQ+Gy1KovpL+A==:17 a=8WOtGVI2NMsA:10 a=jLN7EqiLvroA:10 a=9YQ-1ebCAAAA:8 a=O7lrEePju-kA:10 a=7FMKqd2x0ZHJREQOobQA:9 a=Dm9TOXL4taQ+Gy1KovpL+A==:117 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Authentication-Results: smtp02.insight.synacor.com header.from=mueller23@insightbb.com; sender-id=softfail Authentication-Results: smtp02.insight.synacor.com smtp.mail=mueller23@insightbb.com; spf=softfail; sender-id=softfail Received-SPF: softfail (smtp02.insight.synacor.com: transitional domain insightbb.com does not designate 74.130.198.7 as permitted sender) Received: from [74.130.198.7] ([74.130.198.7:48859] helo=localhost) by mail.insightbb.com (envelope-from ) (ecelerity 2.2.3.49 r(42060/42061)) with ESMTP id C0/7D-23131-B1BCF705; Thu, 18 Oct 2012 05:25:47 -0400 Date: Thu, 18 Oct 2012 05:25:47 -0400 Message-ID: From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: A little question about safe mode Cc: Alexander Yerenkow 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 09:25:54 -0000 > 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) > 2. If I enter ufs:ada0s1a rw - I have / mounted in read-only anyway. <== Is > this bug?... > 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. > 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 :) > Thanks. > -- > Regards, > Alexander Yerenkow I think you would need to mount -uw / u being for update. It looks like your post describes single-user mode rather than safe mode. When there is no /etc/fstab or the fstab is unworkable, you are put into single-user mode with a prompt to enter full path to shell or Enter for /bin/sh Maybe you could create your boot media with /etc/fstab pointing to the correct partition? Tom