devil-linux-discuss — General Mailing List for all discussions

Re: [Devil-Linux-discuss] Automatic NFS mounts

[Bruce S. <bw...@ar...>]

> > Are there any other scripts that should "require" the nfs script first?
> 
> As long as the init script is started in the right order, nothing. ;-)

I guess we'll find out what's in the wrong order after we release it! :)

> >> If you're going to make it easier to do NFS mounts, you should
> >> also consider making it easier to create mount points in a logical place.
> >>
> >>
> >> Unless I'm missing something, it doesn't appear that you can
> >> create new directories under /mnt since the filesystem is read only.
> >> Perhaps /mnt should be made a link to /shm/mnt,
> >> like /etc and /var, to allow new directories to be created under /mnt.
> >
> > That is probably a good idea, but what is that going to break?
> > Do any of the standard scripts make use of /mnt now?
> > (save-config? -- appears NOT to use /mnt, but what else?)

My searching for "/mnt" only found:  initrdtree/mount_cdrom
that needs to be changed to another mount point.

Can you think of anything else?

 - BS

Re: [Devil-Linux-discuss] Automatic NFS mounts

[Heiko Z. <he...@zu...>]

On Fri, October 6, 2006 12:49, Bruce Smith wrote:
>>> We could start portmap and mount.nfs right after the network, before
>>> anything else starts. You'll need to modify the inserv config file, I
>>> think we had that in build/scripts/config/
>
> OK, I added a /etc/init.d/nfs script for NFS mounts in /etc/fstab.
> The script also does a mkdir on all the directories before the mount,
> just in case they don't exist.
>
> I'm not sure what you wanted me to change in the insserv.conf file.
>
>
> Are there any other scripts that should "require" the nfs script first?

As long as the init script is started in the right order, nothing. ;-)

>> If you're going to make it easier to do NFS mounts, you should
>> also consider making it easier to create mount points in a logical place.
>>
>>
>> Unless I'm missing something, it doesn't appear that you can
>> create new directories under /mnt since the filesystem is read only.
>> Perhaps /mnt should be made a link to /shm/mnt,
>> like /etc and /var, to allow new directories to be created under /mnt.
>
> That is probably a good idea, but what is that going to break?
> Do any of the standard scripts make use of /mnt now?
> (save-config? -- appears NOT to use /mnt, but what else?)
>
>
> BTW, I ran a little test mounting a directory that is really a symlink
> to another directory, and it seems to work fine.
>
> - BS
>
>
>
>
> -------------------------------------------------------------------------
>  Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your opinions on IT & business topics through brief surveys -- and earn
> cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>  _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
>


-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-Linux-discuss] Automatic NFS mounts

[Bruce S. <bw...@ar...>]

> > We could start portmap and mount.nfs right after the network, before
> > anything else starts.
> > You'll need to modify the inserv config file, I think we had that in
> > build/scripts/config/

OK, I added a /etc/init.d/nfs script for NFS mounts in /etc/fstab.
The script also does a mkdir on all the directories before the mount,
just in case they don't exist.

I'm not sure what you wanted me to change in the insserv.conf file.

Are there any other scripts that should "require" the nfs script first?

> If you're going to make it easier to do NFS mounts, you should
> also consider making it easier to create mount points in a
> logical place.
> 
> Unless I'm missing something, it doesn't appear that you can
> create new directories under /mnt since the filesystem is
> read only. Perhaps /mnt should be made a link to /shm/mnt,
> like /etc and /var, to allow new directories to be created
> under /mnt.

That is probably a good idea, but what is that going to break?
Do any of the standard scripts make use of /mnt now?  
(save-config? -- appears NOT to use /mnt, but what else?)

BTW, I ran a little test mounting a directory that is really a symlink
to another directory, and it seems to work fine.

 - BS

Re: [Devil-Linux-discuss] dhcpd.conf: fixed-address not working

[Bruce S. <bw...@ar...>]

> > I just installed devil-linux-1.2.10 and have three problems.
> >
> > 1. The documentation says that specific hosts can be given a specific IP
> > number like in the following example: host murauer { hardware ethernet
> > 00:30:65:6F:A5:D4;
> > fixed-address 192.168.1.5; }
> >
> > Unfortunately, it doesn't work for for me. Is there anything else I need
> > to pay attention to?
> 
> This is probably more a question for the dhcpd folks: http://www.isc.org

I've used static MAC->IP maps in the DL DHCP server for a long time and
have never had a problem.

You may need to force your client to renew it's lease (sometimes
rebooting isn't enough).  Or you have a mistake in your dhcpd.conf file.

 - BS

[Devil-Linux-discuss] UDP broadcast rebroadcast

[Moray M. <mmc...@ox...>]

I need a software solution to run on a DL box to take UDP packets
broadcast on a subnet attached to one NIC, and rebroadcast them on
another subnet attached to another NIC, preferably without changing the
source address. I didn't allow enough time for this, so I need to figure
it out soon.

So I wondered if anyone had any experience of doing this, and if so what
they used? I've heard some Cisco hardware can do this trick.

And secondly, if anyone had a little time could they compile this UDP
broadcast relay software I found for DL 1.2.10? The software could be
found at=20

http://www.joachim-breitner.de/udp-broadcast-relay/files/udp-broadcast-r
elay-0.3.tar.gz=20

I don't have time to set up a development box which can compile things
for the right kernel in the timescale I need a solution by :-<

Yours,
Moray
-------------------------------------=20
Moray McConnachie
IS Manager        +44 1865 261 600
Oxford Analytica  http://www.oxan.com

Re: [Devil-Linux-discuss] dhcpd.conf: fixed-address not working

[Heiko Z. <he...@zu...>]

On Mon, October 2, 2006 09:30, Gürsoy Turan wrote:
> I just installed devil-linux-1.2.10 and have three problems.
>
>
> 1. The documentation says that specific hosts can be given a specific IP
> number like in the following example: host murauer { hardware ethernet
> 00:30:65:6F:A5:D4;
> fixed-address 192.168.1.5; }
>
>
> Unfortunately, it doesn't work for for me. Is there anything else I need
> to pay attention to?

This is probably more a question for the dhcpd folks: http://www.isc.org

> 2. The command "save-config" does not save onto the floppy disk. After
> doing changes in the configurations, I have to tar the "etc" folder and
> mcopy the resulting archive to the floppy, manually. Why would this be the
> case?

Do you have any error messages?
What's the output of save-config?
Anything in the syslog?

