Banuiesc ca nu este o greseala sau o inconsistenta in carte, dar poate cineva ma lumineaza, ca eu am facut ca Linus si totul e ok.
Din Securing and Optimizing Linux: 7.2. Uninstallation and Optimization ........ 1. We must copy the archive file of the Kernel to the /usr/src directory and move to this directory. ..... Remove the Linux kernel headers directory with the following command: [root@deep ] /src#rm -rf linux-2.2.xx ............... To uninstall the linux kernel RPM, use the following command: [root@deep ] /src#rpm -e --nodeps kernel-headers kernel Aiiie!!! chiar trebuie? .......... 1. The asm, and linux subdirectories are a soft link to the real include kernel source header directories needed for our Linux architecture, for example /usr/src/linux/include/asm-i386 for asm. Type the following commands on your terminal: [root@deep ]/src#cd /usr/include/ [root@deep ] /include#rm -rf asm linux [root@deep ] /include#ln -s /usr/src/linux/include/asm-i386 asm [root@deep ] /include#ln -s /usr/src/linux/include/linux linux In: http://www.uwsg.iu.edu/hypermail/linux/kernel/0007.3/0587.html Linus zice ca: ........ >/usr/include/asm is a symlink to /usr/src/linux/include/asm, as in the >original distribution but /usr/src/linux is a 2.4.0-testX tree. >With a 2.2.X source tree, it does not produce any warning. I've asked glibc maintainers to stop the symlink insanity for the last few years now, but it doesn't seem to happen. Basically, that symlink should not be a symlink. It's a symlink for historical reasons, none of them very good any more (and haven't been for a long time), and it's a disaster unless you want to be a C library developer. Which not very many people want to be. The fact is, that the header files should match the library you link against, not the kernel you run on. ..... Now, if you start mixing a new kernel header file with an old binary "glibc", you get into trouble. The new kernel header file will use the _new_ "struct X", because it will assume that anybody compiling against it is after the new-and-improved interfaces that the new kernel provides. .......... I would suggest that people who compile new kernels should: - NOT do so in /usr/src. Leave whatever kernel (probably only the header files) that the distribution came with there, but don't touch it. - compile the kernel in their own home directory, as their very own selves. No need to be root to compile the kernel. You need to be root to _install_ the kernel, but that's different. - not have a single symbolic link in sight (except the one that the kernel build itself sets up, namely the "linux/include/asm" symlink that is only used for the internal kernel compile itself) ........ Paul On Mon, 2001-11-19 at 18:07, Mircea MITU wrote: > > On Mon, 2001-11-19 at 17:48, Stoicescu, Mircea wrote: > > > > Are cineva $subj? in format pdf sau ceva printabil, oricum? > > Sau un link de dl? > > format text > >http://www.ibiblio.org/pub/Linux/docs/linux-doc-project/solrhe/Securing-Optimizing-Linux-RH-Edition-v1.3.txt > 1.7 Mb > > > --- > Send e-mail to '[EMAIL PROTECTED]' with 'unsubscribe rlug' to > unsubscribe from this list. -- Attached file included as plaintext by Listar -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA7+TQMIiHXb2xfh64RAoCGAJ4qvP00mcKUBU/nC6pk0lTXI9NqrACbBcmg anlRc+MuTJvikKmS4oDgwh8= =uU3h -----END PGP SIGNATURE----- --- Send e-mail to '[EMAIL PROTECTED]' with 'unsubscribe rlug' to unsubscribe from this list.
