Re: what about cdrecord ?

["C.M. Connelly" <c@eskimo.com>]

>>>>> "CL" == Chris Lawrence <cnlawren@olemiss.edu> writes:

    CL> don't remember where the parameter is, but you should change
    CL> it to what it is on Intel (16 MB I think) and recompile the
    CL> kernel.


The parameter is SHMMAX, #defined in /usr/src/linux/include/asm*/shmparam.h.  
This parameter is set to 4 MB by default in older (pre-2.2.10)
kernels, but has been changed in more recent versions of the Vger
source code (presumably these patches have propagated to the main
source tree, but I wouldn't take it on faith).

If it hasn't been changed (or you have an older kernel), then you
should redefine SHMMAX to

  #define SHMMAX 0x1000000                /* max shared seg size (bytes) */

All this information, and much, much more can be found in the cdrecord
documentation (in /usr/doc/cdrecord on my system; the SHMMAX parameter
problem is discussed in the README.linux file.


Hope that helps,

   C.

+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
 Behind the counter a boy with a shaven head stared vacantly into space, 
 a dozen spikes of microsoft protruding from the socket behind his ear.
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
   C.M. Connelly               c@eskimo.com                   SHC, DS
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+