> 3. At startup, it takes a long time searching for RAID devices, but I
> don't have any. How can I stop it from doing so?
>
>
> Any help is greatly appreciated.

You can't turn this off.
This must be related to your hardware configuration. What hardware are you
using in your DL box?
On my boxes this doesn't even take 1 second.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-Linux-discuss] dhcpd.conf: fixed-address not working

[Zsolt Z. <zsz...@gm...>]

1. Did you create a subnet section in your dhcpd.conf file or yust
remove #s from the example?
Did you checked /var/log/messages logfile about dhcpd messages?
You have to restart the service after changing dhcpd.conf file to take effe=
ct.

There is not too much info to help solve your problem.

2. Is there any output of your save-config?

Rgds, Zsolt

On 10/2/06, G=FCrsoy Turan <gur...@iy...> wrote:
> I just installed devil-linux-1.2.10 and have three problems.
>
> 1. The documentation says that specific hosts can be given a specific IP
> number like in the following example:
>           host murauer {
>               hardware ethernet 00:30:65:6F:A5:D4;
>               fixed-address 192.168.1.5;
>           }
>
> Unfortunately, it doesn't work for for me. Is there anything else I need =
to
> pay attention to?
>
> 2. The command "save-config" does not save onto the floppy disk. After do=
ing
> changes in the configurations, I have to tar the "etc" folder and mcopy t=
he
> resulting archive to the floppy, manually. Why would this be the case?
>
> 3. At startup, it takes a long time searching for RAID devices, but I don=
't
> have any. How can I stop it from doing so?
>
>
> Any help is greatly appreciated.
> GT.
>

[Devil-Linux-discuss] dhcpd.conf: fixed-address not working

[<gur...@iy...>]

I just installed devil-linux-1.2.10 and have three problems.

1. The documentation says that specific hosts can be given a specific IP 
number like in the following example:
          host murauer {
              hardware ethernet 00:30:65:6F:A5:D4;
              fixed-address 192.168.1.5;
          }

Unfortunately, it doesn't work for for me. Is there anything else I need to 
pay attention to?

2. The command "save-config" does not save onto the floppy disk. After doing 
changes in the configurations, I have to tar the "etc" folder and mcopy the 
resulting archive to the floppy, manually. Why would this be the case?

3. At startup, it takes a long time searching for RAID devices, but I don't 
have any. How can I stop it from doing so?


Any help is greatly appreciated.
GT.

Re: [Devil-Linux-discuss] Automatic NFS mounts

[<sa...@pe...>]

Heiko Zuerker wrote on 09/26/2006 03:55:26 PM:
> We could start portmap and mount.nfs right after the network, before
> anything else starts.
> You'll need to modify the inserv config file, I think we had that in
> build/scripts/config/

If you're going to make it easier to do NFS mounts, you should
also consider making it easier to create mount points in a
logical place.

Unless I'm missing something, it doesn't appear that you can
create new directories under /mnt since the filesystem is
read only. Perhaps /mnt should be made a link to /shm/mnt,
like /etc and /var, to allow new directories to be created
under /mnt.

I guess putting the mkdir commands, to create mount points, in
/etc/init.d/boot.local (as I have done) is ok, unless you want
a more dedicated way to do this.

--
Scott Allen

Re: [Devil-Linux-discuss] Automatic NFS mounts

[Heiko Z. <he...@zu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Tue, September 26, 2006 14:50, Bruce Smith wrote:
>> On Tue, September 26, 2006 09:52, Bruce Smith wrote:
>>
>>> Wouldn't it be simpler and more standard to simply start portmap
>>> before the /etc/fstab mounts?  That would allow people to put NFS
>>> mounts in /etc/fstab, as other distros do it.
>>>
>>
>> Agreed.
>> Do you have time to implement it?
>>
>
> After looking at it, that's not going to work.  mountfs runs before
> networking has started.
>
> I suppose we could hack up /etc/init.d/portmap to mount NFS volumes,
> but I'm not sure that's a good idea.
>
> Looking at my SuSE desktop, they have a separate start script for NFS
> mounts.  It looks like that's the way to go.
>
> Thoughts?

That's probably the best way and we know it'll work this way.
We could start portmap and mount.nfs right after the network, before
anything else starts.
You'll need to modify the inserv config file, I think we had that in
build/scripts/config/

- -- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iEYEARECAAYFAkUZha4ACgkQUcytMSbs+YWh5ACgl1UcPdmsYP2KxmP/8scsebH9
lowAn2zVwGTQ533CXndqgKHtXi2/AJUf
=nZQ9
-----END PGP SIGNATURE-----

Re: [Devil-Linux-discuss] Automatic NFS mounts

[Bruce S. <bw...@ar...>]

> On Tue, September 26, 2006 09:52, Bruce Smith wrote:
> > Wouldn't it be simpler and more standard to simply start portmap before
> > the /etc/fstab mounts?  That would allow people to put NFS mounts in
> > /etc/fstab, as other distros do it.
> 
> Agreed.
> Do you have time to implement it?

After looking at it, that's not going to work.  mountfs runs before
networking has started.

I suppose we could hack up /etc/init.d/portmap to mount NFS volumes, 
but I'm not sure that's a good idea.  

Looking at my SuSE desktop, they have a separate start script for NFS
mounts.  It looks like that's the way to go.

Thoughts?

 - BS

Re: [Devil-Linux-discuss] Automatic NFS mounts

[Heiko Z. <he...@zu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Tue, September 26, 2006 09:52, Bruce Smith wrote:
> Wouldn't it be simpler and more standard to simply start portmap before
> the /etc/fstab mounts?  That would allow people to put NFS mounts in
> /etc/fstab, as other distros do it.

Agreed.
Do you have time to implement it?

- -- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iEYEARECAAYFAkUZeT8ACgkQUcytMSbs+YUbzgCeLTQCNVTek+vGtpm5mnDexDjT
MR8AnjhSlyumQf0YzN07HZOtoToPUaHz
=qknL
-----END PGP SIGNATURE-----

Re: [Devil-Linux-discuss] Automatic NFS mounts

[Bruce S. <bw...@ar...>]

Wouldn't it be simpler and more standard to simply start portmap before
the /etc/fstab mounts?  That would allow people to put NFS mounts
in /etc/fstab, as other distros do it.

 - BS


> Heiko Zuerker wrote on 09/25/2006 09:13:28 PM:
> > just a quick answer, since I don't have much time.
> > Your best bet is to copy the script /etc/init.d/skeleton and add
> your
> > commands there.
> > As you already suspected, add the script with insserv to the boot
> order.
> >
> > Of course don't forgett to run a save-config before you reboot. ;-)
> 
> Thanks for the reply, Heiko.
> 
> It appears that this isn't quite enough to get a service running in
> DL.
> In addition to creating a script based on skeleton (which I called
> nfsmount)
> and installing it using insserv, I found I also had to add the
> following
> lines to /etc/sysconfig/config
> 
> # Mount NFS directories specified in fstab?
> START_NFSMOUNT=no
> 
> The NFSMOUNT service will then be listed in the Services section of
> the setup command. You can then enable it and it will take effect.
> 
> I've included the contents of the /etc/init.d/nfsmount file that I
> created, in case it can be of use to anyone. Permissions for this file
> should be set to -rwx------ as with other service scripts.
> 
> ---- Cut here: start /etc/init.d/nfsmount ---------------------------
> #!/bin/bash
> #
> 
> ### BEGIN INIT INFO
> # Provides:       NFS mounting
> # Required-Start: $network $syslog $named portmap
> # Required-Stop:  $network $syslog $named portmap
> # Default-Start:  3 5
> # Default-Stop:   6 0
> # Description:    Mount NFS entries in /etc/fstab
> ### END INIT INFO
> 
> # settings
> source /etc/sysconfig/config
> 
> # parameters
> NAME="NFS directories"
> CONFIGNAME=NFSMOUNT
> MOUNT_PROG=/bin/mount
> UMOUNT_PROG=/bin/umount
> PARAMETER="-a -t nfs"
> 
> # source function library
> source /etc/init.d/functions
> 
> eval START=\$START_$CONFIGNAME
> 
> # Determine the base and follow a runlevel link name.
> base=${0##*/}
> link=${base#*[SK][0-9][0-9]}
> 
> # Force execution if not called by a runlevel directory.
> test $link = $base && START=yes
> test "$START" = "yes" || exit 0
> 
> case "$1" in
> start)
> echo -n "Mounting $NAME: "
> $MOUNT_PROG $PARAMETER
> evaluate_retval
> ;;
> stop)
> echo -n "Unmounting $NAME: "
> $UMOUNT_PROG $PARAMETER
> evaluate_retval
> ;;
> restart)
> $0 stop
> sleep 1
> $0 start
> ;;
> *)
> echo "Usage: $0 {start|stop|restart}"
> exit 1
> ;;
> esac
> ---- Cut here: end /etc/init.d/nfsmount ----------------------------
> 
> -- 
> Scott A.

