Im trying to mount my cdrom and it''s not working. What the command to mount my cdrom? im using "mount /dev/cdrom /mnt/cdrom -t iso9660" that told me that the medium did not exist i tried "mount /dev/hdd /mnt/cdrom -t iso9660" and that gave the same problem What am i doing wrong? Keep It Real!

It''s saying that there''s no CD in the drive. Is there?

The filesystem type flag appears to be -F, not -t. Sorry about that.

You really should read the manpage. The filesystem type (iso9660) may also be wrong, but the available types should be listed somewhere in that manpage.

[ GDNet Start Here | GDNet Search Tool | GDNet FAQ ]
[ MS RTFM [MSDN] | SGI STL Docs | Boost ]
[ Google! | Asking Smart Questions | Jargon File ]
Thanks to Kylotan for the idea!

quote: Original post by Oluseyi
The filesystem type flag appears to be -F, not -t. Sorry about that.

quote: mount(8)

       -F     (Used in conjunction with  -a.)   Fork  off  a  new              incarnation of mount for each device.  This will do              the mounts on different devices  or  different  NFS              servers  in  parallel.  This has the advantage that              it is faster; also NFS timeouts go in  parallel.  A              disadvantage  is  that the mounts are done in unde�              fined order.  Thus, you cannot use this  option  if              you want to mount both /usr and /usr/spool.

quote: mount(8)

       -t vfstype              The argument following the -t is used  to  indicate              the  file system type.  The file system types which              are currently supported are:  adfs,  affs,  autofs,              coda,  coherent,  cramfs,  devpts,  efs, ext, ext2,              ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs,              nfs,  ntfs,  proc,  qnx4,  reiserfs,  romfs, smbfs,              sysv, tmpfs, udf, ufs, umsdos,  vfat,  xenix,  xfs,              xiafs.   Note  that  coherent,  sysv  and xenix are              equivalent and that  xenix  and  coherent  will  be              removed  at  some  point  in the future -- use sysv              instead. Since kernel version 2.1.21 the types  ext              and xiafs do not exist anymore....

Hey, I was on a Solaris box...

[ GDNet Start Here | GDNet Search Tool | GDNet FAQ ]
[ MS RTFM [MSDN] | SGI STL Docs | Boost ]
[ Google! | Asking Smart Questions | Jargon File ]
Thanks to Kylotan for the idea!

Yeha there is a cd in the drive.

Keep It Real!

What usually works for me when having to mount a cdrom drive is:
mount -t iso9660 /dev/hdc /dev/cdrom

You may have to change /dev/hdc appropriately to whatever your cdrom is sitting at, maybe a dmesg | grep cdrom might give you a helpful answer. It will normally be /dev/hdc or /dev/hdd depending on how many drives you have.

-------------------------------------------------------------
Side Note:
Is there a difference if you define the mount as "mount -t iso9660 /dev/hdc /dev/cdrom" and "mount /dev/hdc /dev/cdrom -t iso9660" ?


Hitchhiker90
"There's one bitch in the world, one bitch with many faces" -- Jay
"What are you people, on dope?" -- Mr. Hand

[edited by - hitchhiker90 on April 29, 2002 2:59:03 AM]

quote: Original post by Oluseyi
The filesystem type flag appears to be -F, not -t. Sorry about that.

You really should read the manpage. The filesystem type (iso9660) may also be wrong, but the available types should be listed somewhere in that manpage.

[ GDNet Start Here | GDNet Search Tool | GDNet FAQ ]
[ MS RTFM [MSDN] | SGI STL Docs | Boost ]
[ Google! | Asking Smart Questions | Jargon File ]
Thanks to Kylotan for the idea!

Sorry to correct you on that but the -t flag is the filesystem type flag specifier for mount. Otherwise, when I mount my NFS partitions it wouldn''t work, since you have to specify the NFS filesystem type at mount time.



"And that''s the bottom line cause I said so!"

Cyberdrek
danielc@iquebec.com
Founder
Laval Linux

/(bb|[^b]{2})/ that is the Question -- ThinkGeek.com
Hash Bang Slash bin Slash Bash -- #!/bin/bash

quote: Original post by Hitchhiker90
What usually works for me when having to mount a cdrom drive is:
mount -t iso9660 /dev/hdc /dev/cdrom

You may have to change /dev/hdc appropriately to whatever your cdrom is sitting at, maybe a dmesg | grep cdrom might give you a helpful answer. It will normally be /dev/hdc or /dev/hdd depending on how many drives you have.

Actually, in most Linux distros, this will give you an error since /dev/cdrom is actually a sybolic link to the device your CDROM is located on. So it should be something like: mount -t iso966o /dev/hdx /mnt/cdrom (or what ever directory you want to mount as the CDROM ). You also need to make sur that the directory does exist before mounting it.

quote:
-------------------------------------------------------------
Side Note:
Is there a difference if you define the mount as "mount -t iso9660 /dev/hdc /dev/cdrom" and "mount /dev/hdc /dev/cdrom -t iso9660" ?

None, the parameters can go anywhere. It's a matter of preference. I like having it before, some prefer to have it at the end. GCC works the same way, you can give the params the way you want, as long as you give it what it wants with the param like the -o param where you need to give it the name of the built project immediately after the flag.



"And that's the bottom line cause I said so!"

Cyberdrek
danielc@iquebec.com
Founder
Laval Linux

/(bb|[^b]{2})/ that is the Question -- ThinkGeek.com
Hash Bang Slash bin Slash Bash -- #!/bin/bash

[edited by - cyberdrek on April 29, 2002 8:20:43 AM]

Ah shoot, that was my error. I mistyped. What I meant to say was that what usually works for me is:
mount -t iso9660 /dev/hdc /mnt/cdrom

Which is what you just said Cyberdrek. Sorry, it was a typo (hey it was at like 3am, what do you expect?) Thanks for clearing up the other question too. I thought the parameters had to be listed in a certain order for it to work.