Thus spoke Tom Eastep:
> Hmmm -- This is probably because of how "grep" is defined on LRP. Please
> try it with the attached /etc/shorewall/functions file.
>
Pardon me for following up my own post but the previously-posted functions
file was brain-damaged. Here's one that works better...
Regard
Thus spoke Ewald Wasscher:
> Tom Eastep wrote:
>
> >
> > Hmmm -- This is probably because of how "grep" is defined on LRP. Please
> > try it with the attached /etc/shorewall/functions file.
>
> I did and the result is:
>
> : not found
> /etc/shorewall/functions: 29: Syntax error: expecting "in"
>
Tom Eastep wrote:
>
> Hmmm -- This is probably because of how "grep" is defined on LRP. Please
> try it with the attached /etc/shorewall/functions file.
I did and the result is:
: not found
/etc/shorewall/functions: 29: Syntax error: expecting "in"
But as I was reading around the shorewall sc
I previously compiled tinyps (with glibc 2.0.7) and have been using it
in a glibc 2.0.7 environment. Recently I shifted to a glibc 2.1.3
environment, and tinyps stopped working - it gives a SegFault right
after the title line.
I thought this was just the time to shift to busybox ps - after all,
I've the following to do:
* test Oxygen (glibc 2.1.3) with CDROM style loading
* replace ps (segfaults) with busybox ps
* bulletproof (?) config file some more
* shift release designator to 1.7-devel
* burn CDROM and release
I've snarfed the patches for 2.4.0-test11 that Charles had and put
them
Thus spoke David Douthitt:
> I was running Seawall and it crashed after a line that had something
> like the following in it (part of the Remote Chains section):
>
> sed 's/ inet .*brd/; ...'
>
> except that in my case, there apparently was *NO* broadcast setting -
> thus the string "brd" did n
Thus spoke Ewald Wasscher:
> Hello Tom and others,
>
> I've been testing the new shorewall-1.1.1.lrp package on Eigerstein2beta
> today and have run into a few problems:
>
> First there seems to be an extra space in the line for
> /etc/shorewall/policy in /var/lib/lrpkg/shorewal.conf. When I trie
I was running Seawall and it crashed after a line that had something
like the following in it (part of the Remote Chains section):
sed 's/ inet .*brd/; ...'
except that in my case, there apparently was *NO* broadcast setting -
thus the string "brd" did not exist in the "inet" line from "ip add
Hello Tom and others,
I've been testing the new shorewall-1.1.1.lrp package on Eigerstein2beta
today and have run into a few problems:
First there seems to be an extra space in the line for
/etc/shorewall/policy in /var/lib/lrpkg/shorewal.conf. When I tried to
edit /etc/shorewall/policy throu
Ewald Wasscher, 2001-04-09 22:28 +0200
>3. Some patches from the iptables-1.2.1a path-o-matic. If you use these
>you should be able to use my iptables.lrp package found here
>
>http://leaf.sourceforge.net/devel/ewaldw/
>When configuring your kernel you'll need to say yes to these: (isn't there
>
Bill Pitz wrote:
> On Mon, Apr 09, 2001 at 09:51:31PM +0200, Ewald Wasscher <[EMAIL PROTECTED]>
>wrote:
>
>> Unfortunately for you my kernel has support for ide-floppies (isn't that
>> what your zip-disk is?) compiled as a module. But If you ask nicely I
>> might compile you a custum one with
On Mon, Apr 09, 2001 at 09:51:31PM +0200, Ewald Wasscher <[EMAIL PROTECTED]>
wrote:
> Unfortunately for you my kernel has support for ide-floppies (isn't that
> what your zip-disk is?) compiled as a module. But If you ask nicely I
> might compile you a custum one with zip disk upport included i
On Mon, Apr 09, 2001 at 12:35:33PM -0700, Mike Noyes <[EMAIL PROTECTED]>
wrote:
> Bill Pitz, 2001-04-09 12:24 -0700
> >What exactly needs to be done to get an eigerstein box to run a 2.4 kernel?
> >
> >I've searched the leaf site a bit, but couldn't find anything. What do
> >I need to do? Patch
David Douthitt wrote:
> Ewald Wasscher wrote:
>
>> David Douthitt wrote:
>
>>> BB has as one requirement that it only use glibc as I remember.
>>
>> debian:~/lrp-2.9.8/build/busybox-0.50# grep --context=3 uClib *
>> README-
>> README-Supported libcs:
>> README-
>> README: glibc-2.0.x, glibc-
Mike Noyes wrote:
> Bill Pitz, 2001-04-09 12:24 -0700
>
>> What exactly needs to be done to get an eigerstein box to run a 2.4
>> kernel?
>>
>> I've searched the leaf site a bit, but couldn't find anything. What do
>> I need to do? Patches? Where can they be found?
>
>
> Bill,
> Take a lo
Thus spoke [EMAIL PROTECTED]:
> from there on one might include them in the basic shorewall built in config.
> (some are already there)
>
Just to clarify -- Shorewall does not have a "built in configuration" but
rather it has a "default configuration". Virtually everything about the
default con
Ewald Wasscher wrote:
>
> David Douthitt wrote:
> > BB has as one requirement that it only use glibc as I remember.
> debian:~/lrp-2.9.8/build/busybox-0.50# grep --context=3 uClib *
> README-
> README-Supported libcs:
> README-
> README: glibc-2.0.x, glibc-2.1.x, Linux-libc5, uClibc. People
Bill Pitz, 2001-04-09 12:24 -0700
>What exactly needs to be done to get an eigerstein box to run a 2.4 kernel?
>
>I've searched the leaf site a bit, but couldn't find anything. What do
>I need to do? Patches? Where can they be found?
Bill,
Take a look at these:
http://leaf.sourceforge.net/deve
What exactly needs to be done to get an eigerstein box to run a 2.4 kernel?
I've tried compiling a 2.4 kernel, but the system doesn't boot. It
eventually complains about not being able to mount the root filesystem
from the device. (I'm booting off of a zip disk...worked great with the
stock 2.2.
Everyone deserves a huge pat on the back. Our project continues to move up
the SourceForge rankings. We broke into the top 200 active projects on the
7th. In addition, Google searches for "embedded appliance" and "appliance
firewall" return our project as the first link. Statistics follow.
Dat
David Douthitt wrote:
> George Metz wrote:
>
>> On the other hand, Busybox isn't that huge... 95k in 2.9.8.
>
>
> 156k in Oxygen.
>
>> It's possible
>> that we can get the whole shebang in there if BB only needs one or two of
>> the libs.
>
>
> BB has as one requirement that it only use
Am Sonntag, 8. April 2001 22:06 schrieb Ewald Wasscher:
> KP Kirchdörfer wrote:
>
> >
> > Just a workaround until Tom find a new name:
> > rename shorewall.lrp to shorewal.lrp
> > after booting the disk
> > move /var/lib/lrpkg/shorewall.* to /var/lib/lrpkg/shorewal.*
> > edit shorewal.list to inc
[EMAIL PROTECTED] wrote:
>
> Long filenames are usually attractive, but not when they cause headaches.
Agreed!
> On Mon, 9 Apr 2001, David Douthitt wrote:
> > My thoughts are the package name could be picked up from a file named
> > "var/lib/lrpkg/XX.list" instead - and if there isn't one,
Jack Coates, 2001-04-09 08:06 -0700
>the URL method linked to the devel pages is the best way, IMHO. That way
>when I finally get around to doing rsync (shortly after getting my DSL
>restored on Thursday).
Jack,
It's done. :)
http://leaf.sourceforge.net/content.php?menu=1103&page_id=13
I think y
On Mon, 9 Apr 2001, David Douthitt wrote:
[...]
> What do you all think about NOT getting package names from the name of
> the package file?
>
> For example:
>
> foo.lrp
>
> ...could have its real name being...
>
> fooBecomesALongNameBeforeYouKnowItanditsUNSTOPPABLE
>
> :-) Seriously t
> From: Tom Eastep [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 09, 2001 3:55 PM
>
> Thus spoke [EMAIL PROTECTED]:
> > hope to have helped.
> >
> > another thing, is anyone *building* an iptables rule set yet?
> > I'm, and I'd like to compare/enhance it.
> > made a stand_alone_with_internet_c
I've been wrestling and wrestling with a totally bizarre problem with
the new configuration file. Since there are much fewer defaults than
before, and the bullet-proofing is just getting started, it's much
more dangerous :-)
I finally figured out the problem.
Anyone know what happens when you r
beowulf! beowulf! Cluster them and you'll have all the blinding speed of
a 486/33!
:-)
--
Jack Coates
Monkeynoodle: It's what's for dinner!
On Mon, 9 Apr 2001, David Douthitt wrote:
> Jack Coates wrote:
> >
> > well, http://www.mac.linux-m68k.org is probably a better fit for David
> > -- ain'
the URL method linked to the devel pages is the best way, IMHO. That way
when I finally get around to doing rsync (shortly after getting my DSL
restored on Thursday).
--
Jack Coates
Monkeynoodle: It's what's for dinner!
On Mon, 9 Apr 2001, Mike Noyes wrote:
> Jack Coates, 2001-04-08 23:20 -070
Thus spoke [EMAIL PROTECTED]:
> hope to have helped.
>
> another thing, is anyone *building* an iptables rule set yet?
> I'm, and I'd like to compare/enhance it.
> made a stand_alone_with_internet_connection rule set, am doing a simple masq
> router rule set, when finished I'll move to the full mu
Thus spoke Scott C. Best:
>
> Just wanted to confirm that ipmasqadm portfw
> can *only* handle tcp and udp right now behind the -P
> switch. Yes?
Yes
> If so...then to confirm: IPSec (even using
> *only* tunnel-mode ESP and not AH) and PPTP must
> terminate on a masq'ing firewall ro
> Just wanted to confirm that ipmasqadm portfw
> can *only* handle tcp and udp right now behind the -P
> switch. Yes?
I believe so.
> If so...then to confirm: IPSec (even using
> *only* tunnel-mode ESP and not AH) and PPTP must
> terminate on a masq'ing firewall router right now.
>
"Scott C. Best" wrote:
> Also...has anyone built a redir.lrp or IPFwd.lrp
> package yet, or have I found something else to do? :)
I built a redir.lrp a long time ago; I've also a redir4all built too.
redir4all includes a identd daemon and IRC redirector and a few other
goodies.
The former shou
Ewald Wasscher wrote:
> P.S. If I'm right the lrp package of shorewall is broken as "shorewall"
> is 9 characters long and doesn't fit the 8.3 msdos filenames on lrp boot
> floppies.
Reminds me of something I've been thinking about...
What do you all think about NOT getting package names from t
Ewald Wasscher wrote:
>
> George Metz wrote:
> > Thought here is to get a bootstrap initrd archive up and running first,
> > then use what it contains to load System packages, then addon packages,
> > from a significantly larger medium than a floppy disk. In this case, if
> > we're using bzip2,
Jack Coates wrote:
>
> well, http://www.mac.linux-m68k.org is probably a better fit for David
> -- ain't nothing running on a Mac Plus except what it came with. I think
> PalmOS might be a good fit, but the HCI issues would bite :-)
Heh heh.
Yet I don't have a Mac Plus in MY house :-) I do hav
Morgan Reed wrote:
> Macs require a PROM to boot from, but they don't require that you have the
> mac OS installed.
My version of OpenBSD 2.6 required a MacOS partition to load software,
drivers, etc. before it could boot. At one time, I played with a Mac
INIT that would allow you to boot into
[EMAIL PROTECTED] wrote:
> Then you need to re-read the man page for tar. That would be
> horrendous default behavior in *nix. This isn't DOS... where the user ==
> the sysadmin :)
In the book "UNIX System Administration", by David Fiedler and Bruce
Hunter, it says this:
tar's syntax is simpl
George Metz wrote:
>
> On Sat, 7 Apr 2001, Ewald Wasscher wrote:
> > Tweaking linuxrc so that
> > it will work with busybox's sed applet instead of GNU sed could save a
> > few bytes too.
> As for Sed, well, sed is an uncompressed 17k, so I don't know that the
> savings would be worth making li
George Metz wrote:
> On the other hand, Busybox isn't that huge... 95k in 2.9.8.
156k in Oxygen.
> It's possible
> that we can get the whole shebang in there if BB only needs one or two of
> the libs.
BB has as one requirement that it only use glibc as I remember.
Jack Coates, 2001-04-08 23:20 -0700
>sure thing. Would it accept symlinks? I'm hoping to get rsync working in
>order to put stuff onto sourceforge.net.
Jack,
phpWS holds all of it's content in our MySQL dbase. I can put a URL in
there or the HowTos. It's your choice. The BusyBox and ash menu ite
41 matches
Mail list logo
