I would like to request the inclusion of zen kernel ebuilds into the portage tree. They are updated daily (stable/unstable versions) via GIT and used by several individuals on several distributions (momonga, arch, sourcemage - option within distro, yoper - default kernel of distro, debian, fedora, ubuntu, slackware) The most users using the kernel are gentoo users, followed by arch and then probably the next closest is debian or ubuntu. It is a desktop-oriented kernel (BFS and BFQ are both default choices - compared to CFS and CFQ), which includes very common and unique features at the same time (bfs scheduler - also cfs scheduler, bfq i/o scheduler, smapi support + thinkpad-sl support, nouveau, reiser4, ksm, PHC, fbcondecor, and numerous misc things - like logos+random logo selection, lirc, l7filter, ipmi sensors, gamecube/wii linux support, slqb slab allocator, compcache, cko, aufs, dsdt, TuxOnIce typically - but waiting for a few fixes before it will go back in) - irregardless, the list goes on and on. There is tons more minor things that make some options exposed and easier to understand/change. The kernel does not remove the cfs scheduler either, the cfs scheduler is still an option and is glorified with moderate tweaks/fixes/updates as deliberated on #ck/IRC (not to mention options like BFS X auto sched_iso and CFS boost) The zen kernel, when compared to the vanilla or gentoo kernel (doesn't really make a difference since gentoo kernel doesnt change any performance related things), will show tremendous increases in desktop performance across the board (particularly with the combination of bfs, bfs, tweaks, and slqb) - And not to mention, the inclusion of several features that people commonly use (smapi, thinkpad sl, dsdt, tuxonice, compcache, .........) The kernel is maintained through git, but patches are also released - and typically every release compiles with allmod and allyes configurations, and experience minimal bug reports. A few kernel/kernel project developers also ask zen to include features that way they can get user feedback and bug reports for their project. Patches are frequently available for stable and -rc releases, which apply directly over the vanilla patches. A maintainer(s) for the ebuilds could easily provided if needed. Reproducible: Always
Yeah! I want zen in portage too !!
+1 from me as well.
+1 I third that !
+2. There is no reason not to add it!
layman -a zen-overlay
The zen-overlay is no longer being supported by the zen devs.
@5: doesn't work for me ! zen-overlay doesn't even exist ! take a look at: http://git.zen-sources.org/
As commented the overlay is dead.
I took a closer look at it and there is an ebuild for the latest release in it http://gentoo-overlays.zugaina.org/zen-overlay/portage/sys-kernel/zen-sources/zen-sources-2.6.31-r1.ebuild Perhaps you should try to work together with the ebuild writter to enhance it. Second there is a live ebuild in the arcon overlay.
There is no zen overlay (the zen devs don't use gentoo), and the kernel in that one is way outdated and i've never even heard of it.
Created attachment 206998 [details] Zen-Sources 2.6.30-zen7 Updated ebuild for latest stable release zen-sources-2.6.30-zen7
Created attachment 207001 [details] Zen-Sources 2.6.31-zen3 Updated ebuild for latest stable release zen-sources-2.6.31-zen3
I would also like to add a few things to consider when this bug report is reviewed: Of course I am aware of previous bug reports to include various kernel patches in portage. And that they have been rejected due to the maintainers not wanting to support them. What makes this different than all of those is: 1. It is consistently updated and maintained through git by multiple developers (all of these previous patchsets have been maintained by a single individual, not group/groups) 2. There is not the amount of kernels as their used to be in portage (no more ck releases, no more mm releases, and several of the other sources are dead and no longer updated anyway) - plus any maintainer could be offered if needed - although updating is as simple as copying the ebuild and changing a number 3. I'd say more people use and demand zen than any of the previous (ok, maybe except for beyond on the arch distribution). Although the others had either generic or very very specific user bases - the zen user base includes anyone who runs a desktop - which happens to be most people. 4. Kernel developers and such like zen as it allows them feedback/bug reports for their code. I don't think any of the others had any interactions with any kernel developers. 5. It is not a patchset like the other kernels requested. It is maintained and revisioned through git - patches are diffed based on the git tags. It's an actual kernel tree (when you get zen.git you don't just get patches, it's a whole kernel) 6. It has developed a stable nature recently (zen-stable.git) still young, but as it looks now there are virtually no bugs now, save for upstream kernel bugs. Please consider all of these factors. I am even willing to post benchmarks of the 2.6.31-zen4 kernel versus 2.6.31.4 (or gentoo) kernels - the differences will be impressive.
Created attachment 207043 [details] Ebuild for 2.6.31-zen4 Updated and change the description to be more accurate, since we don't call zen a patchset (it isnt a series of patches - it's maintained in a git tree)
I am willing to maintain this package as much as I can ( I am on a long devaway status right now ) Is somebody (user or not ) willing to co-maintain it with me? We can create a git repository on github and I will add it on layman overlays as well So contact me if you want to help me maintain it and I will create a git repository. Plus I will add it on layman asap Thanks
Overlay is ready http://github.com/hwoarang/zen-sources Please try the zen-sources and report problems here I would like to thank Oisin O Malley and Brandon Berhent for their ebuilds I wont add them on portage yet because I want to ensure that they are not dangerous (:p) for everyday usage ;)
Thanks Markos, i ensure you they are not dangerous but hopefully you will find out soon enough :D (2.6.30-zen7 has a bfs problem, which I am working on now)
(In reply to comment #17) > Thanks Markos, > i ensure you they are not dangerous but hopefully you will find out soon enough > :D > > (2.6.30-zen7 has a bfs problem, which I am working on now) > 2.6.31-r4 seems to work ok here but I havent tested it enough yet
Created attachment 207130 [details] Ebuild for 2.6.30-zen8 ebuild for latest 2.6.30 zen, differences over zen7 is: - Matched BFS schedule function to 2.6.30 cfs - Fixed BFS won't boot on CONFIG_SMP - Tuxonice - BFS documentation added
Created attachment 207136 [details] proposed live zen-sources This is a quick and dirty ebuild for live zen-sources Since my net is extremely slow I can't clone the whole git repo at the moment, so if you have a fast internet connection, please test the current ebuild, and let me know the results Many thanks!
I am 100% against live ebuilds for our zen kernels. If you want live use git... There should only be ebuilds for tagged releases.
Zen in portage. This is a good thing.
(In reply to comment #21) > I am 100% against live ebuilds for our zen kernels. If you want live use git... This is what live ebuilds use. Git clone > There should only be ebuilds for tagged releases. > What is wrong with live ebuilds? They help our power ( and crazy ) users to be able to use those crazy kernel sources
(In reply to comment #23) > (In reply to comment #21) > > I am 100% against live ebuilds for our zen kernels. If you want live use git... > This is what live ebuilds use. Git clone > > There should only be ebuilds for tagged releases. > > > What is wrong with live ebuilds? They help our power ( and crazy ) users to be > able to use those crazy kernel sources > Tpse power (and crazy) users should be using git directly then, so that they can do things like git-bisect if they want to track down a bug or cherry-pick a commit in a testing branch. If a user really needs such a new kernel that a released kernel (with a patch applied to a vanialla kernel) we want them using git.
Here we are: Zen is back up at: zen-kernel.org Git is located at: git.zen-kernel.org Patches will soon be uploaded as well. Thanks guys!
Great! Ebuilds are up and running on overlay. If there are not futher objections or proposed modifications, 2.6.30 and 2.6.31 sets will hit the tree tonight Thanks
Plus I need someone with minor git experience, to commit the upcoming zen-sources ebuilds whilst I am on a my devaway ( my next devaway period starts on Thursday morning ) Thanks
+*zen-sources-2.6.31-r4 (20 Oct 2009) +*zen-sources-2.6.30-r9 (20 Oct 2009) + + 20 Oct 2009; Markos Chandras <hwoarang@gentoo.org> + +zen-sources-2.6.30-r9.ebuild, +zen-sources-2.6.31-r4.ebuild, + +metadata.xml: + Initial commit of zen-sources. Fixes bug #288512. Thanks to Brandon + Berhent + <cheater1034@gmail.com> for the initial ebuilds + Committed. Thanks for reporting this :) Enjoy your band new kernel sources zen-sources overlay will remain a testing place for safety reasons
