Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pseudo(4) [v7 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)

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)
Man Page

9 More Discussions You Might Find Interesting

1. Solaris

pseudo: [ID 129642 kern.info] pseudo-device: vol0

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)
Discussion started by: mndavies
0 Replies

2. Solaris

what is /devices/pseudo/ ??

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)
Discussion started by: wrapster
3 Replies

3. Shell Programming and Scripting

how to create a ramdisk

Hi all, I wanted to make a ramdisk for a opensolaris distro. I have very little idea of how to create it? can anyone pls help me out? Is there any tutorial on creating it on the net??? Also can i make changes to the actual os itself by changing the scripts involved in ramdisk then use it to... (1 Reply)
Discussion started by: wrapster
1 Replies

4. Shell Programming and Scripting

how to modify ramdisk size,kinda urgent !!!

Hi all, I wanted to know how to modify the size of the ramdisk? I mean am manipulating a live cd ,for which the file am manipulating is within a ramdisk now due to size constraints i am unable to play around with some stuff.... currently the size of the ram disk is 64M... I would like to... (1 Reply)
Discussion started by: wrapster
1 Replies

5. Shell Programming and Scripting

Sorting in ramdisk

Hi, I have sort command that sorts in ramdisk created by a script 'mktd' and later unmounted by script 'rmtd'. The platform is AIX. # code sudo -E mktd 44 # create ramdisk of size 44GB sort ... -k1,1 -2,2 ... # sort a file using the ramdisk on keys 1 and 2 sudo -E rmtd # unmount... (1 Reply)
Discussion started by: ChicagoBlues
1 Replies

6. AIX

maximum size of a ramdisk on AIX 5.3

Hi, Do you know what is the maximum size I can use to create a ramdisk on AIX 5.3? I m pretty sure i've seen somewhere i can use more than 2 Gb but I can't remember where. I need to do some recommandations for one of my customer and they'll need to create a ramdisk of 20 Gb. Can this be done? ... (1 Reply)
Discussion started by: cedric hanquez
1 Replies

7. UNIX for Dummies Questions & Answers

IF $ has value then?

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)
Discussion started by: juzt1s
3 Replies

8. Solaris

pseudo device?

sometimes I see this message in dmesg: what does it mean? thanks. (5 Replies)
Discussion started by: orange47
5 Replies

9. AIX

0514-516 Device Configuration Database Lock Service

Hello guys, on one of our AIX VIO LPARs I can not remove hdiskpower devices, which seemed to presented to the VIO in an incorrect way and behaviour (not all paths can be seen, pseudo device name is unknown etc.) Therefor I decided to deattach the hdiskpower device from PowerPath controll by: ... (5 Replies)
Discussion started by: tomek79
5 Replies