On Tuesday 08 February 2005 11:24, Jon LaBadie wrote: >On Tue, Feb 08, 2005 at 10:04:40AM +0100, Paul Bijnens wrote: >> Jon LaBadie wrote: >> >With the ultrium it is less important about considering HW or SW >> >compression. But be aware that on Solaris whether HW compression >> >is turned on or not is determined by the device you choose. You >> >will find lots of /dev/rmt/0"xyz" devices. The "xyz" determines >> >the properties of the device the driver will set upon opening it. >> > >> >Don't be fooled into assumptions about the various devices. The >> >"c" device is listed as "compressed". But that is the >> > conventional use. There is no certainty that it turns >> > compression on for every device, or that devices without the "c" >> > are no compression. You will even have a "c" device for drives >> > that are not capable of HW compression ;-) Only way to tell is >> > check the docs for the drive and settings for the driver. And >> > then I'd check it if I could. >> >> Indeed. >> >> And check the file st.init, where the letters get their meaning. > >Paul, I'm unfamiliar with the file st.init. >Nor do I find one on my system. >Did you mean the st.conf file in /kernel/drv? > >If the st.conf file, I don't find an entries for any lto's I >recognize. One poster said it was "builtin" to the driver, >another said they had to edit the file and add an entry. > >The drive docs would probably still be needed to interpret >the entry.
Paul: That file (st.init/st.conf) doesn't exist on a redhat flavored linux install. Nor on a debian sarge based install of BDI-4.08, I just checked that one too. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.33% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