Re: [Devil-Linux-discuss] Automatic NFS mounts

[<sa...@pe...>]

Heiko Zuerker wrote on 09/25/2006 09:13:28 PM:
> just a quick answer, since I don't have much time.
> Your best bet is to copy the script /etc/init.d/skeleton and add your
> commands there.
> As you already suspected, add the script with insserv to the boot order.
>
> Of course don't forgett to run a save-config before you reboot. ;-)

Thanks for the reply, Heiko.

It appears that this isn't quite enough to get a service running in DL.
In addition to creating a script based on skeleton (which I called
nfsmount)
and installing it using insserv, I found I also had to add the following
lines to /etc/sysconfig/config

# Mount NFS directories specified in fstab?
START_NFSMOUNT=no

The NFSMOUNT service will then be listed in the Services section of
the setup command. You can then enable it and it will take effect.

I've included the contents of the /etc/init.d/nfsmount file that I
created, in case it can be of use to anyone. Permissions for this file
should be set to -rwx------ as with other service scripts.

---- Cut here: start /etc/init.d/nfsmount ---------------------------
#!/bin/bash
#

### BEGIN INIT INFO
# Provides:       NFS mounting
# Required-Start: $network $syslog $named portmap
# Required-Stop:  $network $syslog $named portmap
# Default-Start:  3 5
# Default-Stop:   6 0
# Description:    Mount NFS entries in /etc/fstab
### END INIT INFO

# settings
source /etc/sysconfig/config

# parameters
NAME="NFS directories"
CONFIGNAME=NFSMOUNT
MOUNT_PROG=/bin/mount
UMOUNT_PROG=/bin/umount
PARAMETER="-a -t nfs"

# source function library
source /etc/init.d/functions

eval START=\$START_$CONFIGNAME

# Determine the base and follow a runlevel link name.
base=${0##*/}
link=${base#*[SK][0-9][0-9]}

# Force execution if not called by a runlevel directory.
test $link = $base && START=yes
test "$START" = "yes" || exit 0

case "$1" in
      start)
            echo -n "Mounting $NAME: "
            $MOUNT_PROG $PARAMETER
            evaluate_retval
            ;;
      stop)
            echo -n "Unmounting $NAME: "
            $UMOUNT_PROG $PARAMETER
            evaluate_retval
            ;;
      restart)
            $0 stop
            sleep 1
            $0 start
            ;;
      *)
            echo "Usage: $0 {start|stop|restart}"
            exit 1
            ;;
esac
---- Cut here: end /etc/init.d/nfsmount ----------------------------

--
Scott A.

Re: [Devil-Linux-discuss] Error compiling LPRng

[Heiko Z. <he...@zu...>]

On Tue, September 26, 2006 08:34, Devil-Linux wrote:
> I am compiling 1.2... atleast I thought so...
>
>
> I am not aware of anything other than enabling IPTraf, but I have
> compiled using this config file before.
>

Sometimes you have to completely start over ( I do that on a regular basis).
Wipe out the lfssystem and extract a new copy.
Then do the compile with a "make mrproper", to wipe out everything within
the build/tmp directory.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-Linux-discuss] Error compiling LPRng

[Devil-Linux <dev...@js...>]

I am compiling 1.2... atleast I thought so...

I am not aware of anything other than enabling IPTraf, but I have compiled 
using this config file before.

