Encountered:
warhammer etc # mount /dev/cdrom
mount: block device /dev/cdrom is write-protected, mounting read-only
mount: No buffer space available
i googled and found a no buffer space available.
followed suggestions on the thread:
warhammer etc # mount -va df mount -v /mnt/cdrom
mount:
On Tuesday 01 January 2008 10:50:26 pm Cocoy Dayao wrote:
Encountered:
warhammer etc # mount /dev/cdrom
mount: block device /dev/cdrom is write-protected, mounting read-only
mount: No buffer space available
i googled and found a no buffer space available.
followed suggestions on the
On Jan 2, 2008, at 12:22 PM, Jerry McBride wrote:
On Tuesday 01 January 2008 10:50:26 pm Cocoy Dayao wrote:
What is the cdrom? Music or Data? You can't mount a music cdrom...
period.
data
However, if it's a data cd, then iso9660 MUST either be build into
the kernel
or available as a
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.
On Jan 2, 2008, at 1:32 PM, Adam Carter wrote:
If it says
CONFIG_ISO9660_FS=y - its built into the kernel, and should be
working
yep. it is built into the kernel. so auto should work, correct?
--
Cocoy
People who are really serious about software should make their own
On Wed, 2 Jan 2008, Cocoy Dayao wrote:
On Jan 2, 2008, at 1:32 PM, Adam Carter wrote:
If it says
CONFIG_ISO9660_FS=y - its built into the kernel, and should be
working
yep. it is built into the kernel. so auto should work, correct?
You could try moving iso9660 to the top in
On Jan 2, 2008, at 2:42 PM, Paul Colquhoun wrote:
On Wed, 2 Jan 2008, Cocoy Dayao wrote:
You could try moving iso9660 to the top in /etc/filesystems, so it
gets
tried first.
yep. done. thanks!
--
Cocoy
People who are really serious about software should make their
Am Freitag, 23. November 2007 schrieb ext Dan Farrell:
On Fri, 23 Nov 2007 09:11:06 +
Neil Bothwick [EMAIL PROTECTED] wrote:
On Fri, 23 Nov 2007 08:15:48 + (UTC), Thufir wrote:
In this case, the discs are fine, as are the drives. The drives
mount fine in Fedora and read these
On Fri, 23 Nov 2007 07:36:44 +0100
Dirk Heinrichs [EMAIL PROTECTED] wrote:
Am Donnerstag, 22. November 2007 schrieb ext Stroller:
A Google seems to suggest that mount: No buffer space available
is commonly returned when the device is already mounted.
I also found (with Google) one forum
On 22 Nov 2007, at 09:18, Thufir wrote:
...
arrakis ~ #
arrakis ~ # mount -a
arrakis ~ #
arrakis ~ # mount /mnt/cdrom
mount: block device /dev/cdrom is write-protected, mounting read-only
mount: No buffer space available
arrakis ~ #
arrakis ~ # mount /mnt/cdrom1
mount: block device /dev/cdrom1
On Thu, 22 Nov 2007 15:20:43 +
Stroller [EMAIL PROTECTED] wrote:
A Google seems to suggest that mount: No buffer space available is
commonly returned when the device is already mounted.
Possibly, but I think this is unlikely. I have seen the 'already
mounted' error many times but never
Am Donnerstag, 22. November 2007 schrieb ext Stroller:
A Google seems to suggest that mount: No buffer space available is
commonly returned when the device is already mounted.
I also found (with Google) one forum posting where it was stated that the
cause was a bad, self-burned disk in the
12 matches
Mail list logo
