paulkoning at comcast.net
Thu Aug 19 15:45:47 CDT 2021
> On Aug 19, 2021, at 4:37 PM, John Forecast via cctalk <cctalk at classiccmp.org> wrote:
>> On Aug 19, 2021, at 9:37 AM, Bill Gunshannon via cctalk <cctalk at classiccmp.org> wrote:
>> On 8/19/21 12:23 AM, Warner Losh via cctalk wrote:
>>> On Wed, Aug 18, 2021 at 10:07 PM Bill Degnan <billdegnan at gmail.com> wrote:
>>>> pretty cool
>>> Thanks! Looking at the boot source I figured out that I just needed to
>>> build a non-generic kernel
>>> to get rid of the load device prompt... I'd somehow omitted that during the
>> I always skip that during the install. Much safer to do it
>> later when I am sure I have a stable system. Need to add
>> serial devices and network device. I wonder if the DECNET
>> daemon from Linux would back port to Ultrix-11? CLient side
>> is provided, but no daemon that I am aware of.
> If by daemon you mean the kernel code supporting NSP and routing protocols then, no, it would not be an easy back port, that code makes heavy use of Linux-specific functions and capabilities. The user-level utilities would be much simpler but you would need to copy over the DECnet header files and implement the expected library routines (getnodebyname(), getobjent() etc).
Does Linux follow the DECnet socket services of Ultrix, or are they different? I remember that Ultrix had socket operations matching the power of the DECnet application interface, stuff like connect data or packet-oriented data transmission. It also supported a basic stream service, which was mapped (somehow -- I'd like to find the details) onto the underlying DECnet packet service.
I've been thinking it would be neat to have an httpd that answers DECnet connections (object number 80, of course).
More information about the cctech