CONFIG_ALSA=n
CONFIG_APCUPSD=y
CONFIG_ARPWATCH=y
CONFIG_BINUTILS=y
CONFIG_BOOT_OPTION_VGA=800x600
CONFIG_BRIDGE_UTILS=y
CONFIG_CAMSOURCE=y
CONFIG_CDRTOOLS_ON_CD=y
CONFIG_CIPE=y
CONFIG_CLAMAV=y
CONFIG_CLAMAV_PATCH=y
CONFIG_CPQARRAYD=y
CONFIG_CPU=686
CONFIG_CRON=y
CONFIG_CVS=y
CONFIG_CYRUS_IMAPD=y
CONFIG_CYRUS_SASL=y
CONFIG_DAEMONTOOLS=y
CONFIG_DANSGUARDIAN=y
CONFIG_DANTE=y
CONFIG_DDUP=y
CONFIG_DEVIL_DOC_ISO=y
CONFIG_DEVIL_MAN_ISO=y
CONFIG_DISABLELOGGING=n
CONFIG_DISTCCD=y
CONFIG_DJBDNS=y
CONFIG_DNSMASQ=y
CONFIG_DOSFSTOOLS=y
CONFIG_DOVECOT=y
CONFIG_DVDRWTOOLS=y
CONFIG_EAGLE_USB=y
CONFIG_EBTABLES=y
CONFIG_ENBD=y
CONFIG_ETHTOOL=y
CONFIG_EZ_IPUPDATE=y
CONFIG_FETCHMAIL=y
CONFIG_FILE=y
CONFIG_FREERADIUS=y
CONFIG_FREETYPE=y
CONFIG_FROX=y
CONFIG_FWLOGWATCH=y
CONFIG_GCC3=y
CONFIG_GCC_ET_DYN=y
CONFIG_GCC_PIE=y
CONFIG_GCC_STACK_PROTECTOR=y
CONFIG_GPM=y
CONFIG_GRSECURITY=y
CONFIG_HEARTBEAT=y
CONFIG_HIGHMEM=y
CONFIG_HOSTAP=y
CONFIG_HOSTAPD=y
CONFIG_HOSTAP_DRIVER=y
CONFIG_HOSTAP_UTILS=y
CONFIG_HOTPLUG=y
CONFIG_HTTPD=y
CONFIG_IANS=y
CONFIG_ID3=y
CONFIG_IMAGEMAGICK=y
CONFIG_INITRD_FS=CRAMFS
CONFIG_IPAC_NG=y
CONFIG_IPROUTE2=y
CONFIG_IPTRAF=y
CONFIG_ISAPNPTOOLS=y
CONFIG_ISC_BIND=y
CONFIG_ISC_DHCP=y
CONFIG_JFS=y
CONFIG_JFTPGW=y
CONFIG_JOE=y
CONFIG_KERBEROS5=y
CONFIG_KERNEL_CPU=686
CONFIG_L2TPD=y
CONFIG_LCD4LINUX=y
CONFIG_LFTP=y
CONFIG_LHA=y
CONFIG_LIBSAFE=y
CONFIG_LIBSTDC_COMPAT=y
CONFIG_LINUX_NR_CPUS=4
CONFIG_LINUX_SMP=y
CONFIG_LINUX_VERSION=2.4
CONFIG_LINUX_WLAN_NG=y
CONFIG_LM_SENSORS=y
CONFIG_LOGROTATE=y
CONFIG_LPRNG=y
CONFIG_LVM=y
CONFIG_LYNX=y
CONFIG_MAIL_SPAMASSASSIN=y
CONFIG_MC=y
CONFIG_MDADM=n
CONFIG_MEMTEST86=y
CONFIG_MGETTY=y
CONFIG_MINICOM=y
CONFIG_MOTION=y
CONFIG_MOXIO_SMARTIO=y
CONFIG_MPEG_ENCODE=y
CONFIG_MRTG=y
CONFIG_MTOOLS=y
CONFIG_MTR=y
CONFIG_MT_ST=y
CONFIG_MYSQL_CLIENT=y
CONFIG_MYSQL_SERVER=y
CONFIG_NAIL=y
CONFIG_NCFTP=y
CONFIG_NETACCT=y
CONFIG_NET_SNMP=y
CONFIG_NF_BASE=y
CONFIG_NF_EXTRA=y
CONFIG_NF_LAYER7=y
CONFIG_NF_PATCHES=y
CONFIG_NF_PENDING=y
CONFIG_NFS=y
CONFIG_NFSD=y
CONFIG_NF_UPDATES=y
CONFIG_NICE=y
CONFIG_NIS=y
CONFIG_NO_IP_UPDATER=y
CONFIG_NSSLDAPLIB=y
CONFIG_NTOP=y
CONFIG_NTP=y
CONFIG_OIDENTD=y
CONFIG_OPENH323=y
CONFIG_OPENH323GK=y
CONFIG_OPENLDAP_FULL=y
CONFIG_OPENLDAPLIB=y
CONFIG_OPENSSH=y
CONFIG_OPENSSL_BIN=y
CONFIG_OPENVPN=y
CONFIG_PASSWDGEN=y
CONFIG_PCIUTILS=y
CONFIG_PCMCIA_CS=y
CONFIG_PERL=y
CONFIG_PHP=y
CONFIG_PMAKE=4
CONFIG_POPTOP=y
CONFIG_PORTMAP=y
CONFIG_PORTSLAVE=n
CONFIG_POSTFIX=y
CONFIG_POSTFIX_TLS=y
CONFIG_POSTGRESQL_CLIENT=y
CONFIG_POSTGRESQL_SERVER=y
CONFIG_PPP=y
CONFIG_PPTP_CLIENT=y
CONFIG_PRISM54=y
CONFIG_PROCMAIL=y
CONFIG_PSCHED_CLOCK_SOURCE=PSCHED_JIFFIES
CONFIG_PWLIB=y
CONFIG_PYTHON=y
CONFIG_PYTHON_LDAP=y
CONFIG_QADSL=y
CONFIG_QUAGGA=y
CONFIG_QUOTA_TOOLS=y
CONFIG_RADVD=y
CONFIG_RAIDTOOLS=n
CONFIG_RAZOR_AGENTS=y
CONFIG_RCS=y
CONFIG_RPM=n
CONFIG_RPPPPOE=y
CONFIG_RRDTOOL=y
CONFIG_RRLOGIND=y
CONFIG_RSYNC=y
CONFIG_SAGATOR=y
CONFIG_SAMBA=y
CONFIG_SARG=y
CONFIG_SCREEN=y
CONFIG_SER=y
CONFIG_SG3_UTILS=y
CONFIG_SHFS=y
CONFIG_SHOREWALL=y
CONFIG_SMARTMONTOOLS=y
CONFIG_SNORT=y
CONFIG_SQUID=y
CONFIG_SQUIDGUARD=y
CONFIG_STUNNEL=y
CONFIG_SUDO=y
CONFIG_SUPER_FREESWAN=y
CONFIG_SUPER_FREESWAN_NATT=y
CONFIG_SYSSTAT=y
CONFIG_TCPDUMP=y
CONFIG_TCP_WRAPPERS=y
CONFIG_TELNET_BSD=y
CONFIG_TFTP_HPA=y
CONFIG_THTTPD=y
CONFIG_UCARP=y
CONFIG_UCSPI_TCP=y
CONFIG_UNARJ=y
CONFIG_UNIONFS=n
CONFIG_UNRAR=y
CONFIG_UNZIP=y
CONFIG_USBAT02=y
CONFIG_USBUTILS=y
CONFIG_USE_DISTCC=n
CONFIG_VHZ=OFF
CONFIG_VIM=y
CONFIG_VLAN=y
CONFIG_VOBCOPY=y
CONFIG_VSFTPD=y
CONFIG_VTUN=y
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_PCWD=y
CONFIG_WEBALIZER=y
CONFIG_WGET=y
CONFIG_WIRELESS_TOOLS=y
CONFIG_WOL=y
CONFIG_WVDIAL=y
CONFIG_XFS=y
CONFIG_XINETD=y
CONFIG_XMBMON=y
CONFIG_ZIP=y
CONFIG_ZISOFS=y


