10 More Discussions You Might Find Interesting
1. Red Hat
Hi,
Please suggest steps to change grub from /dev/sda to /dev/sdb, (1 Reply)
Discussion started by: manoj.solaris
1 Replies
2. 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
3. AIX
Hi,
How can i check that i am using RAW devices for storage in my AIX machine...
Also after adding a LUN from storage to a aix host, when i check /dev in the host, i can see both rhdisk and hdisk with same number
eg:
dcback1(root):/dev>ls -lrt | grep disk12
crw------- 1 root ... (4 Replies)
Discussion started by: jibujacob
4 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. 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
6. AIX
Hello,
I attached a tape drive to one of my partitions but i cannot find the device.
I run the command lsdev|grep rmt but i dont get anything in return.
When i run lsslot -c slot i can see the slot number and the device that belongs to the tape drive but i cannot find any rmt files in /dev.... (6 Replies)
Discussion started by: omonoiatis9
6 Replies
7. Linux
Hello all,
I am using openSUSE 11.1 and have an issue with my wireless adapter which I am trying to understand and fix.
I just have a quick question about the following image: (It was the output of the lspci command)
Why are there two modules being loaded? (ath5k and ath9k)
is this a... (2 Replies)
Discussion started by: septima.pars
2 Replies
8. UNIX for Dummies Questions & Answers
I am having trouble understanding the difference between a passthrough device and a named device and when you would use one or the other to access equipment.
As an example, we have a tape library and giving the command
"camcontrol devlist" gives the following output:
akx# camcontrol... (1 Reply)
Discussion started by: thumper
1 Replies
9. 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
10. AIX
Hi,
just wondering what the /dev/rmt0.x devices relate to. I assume some are no rewind/compression etc but can't seem to find a man page which tells you which one is which.
Can anyone help?
Thnx (0 Replies)
Discussion started by: backslash
0 Replies
TDFX(4) BSD Kernel Interfaces Manual TDFX(4)
NAME
tdfx -- Voodoo Graphics and VoodooII Memory Access GLIDE device driver
SYNOPSIS
device tdfx
device tdfx_linux
DESCRIPTION
This driver creates an entry in /dev that allows programs (mostly GLIDE-based software) to access the device memory of the Voodoo Graphics
and VoodooII 3D accelerators created by 3Dfx, Inc. This provides an interface for applications based on the GLIDE API or that simply use the
API provided by the linux /dev/3dfx device to use the video device.
Supports all cards based on the following chipsets:
3Dfx Voodoo Graphics
3Dfx Voodoo II
Specifically, the following cards should work:
Diamond Multimedia Monster 3D
Diamond Multimedia Monster 3D II
Note that this driver does not currently have support for the Voodoo Banshee, Voodoo3, Voodoo5, or Voodoo6 based cards. It also does not
currently support the Voodoo Rush. It also does not yet handle the SLI feature of the Voodoo II boards. You can only use each of them sepa-
rately.
By including tdfx_linux, you can enable the linux ioctl code for this driver, where the only supported applications currently reside.
FILES
/dev/3dfx Symlinked to default 3dfx board
/dev/3dfx* Character Device programming interface
/dev/voodoo Mirrors of above interfaces
/dev/voodoo* (Some apps use /dev/voodoo)
HISTORY
The tdfx driver appeared in FreeBSD 5.0, and was originally developed for Linux kernel 2.0.x, later written for 2.2.x and 2.4.x.
AUTHORS
The driver was developed by Coleman Kane <cokane@micro.ti.com> after the linux version of this driver by Darryll Straus, John Taylor, Jens
Axboe, Carlo Wood <carlo@alinoe.com> and Joseph Kain <joseph@3dfx.com> to be directly compatible with it and support the many GLIDE based
games available for Linux and UNIX.
BSD
February 19, 2001 BSD