Kory Krofft wrote:
when Nero burns it, sh-httpd becomes sh_httpd.
FWIW, this is a feature of burning proper-spec ISO-9660 CD's. That
charset for 'ISO' filenames is limited (i.e. dashes are not valid
filename chars) so Nero is 'helping' you by renaming the file for ya, to
be compliant with the
You can get a Nov 2004 version of the guide from here:
http://web.archive.org/web/20041106175146/http://leaf-project.org/doc/guide/leaf-guide-collection.pdf
(When sites/pages can't be found on the net but you know they used to be
there, archive.org is your friend.)
scott; canada
Fabricio
This error was observed and posted by another on Oct 16 and the problem
has returned (or persisted).
I'm seeking to acquire the PDF doc. On page:
http://leaf.sourceforge.net/doc/guide/
I click the hyperlinked text pdf version, which links to:
Whew, that was a bit of an exercise.
Some issues I discovered and some quick things that I learned - maybe
this will help others. Likely I need some correction/clarification too?!
FWIW I use a CD for the bulk of the packages and a floppy for 'partial'
backups of the packages that I adjust.
Jim Ford wrote:
I'd be interested in the experience (and workarounds) of others.
I use a CD-ROM drive and find that gives me a number of benefits...
- CD-ROM is read-only, so integrity of its files can be preserved
- simple, no-hassle 1.44MB floppy for config changes
- faster package saves
I'm of the mindset that this is, for all practical intents and purposes,
ill advised and here's my reasoning.
The packages are the products of various authors, Tom Eastep for one.
Unless he and all contributors were to adhere to some protocol there's
the definite potential for problems.
Eric Spakman wrote:
To the package maintainer:
- is it possible to remove the dependency on /etc/hosts.allow since
it would seem to be redundant with shorewall rules?
It is possible to remove the dependency, but there is a reason why p9100
(and a few other packages) are compiled with
Hi, I'm using BuC 2.3 with a dynamic-IP, PPPoE, DSL connection. pppd and
pppoe are both version 2.4.2 Rev 2 (current, per the packages page).
I'm seeking info from my ppp(oe) software about (esp) the name of the
access concentrator I'm connecting to. If I had a standalone pppoe
executable I'd
Eric Spakman wrote:
But pppd/pppoe is logging
to /var/log/ppp.log, did you also looked at that one?
My ppp.log is always empty. All logging that I can find is located in
daemon.log.
(I've got an old ppp.log that had chat entries from a modem connection
but /pppd/, in all cases, seems to
Whew, what a journey down source code lane...
One thing that was killing my effort was that the debug statements in
the source code were using printf's, so the fact that, by default, pppd
spins itself off into the background means that one would never see the
printf's at all!
Wanting to
I've noticed for the past day-ish that two packages I'm interested in
(tc, qos-htb) have been unavailable from the sf website.
e.g. URL:
http://cvs.sourceforge.net/viewcvs.py/leaf/bin/bering-uclibc/packages/qos-htb.lrp?rev=HEADcontent-type=application/octet-stream
times out eventually and
I've got myself a sweet Sipura SPA-2100 but even though it has built-in
QoS routing that seems to perform superbly
(http://www.tomsnetworking.com/2005/06/22/review_spa2100/page4.html) I
prefer to place it behind my LEAF firewall so as to:
- learn QoS
- keep my LEAF unit as the PPPoE login unit,
I'm of the mindset that the way the LEAF CD-image is presently
constructed is unnecessarily obtuse.
Regarding BuC 2.4.1 in particular (though I recall that recent versions
of BuC-from-CD all work this way):
The LEAF ISO is bootable and this is effected via a floppydisk image
that is stored on
Sorry, a small word omission (**) that made obscured the functionality I
was trying to describe (and made me look all-too-easily impressed).
groups, freeman wrote:
Instead of timing-out to the LEAF bootup, I can also elect to have the
system boot a DOS diskette *image-file*, for e.g. if I want
KP Kirchdoerfer wrote:
The Bering-uClibc team releases LEAF Bering-uClibc 2.4.2
This version provides another fix dnsmasq 2.27 and the usual shorewall update
(now up to shorewall version 3.0.7).
Thanks! Yesterday I had observed (on BuC 2.4.1), 2 instances of the
dnsmasq process
Just sharing my success at employing a USB network adapter on BuC3 beta2.
I have a USB CATC (Netlink II) adapter and found these modules needed to
make it work:
usbcore
usb-uhci (AIUI for some people usb-ohci might be used here, instead)
catc
(In particular I was pleasantly surprised
Way back on Aug 23, regarding apkg
Eric Spakman wrote:
A 'complete' backup is always done for a few reasons:
-it removes stale changed config files from no longer installed packages.
-it's fast because the configdb is not big
-it's much simpler and robust
it's the removal of stale
Eric Spakman wrote:
Hi Scott,
I don't want to make the config system more complex than it needs to
be, also for future enhancements like remove packages and current
options like upgrade and show config changes (which will show strange
output because the default config file wouldn't
Heh, I spent some time messing with 1680 floppies in a DOS/Windows
environment. What I observed was that 1680 size isn't recognized
properly in pure DOS and/or XP, so it was in my case a very unfriendly
format.
Given how much simpler one's life is with 1440 size disks (including,
one
Eric Faden wrote:
Found it. hosts.allow.
-Eric
Wow.
I went thorough the same painful discovery of hosts.allow as did Eric
(for me it was p9100). At the time I posted about this issue and made
some suggestions but nothing was agreed upon between all we various
opinions :) Perhaps
I'm not sure why the two items you linked to aren't 100% suitable for you...
but matrix orbital at http://www.matrixorbital.com/ makes
RS-232-connected LCD displays that also have input (buttons)
functionality all built-in. A 2-line LCD like I have is something like
$40-$50 IIRC.
I'm using
Kwon wrote:
I am thinking of using the following for Bering uClibc for a quiet low
power solution:
http://www.via.com.tw/en/products/mainboards/motherboards.jsp?motherboard_id=301
Please post again of your findings? Thanks!
I can share with you my measurements about power consumption for one
Kwon wrote:
Thank you for posting! Btw, what tool did you use for the above measurements?
Is that a software tool and open source?
A hardware gizmo called P3 Killawatt:
http://www.p3international.com/products/special/P4400/P4400-CE.html
Cost is approx $30; sometimes they're available on
Hi folks, as always thanks for everyone's work on LEAF!
FWIW I'm presently on Bering v3.0 RC2.
I'm setting up a FAT32 fileserver and thought that LEAF would make a
nice tight base upon which to build that ... and I know LEAF quite well.
I'm having some difficulty with the provided v2.2 of
Paul G Rogers wrote:
I'm setting up a FAT32 fileserver and thought that LEAF would make a
nice tight base upon which to build that ... and I know LEAF quite
well.
Pardon my asking but, why on Earth would anyone want Samba on a perimeter
firewall/router?!
Uh, cuz I'm not setting up
Martin Hejl wrote:
Hi bino,
I see that it's not just me that see BuC is to hot to just positioned as
router/firewall
I see BuC as Platform that we can build anything on top of it.
one _can_ - but it doesn't mean that the people working of LEAF should
necessarily spend their time on
Wow, I've been around and around (e.g. BuC Dev. Guide, Chapter 1.
Development) trying everything under the sun to get a busybox built - I
did get it built using buildtool, but then observed that 1.2.x doesn't
have the arp command which I assume was patched in. I was seeking the
patch, in .svn
Hi, I'm testing with BuC 3.1, having downloaded the USB image and dd'd
it onto a 256MB USB stick. (Mobo is a very new ASUS Wolfdale.)
However the bootup would not complete - none of the .LRP files get found
(nf!) and finally I get the msg:
/linuxrc: source: line 277: can't open
I've got a BuC 3.0beta2 box connected via PPPoE using DSL.
I'm wanting to implement single-physical-connection MLPPP but it's not
working, so at the top level I'm wondering if anyone has tried this
(MLPPP using one or more physical connections) and had success or failure?
Specifically for
Gordon Bos wrote:
Craig Caughlin wrote:
1.)If you're using the Bering-uClibc CD, how do you make changes and then
back those up?
You'll need writeable media ;)
Although deprecated the 3.5 floppy disks are still a good choice
because of their write inhibit switch. The only other
Jim Ford wrote:
Is there anything against using a SD to CF adaptor, eg:
http://tinyurl.com/6nzbau
Then using it in a CF to IDE adapter (which is a set-up I use)?
You would then effectively have a write protectable IDE disk.
Jim
Nope, that would do just as well ... in fact it's be a tad
Hi, just starting to look at 3.1.1b2 and seem to have noticed that the
folder
\2.4.34.6\kernel\drivers\i2c
is missing the the modules tarball, that I grabbed from:
http://downloads.sourceforge.net/leaf/Bering-uClibc_modules_2.4.34.6.tar.gz?use_mirror=internap
I think this may cause bustage
Hi, working with the new 3.1.1b2 release.
I am working with the floppy image in a pretty near-to-defaults setup,
just to try to get the pppd working (PPPoE actually).
I'm having trouble getting the pppd to behave - in the syslog I'm
seeing, every time I try to cause a PPPoE connection, my
KP Kirchdoerfer wrote:
Am Sonntag, 29. März 2009 18:09:53 schrieb groups, freeman:
Hi, working with the new 3.1.1b2 release.
I am working with the floppy image in a pretty near-to-defaults setup,
just to try to get the pppd working (PPPoE actually).
I'm having trouble getting the pppd
KP sent me a fix for this Fatal Error 11, which made the problem go away
for me, so just a heads up that there seems to be a known problem with
the PPP(oE) of 3.1.1b2.
Hat tip, of course, to KP :)
scott
--
Stay on
for redistribution of the resultant exe. This contrasts with
the 2.4.1 imaging-1680 exe which does not offer that admonition. This
might be a no-no for a project like LEAF :)
Thanks as always for LEAF, hopefully this is helpful to the project!
scott
groups, freeman wrote:
Hi, just starting
Hi, a few more things I noticed, my perspective is functional
differences between BuC 3.0b2 and BuC 3.1.1b2.
no shutdown facility
- /sbin/shutdown doesn't exist
- /sbin/halt has no '-p' (poweroff) option
=-=-=-=-=-=-=-
My setup: boot from CD using pure isolinux, cfg stored on floppy
davidMbrooke wrote:
there are some
other core i2c modules that come from source package i2c, (for example
i2c-dev, i2c-proc). Those are missing.
I found that the i2c-core.o and i2c-proc.o files from the BuC3.1.1b1
release worked on my BuC3.1.1b3 setup.
scott
KP Kirchdoerfer wrote:
Am Samstag, 6. Juni 2009 16:45:17 schrieb davidMbrooke:
there are some
other core i2c modules that come from source package i2c, (for example
i2c-dev, i2c-proc). Those are missing.
Thx for reporting;
corrected both issues for the next version.
kp
As a sanity
Under both Firefox IE getting err 400 for packages.
E.G. for BuC v3 packages, try:
1. 6wall.lrp [45 k]
gives link of:
http://leaf.cvs.sourceforge.net/*checkout*/leaf/bin/packages/uclibc-0.9/28/6wall.lrp?rev=HEADcontent-type=application/octet-stream
and resultant page:
===
An
wrote:
On Mon, 2010-07-12 at 11:11 -0400, groups, freeman wrote:
Under both Firefox IE getting err 400 for packages.
-snip-
Everyone,
I have an open ticket with SourceForge Staff concerning this issue.
http://sourceforge.net/apps/trac/sourceforge/ticket/11869
BB via WiFi, through a LEAF router (v3.1.1 something), works fine -
personal experience.
(If special ports needed to be opened then every open HotSpot would need
special config to support BB users ... so no special config being
required makes sense, right?)
I'd verify that your BB plan
Hi, taking a peek at BuC4. Wanted to check the packages page by clicking
on link on left side of LEAF's SF site, which sends me to:
http://leaf.sourceforge.net/bering-uclibc/index.php?module=pagemasterPAGE_user_op=view_pagePAGE_id=13MMN_position=33:33
However when I view the page in FF I get:
Sort of a brief, general question, having spent 8 hrs on this and gotten
nowhere.
I currently have LEAF uC v3.1.1b3 router, with extensive shorewall rules
for eth1 (my LAN).
If I want to migrate to using OpenVPN, road warrior setup (incl using
bridging and not routing to access the eth1
Hi, I'm testing with 4.2b1 and want to examine the
uncompressed-then-mounted contents of the initrd.lrp file.
On my running 3.1.1b3 I'd gunzip the lrp file via:
gunzip -c initrd.lrp /tmp/initrd.minix
and then loop-mount the output as a minix filesys ... but that doesn't
work now :(
First
There appear to be missing, from the current (v4) EasyRSA package, a
handful of files from the /usr/bin dir ... at least when compared to the
v3 EasyRSA package.
e.g. clean-all, build-ca, build-key-server, etc
FWIW I'm trying to follow the v4 VPN setup instructions at:
On 12/01/22 10:42, KP Kirchdoerfer wrote:
Look in /usr/sbin
My bad, I was in fact originally looking in /usr/Sbin.
I also noticed that clean-all is there, however the one I actually need,
build-ca, is definitely missing.
Cheers!
On 12/01/23 00:31, n22e113 wrote:
Try:
# /usr/sbin/pkitool --initca
# /usr/sbin/pkitool --server ${SERVER}
http://ubuntuguide.org/wiki/OpenVPN_server
I ended up just pulling in the missing scripts (from the easy-rsa/2.0
dir) from the OpenVPN source:
On 12/01/23 07:23, groups, freeman wrote:
I ended up just pulling in the missing scripts (from the easy-rsa/2.0
dir)
BTW the output of 'help easyrsa' displays the version 1.0 README file,
instead of what I think it should show, which would be the ver 2.0
README file.
Cheers thanks for LEAF
1) The 4.0 packages now download as files named '4_0_pkgname.lrp'
instead of the traditional 'pkgname.lrp' - I suspect this is unintentional.
2) The EasyRSA package that downloads as a singular package is not the
newest (i.e. it doesn't contain KP's addition of the 'build-ca'
script),
On 12/02/23 14:30, Robert K Coffman Jr. -Info From Data Corp. wrote:
I'm running it on older low end (P4 class) PCs with various NICs.
Me too.
I boot from old hard disks that spin down after boot.
Me, CD-ROM + floppy for config.
Is there some way I
could push a disk image onto those? I can
On 12/02/22 13:43, Robert K Coffman Jr. -Info From Data Corp. wrote:
The current release (4.2 beta) is too large for the root drive of my
storage (vfat /dev/sda1). If I move these files into a subdirectory
rather than the root of the hard drive, how do I reflect that in
leaf.cfg and
On 12/03/26 05:11, Andrew wrote:
26.03.2012 07:03, ads...@genis-x.com написал:
How do I change the order of NIC detection? or how can I force the system to
load e1000e BEFORE the igb driver?
Bering-uClibc_4.2_i686_syslinux_vga
{{ snip }}
Hi.
Just add e1000e in /etc/modules - it is
) output at all
times since diag output is pretty 'cheap' to implement, but it could
instead be set to only show this info if $VERBOSE is true.
Cheers thanks for LEAF!
On 12/03/31 05:41, Andrew wrote:
31.03.2012 00:27, groups, freeman написал:
On 12/03/26 05:11, Andrew wrote:
26.03.2012 07:03
On 12/04/10 16:57, davidMbrooke wrote:
Does anybody still use Floppy Disks?
I do (bootable CD, configdb and leaf.cfg on floppy).
I'd speculate this however - it's probably only the more technical (or
old-timer) people who use floppy, so they might be a group of users most
able to reconfig
My tor client (running on BuC 4.2b1) is warning me that the server
version I'm using is needing an update:
[warn] Please upgrade! This version of Tor (0.2.2.33) is not recommended,
according to the directory authorities. Recommended versions are:
0.2.1.32
0.2.2.35
0.2.3.10-alpha
On 12/04/16 13:06, KP Kirchdoerfer wrote:
[Tor version]0.2.2.35 has been committed to git and will available soon.
Thx KP!
Generally the packages are for 4.x, but kernel related packages for 4.2
only. We don't test newer packages on oler releases, though they may work.
Eeek! I've been using
I'm using BuC 4.2 beta 1, on an ASUS P4E mobo, using the sensors pkg.
My dmesg log is getting overrun with repetitions, every 7-8 secs, of
this pair of debug lines:
[ 687.583914] asb100 0-002d: starting device update...
[ 687.777041] asb100 0-002d: ... device update complete
and this is
I noticed that atop the DL page
(http://sourceforge.net/projects/leaf/files/Bering-uClibc/) it says:
Looking for the latest version? Download
Bering-uClibc_4.2-rc1_i686_isolinux_vga.iso (74.2 MB)
.. but wouldn't 4.2 release be a better (latest, finalized) version?
Cheers thanks for LEAF!
First, I somewhat conjoined two effects of these debug msgs from asb100
so let me clarify the effects and resultant problem (and modify the
subject line):
1) the debug msgs from asb100 (invoked via dev_dbg() in asb100.c) get
dumped into the kernel ring buffer, such that it gets outputted if
Seems as well to be the case for 5.1.6.
Cheers thanks for LEAF!
--
leaf-user mailing list: leaf-user@lists.sourceforge.net
is absent.
Cheers thanks again for LEAF!
On 15/08/10 12:44, kp kirchdoerfer wrote:
Am Sonntag, 9. August 2015, 04:58:18 schrieb groups, freeman:
Seems as well to be the case for 5.1.6.
It's missing since about three yrs.
The commit message by Yves Bluessaeu says:
This allow ezipupd to manage
I seem to need the an AMD 79C970 driver (which is fulfilled by PCnet32)
for my VMWare Player v5 testbed.
Trying BuC v5.2.7, I notice that the modules.sqfs filesystem contains no
"amd" dir under the 'drivers/net' subdir and since the pcnet32 driver is
stored in that 'amd' dir, it explains the
On 16/09/01 13:09, kp kirchdoerfer wrote:
> HI;
>
> Am Mittwoch, 31. August 2016, 19:49:43 schrieb groups, freeman:
>> I seem to need the an AMD 79C970 driver (which is fulfilled by PCnet32)
>> for my VMWare Player v5 testbed.
>>
>> [...]
> Yes you are right
Having setup BuC5.2.7 under a VM and gotten it all setup I went to run
it on my production machine (an old ASUS mobo with Semperon 3400+ CPU)
and came up missing some more drivers.
Of particular urgency is for me is the 'forcedeth' drive
(/kernel/drivers/net/ethernet/nvidia), since this is the
I just gave a quick test to the latest BuC branch and made the two
observations:
- starting up a new VM with default devices results in 5.2.8-rc1
installing drivers for all netcards
- manually adjusting the cfgfile of VMware, to use the aforementioned
"vmxnet3" driver, results in LEAF
66 matches
Mail list logo
