From owner-freebsd-hackers Mon Jan 29 10: 8:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 2A2C237B400 for ; Mon, 29 Jan 2001 10:08:25 -0800 (PST) Received: from cs.rpi.edu (bill.cs.rpi.edu [128.213.2.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA51987; Mon, 29 Jan 2001 13:08:23 -0500 (EST) Message-Id: <200101291808.NAA51987@cs.rpi.edu> To: freebsd-hackers@freebsd.org Cc: crossd@cs.rpi.edu Subject: Using multiple Malloc-Disks Date: Mon, 29 Jan 2001 13:08:22 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need to use multiple malloc disks for a custom net-boot image I am working on. The problem is that whenever I access /dev/md1 from the disk it gives me a 'device not configured' error. I originally thought that this was an error in how a preloaded image interfaced with the system, but I also get this on a disk-booted machine. Consider the following test: > dd bs=512 if=/dev/md0c of=/dev/null > 20000 Blocks in > 20000 Blocks out > > dd bs=512 if=/dev/md1c of=/dev/null > Device not configured. Yet, according to the manpage: > The md driver uses the ``almost-clone'' convention, whereby opening de- > vice number N creates device instance number N+1. What is wrong here? A quick look through the source finds there is no code in the open() routine to create a new instance; though I am not entirely sure that is where it would be located. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message