Re: SA_{SPACE,REWIND,ERASE}_TIMEOUT

1999-05-21 Thread 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

Re: SA_{SPACE,REWIND,ERASE}_TIMEOUT

1999-05-21 Thread 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 par

Re: SA_{SPACE,REWIND,ERASE}_TIMEOUT

1999-05-21 Thread 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' t

SA_{SPACE,REWIND,ERASE}_TIMEOUT

1999-05-21 Thread Dag-Erling Smorgrav
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.pin