pseudo(4) File Formats pseudo(4)NAME
pseudo - configuration files for pseudo device drivers
DESCRIPTION
Pseudo devices are devices that are implemented entirely in software. Drivers for pseudo devices must provide driver configuration files to
inform the system of each pseudo device that should be created.
Configuration files for pseudo device drivers must identify the parent driver explicitly as pseudo, and must create an integer property
called instance which is unique to this entry in the configuration file.
Each entry in the configuration file creates a prototype devinfo node. Each node is assigned an instance number which is determined by the
value of the instance property. This property is only applicable to children of the pseudo parent, and is required since pseudo devices
have no hardware address from which to determine the instance number. See driver.conf(4) for further details of configuration file syntax.
EXAMPLES
Example 1: A sample configuration file.
Here is a configuration file called ramdisk.conf for a pseudo device driver that implements a RAM disk. This file creates two nodes called
"ramdisk". The first entry creates ramdisk node instance 0, and the second creates ramdisk node, instance 1, with the additional disk-size
property set to 512.
#
# Copyright (c) 1993, by Sun Microsystems, Inc.
#
#ident "@(#)ramdisk.conf 1.3 93/06/04 SMI"
name="ramdisk" parent="pseudo" instance=0;
name="ramdisk" parent="pseudo" instance=1 disk-size=512;
SEE ALSO driver.conf(4), ddi_prop_op(9F)
Writing Device Drivers
SunOS 5.10 15 Jun 1993 pseudo(4)
Check Out this Related Man Page
pseudo(4) File Formats pseudo(4)NAME
pseudo - configuration files for pseudo device drivers
DESCRIPTION
Pseudo devices are devices that are implemented entirely in software. Drivers for pseudo devices must provide driver configuration files to
inform the system of each pseudo device that should be created.
Configuration files for pseudo device drivers must identify the parent driver explicitly as pseudo, and must create an integer property
called instance which is unique to this entry in the configuration file.
Each entry in the configuration file creates a prototype devinfo node. Each node is assigned an instance number which is determined by the
value of the instance property. This property is only applicable to children of the pseudo parent, and is required since pseudo devices
have no hardware address from which to determine the instance number. See driver.conf(4) for further details of configuration file syntax.
EXAMPLES
Example 1: A sample configuration file.
Here is a configuration file called ramdisk.conf for a pseudo device driver that implements a RAM disk. This file creates two nodes called
"ramdisk". The first entry creates ramdisk node instance 0, and the second creates ramdisk node, instance 1, with the additional disk-size
property set to 512.
#
# Copyright (c) 1993, by Sun Microsystems, Inc.
#
#ident "@(#)ramdisk.conf 1.3 93/06/04 SMI"
name="ramdisk" parent="pseudo" instance=0;
name="ramdisk" parent="pseudo" instance=1 disk-size=512;
SEE ALSO driver.conf(4), ddi_prop_op(9F)
Writing Device Drivers
SunOS 5.10 15 Jun 1993 pseudo(4)
Hi I have a system that gave me some messages on bootup that I was not used to seeing:
pseudo: pseudo-device: vol0
genunix: vol0 is /pseudo/vol@0
these came with these:
Feb 13 17:42:17 system1 eri: SUNW,eri0 : 100 Mbps full duplex link up
Feb 13 17:42:21 system1sendmail: My unqualified... (0 Replies)
Hi all,
what does this mean?
if
then
<something>
fi
here is what i know..
it checks if the specified argument no($devid) in some function call is made into a block device and then proceeds with the execution of the loop.
However am not understand what lofi@0:means?
also is there... (3 Replies)
Hello,
I was wondering if there is any way to declare something like this pseudo code:
If ;then?
how to write to check if that $x has a value or anything? (3 Replies)