Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+Finding\s+\/dev\s+file\s+of\s+a\s+drive\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+Finding\s+\/dev\s+file\s+of\s+a\s+drive\s*$/: 2 ]

Total 2 documents matching your query.

1. [Veritas-bu] Finding /dev file of a drive (score: 1): Author: Jason.Ahrens AT telus DOT com (Jason Ahrens); Date: Tue, 15 Jan 2002 12:29:11 -0500; Once I get a tape mountd with tpreq, I can find what drive the tape ended up in with vmoprcmd. However, I need to access the device itself for my next operation (ie: /dev/rmt/...) /dev device file?; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2002-01/msg00231.html (10,803 bytes)
2. [Veritas-bu] Finding /dev file of a drive (score: 1): Author: gyurchak AT veritas DOT com (Gregg Yurchak); Date: Tue, 22 Jan 2002 18:25:27 -0500; Sorry to jump in so late here. When you use tpreq to load a tape for use, you shouldn't use the /dev/rmt entries to access it. Instead, you should use the file you specified with the tpreq command (/; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2002-01/msg00371.html (11,901 bytes)

Current List: 1 - 2
Page: [1]