[Coco] Unresolved inet error issue

[Taylor, Phillip L CIV]

I am trying to fix the error issue with Inetd and the nil device does not 
exist on the Nitro-Os9 disk. Using Nil I do not think that will fix it either.


Message: 5
Date: Fri, 17 Mar 2017 02:22:11 +0000
From: Jeff Teunissen <deek at d2dc.net>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Subject: Re: [Coco] Error trying to use Inetd &
Message-ID:
	<CACuf1ij_Sh+Oi5RH74bQM6_vov_1+0Co0cTd18-sE5tAhYrDTg at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

I think you may have to use the + directive for appending, i.e.:

inetd <>>>+/dd/sys/logs/inetd.log&


On Thu, Mar 16, 2017, 7:22 AM William Carlin <whcarlinjr at gmail.com> wrote:

> This is 'debugging' text that is spewed out of the inetd when in operation.
>
> On my CoCo 3 I have /w15 initialized with no active shell and then dump the
> debugging messages to that window.  So my startup looks like this for
> initializing the inetd:
>
> [/DD/startup]
>
> inetd<>>>/w15&
>
>
> On my CoCo 2 I can either dump the debugging info to a text file in the
> /DD/SYS/LOGS folder or I will add the /nil device and send it there:
>
> inetd<>>>/dd/sys/logs/inetd.log&
>
> or
>
> inetd<>>>/nil&
>
>
> Note that when dumping to a text file you will need to delete that file if
> it already exists as the standard NitrOS9 shell does not seem to support
> appends or overwrites when redirecting output.
>
>
> William Carlin
>
>
>
> On Wed, Mar 15, 2017 at 8:46 PM, phillip taylor <ptaylor2446 at gmail.com>
> wrote:
>
> > When the error displays on the screen it keeps repeating the same mesage
> > and it does not return back to the shell with the process number then
> end.
> >
> > On Wed, Mar 15, 2017 at 7:53 PM, phillip taylor <ptaylor2446 at gmail.com>
> > wrote:
> >
> > >
> > > I am trying to get my coco so I can telnet and login and after I type
> > > inetd & I am etting ss.ssig on net path. How can I fix this issue?
> > >
> > > Thanks
> > >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__pairlist5.pair.net_mailman_listinfo_coco&d=DwIGaQ&c=0NKfg44GVknAU-XkWXjNxQ&r=_wDO0Ub5GRKd_gN_Uz7gGyIfuv5XrYnarPGRxBtD3N0&m=Q6Xhq2gMBIiaWOtbTZMdEc1L6S7t0LGqSWRF_skqZpU&s=Ra4lWLZytuWL0Y1Gl_WZTPMR-rirhDitn4OniOyx6ug&e=
> >
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://urldefense.proofpoint.com/v2/url?u=https-3A__pairlist5.pair.net_mailman_listinfo_coco&d=DwIGaQ&c=0NKfg44GVknAU-XkWXjNxQ&r=_wDO0Ub5GRKd_gN_Uz7gGyIfuv5XrYnarPGRxBtD3N0&m=Q6Xhq2gMBIiaWOtbTZMdEc1L6S7t0LGqSWRF_skqZpU&s=Ra4lWLZytuWL0Y1Gl_WZTPMR-rirhDitn4OniOyx6ug&e=
>


------------------------------

Message: 6
Date: Thu, 16 Mar 2017 23:37:37 -0400
From: "Bill" <cwgordon at carolina.rr.com>
To: "Coco Enthusiasts" <coco at maltedmedia.com>
Subject: [Coco] (no subject)
Message-ID: <000001d29ecf$d2fe5d70$78fb1850$@rr.com>
Content-Type: text/plain;	charset="us-ascii"

I'm using Drivewire 4 and nos96809l2v030300coco3_dw.dsk, and when I try to
access a physical drive, I get an ERROR 249 message. Does anyone have a
solution to this? I can format to the physical drive, and after that, II get
the ERROR 249 again



------------------------------

Subject: Digest Footer

_______________________________________________
Coco mailing list
Coco at maltedmedia.com
https://urldefense.proofpoint.com/v2/url?u=https-3A__pairlist5.pair.net_mailman_listinfo_coco&d=DwIGaQ&c=0NKfg44GVknAU-XkWXjNxQ&r=_wDO0Ub5GRKd_gN_Uz7gGyIfuv5XrYnarPGRxBtD3N0&m=Q6Xhq2gMBIiaWOtbTZMdEc1L6S7t0LGqSWRF_skqZpU&s=Ra4lWLZytuWL0Y1Gl_WZTPMR-rirhDitn4OniOyx6ug&e=


------------------------------

End of Coco Digest, Vol 174, Issue 74
*************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5379 bytes
Desc: not available
URL: <https://pairlist5.pair.net/pipermail/coco/attachments/20170317/95bd34f1/attachment.bin>