| |
I0OJJ > SYSOP 03.04.23 00:01l 32 Lines 1030 Bytes #999 (0) @ WW
BID : A3ELR_I0OJJ
Read: GUEST
Subj: Apropos of a LinBPQ Term
Path: IW8PGT<I3XTY<IZ3LSV<IW0QNL<VE2PKT<VE3KPG<VE3CGR<VE3CGR<I0OJJ
Sent: 230402/2147z @:I0OJJ.ITA.EU [Rome] $:A3ELR_I0OJJ
>From i0ojj@i0ojj.ampr.org Sun Apr 2 23:47:59 2023
Received: from [44.134.32.240] by i0ojj.ampr.org (JNOS2.0o.1) with SMTP
id AA16955055 ; Sun, 02 Apr 2023 23:47:58 +0200
Message-ID: <f38e50b1-b269-c2b4-4c1b-1067ed1100bb@i0ojj.ampr.org>
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.9.1
Content-Language: en-US
>From: Gustavo Ponza <i0ojj@i0ojj.ampr.org>
Organization: SICD Rome
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
noted that the LinBPQ node is 'de facto' lacking of
a terminal console integrated on the linux character
console; This limiting the local sysop to access the
node ONLY by the classic telnet or the X11 QtTermTCP.
Being this last a VERY good software, indeed!
The goal could be to have the capability to boot the
linbpq system with a more or less elaborate character
console, and maintaining the actual daemon feature
if needed.
--
73 and ciao, gustavo i0ojj/ir0aab/ir0eq
non multa, sed multum
Read previous mail | Read next mail
| |
