Re: [IPCop-devel] #includes

[Mark W. <ma...@wo...>]

Hi,

> > Will the rc.firewall.up and associated files handle having an
> > #include directive or something like it in them?
> >
> > If they could, it could lead to a customizable file that is never
> > overwritten with a patch, yet automatically included.
> >
> > That way, we would never modify the rc.firewall.up (etc), but the
> > rc.firewall.up.include file instead.
> >
> > Fresh installs would put out an empty copy of the include file,
> > upgrades would never touch it, and the original file would always
> > include a reference to the include file.
> >
> > I think this would lend itself well to further enhancements and
> > modifications by users and could make copying enhancements to a
> > floppy prior to a major upgrade simple. Go to /etc/rc.d and copy
> > *.include to the floppy. Copy it back after the upgrade.
> >
> > Thoughts?
>
> Someone pointed out that these are shell scripts. That means you could
> end one shell script with a call to the next shell script...

In my setup at home, I include this line at the end of
/etc/rc.d/rc.firewall.up
/etc/rc.d/rc.eth2

This brings up my eth2, which is a private connection to my neighbour.  When
I upgrade, I just copy over my rc.eth2 and add it to rc.firewall.up again.

Kind regards,

    Mark Wormgoor