[leaf-devel] Compile host for Bering? (glibc, gcc, kernel versions etc...)
I have been using UML (debian slink/woody) for my kernel compiles, but never been able to successfully compile userland stuff in either environments. Since upgrading my workstastion to SUSE 9.2 my UML virtual machines won't start, and I'm beginning to tire of the complexity of all that. So I'm now looking at setting up a dedicated system for compilation/development. I have been looking at the Develping and using LEAF in a virtual environment howto at: http://leaf.sourceforge.net/bering/index.php?module=pagemasterPAGE_user_op=view_pagePAGE_id=3MMN_position=3:3 - to try to decide which base system to use. Being basically completely unfamiliar with Debian (and apt in particular), I'm thinking SuSE 7.3 or 8.x should be viable alternatives, as long as I manage to set it up with all the 'correct' versions of everything. Now, the above looks pretty dated, and while I'm aware that the development environment is pretty static, I'd still like to make sure I don't set up something that's completely outdated... So the questions are: Which versions of glibc, gcc, make, (other), should I have in such a system? TIA /Jon -- YMMV --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Creating Bering uClibc images
Hi, here are a few thoughts about how to create media images with Bering uClibc. They may serve as thought food and a foundation for a healthy discussion... 1. It is non-trivial to create images if you don't have a step by step HOWTO to follow. Currently we have these: http://leaf-project.org/doc/guide/bugrub.html (Bering User's Guide) http://leaf-project.org/doc/guide/bucu-ide.html (Bering uClibc User's Guide) http://leaf.lauft.net/bu-docs/buci-hdd.html (Originally intended for the Bering uClibc Installation Guide, written before finding out that HDD installation is not covered in the Installation Guide, but in the User's Guide. Go figure.) Composing all relevant information in a chapter of the BU Install Guide will probably the best way to improve this. 2. Bering uClibc releases ship as floppy (FDD) and cdrom (ISO) images, but not as harddisk (HDD) images. But the users of all other devices like HDDs, CF media, USB Sticks, Flash Disks, etc. have to build their images from scratch. 3. Building a FDD image can be easily done by a script. You basically do dd if=/dev/zero of=image mkdosfs image mcopy *.lrp image: syslinux image and you have a working image. You don't even need to be root. 4. On IRC, Mike brought up a few possibilities to deploy an image creator: a) A website where you can click together your custom BU image similar to http://rom-o-matic.net/5.2.6/ b) A CD-ROM image with a booting version of linux on it, from which you can build BU images. I suggested to call this LICK - LEAF Image Creator Knoppix :) 5. Building a HDD image is difficult. You either a) do it as root on a real HDD device b) do a lot of evil dd if= of= bs= count= skip= seek= magic with harddisk and partition images to emulate userspace partition handling. You have to take into account CHS mappings, whether you want to use SYSLINUX or GRUB, whether you want multiple BU partitions there etc. IMHO, some of this stuff would be nice to have, but of course someone would have to implement it first :) Gru, Uli pgpg6zGPhdvTy.pgp Description: PGP signature
Re: [leaf-devel] Creating Bering uClibc images
Hi, First of all, I must say that the process of creating _images_ is not something I worry about too much (I simply don't need disk images all that often) - but being able to create fully configured _packages_ would be something I'd care for a lot (and something I've been thinking about for a long time, I just haven't had any time to do any real coding). That being said, I see your point - and I hope others will jump in and share their thoughts/ideas as well. Hans Ulrich Niedermann wrote: Composing all relevant information in a chapter of the BU Install Guide will probably the best way to improve this. Absolutely. Unfortunately, there hasn't been anybody willing to write that up yet. 2. Bering uClibc releases ship as floppy (FDD) and cdrom (ISO) images, but not as harddisk (HDD) images. But the users of all other devices like HDDs, CF media, USB Sticks, Flash Disks, etc. have to build their images from scratch. I work with CFs a lot, and dd images haven't worked well at all for me on those (I assume due to the different layouts of different CF models - or something like that. I ran into trouble when I tried it the first time, but I didn't investigate any further, mainly since there were other ways to get things to work) - so I usually boot using pxeboot and just set up everything from there, which works extremely well for me (also see help hdsupp for step by step instructions on what to do to set up LEAF on a harddrive/CF). 3. Building a FDD image can be easily done by a script. You basically do dd if=/dev/zero of=image mkdosfs image mcopy *.lrp image: syslinux image and you have a working image. You don't even need to be root. Yes - but you need to have a Linux box - which seems to not be something you can simply expect in our userbase (just look at the download numbers, the fact that the winimage image file is the one that's downloaded the most doesn't really imply that simplified instructions/scripts for creating images on Linux are going to benefit the majority of our userbase). 5. Building a HDD image is difficult. You either a) do it as root on a real HDD device b) do a lot of evil dd if= of= bs= count= skip= seek= magic with harddisk and partition images to emulate userspace partition handling. You have to take into account CHS mappings, whether you want to use SYSLINUX or GRUB, whether you want multiple BU partitions there etc. As I said, pxeboot works extremely well on boxes that support booting via pxe (I'm using soekris boxes, but I gather that should work as well on a regular box, if the nic supports booting via pxe). IMHO, some of this stuff would be nice to have, but of course someone would have to implement it first :) Good point - and that's usually the reason why there are not more fine tuned tools - the guys who are working on the distribution are busy already (and usually, they're comfortable enough setting things up with the existing tools, that it's hard to justify letting other things slide to work on such a tool-set). But if somebody is willing to jump in and work on such a thing (and also document it - something that's often lacking in OpenSource projects), I'm sure there'll be many happy users for such a toolset. Martin --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
