Re: SA_{SPACE,REWIND,ERASE}_TIMEOUT

[Matthew Jacob]

These may go away soon as currently constituted because they are properly
a per-device type value.



On 21 May 1999, Dag-Erling Smorgrav wrote:

 I want to convert these kernel options to sysctl variables. Where
 should they be inserted into the tree? I was thinking of creating a
 new 'cam' top-level category and put them there:
 
   cam.sa.space_timeout
   cam.sa.rewind_timeout
   cam.sa.erase_timeout
 
 DES
 -- 
 Dag-Erling Smorgrav - d...@flood.ping.uio.no
 
 
 To Unsubscribe: send mail to majord...@freebsd.org
 with unsubscribe freebsd-hackers in the body of the message
 




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message

Re: SA_{SPACE,REWIND,ERASE}_TIMEOUT

[Mike Smith]

 I want to convert these kernel options to sysctl variables. Where
 should they be inserted into the tree? I was thinking of creating a
 new 'cam' top-level category and put them there:
 
   cam.sa.space_timeout
   cam.sa.rewind_timeout
   cam.sa.erase_timeout

These should be per-device parameters; you will want to create a 
virtual namespace for them, or make them settable via ioctl on each sa 
device.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  msm...@freebsd.org
\\-- Joseph Merrick   \\  msm...@cdrom.com




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message

Re: SA_{SPACE,REWIND,ERASE}_TIMEOUT

[Matthew Jacob]

  I want to convert these kernel options to sysctl variables. Where
  should they be inserted into the tree? I was thinking of creating a
  new 'cam' top-level category and put them there:
  
cam.sa.space_timeout
cam.sa.rewind_timeout
cam.sa.erase_timeout
 
 These should be per-device parameters; you will want to create a 
 virtual namespace for them, or make them settable via ioctl on each sa 
 device.

It should be an argument to the 'mt' command.




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message