World: r3wp

Kaj, I have now all X libs installed. But I still don't get why Command 
requires them. It's plain cosole based no graphics. So why the X 
libs?

shebang: Luckly my Windows editor can handle files with mixed returns. 
So the first line is now unix style while all others are windows 
style.

I have one strange effect, that a Rebol script using a DLL works 
on Windows whereas on Linux I get a SEGVAULT.


How can I best track this down? I tried GDB but didn't made it to 
load rebol, include script, script etc. until I could start the whole 
thing.

Is there a "simple" way to get more information than just: SEGVAULT? 
Is it always a memory-problem?

Command/View needs X just like View does, even if you are just doing 
console stuff. Have you tried a Command build, or Core?

They use the X libs for font management in Draw, which can draw to 
in-memory image! values as well.

I just used command, not command/view. But OK I think it's the DRAW 
into-memory support.

Made it with GDB. ... Hacking around with the different path etc. 
solved it.

If I remember correctly, the console REBOL versions need the X11 
libraries for image manipulation

This is indeed an important issue when integrating with console Linux 
server versions

more specifically, X libs are needed for rendering text.

Gab, thanks for clearifying. BTW: Is this somewhere documented? I 
think its a quite importan piece of information.

It may be noted in the command docs, but I'm not sure.

Does REBOL work with Suse Linux? I can see Debian in the list, so 
I expect it to work with Ubuntu for e.g.?

I've had it working on OpenSuse

If it doesn't work on any Linux variety, it depends on the age of 
the Linux system (C) libraries

I think there is a list of needed lib files that some distros may 
not include in the basic install. I assume they can be added....

I need to restart cheyenne.  So, I login using ssh, and start Rebol 
and then cheyenne.  But once I close my shell down, Rebol also closes. 
 Anyone know how I can keep them running?

Graham, follow the command with an ampersand, like so:

rebol script.r &

man nohup

kcollins .. I tried that to detach the process, but it didn't seem 
to work.

That was the first thing that came to mind, but I'm playing around 
with a similar scenario and it doesn't work for me either.

I'm going to research nohup

there''s also disown (pid)

It looks like dtach can do what you need.

http://www.nslu2-linux.org/wiki/HowTo/KeepRemoteConsoleSessionRunning

have you tried it?

yes

I just learned about it and tried it

like this 
dtach -A /tmp/mydtachsocket -z bash

yes, then you can hit Control - \ to disconnect, and dtach -a /tmp/mydtachsocket 
to reconnect

oh .. no dtach ...

what distro do you have? Debian?

Opensuse 10.0

I haven't used that. Does it use yum as package manager?

yast

wow .. it has a text gui :)s

yast can't find it ...

you could build it from source...it's documented on that page I linked

found a rpm, and it's working.  Thanks!

I have a problem with a CRON job. Running it by hand works, but it 
looks like it's not working if run via CRON.

How can I write some message to the system logfile from inside a 
shell script? Is there a command for this?

http://www.cyberciti.biz/tips/howto-linux-unix-write-to-syslog.html

Graham: I have no problem launching Cheyenne from ssh. I'm always 
using the binary version : ./cheyenne &

Your binary doesn't work on OpenSuse.  I get encapsulation errors.

That's strange. Can you show me what : ldd cheyenne returns ?

Btw, did you tried with : rebol -qws cheyenne.r & ?

hang on ... I have to login via putty

hmm.  didn't give me any message via ssh
here's ldd 
http://screencast.com/t/MnsrSebIz