X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: Mapping of \device\harddisk12 and beyond Date: Wed, 1 Nov 2006 14:46:37 -0000 Message-ID: <015901c6fdc4$88cd6fa0$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 01 November 2006 14:37, Loh, Joe wrote: > Thanks for the feedback Dave. > > Is there a solution to getting more devices mapped without modifying the > Cygwin source? We test with Cygwin using distributed components only. > We do develop our own test components under Cygwin, so a programmatic > recommendation is acceptable. > > Mapping something like /dev/sda to /dev/sdz, then /dev/sdaa to > /dev/sdaz, then /dev/sdba all the way to /dev/sdzz maybe? No, I'm afraid that won't work, because only /dev/sda ... /dev/sdz exist by default. "mknod" doesn't work on cygwin the same way it works on *nix: yes, it creates a special file representing a device, but there is no kernel to translate special device major/minor numbers into actual hardware devices. The sources that I pointed you at are the only connection between files and devices on cygwin, and you do need to modify them. However, it is simple and reliable, so you should not worry about using the technique; you're only doing what the cygwin dll already does, just for more device names. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/