From owner-freebsd-current Sun Oct 20 19:50:22 2002 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 E78C537B401; Sun, 20 Oct 2002 19:50:20 -0700 (PDT) Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70DCA43E6E; Sun, 20 Oct 2002 19:50:20 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0317.cvx22-bradley.dialup.earthlink.net ([209.179.199.62] helo=mindspring.com) by snipe.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 183Se3-0002sd-00; Sun, 20 Oct 2002 19:50:19 -0700 Message-ID: <3DB36B24.9416EFCA@mindspring.com> Date: Sun, 20 Oct 2002 19:49:08 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: bmah@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: Release-building saga continues References: <200210210114.g9L1EXQR010465@intruder.bmah.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Bruce A. Mah" wrote: > I successfully built an i386 miniinst.iso image, using a repository > updated around mid-day Saturday (California time). When I burned and > booted this image, I landed in sysinstall (yay!) with a dialog box > complaining "Couldn't create directory /tmp: Read-only file system" > (d'oh!). Check the boot log itself; you may want to get rid of the sysinstall, so that it doesn't clear the screen, or have it emit 25+ LF before it starts its thing, to ensure that all the console messages are thus available via scroll-lock. One possible source of a problem could be the GEOM changes to change the xx0c to xx0 instead, removign legacy support for xx0c; in that case, the root remount attempt fromt he device in /etc/fstab is probably referencing the old name instead of the new name (a good reason to *never* change device names, unless the old names offend thing God), so the root remount never happened, leaving the root read-only. > There's a number of other operations that result in the same dialog, > including all of the documentation items. It's not possible to mount a > fixit CDROM to investigate further because sysinstall isn't able to > create the mount points. > > It kind of looks like the mfsroot filesystem image got mounted > read-only. Is this just me? No, it was an expected result of the change in device names from use of GEOM. I pointed this out on the -current list almost a month ago, and made specific reference to "live FS" and "PicoBSD" and "Bootable CDROM" (the other places I expect you will now see this problem). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message