> > > I would like to know if how do I handle/implement this on a DS 2.2.19
> > > environment (if this hasn't been done yet). I really need to raise my
> > > ram disk size to above 64M.
> > initrd.lrp is a package that was designed for Bering in order to get rid of
the
> > original LRP patches and
Hello Charles,
> As mentioned, the size limit for minix is 64M.
I see.
> If you want a really huge ramdisk, you can format and mount one after
the system has initally booted. Ext2 would be a good choice for the
file-system...you can
> get the ext2 userspace tools from the hard-disk support pack
Hello Jacques,
I figured someone from LEAF would suggest this. For starters, I'll try
to minimize/optimize my DS 2.2.19 packages as everything is already well
configured for DS 1.0.2 and hopefully create more ram space. But I'll
definitely look into Bering's offerings as the 2.4 environment seem
Gary Dodge wrote:
> Internet (dsl)
> |
> |_Eth0 Firewall
> |_
>|| |
> Eth1Eth2 Eth3
> (192.168.1.254) (10.10.10.254) (192.168.2.254)
>
On Wed, 13 Mar 2002, Jacques Nilo wrote:
> > I have a need to increase my syslinux.cfg ramdisk_size declaration to a
> > value above 65536. My DS box has 128MB physical ram, and it's currently
> > using 65536, but for database reasons, I'm thinking of jacking this
> > value to 98304.
> >
> > I di
I am completely embarrassed 'cause the web server was missing a gateway
address!
Actually, it makes quite a lot of sense when you think about why I was able to
browse from within the internal network as opposed to from the 'Net. The web
server knew what address to pass back the requested packets
At 05:14 PM 3/13/02 -0600, guitarlynn wrote:
>On Wednesday 13 March 2002 12:45, Doug Sampson wrote:
>
>> I still can't access the web server via
>> http://www.cybersampson.com!!! #$%#!&
>
>It works now from my house!
And from mine as well. But it didn't before when I tried, so you did fix
someth
Internet (dsl)
|
|_Eth0 Firewall
_|___
|| |
Eth1Eth2 Eth3
(192.168.1.254) (10.10.10.254) (192.168.2.254)
On Wednesday 13 March 2002 12:45, Doug Sampson wrote:
> I still can't access the web server via
> http://www.cybersampson.com!!! #$%#!&
It works now from my house!
--
~Lynn Avants
aka Guitarlynn
guitarlynn at users.sourceforge.net
http://leaf.sourceforge.net
If linux isn't the answer, you've
I have added my networks to the INTERN_NET= variable and now only the last
entry can reach the internet.
i.e.: INTERN_NET=10.10.10.0/24 192.168.1.0/24
only the 192.168.1.0/24 will be forwarded to the internet, if I reverse the
order then Only the 10.10.10.0/24 will reach the outside world.
do I
> I have a need to increase my syslinux.cfg ramdisk_size declaration to a
> value above 65536. My DS box has 128MB physical ram, and it's currently
> using 65536, but for database reasons, I'm thinking of jacking this
> value to 98304.
>
> I did some research on the past mail archives and stumbled
Doug Sampson wrote:
[snip]
> I still can't access the web server via http://www.cybersampson.com!!!
> #$%#!&
>
> I'm beginning to think it's the web server that is denying access. I'm
That web address is having problems. Apparently www2.cybersampson.com
does not work at this time.
Regards,
At 10:45 AM 3/13/02 -0800, Doug Sampson wrote:
[...]
>I still can't access the web server via http://www.cybersampson.com!!!
>#$%#!&
>
>I'm beginning to think it's the web server that is denying access. I'm
>thinking that the web server does accept requests from the private network
>but is *someh
> If I understand the setup right, you are referring here to
> hosts.allow and
> hosts.deny on the LEAF router. But the actual Web server runs
> on a different
> host, on its port 80, and gets (or is supposed to get, once everything
> works) traffic forwarded from port 8080 on the LEAF router's
> I did not mean to imply that the list had let an obvious security hole get
> propagated - I know my own understanding is limited and probably flawed,
> and I probably phrased the post poorly.
No, your question was phrased well. I was explicit in my reply because a)
this question has come up be
Am Mittwoch, 13. März 2002 00:58 schrieb Pete Dubler:
> There is talk around about libz in general having security flaws
> (Redhat send out an alert and update for theirs). Does anyone know
> what version of libz.lrp are "safe" for Dachstein (and other LEAF
> distributions)?
I've build yesterday
Thanks for the response, Charles.
I did not mean to imply that the list had let an obvious security hole get
propagated - I know my own understanding is limited and probably flawed,
and I probably phrased the post poorly.
Just to confirm my understanding:
In order to allow HTTP access to 192.
> I have a need to increase my syslinux.cfg ramdisk_size declaration to a
> value above 65536. My DS box has 128MB physical ram, and it's currently
> using 65536, but for database reasons, I'm thinking of jacking this
> value to 98304.
>
> I did some research on the past mail archives and stumbled
> I have a question regarding ipchain rules that are enabled by default.
>
> The FAQ (sourceforge LEAF, sec06) on 'LRP won't route to a private IP
> Range' states:
>
> "As your external NIC address falls in the 192.168.x.x range,
> comment out that one line
>
> # $IPCH -A $LIST -j DENY -p
I'm not sure but I think the maximum size for minix filesystems is 64Mb.
Try Bering, since it uses TMPFS, there should be no limit for the
filesystem.
-Original Message-
From: Vic Berdin [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 13, 2002 7:59 AM
To: [EMAIL PROTECTED]
Subject: [L
Hello all!
Kudos to the LEAF and LRP team, esp. Mr. Steinkuehler - once I
actually understood the installation instructions (having misread one
section about a dozen times), Dachstein came up and just worked!
I have a question regarding ipchain rules that are enabled by default.
The FAQ (source
21 matches
Mail list logo
