World: r3wp

That will depend on the still-to-be-revealed two licenses

I mean architecturally compatible: Dynamic linking with a clean integration 
interface.

Yes

I think that many ppl will be disappointed by licences. There's some 
hint already in Host related wiki document ... imo the licence will 
prevent R3 Clone DLL to work with host .... but I would be glad if 
it would not be so ...

Though that would be bad on principle, in practice we don't want 
to encourage cloning - it could lead to dividing the community. It's 
better to cooperate than to compete in this case. The main license 
restriction that would hurt us is anything that would prevent us 
from cloning the host code, since that is basically what every host 
code port is.

Clones are good if they don't fork the development effort. As long 
as clone code can be reintegrated into the original, cool.

the point of the host is not to start your own rebol, but to allow 
rebol to work in your stuff.  that, I think, should be emphasized 
within the documentation/web site when it will all be official and 
"a product".

going OT we are in syllable group, and I think now is not the time 
for a license debate.

To the contrary, it's extremely important to Syllable

The project almost exploded over it two years ago, and I've been 
in dire straits since

Wasn't Syllable derived from Atheos, which was GPL iirc? How did 
yo manage to switch to LGPL?

We didn't switch; it was always like this

When you say "LGPL", it will echo "GPL" in the heads of free software 
zealots and "evil" in the heads of anti free software zealots

I guess I didn't recall correctly. I remrmber that the original developer 
of Atheos used the GPL to prevent anyone from making commercial clones 
of his operating system, then abandoned it. Syllable was the result 
of that. I guess I remember wrong.

What he said was that he would abandon it in favour of BSD if the 
GPL zealots kept nagging him

ok, but part of the point for me is that the license isn't yet finalized 
and a direct discussion between you and Carl, is going to be much 
more effective at making the host suitable to your needs than us 
assuming and argumenting about it.


Contrary to what many might think, Carl is quite open to suggestions. 
  When the case and reasoning for it is founded and logical, he has 
rarely been, if ever, at odds with anything I've suggested.

Syllable was the result of him simply disappearing

So he relicensed as LGPL? Good for him :)

NO: it was always like this

That is what I meant by "abandoned".

Him disappearing.

There was NO LICENSE ABANDONMENT

No, project abandonment.

Does syllable run on ARM v5 instruction set?

The Syllable libraries are LGPL, so that it is a platform for all 
software. This includes GNU's C library

Ah, the libraries. That fits then.

The applications are GPL, because noone needs to build on them, anyway

When Ohloh analysed our code, it turned out we're predominantly LGPL. 
(While Haiku, which chose to be MIT, is predominantly GPL in practice)

And no, there is only Syllable for 32 bit Intel

what's the smallest server footprint in mb?

Well, the R3 host code license needs to allow LGPL licensed hosts 
- that is what I was talking about earlier. If there are restrictions 
in the host code license that would prevent that, it would be a problem 
for platforms like Syllable with LGPL libraries.

( shame ..all these plug computers which are being used as stealth 
servers are using ARM processors )

If you're talking about Syllable Server, that is 370 MB installed 
for the 0.3 version. It is currently growing, but I also did a test 
build for a stripped cloud server that was around 250 MB

And ram requirements?

How well does it treat NAND ?

Depends greatly on where you load it and what you run

On a 192 MB machine, it starts up using 13 MB. On a 768 MB machine, 
it uses 21 MB for itself

I'm running a number of websites on Cheyenne fairly comfortably within 
64 MB

What's the context for NAND?

Does it need to write to disk frequently?

I think I read somewhere that some of these linuces are optimized 
to reduce disk writes ...

Oh, flash. Syllable Desktop is very silent in terms of disk writes, 
and Server doesn't carry many more processes

It's just the standard system logging going on, but there's no specific 
support such as an SSD filesystem

Again, it will depend on what you install on it, but there are no 
gross background processes going on such as on other systems

Brian, yes, we need LGPL compatibility, but for even deeper reasons

Graham, I intend to port Server to ARM, but it's only a plan right 
now

I don't have an ARM based PC yet .. but that is going to be my next 
purchase :)

Tried to load syllable on virtualbox yesterday.  Does syllable support 
virtual clients?

Yes, did you download our VMware image?

VirtualBox is weird, though; it works less well than VMware and QEmu