Re: More on compile problem

[markus@infoscape.com]

--pgp-sign-Multipart_Wed_Jul__9_09:20:38_1997-1
Content-Type: text/plain; charset=US-ASCII

simos@athena.teiath.gr writes:
 >                 cd /usr/include
 >                 rm -rf asm linux scsi
 >                 ln -s /usr/src/linux/include/asm-i386 asm
 >                 ln -s /usr/src/linux/include/linux linux
 >                 ln -s /usr/src/linux/include/scsi scsi
 >
 > Whenever you replace your kernel with a newer version, you have to do
 > those symlinks.

As these are _symbolic_ rather than _hard_ links, there is no need to
restore them after installing a new kernel. Just make sure, that the
kernel source always resides in "/usr/src/linux"; the latter can very
well be a symbolic link to whatever version-specific directory you
want to store the kernel in. A very common configuration is to have
the kernel in a directory named "/usr/src/linux-2.0.30" and then
create a symbolic link "ln -s /usr/src/linux-2.0.30
/usr/src/linux". (BTW, you *never* want to use hard links for refering
to a directory!)


Markus

--
Markus Gutschke                         Internet: markus@infoscape.com
Infoscape, Inc                          Phone:    +1-415-537-3778
657 Mission Street, Suite 200
San Francisco, CA 94105

Disclaimer: The above message represents my personal opinion; It does
            not constitute an offical statement by Infoscape!

--pgp-sign-Multipart_Wed_Jul__9_09:20:38_1997-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP MESSAGE-----
Version: 2.6.2

iQCVAwUBM8O6VhqJqDLErwMxAQEdBQP/f7ts2pD+Q1dCMX9LsjPm2DZ5FoAUWrLB
G422l7AkKAjAb1zmJuPdZvyFDrA8GNGr0KtW+p2wUsyqa3vXQadWRGbbKxRBj1dK
d8eVwCNW7hDfw/mzcLjOIOQRfoLuwysZC5MpTC+DlKl7R1MuJW3vS6pGkDMH0615
83yHD54pqgQ=
=ZjNe
-----END PGP MESSAGE-----

--pgp-sign-Multipart_Wed_Jul__9_09:20:38_1997-1--