Re: Re: [colorforth] A request for CF code & data for the CF block server

["pattenre" <pattenre@xxxxxxxxxxx>]

Billy, I was refering to this:

Server development status is as follows:

The server has been up for several days now, I can access it from home, and
use it daily. At this point the server is not backed up, It is also not
populated. The plan at hand is to back this system up to a second cf machine
via the internet, this machine will then write the archive to ide disk. This
machine is in a seperate building from the server. I am starting this as my
next colorforth task. It should not cause in itself an interruption of
service. Until then local copies are a must to prevent data loss. Further
some small changes would be needed to support the access scheme mentioned
above. I will wait for feedback, and then implement the changes if any are
suggested. If none are suggested I will start with the scheme that I have
presented here. Please keep in mind that at the moment I need to choose for
something easy to implement. Later there will be a more robust access
system. This more robust system will take month's in total to finish due to
my busy schedule. I am looking for the best easy method until then. This
will allow others to gain the benefits of this server now. Some of these
advantages are subtle, but really helpfull. It has for me almost eliminated
the swapping of floppies. I use a standard client floppy and get/develop the
code from the server. It also allows me to write protect the floppy disk.
This makes crash recovery much better, the client will "always" reboot. The
code that caused the client crash will still be on the server to try
again...

With kind regards,

Tim Neitz.
rj_cf on #c4th IRCnet
tim@xxxxxxxxxxxxxx


----- Original Message -----
From: <wtanksleyjr@xxxxxxx>
To: <colorforth@xxxxxxxxxxxxxxxxxx>
Sent: Monday, June 23, 2003 8:52 AM
Subject: Re: Re: [colorforth] A request for CF code & data for the CF block
server


> From: "pattenre" <pattenre@xxxxxxxxxxx>
>
> >I would setup a 32 block private read write block area
> >for each user with the ability to publish finished blocks
> >in read only public portion of the disk.
>
> Is there some reason to do this? I mean, this is a lot more
> code than just letting people set up their own ColorForth
> servers.

This allows me to safely access Tim Neitz colorForth block server and
develop code with you and the public can see the stable code only. You and I
have access to 32 blocks and copy access to 32 public blocks via password on
our block zero. The remainder of block 0 is logging of IP and Time of you
and me accessing these blocks.
If I do not have the password for a block group, the server will ignore me
for 5 minuets.
This gives the server reasonable protection and our privacy with 1 block of
code running on the server.    If you know a avalible block groop and it's
password you can start using the block server now with out  administration
by the server oner.

Robert

>
> -Billy
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: colorforth-unsubscribe@xxxxxxxxxxxxxxxxxx
> For additional commands, e-mail: colorforth-help@xxxxxxxxxxxxxxxxxx
> Main web page - http://www.colorforth.com


---------------------------------------------------------------------
To unsubscribe, e-mail: colorforth-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: colorforth-help@xxxxxxxxxxxxxxxxxx
Main web page - http://www.colorforth.com