have an ? about the source code for the kernel after i compile my new kernel and install it do i need to keep the source code on the machine r can i remove it so i can free up alot of harddrive space i am thinking i can but just want to be sure! thanks again Bob
On Fri, 23 May 2003 21:26:04 -0400 (EDT)
N1UAN Bob
have an ? about the source code for the kernel after i compile my new kernel and install it do i need to keep the source code on the machine r can i remove it so i can free up alot of harddrive space i am thinking i can but just want to be sure! thanks again
Sometimes when you try to compile some programs it will look for the kernel's include files. They are in /usr/src/linux/include/linux and are usually copied to /usr/include/linux, but if you do copy them over, then you can probably delete your kernel source. But this isn't automatically done, IIRC. Why not comprimise? Just tar and gzip the source tree? You may want to apply a patch or get your old config out of it. Saving the config is a good idea, it can save you alot of time when you build your next kernel. -- use Perl; #powerful programmable prestidigitation
The 03.05.24 at 06:20, zentara wrote:
Why not comprimise? Just tar and gzip the source tree? You may want to apply a patch or get your old config out of it.
Or use "make clean" perhaps, then compress.
Saving the config is a good idea, it can save you alot of time when you build your next kernel.
It can also be get from /proc/config.gz, or using "make cloneconfig" with SuSE kernels. -- Cheers, Carlos Robinson
On Saturday 24 May 2003 01:43 pm, Carlos E. R. wrote:
The 03.05.24 at 06:20, zentara wrote:
Why not comprimise? Just tar and gzip the source tree? You may want to apply a patch or get your old config out of it.
Or use "make clean" perhaps, then compress.
Yes. Do a "make clean" at the very least. This will remove all the object files and will give you much needed space, then you will still have the header files and your kernel cfg. if you need to re-compile, or just compile a new module. However it will take longer to compile, but you seem to need space over time anyways. This is what I would do, I compile a kernel only once in a while. If you REALLY need space, then you should TGZ the source tree after doing a "make clean". Alternitevly, bzip2 seems to give better compression. When I see bzip and gzip kernels on the web, the bzip ones are at least a meg or two smaller. Just remember yo keep you header files "/usr/src/linux/include" i think, or you will be unzipping-rezipping your sourse alot to compile programs
Saving the config is a good idea, it can save you alot of time when you build your next kernel. Most definatly! I spend most of my time going through a new kernel and hitting spacebar (menuconfig) to get everything as modules.
It can also be get from /proc/config.gz, or using "make cloneconfig" with SuSE kernels.
Theres something I learned today :) ---------------------- Eric Bambach Eric@CISU.net ----------------------
Eric wrote:
This is what I would do, I compile a kernel only once in a while. If you REALLY need space, then you should TGZ the source tree after doing a "make clean". Alternitevly, bzip2 seems to give better compression. When I see bzip and gzip kernels on the web, the bzip ones are at least a meg or two smaller.
Just remember yo keep you header files "/usr/src/linux/include" i think, or you will be unzipping-rezipping your sourse alot to compile programs
There is no longer anything in the kernel source tree required for compiling user applications. Glibc now provides its own /usr/include/linux and /usr/include/asm. Mark
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mardi 27 Mai 2003 11:56, Mark Hounschell a écrit :
Just remember yo keep you header files "/usr/src/linux/include" i think, or you will be unzipping-rezipping your sourse alot to compile programs
There is no longer anything in the kernel source tree required for compiling user applications. Glibc now provides its own /usr/include/linux and /usr/include/asm.
Are you sure? If I remember correctly, it's strongly *not* recommended to use the headers from glibc, as they may not match the running kernel. - -- Thibaut Cousin Web : http://www.thibaut-cousin.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+0ze9fBjEv/Ah2egRAicHAJwOOBEba8hzt32zGWfIl+IExDVkGwCfVk5K X3bDyOUaGmKK5MV2NUU8Ybc= =5bIN -----END PGP SIGNATURE-----
Thibaut Cousin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le Mardi 27 Mai 2003 11:56, Mark Hounschell a écrit :
Just remember yo keep you header files "/usr/src/linux/include" i think, or you will be unzipping-rezipping your sourse alot to compile programs
There is no longer anything in the kernel source tree required for compiling user applications. Glibc now provides its own /usr/include/linux and /usr/include/asm.
Are you sure? If I remember correctly, it's strongly *not* recommended to use the headers from glibc, as they may not match the running kernel.
You only need the "real" ones if you are doing devel on a kernel module/driver. These "/usr/include/linux and /usr/include/asm" from the glibc package used to actually be links into /usr/src/linux. The kernel and glibc people agreed that this was bad and now glibc provides it own set of these headers. No user app "should" require the real ones located in the kernel source tree. Mark
participants (6)
-
Carlos E. R. -
Eric -
Mark Hounschell -
N1UAN Bob -
Thibaut Cousin -
zentara