Prev: memory stick
Next: Lilo problem
From: Kees Theunissen on 16 Jan 2007 16:48
Eric Hameleers wrote:
> Grant wrote:
>
>
>>Slackware's placement of the kernel source under /usr/src is the old
>>way, quaint, but deprecated long ago. Should be harmless?
>
>
> Deprecated? This is where most distros if not all still place the
> kernel sources.
>
> Eric

And even scripts/patch-kernel in the kernel source defaults to that
place:

#! /bin/sh
# Script to apply kernel patches.
# usage: patch-kernel [ sourcedir [ patchdir [ stopversion ] [ -acxx ] ] ]
# The source directory defaults to /usr/src/linux, and the patch
# directory defaults to the current directory.
#
[snip]




Regards,

Kees.

--
Kees Theunissen.
From: Eef Hartman on 17 Jan 2007 03:42
Eric Hameleers <alien(a)penguin1.dyndns.org> wrote:
> You should point the installer to /usr/include/linux which is where
> Slackware keeps it's copy of the kernel headers (installed by the
> kernel-headers package).

That depends:
user space programs (applications) should use /usr/include/linux,
in which the headers _should_ match the kernel version the C library
(glibc) was compiled WITH. Because they will be linked against that
library, of course.

> Don't use /usr/src/linux/include ...

For kernel drivers (nvideo, vmware, etc.) you should use the real kernel
headers, NOT the ones in /usr/include/linux.
Most of their installers will do that automatic, though, so make sure the
/usr/src/linux and /lib/modules/<kernel_version>/build links DO point to
the real kernel source tree you're building that driver for.
--
********************************************************************
** 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: rshepard on 17 Jan 2007 14:13
On 2007-01-16, Peter <peter(a)localhost.com> wrote:

> Try this.
> http://www.filemirrors.com/search.src?type=begins&file=vmware
>
> VMWare for some reason, does not have the most recent version on its
> servers. However, if you download this, check its checksums against the
> following courtesy of the Gentoo Manifest.
>
> VMware-workstation-5.5.3-34685.tar.gz 111527809
> RMD160 ad664c254b8d4cf010fdccf833f75e7112b50696
> SHA1 55ed65a94a3058df95ee93ad46564619c324bfed
> SHA256 a46f7199957c96d25f25c401e10da3c81728409b1bbd62db1bebb3b8a568c595

Peter,

While VMware _does_ have 5.5.3 on their servers, I could not get a
complete download in three days of trying. On my DSL connection, 106M takes
a while, and after about 60% has been downloaded, the transfer speed drops
slowly. When it falls below some threshold value, the server stops
responding.

Using the ftp server in Russia, I was able to get the download in about 20
minutes. The nice thing about using ncftpget is that an interrupted download
is continued from the place it stopped rather than begun again. After about
70M were downloaded, the transfer speed started to drop. When it reached the
limits of my patience, I killed the process and re-started it. That brought
the speed back to where it started, and the download completed.

The SHA1 hash matched. On my system I have md5sum and sha1sum, but no
sha256sum.

Thanks very much,

Rich
First  |  Prev  | 
Pages: 1 2 3
Prev: memory stick
Next: Lilo problem