[leaf-devel] cdrom module support loading from leaf.cfg
Hi, I'm testing bering-uclibc 2.2 beta 4 The new leaf.cfg is really great ! But I tried to load the modules for ide-cdrom support ( cdrom.o , ide-*.o, isofs...) from the config floppy ( to be able to use the standard initrd.lrp) ( I was testing a kernel that crashed with the modules in initrd-ide.lrp ) So Here is my leaf.cfg - # This file is parsed as a shell script # Kernel command line parameters are available as KCMD_variable # ie: KCMD_LRP contains the LRP= portion of the kernel command line # NOTE: For kernel command line settings that do not include an equals # sign (ie: rw or similar), the variable is set to itself, allowing # for easy testing (ie: KCMD_rw=rw). # LRP and PKGPATH variables now support whitespace (space, tab, newline) # as well as commas for seperators. # Uncomment for more verbose execution. VERBOSE=1 # Other variables you might want to set in this file include: # LRP Packages to load # PKGPATH Device(s) to load packages from # syst_size Size of root ramdisk # tmp_size Size of /tmp ramdisk # log_size Size of /var/log ramdisk # Example: #LRP=$KCMD_LRP rsync #LRP=root hdsupp libm iptables keyboard p9100 upnp config etc local modules dnsmasq ppp pppoe dropbear weblet shorwall ulogd ezipupd squid-2 LRP=root wireless wireutil libm ulogd iptables keyboard config etc local modules uhotplug dnsmasq ppp pppoe weblet shorwall PKGPATH=/dev/fd0u1440:msdos,/dev/cdrom:iso9660 syst_size=32M log_size=4M tmp_size=4M insmod $MNT/cdrom.o insmod $MNT/ide-cor.o insmod $MNT/ide-cd.o insmod $MNT/ide-dsk.o insmod $MNT/ide-det.o insmod $MNT/isofs.o insmod $MNT/vfat.o -- but it didn't worked ;-( panic after linuxrc It seems that the /dev/cdrom computation done in /var/lib/lrpkg/root.blk.mk is done too early ( before leaf.cfg parsing) the packages cannot be loaded from /dev/cdrom After discussion with Eric Spakman, it seems that the /dev/cdrom computation could be moved to root.dev.mk that's executed after leaf.cfg parsing Charles ?? any clever idea ??? Kind regards, Etienne Charlier --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Strange behavior with wireless
Hi, I'm trying the use a wireless pci card ( usr 2216) based on a acx100 chipset I driver is being written for this card ( acx100.sourceforge.net) I managed to make it work with bering 1.0 ( glibc based , kernek 2.4.18) On the same hardware, I exhange the cd floppy with a bering 2.2 beta3 based configuration, and I cannot manage to make it work It seems that the ifup command doesn't open the card, The iwconfig commands put in the interfaces file get executed but I don't see the log entry from the driver specifying that the card is being upped the ifup complete successfully but - there isn't any route to this interace in the ip route print listing - the ip addresss seems to be assigned ( ip addr list displays it) Any though ??? Kind regards thanks in advance ! Etienne --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Newbie question about applying the patches to compile the bering kernel
Hi, I'm trying to transform an old laptop into a wireless accesspoint It's fitted with a prism54 based wireless card and a 3C575 ethernet card. I need to recompile the bering kernel I'm following the kernel.txt file in the cvs repository ( 2.4.26) but I cannot find the correct syntax for the patch command to be used to patch the kernel. assuming KERNELDIR=/usr/src/linux-2.4.26 PATCHDIR=/home/bering/leaf/src/bering-uclibc/configs/kernel/2.4.26/patches PATCH1=helpers-2.4.26.patch.gz what would be the patch command that must be applied ?? Many thanks Etienne Charlier --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Fw: [leaf-devel] ANN: Bering-uClibc 2.2 beta3
2nd try ( without attachments) checkout.cmd: - cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/leaf login cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/leaf -z3 checkout bin/packages/uclibc-0.9/20 cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/leaf -z3 checkout bin/bering-uclibc/beta cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/leaf -z3 checkout bin/bering-uclibc/packages --- UpdateImage.cmd - set CVSEXE=c:\Program Files\cvsnt\cvs.exe set BASEDISK=d: set BASDIR=buc21 set BASE=%BASEDISK%\%BASDIR% set CVSLOCAL=%BASE%\bin set CVSPACKAGES=%CVSLOCAL%\packages\uclibc-0.9\20 set MYPACKAGES=%BASE%\MesBrols set DISKCONTENT=%BASE%\diskcontent rem %MODULESDIR% contains the module tarball extracted( no tar on windows...) set MODULESDIR=lib set FLOPPYIMAGE=%BASE%\floppy rem 1. Update packages From cvs cd %CVSPACKAGES% %CVSEXE% update -R cd %BASE% rem 2. Cleanup diskcontent rd %DISKCONTENT% /s /q md %DISKCONTENT% rem 3.0 copy modules directory xcopy %MODULESDIR%\*.* %DISKCONTENT%\lib /ei rem 3.1 copy initial packages copy %CVSLOCAL%\bering-uclibc\packages\*.LRP %DISKCONTENT% rem 4. copy packages from cvs directory copy %CVSPACKAGES%\*.LRP %DISKCONTENT% rem 4.9 overwrite with beta directory copy %CVSLOCAL%\bering-uclibc\beta\*.* %DISKCONTENT% rem 3.2 rename kernel ren %DISKCONTENT%\linux-2.4.24.upx linux rem 3.3 rename syslinux.cfg del %DISKCONTENT%\syslinux.cfg rem 5. delete initrd del %DISKCONTENT%\initrd.lrp rem 6. Rename initrd-ide-cd -- initrd ren %DISKCONTENT%\initrd_ide_cd.lrp initrd.lrp rem 7. overwrite with my packages copy %MYPACKAGES%\*.LRP %DISKCONTENT% copy %MYPACKAGES%\isolinux.bin %DISKCONTENT% copy %MYPACKAGES%\isolinux.cfg %DISKCONTENT% copy %MYPACKAGES%\syslinux.dpy %DISKCONTENT% rem end cd %BASE% rem build iso image mkisofs -o beringuclibc.iso -b isolinux.bin -relaxed-filenames -c isolinux.cat -no-emul-boot -boot-load-size 4 -boot-info-table -hide isolinux.cat -hide isolinux.bin -l diskcontent :end - - Original Message - From: Etienne Charlier [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, June 06, 2004 12:41 AM Subject: Re: [leaf-devel] ANN: Bering-uClibc 2.2 beta3 Hi, Please find attached a copy of my scripts... not everyone will be hapyy, they're .cmd files ;-) it's really something I did to help myself, I could polish it if someone is interested The first script does a checkout of the needed part of the cvs repository the second builds an iso image from- - the standard packages - the optional packages - a pre extracted module tarball - my private stuff I tried isolinux to build the images ( with instructions from the bering user's guide) and it worked on all my firewalls ( the only pb, were with old cdrom drives that cannot read cd-rw disks ...) By the way, While trying the bering-uclibc 2.2 with leaf.cfg, i noticed a lot of wiered error messages and if turned ou that I edited the leaf.cfg located on my config floppy with notepad on windows,... the newlines made the linuxrc script sick ;-) would it be very difficult to strip the \r from those files while reading them ( at least for the files that are supposed to be stored on the config floppy ??) For me, it's easier to put the floppy in my xp machine to edit leaf.cfg versus mounting the floppy, edit , unmout... Now, i use ultraedit to edit the file but for the one trying for the first time, it can be annoying... Kind regards, Etienne - Original Message - From: K.-P. Kirchdörfer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, June 06, 2004 12:00 AM Subject: Re: [leaf-devel] ANN: Bering-uClibc 2.2 beta3 Hello Etienne; Am Samstag, 5. Juni 2004 23:30 schrieb Etienne Charlier: Hi, I wrote a smal script that build an iso image from the cvs repository ( leaf/bin/bering-uclibc and leaf/bin/packges ) Hey, that sounds interesting. What approach do you use to make the iso-image bootable (isolinux or bootdisk.img)? I vote for bootdisk.img (as used in Dachstein and the images I provided so far for Bering-uClibc), because it's capable to boot on older machines as well. will the beta 3 packages be put in the beta area ( leaf/bin/bering-uclibc/beta) ?? I cannot find the initrd_ide_cd for beta3 ... They will - just give us some time - and I have to confess you are the first who asked for those beta packages. We appreciate that someone is aware of it. kp --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel --- This SF.Net email
Re: [leaf-devel] ANN: Bering-uClibc 2.2 beta3
Hi, I wrote a smal script that build an iso image from the cvs repository ( leaf/bin/bering-uclibc and leaf/bin/packges ) will the beta 3 packages be put in the beta area ( leaf/bin/bering-uclibc/beta) ?? I cannot find the initrd_ide_cd for beta3 ... Kind regards, Etienne Charlier - Original Message - From: K.-P. Kirchdörfer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, June 04, 2004 6:52 PM Subject: [leaf-devel] ANN: Bering-uClibc 2.2 beta3 The Bering-uClibc team releases Bering-uClibc 2.2 beta3 This release includes a new/improved modules loading as you know it from Dachstein - the so-called bang commands. It has rewritten for Bering(-uClibc) by Charles Steinkuehler. On the base image dnscache and dhcpd has been replaced by dnsmasq, provding the same and more features by occupying less space on the floppy. You'll find a new chapter in Bering-uClibc User's Guide about using dnsmasq. Additionally shorewall has been updated toversion 2.0.2f and a few bugfixes in different packages - including the fix for the mail command. For a complete changelog please read: http://leaf.sourceforge.net/mod.php?mod=userpagemenu=91003page_id=39 You'll find the image plus ipv6 drop-in replacement in FRS: http://sourceforge.net/project/showfiles.php?group_id=13751package_id=67534 Suggestions, reports and fixes are welcome. kp --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] could Swapon/off be included in the next release of bering uclibc
Dear bering uclibc dev team ;-) swapon/off disappeard from busybox somewhere between dachstein and bering... I used to use an heavily modified bering release ( glibc2.2,...) ( cdrom boot, openvpn, upnp,...) I used the squid binary from a redhat 7.3 distro I had to put an old version of busybox ( dachstein ) plus a couple of links into local.lrp in order to be able to activate swap I think that those applets have been removed from Bering due to the lack of space on the standard floppy Now that - bering uclibc has more space left on the floppy, - some squid related work has started in buildtool could it be possible to add back those 2 applets to busybox ??? ( my old busybox from dachstein won't work on uclibc) Many thanks for your hard work !! Kind regards Etienne Charlier --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Bering Crew looks for expansion
Hello, I'm Etienne Charlier, I live in belgium. I'm sofware analyst/developper since 15years I've been doing Operating system development ( Assembler 370), C/C++ Windows DNA applications, now, i'm working in a 10 people team developping software for customers ( in .NET) Please forgive my english a little bit ( Frenchie) ;-) .. good you can just read me, not hear me ;-) I follow this list since its beginining ( and before on the original lrp mailing list) and I'm really impressed by the level of expertise of all the developpers.. I have +/- 12 bering installed ( some of them running from floppies), most of them running from CD 6 are connected by pair through openvpn tunnels ( only vpn software that I managed to configure when both ends on the tunnel are on volatiles IP addresses ( ADSL PPPOE)) squid, ..tinydns,... I started customizing bering uclibc 2.0 - I managed to make a package with linux-igd ( upnp support) CVS version ( for now staticaly linked) thanks to the http://www.fastflow.it/floppinux/bering/index.html page but by rebuilding the package myself - I'm trying to master the bering-uclibc build environment and trying to make a package with openvpn ( a little bit hard for a .NET /DNA developper/architect ;-) ) - I would also like to make run the dsl_qos_queue program ( http://www.sonicspike.net/software/ ) - A few years ago ( my posts are on the list archive ) I started developping an alternate configuration system based on a unique configuration file stored on the boot floppy ( outside of the .LRP) used to process configuration file templates ( a call was made to a setup.sh or something like that at the end of the linuxrc script). That script generated the actual configuration files that overwrote the one from the packages. - I'm really interested by contributing to the web interface/cdb configuration system mainly for the soho release.. something like the web interface of the router/accesspoint/adsl modem appliances available in the stores ( usrobotics, linksys) - I'll have some spare time ( but disconnected from the Internet) during the End of year hollidays and I would be really interested by learning more deeply the cdb stuff written by Eric Chad Now a survey ??? What would be the advantage and drawbacks of merging the Bering Bering-uclibc distributions ? What would be the advantage and drawbacks of keeping the Bering Bering-uclibc distributions separate ? IMHO, I think that we don't need 2 separate variantes of bering. What do the others gurus think about that ??? Etienne Charlier [EMAIL PROTECTED] - Original Message - From: Erich Titl [EMAIL PROTECTED] To: Eric Wolzak [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, December 18, 2003 11:24 AM Subject: Re: [leaf-devel] Bering Crew looks for expansion Eric At 23:31 17.12.2003 +0100, Eric Wolzak wrote: Hello everybody, As you might know , Jacques has stopped, and gave the rudder to me. My plans with Bering are. 1. update kernel to 2.4.23. 2. update packages 3 revise the documentation and make some improvements. 4 create a basic webinterface. 5 cleanup linuxrc. 6 create a bering light for the soho environment with few options. 7 Translate the Bering Documentation This all under the following conditions A I want to keep rather close to the bering-uclibc group. B A floppy distro should still be possible. But I know I will need help with those plans :) Are there any volunteers for come aboard . Looks like a major issue, I am interested to see this move on. I am about to deploy a few boxes with specialised hardware based on Bering which needed kernel tweaks anyway. Those have been adapted by Eric Spakman for Bering uClibc. I was discussing the differences between the two distributions with members of the Bering uClibc team. I believe the kernel work could be a joint effort. I will try to move my modified kernel to 2.4.23 anyway, based on Jacques' 2.4.20 config and on the kernel building description by the uClibc team. So count me in for this. I don't know to what level Jacques has standardised the package building process. I believe the work done in the uClibc crew is remarkable, it might well be worth the effort to use it for glibc based Bering too. I believe closing ranks with the guys from the uClibc group is worth it, most of your points up there may apply to both distributions. Well what the heck, count me in with the limited time I have... Erich THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78alloc_id371op=ick ___ leaf-devel mailing list [EMAIL PROTECTED
[leaf-devel] myconfig.lrp was Template system [was Webconfiguration]
Hi, I followed with great interrest the discussion.. My 0,02 euros ( more than 0,02 $ ;-) ) ( forgive my frenchie english..) I few months ago ( maybe a year) , I faced the task of maintaining a dozen of leaf boxes ( dachstein at that time) with similar config but quite different that the released versions ( pppoe,ez-ipupdate,...) Here is a small explanation of what I did ( I didn't yet upgraded it to bering). My design goals - keep the downloaded packages untouched by my tweakings mainly don't modify linuxrc,... - ease the preparation of a new leaf instance only config.cfg must be modified - I have a clear view of what I changed from a released version ( all is in myconfig.lrp) I have a - package called myconfig.lrp - A script (config.cfg) stored on the floppy out of the package containing only val=value lines ( internal net, ezipupdate username and host name,) in the myconfig.lrp - a script /sbin/unconfigured.sh that gets called after the package extraction and before init - a directory /myconfig /myconfig/templates/packagename/*.tpl where package is a the name of the .lrp ( dhcpd, dnscache,ez-ipupd) a flat file called /myconfig/template.conf containing #--- package template destination user group permissions dhcpddhcpd.conf.tpl /etc/dhcpd.cong root root 777 #- the template files ( *.tpl) contains template of config files ( dhcpd.conf,...) with tags like ##INTERN_IP## that references the INTERN_IP variable defined in the config.cfg file. the unconfigured.sh gets called by the startup process after everything is has been extracted into the ramdisk and before init. it does: - translate the config file into a sed script that will replace the ##VAR## with the value - for each line in /myconfig/template.conf - if it doesn't find a variable CONFIG_PackageName=Yes in the config.cfg, it skips that line - else, it passes the template throught sed using the generated script and (over)write the real config file with the output. - it changed to owner, group and permissions - end for. there also a small script that directly copy files from a directory on the floppy somewhere in the ramdisk ( with a config files ) this is used for files like the ssh keys files, /etc/passwd, ... I think we could extend the idea - make a friendly user interface to the config.cfg file ( web or other) - split the config.cfg in a few files ( like etc/sysconfig in redhat) but we need to centralize the definition of the contents of config.cfg Regards, Etienne PS: I keep seeing fat 8.3 file names, isn't it possible to move to fat32 compiled into the leaf kernels and modify the mount command to use fat32 instead of msdos ,??? - Original Message - From: Greg Morgan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 03, 2003 11:44 AM Subject: [leaf-devel] Re: Template system [was Webconfiguration] Matt Schalit wrote: o All the types of variables used in all LEAF distros must be collected and given a type name. My presupposition is that the LEAF lrp archive is a great tool. It is great for what it does. Its that just that the gziped tar archive is not easy to edit by hand. In any system that evolves from these discussions, the system has to have an implementation plan. I don't believe this is complex at all. Where does a project like this start? I think you have to go and survey all the files and variables that a CGI GUI or other more user friendly system would display for the user to edit. How would any program know where to find these variables to edit, if you didn't know what package they were in or even which file that they are in? How will you know what priority a package will be on an implementation plan, if you cannot survey its importance in the larger scheme of all packages? The template system I started to describe here is executed externally from the LEAF image. It does not use the LEAF footprint to work in. The result of running a modified Anaconda installer it to spit out LEAF images. The XML is not stored with the working LEAF Image. If the resulting GUI system is not mature enough to support all desired edits,then the floppy image can still be hand edited where support is lacking in the GUI. http://www.mail-archive.com/leaf-devel%40lists.sourceforge.net/msg06097.html So I think there are two camps evolving in this discussion. Three sir. Two camps trying to edit all this information via a web GUI, and the third camp is my proposal. The third camp is a system using Python programming that is hosted on a full featured platform using templates. The Python GUI would allow a person to develop more full featured GUIs, if is not running on the target LEAF platform. This still presumes we are taking about say a 16meg host. In a way the third camp could be likened to a cross compiler. XML. That's where I remember this whole idea coming to a halt a year or so ago, when somebody suggesting using this and I
Re: [Leaf-devel] is Bering GNU?
Hi,
Forgive me my poor english. I cannot express my ideas very cleareley.
( at least not with the calm and precision used by Ray ;-) )
0. It's quite amazing that such a great product has been developed
and integrated by a few people during part time ( when do they sleep
??? )
1. I'm not a leaf contributor. I just use the binaries ... and I like them
You looked at the sourceforge.net but you missed the most usefull part
of the site the mailing list archive ( a gold mine for the one who
try to use it )
2 This list was the most polite and fair a ever seen ... till you came
( maybe i'm a little bit too hard but I cannot express it more correctly )
(remember the dns resolver thread ??? )
3 You seem very upset by not being able to {use | install} bering on your
system and you feel better if you can put the responsability on someone
else.
Just my 0.02.
PS: Bering crew: Great job...
Etienne Charlier
- Original Message -
From: George Georgalis [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Saturday, July 13, 2002 7:55 AM
Subject: [Leaf-devel] is Bering GNU?
Is Bering GNU?
I'm beginning to have my doubts. Where is /usr/src/linux/.config? Where
http://leaf.sourceforge.net/devel/jnilo/bering/rc3/Bering_1.0-rc3.config
are the other compile time options for other binaries? Just how was
Bering_1.0-rc3_img_bering_1680.bin made?
After spending a good part of a week, and _all_ day Friday getting up a
Bering router before a deadline -- subsequently missing the first day of
a conference http://h2k2.org -- I looked back at what was the problem. I
discovered I was hacking around a product (the Bering image) much like
the manner of before I used Linux. I have this disk image, that I mount
to find, compressed archives, containing finely tailored scripts and a
handful of binaries. Together they make up the GNU Bering. (And maybe
other leaf versions as well.)
I have hunted all over http://leaf-project.org and
http://leaf.sourceforge.net/ for the source, or even a file that says
version xx.yy.zz of busybox was compiled with the following patch and
http://leaf.sourceforge.net/devel/jnilo/bering/rc2/Config.h
compile time options. Or maybe a tgz of the /usr/local/src/bering where
the image was made? Nothing. I find myself writing scripts to extract
and compress lrp files. Surely everyone doesn't gzip -c9 what they made
by tar cf after mounting and extracting their first floppy image? Is
this the intended way to indoctrinate new developers to the old school?
I even asked a few well read LUG groups what the lrp format was, or
how I could run the lrcfg that I read about without actually booting
the distro. Nobody knew because the design is not conducive to group
development, it's intended use is like that of proprietary software --
take the binary, configure it with the configuration menu and be like
everyone else.
Okay, I just found the developer.rtf and scanned the whole thing.
Formidable task, but I only see part of the forest and none of the
trees. I already know linux and there seem to be some very specific LRP
details in there, but will it be done before it's out of date? I'm
not saying produce a `./configure make make image` but if the
environment for building the release was published, or easier to find,
I'm sure there would be a lot more community support. At one point I
kicked myself for not looking in CVS before, but when I got in there,
was in disbelief -- no source, only doc.
So now I have problems with my image to resolve, why do those Belkin
cards detect as reltek under RH but, none of the Bering modules will
work with them??? How will I ever get my tulips back from my boss so I
can test an image at home? What am I going to do about making an image
and quickly changing a few parameters (ssh host keys, network, firewall
and other site information) or major structure (LaBera, ppp, ipsec,
dns) without spending a ton of time hand extracting and compressing
components? I'm going to make my own distribution. reBering. Complete
with scripts to mount and extract all the subcomponents, global
configure, mix'n'match packages, compress and unmount. Only I don't
think I can call it GNU because since I'm in a hurry, I won't have time
to reverse engineer the compile time options and source. I'd rather work
on putting it on an eprom anyway.
In all sincerity, Bering is very cool. It could just be a lot better
if it was more in the spirit of _encouraging_ open source development
rather than barley qualifying, actually I bet if it was audited, it
wouldn't pass. If there are scripts to tar and gzip a lrp package,
why aren't they part of a tools.tgz right beside package_src.tgz and
compile_configs.tgz next to the Leaf_UML packages and extraction
instructions for odd archives? I know asking for doc is a lot, but
maintaining a file of command lines used to make
Re: [Leaf-devel] request for Bering packages + a couple squid comments
Hi, Some comments below - Original Message - From: Fabrice LABORIE [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, July 13, 2002 2:06 PM Subject: [Leaf-devel] request for Bering packages + a couple squid comments Hi List, I am using a Bering system booting from HD. I am new to Bering ( and LEAF ... and LRP !) and I have to say I am VERY impressed!!! You're not the only one ;-) Even I everyone isn't sharing your opinions ;-) I use a few packages including sshd (Nathan Angelacos) / squid (David Douthitt). I read that Jacques will upgrade sshd in Bering1.0 final . so that's great... maybe David will offer a more recent squid ? ( squid-2.5.PRE8 or 2.4.STABLE7 ( or maybe Jacques will offer one for Bering?) http://leaf.sourceforge.net/devel/kapeka/ You'll find there a more recent version of squid but AFAIK, it's compiled wtih glibc 2.1 You'll find there http://www.wix.net.nz/LEAF/ some instructions how to upgrade the glibc.. David, may I suggest to start squid in init.d/squid with -D to prevent squid from stopping if the DNS server is not available yet? ( patch : diff -ur squid/etc/init.d/squid squid.fab/etc/init.d/squid --- squid/etc/init.d/squid 2001-12-12 22:09:30.0 +0300 +++ squid.fab/etc/init.d/squid 2002-07-02 19:57:37.0 +0300 @@ -17,7 +17,7 @@ chown squid.squid /var/run/squid.pid cd /usr/bin umask 077 ; ulimit -nH 8192 ; ulimit -nS 8192 - $SQ + $SQ -D echo touch /var/lock/subsys/squid ;; ) also I suspect that most people using squid will be using a harddrive of will have tons of RAM, but still, providing the squid.conf.default and mime.conf.default might not be necessary and save a few bytes of .LRP. [ As a side issue, I used libm.lrp on my Bering install and noticed that the var/lib/lrpkg/libm. were not extracted... and that they ended up beeing backup in my root.lrp ] and finaly here is my request for a new Bering package: the documentation http://leaf.sourceforge.net/devel/jnilo/bubooting.html 9.4. Booting from an IDE device suggests to use a windows or linux rescue disk to prepare the hd. why not using a Bering Floppy ??? It would be great to have fdisk mkfsdos, mkfsreiser [ yes I am using reiserfs for my squid ] and syslinux packaged into one HDinstall.LRP. note: i have seen [ not used ] fdisk+mkfsdos + syslinux on different package from David so I suppose one could copy them all . onto the bering floppy( but still no mkfsreiser! ). any comments? We're waiting for you to build this package ;-) ;-) ;-) ;-) ;-) fabrice. Regard, Etienne Charlier --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] Tip about the modification to upgrade to libc 2.2
Hi, I used with success the Simon Blake's instructions to upgrade Bering to Glibc 2.2 I had a small problem and I found the solution by myself but I think I would be usefull to put some comments in the mailing list archive... I built the initrd and root.lrp on a RedHat 7.3 running on a VmWare on My Laptop. I burned a bering cd with those files and I tested it on a PII 350 pc ( the only one in my home able to boot from a CD-RW disk... I worked... I burned a CD-R to use in my production machine ( a P133) and patatra the first instruction in linuxrc gave me an error message more or less like signal 4 sent to linuxrc. After some research, I found that my laptop is a PIII processor and the glibc installed by redhat is compiled for i686... I reinstalled redhat on an old hd on the P133 and I rebuilt the initrd/root from that machine and I could boot that CD on the P133 Just my 0.02 E= Etienne Charlier --- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] Hi there, and (bug?) report
Hi, So either something is weird on my host (bering 1.0rc2), there's a bug in the backup scripts somewhere, or the documentation is not quite up to par... I had the same problem when trying to build a package for openvpn ( openvpn.sourceforge.net) I think that the documentation doesn't (yet) describe the changes in the dachstein backup scripts made ( by Charles) to support the partial backup when he released dachstein CD Just my 2 (euro) cents Regards I haven't checked anything much, but I thought I might as well let you all know what I found... cheers, Jon Clausen --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] Two new packages: Newest CIPE and QoS (Fair Queing)
a LOT of peer-to-peer downloading kazaa etc... have a nice WE regards, Etienne - Original Message - From: Sandro Minola [EMAIL PROTECTED] To: Etienne Charlier [EMAIL PROTECTED]; Leaf-Devel [EMAIL PROTECTED] Sent: Friday, March 29, 2002 10:04 AM Subject: RE: [Leaf-devel] Two new packages: Newest CIPE and QoS (Fair Queing) Hi Etienne, hi all A small question, I've modified your previous package quite a lot, ( make it work bewteen 2 routers connected with pppoe ( very dynamic addresses), and use some central configuration file of my own. Could I just take the new cipcb.o and ciped-cb binaries and drop them on my systems or is there some configuration file changes that must be done ??? Yes, changing the two binaries (module and executable) is enough. Even the new CIPE package only consists of these two binaries. I also checked the sample config files: your parameters still work. The sample file looks the same (I couldn't find any new parameters) If you like, I can upload the binaries to a seperate folder. I'm also very interested with your qos package as one of my customers use the tunnel mainly to access a machine with telnet through the tunnel. Should I install it ( on a dachstein cd ) Hmm, does your customer do other things with his internet link or only access the telnet server through one tunnel? --- Sandro Minola | LEAF Developer (http://leaf.sourceforge.net) mailto:[EMAIL PROTECTED] | mailto:[EMAIL PROTECTED] http://www.minola.ch| http://leaf.sourceforge.net/devel/sminola ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] New FAQs for CVS and Site Mirroring
Hi, Does one know how to setup a CVS client to be able to contact a CVS repository ( Sourceforge or another one) when the client is behind a proxy/firewall (at work) only allowing traffic through an http proxy server ? At home, I could set something up with Dachstein to make the whole thing possible Tanks in advance Etienne Charlier - Original Message - From: Mike Noyes [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, March 10, 2002 12:41 AM Subject: [Leaf-devel] New FAQs for CVS and Site Mirroring Everyone, I just created the following FAQs. Comments and suggestions are welcome. CVS Setup https://sourceforge.net/docman/display_doc.php?docid=9960group_id=13751 Site Mirroring https://sourceforge.net/docman/display_doc.php?docid=9961group_id=13751 -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] How to keep config files separate from the packages ( answer)
Sorry if a repost Hi, Whith the release of dachstein CD (I didn't tried it yet), I think it's time to explain what I am coding now. ( It's not yet ready for a release but you can get the ideas. I might be usefull to store config files on a floppy Introduction: I consider myself as a 'semi-idiot' creating EigerStein/Dachstein for a dozen of super-idiots All of them have the same kind of Internet connexion (ADSL with pppoe). Some of them wanted to have secure tunnels between 2 leaf so I had the requirement to change the internal network addressing quite easily Goal: - How to keep the configurations files separate from the rest of the packages - How to manage the modifications made to configuration file so that I can remember what I did some months before. - How to ease some manipulations of the config files Acknowoledgments I stole a lot of ideas from Oxygen, EigerStein, Dachstien, fli4l And added a few of mine ;-) I want to thanks the LRP/LEAF gurus for building such a great thing...) the leaf project is really a gold mine for the one who wants to learn shell programming Design The Main idea is to keep copies of modified configuration files in the /myconfig directory copy them in the right place early in the boot process. the template of config files contains tags that can be replaced by the actual values stored in a file on the boot device (out of the .lrp easier to edit whithout booting the floppy) Description I've built a package called MYCONFIG.LRP that contains -- a directory called /myconfig /bin : some scripts /templates: templates of config files stored in subdirectories bu package name (see templates.conf) /sbin: some scripts copied to /usr/local/sbin ( tools) /config : folder containing the copy of the config directory stored on the boot filesystem out of the packages myconfig.txt contains variables definitions /scripts : scripts that are called by the unconfigured.sh to setup things that cannot be done with the templates ( creating the dnscache file /etc/dnscache/root/ip/internal net -- a script in /sbin/unconfigured.sh Files: /myconfig/templates.conf This file describes the templates. it has the following format Package template destination owner group perm package: package owning this config file template: name of template in the /myconfig/templates/$package directory destination: full path name where the file must be put owner group perm ( if present, chown chgrp chmod are done on the dest file /sbin/unconfigured.sh this script (if present, of course ) is called by the boot process after packages extractions and before the /etc/init.d it calls /myconfig/bin/setup.sh ( todo: change this filename) /myconfig/bin/setup.sh this scripts does the following - temporarly mount /proc because it will be mounted later during the boot - mount boot device - install all package stored in /boot/addons ( to overcome the command line lenght limit) - look in /boot/config for the first file named *.cfg (eg. a.cfg ) - if found copy it as /myconfig/config/myconfig.txt - copy all files from /boot/config/a/*.* to /myconfig/templates/config that way I can store out of the packages all configuration data - variables from myconfig.txt - other templates (ssh key files...) - call /myconfig/bin/processtemplate - call all scripts in /myconfig/scripts - unmount /proc and boot device /myconfig/bin/processtemplate this script converts the myconfig.txt file into a sed script in: var=val out: s/##var##/val/g for all templates in /myconfig/templates.conf execute the sed script write the output at destination pathname set owner group and permissions next Conclusions. It's working but not yet finished. I wanted to store all my modifications in a new package so that a can simply overwrite a .LRP with a new one without losing my changes. How to use. - basically instead of modifiying a config file from the menus, you copy the file in the /myconfig/template/xx.in - edit it to use the ##tagname## if it's defined in the myconfig.txt - or simply edit it - backup myconfig.lrp. if you want to upgrade a package, you can replace the old one with a new downloaded one and review the config file to compare it with your template. TODO: better comment_stripping ( remove LF if file editied in dos/win) ..bug fixes documentation URL: http://users.skynet.be/Etienne.Charlier/myconfig.lrp If this can give some ideas to the true gurus, . It's just a draft, I'm coding/testing before writing docs... ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] lrpStat
Hi did you tried APPLET . WIDTH=100% HEIGHT=100% Bye Etienne Charlier - Original Message - From: Charles Steinkuehler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 27, 2001 6:17 PM Subject: [Leaf-devel] lrpStat I'm in the process of adding lrpStat to the weblet pages of Dachstein, and have a question. When I run the java applet in a web browser, it has a fixed size, specified as width and height in the applet tag. If, however, I run the application from the command line, I get a scalable window. Does anyone know how to get the applet to pop up in a scalable window when it's loaded from the web page? Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] lrpStat
Hi,
Try this ( just modify the inital size width height )
Could someone test it with netscape, I don't have it installed on my
machines
--
HTML
HEAD
TITLEtest openwindow/TITLE
SCRIPT LANGUAGE=Javascript
function winopen()
{
window.open(netmon.html,monitor,resizable,height=100,width=300);
}
/SCRIPT
/HEAD
BODY
A href=netmon.html target=monitor onclick=winopen();H3Bandwidth
Monitor/H3/A
/BODY
/HTML
-
- Original Message -
From: Charles Steinkuehler [EMAIL PROTECTED]
To: Martin Hejl [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, September 27, 2001 11:26 PM
Subject: Re: [Leaf-devel] lrpStat
Does anyone know how to get the applet to pop up in a scalable window
when
it's loaded from the web page?
I guess it is possible already, by using javascript to bring up a new
window
(preferably without any navigation and URL toolbars), so it'll look just
like one of those annoying ads that are part of some sites. As Etienne
pointed out, in this case you'd have to use WIDTH/HEIGHT=100% in that
case).
If that's not sufficient, I could extend the applet to (optionally) run
in
a
separate frame
I've got the applet launching in it's own browser window, but it's still
got
the toolbars, menus, and such. If someone can point me towards some
java-script to pop up a 'borderless' window, I'd appreciate it (I'm not
much
of a web design guru).
(but let me know quickly, since I'll be on my way to the States for two
weeks on sunday, so I won't be doing any work on that during that time).
I
guess there's not much chance of meeting anyboy in the Andover/Boston
area
over the next two weeks? ;-)
Well, I don't know where everyone else is, but I'm in the middle of the
country (Kansas), so you probably won't be bumping into me ;-)
Basically, my idea was that the applet was included in a whole page of
infos
about the system (like, all the information that's displayed by the
weblet
pages), and the application was for viewing _only_ the network stats.
That's how I'm configuring things...see:
http://216.171.153.180
Assuming the system stays online...I don't know how weblet will handle
being
hit by all the nimda probes now that I've opened it up to the world...
Let me know if there is something I should do - I would gladly do so.
Heck,
I already feel honoured that it'll be included in your dachstein
release.
I always wanted to include the stats package...sadly, this is the first
time
I've re-rolled a release since you got it running sigh.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] YATALWI
Very interresting idea
I think that we could split the project in 3 parts
1. define a set of configurations files à la network.conf but
with ONLY shell variables definitions (maybe split into
smaller files like the RedHat sysconfig directory)
Those files could be sourced by ALL the init.d scripts
to get parameters values to configure the {deamons| packages}
2. use a system like you describe to allow the editing of those
configuration files through SSH
3. develop a web/ncurses interface around the SSH interface
Not a small project !!!
- Original Message -
From: Scott C. Best [EMAIL PROTECTED]
To: Etienne Charlier [EMAIL PROTECTED]
Cc: Eric Wolzak [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, September 17, 2001 10:09 AM
Subject: Re: [Leaf-devel] YATALWI
Etienne:
Heya. Over the last year, I pitched my company's
'echoWare' solution to a number of OEMs, including heavy-iron
OEMS, SOHO-router OEMs, and garage-mode last-mile broadband
wireless gateway startups. Everyone I've spoke with agrees
it's a strong model for the future, but faces an enormous
adoption problem: a Fortune-500 OEM simply *cannot* put
anything into the box unless it's an industry standard. Put
another way...even if a sh!tty, insecure, bloatware protocol
becomes an industry standard, they don't just feel compelled
to support it, they are *proud* to support it. It can be very
frustrating: talk to them about a novel, lean, SSH-based
remote-management architecture, and they ask for SNMP, UPnP,
Passport, or 802.1X.
Not that this surprises me. :) But the doubly
frustrating part is that this resistance affects my ability
to raise funds to support a development staff to actually
release some code that could, who knows, someday actually
become pervasive. Perhaps it's a Peter-principle of mass
market products: they are forced into this awful state of
standardized mediocrity.
/rant off
Anyhow.
The idea behind echoWare is that you run an SSH
service on the machine you want to administer, and exchange
simple ascii directives to that machine to affect its
configuration. You can make these directives as machine
friendly as you want: importantly, the actual *user
interfaces* is filtered by a remote web-server. So, the
end user connects to this website, and that server opens an
SSH connection back to the end-user's gateway, pulling out
ascii config info, and turning it into an HTML picture. Only
takes a second or two in our demo. End-user can now point
and click to make configuration changes, which go up to
the server over SSL, and back down to the gateway over
SSH.
The primary benefit is the cost of the software.
The gateway only needs to run an SSH daemon (which usually
comes from free), and an ascii parser, which bash and sudo
handle well enough. Might be worthwhile to customize the
shell, too, so that only a limited set of commands is
available to the ASP server. Given this...you can load up
all the heavy lifting (graphics, os-specific ifdef's,
etc) on the server, which has the CPU, memory, and storage
to spare.
Anyhow, we call it echoWare here, and someday it'll
actually move beyond the demo phase: I'm hoping to attach
EchoWall 2.0 to this service. So instead of editing the
echowall.conf file by hand, you'd connect to a website, tell
it what services to enable, and it sends the sed commands
into the box, and updates the echowall.rules file if needed.
Very visual for the end-user, but very ascii for the gateway.
Anyhow...hope this helps, somehow. Got something
of a demo running if you'd like to kick the tires around.
Got another meeting this week with a major vendor to talk
about it some more. :)
cheers,
Scott
On Sun, 16 Sep 2001, Etienne Charlier wrote:
Hi,
Since last year ( when I discovered LRP), I think that there was at
least
3 or 4 threads about a web interface to a LEAF derivative.
I would like to start a brainstorming on the feasability/usefullness of
a Web interface for the LEAF project.
what people think about
- usefullness
- would it be secure enough
- technologies to use ( scripting languages ,..)
- is there some exsiting project that could be reused ( I've heard about
Webmin)
- other secrets wishes that you have about LRP/LEAF
happy brainstorming
Etienne Charlier
- Original Message -
From: Eric Wolzak [EMAIL PROTECTED]
To: Etienne Charlier [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Sunday, September 16, 2001 10:37 PM
Subject: Re: [Leaf-user] thttpd CGI Forms for administrating Firewall
through browser
Hi Etienne, Sandro and the rest of the list
I'd be happy to contribute to a web interface for LEAF
If there are more people interested, we could join our efforts :=)
Here are some ideas
First of all, the combinaison LRP/Kernel 2.4/Shorewall is not yet
very
common in
the LRP world and I can understand the lack of feedback Eric got
about
his
web
[Leaf-devel] YATALWI ( Yet Another Thread About Leaf Web Interface)
Hi, Since last year ( when I discovered LRP), I think that there was at least 3 or 4 threads about a web interface to a LEAF derivative. I would like to start a brainstorming on the feasability/usefullness of a Web interface for the LEAF project. what people think about - usefullness - would it be secure enough - technologies to use ( scripting languages ,..) - is there some exsiting project that could be reused ( I've heard about Webmin) - other secrets wishes that you have about LRP/LEAF happy brainstorming Etienne Charlier - Original Message - From: Eric Wolzak [EMAIL PROTECTED] To: Etienne Charlier [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, September 16, 2001 10:37 PM Subject: Re: [Leaf-user] thttpd CGI Forms for administrating Firewall through browser Hi Etienne, Sandro and the rest of the list I'd be happy to contribute to a web interface for LEAF If there are more people interested, we could join our efforts :=) Here are some ideas First of all, the combinaison LRP/Kernel 2.4/Shorewall is not yet very common in the LRP world and I can understand the lack of feedback Eric got about his web interface. I think you ve got a point there. I think that allowing editing existing files through the web interface is a lot of work with a very small ROI, an applet java allowing ssh access could do the job This is what i normally use myself, but I thought that there is some interest to do it with a webinterface. ( a concurrent product fli4l.de uses a windows programm as a frontend) IMHO, What we need is a higher level interface ( Like seawall, you have a few simple configuration files and a lot of work done with the data in those files) That was exactly what I liked about shorewall I think we could design the web interface as an editor modifying a big file ( config.web) containing shell variables definitions and a few scripts which process configuration files templates, replacing the variables in the templates by the actual values from config.web and write actual configuration files in the right place. That is kind of the way the eigerstein was setup. A problem is usually the multiple different lrp packets. If we could create a small yet complete interface in the packages then the central editfile could take this and return them at the appropiate moment ( sounds kind of complicated ;)) example: the local interface ip address ( 192.168.1.254) is used in a lot of configuration files. the web interface should be able to modify this value everywhere It should be easy to add modules to the web interface ( a set of pages and a set of templates) those pages and templates could be stored in the .LRP files or in separate packages (with another file extension). I think that is a good approach now a few questions: - Should the interface be usable with the floppy version of a LEAF-like distribution I personally would like it that way. ( https ? to allow remote management isnt't it too big ?) - Should we try to reuse something exisitng or build from scratch ? I think it is a good idea to complete the concept and after that look at how much we can use from existing files and how much has to be created new. - Could we build our interface so that we could derive from it a set of web pages or a set of scripts using the dialog command ( being usable from the text console ) - how to permit customizations in the templates outside of the web interface ( to allow modifications not ( yet ) possible from the web interface ?? I think about it :=) - I think that it's a big project but it should be possible PS: Maybe we could move on the leaf-devel list or elsewhere ?? I Think it is a good idea to move to the leaf-devel list. Perhaps change the subject a bit. Regards Etienne Charlier [EMAIL PROTECTED] Regards to Belgium :) Eric Wolzak http://leaf.sourceforge.net/devel/ericw ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] Oxygen + glibc 2.1 + programs compiled for glibc 2.0 OK ?
Hi, I was wondering if the old packages built for *Stein ( with binaries compiled for glibc 2.0) run on the oxygen development image using glibc 2.1 ? Thank a lot Etienne Charlier ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] Dachstein Pre-Release avaialble
Hi, I message http://www.mail-archive.com/leaf-devel@lists.sourceforge.net/msg02383.html , Eric Wolzak described a way to integrate the pppoe stuff in the network.conf script Would it be possible to integrate those modifications in the dachstein release ? two more variables PPPOE_USER= PPPOE_PASSWORD= would also be usefull. I think that with those modifications in place, It would be possible to create an image adapted to PPPoE just by removing DHCLIENT.LRP and put PPP.LRP and PPPOE.LRP on the floppy Of course, one (me) must modify the PPPOE.LRP package to add a init.d/pppoe scripts to get the username password from network.conf and generate the pap-secrets/chap-secrets files +/- the same way /etc/hosts could be generated by the EigerStein scripts ?? Any better idea ??? Etienne Charlier - Original Message - From: Charles Steinkuehler [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, August 22, 2001 2:02 AM Subject: [Leaf-devel] Dachstein Pre-Release avaialble I've uploaded a pre-release version of Dachstein, which can be found here: http://lrp.steinkuehler.net/files/diskimages/dachstein/dachstein-pr1-1680.im g Pre-release means that I *know* there are things that will change before the release version. See the readme file below for details on what's changed from Ewald's latest ES2B update image, and what remains to be done. I have generally verified the image boots and functions, but I haven't pounded on it a lot...since several scripts have changed, there could be some hidden problems. Try it if you're daring (or can spend some time testing for bugs), but I wouldn't use it for production systems yet. Please post any problems, desired changes, c to the list, for fixing/inclusion in the next image, which will hopefully be a release candidate. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) -- Changes from Ewald Wasscher's May 27 EigerStein2Beta update: http://leaf.sourceforge.net/devel/ewaldw/Eigerstein2BETA/20010527/Eigerstein 2BETA_test_20010527_1680.bin -- Release officially named Dachstein Syslinux splash screen replaced with version from Richard Lohman dnscache modified to use 0.0.0.0 for IPSEND dnscache still run from script (rather than daemontools) due to licensing issues with daemontools dhclient modified to no longer restart dnscache when getting a new IP log.lrp replaced by ramlog.lrp, which puts log files on their own ramdisk partition. /etc/fstab updated to reflect new mount point for /var/log dhcpd and dhclient modified to prevent storage of dhcp leases as part of root.lrp dhclient.conf modified to prepend 127.0.0.1 (local dnscache) to DNS servers provided by ISP's dhcp server Backup scripts reverted back to using ctar, to avoid file exclude problems when backing up root.lrp root.list changed from * to ./ to fix include problems backing up other packages (like etc) e3 replace with re-compiled version: Pico emulation set as the default mode, and the :x command was added to VI emulation -- TODO -- Update the readme to reflect changes to the editor (ae - e3), and any other changes that affect end-user setup walk-through to verify the readme instructions Update network/firewall scripts, folding together LRP-CD and extended scripts V 1.1 functionality Add java bandwidth applet to weblet.lrp ___ Leaf-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-devel ___ Leaf-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] DachStein for pppoe ?
Hi, I wanted to have a try to the Dachstein pre-release ( 2001/05/27 ) butI didn't found any trace of pppoe support Does someone work on this ?? Have a nice WE Etienne Charlier
Re: [Leaf-devel] Poll: Ladybug Architecture
- Original Message - From: "David Douthitt" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 13, 2001 2:43 PM Subject: Re: [Leaf-devel] Poll: Ladybug Architecture George Metz wrote: On Mon, 12 Mar 2001, David Douthitt wrote: Snip! * Tried to remove EVERYTHING and ANYTHING located in root.lrp that required backups: thus, root.lrp should be completely static for almost all purposes. (if it isn't, I'm not done :) As a note, on the lazy side of things - since I am, first and foremost, a lazy SOB g - this means that any update to Oxygen's root.lrp can be simply plugged in to any Oxygen-derived images and BANG, Derivative updated. That's awfully appealing to me. =) Every good programmer is :) I'm thinking like this: grab your config.lrp, add it to a new Oxygen disk, and bang! Instant update! That's what I was dreaming for some weeks ago when I started the thread about making a config.lrp keep the pressure, David ;-) Etienne * Using a new glibc means you are no longer able to use a floppy (probably). Why? A stripped glibc 2.1.x setup only takes about a hundred to two hundred kbytes more of disk space; if the only things on the disk are the root and etc LRPs, then there should be tons of space for it. Yes and no. 100k - 200k is HUGE! However, the only things required to boot Oxygen is the syslinux overhead and root.lrp; the rest can be loaded over the network. Also, I've been leery of "stripped glibc" ever since I banged my head on ncurses from the get go. First thing I did was replace Dave's stripped ncurses (in LRP) with a full ncurses 4 library. All of a sudden everything worked :) * using a more up-to-date glibc - this is something to seriously consider, methinks. Aye. I've been wondering if newlib or something would implement everything but with basic functions - to provide full support for new libraries and functions, yet in a small package. 100k to 200k is too much for me - I don't have that much free space on disk! ... ___ Leaf-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-devel ___ Leaf-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-devel