----- Original Message ----- 
From: "Heiko Zuerker" <he...@zu...>
To: <dev...@li...>
Sent: Tuesday, September 26, 2006 3:25 PM
Subject: Re: [Devil-Linux-discuss] Error compiling LPRng


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hey,
>
> are you trying to compile DL 1.3 ?
> If yes, please switch to DL 1.2.
> 1.3 is the current (non working) development system.
>
> If no, did you do any customiztions?
>
> Heiko
>
> On Tue, September 26, 2006 06:49, Devil-Linux wrote:
>> Get this error
>> <<
>> executing LPRng with option build (in /build/tmp/LPRng-3.8.28) ERROR
>> /build/scripts/LPRng build failed
>> check log file /build/tmp/LOGS/build/LPRng for details make: *** [build]
>> Error 1
>>
>>>>
>>
>>> From LOG
>>>
>> <<
>> if test -f postinstall.${OSNAME} ; then s=postinstall.${OSNAME} ; else
>> s=postinstall.generic; fi; \ echo POSTINSTALL "'$s'"; cp $s postinstall;
>> POSTINSTALL 'postinstall.linux'
>> OSNAME=linux-gnu; case "linux-gnu" in *linux* ) OSNAME=linux;; esac; \
>> if test -f preremove.${OSNAME} ; then s=preremove.${OSNAME} ; else
>> s=preremove.generic; fi; \ echo PREREMOVE "'$s'"; cp $s preremove;
>> PREREMOVE 'preremove.linux'
>> OSNAME=linux-gnu; case "linux-gnu" in *linux* ) OSNAME=linux;; esac; \
>> if test -f postremove.${OSNAME} ; then s=postremove.${OSNAME} ; else
>> s=postremove.generic; fi; \ echo POSTREMOVE "'$s'"; cp $s postremove;
>> POSTREMOVE 'postremove.generic'
>> echo timestamp > vars.lo /bin/sh ../libtool --mode=link 
>> cc -L/usr/lib  -o
>> liblpr.la accounting.lo child.lo controlword.lo copyright.lo debug.lo
>> errormsg.lo fileopen.lo gethostinfo.lo getopt.lo getprinter.lo
>> getqueue.lo gl rm -fr .libs/liblpr.la .libs/liblpr.* .libs/liblpr.* ar 
>> cru
>> .libs/liblpr.a  accounting.o child.o controlword.o copyright.o debug.o
>> errormsg.o fileopen.o gethostinfo.o getopt.o getprinter.o getqueue.o
>> globmatch.o initialize.o krb5_auth.o linelist.o li ranlib .libs/liblpr.a
>> creating liblpr.la (cd .libs && rm -f liblpr.la && ln -s ../liblpr.la
>> liblpr.la) /bin/sh ../libtool --mode=link gcc -L/usr/lib  -o lpc lpc.o
>> liblpr.la -lssl -lcrypto /bin/sh ../libtool --mode=link 
>> cc -L/usr/lib  -o
>> lpd lpd.o liblpr.la -lssl -lcrypto /bin/sh ../libtool --mode=link gcc
>> -L/usr/lib  -o lpq lpq.o liblpr.la -lssl -lcrypto
>> /bin/sh ../libtool --mode=link gcc -L/usr/lib  -o lpr lpr.o liblpr.la
>> -lssl -lcrypto
>> gcc -o lpc lpc.o  -L/usr/lib ./.libs/liblpr.a -lssl -lcrypto gcc -o lpd
>> lpd.o  -L/usr/lib ./.libs/liblpr.a -lssl -lcrypto gcc -o lpr lpr.o
>> -L/usr/lib ./.libs/liblpr.a -lssl -lcrypto
>> gcc -o lpq lpq.o  -L/usr/lib ./.libs/liblpr.a -lssl -lcrypto
>> ./.libs/liblpr.a(lpd_secure.o): In function `Fix_receive_auth':
>> common/lpd_secure.c:394: undefined reference to `SecuritySupported'
>> ./.libs/liblpr.a(sendauth.o): In function `Fix_send_auth':
>> common/sendauth.c:272: undefined reference to `SecuritySupported'
>> collect2: ld returned 1 exit status
>> make[2]: *** [lpc] Error 1
>> make[2]: *** Waiting for unfinished jobs....
>> ./.libs/liblpr.a(lpd_secure.o): In function `Fix_receive_auth':
>> common/lpd_secure.c:394: undefined reference to `SecuritySupported'
>> ./.libs/liblpr.a(sendauth.o): In function `Fix_send_auth':
>> common/sendauth.c:272: undefined reference to `SecuritySupported'
>> collect2: ld returned 1 exit status
>> make[2]: *** [lpd] Error 1
>> ./.libs/liblpr.a(lpd_secure.o): In function `Fix_receive_auth':
>> common/lpd_secure.c:394: undefined reference to `SecuritySupported'
>> ./.libs/liblpr.a(sendauth.o): In function `Fix_send_auth':
>> common/sendauth.c:272: undefined reference to `SecuritySupported'
>> collect2: ld returned 1 exit status
>> make[2]: *** [lpr] Error 1
>> make[1]: *** [src] Error 2
>> make[1]: Leaving directory `/build/tmp/LPRng-3.8.28'
>> ./.libs/liblpr.a(lpd_secure.o): In function `Fix_receive_auth':
>> common/lpd_secure.c:394: undefined reference to `SecuritySupported'
>> ./.libs/liblpr.a(sendauth.o): In function `Fix_send_auth':
>> common/sendauth.c:272: undefined reference to `SecuritySupported'
>> collect2: ld returned 1 exit status
>>
>>>> ---------------------------------------------------------------------
>>>> ----
>>>>
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>> your opinions on IT & business topics through brief surveys -- and earn
>> cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>
>>
>
>
> - -- 
>
> Regards
>  Heiko Zuerker
>  http://www.devil-linux.org
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
>
> iEYEARECAAYFAkUZKk8ACgkQUcytMSbs+YVzJACeL++GMGQmKgQHNCTMCF3xGjMd
> hScAnjoTeZXhLf5xUzlV/gV2K5M7B4Ct
> =mEh5
> -----END PGP SIGNATURE-----
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share 
> your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss 

Re: [Devil-Linux-discuss] Error compiling LPRng

[Heiko Z. <he...@zu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey,

are you trying to compile DL 1.3 ?
If yes, please switch to DL 1.2.
1.3 is the current (non working) development system.

If no, did you do any customiztions?

Heiko

On Tue, September 26, 2006 06:49, Devil-Linux wrote:
> Get this error
> <<
> executing LPRng with option build (in /build/tmp/LPRng-3.8.28) ERROR
> /build/scripts/LPRng build failed
> check log file /build/tmp/LOGS/build/LPRng for details make: *** [build]
> Error 1
>
>>>
>
>> From LOG
>>
> <<
> if test -f postinstall.${OSNAME} ; then s=postinstall.${OSNAME} ; else
> s=postinstall.generic; fi; \ echo POSTINSTALL "'$s'"; cp $s postinstall;
> POSTINSTALL 'postinstall.linux'
> OSNAME=linux-gnu; case "linux-gnu" in *linux* ) OSNAME=linux;; esac; \
> if test -f preremove.${OSNAME} ; then s=preremove.${OSNAME} ; else
> s=preremove.generic; fi; \ echo PREREMOVE "'$s'"; cp $s preremove;
> PREREMOVE 'preremove.linux'
> OSNAME=linux-gnu; case "linux-gnu" in *linux* ) OSNAME=linux;; esac; \
> if test -f postremove.${OSNAME} ; then s=postremove.${OSNAME} ; else
> s=postremove.generic; fi; \ echo POSTREMOVE "'$s'"; cp $s postremove;
> POSTREMOVE 'postremove.generic'
> echo timestamp > vars.lo /bin/sh ../libtool --mode=link gcc -L/usr/lib  -o
> liblpr.la accounting.lo child.lo controlword.lo copyright.lo debug.lo
> errormsg.lo fileopen.lo gethostinfo.lo getopt.lo getprinter.lo
> getqueue.lo gl rm -fr .libs/liblpr.la .libs/liblpr.* .libs/liblpr.* ar cru
> .libs/liblpr.a  accounting.o child.o controlword.o copyright.o debug.o
> errormsg.o fileopen.o gethostinfo.o getopt.o getprinter.o getqueue.o
> globmatch.o initialize.o krb5_auth.o linelist.o li ranlib .libs/liblpr.a
> creating liblpr.la (cd .libs && rm -f liblpr.la && ln -s ../liblpr.la
> liblpr.la) /bin/sh ../libtool --mode=link gcc -L/usr/lib  -o lpc lpc.o
> liblpr.la -lssl -lcrypto /bin/sh ../libtool --mode=link gcc -L/usr/lib  -o
> lpd lpd.o liblpr.la -lssl -lcrypto /bin/sh ../libtool --mode=link gcc
> -L/usr/lib  -o lpq lpq.o liblpr.la -lssl -lcrypto
> /bin/sh ../libtool --mode=link gcc -L/usr/lib  -o lpr lpr.o liblpr.la
> -lssl -lcrypto
> gcc -o lpc lpc.o  -L/usr/lib ./.libs/liblpr.a -lssl -lcrypto gcc -o lpd
> lpd.o  -L/usr/lib ./.libs/liblpr.a -lssl -lcrypto gcc -o lpr lpr.o
> -L/usr/lib ./.libs/liblpr.a -lssl -lcrypto
> gcc -o lpq lpq.o  -L/usr/lib ./.libs/liblpr.a -lssl -lcrypto
> ./.libs/liblpr.a(lpd_secure.o): In function `Fix_receive_auth':
> common/lpd_secure.c:394: undefined reference to `SecuritySupported'
> ./.libs/liblpr.a(sendauth.o): In function `Fix_send_auth':
> common/sendauth.c:272: undefined reference to `SecuritySupported'
> collect2: ld returned 1 exit status
> make[2]: *** [lpc] Error 1
> make[2]: *** Waiting for unfinished jobs....
> ./.libs/liblpr.a(lpd_secure.o): In function `Fix_receive_auth':
> common/lpd_secure.c:394: undefined reference to `SecuritySupported'
> ./.libs/liblpr.a(sendauth.o): In function `Fix_send_auth':
> common/sendauth.c:272: undefined reference to `SecuritySupported'
> collect2: ld returned 1 exit status
> make[2]: *** [lpd] Error 1
> ./.libs/liblpr.a(lpd_secure.o): In function `Fix_receive_auth':
> common/lpd_secure.c:394: undefined reference to `SecuritySupported'
> ./.libs/liblpr.a(sendauth.o): In function `Fix_send_auth':
> common/sendauth.c:272: undefined reference to `SecuritySupported'
> collect2: ld returned 1 exit status
> make[2]: *** [lpr] Error 1
> make[1]: *** [src] Error 2
> make[1]: Leaving directory `/build/tmp/LPRng-3.8.28'
> ./.libs/liblpr.a(lpd_secure.o): In function `Fix_receive_auth':
> common/lpd_secure.c:394: undefined reference to `SecuritySupported'
> ./.libs/liblpr.a(sendauth.o): In function `Fix_send_auth':
> common/sendauth.c:272: undefined reference to `SecuritySupported'
> collect2: ld returned 1 exit status
>
>>> ---------------------------------------------------------------------
>>> ----
>>>
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your opinions on IT & business topics through brief surveys -- and earn
> cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
>


