From: "Adam Carter" <Adam.Carter@optus.com.au>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] mount cdrom: No buffer space available
Date: Wed, 2 Jan 2008 16:32:07 +1100 [thread overview]
Message-ID: <39080C5B7143BC4780067586F60979C40BEC5A@msgprdmbxw002.optus.com.au> (raw)
In-Reply-To: <E82C1B5C-8839-47D6-980D-BE428F70AA14@gmail.com>
> data
>
> > However, if it's a data cd, then iso9660 MUST either be build into
> > the kernel
> > or available as a module for the "auto" part of your cdrom fstab
> > line to work
> > correctly... hmmm... maybe need also "autoload" in the module
> > loading section
> > of the kernel configurator.
> >
>
>
> ok. thanks! i'll check that out.
Try;
$ grep ISO9660 /usr/src/linux/.config
If it says
CONFIG_ISO9660_FS=y -> its built into the kernel, and should be working
CONFIG_ISO9660_FS=m -> its built as a module, so try 'modprobe iso9660'
and attempt the mount again (but it should load the module automatically
# CONFIG_ISO9660_FS is not set -> you need to build it. You might as
well just build it as a module, so you don't have to change your kernel
and reboot etc. Just update your .config file, then run "make modules &&
make modules_install && modprobe iso9660" and try to mount it again.
-Ad
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2008-01-02 5:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 9:38 [gentoo-user] how would I use device names in fstab? Thufir
2007-12-27 11:26 ` Dirk Heinrichs
2008-01-02 10:27 ` [gentoo-user] " Thufir
2007-12-27 13:31 ` [gentoo-user] " Stroller
2007-12-28 19:45 ` [gentoo-user] " Thufir
2007-12-29 8:16 ` Dirk Heinrichs
2007-12-31 7:49 ` Thufir
2007-12-31 8:41 ` Dirk Heinrichs
2008-01-02 10:59 ` Thufir
2008-01-02 11:14 ` Thufir
2008-01-03 6:31 ` Dirk Heinrichs
2008-01-02 3:50 ` [gentoo-user] mount cdrom: No buffer space available Cocoy Dayao
2008-01-02 4:22 ` Jerry McBride
2008-01-02 4:32 ` Cocoy Dayao
2008-01-02 5:32 ` Adam Carter [this message]
2008-01-02 5:48 ` Cocoy Dayao
2008-01-02 6:42 ` Paul Colquhoun
2008-01-02 6:55 ` Cocoy Dayao
-- strict thread matches above, loose matches on Subject: below --
2007-11-22 9:18 Thufir
2007-11-22 15:20 ` Stroller
2007-11-22 19:00 ` Dan Farrell
2007-11-23 6:36 ` Dirk Heinrichs
2007-11-23 8:01 ` Dan Farrell
2007-11-23 9:11 ` [gentoo-user] " Neil Bothwick
2007-11-23 18:21 ` Dan Farrell
2007-11-26 6:53 ` [gentoo-user] " Dirk Heinrichs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39080C5B7143BC4780067586F60979C40BEC5A@msgprdmbxw002.optus.com.au \
--to=adam.carter@optus.com.au \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox