Arch Linux User Repository

As for yaourt i will still use it because it's great for other aur pakckages ( or at least i did't find better one), and it can install this package so for now i stick with it. I'am using virtualbox_bin PKGBUILD from AUR for vbox and "/etc/rc.d/vboxdrv setup" script for installing modules As fior config here it is , but i can say that it's lightly modified original arch linux config so nothing special, didn't have time to create new one for this http://paste2.org/p/1121994

I really, really do not recommend to use yaourt for this package. As for your third point, it'd be great if you could upload your config so that I can check, what's wrong. VBox works perfectly fine over here.

First of all good work on this PKBUILD. Second when i installed it with yaourt i get that i installed kernel26-zen , but i don't get information that zen-kernel is installed so i will always need to remeber about this package and it don't update when i use yaourt --devel (like mplayer-svn aur package or deluge-svn ) which is great way to update development packages. Third when i try to compile vbox module i get Makefile:170: *** Error: /usr/src/linux (version 2.6.36-zen0-ARCH-20101112-stable) does not match the current kernel (version 2.6.36-zen0-ARCH-20101112-stable-00217-ga3dd510). Stop. cp: nie można wykonać stat na `/tmp/vboxdrv-Module.symvers': Nie ma takiego pliku ani katalogu Makefile:105: *** Error: /usr/src/linux (version 2.6.36-zen0-ARCH-20101112-stable) does not match the current kernel (version 2.6.36-zen0-ARCH-20101112-stable-00217-ga3dd510). Stop. cp: nie można wykonać stat na `/tmp/vboxdrv-Module.symvers': Nie ma takiego pliku ani katalogu Makefile:101: *** Error: /usr/src/linux (version 2.6.36-zen0-ARCH-20101112-stable) does not match the current kernel (version 2.6.36-zen0-ARCH-20101112-stable-00217-ga3dd510). Stop. so i think maybe you change something in naming to get it working ?

Looking at the kernel26-lts package, which can be found in the core repository, I noticed that the package and file names of my package were wrong, so I've renamed them. The PKGBUILD now also installs the System.map file which might be interesting for debugging purposes. See the ChangeLog for a complete list of changes.

Unfortunately it appears that the tree is currently broken and all developers are offline. I created the _no_update option for such cases so that the user has the abilitly to revert to a stable tree. As a temporary solution you can uncomment the _no_update option in the PKGBUILD. Then navigate to src/zen-sources/ and run "git checkout -b tmp master~1". When the issue is resolved, run "git checkout master; git branch -D tmp" and unset the _no_update option. I'm sorry for that, but as this is a live repository, things can and will(!) break from time to time.

Added a workaround so that the AUR shows the correct package description.

I'm happy to announce, that I've completely rewritten the whole package from scratch. Now it is more lightweight, faster and more robust. Issues such as the missing zc0301 directory should never happen again due to the much more robust kernel headers installing part. You can maintain the GIT tree yourself if desired. Take a look at the PKGBUILD for that purpose. The PKGBUILD is also capable of properly fixing broken GIT trees. (thanks to zxy_64 for the hint) It makes use of the separate output directory feature of the kernel Makefile. The source tree remains untouched and only the necessary parts are built. Thus multiple rebuilds should be much faster now. Additionally, the package no longer ships a default config. It is up to you to create one that fits your needs. A default was useless anyway since the kernel is designed to be user configured. When that "magic 200 lines patch" was released a lot of users wanted to try zen-kernel. Unfortunately all the clone requests have stressed the server a lot and as each clone request requires ~500MB of RAM, the GIT daemon crashed when handling multiple requests at once. As a temporary solution the zen-kernel developers have limited the maximum connections in order to reduce the server's stress. This led to the fact that almost nobody was able to update his tree because all slots were taken by people that tried to clone it. Another issue was that people never kept a copy of the tree. They were probably using yaourt or similar utilities. Having successfully built the kernel, they removed the kernel source. Zen-kernel developers have requested more RAM for their server and it will arrive soon. As a temporary solution the PKGBUILD downloads a snapshot instead of cloning the tree. You can disable that behaviour by taking a look at the PKGBUILD however it is not recommended to to so.