World: r3wp

Gettting an Access Error: Error opening socket listening port

using latest ubuntu

or is there a daytime server for ubuntu...I searched google but no 
luck.

I am having some issues running 276 rebview on the fractured Xandros 
that comes on an Asus Eee Netbook ... anyone else trying Rebol on 
an Eee (mine is just a linux Atom 900A)

I have put eeeBuntu on a LiveUSB (the base version was only about 
600 Mb ISO ) and may install that as my debian

There is also an eeeDora (Fedora) and an alternate debian (Easy Peasy 
aka Ubuntu-eee )

You are trying to listen on this port = running Time service from 
Rebol.

you should use something like open tcp://localhost:13

same access error

Have you checked no one else is using this port already?

netstat -tna

also try  iptables -L   if the port is not blocked

iptaables -L...
I do not see any mention of any blocked ports...

To use a port under 1024 in linux you have to be root

I'm trying to get the daytimer from xinetd running...

Not sure how . I see the daytime config file and turned of disabled 
and restarted xinetd but still can't readh it.

root!!! Good point...

I did notice something strange, though - enough failed attempts at 
opening a listening port, and rebol can't open any more.  Have to 
start a clean session

You are the man...Izkata

Got it up and running

I hate root

RobertS, I think most of us with the eee just reformat them and install 
windows xp

Graham, I'm assuming then that there are no driver issues when you 
do this?

Just download the drivers first

RobertS, I know two people using REBOL on Eee with Linux. What are 
your issues?

Graham, funny, I did the opposite, bought an eee Box, reformatted 
and installed Linux...

:-)

Gabriele, that's odd ... the linux versions are cheaper!  And i have 
quite a few spare XP licenses ...

It depends on which country you live in. Installing XP on it is not 
a simple task though - you need to PXE boot your installer.

The XP installer often has problems with USB-connected drives, in 
my experience. It's simpler to clean up the OEM XP install.

Booted fine with my USB DVD writer

Cool.

I recommend awxLink if you want to use it with XP - it's a lot easier 
than trying to get software to install on D itself.

G: there was no Linux version of the Box (notice, not eee PC, eee 
Box).

G: ahh.... never met anyone who bought one of those.  They already 
come with embedded linux, was that enough?  :)

wasn't ...

Two Linuxes is better than one :-)

That wasn't enough, that box needs to run a View program (and basically 
just that, though since now it's there it also runs Skype etc.). 
It was a replacement for a old (10 years old, and it was low spec 
back then) PC that literally exploded.

Capacitors ?

probably, it was the power supply. i didn't open it is there really 
was no point. the pc still works after replacing the power supply 
with one I had around, though i don't think it would last more than 
a couple months, and it's too old to be used for anything.

RIP

Syllable can probably raise it from the dead :-)

Those power supplies can make a rather loud bang with smoke etc :)

Kaj, possible, but I have no use for it at this point. The installed 
OS right now is Xubuntu, which is slow to boot etc. but once booted 
runs REBOL fine enough.

I normally don't install development tools on my production servers. 
I just install pre-compiled packages. This works good most of the 
time.

But how to handle source-only packages? I have an other system with 
everything on place. But how to do the install on the production 
server?

The makefiles won't run (because compiler versions etc. is checked) 
and deriving what to install where is not straight forward to derive 
from makefiles.

Any idea how to best do it?

What would be good to know is what new files are added during an 
installation. So maybe you could compile & install on your other 
system with development tools in place, then examine which files 
were added, then copy them to the production server.

To achieve the above you need to do 2 things:

1) Log files that were modified or added during the compile/installation 
(or otherwise find them after the installation).
2) Copy to the production server.

Well... yes, but that's quite heavy. But maybe the only way to handle 
it.