Re: Bug#18513: kernel-headers-2.0.32: sets /usr/src/linux symlink on upgrade
/usr/src/linux has always been the location of the kernel and is primarily
a user responsibility. It cannot be moved to another location. Messing
around with it is wrong if it exists. And moving the symlink to your
headers when its pointing to a perfectly fine kernel tree is definitely a
On 22 Feb 1998, Manoj Srivastava wrote:
> >>"clameter" == clameter <firstname.lastname@example.org> writes:
> clameter> Package: kernel-headers-2.0.32 Version: 2.0.32-5
> clameter> Please do not touch the /usr/src/linux symlink on
> clameter> upgrade. Its bad enough that the package is messing around
> clameter> with /usr/src.
> Sorry. /usr/src is under vendor jurisdiction. Read the FHS and
> the FSSTND. This has been discussed on policy *and* debeian devel,
> and I do not think you should use the bug system to exress your
> clameter> One idea: Is it possible to move the kernel-headers out of
> clameter> /usr/src?
> I do not hink so.
> clameter> I.e. install them in /usr/include/kernel-headers-2.0.32 and
> clameter> put symlinks into those dirs? The kernel-headers are part of
> clameter> the include files after all.
> clameter> I do not have a 2.0.32 kernel but I need the headers for
> clameter> compilation.
> Please read the FASQ about the headers. That reflects Debian
> policy. You can find it in /usr/doc/kernel-headers-2.0.32/
> If you disagree, get the FHS and policy changed.
> I am closing this bug.
> Maintain eternal vigilance, small squishy thing, and kill anything
> that threatens. -- Viver farewell saying.
> Manoj Srivastava <email@example.com> <http://www.datasync.com/%7Esrivasta/>
> Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .