From: "Daniel Weismüller" <whytea@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Firewall Groups 2
Date: Tue, 13 Nov 2012 10:30:25 +0100 [thread overview]
Message-ID: <50A21331.9030708@ipfire.org> (raw)
In-Reply-To: <50A11253.5020605@oab.de>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
Hi Alex
I'll test it a bit but I have a little wish for the future.
Could you please include the information in which folder the files are
which we have to replace with your files. It would be nearly perfect if
you include the structure in your tar-file. ;-)
And if we have to do further things like (perl -e "require
'/var/ipfire/lang.pl'; &Lang::BuildCacheLang") please tell us, too.
Thanks
- Daniel
Am 12.11.2012 16:14, schrieb Alexander Marx:
> Dear List,
>
> Please take this version.
>
> I gave you wrong information:
>
> The directory needed must be /var/ipfire/fwhosts
>
> Sorry ;-)
>
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
>
--
__________________________________________
You need a firewall?
Easy to use? Powerful? Modular? For free?
www.ipfire.org
An Open Source Firewall Solution
parent reply other threads:[~2012-11-13 9:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <50A11253.5020605@oab.de>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50A21331.9030708@ipfire.org \
--to=whytea@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox