World: r3wp

I was sudo ./cheyenne

So that's where you get encapsulation errors ?

yes, I think so.

It was 2 days ago and so I switched to using cheyenne.r instead

You can use Gab's workaround for that : write a small shell script 
that run cheyenne and run the script with sudo.

I will try ...

Gab says it causes the same problem on all unixes, but on ubuntu 
jeos, i don't get the encapsulation error.

maybe because you're logging as root ?

graham, you can also use "screen" if you want to be able to connect 
back and see the output. though, what you really need is just redirecting 
the input and output. rebol your-script.r >/dev/null </dev/null 2>/dev/null 
&

Tried again ...

./cheyenne - netstat says port 8001 is being listened, but I don't 
get any output using wget
sudo ./cheyenne - get the encapsulation error as you reported it
sudo rebol 
and then do %cheyenne.r works.

and wrapping it like ch.sh

#!/bin/sh 
./cheyenne &

sudo ./ch.sh

also works

not seeing this request to write a cofiguration file at present

I was installing ubuntu Jeos, and it seems to find the NICs, and 
gets the UTC time etc.  But when it starts up, ifconfig -a only shows 
the local loop adaptor.
And if I try and startup eth0, it says it doesn't exist.
Ideas?

Since Gutsy, the first couple of lines of /etc/iftab


# This file is no longer used and has been automatically replaced.

# See /etc/udev/rules.d/70-persistent-net.rules for more information.


The system for naming / managing eth0 eth1 has changed.  I had to 
mess a file in the path above to get my eth0 back.

oh gawd ...

Has anyone some experience with Truecrypt? I would like to fully 
encrypt my Linux system.

But  I don't want to get locked out ;-).

My experience of Truecrypt is that the code is excellent quality, 
and it has many well-engineered safeguards to prevent data loss.....But 
I've never used the Linux version, so I cannot vouch for that. Good 
luck!

Graham, why do you say JeOS finds your NICs? ifconfig not showing 
them would seem to indicate it doesn't

well, it says fetching time etc and doesn't say it can't find them

Also if I have two nics, it asks which one I want to use as the primary 
adaptor.

Does it fetch time through NTP or just from the system clock?

doesn't tell me

Also Iknow the nics work because I booted up in UBCD and was able 
to browse

Usually just the hardare clock. NTP must be configured later

One is a Via Rhine and the other a Realtek chipset

Sounds like it finds them on installation, but not afterwards. Odd

Yes exactly

Is the ip command available? That's the modern replacement for ifconfig

dunno

have no problems installing JeOS under vmware

Here's another JeOS annoyance .. I installed on a  Compaq PC with 
USB keyboard. It asked me about keyboard type etc ... and I think 
I manually selected USA.

But when it boots up, it doesn't recognize the keyboard anymore :(

So, I am going to have to reinstall, give it a fixed ip address so 
that I can ssh into it

As far as I know, there is no USB module in JeOS. JeOS is designed 
to be run inside a Virtual Machine, not as a Virtual Machine Host.

So, big oops .. should not have used JeOS.

It probably only works with virtual network cards too.

Or the real network cards that VM hosts emulate - that's how all 
of the VM hosts work.

Sad ...

I swapped for ubuntu server and that's fine.  No glitches.

What was the installed footprint of JeOS?

Can't remember .. wiped it now.

Anyone using Kubuntu 8.04 Hardy ?

I'm not having nice networking experiences since upgrading from Feisty 
to Gutsy.

Lots of timeouts, flaky domain name resolution seems to work only 
half the time...
(AltME is fine - it probably caches the ip address).

Connecting and using certain sites has often been really difficult, 
like ubuntu updates, ubuntuforums, my bank's online banking, and 
rebol.org, to name a few. Rebol.org I've noticed has been really 
slow.

Wait a minute, before the upgrade, I did a *hardware* upgrade, replacing 
the motherboard and 32-bit cpu for a 64-bit one. This is when 'eth0' 
changed to 'eth1' and I had to muck about to fix it.  <--- This is 
probably related to the network problems.
(So much happened since then, I keep forgetting about this.)
My solution is probably to do a fresh 64-bit install.

Anton, Rebol will not run on 64-bit Linux without some hacking.

Also, are you using wireless networking? I have a machine running 
Hardy and ended up needing ndiswrapper to get wireless working well. 
The following instructions worked for me: http://ubuntuforums.org/showthread.php?t=766560

kcollins, ahh... you mean: "Rebol runs on 64-bit Linux, with some 
hacking."  ;)  So what's the hacking ?

I haven't done it myself, but someone posted about it a while back...let 
me find the thread...

I'm not using wireless on my main machine, but my wireless networking 
experiences in linux have been abysmal ones so far. I didn't devote 
myself to it, though.

http://www.rebol.org/cgi-bin/cgiwrap/rebol/ml-topic-detail.r?l=0&topic={308227A880B92F1C4D34586C4B0C4BDEDFF1A8DA}