From owner-freebsd-current@FreeBSD.ORG Thu Oct 18 07:35:58 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 6AAAC20E for ; Thu, 18 Oct 2012 07:35:58 +0000 (UTC) (envelope-from yerenkow@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2A1688FC16 for ; Thu, 18 Oct 2012 07:35:57 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id k10so17309784iea.13 for ; Thu, 18 Oct 2012 00:35:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=7vgu2ueygbbZ7RXzk6EdrmQGMfw+QGeHTsYAu8VW04s=; b=WaqaURgHFFUOcEw6api513r7Edm4Bdw4FWrpwSTKH/d7uT7QPwxKzxxXp6Z2VA9pCA b6/sorC894bWfpXDmG9VxwZZ8uKH0g9YqlgHj1JtpnFjlH2t2RHnKj4fTG7GBrtVni/c mVYbWE9L7h1jcwCRn/yO2o8FFS1W+Pys7g582EiP/haMOwG+OSpT1QJiUx1R0LPg2jhn kTJAgXsqUykCxNU6IqqP3iG35CZ/7rmIIEbNGTxx3vTyJlielcC71I4mcC1xM8x9vfxW GhYvkMnXrtNmcmDw6lae1T+258Qi9BaGganStC/uWWDPZQvfbVmT/kYc6vPExyDHmTZM ZwaA== MIME-Version: 1.0 Received: by 10.50.42.197 with SMTP id q5mr3945235igl.21.1350545757467; Thu, 18 Oct 2012 00:35:57 -0700 (PDT) Received: by 10.64.32.10 with HTTP; Thu, 18 Oct 2012 00:35:57 -0700 (PDT) Date: Thu, 18 Oct 2012 10:35:57 +0300 Message-ID: Subject: A little question about safe mode From: Alexander Yerenkow To: freebsd-current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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 07:35:58 -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