11-05-2019
I try to restart this server few times, but it not help, also try rmdev -Rdl after which device totaly dissapeared and cfgmgr cant find it.
5 More Discussions You Might Find Interesting
1. 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
2. SuSE
Hi All,
I used to have my suse linux(VM) server in graphic mode but not anymore since morning. I cant rolback since i loose somuch work. Any idea how to it back to normal. Thanks (6 Replies)
Discussion started by: s_linux
6 Replies
3. UNIX for Advanced & Expert Users
Hi All,
Can please let me know what is the difference between the single line mode and multi line mode in regular expresions?
Thanks,
Chidhambaram B (3 Replies)
Discussion started by: chidhu.anu
3 Replies
4. Solaris
:confused:
when i tried to look the status of DNS-client, it is in maintenance mode.....
Please tell me how to bring it back to online mode...PLEASE TELL ME STEP BY STEP.... PLEASE...
:wall: (2 Replies)
Discussion started by: vamshigvk475
2 Replies
5. HP-UX
is there a way for my C++ application to find out which mode the hpux OS is running in?
standard mode or trusted mode. (3 Replies)
Discussion started by: einsteinBrain
3 Replies
kmknod(8) System Manager's Manual kmknod(8)
NAME
kmknod - Creates device special files for static kernel layered products
SYNOPSIS
/sbin/kmknod
DESCRIPTION
The kmknod command obtains information from a running kernel and determines if any device special files must be created for use by the ker-
nel layered products that are statically configured.
To enable kmknod to create device special files, the statically configured kernel layered products must have been registered with the kreg
command.
Note
To create device special files for the kernel layered products that are loadable modules, such as loadable device drivers, use the cfgmgr
command instead of the kmknod command.
The kmknod command first deletes any files that have matching names and any files that have both matching major numbers and matching device
types (block or character). After any matching files are deleted, the kmknod command creates all the required device special files.
The /etc/inittab file contains instructions to invoke the kmknod command at boot time.
You must be superuser to invoke the kmknod command.
FILES
Provides the init program with instructions for creating and running initialization processes.
SEE ALSO
Commands: kmknod(8), kreg
System Administration
Writing Device Drivers: Tutorial
kmknod(8)