[leaf-devel] LEAF and kernel patches
Mandag den 16. september 2002 22:15 skrev David Douthitt: The Oxygen/LEAF Resource CDROM contains a kernel/ directory which contains kernel sources and all available patches, including LRP patches and Openwall and others. Great. Is the situation the same with the Bering distribution, which I use? Anyhow, I am glad to see the tumbling with the idea of basing a LEAF distribution on source based distribution instead of an outdated debian. The LEAF distribution isn't bigger that it should be possible to compile everything from scratch without spending several days, and secondly and maybe most important: It would be easier to get the latest security patches included. Keep up the good work. Regards, -- /\ ,_ _|,_ _ _ _, |¨) _ _ |_/\ _ _ ,_ /¨¨\| )(_|| (-'.-|`-, |¨).-|(_ | ) /¨¨\.-|(-'| ) ¨¨ grep -r 'Andreas Bach Aaen' /usr/src/linux --- Sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Possible framework for build-from-source system.
Hello all, I am currently evaluating GAR, the build-system from http://www.lnx-bbc.org/ for use with leaf. So far it looks really good. It's flexible, quite well documented and there are lots of examples for building packages, a bootdisk or an iso image. I encourage anyone interested in the subject to take a look at the above site. Ewald Wasscher --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LEAF and kernel patches
Le Mardi 17 Septembre 2002 18:21, Andreas Bach Aaen a écrit : Mandag den 16. september 2002 22:15 skrev David Douthitt: The Oxygen/LEAF Resource CDROM contains a kernel/ directory which contains kernel sources and all available patches, including LRP patches and Openwall and others. Great. Is the situation the same with the Bering distribution, which I use? For Bering: Kernel config file is here: http://leaf.sourceforge.net/devel/jnilo/bering/latest/Bering_1.0-rc3.config Kernel patches are here: http://leaf.sourceforge.net/devel/jnilo/bering/latest/patches/kernel/ Patching sequence is here: http://leaf.sourceforge.net/devel/jnilo/bering/latest/patches/kernel/README.txt Anyhow, I am glad to see the tumbling with the idea of basing a LEAF distribution on source based distribution instead of an outdated debian. The LEAF distribution isn't bigger that it should be possible to compile everything from scratch without spending several days, and secondly and maybe most important: It would be easier to get the latest security patches included. Keep up the good work. Regards, --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Possible framework for build-from-source system.
Le Mardi 17 Septembre 2002 19:18, Ewald Wasscher a écrit : Hello all, I am currently evaluating GAR, the build-system from http://www.lnx-bbc.org/ for use with leaf. So far it looks really good. It's flexible, quite well documented and there are lots of examples for building packages, a bootdisk or an iso image. I encourage anyone interested in the subject to take a look at the above site. Ewald Wasscher Ewald: Following on this and the previous thread on buiding Bering from source tree, please feel free to test that or any other approach to test your ideas on building Bering from source since apparently their an interest for it. I am ready to help you on this project (I won't have much time to work on it myself and even if I feel that there will be many questions/obstacles along the way, I think it might be worth trying). One key question is the development environnement to be chosen. I understand that you consider slink as being outdated which is true but which is still the only way to have a single floppy based distro. I know that some users have switched to other media but I have the impression it is not the majority (Mike: what about a poll on this on the leaf site ?) Some recent programs (e.g. freeswan userland stuff) have to be patched to compile cleanly with slink. Would you be ready to do that on - say - a slink and woody based environnement ? Suggestions /comments from the list ? Jacques --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] bwhitley is currently out of the office.
I will be out of the office until the 20th of September. E-Mail scanned by www.messagelabs.com --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Possible framework for build-from-source system.
On Tue, 2002-09-17 at 20:57, Mike Noyes wrote: On Tue, 2002-09-17 at 11:37, Jacques Nilo wrote: One key question is the development environnement to be chosen. I understand that you consider slink as being outdated which is true but which is still the only way to have a single floppy based distro. I know that some users have switched to other media but I have the impression it is not the majority (Mike: what about a poll on this on the leaf site ?) Jacques, I'll attempt to get our phpWS poll code working. I'll keep you informed of my progress. Would it be a good idea to create a leaf-stats package that periodically sends an email with details about the system. Of course only after approval of the user. To get an idea of what I mean: http://gentoo.iq-computing.de/ Ewald Wasscher --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Possible framework for build-from-source system.
On Tue, 2002-09-17 at 13:09, Ewald Wasscher wrote: BTW, your CVS devel/ddouthitt tree has been empty for the last days. Is that on purpose? I went there to get a fresh copy of your build system, and noticed this. Ewald, David's base tree was moved it's now in src/oxygen. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/src/oxygen/ -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Possible framework for build-from-source system.
On Tue, 2002-09-17 at 20:37, Jacques Nilo wrote: Le Mardi 17 Septembre 2002 19:18, Ewald Wasscher a écrit : Ewald: Following on this and the previous thread on buiding Bering from source tree, please feel free to test that or any other approach to test your ideas on building Bering from source since apparently their an interest for it. Ah great to hear this! I will do so after (or paralell with) the next release of Dachstein. I am ready to help you on this project (I won't have much time to work on it myself and even if I feel that there will be many questions/obstacles along the way, I think it might be worth trying). Nice to hear this. I'll appreciate any help, also if it isn't much. One key question is the development environnement to be chosen. I understand that you consider slink as being outdated You understand that correctly. which is true but which is still the only way to have a single floppy based distro. I don't agree with you that it's the _only_ way. But maybe we can keep glibc-2.0.7 as an option. I know you have been wary of uClibc and other c-libraries targeted at embedded systems in the past, but I think it is possible to have a base system with uClibc (and AFAIK all of the programs on the Bering floppy can be built with it). If you want to discuss the use of uClibc maybe we can move that to another thread? Furthermore there is still some room left for space saving in Bering: - mkfs.minix from asmutils. - switch to ash from busybox - ? development branch of busybox is smaller - compile iptables with the extensions linked in statically. I know that some users have switched to other media but I have the impression it is not the majority (Mike: what about a poll on this on the leaf site ?) Yes! Polls! Polls! Polls! (What branch do you use? What hardware? What purpose? What do you want added/changed to leaf? Would you switch to a glibc 2.2 based leaf even if it would be bigger? etc) Some recent programs (e.g. freeswan userland stuff) have to be patched to compile cleanly with slink. That is one reason I don't like using glibc 2.0.x. The major other ones are the not exactly known but almost certainly present security holes. Would you be ready to do that on - say - a slink and woody based environnement ? If necessary. But I think I prefer a combined uClibc/glibc 2.x.y approach where x=2 or x=1. Suggestions /comments from the list ? Yes please, give them. Ewald --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Possible framework for build-from-source system.
On Tue, 2002-09-17 at 13:36, David Douthitt wrote: On Tue, Sep 17, 2002 at 10:09:12PM +0200, Ewald Wasscher wrote: On Tue, 2002-09-17 at 21:22, David Douthitt wrote: BTW, your CVS devel/ddouthitt tree has been empty for the last days. Is that on purpose? I went there to get a fresh copy of your build system, and noticed this. Wasn't aware of that! Why would this be, Mike? David, You told me off-list I could have devel/ddouthitt/base moved to src/oxygen/base. I just forwarded the message where you said it was ok to do this to you off-list. See SF support request 603606. https://sourceforge.net/tracker/index.php?func=detailaid=603606group_id=1atid=21 -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Linux Virtual Server using LEAF Bering RFC
On 2002.09.17_11:54:09_+, Brad Fritz wrote: I cannot answer your question about whether it will be included, but I can say that the linux-2.4.12-ipvs-0.8.2 patch applies cleanly over the stock Bering rc3 patched kernel[1]. Actually I have tested applying linux-2.4.19-ipvs-1.0.6.patch.gz to 2.4.18 with Bering patches. Also applies cleanly. The IPVS kernel, including IPVS debugging support, is only 44 bytes larger than the stock kernel after UPX compression. $ ls -l ../*.upx -rw-r--r--[..] 495299 Sep 17 11:42 ../Bering_1.0-rc3-ipvs.upx -rw-r--r--[..] 495235 Sep 17 11:26 ../Bering_1.0-rc3.upx Great. May be this will be a good reason to incorporate IP_VS into Bering or Dachstein kernel. make modules is running now. If it would be helpful, I could upload the (completely untested) kernel and modules, along with the build script I used to download patches and apply them to the stock 2.4.18 kernel, to my devel subdirectory in CVS. Let me know if that would be useful to you. Sure it would help. I would like to have such a script to automate the work. So far I have been doing it manually. The kernel should help me examine different result of patches version for testing. Thanks Brad. --Brad [1] with the exception of non-essential Documentation/Configure.help file -- H. D. Lee --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Linux Virtual Server using LEAF Bering RFC
On Wed, 18 Sep 2002 06:55:56 +0700 H. D. Lee wrote: Great. May be this will be a good reason to incorporate IP_VS into Bering or Dachstein kernel. Even if it's not included, the build-from-source approach being discussed should make it easy for interested parties to roll their own kernel and modules. If it would be helpful, I could upload the (completely untested) kernel and modules, along with the build script I used to download patches and apply them to the stock 2.4.18 kernel, to my devel subdirectory in CVS. Let me know if that would be useful to you. Sure it would help. I would like to have such a script to automate the work. So far I have been doing it manually. The kernel should help me examine different result of patches version for testing. Thanks Brad. Posted to http://fritzfam.com/brad/leaftmp/make_bering_ivs_kernel temporarily. As time allows, I am going to re-write it using GAR or David's ports-like system (or both). Once I do, I will check it into cvs.sf.net under leaf/devel/bradfritz . --Brad -- H. D. Lee --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Linux Virtual Server using LEAF Bering RFC
On 2002.09.17_19:27:06_+, Brad Fritz wrote: On Wed, 18 Sep 2002 06:55:56 +0700 H. D. Lee wrote: Great. May be this will be a good reason to incorporate IP_VS into Bering or Dachstein kernel. Even if it's not included, the build-from-source approach being discussed should make it easy for interested parties to roll their own kernel and modules. Yes, you are right. If it's not included, I will roll my own kernel and modules, and make it available. It means people who want LVS have to change the kernel and add the supported modules. IMHO, it would be convenient to have to add ip_vs related modules to turn the features on, just like other modules. Sure it would help. I would like to have such a script to automate the work. So far I have been doing it manually. The kernel should help me examine different result of patches version for testing. Thanks Brad. Posted to http://fritzfam.com/brad/leaftmp/make_bering_ivs_kernel temporarily. As time allows, I am going to re-write it using GAR or David's ports-like system (or both). Once I do, I will check it into cvs.sf.net under leaf/devel/bradfritz . Thank you. --Brad -- H. D. Lee --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Re: [off-list] GNU licensing
On Monday 16 September 2002 14:27, Mike Noyes wrote: Everyone, This is the first post I've seen from a kernel contributer on our devel list. Is this a gentle reminder that we may have some licensing problems with the files we provide? I would imagine so. I also missed a couple on the quiz...good learning experience! If this is a gentle prod, my interpretation of the quiz/GPL would indicate that we do NOT need source posted on the site, however it MANDATES that we have the source available on some physical media per request and that charging for the expense of shipping and media is allowed. With this in mind, each variant or any combination of variants should have something along the lines of David's developer CD that could be mailed if requesteda downloadable .iso would be nice, but beyond necessity of the GPL. I won't have guessed at this mandate myself, but after taking the quiz does anyone else have a different interpretation? -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] Re: Building Bering from source
So ... the key word in Erich's comment is primitive. If one's ends are simple, LEAF setup requirements probably are too demanding. But complex needs require complex solutions, and that is what all the LEAF and related-project (Shorewall, for example) developers seem interested in supporting. Yes, the existence of multiple LEAF branches does complicate things a bit, but blaming this diversity for the greater complexity of LEAF misses a lot of the point ... that LEAF configuration is more complicated than router-in-a-box solutions precisely because it can do more complicated things. Ok, with this line in thought being pointed out. In less than a week, I can presently turn out a set of custom images of several present LEAF variants that: 1) Provides a general firewall. 2) Provides a web-based interface linked to internal ip's w/ virtually no security (other than name/password). 3) Is simple to setup due to lack of configuration options. Is this what you desire to have available??? I feel that several others in the past have likely come this far in development, but feel the need not to release it due to the massive amount of specific request for more rarely needed options that don't necessarily keep everything simple (or on a floppy). Personally, I feel the upcoming development with the web-based configuration thread would be preferrable in the long run. Lots of people in the team have done little (or even big) extensions to the base threads. Some of these externsions may have found their way into the distribution. I would like to see a distribution tree with sources included, embracing as much additional stuff as is seen fit by the lead developers and I am prepared to help where I can with as much time as I can pry loose. I believe the community can profit from such a model and who knows, maybe we have success. I believe Ewald has expressed his dedication too and certainly others may want to get involved. If you think this is too big a bite for anyone's appetite let me know. Building a type of ports system such as David is working on interests me tremendously, however after several short precursive peeks at his tree leaves me with several inpending questions: Is the target system compiling the source itself? 1) If so, what compiler is available on the target system (floppy?)? 2) If the target system is not compiling the code, the user must use some form of *NIX system to compile on this pretty much eliminates M$ users. 3) if the compilation is done by the system remotely, is the SF compile farm (or some other system) going to work with any GPL restrictions (distributing binaries?). These are simply concerns due to my lack of understanding of port systems outside of LFS, which requires a Linux compiler on the host system. A simple description of the process being proposed would likely build more dialog on the topic. Any direction this is taken is going to have a baseline environment, which will affect the required licensing or end-user in some way. I'm still attempting to figure out what the required system can/will be. Thanks for the thoughts, the effort, and the development! -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] bwhitley is currently out of the office.
I will be out of the office until the 20th of September. E-Mail scanned by www.messagelabs.com --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] (no subject)
On Sunday 15 September 2002 06:10, Erich Titl wrote: The currently available releases may still exist but it might be possible to get the best features out of everything. I was wondering if Eric's plans to base the configuraion on a common base would not automagically lead to a unified environment. Evolution will have it's way. This unified environment would not be mandatory. However it would require a compatibility layer for any LEAF variant since the packages that would depend on certain configuration data could not be assumed. This would be left optional for the user/variant to use at it's discretion. -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
