http://qa.mandrakesoft.com/show_bug.cgi?id=5221


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




------- Additional Comments From [EMAIL PROTECTED]  2003-16-09 17:16 -------
Can you verify that /sbin/installkernel is fixed in your system  
according to the patch: 
 
http://qa.mandrakesoft.com/attachment.cgi?id=732&action=view 
 
do you install the kernel or the kernel-source first ? 
 
I'm seeing some other weird things here... 
 
I'm installing the kernel-source first... 
my /usr/src now has: (since I have installed every source with rpm -i ...) 
linux-2.4.22-7mdk/ 
linux-2.4.22-8mdk/ 
linux-2.4.22-9mdk/ 
 
 
then when I installed the 9mdk kernel, I got a ~linux-2.4.22-9mdk symlink 
in the 7mdk and 8mdk directories... that points to the 9mdk 
 
(the /lib/modules/'uname -r'/~build symlink gets created correctly) 
 
Seems I have to take a second look at the installkernel script.. 
 

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: REOPENED
creation_date: 
description: 
Whenever new kernel is installed, the following message will be seen:

    ln: invalid option -- o
    Try `ln --help' for more information.

It's because there is a typo in do_create_link_source():

    version="`echo $version | sed 's/-BOOT//'`"
                                                                                
    local kernel_source=/usr/src/linux-$version
    if [ -d $kernel_source ]; then
        ln -sf $kernel-source /lib/modules/$kversion/build
    fi

The hyphen between "$kernel" and "source" should be underscore instead.
Otherwise "-source" will be parsed as option to ln, thus causing failure to
create the .../build symlink.

Reply via email to