2005/8/11, Ken Schneider <suse-list@bout-tyme.net>:
On Thu, 2005-08-11 at 19:32 -0400, Greg Freemyer wrote:
On 8/11/05, Sebastian Jeremias <ljeremias@lightech.com.ar> wrote:
I didn't try that because I don't know the density value to pass to stinit. Do you know it?
A quick google comes up with:
# My guess for DDS-4 manufacturer=SONY model = "SDT-10000" { scsi2logical=1 can-bsr can-partitions auto-lock mode1 blocksize=0 compression=1 mode2 blocksize=1024 compression=1 mode3 blocksize=0 compression=0 mode4 blocksize = 1024 compression=0 }
That is the entry that goes into /etc/stinit.def
Mode1 is the default I think. blocksize=0 means it is variable. compression=1 enables compression. (I think more precise densities can be set here also, but make sure you have compression working first.)
If you look at your dmesg output after a boot, you should be able to verify the above manufacturer and model match your drive. the above will only have an impact if you have a stanza like above that matches your drive.
Then you typically just call stinit with no args.
Greg
The OP is asking about the density code for the drive -not- compression setting. I think the density setting has something to do with the amount of data that will fit on a tape (haven't found info yet). On my DDS-3 it is set to 0x25 (unknown) according to the status command.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
By the way, i think it's better to use "mtst" instead of "mt" CI.-