[nos-bbs] nos-bbs Digest, Vol 137, Issue 1

ve1jot ve1jot at eastlink.ca
Thu Mar 3 18:56:48 EST 2016


Direwolf handles my ports here, and I link to direwolf with jnos2 on a 
tunnel, as direwolf handles the new pty stuff, and creates it's own link 
to "/tmp/kisstnc"..
Eg:
/usr/local/bin/direwolf -p -c /home/pi/direwolf.conf >/dev/tty1 &
     sleep 5
     mkiss -s 1200 /tmp/kisstnc /dev/ptyq2 /dev/ptyq3
     sleep 2
     kissattach /dev/ttyq2 sm0 $AMPRIP
     sleep 1
     kissattach /dev/ttyq3 sm1 $AMPRIP
     kissparms -p sm0 -c 1 -t 300 -s 20 -r 164 -l 100
     ##kissparms -p sm0 -f n
     kissparms -p sm1 -c 1 -t 300 -s 20 -r 132 -l 100



On 16-03-03 05:43 PM, nos-bbs-request at tapr.org wrote:
> Send nos-bbs mailing list submissions to
> 	nos-bbs at tapr.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://www.tapr.org/mailman/listinfo/nos-bbs
> or, via email, send a message with subject or body 'help' to
> 	nos-bbs-request at tapr.org
>
> You can reach the person managing the list at
> 	nos-bbs-owner at tapr.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of nos-bbs digest..."
>
>
> Today's Topics:
>
>     1. Legacy pty/tty devices at Raspberry PI 2 (Boudewijn (Bob) Tenty)
>     2. Re: Legacy pty/tty devices at Raspberry PI 2 (ve1drg)
>     3. Re: Legacy pty/tty devices at Raspberry PI 2
>        (Boudewijn (Bob) Tenty)
>     4. Re: Legacy pty/tty devices at Raspberry PI 2 (Bill Vodall)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 3 Mar 2016 14:08:32 -0500
> From: "Boudewijn (Bob) Tenty" <bobtenty at gmail.com>
> To: nos-bbs at tapr.org
> Subject: [nos-bbs] Legacy pty/tty devices at Raspberry PI 2
> Message-ID: <56D88BB0.3040906 at gmail.com>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
>
> I recompiled the pi kernel and modules to switch on the pty/tty BSD
> legacy devices.
> The kernel config (config.gz) in /proc shows they are turned on but I
> don't see them in /dev
> I used "udevadm trigger" while I monitored in another shell with
> "udevadm monitor"
> but I don't see them  at all listed (You can also look in /sys, they are
> not there)
>
> Anybody aware of problems with these devices at the PI?
> kernel is 4.1.18
>
> 73,
>
> Bob VE3TOK
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.tapr.org/pipermail/nos-bbs/attachments/20160303/f59278ba/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 03 Mar 2016 15:24:32 -0500
> From: ve1drg <ve1drg at gmail.com>
> To: TAPR xNOS Mailing List <nos-bbs at tapr.org>
> Subject: Re: [nos-bbs] Legacy pty/tty devices at Raspberry PI 2
> Message-ID: <lssl26kwgdm82o3yqdnrmn95.1457036672715 at email.android.com>
> Content-Type: text/plain; charset="utf-8"
>
>
>      
> Holy cow Bob.
> Thanks for all the work. But why is it not working?
> Is everyone  having this problem with the raspberry  Pi??
>
>
>
> --Ted Gervais 1464 luxury aveWindsor OntarioN8p0a9
>
>
> -------- Original message --------
> From: "Boudewijn (Bob) Tenty" <bobtenty at gmail.com>
> Date: 2016-03-03  2:08 PM  (GMT-05:00)
> To: nos-bbs at tapr.org
> Subject: [nos-bbs] Legacy pty/tty devices at Raspberry PI 2
>
>
>      
>      
>
>      
>      I recompiled
>        the pi kernel and modules to switch on the pty/tty BSD legacy
>        devices.
>      The kernel
>        config (config.gz) in /proc shows they are turned on but I don't
>        see them in /dev
>      I used
>        "udevadm trigger" while I monitored in another shell with "udevadm
>        monitor"
>      but I don't
>        see them  at all listed (You can also look in /sys, they are not
>        there)
>
>      
>      
>
>      
>      Anybody aware
>        of problems with these devices at the PI?
>
>        kernel is 4.1.18
>
>        
>
>        73,
>
>        
>
>        Bob VE3TOK
>
>      
>      
>
>      
>
>    
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.tapr.org/pipermail/nos-bbs/attachments/20160303/2a18861b/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 3 Mar 2016 16:36:13 -0500
> From: "Boudewijn (Bob) Tenty" <bobtenty at gmail.com>
> To: TAPR xNOS Mailing List <nos-bbs at tapr.org>
> Subject: Re: [nos-bbs] Legacy pty/tty devices at Raspberry PI 2
> Message-ID: <56D8AE4D.3050202 at gmail.com>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> That is exactly what I want to know or for that kernel release at least
> It has to do with Udev.
>
> 73,
>
> Bob VE3TOK
>
> On 16-03-03 03:24 PM, ve1drg wrote:
>> Holy cow Bob.
>>
>> Thanks for all the work. But why is it not working?
>>
>> Is everyone  having this problem with the raspberry  Pi??
>>
>>
>>
>>
>> -- 
>> Ted Gervais
>> 1464 luxury ave
>> Windsor Ontario
>> N8p0a9
>>
>>
>>
>> -------- Original message --------
>> From: "Boudewijn (Bob) Tenty" <bobtenty at gmail.com>
>> Date: 2016-03-03 2:08 PM (GMT-05:00)
>> To: nos-bbs at tapr.org
>> Subject: [nos-bbs] Legacy pty/tty devices at Raspberry PI 2
>>
>>
>> I recompiled the pi kernel and modules to switch on the pty/tty BSD
>> legacy devices.
>> The kernel config (config.gz) in /proc shows they are turned on but I
>> don't see them in /dev
>> I used "udevadm trigger" while I monitored in another shell with
>> "udevadm monitor"
>> but I don't see them  at all listed (You can also look in /sys, they
>> are not there)
>>
>> Anybody aware of problems with these devices at the PI?
>> kernel is 4.1.18
>>
>> 73,
>>
>> Bob VE3TOK
>>
>>
>>
>>
>> _______________________________________________
>> nos-bbs mailing list
>> nos-bbs at tapr.org
>> http://www.tapr.org/mailman/listinfo/nos-bbs
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.tapr.org/pipermail/nos-bbs/attachments/20160303/4307ea8f/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 3 Mar 2016 13:11:50 -0800
> From: Bill Vodall <wa7nwp at gmail.com>
> To: TAPR xNOS Mailing List <nos-bbs at tapr.org>
> Subject: Re: [nos-bbs] Legacy pty/tty devices at Raspberry PI 2
> Message-ID:
> 	<CAPSBm53G-kuJ9ak9Uw_MJ-sVOSPsWi_eNgvRghvmBHJwptQ+3g at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Thu, Mar 3, 2016 at 12:24 PM, ve1drg <ve1drg at gmail.com> wrote:
>> Holy cow Bob.
>>
>> Thanks for all the work. But why is it not working?
>>
>> Is everyone  having this problem with the raspberry  Pi??
>
> Newer Linux kernels, from the past few years, use the new PTY system
> and don't turn on the legacy PTY's we need.  The last time I ran into
> it I had to add an option to the boot line to tell the Kernel to use
> Legacy PTY's.  From there on they showed up.
>
> 73
> Bill, WA7NWP
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs
>
>
> ------------------------------
>
> End of nos-bbs Digest, Vol 137, Issue 1
> ***************************************




More information about the nos-bbs mailing list