We do it even without conversion to .deb. We just use rpm on Debian.
Here is the script that takes care of all the dependencies and
differences between RH and Debian. Also the script can be used on either
RedHat or Debian systems. It requires lgtoclnt, lgtoman packages and
rw.cln script. Very simple and works ok for us.


SERVER=your_backup_server
export PATH=/sbin:/usr/sbin:$PATH
[ ! -f /etc/redhat-release ] && mkdir -p /etc/X11/app-defaults &&
apt-get install rpm && mkdir /var/lib/rpm
rpm -ihv --nodeps lgt*
[ -f /etc/redhat-release ] || ln -s /etc/init.d/networker
/etc/rc2.d/S95networker
echo $SERVER >>/nsr/res/servers
[ -x /etc/rc2.d/S95networker ] && /etc/rc2.d/S95networker start && exit
[ -x /etc/rc.d/rc3.d/S95networker ] && /etc/rc.d/rc3.d/S95networker
start && exit
[ -x /etc/rc3.d/S95networker ] && /etc/rc3.d/S95networker start && exit



Matt Temple wrote:

Yes, we absolutely do run the client from Debian.   (I don't know about
the server -- never had the nerve to try that!)   With RedHat now
forking
its offerings to fedora.redhat.com and RedHat enterprise Linux, and with
SUSE being bought by Novell ..... we're in a bit of a quandry.


If I remember correctly, what we did first was to run "alien" on the
rpms to make the debian packages.   Then, installed the Debian
packages.   (I think there's an rpm2cpio package that might work as
well.

I made a few changes to the startup script for use with debian.   The
whole "status" thing is obviously only useful when we started networker.
If it dies, the pid file will still be around.
                                                       mht
==============================/etc/init.d/networker============
#!/bin/sh
#
# Copyright (c) 2000 by Feral Software
# All rights Reserved
#
# chkconfig: 345 91 35
# description:  This shell script takes care of starting and stopping
#               networker clients for RedHat based Linux machines.
#
# networker     This shell script takes care of starting and stopping
#               networker clients for RedHat based Linux machines.
#
# note that this will have to change if a server (nsrd) is added.
#
# modified from original by mht for use with Debian system.
# --- these are Red Hat -- don't use --Source function library.
#. /etc/rc.d/init.d/functions
#
# Source networking configuration.
#. /etc/sysconfig/network

# Check that networking is up.
#[ ${NETWORKING} = "no" ] && exit 0
#
# --- these are redhat -- end

PIDFILE=/var/run/networker.pid

NSRDIR=/usr/sbin
NAME=nsrexecd
DAEMON=$NSRDIR/$NAME
ARGS="-s tapes"
[ -f ${DAEMON} ] || exit 0

# See how we were called.
case "$1" in
  start)
        # Start daemons.
                          echo -n "Starting networker: "
                                  start-stop-daemon --start --quiet
--pidfile $PIDFILE -m --exec ${DAEMON}
                                  ;;
  stop)
        # Stop daemons.
        echo -n "Shutting down networker: "
        start-stop-daemon --stop --quiet --name $NAME --oknodo --exec
${DAEMON}
        rm -f $PIDFILE
        echo
        ;;
  status)
        # look for PID file
        if [ -f $PIDFILE ]; then
                echo  "<$NAME> appears to be running"
        else
                echo  "<$NAME> does NOT appear to be running"

                                           fi
        ;;
  *)
        echo "Usage: networker {start|stop|status}"
        exit 1
esac


==============================
On Tuesday, Nov 4, 2003, at 12:32 US/Eastern, Paul Brears wrote:

I know it's not on the approved list for Legato NetWorker but have any
readers of this list had any
experience using Debian as a NetWorker client?

I'd really appreciate any information, either success stories or any
likely problems.



There are some Debian mailing list entries saying it should work
although most seem to mention
rather old versions of NetWorker.



Paul

--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

========================================================
Matthew Temple                Tel:    617/632-2597
Director, Research Computing  Fax:    617/632-4012
Dana-Farber Cancer Inst       mht AT research.dfci.harvard DOT edu
44 Binney Street,  M L105     http://research.dfci.harvard.edu
Boston, MA 02115              Choice is the Choice!

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Yuri Pismerov, Sr. System Administrator,
TUCOWS.COM INC. (416) 535-0123  ext. 1352

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=