From owner-freebsd-current Tue Aug 18 16:59:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02652 for freebsd-current-outgoing; Tue, 18 Aug 1998 16:59:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02636 for ; Tue, 18 Aug 1998 16:59:04 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id QAA14056; Tue, 18 Aug 1998 16:56:04 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: brdean@unx.sas.com cc: freebsd-current@FreeBSD.ORG Subject: Re: Sysinstall broken: can't load config file from floppy In-reply-to: Your message of "Tue, 18 Aug 1998 14:23:26 EDT." <199808181823.OAA05715@dean.pc.sas.com> Date: Tue, 18 Aug 1998 16:55:58 -0700 Message-ID: <14048.903484558@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While installing FreeBSD from today's snap (8/18), I got the following > error when loading a configuration file from a floppy: > > "Error mounting floppy fd0 (/dev/fd0) on /dist : Invalid argument" > > The debug screen only said: > > "DEBUG: Init floppy called for xxx.cfg distribution" I took MSDOSFS out of the GENERIC kernel a few days ago in order to make the snaps work again - we were out of space. This isn't critical from the DOS installation code since it doesn't use msdosfs, it uses stand-alone DOSFS parsing code in sysinstall. Unfortunately, the corner case here is the floppy mount code which tries UFS then MSDOSFS as a mount type - it doesn't go through the stand-alone stuff. Hmmmm. Is this really critical, or can you put your config file on a UFS formatted floppy? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message