09-17-2008
Only devices in state "Available" are usable. A device in state "Defined" means that once there was such a device but has been removed/inactivated since and only the devices information is still left.
Exactlxy this definition you have removed by issuing rmdev. (Btw. consider using the "-d" switch to rmdev.) When you ran cfgmgr again the device was not created because it has still not been there and therefor the config manager had no reason to create the device entries (in the ODM). But the device was not attached to the machine (or simply switched off) before either because otherwise the devices status wouldn't have been "Defined".
To answer your question: you can immediately tell that the device is unusable, because if it would be usable it would at least be in state "Available".
I hope this helps.
bakunin
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm trying to install a tape drive on a compaq SCO OS 505. well I have gone through the mkdev tape comands and what have you yet no luck. when I reboot and do a simple tape rewind it gives me an error no such device etc.etc. IS there a diference in the xct0 and rct0 a the default?
help.. (2 Replies)
Discussion started by: kikkin
2 Replies
2. Linux
Hello. I have Redhat 8.0 on a laptop. Working good.
I wanted to install the tape drive that is physically attached to it. The tape drive worked fine under Windows98SE. It's one of those parallel QIC-80 drives and I confirmed that it is supported by FTape. It appears that FTape might already... (0 Replies)
Discussion started by: RuralTurtle
0 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I need to restore my tape backup, when I type "tape status" it gives;
status : ready beginning-of-tape write-protected
soft errors : 0
hard errors : 0
underruns : 3
but... (4 Replies)
Discussion started by: alisevA3
4 Replies
4. SCO
Dear All,
I have a tape drive which has worked for offer 3yrs properly on SCO Openserver Release = 3.2v5.0.5. I tried to clean it all invain. I did a fresh installation of unix of the same OS and did the configuration still didn't bear fruits. The tape is a scsi and the configuration is as... (4 Replies)
Discussion started by: njoroge
4 Replies
5. Solaris
Hey folks,
Linux admin here, forced to use Opensolaris to try to use ufsdump/ufsrestore to get some data of some old tapes.
I've got Opensolaris 2009.06 on x86 and a Sony SDX-700V.
As a "control" experiment, I booted the system with a Linux live CD and the tape drive worked perfectly.
... (2 Replies)
Discussion started by: eddy_sysad
2 Replies
6. SCO
I've recently been tasked with "refurbishing" an HP Proliant ML370 running SCO 5.0...something. This is primarily used for legacy support and is kept on a shelf for safe keeping. The scope of work includes hardware diagnostics and blowing the dust out.
I have run HP diagnostics on the array,... (1 Reply)
Discussion started by: v1corp
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
Using Redhat 5.7. I have Quantum tape drive connected to the server. I am trying to install the Netbackup software. Just wondering how can I see the Quantum is connected to the server. is any command I run to see the tape drive is connected?
I used to work on Solaris, I used to do... (1 Reply)
Discussion started by: samnyc
1 Replies
8. HP-UX
I have used ioscan -fnC tape and the system identified the tape drive. what is the command to show a listing of what is on the tape? I have used ls /dev/rmt/rmt0 to no avail. can anyone help?
Thanks in advance (10 Replies)
Discussion started by: Randydog
10 Replies
LEARN ABOUT FREEBSD
devctl
DEVCTL(8) BSD System Manager's Manual DEVCTL(8)
NAME
devctl -- device control utility
SYNOPSIS
devctl attach device
devctl detach [-f] device
devctl disable [-f] device
devctl enable device
devctl suspend device
devctl resume device
devctl set driver [-f] device driver
DESCRIPTION
The devctl utility adjusts the state of individual devices in the kernel's internal device hierarchy. Each invocation of devctl consists of
a single command followed by command-specific arguments. Each command operates on a single device specified via the device argument. The
device may be specified either as the name of an existing device or as a bus-specific address. More details on supported address formats can
be found in devctl(3).
The following commands are supported:
attach device
Force the kernel to re-probe the device. If a suitable driver is found, it is attached to the device.
detach [-f] device
Detach the device from its current device driver. If the -f flag is specified, the device driver will be detached even if the device
is busy.
disable [-f] device
Disable a device. If the device is currently attached to a device driver, the device driver will be detached from the device, but
the device will retain its current name. If the -f flag is specified, the device driver will be detached even if the device is busy.
enable device
Enable a device. The device will probe and attach if a suitable device driver is found. Note that this can re-enable a device dis-
abled at boot time via a loader tunable.
suspend device
Suspend a device. This may include placing the device in a reduced power state.
resume device
Resume a suspended device to a fully working state.
set driver [-f] device driver
Force the device to use a device driver named driver. If the device is already attached to a device driver and the -f flag is speci-
fied, the device will be detached from its current device driver before it is attached to the new device driver. If the device is
already attached to a device driver and the -f flag is not specified, the device will not be changed.
SEE ALSO
devctl(3), devinfo(8)
HISTORY
The devctl utility first appeared in FreeBSD 11.0.
BSD
February 5, 2015 BSD