World: r3wp

Is there someone using postfix under debian? I lost my /etc/init.d/postfix 
script I cannot find it anywhere... without the script I cannot even 
reinstall postfix:/

Can't reinstall or can't reconfigure?

Can't do nothing as everything stops on trying to stop the service 
using the script which does not exists

also    apt-get install postfix   stops on trying to run the script.

Was that the original script or did you modify it?

original

Then you can probably get it out of one of the original packages, 
such as here:

http://ftp.de.debian.org/debian/pool/main/p/postfix/

Interesting catch 22, by the way

It's the only init script in the .deb packages

thanks.. I found it there:)

Did you manage to unpack it?

I downloaded tar.gz

Oh, the source. It's probably not a problem here, but it's a bit 
dangerous because the source file may need processing

I just found out that the .deb distribution packages are in a weird 
format: ancient ar format which contains a few .tar.gz files

hm... I still have problems.. the file is missing LSB information 
:/

it's probably wrong file.

Try the .deb package that is closest to your Postfix version and 
Debian version

Unpack it with ar similar to how tar works

yes.. this one looks better :)

has anyone written syntax hilighter for Gedit? (Default Gnome Editor)? 
I don't need it, but my friend who starts using REBOL asked, and 
I am not following this topic properly. So - in case you know someone 
who has it, please suggest :-)

Is anyone familiar with the debootstrap process? I used it to setup 
a Lenny that I can use via CHROOT, which works. Now I want to make 
it bootable. I added it to GRUB and can boot into the version. But 
I can't get the network up & running.

I have spend most of the day to find out how to setup a network. 
I have done most things:
- /etc/networks/interfaces has an entry for eth0
- /etc/networks strangly only contains if-up.d/

- I'm somehow missing /etc/init.d/networking but don't know how to 
install it or why it's missing

The eth0 interface is there but has no IP address assigned, and route 
-n is empty.

IMO there is not a lot missing but I don't know how to fix it.

Sounds like half the infrastructure is missing. It's no wonder it 
doesn't work

you need to chroot and install more packages, I guess. you need to 
do an actual installation, and not just a bootstrap.

alternatively, you can configure the network manually :-)

On the Free Software Foundation site I read about gNewSense linux 
based on Debian. The gNewSense Laptop and Netbook Guide 
http://wiki.gnewsense.org/Main/LaptopGuide#toc1

lists a laptop, the Lemote YeeLoong
http://www.tekmote.nl

Has anyone seen or tried this laptop?

Only read about it. They're among the lowest-end netbooks, but interesting

can anyone tell me why... on linux... (running debian) everytime 
I launch rebol, I get two processes?

 3156  3156  3016 pts/1    00:00:00           rebbase
 3157  3156  3016 pts/1    00:00:00             rebbase

one is parent of the other.


this happens no matter what rebol I launch... command, core or  view.

dns

it's the dns helper process.

rebol forks to be able to use gethostbyname() asynchronously (dns:///async)

Does anyone have a solution to run encapped 2.7.6 View on Ubuntu 
9.04 or 9.10? I'm stuck with our new server, Cheyenne binary (with 
built-in View) requires libstdc++.so.5 which is obsolete. Making 
a symlink to .so.6 doesn't work.

obsolete: can't Ubuntu tell the difference between the two libraries 
and keep both?

I've found the Debian package for libstdc++.so.5 but it needs an 
older version of gcc (3.3) that I can't manage to install on 9.04 
without messing up the system.

interesting

I'm not able to get a correct installation of libstdc++.so.5 deb 
package, it messes up the gcc lib dependencies.

Maybe I should really drop View support completly in Cheyenne.

I do think that it would make cheyenne installation much easier.

I guess that a 2.7.7 SDK should have cured that, View 2.7.7 seems 
to link to .so.6.

I've always thought that a gfx engine built in Cheyenne would have 
brought a nice added value, but it seems that using View is just 
too much trouble on anything else than Windows.

Send Carl a priority feedback ...

for windows it's very nice to have a taskbar icon and all, but when 
you run on server I want no view.. I have just command line on all 
servers anyways

so how do you interact with running servers?

browser interface?

I don't interact.. are there any interaction possible (I know for 
reload config and restart workers on windows)

My intent with providing a View kernel for Cheyenne was to use it 
as a general purpose image generation library. But as it fails to 
accomplish the most basic job of making decent thumbnails, and is 
quite painfull to run when the required dependencies are not satisfied, 
it's maybe better to get rid of it.

are there any interaction possible (I know for reload config and 
restart workers on windows)

 Similar interactions are possible on all platforms. For non-Windows 
 systems, use signals :
- reload config: kill -HUP <cheyenne-pid>
- reset workers: kill -USR1 <cheyenne-pid>
- quit: kill <cheyenne-pid> (or CTRL-C if running in foreground)