06-23-2013
The question can easily be answered with a 5-second google search for "AIX rhdisk hdisk". I suggest you read the first hit coming up on this search:
IBMs documentation.
Even without searching for anything your directory listing shows one to be a character-device and the other to be a block device.
For the future i suggest using google first and us second.
I hope this helps.
bakunin
9 More Discussions You Might Find Interesting
1. Solaris
Hi, Anyone can help
My solaris 8 system has the following
/dev/null , /dev/tty and /dev/console
All permission are lrwxrwxrwx
Can this be change to a non-world write ??
any impact ?? (12 Replies)
Discussion started by: civic2005
12 Replies
2. UNIX for Dummies Questions & Answers
Hello,
i am using finch (unix commandline instant messaging client using libgnt) which is running connected to /dev/pts/1
Now I would like to "remote control" the program by sending the key combinations normally typed on the keyboard from a programm in another shell. So I tried:... (0 Replies)
Discussion started by: mentos
0 Replies
3. UNIX for Dummies Questions & Answers
Please explain me the difference between /dev and devices..
Googled info is -
/dev - where logical device names stores here
devices - physical device info stores here...
Could any one explain me.. the real difference and major one (3 Replies)
Discussion started by: VijaySolaris
3 Replies
4. Solaris
So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following:
devfsadm -Cv
powermt -q
luxadm -e offline <drive path>
luxadm probe
All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies
5. AIX
Hello AIXians,
I can't boot my AIX, it hangs and stops at the code error: 0518
After searching google, I knew the problem is due to problems in File Systems.
So the solution is booting from any bootable media, then run these commands in maintenance mode:
#fsck -y /dev/hd4
#fsck -y... (3 Replies)
Discussion started by: Mohannad
3 Replies
6. Shell Programming and Scripting
Objective: To recreate the partitioning setup of /dev/sda on /dev/sdc
How would I parse the below information and initialize variables
(an array?) that can be used to build sgdisk commands in a script, regardless of the number of partitions?
Something along the lines of:
sgdisk -n... (12 Replies)
Discussion started by: RogerBaran
12 Replies
7. AIX
Some storage/disks have been added to an existing AIX 6.1 server. The admin sent me the list of hdisk#'s for the new disks, but I need the corresponding rhdisk# for the same hdisk. (I know from past experience that the rhdisk that maps to an hdisk is not always the same number. For instance,... (5 Replies)
Discussion started by: sbrower
5 Replies
8. Red Hat
Hi,
Please suggest steps to change grub from /dev/sda to /dev/sdb, (1 Reply)
Discussion started by: manoj.solaris
1 Replies
9. HP-UX
Hi,
In our HP-UX B.11.11. I could not find dev/urandom and dev/random
Are all pseudo-devices implemented as device drivers, or in need to run /configure some package to install the package to have dev/urandom.
Please help (4 Replies)
Discussion started by: rashi
4 Replies
LEARN ABOUT SUSE
sane-ibm
sane-ibm(5) SANE Scanner Access Now Easy sane-ibm(5)
NAME
sane-ibm - SANE backend for IBM and Ricoh SCSI flatbed scanners
DESCRIPTION
The sane-ibm library implements a SANE (Scanner Access Now Easy) backend that provides access to the IBM 2456 and the Ricoh IS-410, IS-420,
and IS-430 flatbed scanners. Support for the IS-410 and IS-430 is untested. Please contact the maintainer or the sane-devel mailing list if
you own such a scanner.
This backend is alpha-quality. It may have bugs and some scanners haven't been tested at all. Be careful and pull the plug if the scanner
causes unusual noise.
DEVICE NAMES
This backend expects device names of the form:
special
Where special is either the path-name for the special device that corresponds to a SCSI scanner. The program sane-find-scanner helps to
find out the correct device. Under Linux, such a device name could be /dev/sg0 or /dev/sga, for example. See sane-scsi(5) for details.
CONFIGURATION
The contents of the ibm.conf file is a list of device names that correspond to SCSI scanners. Empty lines and lines starting with a hash
mark (#) are ignored. See sane-scsi(5) on details of what constitutes a valid device name.
FILES
/etc/sane.d/ibm.conf
The backend configuration file (see also description of SANE_CONFIG_DIR below).
/usr/lib64/sane/libsane-ibm.a
The static library implementing this backend.
/usr/lib64/sane/libsane-ibm.so
The shared library implementing this backend (present on systems that support dynamic loading).
ENVIRONMENT
SANE_CONFIG_DIR
This environment variable specifies the list of directories that may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configura-
tion file is searched in two default directories: first, the current working directory (".") and then in /etc/sane.d. If the value
of the environment variable ends with the directory separator character, then the default directories are searched after the explic-
itly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories "tmp/config", ".",
and "/etc/sane.d" being searched (in this order).
SANE_DEBUG_IBM
If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. Higher
debug levels increase the verbosity of the output.
SEE ALSO
sane(7), sane-find-scanner(1), sane-scsi(5),
AUTHOR
mf <massifr@tiscalinet.it>
Maintained by Henning Meier-Geinitz <henning@meier-geinitz.de>
13 Jul 2008 sane-ibm(5)