From owner-freebsd-questions@FreeBSD.ORG Fri Aug 22 01:48:54 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 31A9B30B for ; Fri, 22 Aug 2014 01:48:54 +0000 (UTC) Received: from server1.shellworld.net (shellworld.net [69.60.117.94]) by mx1.freebsd.org (Postfix) with ESMTP id 055223380 for ; Fri, 22 Aug 2014 01:48:53 +0000 (UTC) Received: from server1.shellworld.net (localhost [127.0.0.1]) by server1.shellworld.net (Postfix) with ESMTP id 0D2F1229A7 for ; Thu, 21 Aug 2014 21:48:53 -0400 (EDT) cc: freebsd-questions@freebsd.org Subject: Re: Mounting One of the memstick Image Files MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <62662.1408672133.1@server1.shellworld.net> Date: Thu, 21 Aug 2014 20:48:53 -0500 From: "Martin G. McCormick" Message-Id: <20140822014853.0D2F1229A7@server1.shellworld.net> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Aug 2014 01:48:54 -0000 Elliot Robinson writes: > I know your pain. On Linux, `mount -t ufs -o ufstype=44bsd` is what you're > looking for. This requires that your system knows how to write UFS, which > might be a problem. > > A possibly easier way to do this would be to boot off the memstick, > remount > root as rw, and make the change from the live memstick. I've seen some > problems reading any new/modified files created by doing this from > Linux (complains about bad inodes), but it seems to work from the BSD > perspective... Thank you to both posters on this topic. If I could mount the image file on the FreeBSD system, I would do all the editing there and then copy the modified image back to the Debian system to dd in to the thumb drive. I actually got the image that way to start with. When one uses the Linux fdisk program on the drive afterward, it reports that there is both a BSD and DOS magic number and advises the caller to run fdisk with the -b bsd flag. I suspect there is a boot manager of some type that will catch Windows systems in case somebody wants to boot off the memstick on a Windows system. In this case, all I want to do is mount the image in a native FreeBSD environment to actually do the work on adding the comconsole line. All Linux has to do in this exercise is to feed the new modified image back in to the memstick with dd.