Bugs item #1121809, was opened at 02/13/05 07:25
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://test.sf.net/tracker/?func=detail&atid=109368&aid=1121809&group_id=9368

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Programming environment
Group: 4.1
>Status: Closed
Resolution: Fixed
Priority: 9
Submitted By: Duane Berry (dmberry)
Assigned to: David N. Lombard (dnl)
Summary: client build fails for non-default kernel

Initial Comment:
When I tried to build a client from a non-default,
non-rpm kernel the client image was incomplete.  I
haven't had time to test this but I  _think_ the
problem is in the kernel_picker script. 

I noticed that the module paths are "lib/modules"
rather than "/lib/modules".  This is consistent with
what's not happening in the client build.  Modding
kernel_picker to force absolute paths froom root should
fix this problem.

----------------------------------------------------------------------

>Comment By: Nobody/Anonymous (nobody)
Date: 07/12/05 22:21

Message:
Logged In: NO 

This artifact has been closed automatically because no submitter feedback was 
received within administrator-specified timeout period.

----------------------------------------------------------------------

Comment By: David N. Lombard (dnl)
Date: 03/22/05 23:51

Message:
Logged In: YES 
user_id=27334

Deleting      
packages/kernel_picker/RPMS/kernel_picker-1.4-2.noarch.rpm
Adding  (bin) 
packages/kernel_picker/RPMS/kernel_picker-1.4.1-3.noarch.rpm
Deleting      
packages/kernel_picker/SRPMS/kernel_picker-1.4-2.src.rpm
Adding  (bin) 
packages/kernel_picker/SRPMS/kernel_picker-1.4.1-3.src.rpm
Sending        packages/kernel_picker/scripts/post_clients
Sending       
packages/kernel_picker/scripts/post_server_rpm_uninstall
Transmitting file data ....
Committed revision 3070.


----------------------------------------------------------------------

Comment By: David N. Lombard (dnl)
Date: 03/22/05 23:45

Message:
Logged In: YES 
user_id=27334

OK. So it now works correctly, if and only if you have a
modular kernel.  That's a huge improvement, and probably
where I'll have to leave it for 4.1 :-|

----------------------------------------------------------------------

Comment By: David N. Lombard (dnl)
Date: 03/22/05 09:52

Message:
Logged In: YES 
user_id=27334

Found still more errors.  INITRD has *never* been supported,
hardwired to N.  Other errors have not been seen due to
lucky use of shorter kernel versions prior to this.  Still
expecting solution...

----------------------------------------------------------------------

Comment By: John (muglerj)
Date: 03/18/05 13:44

Message:
Logged In: YES 
user_id=505737

Setting this to 4.1 and a 9 pri.

----------------------------------------------------------------------

You can respond by visiting: 
https://test.sf.net/tracker/?func=detail&atid=109368&aid=1121809&group_id=9368


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to