Prev: gtk-gnutella
Next: Slack 11 'dnsmasq: failed to create listening socket: Address already in use
From: tinnews on 12 Oct 2006 08:20
tinnews(a)isbd.co.uk wrote:
> Eef Hartman <E.J.M.Hartman(a)math.tudelft.nl> wrote:
> > tinnews(a)isbd.co.uk wrote:
> > > Yes, I've found that now (I hadn't originally downloaded the source
> > > CDs) and have installed all the headers, modules and source for the
> > > 2.6.18 kernel.
> >
> > See other discussions about installing the kernel-headers (or the
> > README _in_ the same dir), in general, DON'T install them unless
> > you want to recompile glibc too. They are normally the "version
> > of the kernel headers the C library was compiled WITH", the kernel
> > itself has its OWN version of them in the kernel-source package.
> > The kernel-headers package is only to compile application software,
> > that is using the standard library calls to interface WITH the kernel.
> >
> Yes, I have read the warning and was aware of the issue but you have
> clarified it somewhat for me, thanks.
>
If I leave (well restore actually) /usr/src/linux as a symbolic link
to /use/src/linux/linux-2.4.33 is that sufficient to prevent any
problems?

I can recompile kernels to my hearts content then in
/usr/src/linux/linux-2.6.18 but the 'outside' world will see what was
there before I installed any of the 2.6.18 kernel packages.

--
Chris Green
From: Eef Hartman on 12 Oct 2006 11:19
tinnews(a)isbd.co.uk wrote:
> If I leave (well restore actually) /usr/src/linux as a symbolic link
> to /use/src/linux/linux-2.4.33 is that sufficient to prevent any
> problems?

No, the kernel-headers package installs in /usr/include/linux and
/usr/include/asm-i386 (which will linked to /usr/include/asm),
so will be available even if NO kernel sources at all have been installed.

The /usr/src/linux _link_ is just to provide a default "kernel source"
link for some (older) drivers (the newer ones use the link from
/lib/modules/<kernel version>/source (cq build), which is installed
by the kernel-modules package.
--
********************************************************************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M.Hartman(a)math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
********************************************************************
From: tinnews on 13 Oct 2006 04:27
Eef Hartman <E.J.M.Hartman(a)math.tudelft.nl> wrote:
> tinnews(a)isbd.co.uk wrote:
> > If I leave (well restore actually) /usr/src/linux as a symbolic link
> > to /use/src/linux/linux-2.4.33 is that sufficient to prevent any
> > problems?
>
> No, the kernel-headers package installs in /usr/include/linux and
> /usr/include/asm-i386 (which will linked to /usr/include/asm),
> so will be available even if NO kernel sources at all have been installed.
>
Ah, so i really ought to uninstall the 2.6.18 headers package and
re-install the 2.4.33 one.


> The /usr/src/linux _link_ is just to provide a default "kernel source"
> link for some (older) drivers (the newer ones use the link from
> /lib/modules/<kernel version>/source (cq build), which is installed
> by the kernel-modules package.

OK, thanks for all the info.

--
Chris Green
From: Eef Hartman on 13 Oct 2006 06:40
tinnews(a)isbd.co.uk wrote:
> Ah, so i really ought to uninstall the 2.6.18 headers package and
> re-install the 2.4.33 one.

Just "upgradepkg" it, using the 2.4.33 kernel-headers tgz file.

Essentially upgradepkg will replace any package with "another version" of
the same, so the real name should have been "replacepkg" <grin>.

>> The /usr/src/linux _link_ is just to provide a default "kernel source"

PS: it will normally point to "the last source" package you've installed
(you CAN install more than one of those:
lrwxrwxrwx 1 root root 14 2006-10-06 14:47 linux -> linux-2.6.16.7
drwxr-xr-x 15 root root 1024 2005-10-31 11:24 linux-2.4.31
drwxr-xr-x 20 root root 1024 2006-04-25 11:44 linux-2.6.16.7
drwxr-xr-x 20 root root 1024 2006-09-07 11:38 linux-2.6.17.8
on my own (10.2) system).
We've made a script that will set the link at each reboot to
"the source of the current bootup kernel", from which you can see
I'm currently running 2.6.16.7
The 2.6.17 one will probably be replaced with the one from Slack 11
but all of these are "custom" kernels, not the distributed binaries.
--
********************************************************************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M.Hartman(a)math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
********************************************************************
From: tinnews on 13 Oct 2006 09:47
Eef Hartman <E.J.M.Hartman(a)math.tudelft.nl> wrote:
> tinnews(a)isbd.co.uk wrote:
> > Ah, so i really ought to uninstall the 2.6.18 headers package and
> > re-install the 2.4.33 one.
>
> Just "upgradepkg" it, using the 2.4.33 kernel-headers tgz file.
>
> Essentially upgradepkg will replace any package with "another version" of
> the same, so the real name should have been "replacepkg" <grin>.
>
OK, so upgradepkg will go backwards as well as forwards, thanks.

--
Chris Green
First  |  Prev  | 
Pages: 1 2 3
Prev: gtk-gnutella
Next: Slack 11 'dnsmasq: failed to create listening socket: Address already in use