Re: Recognizing Kernel Update to 2.4.12 -- CORRECTION
eDoc wrote: > > > You need to untar the source: > > [EMAIL PROTECTED]:/usr/src# tar -xvzf > > After that, change the directory name to 'linux', so that your > uncompressed, > > untarred sources are in /usr/src/linux: > > The usr/src/linux directory that was missing before has been created, > apparently > for some reason a reboot was necessary for it to show up. > > Problem: > > I only have linux-2.4.12.tar.gz file in /usr/src ... > > "find -name *2.4.12*" only finds > > "linux-2.4.12.tar.gz file in /usr/src" > > What is wrong, please? > > I have tried everything I have found in man, doc, etc. Nothing seems to > successfully extract the 2.4.12 kernel-source everyone keeps referring to. > > Thanks! Doc > > > [EMAIL PROTECTED]:/usr/src# mv linux > > > > [EMAIL PROTECTED]:/usr/src# cd linux The kernel tarballs from kernel.org are created in such a way as to create a dierctory called "linux" inside your current directory when you untar them. Thus, if you got linux-2.4.12.tar.gz from kernel.org and put it in /usr/src, then did a tar zxvf on it, the new kernel source for 2.4.12 is in /usr/src/linux. Because of this, the first steps, before even unpacking the kernel tarball, should be to either rm the /usr/src/linux symlink (usually it is a symlink to another directory), or, if it is in fact a real directory, to move it to a name like "linux-2.4.9" or whatever. Also because of this, after unpacking the new kernel tarball, it is recommended that you move the newly created "linux" directory to "linux-2.4.12" (in this case) and create a symlink from it to /usr/src/linux (ln -s /usr/src/linux-2.4.12 /usr/src/linux). hth, patrick
Re: Recognizing Kernel Update to 2.4.12 -- CORRECTION
eDoc wrote: > > > You need to untar the source: > > root@hostname:/usr/src# tar -xvzf > > After that, change the directory name to 'linux', so that your > uncompressed, > > untarred sources are in /usr/src/linux: > > The usr/src/linux directory that was missing before has been created, > apparently > for some reason a reboot was necessary for it to show up. > > Problem: > > I only have linux-2.4.12.tar.gz file in /usr/src ... > > "find -name *2.4.12*" only finds > > "linux-2.4.12.tar.gz file in /usr/src" > > What is wrong, please? > > I have tried everything I have found in man, doc, etc. Nothing seems to > successfully extract the 2.4.12 kernel-source everyone keeps referring to. > > Thanks! Doc > > > root@hostname:/usr/src# mv linux > > > > root@hostname:/usr/src# cd linux The kernel tarballs from kernel.org are created in such a way as to create a dierctory called "linux" inside your current directory when you untar them. Thus, if you got linux-2.4.12.tar.gz from kernel.org and put it in /usr/src, then did a tar zxvf on it, the new kernel source for 2.4.12 is in /usr/src/linux. Because of this, the first steps, before even unpacking the kernel tarball, should be to either rm the /usr/src/linux symlink (usually it is a symlink to another directory), or, if it is in fact a real directory, to move it to a name like "linux-2.4.9" or whatever. Also because of this, after unpacking the new kernel tarball, it is recommended that you move the newly created "linux" directory to "linux-2.4.12" (in this case) and create a symlink from it to /usr/src/linux (ln -s /usr/src/linux-2.4.12 /usr/src/linux). hth, patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Recognizing Kernel Update to 2.4.12 -- CORRECTION
> You need to untar the source: > [EMAIL PROTECTED]:/usr/src# tar -xvzf > After that, change the directory name to 'linux', so that your uncompressed, > untarred sources are in /usr/src/linux: The usr/src/linux directory that was missing before has been created, apparently for some reason a reboot was necessary for it to show up. Problem: I only have linux-2.4.12.tar.gz file in /usr/src ... "find -name *2.4.12*" only finds "linux-2.4.12.tar.gz file in /usr/src" What is wrong, please? I have tried everything I have found in man, doc, etc. Nothing seems to successfully extract the 2.4.12 kernel-source everyone keeps referring to. Thanks! Doc > [EMAIL PROTECTED]:/usr/src# mv linux > > [EMAIL PROTECTED]:/usr/src# cd linux
Re: Recognizing Kernel Update to 2.4.12
On Mon, Oct 29, 2001 at 12:11:58PM -0500, eDoc wrote:
> > you need to, as in the documentation, run make-kpkg from the top-level
> kernel
> > directory, which will depend on where you put your kernel source. This is
> typically
> > either /usr/src/linux or /usr/src/kernel-source-
> > glen
>
> kernel-source? You mean "linux-2.4.12.tar.gz?
>
> Or do you mean "linux-2.4.12.gz"?
>
> "linux-2.4.12.tar.gz" is in /usr/src and I tried to run "make-kpkg" there.
> No go.
I'll take you through my complete set of steps for building kernel
packages from pristine kernel.org source.
- Download whatever it is you're getting. I tend to grab a tarball
at one point and then grab the successive patches for a while until
the point where I get tired of typing "patch -p1". You might also
want to verify the kernel sources with the signatures distributed
from that site if you know how to use gpg.
- cd /usr/src
- Untar the source tarball from kernel.org. It should get unpacked
to a "linux" directory in /usr/src.
- Apply any patches I need.
- Move the kernel dir so the dir name contains a version, such as
"linux-2.4.13". (I'll assume I'm building 2.4.13 from here on
out.) So, something like "mv /usr/src/linux /usr/src/linux-2.4.13"
should do the trick. I do this so I can keep track of exactly what
version of the kernel source I have handy.
- Grab the source for any other modules you think you may need.
Debian packages module source as packages that you can install;
look for packages with names that end in "-source". ("dpkg --list
'*-source'" should give you a nice list.) Once you have package
names, just apt-get them.
- The source packages unpack their source as tarballs in /usr/src.
Unpack each one with:
cd /usr/src
(b)zcat foo.tar.(gz|bz2) | tar xvf -
Something like this should unpack them all:
cd /usr/src
for file in *.tar.gz; do zcat $file | tar xvf -; done
for file in *.tar.bz2; do bzcat $file | tar xvf -; done
It's important to be in /usr/src when you unpack the tarball, as
it's set up to unpack to just the right place for make-kpkg to find
it.
- cd /usr/src/linux-2.4.13
- Configure the kernel. This isn't Debian-specific. Some people
like "make menuconfig", others "make xconfig", others just plain
"make config". One handy tip: Debian kernel packages store their
configs in /boot/config-X.Y.Z, so you can start with a good kernel
config and go from there. If you do that and just want to be asked
the questions that are new since that kernel version, run "make
oldconfig".
- Pick a Debian package revision for your kernel stuff. I generally
pick something that describes the purpose of the kernel and a
version, such as "laptop.1".
- Run "make-kpkg clean".
- Run "make-kpkg --revision= kernel_image".
- If that succeeds, run "make-kpkg modules_image".
- If you think you may need to compile other modules for this kernel
after you've built other kernels with this source tree, run
"make-kpkg kernel_headers".
- cd /usr/src
- ls -l *deb
You should now have a list of Debian packages on your screen,
corresponding to the kernel packages you just built (and maybe some
older ones, if you've been building kernels before). Run a "dpkg -i"
on them, and you're all set.
Re: Recognizing Kernel Update to 2.4.12
From: "eDoc" <[EMAIL PROTECTED]> > > Somewhere folks are assuming that I am taking a step that they have not > explicitly stated and thus the creation of the critical kernel-source in the > necessary format in the necessary location is not happening. No, they're just assuming you understood the docs you read. Having built kernels in the past week, I knew for a fact that the README in the kernel-package pretty explicitly tells you you need to unpack the source. It's on line 7 (excluding whitespace) of /usr/share/doc/kernel-package/README.gz and just as obvious, though further down, in .../kernel-source-*/README.gz
RE: Recognizing Kernel Update to 2.4.12
Hey doc: I think we were all assuming a slightly higher level of linux-ness than you've got. I'd highly, highly suggest that you read all the docs online before you go into kernel compilation, particularly the ones about lilo (or grub) and booting to an alternate kernel-- you'll really want to be able to boot if you forget to include, say, IDE support, or your filesystem support or something like that. So, it looks like you've done some sort of 'apt-get install kernel-source-2.4.somethingorother', or downloaded the source from kernel.org, or somewhere else. You need to untar the source: [EMAIL PROTECTED]:/usr/src# tar -xvzf a .gz extension means it's been compressed with gzip. A tar extention means that the file is part of a unix Tape ARchive. A tgz extension means it's a tar archive that's been compressed with gzip. After that, change the directory name to 'linux', so that your uncompressed, untarred sources are in /usr/src/linux: [EMAIL PROTECTED]:/usr/src# mv linux [EMAIL PROTECTED]:/usr/src# cd linux Now, read the README files in there. It's going to say some stuff about make, make modules, make modules_install--- note that debian and make-kpkg does a bunch of this for you. What you NEED to do, however, is one of: [EMAIL PROTECTED]:/usr/src# make config [EMAIL PROTECTED]:/usr/src# make menuconfig [EMAIL PROTECTED]:/usr/src# make xconfig config is plain text, and kind of annoying, but it always works. menuconfig is ncurses-based (you'll need the libncurses5-dev package), and sort of like the debian install. xconfig will only work if you have x running, but it's nice if you like to use your mouse. go through all the menus. Read the helpfiles. RTFM. Have a web browser handy. Then, finally: [EMAIL PROTECTED]:/usr/src# make-kpkg clean [EMAIL PROTECTED]:/usr/src# make-kpkg --revision= kernel_image cd .. dpkg --install kernel-image-2.4.12-.deb double, no, triplecheck that lilo is pointing to a good kernel for the LinuxOLD tag. Run lilo again, just to be sure. Reboot. RTFM. YMMV. This could render your system unbootable, don't cry to me if it does, just fix it ;> Good luck. glen -Original Message- From: eDoc [mailto:[EMAIL PROTECTED] Sent: Monday, October 29, 2001 09:12 AM To: Glen Mehn; [email protected]; [email protected]; [email protected] Subject: Recognizing Kernel Update to 2.4.12 > you need to, as in the documentation, run make-kpkg from the top-level kernel > directory, which will depend on where you put your kernel source. This is typically > either /usr/src/linux or /usr/src/kernel-source- > glen kernel-source? You mean "linux-2.4.12.tar.gz? Or do you mean "linux-2.4.12.gz"? "linux-2.4.12.tar.gz" is in /usr/src and I tried to run "make-kpkg" there. No go. Neither "linux-2.4.12.gz" or "kernel-source-2.4.12" exist according to "find -name linux-2.4.12*" and "find -name kernel-source-2.4.12*" issued from / This despite following all of the suggested commands from this list and others to cause it to be created (e.g. "tar -xvvzf linux-2.4.12.tar.gz") from docs or man or whatever resource I found that. Somewhere folks are assuming that I am taking a step that they have not explicitly stated and thus the creation of the critical kernel-source in the necessary format in the necessary location is not happening. As always I have perused man, docs, help, articles and posts, and every other online resource I can find. All assume things not explicitly stated or use terminology I do not as-of-yet understand fully. Help? Thanks! Doc
Re: Recognizing Kernel Update to 2.4.12
you need to unpack linux-2.4.12.tar.gz first. Use tar zxvf linux-2.4.12.tar.gz (better copy linux-2.4.12.tar.gz to /usr/local/src and then unpack it there). Then cd to the directory created and then do make-kpkg there. But you have to do make xconfig or make menuconfig there first). Please follow directions given in the installation guide for Debian 2.2 for custom kernel compilation. The directions are detailed and more than helpful to make your own kernel renchi On Mon, Oct 29, 2001 at 12:11:58PM -0500, eDoc wrote: > > you need to, as in the documentation, run make-kpkg from the top-level > kernel > > directory, which will depend on where you put your kernel source. This is > typically > > either /usr/src/linux or /usr/src/kernel-source- > > glen > > kernel-source? You mean "linux-2.4.12.tar.gz? > > Or do you mean "linux-2.4.12.gz"? > > "linux-2.4.12.tar.gz" is in /usr/src and I tried to run "make-kpkg" there. > No go. > > Neither "linux-2.4.12.gz" or "kernel-source-2.4.12" exist according to > "find -name linux-2.4.12*" and "find -name kernel-source-2.4.12*" issued > from / > This despite following all of the suggested commands from this list and > others to > cause it to be created (e.g. "tar -xvvzf linux-2.4.12.tar.gz") from docs or > man or > whatever resource I found that. > > Somewhere folks are assuming that I am taking a step that they have not > explicitly stated and thus the creation of the critical kernel-source in the > necessary format in the necessary location is not happening. > > As always I have perused man, docs, help, articles and posts, and every > other > online resource I can find. All assume things not explicitly stated or use > terminology I do not as-of-yet understand fully. > > Help? > > Thanks! Doc > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: Recognizing Kernel Update to 2.4.12 -- CORRECTION
> You need to untar the source: > root@hostname:/usr/src# tar -xvzf > After that, change the directory name to 'linux', so that your uncompressed, > untarred sources are in /usr/src/linux: The usr/src/linux directory that was missing before has been created, apparently for some reason a reboot was necessary for it to show up. Problem: I only have linux-2.4.12.tar.gz file in /usr/src ... "find -name *2.4.12*" only finds "linux-2.4.12.tar.gz file in /usr/src" What is wrong, please? I have tried everything I have found in man, doc, etc. Nothing seems to successfully extract the 2.4.12 kernel-source everyone keeps referring to. Thanks! Doc > root@hostname:/usr/src# mv linux > > root@hostname:/usr/src# cd linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Recognizing Kernel Update to 2.4.12
On Mon, Oct 29, 2001 at 12:11:58PM -0500, eDoc wrote:
> > you need to, as in the documentation, run make-kpkg from the top-level
> kernel
> > directory, which will depend on where you put your kernel source. This is
> typically
> > either /usr/src/linux or /usr/src/kernel-source-
> > glen
>
> kernel-source? You mean "linux-2.4.12.tar.gz?
>
> Or do you mean "linux-2.4.12.gz"?
>
> "linux-2.4.12.tar.gz" is in /usr/src and I tried to run "make-kpkg" there.
> No go.
I'll take you through my complete set of steps for building kernel
packages from pristine kernel.org source.
- Download whatever it is you're getting. I tend to grab a tarball
at one point and then grab the successive patches for a while until
the point where I get tired of typing "patch -p1". You might also
want to verify the kernel sources with the signatures distributed
from that site if you know how to use gpg.
- cd /usr/src
- Untar the source tarball from kernel.org. It should get unpacked
to a "linux" directory in /usr/src.
- Apply any patches I need.
- Move the kernel dir so the dir name contains a version, such as
"linux-2.4.13". (I'll assume I'm building 2.4.13 from here on
out.) So, something like "mv /usr/src/linux /usr/src/linux-2.4.13"
should do the trick. I do this so I can keep track of exactly what
version of the kernel source I have handy.
- Grab the source for any other modules you think you may need.
Debian packages module source as packages that you can install;
look for packages with names that end in "-source". ("dpkg --list
'*-source'" should give you a nice list.) Once you have package
names, just apt-get them.
- The source packages unpack their source as tarballs in /usr/src.
Unpack each one with:
cd /usr/src
(b)zcat foo.tar.(gz|bz2) | tar xvf -
Something like this should unpack them all:
cd /usr/src
for file in *.tar.gz; do zcat $file | tar xvf -; done
for file in *.tar.bz2; do bzcat $file | tar xvf -; done
It's important to be in /usr/src when you unpack the tarball, as
it's set up to unpack to just the right place for make-kpkg to find
it.
- cd /usr/src/linux-2.4.13
- Configure the kernel. This isn't Debian-specific. Some people
like "make menuconfig", others "make xconfig", others just plain
"make config". One handy tip: Debian kernel packages store their
configs in /boot/config-X.Y.Z, so you can start with a good kernel
config and go from there. If you do that and just want to be asked
the questions that are new since that kernel version, run "make
oldconfig".
- Pick a Debian package revision for your kernel stuff. I generally
pick something that describes the purpose of the kernel and a
version, such as "laptop.1".
- Run "make-kpkg clean".
- Run "make-kpkg --revision= kernel_image".
- If that succeeds, run "make-kpkg modules_image".
- If you think you may need to compile other modules for this kernel
after you've built other kernels with this source tree, run
"make-kpkg kernel_headers".
- cd /usr/src
- ls -l *deb
You should now have a list of Debian packages on your screen,
corresponding to the kernel packages you just built (and maybe some
older ones, if you've been building kernels before). Run a "dpkg -i"
on them, and you're all set.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Recognizing Kernel Update to 2.4.12
From: "eDoc" <[EMAIL PROTECTED]> > > Somewhere folks are assuming that I am taking a step that they have not > explicitly stated and thus the creation of the critical kernel-source in the > necessary format in the necessary location is not happening. No, they're just assuming you understood the docs you read. Having built kernels in the past week, I knew for a fact that the README in the kernel-package pretty explicitly tells you you need to unpack the source. It's on line 7 (excluding whitespace) of /usr/share/doc/kernel-package/README.gz and just as obvious, though further down, in .../kernel-source-*/README.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Recognizing Kernel Update to 2.4.12
Hey doc: I think we were all assuming a slightly higher level of linux-ness than you've got. I'd highly, highly suggest that you read all the docs online before you go into kernel compilation, particularly the ones about lilo (or grub) and booting to an alternate kernel-- you'll really want to be able to boot if you forget to include, say, IDE support, or your filesystem support or something like that. So, it looks like you've done some sort of 'apt-get install kernel-source-2.4.somethingorother', or downloaded the source from kernel.org, or somewhere else. You need to untar the source: root@hostname:/usr/src# tar -xvzf a .gz extension means it's been compressed with gzip. A tar extention means that the file is part of a unix Tape ARchive. A tgz extension means it's a tar archive that's been compressed with gzip. After that, change the directory name to 'linux', so that your uncompressed, untarred sources are in /usr/src/linux: root@hostname:/usr/src# mv linux root@hostname:/usr/src# cd linux Now, read the README files in there. It's going to say some stuff about make, make modules, make modules_install--- note that debian and make-kpkg does a bunch of this for you. What you NEED to do, however, is one of: root@hostname:/usr/src# make config root@hostname:/usr/src# make menuconfig root@hostname:/usr/src# make xconfig config is plain text, and kind of annoying, but it always works. menuconfig is ncurses-based (you'll need the libncurses5-dev package), and sort of like the debian install. xconfig will only work if you have x running, but it's nice if you like to use your mouse. go through all the menus. Read the helpfiles. RTFM. Have a web browser handy. Then, finally: root@hostname:/usr/src# make-kpkg clean root@hostname:/usr/src# make-kpkg --revision= kernel_image cd .. dpkg --install kernel-image-2.4.12-.deb double, no, triplecheck that lilo is pointing to a good kernel for the LinuxOLD tag. Run lilo again, just to be sure. Reboot. RTFM. YMMV. This could render your system unbootable, don't cry to me if it does, just fix it ;> Good luck. glen -Original Message- From: eDoc [mailto:[EMAIL PROTECTED]] Sent: Monday, October 29, 2001 09:12 AM To: Glen Mehn; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Recognizing Kernel Update to 2.4.12 > you need to, as in the documentation, run make-kpkg from the top-level kernel > directory, which will depend on where you put your kernel source. This is typically > either /usr/src/linux or /usr/src/kernel-source- > glen kernel-source? You mean "linux-2.4.12.tar.gz? Or do you mean "linux-2.4.12.gz"? "linux-2.4.12.tar.gz" is in /usr/src and I tried to run "make-kpkg" there. No go. Neither "linux-2.4.12.gz" or "kernel-source-2.4.12" exist according to "find -name linux-2.4.12*" and "find -name kernel-source-2.4.12*" issued from / This despite following all of the suggested commands from this list and others to cause it to be created (e.g. "tar -xvvzf linux-2.4.12.tar.gz") from docs or man or whatever resource I found that. Somewhere folks are assuming that I am taking a step that they have not explicitly stated and thus the creation of the critical kernel-source in the necessary format in the necessary location is not happening. As always I have perused man, docs, help, articles and posts, and every other online resource I can find. All assume things not explicitly stated or use terminology I do not as-of-yet understand fully. Help? Thanks! Doc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Recognizing Kernel Update to 2.4.12
you need to unpack linux-2.4.12.tar.gz first. Use tar zxvf linux-2.4.12.tar.gz (better copy linux-2.4.12.tar.gz to /usr/local/src and then unpack it there). Then cd to the directory created and then do make-kpkg there. But you have to do make xconfig or make menuconfig there first). Please follow directions given in the installation guide for Debian 2.2 for custom kernel compilation. The directions are detailed and more than helpful to make your own kernel renchi On Mon, Oct 29, 2001 at 12:11:58PM -0500, eDoc wrote: > > you need to, as in the documentation, run make-kpkg from the top-level > kernel > > directory, which will depend on where you put your kernel source. This is > typically > > either /usr/src/linux or /usr/src/kernel-source- > > glen > > kernel-source? You mean "linux-2.4.12.tar.gz? > > Or do you mean "linux-2.4.12.gz"? > > "linux-2.4.12.tar.gz" is in /usr/src and I tried to run "make-kpkg" there. > No go. > > Neither "linux-2.4.12.gz" or "kernel-source-2.4.12" exist according to > "find -name linux-2.4.12*" and "find -name kernel-source-2.4.12*" issued > from / > This despite following all of the suggested commands from this list and > others to > cause it to be created (e.g. "tar -xvvzf linux-2.4.12.tar.gz") from docs or > man or > whatever resource I found that. > > Somewhere folks are assuming that I am taking a step that they have not > explicitly stated and thus the creation of the critical kernel-source in the > necessary format in the necessary location is not happening. > > As always I have perused man, docs, help, articles and posts, and every > other > online resource I can find. All assume things not explicitly stated or use > terminology I do not as-of-yet understand fully. > > Help? > > Thanks! Doc > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
