World: r3wp

from this on, a -a once an hour via a cronjob would keep it in sync

I've put it in the startup script, before Fossil

No Cron, and I don't plan on adding it

msntp -x
 would make it run as a daemon

Does that have a configuration file, or how often does it adjust?

(so the full cmdline would be: msntp -x -v -a ntp1.nl.net)

that estimates clock drift and adapts accordingly

but does not check more often than every 5 hours

yikes, ignore the -v

msntp -x -a ntp1.nl.net

or "msntp -x 1440 -a ntp1.nl.net" to have it check no more than once 
daily

Hm, that didn't go down too well. Or actually, it did, because the 
server won't restart

msntp -x won't detach on it's own, so you'll have to use & or whatever 
your shell's (or startup script runner's) mechanism for backgrounding 
processes is

Yeah, I'm finding out

Cool, it runs now

Thanks, that's one item off my roadmap

you're welcome

The broader roadmap is to switch to SystemD. Then I can reclaim the 
memory that the msntp server takes

a meager ~800kB in this case :)

Yes, but a bit much for just looking at the clock every five hours

Fossil serves distributed versioned databases and it only has 500 
KB resident right now

what's wrong w the cron approach then. it would take up that 800kb 
for a fraction of a second every 5hr

SystemD is more advanced

On high holidays you may also spell it sØst‘md.
 :) the author seems to be pretty restrictive about the spelling

:-)

http://www.fm.tul.cz/~ladislav/rebol/nistclock.r

we have this script too. would it be hard to port the system/schemes/daytime 
to r3?

onetom - see https://github.com/gchiu/Rebol3/blob/master/protocols/prot-daytime.r

I think for daytime all you need to do is open a port on 13, read 
what is returned and close the port.

indeed, thx GrahamC

$ nc time-a.nist.gov 13

55676 11-04-25 16:30:36 50 0 0 433.9 UTC(NIST) *

Robert, you could do your presentation along the lines of my Boron 
presentation?

Good idea, do you have a link?

http://tryrebol.esperconsultancy.nl/Boron/

Show them HELP (?) and SOURCE, which are strong tools to get you 
going as a programmer.

As for R3 console, which is ugly, but has some helpfull features 
too:

 Chat - open DevBase developer forum/BBS
 Docs - open DocBase document wiki (web)
 Bugs - open CureCode bug database (web)
 Demo - run demo launcher (from rebol.com)
 Help - show built-in help information
 Upgrade - check for newer releases
 Changes - what's new about this version (web)

And how to build sentences from words and values without irritating 
syntax to get in the way.

The benefit from having so many datatypes, which make functions work 
in many ways depending on argument datatype. One good example, I 
think, is READ, but you can probably find others.

e.g. I always welcome the ability to check the changelog - nice addition 
with Changes.

Also:

>> 1 / 0
** Math error: attempt to divide by zero
** Where: /
** Near: / 0

>> why?
Opening web browser...

Is it really a good idea to go deep into R3, with the situation?

probably not, but why not outline the planned future? R3 is alpha, 
and it should be treated as such. R3 adds nice stuff - unicode, modules, 
control of boot sequence, devices, codecs, etc. Robert might face 
the questions of recent REBOL status anyway ....

is there any future? Maybe postapocalyptic world where the only way 
how to comunicate is face to face or using ham radios.

REBOL has fostered ideas in many people, and I'm sure, whose ideas 
will evolve into a future with better programming tools, than the 
world has today. So yes, I'll say there is a future.

I only have 6:40 mintues. So, I concentrate on REBOL as a language, 
not so much on R3 / R2 the products.

Devices, codecs? Where?

They are there, just not finished and optimal ...

Where?

There are just some traces of them as an internal implementation 
detail. There's nothing you can do with them

There are reasons that you don't see anybody writing extra devices 
and codecs

Kaj - I think  that you are not accurate, and that you even know 
it?. Codecs are useless, and even Carl later introduced the plan,of 
how to reimplement them. But devices? There is list of devices out 
there, no? http://www.rebol.net/wiki/DevicesThe other fact is, that 
those are not usable via extensions, but it does not mean the abstraction 
is not there?

Yes, they're there, as an implementation detail of the internal abstraction 
of R3. The only place where some devices are exported is in the host 
kit, but they're hardwired there. You can port those specific devices 
to other platforms, but other than that, there's nothing you can 
do with the abstraction

Robert, code, including gui's,  created by other code and then executed, 
is a great feature of Rebol.