From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 8 00:50:28 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D945816A4CE for ; Thu, 8 Jan 2004 00:50:28 -0800 (PST) Received: from lupinella.troll.no (lupinella.troll.no [80.232.37.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7D0343D1D for ; Thu, 8 Jan 2004 00:50:24 -0800 (PST) (envelope-from ebakke@trolltech.com) Received: from steinbit.troll.no ([80.232.37.113]:61632 "EHLO steinbit.troll.no" ident: "NO-IDENT-SERVICE[2]") by trolltech.com with ESMTP id ; Thu, 8 Jan 2004 09:50:11 +0100 From: "Erik H. Bakke" To: Joe Fenton Date: Thu, 8 Jan 2004 09:51:02 +0100 User-Agent: KMail/1.5.4 References: <20040107200042.67A0B16A4D2@hub.freebsd.org> <3FFCD437.6090704@citlink.net> In-Reply-To: <3FFCD437.6090704@citlink.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401080951.02162.ebakke@trolltech.com> cc: freebsd-amd64@freebsd.org Subject: Re: freebsd-amd64 Digest, Vol 31, Issue 3 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 08:50:29 -0000 On Thursday 08 January 2004 04:53, Joe Fenton wrote: > I'm trying to get a "mptable -dmesg" to send to the guy keeping the mobo > database > for AMD64 systems, but I can't get the damn floppy to mount. /dev/fd0 is > there, > but when I try to mount it, it says that /mnt/floppy doesn't exist. > Maybe someone > can give me a little hint on this. > A very stupid suggestion, but I haven't followed this thread closely so I may have missed the obvious here. /mnt/floppy does exist in your filesystem, I assume? An alternative could be to mount a disk image file, as far as the filesystem driver is concerned that should work (The notorious 'should work') the same way as a device node, I think. Then, when you're done with the disk image, unmount it and copy the file raw to /dev/fd0. I do not have my AMD64 system yet, but it's on my budget for April so I can't reproduce the problem locally yet, I'm afraid. Best regards. -- Erik H. Bakke