Yes...
If you are in LM81, that means devfs is in place. Devfs is probably one of
the better advancements in the Linux world within the last few years. It
carries with it quite a few advantages; one of which is to actually be able
to see what devices have been detected on your system. Of course you can
also do this with the /proc directory; however, if you go into the devfs
directory you can see the true names of the devices in addition to there
being only what has been detected.
In the old dev system, when the devices were created on your system, they
were all put there at once, wether they existed or not. Devfs puts a brain
to the problem, and the daemon only places items in their real designated
spots if they actually exist, using a directory structure as a means of
categorization, as it was meant to be used. Devfs gives you many other
features and abilities, I'm nutshelling one aspect of it here for brevity.
Caveat: In order to maintain backward compatibility, softlinks are created
in the /dev directory that all correspond to the old device names that used
to be there. These names link you up with the *real* device names, the ones
that have been properly categorized within their respective directory
structures. This is what you are trying to mount when you designate /dev/hdd
or whatever.
To check what devfs has actually detected on your system, in your scenario
you would go to
/dev/ide/host0/bus0/target0/lun0
and do something like
ls -ail
To see what you have. What you see (if anything) is all that you have
available to use for mounting. In my case, I see the following:
__________________________________________________________
[root@tamriel lun0]# ls -ail
total 0
374 drwxr-xr-x 1 root root 0 Dec 31 1969 ./
373 drwxr-xr-x 1 root root 0 Dec 31 1969 ../
387 brw------- 1 root root 3, 0 Dec 31 1969 disc
388 brw------- 1 root root 3, 1 Dec 31 1969 part1
[root@tamriel lun0]# pwd
/dev/ide/host0/bus0/target0/lun0
[root@tamriel lun0]#
___________________________________________________________
At this point you may use the "real" filenames to mount your device. For
instance, "disc" is telling me that that is the device I would use for the
fdisk command to create or delete partitions; ie, it represents the whole
enchalada of that device. On the other hand, "part1" is telling me that
there is a partition already there. So therefore I could issue the following
command:
mount -t vfat /dev/ide/host0/bus0/target0/lun0/part1 /mnt/disk
which would mount that dos 7.10 drive to /mnt/disk. I just happen to already
know that it's formatted as a Win95 LBA partition, so I told mount that it
was a vfat filesystem. Telling mount what kind of filesystem you are
mounting tends to make it happy.
So do a dir of that spot and see what you've got. ;)
L8R,
LX
On Monday 04 February 2002 08:35, you wrote:
> I've got an ATAPI ZIP drive, and tried the following, based on Roman's
> suggestion:
>
> Mkdir /mnt/zip
> Mount /mnt/zip /dev/hdd4 (harddrake reports the ZIP drive as HDD -- it's
> the 2nd device on the 2nd IDE channel)
> ...and I got this error:
> "mount: /dev/hdd4 is not a block device"
> ...so I tried:
> Mount /mnt/zip /dev/hdd
> ...and I got this error:
> "mount: /dev/hdd is not a block device"
>
> Any ideas?
>
> ---
> ===============================================================
> Andrew Vogel: Manager of Professional Programs at the University of
> Cincinnati College of Pharmacy
> http://pharmacy.uc.edu (513)-558-3784
> ===============================================================
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