- -- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iEYEARECAAYFAkUZKk8ACgkQUcytMSbs+YVzJACeL++GMGQmKgQHNCTMCF3xGjMd
hScAnjoTeZXhLf5xUzlV/gV2K5M7B4Ct
=mEh5
-----END PGP SIGNATURE-----

[Devil-Linux-discuss] Error compiling LPRng

[Devil-Linux <dev...@js...>]

Get this error
<<
executing LPRng with option build (in /build/tmp/LPRng-3.8.28)
ERROR
/build/scripts/LPRng build failed
check log file /build/tmp/LOGS/build/LPRng for details
make: *** [build] Error 1
>>

>From LOG
<<
if test -f postinstall.${OSNAME} ; then s=3Dpostinstall.${OSNAME} ; else =
s=3Dpostinstall.generic; fi; \
echo POSTINSTALL "'$s'"; cp $s postinstall;
POSTINSTALL 'postinstall.linux'
OSNAME=3Dlinux-gnu; case "linux-gnu" in *linux* ) OSNAME=3Dlinux;; esac; =
\
if test -f preremove.${OSNAME} ; then s=3Dpreremove.${OSNAME} ; else =
s=3Dpreremove.generic; fi; \
echo PREREMOVE "'$s'"; cp $s preremove;
PREREMOVE 'preremove.linux'
OSNAME=3Dlinux-gnu; case "linux-gnu" in *linux* ) OSNAME=3Dlinux;; esac; =
\
if test -f postremove.${OSNAME} ; then s=3Dpostremove.${OSNAME} ; else =
s=3Dpostremove.generic; fi; \
echo POSTREMOVE "'$s'"; cp $s postremove;
POSTREMOVE 'postremove.generic'
echo timestamp > vars.lo
/bin/sh ../libtool --mode=3Dlink gcc -L/usr/lib  -o liblpr.la =
accounting.lo child.lo controlword.lo copyright.lo debug.lo errormsg.lo =
fileopen.lo gethostinfo.lo getopt.lo getprinter.lo getqueue.lo gl
rm -fr .libs/liblpr.la .libs/liblpr.* .libs/liblpr.*
ar cru .libs/liblpr.a  accounting.o child.o controlword.o copyright.o =
debug.o errormsg.o fileopen.o gethostinfo.o getopt.o getprinter.o =
getqueue.o globmatch.o initialize.o krb5_auth.o linelist.o li
ranlib .libs/liblpr.a
creating liblpr.la
(cd .libs && rm -f liblpr.la && ln -s ../liblpr.la liblpr.la)
/bin/sh ../libtool --mode=3Dlink gcc -L/usr/lib  -o lpc lpc.o liblpr.la =
-lssl -lcrypto
/bin/sh ../libtool --mode=3Dlink gcc -L/usr/lib  -o lpd lpd.o liblpr.la =
-lssl -lcrypto
/bin/sh ../libtool --mode=3Dlink gcc -L/usr/lib  -o lpq lpq.o liblpr.la =
-lssl -lcrypto
/bin/sh ../libtool --mode=3Dlink gcc -L/usr/lib  -o lpr lpr.o liblpr.la =
-lssl -lcrypto
gcc -o lpc lpc.o  -L/usr/lib ./.libs/liblpr.a -lssl -lcrypto
gcc -o lpd lpd.o  -L/usr/lib ./.libs/liblpr.a -lssl -lcrypto
gcc -o lpr lpr.o  -L/usr/lib ./.libs/liblpr.a -lssl -lcrypto
gcc -o lpq lpq.o  -L/usr/lib ./.libs/liblpr.a -lssl -lcrypto
./.libs/liblpr.a(lpd_secure.o): In function `Fix_receive_auth':
common/lpd_secure.c:394: undefined reference to `SecuritySupported'
./.libs/liblpr.a(sendauth.o): In function `Fix_send_auth':
common/sendauth.c:272: undefined reference to `SecuritySupported'
collect2: ld returned 1 exit status
make[2]: *** [lpc] Error 1
make[2]: *** Waiting for unfinished jobs....
./.libs/liblpr.a(lpd_secure.o): In function `Fix_receive_auth':
common/lpd_secure.c:394: undefined reference to `SecuritySupported'
./.libs/liblpr.a(sendauth.o): In function `Fix_send_auth':
common/sendauth.c:272: undefined reference to `SecuritySupported'
collect2: ld returned 1 exit status
make[2]: *** [lpd] Error 1
./.libs/liblpr.a(lpd_secure.o): In function `Fix_receive_auth':
common/lpd_secure.c:394: undefined reference to `SecuritySupported'
./.libs/liblpr.a(sendauth.o): In function `Fix_send_auth':
common/sendauth.c:272: undefined reference to `SecuritySupported'
collect2: ld returned 1 exit status
make[2]: *** [lpr] Error 1
make[1]: *** [src] Error 2
make[1]: Leaving directory `/build/tmp/LPRng-3.8.28'
./.libs/liblpr.a(lpd_secure.o): In function `Fix_receive_auth':
common/lpd_secure.c:394: undefined reference to `SecuritySupported'
./.libs/liblpr.a(sendauth.o): In function `Fix_send_auth':
common/sendauth.c:272: undefined reference to `SecuritySupported'
collect2: ld returned 1 exit status
>>

Re: [Devil-Linux-discuss] Automatic NFS mounts

[Heiko Z. <he...@zu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

just a quick answer, since I don't have much time.
Your best bet is to copy the script /etc/init.d/skeleton and add your
commands there.
As you already suspected, add the script with insserv to the boot order.

Of course don't forgett to run a save-config before you reboot. ;-)

cu
  Heiko

On Mon, September 25, 2006 15:28, sa...@pe... wrote:
>

>
> Hello,
>
>
> I just started experimenting with DL and this is my first post to this
> list.
>
> I would like to have remote NFS directories mounted automatically when
> the system boots. It there a proper way to do this with DL? I would prefer
> not to have to alter the standard CD iso image, if possible. Here's what
> I've
> tried so far:
>
> First a mount point is required for each NFS mount. I created these by
> adding mkdir commands to the file /etc/init.d/boot.local
>
>
> E.g.:
> mkdir /shm/nfsmnt && mkdir /shm/nfsmnt/nfs1 /shm/nfsmnt/nfs2
>
> This works ok. Is there a better way?
>
>
> Next I need to mount the remote directories. This is usually done by
> adding entries to /etc/fstab with the "auto" option. The problem with this
> is that NFS requires the portmap daemon to be running, but DL tries to
> mount fstab entries before portmap has been started, so all the NFS
> entries in fstab fail.
>
> Is there a place that I could put a command (mount -a -t nfs) that would
> be executed after the networking and portmap service is started? My only
> thoughts on this are to create a new service, e.g. nfsmount, in
> /etc/init.d
> containing the mount command and have it prioritised such that it runs
> after portmap.
>
> If adding a new service is the best way to do this, what is the proper
> way to install it? Should I manually add the links in the
> /etc/init.d/rcX.d
> directories, or is there a command that can be run to do this? (maybe
> insserv?) Is there a way to add the new service to the setup program
> without changing the CD?
>
> If it doesn't exist already and I missed it, it would be nice to have a
> service file, similar to boot.local, except that is the last thing to run,
>  instead of very early in the boot process.
>
> Thanks,
> Scott
> A.-----------------------------------------------------------------------
> --
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your opinions on IT & business topics through brief surveys -- and earn
> cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
>


- -- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iEYEARECAAYFAkUYfrcACgkQUcytMSbs+YWJ7gCeLmnYOeYqAwgmm4UvttT7NPUF
JD4An1Em1hEuohXGMAT2tqD7NW4XDEh6
=0bB6
-----END PGP SIGNATURE-----

[Devil-Linux-discuss] Automatic NFS mounts

[<sa...@pe...>]

Hello,

I just started experimenting with DL and this is my first post to this
list.

I would like to have remote NFS directories mounted automatically when =
the
system boots. It there a proper way to do this with DL? I would prefer =
not
to have to alter the standard CD iso image, if possible. Here's what I'=
ve
tried so far:

First a mount point is required for each NFS mount. I created these by
adding mkdir commands to the file
/etc/init.d/boot.local

E.g.:
mkdir /shm/nfsmnt && mkdir /shm/nfsmnt/nfs1 /shm/nfsmnt/nfs2

This works ok. Is there a better way?

Next I need to mount the remote directories. This is usually done by ad=
ding
entries to /etc/fstab with the "auto" option. The problem with this is =
that
NFS requires the portmap daemon to be running, but DL tries to mount fs=
tab
entries before portmap has been started, so all the NFS entries in fsta=
b
fail.

Is there a place that I could put a command (mount -a -t nfs) that woul=
d be
executed after the networking and portmap service is started? My only
thoughts on this are to create a new service, e.g. nfsmount, in /etc/in=
it.d
containing the mount command and have it prioritised such that it runs
after portmap.

If adding a new service is the best way to do this, what is the proper =
way
to install it? Should I manually add the links in the /etc/init.d/rcX.d=

directories, or is there a command that can be run to do this? (maybe
insserv?) Is there a way to add the new service to the setup program
without changing the CD?

If it doesn't exist already and I missed it, it would be nice to have a=

service file, similar to boot.local, except that is the last thing to r=
un,
instead of very early in the boot process.

Thanks,
Scott A.=

[Devil-Linux-discuss] CVS

[Devil-Linux <dev...@js...>]

Hi,

Finally figured out why the CVS worked so darn shaky for me.
Seem sourceforge have changed names from cvs.sourceforge.net
to devil-linux.cvs.sourceforge.net.

I am shure you all knew this considering the answers I got when asking,
the documentation should maby reflect this tho :)

http://www.devil-linux.org/documentation/1.2.x/ch03s01.html#d0e1463

/Jacob=20

[Devil-Linux-discuss] Virtual interfaces with iptables [was RE: Devil Linux and VLAN tagging (+ also Avaya IP Office)]

[Moray M. <mmc...@ox...>]

>> 2) does iptables interface identification (-i and -o switches)
support=20
>> identification of vlan interfaces as the source and destination=20
>> interfaces of packets, or only the physical interfaces? I would
expect=20
>> it to work, except I expected that with virtual interfaces (e.g.
>> eth1:1), and it doesn't work with those, but I guess vlan's a=20
>> different kernel mechanism.

>Were you using this on the FORWARD, PREROUTING, or POSTROUTING chain?

I was trying to use virtual interfaces on the forward chain.

M.

Re: [Devil-Linux-discuss] Devil Linux and VLAN tagging (+ also Avaya IP Office)

[cdmiller <cdm...@ad...>]

Moray McConnachie wrote:

> 
> 1) is the sample included with DL the best way to define VLANs
> (ifcfg-vlan100.sample on my box)? It is like a regular inferface config
> file, with the addition of VLANID=100 and removal of the MODULE= line
> defining the kernel driver module.

I think it is the best way.  Also look in the /etc/init.d/network script
to see the vconfig options being used.

> 2) does iptables interface identification (-i and -o switches) support
> identification of vlan interfaces as the source and destination
> interfaces of packets, or only the physical interfaces? I would expect
> it to work, except I expected that with virtual interfaces (e.g.
> eth1:1), and it doesn't work with those, but I guess vlan's a different
> kernel mechanism.

Were you using this on the FORWARD, PREROUTING, or POSTROUTING chain?

- cameron

Re: [Devil-Linux-discuss] Devil Linux and VLAN tagging (+ also Avaya IP Office)

[Heiko Z. <he...@zu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey,

I'm glad I can at least answer one question. ;-)

> 3) I'll want to run dhcpd on the DL box only on the vlan port, since it
> will only provide DHCP services for the phones, but our main Windows
> servers will continue to provide DHCP for everything else (saves messing
> with interoperability between Linux DHCP and Windows' dynamic DNS, tho'
> this looks doable if I really have to). Looking through /etc/init.d/dhcpd,
> DL starts DHCPD on interfaces which have DHCP=server
> in their interface config, which makes this easy, but can anyone tell me
> what the routes being created in the following lines are for ?
>
> for DEVICE in $DEVICES; do route add -net 255.255.255.255 netmask
> 255.255.255.255 $DEVICE
> done

DHCP used broadcasts for the early communication stages. That's why this
route has to be added to the interface where the DHCP server needs to
communicate on.

- -- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iEYEARECAAYFAkUOmF0ACgkQUcytMSbs+YW8tQCfdSYhNOx1ppuq2HsTJfpt80TB
3U8An1QJdqxpU4cpw+51Pddxhr48C2rE
=mlDx
-----END PGP SIGNATURE-----

Re: [Devil-Linux-discuss] installation

[Heiko Z. <he...@zu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Sun, September 17, 2006 19:47, Adam St. George wrote:
> Can I install DL to a hd? i would like to install to a hd so i wouldnt
> have to use a bootable cd and floppy.  Is this possible?

You can install it on a USB or CF card. The same method works also for
harddisks, but you won't be able to write to the media.

Check our documentation and mailinglist archives.

- -- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iEYEARECAAYFAkUOl9AACgkQUcytMSbs+YUWswCeICQM4XJSca5luoFwNHE4ExaP
InoAn12LaC7V2XcPVQinBh2Cg8gnSiaP
=C6yI
-----END PGP SIGNATURE-----