On Thu, 2004-02-26 at 05:15, S Mohan wrote:
I put up a build machine to try and build some stuff on Bering. My first
task was to compile the kernel and look at replicating the build process
using gcc 2.95 and glibc2.0. Compilation gave me a 1MB kernel using default
config file that came with
On Fri, 2003-03-07 at 18:19, S Mohan wrote:
Tom had indicated his willingness to work with someone so as to have
shorewall working with bridged configuration. I did some initial
research. It looks like we need to use etables to force packets up one
layer so that iptables can operate on them. I
On Thu, 2003-02-27 at 06:58, Tom Eastep wrote:
--On Thursday, February 27, 2003 08:08:36 PM +0530 S Mohan
[EMAIL PROTECTED] wrote:
Yes I did try directions also. No luck. Jaime (LinCE) also seems to have
checked this out and had the same result.
So in other words, iptables support
On Mon, 2002-10-14 at 02:36, Luis.F.Correia wrote:
Command recall that is used in all Leaf variants uses a patch made by
someone
from the LRP community to add 'command history' to the original ASH.
It may be possible that this patch is not functional for long lines.
Please note that ash
On Mon, 2002-10-14 at 08:26, Luis.F.Correia wrote:
I command my Leaf through a serial line. I have no experience with ssh.
'command/path completion' is available on BusyBox...
but it seems busybox sh is not suitable...
Current versions of busybox ash are quite suitable for LEAF
On Sun, 2002-09-29 at 05:51, Luis.F.Correia wrote:
Ok guys, here's a crazy thought:
For a while it puzzled me why didn't LEAF evolve to a more recent and stable
libc.
Then I looked a bit into it and realised the obvious, to better support
virtually everything, libc has bloated. Its
On Sun, 2002-07-14 at 12:20, Mike Noyes wrote:
On Sun, 2002-07-14 at 11:43, John Klar wrote:
Just some observations about my interpretation of the GPL. Perhaps they
won't be terribly popular, but hopefully it'll make a few people *think*.
[2] Pointing requestors to the upstream source
On Tue, 2002-07-09 at 07:40, Vladimir I. wrote:
In my experience you have to be careful with uClibc.. I also tried migrating to
it and while the binaries seemed to run, I got various glitches and strange
behavior.
Which binaries caused problems? uClibc gets better and better all the
time
On Tue, 2002-07-09 at 08:30, Eric Spakman wrote:
Hello,
I managed to build an (allmost) complete version of Bering RC3 against
uClibc 0.9.12. This version is *a lot* smaller than the original versionbuild
Cool.
against GLIBC2. I tested the following modules: weblet, root, initrd,
On Tue, 2002-07-09 at 11:01, Mike Noyes wrote:
On Tue, 2002-07-09 at 10:39, Richard Doyle wrote:
On Tue, 2002-07-09 at 08:30, Eric Spakman wrote:
I don't know if uClibc is the way to go for LEAF, but it's rappidly evolving.
Glibc 2.0.7 is not maintained and Glibc 2.2.x is just to big
Charles,
Would this be acceptable?
bin/packages + /glibc-2.0
|
+ /glibc-2.1
|
+ /glibc-any
I guess so, but I sort of got the idea (perhaps incorrect)
that there were
packages that *did not* require a C library. If that's
Hi all
I've just finished two new packages:
ciped-1.lrp (for floppy kernels)
ciped-1-ide.lrp (for IDE kernels, Dachstein-CD needs this!)
qos.lrp
snip
QoS:
I created a QoS (Fair Queing) package for Dachstein. Because it's not
completely finished, this package does not appear in the
I figured out some of the confusion I was seeing:
snip
6) There is a NTP client - ntpclient appropriately - which
could replace rdate, if it is small enough...
On my system, ntpclient is 12320 bytes compiled under uClibc (0.9.9+),
6474 bytes zipped at maximum compression.
David Douthitt
Comments below:
Luis.F.Correia wrote:
Anyway, I could think of a core that boots without glibc and loads
glibc 2.0.7 for floppy releases and glibc whatever for CD, HD et
al...
I think supporting 3 different c-libraries at a time will
cause lots of
problems for users, and for the
Looks good! Comments inline...
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
snip
you can also use the net command
# net
Usage: net start|stop|reload
net ifup|ifdown|ifreset eth0|eth1|eth2|all
net ipfilter
snip
LRP-the Original
-Dave Cinege's original LRP release. This is not part of the LEAF
project, but mentioned out of respect of being the base that the LEAF
versions came from. Development has been rather slow, but the upcoming
Butterfly release (LRPv4.0) should be out soon. The most
snip
I agree, we even have LRP 2.9.8 in our files area(1). The
snip
(1) http://sourceforge.net/project/showfiles.php?group_id=13751
FYI, the linuxrouter.org site provides 2.2.19 kernels for LRP, which
aren't listed on the LEAF site. The release announcement follows:
arne @ loopback . org wrote:
Hi,
i spent my last two weeks in playing around with my gcc
again, and made a
first test version of a text/menu based version of a config
frontend for lrp
(it currently works for my version for kernel 2.4, based on
lrp 2.9.8 and
soon uClibc).
I've been
How did you manage to get everything so small? Your initrd.gz +
root.lrp weigh in at 742,530 bytes, which is considerably less
than the 835,457 of my current root.lrp (lrp 2.9.8 based, with
linux 2.2.18).
Ah, I see you've used libc 2.0.7.
The disk booted on one computer but not another. Did you
How did you manage to get everything so small? Your initrd.gz +
root.lrp weigh in at 742,530 bytes, which is considerably less
than the 835,457 of my current root.lrp (lrp 2.9.8 based, with
linux 2.2.18).
Ah, I see you've used libc 2.0.7.
The disk booted on one computer but not another. Did you
20 matches
Mail list logo
