building kernel modules
In latest VirtualBox release there was an issue with building kernel modules for LTS kernel 3.10 which was basically caused by missing KERNELRELEASE definition. Since for one module build depends on target kernel version, the decision was made incorrectly in the absence of above var. Now from top level Makefile in kernel-headers: KERNELRELEASE = $(shell cat include/config/kernel.release 2> /dev/null) kernel.release file is fine and contains correct value, however the implicit requirement is to have $PWD pointing to kernel headers top dir. That's not the case for our %build_kernel_modules macro which uses O=$PWD/o in turn causing `cd $O` before evaluating KERNELRELEASE. As a result KERNELRELEASE ends up empty. As I'm not really proficient with build process of kernel modules, can someone advise if O= is really necessary or is there some other way to fix the issue? ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: PLD New Rescue th2015-1.5
On 2016-04-19 15:59, Grzesiek Pycia wrote: Works fine for me, both 32&64bit. Under qemu/kvm it does not power off machine, but version th-2014 stops on "System halted" to. On 2016-04-20 18:07, Elan Ruusamäe wrote: reported okay with: proxmox-ve 4.1-41, pve-qemu-kvm 2.5-9 Thanks! I'll remove the 'pre-release' flag on GitHub. Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: bacula versions
looks like 7.2.0 is older than 7.0.5? like 7.2 is development branch for 7.0? huh? and they both result v14 database? so i'm a bit confused of their releases, and what version series we should stick in pld? Its not older. Bacula isn't always providing all SQL migration paths and scripts in their tarballs, you have to obtain proper ones from older tarballs if doing bigger version jump. Its not the first time its that way. AFAIR there was no DB update after 5.x to 7.x series switch or it was mere cosmetics. I may be wrong however, I've switched to 7.x series back in 2014. the problem i have is that i have bacula5 director, and having upraded clients to bacula7 results authentication failures yet if i read 7.4.0 release notes http://blog.bacula.org/release-7-4-0/ it claims: " Upgrading should be easy since there is no database change and all older File Daemons should remain compatible with Bacula 7.4.0." of course i don't know do they claim if 5.2 clients can connect there or not Director will work with all older clients, but will not work with any newer clients. If client is newer than director it will be rejected. It is explained in bacula documentation. You either have to upgrade your director or downgrade the clients. There is no other way to make it work due to changes made in client-director communication protocol. FYI there is bacula 7.4.0 in TLD git. Feel free to merge it if you want. M. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: bacula versions
looks like 7.2.0 is older than 7.0.5? like 7.2 is development branch for 7.0? huh? and they both result v14 database? so i'm a bit confused of their releases, and what version series we should stick in pld? Its not older. Bacula isn't always providing all SQL migration paths and scripts in their tarballs, you have to obtain proper ones from older tarballs if doing bigger version jump. Its not the first time its that way. AFAIR there was no DB update after 5.x to 7.x series switch or it was mere cosmetics. I may be wrong however, I've switched to 7.x series back in 2014. the problem i have is that i have bacula5 director, and having upraded clients to bacula7 results authentication failures yet if i read 7.4.0 release notes http://blog.bacula.org/release-7-4-0/ it claims: " Upgrading should be easy since there is no database change and all older File Daemons should remain compatible with Bacula 7.4.0." of course i don't know do they claim if 5.2 clients can connect there or not Director will work with all older clients, but will not work with any newer clients. If client is newer than director it will be rejected. It is explained in bacula documentation. You either have to upgrade your director or downgrade the clients. There is no other way to make it work due to changes made in client-director communication protocol. FYI there is bacula 7.4.0 in TLD git. Feel free to merge it if you want. M. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
