The following reply was made to PR port-i386/36808; it has been noted by GNATS.

From: "Christoph Egger" <Christoph_Egger@gmx.de>
To: gnats-bugs@NetBSD.org, netbsd-bugs@netbsd.org,
	gnats-admin@netbsd.org, port-i386-maintainer@netbsd.org
Cc: 
Subject: Re: port-i386/36808: NetBSD not installable from a second disk
Date: Mon, 20 Aug 2007 23:57:50 +0200

 > The following reply was made to PR port-i386/36808; it has been noted by
 > GNATS.
 > 
 > From: David Laight <david@l8s.co.uk>
 > To: gnats-bugs@netbsd.org
 > Cc: 
 > Subject: Re: port-i386/36808: NetBSD not installable from a second disk
 > Date: Mon, 20 Aug 2007 21:40:23 +0100
 > 
 >  On Mon, Aug 20, 2007 at 10:30:30PM +0200, Christoph Egger wrote:
 >  > 
 >  > No, I aborted the install process and exited sysinst to get a shell.
 >  > 
 >  > Then I typed 'mount -t ext2fs /dev/wd1e /mnt2 && ls
 > /mnt2/i386/binary/sets/'
 >  > 
 >  > I typed 'sysinst' and restartet install process and
 >  > choosed 'local directory'.
 >  
 >  /mnt2 is a bad idea, sysinst probably unmounts it.....
 
 oh! That would explain why it says, a file does not exist.
 That is a behaviour, I don't expect when I choose 'local directory'.
 I thought, this is what sysinst would do with 'unmounted fs'.
      
 >  > >  There is no reason why the above shouldn't work.  I can't see how
 > the
 >  > >  files being on a different disk can make any difference once the
 >  > >  filesystem is mounted.
 >  > 
 >  > Me neither. That's why I think, the bug is somewhere in sysinst.
 >  
 >  But I've installed from sets on a local disk in the past...
 >  (getting the path to the install kernel correct is a PITA when it is
 >  in the bowels of the 'release' directory...)
 
 hm... I'm not sure, what you mean. Please elaborate.
 
 
 -- 
 Greetings,
 
 Christoph