|
Frequently Asked Questions
Linux (page3)
Q11: How common is the code base between the Windows and Unix platforms?
A11: The majority of the code is written and tested first under Windows. We
emulate the Windows GUI code so that the code base can be recompiled
directly, and executables can be quickly updated with bug fixes found on
any platform. Minor emulation discrepancies may occasionally cause
problems, particularly with the non-thread safe nature of X-Windows. Please
document any GUI associated problems so that we can investigate.
Q12: Can scripts be shared between Xmfg versions for Windows, Solaris, and
Linux?
A12: Yes, the script engine is virtually identical between all of the
platforms. Minor discrepancies in implementation may exist. One of the few
instances where you will have to be careful would be absolute path names.
On Windows it would be typical to save a file to C:\\temp for example... the
same script run on Linux would need to reference it as /tmp. Referring to
relative pathways (./subdir/filename.txt) should always be safe.
Q13: What devices are used in the bus probe?
A13: The Extreme SCSI tools work with hard drives, tape drives, and cd roms
under Linux. We access /dev/sg* as our devices.
All platforms can now also
include "file devices" in the device list by adding a line similar to the
following in the ./config/devices.ini file:
File 00:98:00 /XDEVxlnx/posix.txt
which means to map the binary file
specified by the path to device 00:98:00 for program operation. You will not
be able to issue SCSI commands to a file device but they can be opened for
Xperf and Xmfg File IO (which uses posix
aio_read/write.)
Q14: We have SCSI devices attached to our host adapter, but they don't show up
when we start the software?
A14: First off, no devices can be accessed if the low level device is
currently opened by another program. As an example, Cd-roms under Solaris
are typically under control of vold. To see your cdrom drive, you need to
kill vold.
Your driver might not be functional, or the special device files (/dev/sg*)
might not exist for the devices that you're attempting to connect.
Lastly, you may notice that the bus probe in the shell window shows the
devices as being 'discarded (incorrect SCSI ver).' This means that the IDE
device (scsiver 0) is not being added because it can't be effectively used
by the program. IDE devices should use the IDE specific version of the
software. In the future we plan to add more thorough IDE implimentation.
If the bus probe shows simply 'discarded' that means that the
config/devices.ini file has marked those drives as not to be operated on.
When first run, we attempt to determine which drives are in use system
devices by examining /etc/mnttab. If one of the devices is listed there we
discard it automatically. If you are SURE that you want to see this device
and/or issue SCSI commands to it, open up the Device Management window and
remove those Discard entries from the list and do 'Save and Use'.
Viewing the appropriate Debug.txt file may offer insights into why the
devices are not shown.
Q15: What is the maximum buffer and transfer size?
A15: The maximum buffer size for Linux is 512K. A 64k buffer is actually
allocated by default though it will be scaled up as appropriate for testing.
If using variables to define transfer sizes in script, there are ways to
override this mechanism and set the buffer to a particular size.
|
