# dgrp\_cfg\_node **URL:** \ **Category:** Realport\ **Created:** [January 3, 2007, 11:30am UTC](https://forums.digi.com/t/dgrp-cfg-node/7164 "2007-01-03T11:30:30Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![hm2k](https://avatars.discourse-cdn.com/v4/letter/h/a6a055/32.png) [@hm2k](https://forums.digi.com/u/hm2k)\ **Post date:** [January 3, 2007, 11:30am UTC](https://forums.digi.com/t/dgrp-cfg-node/7164/1 "2007-01-03T11:30:30Z")
So I finally got the driver working on CentOS… The device I have is a Digi PortServer 16 on ip 192.68.10.4 (I can check this by telnetting to that ip). So, next I ran this… /usr/bin/dgrp/config/dgrp\_cfg\_node -v -v init a 192.68.10.4 16 And this is the result… [root@localhost dev]# ls arpd loop2 md2 nst0 ram3 stdin tty tty3 tty51 ttyS7 cdrom loop3 md20 nst0a ram4 stdout tty0 tty30 tty52 urandom console loop4 md21 nst0l ram5 systty tty1 tty31 tty53 usersock core loop5 md22 nst0m ram6 tap0 tty10 tty32 tty54 vcs cpu loop6 md23 null ram7 tap1 tty11 tty33 tty55 vcs1 device-mapper loop7 md24 par0 ram8 tap10 tty12 tty34 tty56 vcs2 disk lp0 md25 parport0 ram9 tap11 tty13 tty35 tty57 vcs3 dm-0 lp1 md26 parport1 ramdisk tap12 tty14 tty36 tty58 vcs4 dm-1 lp2 md27 parport2 random tap13 tty15 tty37 tty59 vcs5 dnrtmsg lp3 md28 parport3 rawctl tap14 tty16 tty38 tty6 vcs6 event0 MAKEDEV md29 port root tap15 tty17 tty39 tty60 vcsa fd mapper md3 ppp route tap2 tty18 tty4 tty61 vcsa1 full md0 md30 ptmx route6 tap3 tty19 tty40 tty62 vcsa2 fwmonitor md1 md31 pts rtc tap4 tty2 tty41 tty63 vcsa3 gpmctl md10 md4 ram sda tap5 tty20 tty42 tty7 vcsa4 hda md11 md5 ram0 sda1 tap6 tty21 tty43 tty8 vcsa5 hw\_random md12 md6 ram1 sda2 tap7 tty22 tty44 tty9 vcsa6 initctl md13 md7 ram10 shm tap8 tty23 tty45 ttyS0 VolGroup00 input md14 md8 ram11 skip tap9 tty24 tty46 ttyS1 xfrm ip6\_fw md15 md9 ram12 st0 tape tty25 tty47 ttyS2 XOR kmsg md16 mem ram13 st0a tape1 tty26 tty48 ttyS3 zero log md17 mice ram14 st0l tape2 tty27 tty49 ttyS4 loop0 md18 net ram15 st0m tape3 tty28 tty5 ttyS5 loop1 md19 nflog ram2 stderr tcpdiag tty29 tty50 ttyS6 [root@localhost dev]# /usr/bin/dgrp/config/dgrp\_cfg\_node -v -v init a 192.68.10.4 16 /usr/bin/dgrp/config/dgrp\_cfg\_node: init requested for node a /usr/bin/dgrp/config/dgrp\_cfg\_node: testing for a loaded module /usr/bin/dgrp/config/dgrp\_cfg\_node: double checking the load /usr/bin/dgrp/config/dgrp\_cfg\_node: testing for a in /proc /usr/bin/dgrp/config/dgrp\_cfg\_node: double checking the addition of a /usr/bin/dgrp/config/dgrp\_cfg\_node: making the special devices for a /usr/bin/dgrp/config/dgrp\_cfg\_node: testing for a daemon for a /usr/bin/dgrp/config/dgrp\_cfg\_node: testing for a daemon for a /usr/bin/dgrp/config/dgrp\_cfg\_node: testing for a loaded module /usr/bin/dgrp/config/dgrp\_cfg\_node: testing for a a in /proc /usr/bin/dgrp/config/dgrp\_cfg\_node: attempting to start a daemon for a /usr/bin/dgrp/config/dgrp\_cfg\_node: operation completed (init node a) [root@localhost dev]# ls arpd cu\_dgrp\_a\_26 cu\_dgrp\_a\_62 md12 parport2 pr\_dgrp\_a\_27 pr\_dgrp\_a\_63 stdin tty22 tty59 tty\_dgrp\_a\_22 tty\_dgrp\_a\_59 cdrom cu\_dgrp\_a\_27 cu\_dgrp\_a\_63 md13 parport3 pr\_dgrp\_a\_28 pr\_dgrp\_a\_7 stdout tty23 tty6 tty\_dgrp\_a\_23 tty\_dgrp\_a\_6 console cu\_dgrp\_a\_28 cu\_dgrp\_a\_7 md14 port pr\_dgrp\_a\_29 pr\_dgrp\_a\_8 systty tty24 tty60 tty\_dgrp\_a\_24 tty\_dgrp\_a\_60 core cu\_dgrp\_a\_29 cu\_dgrp\_a\_8 md15 ppp pr\_dgrp\_a\_3 pr\_dgrp\_a\_9 tap0 tty25 tty61 tty\_dgrp\_a\_25 tty\_dgrp\_a\_61 cpu cu\_dgrp\_a\_3 cu\_dgrp\_a\_9 md16 pra00 pr\_dgrp\_a\_30 ptmx tap1 tty26 tty62 tty\_dgrp\_a\_26 tty\_dgrp\_a\_62 cua00 cu\_dgrp\_a\_30 device-mapper md17 pra01 pr\_dgrp\_a\_31 pts tap10 tty27 tty63 tty\_dgrp\_a\_27 tty\_dgrp\_a\_63 cua01 cu\_dgrp\_a\_31 disk md18 pra02 pr\_dgrp\_a\_32 ram tap11 tty28 tty7 tty\_dgrp\_a\_28 tty\_dgrp\_a\_7 cua02 cu\_dgrp\_a\_32 dm-0 md19 pra03 pr\_dgrp\_a\_33 ram0 tap12 tty29 tty8 tty\_dgrp\_a\_29 tty\_dgrp\_a\_8 cua03 cu\_dgrp\_a\_33 dm-1 md2 pra04 pr\_dgrp\_a\_34 ram1 tap13 tty3 tty9 tty\_dgrp\_a\_3 tty\_dgrp\_a\_9 cua04 cu\_dgrp\_a\_34 dnrtmsg md20 pra05 pr\_dgrp\_a\_35 ram10 tap14 tty30 ttya00 tty\_dgrp\_a\_30 ttyS0 cua05 cu\_dgrp\_a\_35 event0 md21 pra06 pr\_dgrp\_a\_36 ram11 tap15 tty31 ttya01 tty\_dgrp\_a\_31 ttyS1 cua06 cu\_dgrp\_a\_36 fd md22 pra07 pr\_dgrp\_a\_37 ram12 tap2 tty32 ttya02 tty\_dgrp\_a\_32 ttyS2 cua07 cu\_dgrp\_a\_37 full md23 pra08 pr\_dgrp\_a\_38 ram13 tap3 tty33 ttya03 tty\_dgrp\_a\_33 ttyS3 cua08 cu\_dgrp\_a\_38 fwmonitor md24 pra09 pr\_dgrp\_a\_39 ram14 tap4 tty34 ttya04 tty\_dgrp\_a\_34 ttyS4 cua09 cu\_dgrp\_a\_39 gpmctl md25 pra10 pr\_dgrp\_a\_4 ram15 tap5 tty35 ttya05 tty\_dgrp\_a\_35 ttyS5 cua10 cu\_dgrp\_a\_4 hda md26 pra11 pr\_dgrp\_a\_40 ram2 tap6 tty36 ttya06 tty\_dgrp\_a\_36 ttyS6 cua11 cu\_dgrp\_a\_40 hw\_random md27 pra12 pr\_dgrp\_a\_41 ram3 tap7 tty37 ttya07 tty\_dgrp\_a\_37 ttyS7 cua12 cu\_dgrp\_a\_41 initctl md28 pra13 pr\_dgrp\_a\_42 ram4 tap8 tty38 ttya08 tty\_dgrp\_a\_38 urandom cua13 cu\_dgrp\_a\_42 input md29 pra14 pr\_dgrp\_a\_43 ram5 tap9 tty39 ttya09 tty\_dgrp\_a\_39 usersock cua14 cu\_dgrp\_a\_43 ip6\_fw md3 pra15 pr\_dgrp\_a\_44 ram6 tape tty4 ttya10 tty\_dgrp\_a\_4 vcs cua15 cu\_dgrp\_a\_44 kmsg md30 pr\_dgrp\_a\_0 pr\_dgrp\_a\_45 ram7 tape1 tty40 ttya11 tty\_dgrp\_a\_40 vcs1 cu\_dgrp\_a\_0 cu\_dgrp\_a\_45 log md31 pr\_dgrp\_a\_1 pr\_dgrp\_a\_46 ram8 tape2 tty41 ttya12 tty\_dgrp\_a\_41 vcs2 cu\_dgrp\_a\_1 cu\_dgrp\_a\_46 loop0 md4 pr\_dgrp\_a\_10 pr\_dgrp\_a\_47 ram9 tape3 tty42 ttya13 tty\_dgrp\_a\_42 vcs3 cu\_dgrp\_a\_10 cu\_dgrp\_a\_47 loop1 md5 pr\_dgrp\_a\_11 pr\_dgrp\_a\_48 ramdisk tcpdiag tty43 ttya14 tty\_dgrp\_a\_43 vcs4 cu\_dgrp\_a\_11 cu\_dgrp\_a\_48 loop2 md6 pr\_dgrp\_a\_12 pr\_dgrp\_a\_49 random tty tty44 ttya15 tty\_dgrp\_a\_44 vcs5 cu\_dgrp\_a\_12 cu\_dgrp\_a\_49 loop3 md7 pr\_dgrp\_a\_13 pr\_dgrp\_a\_5 rawctl tty0 tty45 tty\_dgrp\_a\_0 tty\_dgrp\_a\_45 vcs6 cu\_dgrp\_a\_13 cu\_dgrp\_a\_5 loop4 md8 pr\_dgrp\_a\_14 pr\_dgrp\_a\_50 root tty1 tty46 tty\_dgrp\_a\_1 tty\_dgrp\_a\_46 vcsa cu\_dgrp\_a\_14 cu\_dgrp\_a\_50 loop5 md9 pr\_dgrp\_a\_15 pr\_dgrp\_a\_51 route tty10 tty47 tty\_dgrp\_a\_10 tty\_dgrp\_a\_47 vcsa1 cu\_dgrp\_a\_15 cu\_dgrp\_a\_51 loop6 mem pr\_dgrp\_a\_16 pr\_dgrp\_a\_52 route6 tty11 tty48 tty\_dgrp\_a\_11 tty\_dgrp\_a\_48 vcsa2 cu\_dgrp\_a\_16 cu\_dgrp\_a\_52 loop7 mice pr\_dgrp\_a\_17 pr\_dgrp\_a\_53 rtc tty12 tty49 tty\_dgrp\_a\_12 tty\_dgrp\_a\_49 vcsa3 cu\_dgrp\_a\_17 cu\_dgrp\_a\_53 lp0 net pr\_dgrp\_a\_18 pr\_dgrp\_a\_54 sda tty13 tty5 tty\_dgrp\_a\_13 tty\_dgrp\_a\_5 vcsa4 cu\_dgrp\_a\_18 cu\_dgrp\_a\_54 lp1 nflog pr\_dgrp\_a\_19 pr\_dgrp\_a\_55 sda1 tty14 tty50 tty\_dgrp\_a\_14 tty\_dgrp\_a\_50 vcsa5 cu\_dgrp\_a\_19 cu\_dgrp\_a\_55 lp2 nst0 pr\_dgrp\_a\_2 pr\_dgrp\_a\_56 sda2 tty15 tty51 tty\_dgrp\_a\_15 tty\_dgrp\_a\_51 vcsa6 cu\_dgrp\_a\_2 cu\_dgrp\_a\_56 lp3 nst0a pr\_dgrp\_a\_20 pr\_dgrp\_a\_57 shm tty16 tty52 tty\_dgrp\_a\_16 tty\_dgrp\_a\_52 VolGroup00 cu\_dgrp\_a\_20 cu\_dgrp\_a\_57 MAKEDEV nst0l pr\_dgrp\_a\_21 pr\_dgrp\_a\_58 skip tty17 tty53 tty\_dgrp\_a\_17 tty\_dgrp\_a\_53 xfrm cu\_dgrp\_a\_21 cu\_dgrp\_a\_58 mapper nst0m pr\_dgrp\_a\_22 pr\_dgrp\_a\_59 st0 tty18 tty54 tty\_dgrp\_a\_18 tty\_dgrp\_a\_54 XOR cu\_dgrp\_a\_22 cu\_dgrp\_a\_59 md0 null pr\_dgrp\_a\_23 pr\_dgrp\_a\_6 st0a tty19 tty55 tty\_dgrp\_a\_19 tty\_dgrp\_a\_55 zero cu\_dgrp\_a\_23 cu\_dgrp\_a\_6 md1 par0 pr\_dgrp\_a\_24 pr\_dgrp\_a\_60 st0l tty2 tty56 tty\_dgrp\_a\_2 tty\_dgrp\_a\_56 cu\_dgrp\_a\_24 cu\_dgrp\_a\_60 md10 parport0 pr\_dgrp\_a\_25 pr\_dgrp\_a\_61 st0m tty20 tty57 tty\_dgrp\_a\_20 tty\_dgrp\_a\_57 cu\_dgrp\_a\_25 cu\_dgrp\_a\_61 md11 parport1 pr\_dgrp\_a\_26 pr\_dgrp\_a\_62 stderr tty21 tty58 tty\_dgrp\_a\_21 tty\_dgrp\_a\_58 The question is now… What is what? Why are there so many new ones? Which tty’s relate to which ports on the port server? How can I find out? So many questions, so few answers, I feel like i’ve missed out on some documentation somewhere, yet I can’t locate anything additional. I look forward to your responses. ---
**Author:** ![hm2k](https://avatars.discourse-cdn.com/v4/letter/h/a6a055/32.png) [@hm2k](https://forums.digi.com/u/hm2k)\ **Post date:** [January 3, 2007, 11:37am UTC](https://forums.digi.com/t/dgrp-cfg-node/7164/2 "2007-01-03T11:37:36Z")
So i’m reading this… [http://ftp1.digi.com/support/deviceservers/digiflex/digiflexdcwmodem/linuxsuse/64/documentation/92000316\_a.pdf](http://ftp1.digi.com/support/deviceservers/digiflex/digiflexdcwmodem/linuxsuse/64/documentation/92000316_a.pdf) On page 3-8 (22 of 34) it explains a bit more. However, its only got 16 ports, so why are there so many? ---
**Author:** ![hm2k](https://avatars.discourse-cdn.com/v4/letter/h/a6a055/32.png) [@hm2k](https://forums.digi.com/u/hm2k)\ **Post date:** [January 3, 2007, 12:20pm UTC](https://forums.digi.com/t/dgrp-cfg-node/7164/3 "2007-01-03T12:20:48Z")
After closer examination I noticed there are some tty’s as follows: ttya00 to ttya15 00 relates to physical port 1, so 15 relates to physical port 16. I figured out I had a printer on ttya14, which is physical port 15, and managed to output using: echo 'testing ’ \> /dev/ttya14 Hope this helps others. ---
**Author:** ![userid0](https://avatars.discourse-cdn.com/v4/letter/u/f6c823/32.png) [@userid0](https://forums.digi.com/u/userid0)\ **Post date:** [January 3, 2007, 1:52pm UTC](https://forums.digi.com/t/dgrp-cfg-node/7164/4 "2007-01-03T13:52:30Z")
The cu\* devices are deprecated and no longer used in Linux. The pr\* devices are used for transparent printing and the tty\* devices are the standard devices. ---
**Author:** ![scottk](https://avatars.discourse-cdn.com/v4/letter/s/db5fbb/32.png) [@scottk](https://forums.digi.com/u/scottk)\ **Post date:** [January 3, 2007, 3:42pm UTC](https://forums.digi.com/t/dgrp-cfg-node/7164/5 "2007-01-03T15:42:26Z")
What version of the RealPort driver are you using? The most current “beta” version of the RealPort driver should NOT register 64 ports with sysfs/UDEV when you only have 16. As for the naming itself, the current beta driver has been transitioned to fully support UDEV now: ([http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html](http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html)) This makes the tty naming go back to the way it should be. Scott Kilau