Bug 122114 - /usr/src/kernel-2.6 link to current kernel source does not appear
Summary: /usr/src/kernel-2.6 link to current kernel source does not appear
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-30 16:58 UTC by Andrey Bondarenko
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-04-30 17:04:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Andrey Bondarenko 2004-04-30 16:58:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.2; Linux; ru, ru_RU, ru_RU.UTF-8) (KHTML, like Gecko)

Description of problem:
/usr/src/kernel-2.6 link to current kernel source does not appear after installation

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.
    

Additional info:

This link may be usefull for compilation of some drivers and special kernel modules.

Comment 1 Arjan van de Ven 2004-04-30 17:04:34 UTC
this is done on purpose; the management of that link was really messy.
In addition you can't use the files in /usr/src/kernel-2.6.anything
for buildling modules against (just as you really shouldn't in 2.4 but
it worked there by accident).


Comment 2 Andrey Bondarenko 2004-04-30 17:19:55 UTC
Well, is this bug/feature? And why in /usr/include/linux obsolete 
header stored? 

Comment 3 Arjan van de Ven 2004-04-30 17:21:20 UTC
even in 2.2 and 2.4 modules HAVE to build against
/lib/modules/`uname -r `/build/include
just it happens to be that that is a symlink into /usr/src in those
older kernel rpms.


Comment 4 Andrey Bondarenko 2004-04-30 17:54:51 UTC
OK, I see, it's my misundrestanding, sorry for annoying you :-). Have 
a nice day. 


Note You need to log in before you can comment on or make changes to this bug.