Amit

wd0 is IDE primary master
wd1 is IDE primary slave
...
sd0 is SCSI drive 1...

the 4th alpha is the partition "number"
eg. wd0a wd0b wd0c ... up to "h"

try
disklabel wd0
and
fdisk wd0
to see which partitions are on the disk

(use "man fdisk" or "man disklabel" to find out what each does)

try making a dir under /mnt
eg. mkdir /mnt/mybigfat32
then mount the partition and check it out
mount -t vfat /dev/wd0? /mnt/mybigfat32
(i think that's about right ... replace "?" of course :)

if disklabel and fdisk are too much for you,
just try the "stab in the dark" approach
ie. start at h and work down
(i dont think it will let you do too much damage :)

mount -t vfat /dev/wd0? /mnt/mybigfat32   (error msgs?)
ls /mnt/mybigfat32    (file listing?)
umount /mnt/mybigfat32
(make sure it's unmounted before you try anything else)

im not 100% sure about the details
(i dont have immediate access to my netbsd box ... it's "busy":))
... but I think you get the idea

Marcus

----- Original Message -----
From: "Amit Kulkarni" <amitkulz@hotmail.com>
To: "BrownM03" <brownm03@bigpond.com>; <port-i386@netbsd.org>
Sent: Sunday, September 02, 2001 7:28 AM
Subject: Re: Win2000 & NetBSD Install Help!


> Hi:
> Pardon my lack of knowledge...
> But I don't know which device the file system resides...
> I now have a C: ( NTFS), E: ( for keeping the binary sets) and F:(for
> NetBSD)
> I boot and tried to mount wd0a, wd0b etc.... but I don't know exactly
where
> the E: is there.
> I cd to /dev and there's 100's of devices, I try to a ls- alt and try to
> mount anything on Sept 1 2001
> but no luck. Initially the sysinstall does say that your drive is wd0.
>
> Any ideas on finding out how to go about mounting the partition on which
the
> binary sets reside ?
>
> Thanks
>
> Here's what install.html says ==>
> Installation from an unmounted file system
> In order to install from a local file system, you will need to specify the
> device that the file system resides on (for example sd1e) the type of the
> file system, and the directory on the specified file system where the sets
> are located. sysinst will then check if it can indeed access the sets at
> that location.
>
> >
> > > > I used Partition Magic to create a FAT32 partition, then FTP'd the
> whole
> > =
> > > > NetBSD 1.5.1 onto a=20
> > > > c:/i386/binary/sets which is a NTFS (I don't know if it's NTFS4 or =
> > > > NTFS5) I have a Win2000 SP2
> >
> > win2k = ntfs 5.0    (partition magic 5.01 req to resize)
> > winXP = ntfs 5.1
> >
> > > Here's what I'd do
> > >
> > >   Part 1:  NTFS for W2K
> > >   Part 2:  Blank space where NetBSD will go
> > >   Part 3:  FAT-32 to store the binary sets
> > >   Part 4:  whatever...
> >
> > exact strategy should/will depend on disk size
> > is there still a 1024 cylinder limit on the location of the /boot
> partition
> > ?
> >
> > Dont forget that you can put multiple logical drives in an extended
> > partition
> >
> > > You don't need to create and then destroy/convert a FAT-32 partition
> just
> > > to get a NetBSD partition.
> >
> > Just leave an empty space after resizing your other partition(s)
> >
> > > Also, you can arrange the partitions in any order your heart desires.
> >
> > i would be careful about that statement when windows is involved ;)
> >
> > > FAT-32 can be read by both OS's, that's why the sets should go there.
> >
> > (fast & simple FS, readable by MANY OS's)
> >
> > > This is how I did my install.  Worked like a charm.
> >
> > A network install from a 2nd machine is OFTEN the best/easiest choice.
> >
> > Good luck :)
> >
> > PS. Backup !!! :))
> > (you lose your mp3's and another potential netbsd fan drops off the face
> of
> > the earth :))
> >
> > PPS. Windows is the first virus your machine gets :)