World: r3wp

Maybe try back-tick quoting:

ar rs mylib.a `ls *.o`

The quoted part is evaluated first by the shell.

Alternative to back-ticks that I find more readable (and also allows 
nesting if needed):

ar rs mylib.a $(ls *.o)

Or a multiline version using variables:

OUT=$(ls *.o)
ar rs mylib.a $OUT

Ah.. that's cool. Didn't new I could use $(...) for this.

Anton: it seems that more of the demos on Rebo/demos work with the 
deb file than the dl from rebol.com let me test more and get back 
to you

Alan, the binary packaged in rebol.deb is identical with the rebol-view-277-4-3 
download from rebol.com. (Which is the "Linux x86 Fedora" download.)

I suggest you this link: http://www.maxvessi.net/pmwiki/uploads/Main/rebol.deb
I added also the man page!

At the following link I put the Linux RPM package:  http://www.maxvessi.net/pmwiki/uploads/Main/rebol-2.7.7.4.3-5.i386.rpm

I'd suggest renaming the Debian package to also follow Debian package 
naming conventions.

i.e. rename it to rebol_2.7.7.4.3-4_i386.deb

it would further be nice, to get the dependencies right

I'll do the renaming, but it's a binary. What dependendies I should 
add?

libc6, libc6-i386, libfreetype6, libgcc1, libice6, libsm6, libstdc++6, 
libuuid1, libx11-6, libxau6, libxaw7, libxcb1, libxdmcp6, libxext6, 
libxmu6, libxpm4, libxt6, zlib1g

ignore the libc6-i386

so it should rather be:

libc6, libfreetype6, libgcc1, libice6, libsm6, libstdc++6, libuuid1, 
libx11-6, libxau6, libxaw7, libxcb1, libxdmcp6, libxext6, libxmu6, 
libxpm4, libxt6, zlib1g

Are you sure that all this it's necessary?

Yes.

Thats what is necessary to provide the dynamic libraries the REBOL/View 
binary depends on. (Except that I ignore transitive dependencies.)

Ok, I'll try.

libc6, libstdc++6, libx11-6, libxcb1, libxaw7, libfreetype6

is a more minimal set that will require the rest via transitive dependencies

Added menu integration! You can download from: http://www.maxvessi.net/pmwiki/pmwiki.php?n=Main.GuidaARebol
downloading the nname become the correct one.
I'll work on the dependencies next week.

Good work MaxV

Ok I added the dependencies.

Look at http://www.maxvessi.net/rebsite/Linux/

Very nice. The dependencies for the amd64 Debian package are wrong, 
though. As REBOL still is a 32-bit binary, you'll need to depend 
on the 32-bit compatibility libs.

So to correct this, a depends on "ia32-libs" should be sufficient 
for the amd64 package.

OK, I'll do, bt  my question is: "Is the Rebol binary compiled statically 
or dinamically?"

It is dynamically linked against all those libraries I listed as 
dependencies.

But don't take my word for it, do a ldd on the binary and see for 
yourself :)

Kubuntu 10.10 seems to have several worthwhile improvements so far. 
 For anyone virtualizing (K)ubuntu under VirtualBox, the 10.04 guest 
extensions don't work, but you can install ones that do work as package 
virtualbox-ose-guest-x11 ( See: http://www.unixmen.com/linux-tutorials/1157-install-guest-addition-in-ubuntu-1010-maverick-meerkat-fix
)

Reposted from other conversations... read-only root filesystem article: 
http://www.guciek.net/en/articles/read_only_root_filesystem

Process freezer that does not require root privileges, CryoPID... 
useful!  http://cryopid.berlios.de/

I just tried out "tiny linux core" (11 megs). Boots in seconds, installs 
in a minute (frugal), and runs rebol view out of the box....
Includes simple desktop...pretty cool

Great for kiosk/appliance devices running rebol apps

I thought one or more of you gurus would have some advice. I'm trying 
to back up a website via ftp to move all the files to another server. 
Some of the files have owner "apache" and won't let me move them. 
There are a lot of those files in various directories. Not being 
a linux guy, is there an easy way to chown a whole directory with 
subdirectories of files?

chown -R src dest 


and if you can use scp or rcp (depending on your setup) to copy your 
files over, it should be less hassle than ftp which often has many 
issues with stranger filenames and permissions.


on one server, for example, a file was created with ftp, which is 
a legal (albeit twisted) path, but it cannot be access or deleted 
from that same ftp access, because the path gets mangled when it 
goes through the url path parser of that ftp server.


also unless both source and destination ftp servers are the same, 
you can have other nasties.


its always best (and much faster) to gzip your whole directory and 
copy over one file, and then unpack it on the other server (you also 
get a free backup ;-)

ahh... ignore the dest argument... I got mixed up with rcp in my 
head  ;-)

also note that you should not use * when specifying folders with 
-R cause it *might* ignore "." folders and files.  (ex: .profile, 
.login, .svn, etc)

Thanks Maxim. I use Putty to access the server though I use it so 
infrequently that each time is like a new experience. I appreciate 
your help.

putty comes with an scp file xfer utility. I'd recommend using that 
instead of ftp... its really easy to use... just look in the docs 
everything is there.


this also has the advantage that you're not sending your password 
in clear text over the web (which ftp gladly does for you :-)

Thanks again. You make it sound like it's easy :-)

BTW, if I log in as root do you think I have to even worry about 
chowning?

some newer Linuxes have an improved security model which I don't 
reallly know anything about, but for simple file access within data 
directories, you will have no problems with root.

(as long as you're just doing things locally)

but remember that if you xfer files to another unix and the user/group 
ids don't exist, you will have to do a chown on the other system 
(unless everything runs as root then, hey who cares right ?  ;-)

I see, I hope the application doesn't care. Thanks. I'm checking 
it out right now.

obviously if possible *never* run services as root !

Oh, I mean if later the php app cares whether or not a file is owned 
by a different user.

yes, obviously, a chmod is also very important


chown -R   for data should work without problems and its a good thing 
to do.

Before mucking with a recursive chown, I would recursively list your 
files and save into a file, eg:
$ ls -lR > listedfiles
(that first option is a lowercase L ).

Then later if you are worried about having blasted some particular 
permissions, you just refer to listedfiles.

Thanks Anton. That's a wise move as well.

sorry if it sounds arch but altme for linux  is unreadable .... fonts 
are awfull