From: <dav...@cn...> - 2013-04-19 15:45:41
|
Olivier, Thanks for the reply. This is a truncated resend as the original was over the 40KB limit and is awaiting moderator approval ... So are you looking at two switches(one for firmware inclusion and one for link ?) The link is needed to handle situations like below - rhel6.4 with three kernels installed( 2.6.32-358.2.1.el6.x86_64 current one). As you can see below the drbd module is actually a link to the module directory when it was initially installed. Subsequent kernel updates just link back. Obvioulsy RH does this - not sure about Centos or others. [root@vccstest1 modules]# find /lib/modules -type l -exec ls -al {} \; lrwxrwxrwx 1 root root 5 Oct 7 2012 /lib/modules/2.6.32-279.el6.x86_64/source -> build lrwxrwxrwx 1 root root 58 Feb 14 11:39 /lib/modules/2.6.32-279.el6.x86_64/weak-updates/drbd/drbd.ko -> /lib/modules/2.6.32-279.14.1.el6.x86_64/extra/drbd/drbd.ko lrwxrwxrwx 1 root root 46 Oct 7 2012 /lib/modules/2.6.32-279.el6.x86_64/build -> ../../../usr/src/kernels/2.6.32-279.el6.x86_64 lrwxrwxrwx 1 root root 5 Dec 17 12:48 /lib/modules/2.6.32-279.14.1.el6.x86_64/source -> build lrwxrwxrwx 1 root root 51 Dec 17 12:48 /lib/modules/2.6.32-279.14.1.el6.x86_64/build -> ../../../usr/src/kernels/2.6.32-279.14.1.el6.x86_64 lrwxrwxrwx 1 root root 5 Mar 14 13:25 /lib/modules/2.6.32-358.2.1.el6.x86_64/source -> build lrwxrwxrwx 1 root root 58 Mar 14 13:25 /lib/modules/2.6.32-358.2.1.el6.x86_64/weak-updates/drbd/drbd.ko -> /lib/modules/2.6.32-279.14.1.el6.x86_64/extra/drbd/drbd.ko lrwxrwxrwx 1 root root 50 Mar 14 13:25 /lib/modules/2.6.32-358.2.1.el6.x86_64/build -> ../../../usr/src/kernels/2.6.32-358.2.1.el6.x86_64 [root@vccstest1 modules]# I agree a more deterministic way for firmware is needed - my hack was to copy ALL of /lib/firmware. At the time of uyok generation we should be able to be more selective. As per the lvcreate hang it definitely looks like a lvm tools issue(it did work successfully with a previous pkg). No I didn't try without lvm as the host I was testing with was lvm - have you or anyone else tested without lvm - it should be the same. Thanks again Ugly weather here with snow on the car this morning ... maybe I should give up on the bike and go back to the skis ! David David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 hi David, Thanks a lot for your report. Thanks also for the patch. It is not yet integrated because I want to have a deterministic way of managing firmwares. I don't want to end in a situation when errors occure because guy A had installed a package and guy B didn't. I think that the best way for the moment is to add command line switch to include system installed firmwares . By this way, the user will known that the problem can come from a missing firmware. For the L switch, I understand that it is needed for the firmware sync, but this triggers some problems elsewhere were files a copied twice instead of having a link and a file. using L switch is a quick hack but the image gets even bigger (already very big). I'm aware of both issues, and I'll find a solution. The freeze problem is more problematic. Did you try without using LVM? If it works, then it may be a bad lvm tools build (using system libs instead of initrd built libs..... I tryed to fix most of them, but lvm may be one of them. Best regards, PS: Right now, I'm working on debian systemimager oscar-packager. I'll be back soon. Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: Dav...@cn... |