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

-----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-----

> 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

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.

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

-----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, sallen@... 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
> Devil-linux-discuss@...
> 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-----

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.=

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

>> 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.

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

-----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-----

-----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-----

We're about to set up VLANs on our local network to support shiny new
switches and a shiny new VoIP phone system (Avaya IP Office - if anyone
has any experience of networking IP Office, or indeed any Avaya VoIP
system, I would love to discuss it with you, probably off-line since it
is pretty off-topic.)
Naturally I would like to be able to connect our firewalling DL box to
the new phone VLAN, and use it as the firewall.=20
I've got a couple of questions, if anyone knows the answers. I've
checked out all of this on the web, but haven't found definitive
answers.
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=3D100 and removal of the MODULE=3D =
line
defining the kernel driver module.
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.
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=3Dserver
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
Cheers,
Moray
-------------------------------------=20
Moray McConnachie
IS Manager +44 1865 261 600
Oxford Analytica http://www.oxan.com

I uploaded a new testing release to the ftp server, give this one a try
and let me know how it went.
Thanks for creating the new image, Heiko. It works for me now.
There is another issue with the resource IPaddr2 of heartbeat. The
script expects the binary "ip" to be located in /sbin instead of /usr/sbin
where it is currently located in devil-linux.
I created a custom CD with "ip" in /sbin and IPaddr2 worked fine.
Maybe it would be wise to move | link "ip" to /sbin in the main
distribution.
Thanks a lot for your help!
Marc
---------------------------------
Keine Lust auf Tippen? Rufen Sie Ihre Freunde einfach an.
Yahoo! Messenger. Jetzt installieren .

On Fri, September 8, 2006 14:11, Kari Mattsson wrote:
> Bruce Smith wrote:
>
>>>> BUT we have XFS included, which has support for this. Good enough?
>>>>
>>>>
>>> Mmm.. I reformatted the reiserfs on the test system to xfs.
>>> Nope, it didn't quite do it. With options 'defaults,acl' mount still
>>> gives arror
>>>
>>> mount: wrong fs type, bad option, bad superblock on /dev/sda1,
>>> missing codepage or other error In some cases useful info is found in
>>> syslog
>>>
>>> ...and in syslog:
>>>
>>>
>>> ..... kernel: XFS: unknown mount option [acl].
>>>
>>>
>>
>> I'm not sure you need to mount XFS with the acl option for ACL's to
>> work.
>>
>> Mount the XFS volume with just 'defaults' and try to create an ACL.
>>
>
> Good try ;-) ...however, setfacl consistently (ext2/ext3/reiserfs/xfs)
> responded:
>
>
> # setfacl -m user:jdoe:r file1
> setfacl: file1: Operation not supported
OK from what I could find out, it seems we still need to apply the
separate AE+ACL patches to the kernel.
http://acl.bestbits.at/
Those patches are quite old, no idea if they will even apply to Kernel
2.4.33.x ...
There also seems that the XFS AE+ACL stuff never made it in the mainstream
Kernel and it has to be extracted from the XFS CVS repository...
I doubt I'll have time this weekend to look at it any more.
--
Regards
Heiko Zuerker
http://www.devil-linux.org

Community

Help

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

CountryState

JavaScript is required for this form.

I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. I understand that I can withdraw my consent at any time. Please refer to our Privacy Policy or Contact Us for more details