Dear all:
With its v1.0-rc2 version Bering appears now fairly stable and it seems that
quite a lot of people have been giving it a try.
We would like to stabilize this first version with a "last" rc3 before final
release.
rc3 should include:
2.4.18 kernel with:
a/ More netfilter patches (to take
Le Dimanche 2 Juin 2002 23:54, Brock Nanson a écrit :
> I've been adding more goodies to my RC2 Bering box. However, the 6MB RAM
> disk is getting cramped. How do you increase it? Is there a parameter I
> can add to syslinux.cfg or perhaps initrd.lrp? Poking around I don't see
> an obvious pla
Le Lundi 3 Juin 2002 01:56, Eric House a écrit :
> JNilo wrote:
> > [dhclient.lrp working now]
>
> Do you recommend dhclient over pump for Bering rc2? Pump seems to be
> working for me ok now. (AT&T cable connections with ez-ipupdate
> talking to dyndns.)
>
No. I have been using pump myself for
Well ... you don't tell us very much, and I have to read a bit between the
lines here. So since this is based partly on guesses about what lies behind
veils like "as I would expect them to look", I may be off base. With that
disclaimer ...
... the problem appears to be specific to the wireless
On Mon, 3 Jun 2002, Klint Gore wrote:
> I'm stumped. I can't ping over the wireless even though everything
> looks ok.
>
> I've got a bering setup (finally) with pcmcia wavelan cards to ethernet.
> I'm just doing plain routing so my shorewall is set to wide open (as far
> as I can tell it is).
Hi everybody. I have a problem you may be able to assist me with.
I have a Eigerstein floppy happily routing away on a Pentium 120 with 16
MB of RAM and two old PCI DEC chipset NICs. The version of Tulip that
comes with Eigerstein works fine. My connection is to Bigpond Australia
Cable which u
I'm stumped. I can't ping over the wireless even though everything
looks ok.
I've got a bering setup (finally) with pcmcia wavelan cards to ethernet.
I'm just doing plain routing so my shorewall is set to wide open (as far
as I can tell it is). ethernet is 192.168.1.x, wireless is 10.1.1.x.
be
JNilo wrote:
> [dhclient.lrp working now]
Do you recommend dhclient over pump for Bering rc2? Pump seems to be
working for me ok now. (AT&T cable connections with ez-ipupdate
talking to dyndns.)
Thanks,
--Eric House
***
At 23:54 2/06/2002, Brock Nanson wrote:
Its in /var/lib/lrpkg/root.linuxrc
Search for systsize and increase it.
Backup initrd.lrp and your done
well I think you will have to reboot, I don't know about activating this
one without rebooting
sorry
Kim
>I've been adding more goodies to my RC2 Ber
I've been adding more goodies to my RC2 Bering box. However, the 6MB RAM
disk is getting cramped. How do you increase it? Is there a parameter I
can add to syslinux.cfg or perhaps initrd.lrp? Poking around I don't see an
obvious place, but I thought the 'stein offerings did it in syslinux.cfg.
I found the perfect platform at a local used computer dealer (in Los
Angeles).
Brand and model...
Digital Celebris DL5100
50 Mhz pentium with 64 MB ram for $29.00
or
100 MHZ pentium with 64 MB ran for $39.00
It boots the 1440 stock LRP disk fine, but when I try to boot with either
a Dachstei
On Sun, 2002-06-02 at 12:44, David McBride wrote:
> Sorry to sound so stupid, but I dont really keep up with the list very well,
> only skim for eye catching stuff. What are these drivers for? I know that
> Scyld has something to do with clusering, but what are these drivers for?
> Channel bondi
On Sun, 2002-06-02 at 13:16, Nachman Yaakov Ziskind wrote:
> Now, here's where I'm stuck: attempts to ping to the external interface yield a
> Type 3 error. But I haven't configured any firewall rules yet. Does it come out
> of the box blocking everything?
Nachman,
Yes. Dachstein comes with a pre
Nachman Yaakov Ziskind wrote (on Sun, Jun 02, 2002 at 03:38:56PM -0400):
|
| After some more poking and prodding, I found out that backup stuff lived in
| /var/lib/lrpkg. A file called 'backdisk' contains lines for each item on the
| menu, and lo and behold! - modules appears twice. Remove one li
Sorry to sound so stupid, but I dont really keep up with the list very well,
only skim for eye catching stuff. What are these drivers for? I know that
Scyld has something to do with clusering, but what are these drivers for?
Channel bonding of some sorts??? Please give some details.
Thanks for
| Nachman,
| There are two LEAF releases/branches that fit your needs. Dachstein
| 1.0.2 is one and Bering 1.0-rc2 is the other.
Ok, I bit the bullet and d/loaded Dachstein 1.0.2. I feel like I'm back at
square one again. :-(
My two 3coms, which worked flawlessly in 2.9.8, refused to load - four
**
¯Â°Ó·~¿ì¤½«Ç¥X¯²
**
±MªùªA°È°Ó¥Î¿ì¤½«Ç¤§©Ó¯²¤H¡C
¥x¥_¦Uµ¥¯Å°Ó¥Î¿ì¤½«Ç®×¥ó¡A¾A¦X¦UºØ°Ó·~»Ý¨D¡I¡I
§Ú֦̾³ºZ³qªº¸ê°T¡B¦³«Ü¦h¥ß§Yn¥X¯²ªº¿ì¤½«Ç¡A¥¿µ¥«ÝµÛ±zªº
Hi Kim
> hi all,
>
> I am playing around with the weblet found in bering, and noticed that the
> firewall rules are
> displayed by displaying a firewall file in /var/sh-www/data. Now I wonder
> which process is responsable
This is done by /etc/shorewall/start.
This file is called by shorewall
I fixed the dhclient.lrp package for Bering. Should now work OK.
Main differences with the dhclient.lrp in Dachstein are:
1/ No /etc/init.d/dhclient script. Like with pump, dhclient is automatically
called by ifup/ifdown
2/ dhclient moved to /sbin so that ifup/ifdown can find it
3/ dhclient-enter
By popular request I have compiled Donald Beckers network drivers for Bering
2.4.18 linux kernel.
I have tested eepro100 and it seems to work OK.
All the stuff is here:
http://leaf.sf.net/devel/jnilo/bering/latest/contrib/drivers/scyld
Do not forget to load pci-scan.o first :-)
Reference:
htt
hi all,
Wel the subject sais it all this time.
Are there any security implications or other things I should be aware of
when I run
bash on leaf??
Kim
___
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28
hi all,
I am playing around with the weblet found in bering, and noticed that the
firewall rules are
displayed by displaying a firewall file in /var/sh-www/data. Now I wonder
which process is responsable
for putting that file there? I want to make some minor adjustments like
adding linenumbers
At 10:24 AM 6/2/02 -0400, Adam Drake wrote:
>Thanks for your reply Ray. I can send mail from an internal host, using
>address [EMAIL PROTECTED] to an external host and it arrives. I
>cannot collect mail from qmail, whether sent from internally or externally.
OK. As to the first part ... what I w
as you correctly suggest, i don't really need a waiting interval. what i
really need is to ping a list of hosts every minute or so (the polling
interval). if ping returns an error, then i have to check if other hosts are
unreachable. i don't have to wait to do this check though.
if i cannot reach
Adam Drake wrote:
>
[ snip ]
> Shorewall/rules
[ snip ]
> # Added A.Drake to allow pop3 access to qmail on firewall
> ACCEPTloc fw tcp 110
> ACCEPTloc fw tcp 25
> ACCEPTfw net tcp 110
> ACCEPT
assuming it is proftpd you are using behind your firewall, you will have to
include following two lines in your proftpd.conf
MasqueradeAddress yourhost.com
PassivePorts 4 49000
and set up a port-forwarding for all passive ports to the internal server.
you will pr
Thanks for your reply Ray. I can send mail from an internal host, using
address [EMAIL PROTECTED] to an external host and it arrives. I
cannot collect mail from qmail, whether sent from internally or externally.
Here are some configs:
shorewall/inter
Le Samedi 1 Juin 2002 23:13, ! ! PLZ READ ME ! ! a écrit :
> Hallo Jacques,
>
> could you check http://leaf.sourceforge.net/devel/jnilo/bubooting.html - i
> think 'DISKWAIT=yes' should be 'diskwait=yes' and no one should think of
> deleting 'LDLINUX.SYS' from the first disk. At least it took me on
28 matches
Mail list logo
