[Coco] CoCos with Hitachi CPU

[Carlos Camacho]

Hi folks, I have a few CoCos with Hitachi (C version) for sale along with
two software bundles.
http://m.ebay.com/sch/i.html?sid=colorcomputerstore&isRefine=true

Cheers,
Carlos Camacho


On Jun 27, 2017 1:17 AM, <coco-request at maltedmedia.com> wrote:

Send Coco mailing list submissions to
        coco at maltedmedia.com

To subscribe or unsubscribe via the World Wide Web, visit
        https://pairlist5.pair.net/mailman/listinfo/coco
or, via email, send a message with subject or body 'help' to
        coco-request at maltedmedia.com

You can reach the person managing the list at
        coco-owner at maltedmedia.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Coco digest..."


Today's Topics:

   1. Re: MysticBBS (RETRO Innovations)
   2. Re: MysticBBS (Gene Heskett)


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

Message: 1
Date: Mon, 26 Jun 2017 22:19:31 -0500
From: RETRO Innovations <go4retro at go4retro.com>
To: coco at maltedmedia.com
Subject: Re: [Coco] MysticBBS
Message-ID: <52a124e9-50c0-453f-1da4-08495259e582 at go4retro.com>
Content-Type: text/plain; charset=utf-8; format=flowed

On 6/26/2017 7:52 PM, Gene Heskett wrote:
> On Monday 26 June 2017 20:09:31 Gregory Law wrote:
>
>> The port number should be specified in the -p parameter like this.
>>
>> ssh Mystic.dynu.net -p 2310
>>
> That appears to work, but whats the diff between ssh Mystic.dynu.net -p
> 2310,
>
> and ssh Mystic.dynu.net:2310?  Thats how people get into this machine
> using http protocol.  Difference in routers and port forwarding I guess.
the http protocol stipulates a URI nomenclature, but ssh was designed as
a replacement for telnet and rlogin, which do not know about URIs, as
they were developed in the 1970s and 1980s, prior to Berners-Lee and HTTP.

Some newer applications allow :port as a shortcut to a command line arg,
but ssh does not.

Jim


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

Message: 2
Date: Mon, 26 Jun 2017 23:46:13 -0400
From: Gene Heskett <gheskett at shentel.net>
To: coco at maltedmedia.com
Subject: Re: [Coco] MysticBBS
Message-ID: <201706262346.13369.gheskett at shentel.net>
Content-Type: Text/Plain;  charset="utf-8"

On Monday 26 June 2017 23:19:31 RETRO Innovations wrote:

> On 6/26/2017 7:52 PM, Gene Heskett wrote:
> > On Monday 26 June 2017 20:09:31 Gregory Law wrote:
> >> The port number should be specified in the -p parameter like this.
> >>
> >> ssh Mystic.dynu.net -p 2310
> >
> > That appears to work, but whats the diff between ssh Mystic.dynu.net
> > -p 2310,
> >
> > and ssh Mystic.dynu.net:2310?  Thats how people get into this
> > machine using http protocol.  Difference in routers and port
> > forwarding I guess.
>
> the http protocol stipulates a URI nomenclature, but ssh was designed
> as a replacement for telnet and rlogin, which do not know about URIs,
> as they were developed in the 1970s and 1980s, prior to Berners-Lee
> and HTTP.
>
> Some newer applications allow :port as a shortcut to a command line
> arg, but ssh does not.
>
> Jim

I never knew that Jim, thanks. What I do know is that for my local home
network, which currently has 6 to 8 machines on it, the ssh -Y name at host
just works.  So does file shareing by the use of a fuse mount usually
referred to as sshfs. As long as I stay within my "user" rights, it just
works.  Not colicky or pickity like cifs or nfs4.  So neither of those
file access things are running here. 2 less attack vectors exposed that
way.

Thanks Jim.

Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>


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

Subject: Digest Footer

_______________________________________________
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco


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

End of Coco Digest, Vol 177, Issue 76
*************************************