Re: RSS feed for changelog of stable in git - Was: Re: which updates for Om 2008.8 ? - Was: Re: Repository and Images
Olivier Berger wrote: Olivier Berger [EMAIL PROTECTED] writes: Julian Chu [EMAIL PROTECTED] writes: On Wed, Aug 27, 2008 at 12:06:07AM +0200, Olivier Berger wrote: Is there a changelog of bugs fixed somewhere ? is the git log helps you? http://git.openmoko.org/?p=openmoko.git;a=log;h=org.openmoko.asu.stable Great. Would it be possible to have GITweb upgraded / patched (http://www.gelato.unsw.edu.au/archives/git/0511/11378.html maybe) so that RSS feeds can be output for heads ? Something like http://git.openmoko.org/?p=openmoko.git;a=rss;h=org.openmoko.asu.stable would definitely rock... but at the moment it only gives the same thing as http://git.openmoko.org/?p=openmoko.git;a=rss :( I've hacked something quickly (using http://bent.latency.net/git2rss as a base) to produce such an RSS feed : http://www.olivierberger.com/openmoko-200808-stable.xml Btw, looks like some systematic bug # in the changelog of commits made to git would reassure us on the contents of the stable updates ;) Any comments welcome. Best regards, Nice :) ... and thanks. Sarton ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RSS feed for changelog of stable in git - Was: Re: which updates for Om 2008.8 ? - Was: Re: Repository and Images
Olivier Berger [EMAIL PROTECTED] writes: Julian Chu [EMAIL PROTECTED] writes: On Wed, Aug 27, 2008 at 12:06:07AM +0200, Olivier Berger wrote: Is there a changelog of bugs fixed somewhere ? is the git log helps you? http://git.openmoko.org/?p=openmoko.git;a=log;h=org.openmoko.asu.stable Great. Would it be possible to have GITweb upgraded / patched (http://www.gelato.unsw.edu.au/archives/git/0511/11378.html maybe) so that RSS feeds can be output for heads ? Something like http://git.openmoko.org/?p=openmoko.git;a=rss;h=org.openmoko.asu.stable would definitely rock... but at the moment it only gives the same thing as http://git.openmoko.org/?p=openmoko.git;a=rss :( I've hacked something quickly (using http://bent.latency.net/git2rss as a base) to produce such an RSS feed : http://www.olivierberger.com/openmoko-200808-stable.xml Btw, looks like some systematic bug # in the changelog of commits made to git would reassure us on the contents of the stable updates ;) Any comments welcome. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
We want to let the community join and give commit rights to individuals. In the OpenWRT world they are able to give commit rights to single packages but they use SVN. Is that possible with git as well ? since noone followed up I will add my .1 cents: I don't know if a fine-grained control is possible to allow which user could modify which subdirectories. BUT there is a way to control what user is allowed to advance which head -- ie which branch could be modified by which user. See http://developer.berlios.de/docman/display_doc.php?docid=1812group_id=2#access for the description of such setup. I guess if you are to have relatively large number of allowed users and lack of a person who would be responsible for merging per-person branches, the easiest way is just to create .community branches (e.g. ...asu.dev.community), to which add permission to commute to a set of community members. -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
Julian Chu wrote: On Wed, Aug 27, 2008 at 11:57:37PM +0930, Rod Whitby wrote: Will you be autobuilding from the OE git repository or the OM git repository? If the latter, will non-Openmoko staff have commit rights? If not, then we will still need autobuilders for the community distributions, since there is no automatic syncing from repositories with community commit rights to the Openmoko repository as far as I am aware. We auto-build from OM git tree. And we still trying to make it close to OE git tree. It's that delay (which is often a number of days) which means that we still needs auto-builders (especially for FSO and SHR) which build directly from the OE git tree. Since Openmoko now has it's own stable branches (org.openmoko.asu.stable), I don't see the reason for having a separate org.openmoko.dev branch separate from org.openembedded.dev - in an ideal world you would be always in sync with the org.openembedded.dev branch without any delay caused by manual syncing by Graeme. -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
Dne Wednesday 27 of August 2008 10:33:25 Marek Lindner napsal(a): Hi, this merits some more details: *) Base Images and repository We have a base image. It is minimal image plus Window Manager(e-wm), Om-settings and Om-installer. We will shift away from preinstalled phone stack images. Instead, we provide a base image which allows you to install your preferred applications (GTK/Qtopia/SHR/FSO/etc) and really own your phone. Currently, we are in the process of getting this system running smoothly. Early adopters / testers / developers are invited to test it. We also encourage $your_project to be built by our auto builder and become installable on the base image. This should give you the time to focus on improving your project instead of building and distributing it. The unstable package feed will always contain your latest code, testing the version you think is ready for use. Does this mean that I should use http://downloads.openmoko.org/repository/testing/ repositories to update Trolltech's Qtopia image (qtopia-4.3.2-gta02-rootfs-release-08280107.jffs2) from now instead of default ones http://buildhost.openmoko.org/daily-feed/? -- Ing. Radek Bartoň Faculty of Information Technology Department of Computer Graphics and Multimedia Brno University of Technology E-mail: [EMAIL PROTECTED] Web: http://blackhex.no-ip.org Jabber: [EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
On Wed, Aug 27, 2008 at 01:15:30PM +0200, julien cubizolles wrote: Le mardi 26 août 2008 à 21:07 +0800, Julian Chu a écrit : Holger did some changes in ASU-stable branch. We built it and put on downloads.openmoko.org.[2] [2]http://downloads.openmoko.org/releases/Om2008.8-update/ Does this mean that it includes the fix to ticket #1766 ? Julien. Hi Julien, I am Julian. As far as I know, Zecke did a commit and trying to fix it. (the revision of qtopia-phone-x11 is 9971aa8a...) As Yorick's report in Trac, it seems didn't be fixed yet. Best Regards, -Ju1ian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
On Tue, Aug 26, 2008 at 10:01:59AM -0600, Vince M. Clark wrote: Great work on the repositories. Thank you. One question for clarification. To use testing or dev repositories would I first install the updated stable image and then use test or dev repositories for updates? Hi, As the name of the repository, it is still on Testing. It is not recommend to use it unless you are hardcore developer. If you really wants to use the repository, download the image in http://downloads.openmoko.org/daily/ and install the qtopia stuffs :) Best Regards, -Ju1ian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: which updates for Om 2008.8 ? - Was: Re: Repository and Images
On Wed, Aug 27, 2008 at 12:06:07AM +0200, Olivier Berger wrote: Olivier Berger [EMAIL PROTECTED] writes: Well, actually, I had a network problem, and made a false assumption on that. opkg does indeed upgrade now the network is configured OK. I'm puzzled... How is one supposed to upgrade from the initial 2008.8 ? re-flash the daily built stable ? I suppose the upgrade path is clear, then : opkg update + opkg upgrade with feeds from [3]. Sorry about bothering. Still, this may be helpful though : Is there a changelog of bugs fixed somewhere ? I'll try and update the wiki unless someone's quicker in doing so. Best regards, Hi Olivier, Thanks for your work :-) is the git log helps you? http://git.openmoko.org/?p=openmoko.git;a=log;h=org.openmoko.asu.stable Best Regards, -Ju1ian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
On Wed, Aug 27, 2008 at 11:57:37PM +0930, Rod Whitby wrote: Will you be autobuilding from the OE git repository or the OM git repository? If the latter, will non-Openmoko staff have commit rights? If not, then we will still need autobuilders for the community distributions, since there is no automatic syncing from repositories with community commit rights to the Openmoko repository as far as I am aware. -- Rod Hi Rod, We auto-build from OM git tree. And we still trying to make it close to OE git tree. If the non-Openmoko staff means some project from community, we have a community repository. http://downloads.openmoko.org/repository/Multiverse/ Best Regards, -Ju1ian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
Le vendredi 29 août 2008 à 03:15 +0800, Julian Chu a écrit : On Wed, Aug 27, 2008 at 01:15:30PM +0200, julien cubizolles wrote: Le mardi 26 août 2008 à 21:07 +0800, Julian Chu a écrit : Holger did some changes in ASU-stable branch. We built it and put on downloads.openmoko.org.[2] [2]http://downloads.openmoko.org/releases/Om2008.8-update/ Does this mean that it includes the fix to ticket #1766 ? Julien. Hi Julien, I am Julian. As far as I know, Zecke did a commit and trying to fix it. (the revision of qtopia-phone-x11 is 9971aa8a...) As Yorick's report in Trac, it seems didn't be fixed yet. I'm running raster's image upgrade to the Om2008.8-update repos and I can make/receive calls as I could with zecke's repos. So for me it's fine. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: which updates for Om 2008.8 ? - Was: Re: Repository and Images
Julian Chu [EMAIL PROTECTED] writes: On Wed, Aug 27, 2008 at 12:06:07AM +0200, Olivier Berger wrote: Is there a changelog of bugs fixed somewhere ? is the git log helps you? http://git.openmoko.org/?p=openmoko.git;a=log;h=org.openmoko.asu.stable Great. Would it be possible to have GITweb upgraded / patched (http://www.gelato.unsw.edu.au/archives/git/0511/11378.html maybe) so that RSS feeds can be output for heads ? Something like http://git.openmoko.org/?p=openmoko.git;a=rss;h=org.openmoko.asu.stable would definitely rock... but at the moment it only gives the same thing as http://git.openmoko.org/?p=openmoko.git;a=rss :( Many thanks in advance. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
On Wednesday, 27. August 2008 17:08:34 Al Johnson wrote: Sounds good so long as the packaging stops people accidentally breaking things just by installing a package. The problem installing 2 diallers is a recent example where it didn't work. Also how will it handle the situation where different frameworks use differently patched versions of the same app? Tangogps springs to mind as an example that seems to be slightly different on GTK, FSO and ASU. Obviously, you will be able to install 2 dialers if the dialers support that. If not I suggest to add necessary dependencies tp the packages. Don't consider this as something we completely designed and intend to push over you. Feel free to make suggestions. I see this approach as a chance to combine the different efforts on a single platform with the maximal user experience. Instead of this feature is working on image X but not on image Y which has feature Z running, etc. Is the mechanism for this in place, or still a work in progress? Are there any details available on how to use it? Get in touch with our distro team to include your project. You can accelerate the process by providing a working bb file. Marek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
On Tue, Aug 26, 2008 at 9:07 AM, Julian Chu [EMAIL PROTECTED] wrote: Hi Community, *) A new 2008.8 stable image [2]http://downloads.openmoko.org/releases/Om2008.8-update/ Oh, it's daily build. *) The repository of 2008.8 After the building process complete, we also sync the repository[3] People can upgrade from there. [3] http://downloads.openmoko.org/repository/Om2008.8/ *) Base Images and repository [5] http://downloads.openmoko.org/repository/testing/ Okay I think these details above sound great, but when I tried them out they did not go as expected. Maybe we can get some clarification on the correct path for a user (like me :-)). Anyway, Starting point 2008.08 w/ Zeche's testing repos -- everything up to date. Get this mail installed the testing image created: testing-all-feed.conf testing-armv4t-feed.conf testing-om-gta02-feed.conf all pointing to the testing repository listed above (5) did the opkg update opkg upgrade This did lots of stuff ... I was getting excited about the new code had dropbear and libncurses issues which I have seen before and solved did an opkg update and opkg upgrade again to make sure nothing was missed. And this is where the trouble started I believe... somehow this had added buildhost repositories to my opkg setup. It installed a ton of stuff before I even realized what it was doing so figured I better let it finish and hope that _somehow_ all the information I knew to be true about buildhost wasn't true anymore... Well as you can guess, my device is going to need to be reflashed. So in summary From the information above, I thought link 5 above was the proper repository for 2008.08? Is this correct? If so, how did the buildhost opkg repository files get to my system. I would suggest this be fixed pretty quickly. If I am used to 2008.08 and tangogps, etc. Should I install the new 2008.08 image (link #2 above)? I thought this was intended as the upgrade path for 2008.08 for a more stable (better / more updated packages). Is this not its intention? All information regarding this will probably help many other users. And I suggest that nobody follow the upgrade path that I did, until these things are answered, cleared up. Thanks so much for your efforts. Really looking forward to getting the next build! Since I've bricked my os at the moment I'm going to try to back some stuff up and flash the 2008.08-update just in case its better :-). btw, love the 2008.08 after modding the keyboard and adding the gprs mux stuff. Super great with exception of super slow after startup and some stability issues (turning off instead of suspend, etc.). Thanks again. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
Le mardi 26 août 2008 à 21:07 +0800, Julian Chu a écrit : Holger did some changes in ASU-stable branch. We built it and put on downloads.openmoko.org.[2] [2]http://downloads.openmoko.org/releases/Om2008.8-update/ Does this mean that it includes the fix to ticket #1766 ? Julien. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
On Wed, Aug 27, 2008 at 07:13:58AM -0400, Geoff Ruscoe wrote: On Tue, Aug 26, 2008 at 9:07 AM, Julian Chu [EMAIL PROTECTED] wrote: Hi Community, *) A new 2008.8 stable image [2]http://downloads.openmoko.org/releases/Om2008.8-update/ Oh, it's daily build. *) The repository of 2008.8 After the building process complete, we also sync the repository[3] People can upgrade from there. [3] http://downloads.openmoko.org/repository/Om2008.8/ *) Base Images and repository [5] http://downloads.openmoko.org/repository/testing/ Okay I think these details above sound great, but when I tried them out they did not go as expected. Maybe we can get some clarification on the correct path for a user (like me :-)). Anyway, Starting point 2008.08 w/ Zeche's testing repos -- everything up to date. Get this mail installed the testing image created: testing-all-feed.conf testing-armv4t-feed.conf testing-om-gta02-feed.conf all pointing to the testing repository listed above (5) did the opkg update opkg upgrade This did lots of stuff ... I was getting excited about the new code It also should have asked you if you want to update certain config files. For some reason, with these repositories, they try to overwrite your /etc/opk/*.conf files. It does ask you though, and you can see a diff of the files by pressing D when it asks. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
On Wednesday 27 August 2008, Marek Lindner wrote: On Wednesday, 27. August 2008 17:08:34 Al Johnson wrote: Sounds good so long as the packaging stops people accidentally breaking things just by installing a package. The problem installing 2 diallers is a recent example where it didn't work. Also how will it handle the situation where different frameworks use differently patched versions of the same app? Tangogps springs to mind as an example that seems to be slightly different on GTK, FSO and ASU. Obviously, you will be able to install 2 dialers if the dialers support that. If not I suggest to add necessary dependencies tp the packages. I think we see things the same way. I just wanted to be sure, and was providing a recent example of problems caused when the dependencies in the package don't account for conflicts between frameworks. Don't consider this as something we completely designed and intend to push over you. Feel free to make suggestions. I see this approach as a chance to combine the different efforts on a single platform with the maximal user experience. Instead of this feature is working on image X but not on image Y which has feature Z running, etc. Combining effort sounds much better than 'just fork it' ;-) I would hope it would lead to a single package for all frameworks, or a main package plus framework-specific backend packages. I would like to see a way to request packages already in OE to be added to the repositories, probably starting in unstable as not all of them will work without modification. Minimo works, rdesktop partly works, and openvpn compliles, though I haven't tested it. linphonec works if you can force opkg into installing the older libosip2 it requires - this is probably a badly defined dependency, but I haven't yet learnt how to modify them. This has all been with mokomakefile and 2007.2 Is the mechanism for this in place, or still a work in progress? Are there any details available on how to use it? Get in touch with our distro team to include your project. You can accelerate the process by providing a working bb file. I will once I have something worthy of being a project! I was hoping to find out in advance so I don't end up having to restructure things to fit later. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
On Wednesday 27 August 2008, Marek Lindner wrote: We also encourage $your_project to be built by our auto builder and become installable on the base image. This should give you the time to focus on improving your project instead of building and distributing it. The unstable package feed will always contain your latest code, testing the version you think is ready for use. Will you be autobuilding from the OE git repository or the OM git repository? If the latter, will non-Openmoko staff have commit rights? If not, then we will still need autobuilders for the community distributions, since there is no automatic syncing from repositories with community commit rights to the Openmoko repository as far as I am aware. -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
On Wednesday, 27. August 2008 22:27:37 Rod Whitby wrote: Will you be autobuilding from the OE git repository or the OM git repository? AFAIK it is based is a OM git repository that closely syncs with OE git. Julian and/or Graeme can give details about that. If the latter, will non-Openmoko staff have commit rights? If not, then we will still need autobuilders for the community distributions, since there is no automatic syncing from repositories with community commit rights to the Openmoko repository as far as I am aware. We want to let the community join and give commit rights to individuals. In the OpenWRT world they are able to give commit rights to single packages but they use SVN. Is that possible with git as well ? Marek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Repository and Images
Hi Community, As I mentioned in the previous mail[1] , we did some works. [1]:http://lists.openmoko.org/pipermail/community/2008-August/026491.html *) A new 2008.8 stable image Holger did some changes in ASU-stable branch. We built it and put on downloads.openmoko.org.[2] [2]http://downloads.openmoko.org/releases/Om2008.8-update/ Oh, it's daily build. *) The repository of 2008.8 After the building process complete, we also sync the repository[3] People can upgrade from there. [3] http://downloads.openmoko.org/repository/Om2008.8/ *) Base Images and repository We have a base image. It is minimal image plus Window Manager(e-wm), Om-settings and Om-installer. We built the image[4] from org.openmoko.dev git branch without AUTOREV. And we have the testing[5] and unstable[6] repository We built testing repository without AUTOREV. We built unstable repository with AUTOREV. Yes, they use the same branch, org.openmoko.dev. [4] http://downloads.openmoko.org/daily/ [5] http://downloads.openmoko.org/repository/testing/ [6] http://downloads.openmoko.org/repository/unstable/ We hope poeple can use the image to install some packages and get the power of ASU or FSO or what else in the feature. We know that there are still some problems and we are still working on that. All we did is for that we hope people can choice what they want. More informations *) All repositories are going to place in downloads.openmoko.org. We will shut down the http interface recently. *) When and how do we get Stable branch. Once we pass the QA from testing team, we have it. However, we need a new testing plan and it is on the way. Best Regards, -Julian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repository and Images
Julian Chu wrote: Hi Community, As I mentioned in the previous mail[1] , we did some works. [1]:http://lists.openmoko.org/pipermail/community/2008-August/026491.html *) A new 2008.8 stable image Holger did some changes in ASU-stable branch. We built it and put on downloads.openmoko.org.[2] [2]http://downloads.openmoko.org/releases/Om2008.8-update/ This image works fairly well, issues I have so far: 1) DNS does not work out of the box, I had to add the open dns hack to /etc/network/interfaces up echo nameserver 208.67.222.222 /etc/resolv.conf up echo nameserver 208.67.220.220 /etc/resolv.conf Isn't there a way to populate the resolv.conf from the dhcp info? And if so why is it not enabled by default? 2) illume-config addes the qwerty button but I have not yet found a way to get a full keyboard https://docs.openmoko.org/trac/ticket/1863 Is there one? 3) WIFI works for the first time only? http://docs.openmoko.org/trac/ticket/1625 -- Alex ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: which updates for Om 2008.8 ? - Was: Re: Repository and Images
Julian Chu [EMAIL PROTECTED] writes: Hi Community, As I mentioned in the previous mail[1] , we did some works. [1]:http://lists.openmoko.org/pipermail/community/2008-August/026491.html Thanks for this update. *) A new 2008.8 stable image Holger did some changes in ASU-stable branch. We built it and put on downloads.openmoko.org.[2] [2]http://downloads.openmoko.org/releases/Om2008.8-update/ Oh, it's daily build. *) The repository of 2008.8 After the building process complete, we also sync the repository[3] People can upgrade from there. [3] http://downloads.openmoko.org/repository/Om2008.8/ I think I don't understand very well the situation... and need some clarification concerning updates from the initial 2008.8 image : Is this [3] repository supposed to bring updates over the first 2008.8 stable image ? (It seems it was already there in my opkg config having used this feed already over the 2008.8 install ..., and nothing seems updated so far when doing opkg update; opkg -test upgrade) From your description, it looks like the [2] and [3] are in sync ... so I wonder what the difference would be between the the initial 2008.8 and this new one [2]... I'm puzzled... How is one supposed to upgrade from the initial 2008.8 ? re-flash the daily built stable ? Is there a changelog of bugs fixed somewhere ? Thanks in advance if you can clarify these points. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: which updates for Om 2008.8 ? - Was: Re: Repository and Images
Olivier Berger [EMAIL PROTECTED] writes: Julian Chu [EMAIL PROTECTED] writes: Hi Community, As I mentioned in the previous mail[1] , we did some works. [1]:http://lists.openmoko.org/pipermail/community/2008-August/026491.html Thanks for this update. *) A new 2008.8 stable image Holger did some changes in ASU-stable branch. We built it and put on downloads.openmoko.org.[2] [2]http://downloads.openmoko.org/releases/Om2008.8-update/ Oh, it's daily build. so I wonder what the difference would be between the the initial 2008.8 and this new one [2]... I'm puzzled... How is one supposed to upgrade from the initial 2008.8 ? re-flash the daily built stable ? Is there a changelog of bugs fixed somewhere ? Responding to myself (in part) concerning the changelog between the two image releases. I did a diff against the opkg /usr/lib/opkg/status files in each image and compared the packages reported with different versions. Here's the list of packages which changed versions between Om2008.8-gta02-20080808.rootfs.tar.gz and 20080826-asu-stable-rootfs.tar.gz just downloaded (versions excluded from that list as my diff wasn't easily tweaked to show both packages and versions) : angstrom-version e-wm exquisite exquisite-themes hal illume illume-theme kernel kernel-2.6.24 kernel-image-2.6.24 kernel-module-aes-generic kernel-module-af-key kernel-module-ah4 kernel-module-ah6 kernel-module-aircable kernel-module-airprime kernel-module-anubis kernel-module-arc4 kernel-module-ark3116 kernel-module-as-iosched kernel-module-asix kernel-module-autofs4 kernel-module-belkin-sa kernel-module-berry-charge kernel-module-blowfish kernel-module-bsd-comp kernel-module-camellia kernel-module-cast5 kernel-module-cast6 kernel-module-catc kernel-module-cdc-acm kernel-module-cdc-ether kernel-module-cdc-subset kernel-module-cdrom kernel-module-cfq-iosched kernel-module-cls-basic kernel-module-cls-fw kernel-module-cls-route kernel-module-cls-rsvp kernel-module-cls-rsvp6 kernel-module-cls-tcindex kernel-module-cls-u32 kernel-module-cn kernel-module-configfs kernel-module-cp2101 kernel-module-crc-ccitt kernel-module-crc16 kernel-module-crc32c kernel-module-crypto-null kernel-module-cs89x0 kernel-module-cyberjack kernel-module-cypress-m8 kernel-module-deflate kernel-module-digi-acceleport kernel-module-dm-crypt kernel-module-dm-mod kernel-module-dm-snapshot kernel-module-dm9601 kernel-module-ebt-802-3 kernel-module-ebt-among kernel-module-ebt-arp kernel-module-ebt-arpreply kernel-module-ebt-dnat kernel-module-ebt-ip kernel-module-ebt-limit kernel-module-ebt-log kernel-module-ebt-mark kernel-module-ebt-mark-m kernel-module-ebt-pkttype kernel-module-ebt-redirect kernel-module-ebt-snat kernel-module-ebt-stp kernel-module-ebt-ulog kernel-module-ebt-vlan kernel-module-ebtable-broute kernel-module-ebtable-filter kernel-module-ebtable-nat kernel-module-ebtables kernel-module-ecb kernel-module-empeg kernel-module-esp4 kernel-module-esp6 kernel-module-fcrypt kernel-module-firmware-class kernel-module-ftdi-sio kernel-module-funsoft kernel-module-fuse kernel-module-garmin-gps kernel-module-gf128mul kernel-module-gl620a kernel-module-gpio-keys kernel-module-hp4x kernel-module-io-edgeport kernel-module-io-ti kernel-module-iowarrior kernel-module-ip-gre kernel-module-ip-tables kernel-module-ip6-tables kernel-module-ip6-tunnel kernel-module-ip6t-ah kernel-module-ip6t-eui64 kernel-module-ip6t-frag kernel-module-ip6t-hbh kernel-module-ip6t-hl kernel-module-ip6t-ipv6header kernel-module-ip6t-log kernel-module-ip6t-mh kernel-module-ip6t-owner kernel-module-ip6t-reject kernel-module-ip6t-rt kernel-module-ip6table-filter kernel-module-ip6table-mangle kernel-module-ipaq kernel-module-ipcomp kernel-module-ipcomp6 kernel-module-ipip kernel-module-ipt-addrtype kernel-module-ipt-ah kernel-module-ipt-clusterip kernel-module-ipt-ecn kernel-module-ipt-iprange kernel-module-ipt-log kernel-module-ipt-masquerade kernel-module-ipt-netmap kernel-module-ipt-owner kernel-module-ipt-redirect kernel-module-ipt-reject kernel-module-ipt-same kernel-module-ipt-tos kernel-module-ipt-ttl kernel-module-ipt-ulog kernel-module-iptable-filter kernel-module-iptable-mangle kernel-module-iptable-nat kernel-module-ipv6 kernel-module-ipw kernel-module-ir-usb - kernel-module-isofs kernel-module-kaweth kernel-module-keyspan kernel-module-keyspan-pda kernel-module-khazad kernel-module-kl5kusb105 kernel-module-kobil-sct kernel-module-leds-s3c24xx kernel-module-libcrc32c kernel-module-loop kernel-module-lrw kernel-module-mcs7830 kernel-module-mct-u232 kernel-module-md4 kernel-module-michael-mic kernel-module-mos7720 kernel-module-mos7840
