Re: Re: Compiling the kernel

[Matt Zagrabelny]

On Wed, 2004-11-24 at 16:03 +, [EMAIL PROTECTED] wrote:
> OK, I've tried recompiling 2.6.9 with the various options I think I want, 
> setting some items as modules and so on. make-kpkg runs for ages, lots of 
> screen output (lists of files or modules with CC next to them, etc) and then 
> I get lots of "unrecognised symbol" errors (I think that's what it said).  
> It fails to produce a deb file, presumably as a result.  I'm using commands 
> (as root): 
> 
> make menuconfig
> make dep
> make-kpkg clean
> make-kpkg revision=custom1.0 kernel_image 
> 
> What might the problem be?  And/or, how can I track it down? 
> 
>  - Joe
> 

there is a good howto:

http://newbiedoc.sourceforge.net/tutorials/kernel-pkg/index-kernel-pkg.html

-matt zagrabelny


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Re: Compiling the kernel

[joebosak]

OK, I've tried recompiling 2.6.9 with the various options I think I want, 
setting some items as modules and so on. make-kpkg runs for ages, lots of 
screen output (lists of files or modules with CC next to them, etc) and then 
I get lots of "unrecognised symbol" errors (I think that's what it said).  
It fails to produce a deb file, presumably as a result.  I'm using commands 
(as root): 

make menuconfig
make dep
make-kpkg clean
make-kpkg revision=custom1.0 kernel_image 

What might the problem be?  And/or, how can I track it down? 

- Joe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling the kernel

[David Mandelberg]

[EMAIL PROTECTED] wrote:
> kernels, some even boot but none does what I want. One thing I need to
> know is how to get modules to compile... there doesn't seem to be any
Most modules come with the kernel source code, you just have to compile
them as modules (i.e. 'm' instead of 'y' or  in menuconfig).

> source code on my system except for pcmcia-cs (which I downloaded, and
> which gives an error message during compilation).  Where do I get this
> from?
pcmia-cs probably needs you to compile and install your custom kernel
first so that it can have access to config options and the headers.

> I'm trying to get a kernel for 486 laptop that contains pcmcia and
> wireless (for a WPC11 v3 card).  Also I want to set up the system as a
> firewall so I want IP masquerading etc.
Just enable all relevant options (firewall options are under
iptables/netfilter).

> Finally, I have tried loading the 2.4.18-bf2.4 configuration file, as a
> starting point, but this gives loads of error messages about things not
> being found.  So another question would be - would I be better off using
> something like 2.4.21?
You can't use a 2.4.x config file with a 2.6.x kernel. If you want a
good starting point, install kernel-package and use one of those configs.

-- 
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GAT/CM$/CS>$/CC/IT$/M/S/O/U dpu s+:++ !a C++$>C+++$
UB+++>$L$*-- P+>++$ L+++()$ E-(---) W+++>$ N(+) o? K-
w--(---) O? M V? PS++@ PE-@ Y+@ PGP++(+++)>$ t? 5? X? R tv--(-)
b++(+++)@ DI? D? G e-> h* r? z*
--END GEEK CODE BLOCK--

David Mandelberg
[EMAIL PROTECTED]


signature.asc
Description: OpenPGP digital signature

Re: compiling the kernel

[Benedict Verheyen]

Brian wrote:
> I want to be able to turn some options off and on in the kerenl so how
> do i compile the kernel in a debian system???
>
>
> Thanks
> Brian

Look at this site: http://newbiedoc.sourceforge.net/
It has a very comprehensive explanation on how to compile
your own kernel the Debian way. It's a very good source.

Regards,
Benedict


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling the kernel

[Nano Nano]

On Sun, Feb 15, 2004 at 12:13:05AM -0600, Brian wrote:
> I want to be able to turn some options off and on in the kerenl so how 
> do i compile the kernel in a debian system???

install "kernel-package" with apt-get and then use "make-kpkg"


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling the kernel with GCC 3.3

[Marino Fernandez]

On Saturday 05 July 2003 5:09 am, Christophe Courtois wrote:
> Le Samedi 5 Juillet 2003 10:24, Marino Fernandez a déclamé :
> > Yes, that's what it seems. I had the same problem with 2.4.21... GCC
> > 2.95 and 3.2 work, but no 3.3.
>
From a practical standpoint (in other words... have I noticed anything 
different)... I will say... no. 2.95 and 3.2 did the job fine, and the kernel 
runs OK... I am sure there are some esotheric differences, but I am a simple 
Joe, not a kernel guru.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling the kernel with GCC 3.3

[Kevin McKinley]

On Sat, 5 Jul 2003 09:49:05 +0200
Raffaele Sandrini <[EMAIL PROTECTED]> wrote:

> Hi
> 
> I tried to compile a 2.4.20 kernel with GCC 3.3 and failed.
> I searched through several list and the web to find more infos. I found
> some docs about GCC3.1 and its implemetation (wich isnt).
> 
> Just to be sure: We still must use GCC 2.95 to compile the kernel, right?

No; 2.4.20 compiles with gcc 3.2.3 as well.

Kevin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling the kernel with GCC 3.3

[Christophe Courtois]

Le Samedi 5 Juillet 2003 10:24, Marino Fernandez a déclamé :
> Yes, that's what it seems. I had the same problem with 2.4.21... GCC
> 2.95 and 3.2 work, but no 3.3.

 I compile with 2.95 ; is there a difference for a user with 3.2 ? 

-- 
Christophe Courtois - Ostwald, Alsace, France
http://www.courtois.cc/ - Clé PGP : 0F33E837
--
Yet Mr. Sklyarov still languishes in jail, puzzled, no doubt, about
how a free society can jail someone for writing code that was legal
where written, just because he comes to the United States and gives
a report on encryption weaknesses.
-- Lawrence Lessig in the New York Times.
http://www.nytimes.com/2001/07/30/opinion/30LESS.html?ex=997510756&ei=1&en=2039852b8d9f2448


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: compiling the kernel with GCC 3.3

[Marino Fernandez]

On Saturday 05 July 2003 2:49 am, Raffaele Sandrini wrote:
> Hi
>
> I tried to compile a 2.4.20 kernel with GCC 3.3 and failed.
> I searched through several list and the web to find more infos. I found
> some docs about GCC3.1 and its implemetation (wich isnt).
>
> Just to be sure: We still must use GCC 2.95 to compile the kernel, right?
>
This issue has been on the list recently...

Yes, that's what it seems. I had the same problem with 2.4.21... GCC 2.95 and 
3.2 work, but no 3.3.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Compiling the kernel

[Paolo Alexis Falcone]

[EMAIL PROTECTED] wrote:

>Could those in the know of things , please outline how you would compile a 
>kernel
>(the steps) on a RedHat 7.0 system ?

Recently checked the user's manual on RH7.0 - doesn't mention custom-
compiling the kernel. I believe it's the traditional style (make dep,
make {menu,x}config, make dep, make bz{Image,disk}, make modules, 
make modules_install. Anyway, it works very well without the need to
make an rpm of the kernel. Haven't made an rpm as I'm much more
comfortable with debian.

On debian, it's much convenient (based on experience) to make a .deb 
package of the kernel. Debian has its own default way of placing
kernel modules thus I make it a point to keep it that way as it's 
much easier also to maintain.

Paolo Falcone

__
www.edsamail.com

Re: Compiling the kernel

[ajlewis2]

In linux.debian.user, you wrote:
> I have a new kind of doubt ..
> Could those in the know of things , please outline how you would compile a 
> kernel
> (the steps) on a RedHat 7.0 system ?
> Mr.Bish had done so for a Debian system as a footer on one of his mails .
> 
> I am having a current requirement ..  to disable module version support
> (&subsequently / on another date to re-enable it) .
> 
> I shall be grateful for all help you might render.
> 
> Thanks,
> ([EMAIL PROTECTED])
> Shyam
> 

I just use the directions in /usr/src/linux/README.  You have to get the
kernel source first.  It will probably be placed in a directory with the
kernel name.  You need to either change the name of the directory to 'linux'
or make a link to it called 'linux'.  Then you just follow the README.  It's
good to read it first, because there are changes with various kernel
versions.  Another good thing to look over is
/usr/src/linux/Documentation/Configure.help  That will tell you what is
available in that kernel.  

A very good idea is to copy /usr/src/linux/.config to a safe place if you
already have it.  Then after you do 'make mrproper' move it back.  This
would be the case if you were recompiling with the same source.  That way
you can just change what you want and not have to figure out what you need
all over again.  I believe there is a config file in  /boot if you have not
ever recompiled.  I have one called config-2.2.17 which must have been put
there when I first installed.  I don't know if that was from Debian or from
some other distro I've had on this computer.  You can check to see if you
have something like that if you don't have /usr/src/linux and have to get
the source.

Anita

Re: compiling the kernel

[Pete Meyer]

>> 3) In windows there is the idea of formating a partition
>> or a floppy.  Debian installation seem to do something similar.
>> How does it work in Linux, and what is the utility that does it?

I believe mkfs formatts a partition for linux (it doesn't make the partition).  
This is done mostly transparently during installation.  Mkfs also has an option 
to format ms-dos partitions, but I've had problems getting windows machines to 
read them (your milage may vary).



Who needs Cupid?  Matchmaker.com is the place to meet somebody.
FREE Two-week Trial Membership at http://www.matchmaker.com/home?rs=200015

Re: compiling the kernel

[Cam Ellison]

Thomas Delany wrote:
> 
> Re 3)  I don't have a lot of experience with this as I've usually just let
> the Debian install procedure set up the hard disk for me.  As far as
> partitioning the drive goes, Linux has an fdisk utility that is sort of the
> counterpart of the MS-DOS / Windows fdisk utility (check the man page /
> documentation).
> 
I suggest you sue cfdisk, rather than fdisk.  It's more sophisticated,
and in my (admittedly limited) experience less likely to lead you
astray.

> I believe that the Linux mkfs utility is the closest equivalent to the
> MS-DOS / Windows format command.  Again, check the man page / documentation
> for its options.  Anybody else out there feel free to correct me if I'm way
> off base here, as I'm not exactly an old hand at Linux.
> 
Yes.  If you are doing an installation for the first time, the install
procedure takes care of all this for you.

> I am not at all qualified to answer 4) for you.  Sorry.
> 
My own prejudice is to put it all into the kernel.  I don't think that
it reduces functionality that much.  If you have something that you
don't use very often, it may make more sense to modularize it.  I use
pretty much everything nearly every day. so have put it all in the
kernel.


-- 
Cam Ellison Ph.D. R.Psych.
>From Roberts Creek on B.C.'s incomparable Sunshine Coast
[EMAIL PROTECTED]
[EMAIL PROTECTED]

Re: compiling the kernel

[Thomas Delany]

Re 3)  I don't have a lot of experience with this as I've usually just let
the Debian install procedure set up the hard disk for me.  As far as
partitioning the drive goes, Linux has an fdisk utility that is sort of the
counterpart of the MS-DOS / Windows fdisk utility (check the man page /
documentation).

I believe that the Linux mkfs utility is the closest equivalent to the
MS-DOS / Windows format command.  Again, check the man page / documentation
for its options.  Anybody else out there feel free to correct me if I'm way
off base here, as I'm not exactly an old hand at Linux.

I am not at all qualified to answer 4) for you.  Sorry.

I have also entered the Linux world from the Windows world, as I suspect you
have, and can sympathize with you as far as the learning curve goes.  Hang
in there.

Tom Delany

- Original Message -
From: "Thomas Delany" <[EMAIL PROTECTED]>
To: "Alexander Gutfraind (Sasha)" <[EMAIL PROTECTED]>
Cc: 
Sent: Friday, March 09, 2001 12:59 PM
Subject: Re: compiling the kernel


> Re: 1)  The file System.map is created in the /usr/src/linux subdirectory.
>
> 2)  Looks like you have a hard disk that has > 1024 cylinders.  Go to the
> /etc subdirectory.
> Edit the file  lilo.conf and add the line:
> lba32
>
> to the file somewhere.  (You'll need to be logged in as root, or use the
su
> command.)  That should solve the Lilo problem.
>
> Text files in Linux are different than Windows.  Wordpad will display them
> correctly.
>
> Maybe someone else can help with 3) and 4).
>
> Tom Delany
>
> - Original Message -
> From: "Alexander Gutfraind (Sasha)" <[EMAIL PROTECTED]>
> To: 
> Sent: Friday, March 09, 2001 1:25 AM
> Subject: compiling the kernel
>
>
> > A newbie question:
> > 1) What's System map file, and where is it created
> > relative to the kernel source directory during
> > kernel compilation?
> >
> > 2) (perhaps related to (1) above)
> > Wheneve I try creating a boot floppy,
> > using 'installkernel ', I get a problem
> > as follows:
> >
> > Creating a lilo bootdisk...
> > mkdir /tmp/boot7403mke2fs -q /dev/fd0mke2fs
> > 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> > mount -t ext2 /dev/fd0 /tmp/boot7403cd
> > /tmp/boot7403cp
> > /boot/vmlinuz
> > /boot/boot.b
> > .lilo -C - <<-EOF2Fatal: geo_comp_addr:
> > Cylinder number is too big (1053 > 1023)
> > set +e; cd /; umount /dev/fd0; rmdir /tmp/boot7403
> > There was a problem creating the boot diskette.
> > Please make sure that you inserted the diskette into the
> > correct drive and that the disketteis not write-protected.
> >
> > [End of printout]
> > (I opened the file in win98 notepad, which does not read \n correctly.
> > Had to add newlines myself)
> >
> > What's the deal???
> >
> >
> > 3) In windows there is the idea of formating a partition
> > or a floppy.  Debian installation seem to do something similar.
> > How does it work in Linux, and what is the utility that does it?
> >
> >
> > 4) When compiling the kernel, does moving functionality into
> > modules reduces performance, and if so, is it worth cutting
> > the size of the kernel image?
> >
> > Thanks a lot!
> >
> > ___
> > Alexander Gutfraind (sasha) [EMAIL PROTECTED]
> >
>

Re: compiling the kernel

[Thomas Delany]

Re: 1)  The file System.map is created in the /usr/src/linux subdirectory.

2)  Looks like you have a hard disk that has > 1024 cylinders.  Go to the
/etc subdirectory.
Edit the file  lilo.conf and add the line:
lba32

to the file somewhere.  (You'll need to be logged in as root, or use the su
command.)  That should solve the Lilo problem.

Text files in Linux are different than Windows.  Wordpad will display them
correctly.

Maybe someone else can help with 3) and 4).

Tom Delany

- Original Message -
From: "Alexander Gutfraind (Sasha)" <[EMAIL PROTECTED]>
To: 
Sent: Friday, March 09, 2001 1:25 AM
Subject: compiling the kernel


> A newbie question:
> 1) What's System map file, and where is it created
> relative to the kernel source directory during
> kernel compilation?
>
> 2) (perhaps related to (1) above)
> Wheneve I try creating a boot floppy,
> using 'installkernel ', I get a problem
> as follows:
>
> Creating a lilo bootdisk...
> mkdir /tmp/boot7403mke2fs -q /dev/fd0mke2fs
> 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> mount -t ext2 /dev/fd0 /tmp/boot7403cd
> /tmp/boot7403cp
> /boot/vmlinuz
> /boot/boot.b
> .lilo -C - <<-EOF2Fatal: geo_comp_addr:
> Cylinder number is too big (1053 > 1023)
> set +e; cd /; umount /dev/fd0; rmdir /tmp/boot7403
> There was a problem creating the boot diskette.
> Please make sure that you inserted the diskette into the
> correct drive and that the disketteis not write-protected.
>
> [End of printout]
> (I opened the file in win98 notepad, which does not read \n correctly.
> Had to add newlines myself)
>
> What's the deal???
>
>
> 3) In windows there is the idea of formating a partition
> or a floppy.  Debian installation seem to do something similar.
> How does it work in Linux, and what is the utility that does it?
>
>
> 4) When compiling the kernel, does moving functionality into
> modules reduces performance, and if so, is it worth cutting
> the size of the kernel image?
>
> Thanks a lot!
>
> ___
> Alexander Gutfraind (sasha) [EMAIL PROTECTED]
>

Re: Compiling the Kernel.

[Nathan E Norman]

On Tue, Jun 20, 2000 at 10:21:40PM +0200, Kai Weber wrote:
> At 14:21 19.06.00, you wrote:
> 
> >Better yet:
> >
> >apt-get update; apt-get install kernel-package
> >make config (or menuconfig or xconfig)
> >make-kpkg clean
> >make-kpkg --revision=local. kernel_image
> >dpkg -i ../kernel-image-_local._i386.deb
> 
> 
> I did it. I made a new kernel with settings for my system. But now, 
> whenever I want to install a new package it wants to update the 
> kernel-image as well. I thought it will recognize the installed as a newer 
> version? 

Apparently a recent kernel-image package used an epoch.  To combat
this you need use an epoch in your version also.  I believe you would
do that like this:

  make-kpkg --revision=5:local. kernel_image

HTH,

-- 
Nathan Norman "Eschew Obfuscation"  Network Engineer
GPG Key ID 1024D/51F98BB7http://home.midco.net/~nnorman/
Key fingerprint = C5F4 A147 416C E0BF AB73  8BEF F0C8 255C 51F9 8BB7


pgpm4Fo8xTkTA.pgp
Description: PGP signature

Re: Compiling the Kernel.

[Nathan E Norman]

On Mon, Jun 19, 2000 at 08:02:52AM -0400, dyer wrote:
> Marc Miron wrote:
> 
> > Hi Everybody!!
> >
> > I'm trying to build a new kernel that has IP masqing/port forwarding
> > abilities and I've followed all the directions in the How-TOs and I just
> > can't seem to get it to work as after runing make config and setting it all
> > up, I run make clean;make install; make and after it has been working for
> > probably over an hour it just stops saying there is a file not found error.
> > I do not understand this because I would have thought that all the files
> > would have been included in the original .tar.gz file.  If there is some
> > other way of doing this, I'd be very gratefull of knowing about it.
> > Otherwise, If someone knows of a site with a decent selection of pre-build
> > kernels I'd also be grateful.  Otherwise, if anyone is interested in
> > building such a site, I've got plenty of room on my machine to host it.
> >
> >
> 
> Marc,
> Please post the error about what file it cannot find.  Also, you should not be
> running 'make install'. Take a look at the README in the /usr/src/linux 
> directory.
> You should be running:
> make mrproper
> make config (or menuconfig or xconfig)
> make dep
> make bzImage
> make modules
> make modules_install

Better yet:

apt-get update; apt-get install kernel-package
make config (or menuconfig or xconfig)
make-kpkg clean
make-kpkg --revision=local. kernel_image
dpkg -i ../kernel-image-_local._i386.deb

-- 
Nathan Norman "Eschew Obfuscation"  Network Engineer
GPG Key ID 1024D/51F98BB7http://home.midco.net/~nnorman/
Key fingerprint = C5F4 A147 416C E0BF AB73  8BEF F0C8 255C 51F9 8BB7


pgpoY1p1hIifR.pgp
Description: PGP signature

Re: Compiling the Kernel.

[dyer]

Marc Miron wrote:

> Hi Everybody!!
>
> I'm trying to build a new kernel that has IP masqing/port forwarding
> abilities and I've followed all the directions in the How-TOs and I just
> can't seem to get it to work as after runing make config and setting it all
> up, I run make clean;make install; make and after it has been working for
> probably over an hour it just stops saying there is a file not found error.
> I do not understand this because I would have thought that all the files
> would have been included in the original .tar.gz file.  If there is some
> other way of doing this, I'd be very gratefull of knowing about it.
> Otherwise, If someone knows of a site with a decent selection of pre-build
> kernels I'd also be grateful.  Otherwise, if anyone is interested in
> building such a site, I've got plenty of room on my machine to host it.
>
>

Marc,
Please post the error about what file it cannot find.  Also, you should not be
running 'make install'. Take a look at the README in the /usr/src/linux 
directory.
You should be running:
make mrproper
make config (or menuconfig or xconfig)
make dep
make bzImage
make modules
make modules_install

Again, look at the readme.

dyer

Re: Compiling the kernel?

[Ed Cogburn]

Tom Pfeifer wrote:
> 
> Well, not knowing any better, I fixed it by uninstalling my header and
> source packages (2.0.33), reinstalling the libc6-dev package, and then
> installing bin86 and the 2.0.34 source and header packages.
> 
> This left the usr/include directories (asm, linux, scsi) NOT set up as
> links. This is contrary to the source documentation, but agrees with the
> Debian licb6-dev document that Bob mentioned.
> 
> The configure and compile then went without a hitch, and "make zImage"
> left the kernel image file (278k)in arch/i386/boot as expected. It also
> left a file called vmlinux of about 680k in /usr/src/linux. I don't know
> the purpose of that file.


vmlinux is the uncompressed version of the kernel.  The psupdate
process needs it there to update the database the ps prog uses to
display info about a running kernel.  I don't know the details of what
ps needs from it.  Generaly, when you build a new kernel/modules you
also run psupdate to update the psdatabase file (in either /boot or /etc
- not sure what the offical location for this file is).  Once you've
done this you can use 'make clean' to remove the vmlinux and other files
(like *.o) for space if you prefer.


> 
> Lilo didn't complain, and the 2.0.34 kernel boots and runs with no
> problems - and it seems faster (my imagination maybe). Thanks for all
> the help - it feels good!


If you use lilo (in /boot) you're probably better off using 'make
zlilo'.  This will automatically copy the final kernel to /boot and run
lilo to update everything.


> 
> Tom



-- 
Ed


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Re: Compiling the kernel?

[Bob Nielsen]

On Sun, 5 Jul 1998, Tom Pfeifer wrote:

> Well, not knowing any better, I fixed it by uninstalling my header and
> source packages (2.0.33), reinstalling the libc6-dev package, and then
> installing bin86 and the 2.0.34 source and header packages.

If you install the kernel-source package, you don't need the
kernel-headers package as it is all in the source.

It's probably NOT a good idea for anyone to upgrade to any of the
libc6-2.0.7r-3 packages at this time.  There is a problem, but not all are
susceptible to it.  2.0.7r-5 is in /incoming and hopefully will be put in
hamm asap.   I didn't seem to have any trouble with -3, but just
installed the -5 stuff (libc6, libc6-dev, locales, timezones) to play it
safe.

Bob


Bob Nielsen Internet: [EMAIL PROTECTED]
Tucson, AZ  AMPRnet:  [EMAIL PROTECTED]
DM42nh  http://www.primenet.com/~nielsen


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Re: Compiling the kernel?

[Tom Pfeifer]

Well, not knowing any better, I fixed it by uninstalling my header and
source packages (2.0.33), reinstalling the libc6-dev package, and then
installing bin86 and the 2.0.34 source and header packages.

This left the usr/include directories (asm, linux, scsi) NOT set up as
links. This is contrary to the source documentation, but agrees with the
Debian licb6-dev document that Bob mentioned. 

The configure and compile then went without a hitch, and "make zImage"
left the kernel image file (278k)in arch/i386/boot as expected. It also
left a file called vmlinux of about 680k in /usr/src/linux. I don't know
the purpose of that file. 

Lilo didn't complain, and the 2.0.34 kernel boots and runs with no
problems - and it seems faster (my imagination maybe). Thanks for all
the help - it feels good!

Tom

Tom Pfeifer wrote:
> 
> Hello,
> 
> I'm a fairly new Linux user, and am really starting to enjoy Linux and
> the Debian distribution. I'm running Hamm which I have downloaded and
> installed in bits and pieces with the help of dftp and dpkg. I also have
> the KDE beta4 desktop, the glib version of Communicator 4.05, and the
> Tkdesk file manager. I'm impressed - not bad at all!
> 
> Anyway, I'm trying to learn how to configure and compile the kernel. I
> have the 2.0.33 kernel source and header packages properly installed
> (dpkg is happy anyway), and the /usr/include links set up correctly as
> stated in the source documentation. I then do the following:
> 
> cd /usr/src/linux
> make mrproper
> make xconfig  (then configure, save, and exit)
> make dep
> make clean
> make zImage
> 
> The compile proceeds for a few minutes, and then exits with these lines:
> 
> as86 -0 -a -o bootsect.o bootsect.s
> make[1]: as86 Command not found
> make[1]: *** [bootsect.o] Error 127
> make[1]: Leaving directory 'usr/src/kernel-source-2.0.33/arch/i386/boot'
> make: *** [zImage] Error 2
> 
> It does leave a vmlinuz image file in /usr/src/linux which is about the
> same size as my current kernel, but when I install it in /boot and run
> lilo, it complains about "kernel image too large", or similar words. I
> restored the original so it's no problem as far as running, but does
> anyone have an idea what the problem might be, or where to read up on
> it?
> 
> Will appreciate any help. Thanks
> 
> Tom
> 
> --
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Re: Compiling the kernel?

[Bob Nielsen]

Well, the official Debian position is to link to the 2.0.32 headers,
however it should probably also work with 2.0.3{3|4}, as I doubt that
there are any significant changes (although I haven't checked).

See /usr/doc/libc6/FAQ.Debian.gz for the details (this is somewhat
controversial, particularly among non-debianites).

Here's what I have in /usr/src (as installed by default when I upgraded to
hamm):

drwxr-xr-x   3 root root 1024 Mar 23 21:11 kernel-headers-2.0.32
lrwxrwxrwx   1 root src21 Jun  5 11:06 linux -> 
kernel-headers-2.0.32
lrwxrwxrwx   1 root src21 Mar 23 21:52 linux-2.0.32 -> 
kernel-headers-2.0.32

Bob

On Sun, 5 Jul 1998, Tom Pfeifer wrote:

> Bob,
> 
> Thanks. Looks like I had more than one problem here.
> 
> I take it I should reinstall the 2.0.32 kernel headers package then
> also? I was confused about that and it didn't look right so I removed
> it. This whole setup isn't very clear, but I think you've got me headed
> in the right direction.
> 
> Tom
> 
> 
> --  
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
> 
> 


Bob Nielsen Internet: [EMAIL PROTECTED]
Tucson, AZ  AMPRnet:  [EMAIL PROTECTED]
DM42nh  http://www.primenet.com/~nielsen


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Re: Compiling the kernel?

[Tom Pfeifer]

Reinhold,

Yes I did the make modules and make modules_install, but I left that out
since I didn't get far enough for that to be an issue.

There was no image file in the arch/i386/boot directory (where I was
expecting it to be), only in /usr/src/linux, which was strange, but is
likely caused by my incorrect setup.

Thanks for the tip on bin86. I don't know how I missed that, as it
wasn't a dependancy for any package I installed. Between you and Bob,
I've got some things to look into. Thanks

Tom


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Re: Compiling the kernel?

[Tom Pfeifer]

Bob,

Thanks. Looks like I had more than one problem here.

I take it I should reinstall the 2.0.32 kernel headers package then
also? I was confused about that and it didn't look right so I removed
it. This whole setup isn't very clear, but I think you've got me headed
in the right direction.

Tom


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Re: Compiling the kernel?

[Bob Nielsen]

On Sun, 5 Jul 1998, Tom Pfeifer wrote:

> Hello,
> 
> I'm a fairly new Linux user, and am really starting to enjoy Linux and
> the Debian distribution. I'm running Hamm which I have downloaded and
> installed in bits and pieces with the help of dftp and dpkg. I also have
> the KDE beta4 desktop, the glib version of Communicator 4.05, and the
> Tkdesk file manager. I'm impressed - not bad at all!
> 
> Anyway, I'm trying to learn how to configure and compile the kernel. I
> have the 2.0.33 kernel source and header packages properly installed
> (dpkg is happy anyway), and the /usr/include links set up correctly as
> stated in the source documentation. I then do the following:

The source documentation is incorrect for a Debian libc6 installation.
You should have left it alone.  As root, do 

mv /usr/src/linux /usr/src/linux-2.0.33 (if /usr/src/linux is a link to
this, just remove it.)
ln -s /usr/source/kernel-headers-2.0.32 /usr/src/linux' 

> 
> cd /usr/src/linux
> make mrproper
> make xconfig  (then configure, save, and exit)
> make dep
> make clean
> make zImage
> 
> The compile proceeds for a few minutes, and then exits with these lines:
> 
> as86 -0 -a -o bootsect.o bootsect.s
> make[1]: as86 Command not found
> make[1]: *** [bootsect.o] Error 127
> make[1]: Leaving directory 'usr/src/kernel-source-2.0.33/arch/i386/boot'
> make: *** [zImage] Error 2

Install the bin86 package

> 
> It does leave a vmlinuz image file in /usr/src/linux which is about the
> same size as my current kernel, but when I install it in /boot and run
> lilo, it complains about "kernel image too large", or similar words. I
> restored the original so it's no problem as far as running, but does
> anyone have an idea what the problem might be, or where to read up on
> it?

Use 'make bzImage' instead of 'make zImage'.

To ease compilation and automate the lilo setup, install
kernel-package and read its documentation.

Bob


Bob Nielsen Internet: [EMAIL PROTECTED]
Tucson, AZ  AMPRnet:  [EMAIL PROTECTED]
DM42nh  http://www.primenet.com/~nielsen


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Re: Compiling the kernel?

[Reinhold Fischer]

On Sun, 05 Jul 1998, Tom Pfeifer wrote:
>Hello,
>
>I'm a fairly new Linux user, and am really starting to enjoy Linux and
>the Debian distribution. I'm running Hamm which I have downloaded and
>installed in bits and pieces with the help of dftp and dpkg. I also have
>the KDE beta4 desktop, the glib version of Communicator 4.05, and the
>Tkdesk file manager. I'm impressed - not bad at all!
>
>Anyway, I'm trying to learn how to configure and compile the kernel. I
>have the 2.0.33 kernel source and header packages properly installed
>(dpkg is happy anyway), and the /usr/include links set up correctly as
>stated in the source documentation. I then do the following:
>
>cd /usr/src/linux
>make mrproper
>make xconfig  (then configure, save, and exit)
>make dep
>make clean
>make zImage
>
>The compile proceeds for a few minutes, and then exits with these lines:
>
>as86 -0 -a -o bootsect.o bootsect.s
>make[1]: as86 Command not found
>make[1]: *** [bootsect.o] Error 127
>make[1]: Leaving directory 'usr/src/kernel-source-2.0.33/arch/i386/boot'
>make: *** [zImage] Error 2
>
>It does leave a vmlinuz image file in /usr/src/linux which is about the
>same size as my current kernel, but when I install it in /boot and run
>lilo, it complains about "kernel image too large", or similar words. I
>restored the original so it's no problem as far as running, but does
>anyone have an idea what the problem might be, or where to read up on
>it?
>
>Will appreciate any help. Thanks
>
>Tom


Hi Tom,

you should install the following package (pasted from dselect description):

+bin86 - 16-bit assembler and loader

+This is the as86 and ld86 distribution written by Bruce Evans. It's a
+complete 8086 assembler and loader which can make 32-bit code for the 386+
+processors (under Linux it's used only to create the 16-bit bootsector and
+setup binaries).  

usually if you compile the kernel with "make zImage" the compressed
(installable) kernel image is in /usr/src/linux/arch/i386/boot/zImage.

use this one for lilo, loadlin or however you start your system. 

don't forget to compile (make modules) and install (make modules_install) the
kernels modules also 



Cheers

Reinhold


--  
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Re: compiling the kernel - as86 missing

[Alex Yukhimets]

> The command "as86" is missing to compile the kernel. It's not on my 
> disk. Where can I find this command ?
> 
> Regards,
> Marc

Dear Marc,

you have to install "bin86" package to have as86 available.

Alex Y.

-- 
   _ 
 _( )_
( (o___   +---+
 |  _ 7   |Alexander Yukhimets|
  \(")|   http://pages.nyu.edu/~aqy6633/  |
  / \ \   +---+


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Compiling the Kernel

[Marcus Brinkmann]

Hi!

What Manoj wants to give you a pointer to is his grandious kernel-package.

It does an excellent job at kernel-compile (reduces the possible mistakes
enormously), please give it a try and install it along with the other
packages needed.

Marcus

On Thu, Oct 16, 1997 at 11:19:29AM -0500, Manoj Srivastava wrote:
> Hi,
>   From the kernel-package README file:
> --
[snipped]
> --
> 
>   manoj

-- 
"Rhubarb is no Egyptian god."
Marcus Brinkmann
[EMAIL PROTECTED]
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Compiling the Kernel

[Oliver Elphick]

Steve Koop wrote:
  >I'm compiling the kernel for the first time a having some problems,
  >
  >Avery thing up to the " make zImage ", it works to the end and then has some
  > error msg's:
  >
  >
  >the last few lines are:
  >
  >
  >as86 -0 -a -o bootsect.o bootsec.s
  >
  >Make[1]: as86: Command not found

bootsec.s is assembly code, but you don't have the assembler (as86) available.

as86 is in the package bin86.

-- 
Oliver Elphick[EMAIL PROTECTED]
Isle of Wight  http://lfix.co.uk/oliver

PGP key from public servers; key ID 32B8FAA1




--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Compiling the Kernel

[Manoj Srivastava]

Hi,
From the kernel-package README file:
--
INSTALLATION NOTES:

Before you go any further, please allow me to point out that you need to
have a few other packages installed before you can compile your own kernels
(it is difficult to compile anything without a compiler ;-). 

Firstly, you will need gcc, the libc development package (libc5-dev at
the time of writing), and, on Intel platforms, bin86. [If you use the
menuconfig target of make, you will need ncursesX.X-dev, and make xconfig
also requires tkX.X-dev, and other packages these depend on]

The packages suggested are:
devel:gcc, libc5-dev, binutils, make, and, for intel x86 platforms,
  bin86 (non-Intel platforms don't need this).
interpreters: gawk.
base: gzip, shellutils, and grep.

Of course, pretty gui front ends to kernel configuration require more
packages, but they are not strictly essential (though quite nice really). 

Oh, and of course, make-kpkg is part of kernel-package, usually found
in section misc.


 For the Brave and the impatient:
1% cd 
2% make config   # or make menuconfig or make xconfig and configure
3% make-kpkg clean
4% make-kpkg -r=custom.1.0 kernel_image
5% dpkg -i ../kernel-image-X.XXX_1.0_.deb
6% shutdown -r now # If and only if LILO worked or you have a means of
   # booting the new kernel. YOU HAVE BEEN WARNED!!
--

manoj
-- 
 "Just once I'd like to meet an alien menace that isn't immune to
 bullets." The Brigadier, Doctor Who
Manoj Srivastava   mailto:[EMAIL PROTECTED]>
Mobile, Alabama USAhttp://www.datasync.com/%7Esrivasta/>


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Compiling the Kernel

[Alex Yukhimets]

> I'm compiling the kernel for the first time a having some problems,
> 
> Avery thing up to the " make zImage ", it works to the end and then has 
> some error msg's:
> 
> the last few lines are:
> 
> as86 -0 -a -o bootsect.o bootsec.s
> Make[1]: as86: Command not found
> Make[1]: *** [bootsec.o] Error127
> Make[1]: Leaving directory /usr/src/linux/i386/boot 
> Make[1]: *** [zImage] Error 2
> 
> Then stops.
> 
> All rest of the before these step worked fine.
> 
> I know that it trying to find the file or script for bootsec.o, but it is 
> not in the /usr/src/linux/i386/boot dir, the bootsec.s is though.

You guess is wrong. It cannot find as86 program which will _produce_ .o
file. To have this program on your system you would have to install
"bin86" package from devel.

Alex Y.

-- 
   _ 
 _( )_
( (o___   +---+
 |  _ 7   |Alexander Yukhimets|
  \(")|   http://pages.nyu.edu/~aqy6633/  |
  / \ \   +---+


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Compiling the Kernel

[Manoj Srivastava]

Hi,

Here follows the readme file for kernel-package, which should
 help creating your own kernel image deb package.

manoj


$Id: README,v 1.3 1997/06/25 07:33:26 srivasta Exp $

This is the Debian Linux packaging scripts for the Linux kernel. 
This package has been put together by Manoj Srivastava <[EMAIL PROTECTED]>.


INSTALLATION NOTES:

To use this package to create kernel-image packages, you need to get
the kernel source (available from your favorite Linux archive),
unpack your kernel somewhere. Preferably somewhere other than
/usr/src/linux (more on this later).

Before you go any further, please allow me to point out that you need to
have a few other packages installed before you can compile your own kernels
(it is difficult to compile anything without a compiler ;-). 

Firstly, you will need gcc, the libc development package (libc5-dev at
the time of writing), and, on Intel platforms, bin86. [If you use the
menuconfig target of make, you will need ncursesX.X-dev, and make xconfig
also requires tkX.X-dev, and other packages these depend on]

The packages suggested are:
devel:gcc, libc5-dev, binutils, make, and, for intel x86 platforms,
  bin86 (non-intel platforms don't need this).
interpreters: gawk.
base: gzip, shellutils, and grep.

Of course, pretty gui front ends to kernel configuration require more
packages, but they are not strictly essential (though quite nice really). 


 For the Brave and the impatient:
1% cd 
2% make config   # or make menuconfig or make xconfig and configure
3% make-kpkg clean
4% make-kpkg -r=custom.1.0 kernel_image
5% dpkg -i ../kernel-image-X.XXX_1.0_.deb
6% shutdown -r now # If and only if LILO worked or you have a means of
   # booting the new kernel. YOU HAVE BEEN WARNED!!

 
Unpacking kernel sources:
-

On a debian system, /usr/src/linux always either contains 
include/{linux,asm} or points to a directory which contains
those subdirectories, usually a directory with the full kernel
source or a directory with just the kernel headers.

Debian has standardized on /usr/src/linux being a link (that is the
case if you install released debian kernel packages, and has been
for a while now).

If you like living on the edge and compiling your own kernel 
packages ;-), you have to follow the convention of letting
/usr/src/linux be a link, and unpack the pristine kernel sources
someplace else.

Some of the suggestions about where to unpack the kernel packages are
a) /tmp/linux
b) /var/tmp/linux
c) /usr/src/linux-X.X.XX; where X.X.XX is the version number of the
   kernel. Remember to re-link /usr/src/linux to point to this
   directory, like: (cd /usr/src; rm linux; ln -s linux-X.X.XX) 

In any case, choose a partition that has a large amount of free space,
since recent kernels, unpacked, run to about 23MB, and you need more
than double that in order to create kernel-image, kernel-source, and
the tar file (that is, if you choose to build everything together with
the dist target in debian.rules -- say if you want, for whatever
reason, to run dchanges on the files created). I needed nearly 60MB to
create the full spectrum of packages for version 1.99.7 (and doubtless
this size will go up in the future).

Now, cd linux (wherever you have created the kernel sources).

The version number is deduced from the kernel Makefile directly. to
ensure that the version numbers are in sync(1), so you don't have to
worry about that.

It has been suggested that you renumber the revision number in such a
way that a generic kernel image package will not override the custom
package while using dselect (or dpkg -BOGiE). You may also do this on the
fly by setting the DEBIAN_REVISION environmental variable.

The revision number (the argument supplied after the --revision flag)
has certain constraints: it may contain only alphanumerics and the
characters + . (full stop, and plus) and should contain a digit.
NOTE: No hyphens allowed. (Look at Chapter 5 of the Programmers manual
for details)

This is because dpkg imposes an ordering on version numbers, so that
it can tell whether packages are being up or downgraded and so that
dselect can tell whether a package it finds available is newer than
the one installed on the system.

I've found that using a two-level scheme where the major level starts
with a letter nicely does the job, (--revision custom.Y, so the image
package become kernel-image-X.X.XX-custom.Y.deb), and dselect and dpkg
-BOGiE will refuse to downgrade to a generic kernel (don't give the
BGO arguments to dpkg if you actually do want to downgrade later).


You may also place long term directives (like your name and email
address) in the file /etc/kernel-pkg.conf. Putting your name and
address in that file is a good idea, to remind you that this is not an
official package, unless, of course, you happen to be the maintainer
(Hi Herbert). The file /etc/kernel-pkg.conf is actually a Makefile
snippet include

Re: Compiling the Kernel

[Manoj Srivastava]

Hi,
>>"Bob" == Bob Nielsen <[EMAIL PROTECTED]> writes:

Bob> Install libc5-dev, which includes these files.

Bob> Also, you want to (per the README which comes with the kernel
Bob> source):

Bob> make sure your /usr/include/asm, /usr/include/linux, and
Bob> /usr/include/scsi directories are just symlinks to the kernel
Bob> sources:

Bob> cd /usr/include rm -rf asm linux scsi ln -s
Bob> /usr/src/linux/include/asm-i386 asm ln -s
Bob> /usr/src/linux/include/linux linux ln -s
Bob> /usr/src/linux/include/scsi scsi


Auggh. Don't do that. Debian distributes the required
 headers in the libc packages (read the FAQ beloq for a reason). Also,
 the kernel compile does not need them. 

Have you considered make-kpkg from kernel-package? it creates
 a .deb of your custom configured kernel image that can be further
 managed by dpkg and friends. Ill post a separate message about that. 

manoj

-- 
 He hasn't one redeeming vice. Oscar Wilde
Manoj Srivastava   mailto:[EMAIL PROTECTED]>
Mobile, Alabama USAhttp://www.datasync.com/%7Esrivasta/>


$Id: README.headers,v 1.3 1997/06/25 07:33:27 srivasta Exp $
 

This document contains comments from Linus Torvalds (made in
 an ``off-the-cuff'' personal email) to help clarify the rationale
 behind the Debian way of handling symlinks, but this should not be
 seen as an official policy statement by Linus. I'm attaching a
 disclaimer in his own words.

The only reason that Linus's message is quoted in here is that
 he can explain the technical reasons with far more lucidity than I
 can, and now that I have permission to include his mail, I am
 removing most of my far less facile efforts in that regard. 


>> "David" == David Engel <[EMAIL PROTECTED]> said on Mon, 24 Feb 1997
>> "Linus" == Linus Torvalds said on Mon, 24 Feb 1997

David> Hi Linus,
David> No matter how well we try to explain ourselves, the symlinks issue
David> keeps coming up.  Would you mind if we used your message below in
David> our responses?

Linus> Sure. Don't make it "the word of God" - please point out that
Linus> it was a off-the-bat personal reply to a question concerning
Linus> this, and while I'm more than happy to have the email
Linus> circulated it shouldn't be seen as a "official" document in any
Linus> way..
Linus> Linus
---

The headers were included in libc5-dev after a rash of very
 buggy alpha kernel releases (1.3.7* or something like that) that
 proceeded to break compilations, etc.  Kernel versions are changed
 far more rapidly than libc is, and there are higher chances that
 people install a custom kernel than they install custom libc.

libc6 includes it's own version of /usr/include/linux and
 friends form the beginning (that is, this is no longer a Debian only
 feature, the upstream version has moved to this scheme as well).

>> "Linus" == Linus Torvalds said on Wed, 22 Jan 1997:

Linus> The kernel headers used to make sense exporting to user space,
Linus> but the user space thing has grown so much that it's really not
Linus> practical any more. The problem with Debian is just that they
Linus> are different, not that they are doing anything wrong. That
Linus> leads to differences between the distributions, and that in
Linus> turn obviously can result in subtle problems.

Linus> As of glibc, the kernel headers will really be _kernel_
Linus> headers, and user level includes are user level
Linus> includes. Matthias Ulrich did that partly because I've asked
Linus> him to, but mainly just because it is no longer possible to try
Linus> to synchronize the libc and the kernel the way it used to
Linus> be. The symlinks have been a bad idea for at least a year now,
Linus> and the problem is just how to get rid of them
Linus> gracefully. Personally, I'm counting on glibc, which we are
Linus> already using on alpha.

Linus> Just to give you some idea of exactly why the includes really
Linus> can't be handled by simple symlinks: the main problem is
Linus> version skew. Lots of people want to upgrade their library
Linus> without affecting the kernel, and probably even more people
Linus> want to be able to upgrade their kernel without affecting their
Linus> compilation environment. Right now doing that has been
Linus> extremely fragile.

Linus> Just to give _one_ example of why the symlinks are bad: NR_OPEN
Linus> and "fd_set". I have had no end of problems making NR_OPEN
Linus> larger in the kernel, exactly _because_ of the damn
Linus> sym-links. If I just make NR_OPEN larger (the right thing to
Linus> do), the problem is that people with old libraries will now
Linus> compile against a header file that doesn't match the library
Linus> any more. And when the library internally uses another NR_OPEN
Linus> than the new program does, "interesting" things happen.

Linus> In contras

Re: Compiling the Kernel

[Bob Nielsen]

On Tue, 22 Jul 1997, Bruno O. M. Simoes wrote:

> Hello,
>   I had problems while compiled the kernel.
>   First I didn't have anything in my "/usr/src" directory, so I got the
> "linux-2.0.29.tar.gz" file, that's my installed version, apply "tar -xzvf"
> and got a directory tree "/usr/src/linux/*".
>   So, I did "make config", everything's fine.
>   Finally, when I made "make dep", an error occourred, it didn't find
> several files (includes) like stdio.h,stdlib.h. Well, I don't have those
> files on my system, and guess there's some pratical way to install it on.
>   Please, help me.

Install libc5-dev, which includes these files.

Also, you want to (per the README which comes with the kernel source):

 make sure your /usr/include/asm, /usr/include/linux, and 
/usr/include/scsi
   directories are just symlinks to the kernel sources:

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

(although for most this may not be absolutely necessary.)

Bob


Bob Nielsen Internet: [EMAIL PROTECTED]
Tucson, AZ  AMPRnet:  [EMAIL PROTECTED]
AX.25:[EMAIL PROTECTED]
http://www.primenet.com/~nielsen


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: compiling the kernel

[Philippe Troin]

On Fri, 11 Jul 1997 01:03:24 EDT Paul Miller ([EMAIL PROTECTED]) 
wrote:

> I know how to compile the kernel the regular way, but doesn't Debian
> have a special script for this?  I install it and I don't know the name
> of it... what is it?

There is a kernel-package package to compile the kernel into a package.

Phil.



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: RE-COMPILING the Kernel...

[Franck LE GALL - STAGIAIRE A FT.BD/CNET/DTD/PIH]

You should have a look at 'Kernel HOWTO'. There is there all the 
answers to your questions.
This is some of the information you could find in :


-> Just so I know and have my ducks in order.
-> 
-> Is this the correct method for re-compiling my Kernel??
-> 
-> cd /usr/src/Linux
-> make config  >>> Choose the configuration you want
-> make dep >>>  I don't know

Just add a 'make clean' here in order to delete all the old objects.


-> make zImage  >>> Compile the kernel in /usr/src/linux/arch/bin/i-386
(I am not sur of the path)
-> make zdisk   >>> Compile the kernel on your floppy disk
-> make zlilo   >>> Compile and copy the kernewl on / on then run LILO
-> 
-> Is this correct?  Can someone explain briefly each step and why I have
-> to do this???  I just want to understand it more.
-> 
-> 
-> Tony
-> This email originated from ourtownusa.com.



_
_/_/_/_/  _/_/  _/_/_/_/ _/_/_/_/_/
   _/_/_/  _/  _/   _/
  _/_/ _/ _/  _/_/_/   _/
 _/_/  _/_/  _/   _/
_/_/_/_/  _/_/  _/_/_/_/ _/

Le Gall  Franck
CNET - FRANCE TELECOM Phone: +33 96 05 35 34
2, Route de Tregastel BP 41   Fax:   +33 96 05 34 31
F-22301 LANNION - FRANCE  E-mail: [EMAIL PROTECTED]


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: RE-COMPILING the Kernel...

[Oliver Elphick]

In message <[EMAIL PROTECTED]>
, writes:
  >Just so I know and have my ducks in order.
  >
  >Is this the correct method for re-compiling my Kernel??
  >
  >cd /usr/src/Linux

or /usr/src/linux or whatever

This is where the kernel source is stored, of course.

  >make config

If you're running X-windows with tk/tcl libraries installed, make xconfig
is much nicer, or make menuconfig, if you aren't running X.

This step lets you set up the config.h file which governs what parameters
are built into your kernel.  For example, the Debian kernel comes with
support for a large number of different network cards; but you will
probably need only one.  You therefore configure your kernel with that
driver alone, excluding the rest.  You also choose which bits of Linux
can be loadable modules and which must be permanently loaded in the kernel.

  >make dep

This creates dependency lines in the Makefile according to the choices
which are now defined in config.h

make clean

might be a good idea at this point.

  >make zImage

creates a bootable kernel in arch//boot, called zImage

If (at the configuration stage) you choose a lot of options to be included
in the kernel, it may become too big to be a zImage.  (The reasons for this
are explained in the lilo documentation - it's to do with the small amount
of memory available to the BIOS on a pc.)  In that case, you should make
bzImage instead.

These makefile targets are specific to Intel architecture; I don't have
experience of Linux on other architectures, but inspection of the
makefiles shows some quite different methods.


Unless you have chosen not to use kernel modules at all; which, in general,
would be ill-advised, you should now

make modules

which compiles the kernel code which is to be held in loadable modules
rather than being built into the kernel; and

make modules_install

which is rather obvious, really.
Modules are installed in /lib/modules/

  >make zdisk

copies zImage (or bzImage) onto the floppy disk /dev/fd0

  >make zlilo

renames /vmlinuz to /vmlinuz.old;
copies zImage (or bzImage) to /vmlinuz;
runs lilo to set up /vmlinuz as the new kernel to be booted - this is
particularly important, since, without it, the machine will no longer
be bootable.



-- 
Oliver Elphick[EMAIL PROTECTED]
Isle of Wight  http://lfix.co.uk/oliver

 Make it idiot-proof, and someone will breed a better idiot.




pgpAOzdTSYGOS.pgp
Description: PGP signature

Re: RE-COMPILING the Kernel...

[Emilio Lopes]

> "b" == bigt  <[EMAIL PROTECTED]> writes:

b> cd /usr/src/Linux

With this you go to the directory where the kernel sources are. :-)

b> make config

Here you will be asked a lot of things. Responding these questions you
are saying what you want and what you don't want in your kernel,
acording to your hardware.

b> make dep

This will take care of the dependencies between the various "parts"
you chose in the above step. It determines what has to be compiled to
satisfy the choices you did with "make config".

b> make zImage

Will compile the kernel.

b> make zdisk

Will put the kernel in a floppy.

b> make zlilo

Will install the kernel somewhere and call lilo.

b> Is this correct?  Can someone explain briefly each step and why I
b> have to do this???  I just want to understand it more.

Why don't you use the package "kernel-package"? You just have to
configure the kernel with "make config" or "make xconfig" (provided
you have tcl/tk) and it will compile and make a "deb" package with the
kernel.  The instructions are easy to follow:

1% cd 
2% make config   # or make menuconfig or make xconfig and configure
3% make-kpkg clean
4% make-kpkg -r=custom.1.0 kernel_image
5% dpkg -i ../kernel-image-X.XXX_1.0_.deb
6% shutdown -r now # If and only if LILO worked or you have a means of
   # booting the new kernel. YOU HAVE BEEN WARNED!!

Pretty nice.

Have fun!

-- 
 Emilio C. Lopes 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

RE-COMPILING the Kernel...

[bigt]

Just so I know and have my ducks in order.

Is this the correct method for re-compiling my Kernel??

cd /usr/src/Linux
make config
make dep
make zImage
make zdisk
make zlilo

Is this correct?  Can someone explain briefly each step and why I have
to do this???  I just want to understand it more.


Tony
This email originated from ourtownusa.com.



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? 
e-mail to [EMAIL PROTECTED] .

Re: Compiling the kernel - hiccups, and output

[Manoj Srivastava]

Hi,

Make bzImage would place a image file under
 ./arch/$(architecture)/boot/$(kimage).  You need to care about
 bzImage, ./System.map, and ./vmlinux, which is needed for generating
 the psdatabase, needed for the commands ps and friends. You also need
 to care asbout the modules produced ...

Umm this is getting messy.  May I suggest you install the
 package kernel-package, cd to the kernel source top, and say
 % make mrproper; make menuconfig
   configure the kernel as you wish, and say
 % make=-pkg kernel_image
   Wait. A kernel image file will be produced shortly, which may then
 be shipped home as desired. It really is far easier this way. (You
 could try make-kpkg -n kernel_image to see what it would do).

manoj
-- 
 The programmer, like the poet, works only slightly removed from pure
 thought- stuff.  He builds his castles in the air, from air, creating
 by exertion of the imagination.  Few media of creation are so
 flexible, so easy to polish and rework, so readily capable of
 realizing grand conceptual structures. Frederick Brooks, Jr., The
 Mythical Man Month
Manoj Srivastava   mailto:[EMAIL PROTECTED]>
Mobile, Alabama USAhttp://www.datasync.com/%7Esrivasta/>


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]

Re: Compiling the kernel..

[Manoj Srivastava]

Hi,
>>"Craig" == Craig Sanders <[EMAIL PROTECTED]> writes:

(Thanks, Craig, for answering this) I am merely clarifying a few minor
points in an excellent tutorial, To paraphrase what Craig said:

:  simplest way is to download "kernel_source-x.x.x.deb", use dpkg to
:  install it, and then:
: 1.  cd /usr/src/linux
: 2.  configure the kernel with:
: make config
: -or-
: make menuconfig
: -or-
: make xconfig

 At this point you are done: debian.rules takes care of the rest. Just
 say:
 
3. ./debian.rules kernel_image

 Also, once a .config file exists, it is never overwritten by
 debian.rules -- It is even propogated by ./debian.rules kernel_source
 All this information is also in the file /usr/src/linux/debian.README
 in the newer kernels.

manoj
ps. Please remember Craigs warnings about installing a kernel with the
same version as a previously installed kernel. If you absolutely have
to, remember to manually clean
/lib/modules/version-number-of-image-being-installed/* manually before
installing the new kernel-image, and reboot soon afterwards,
re-running lilo as necessary, of course (or otherwise ensuring that
you can boot with the new image).
-- 
God must love the common man; He made so many of them.
Manoj Srivastava   Systems Research Programmer, Project Pilgrim,
Phone: (413) 545-3918A143B Lederle Graduate Research Center,
Fax:   (413) 545-1249 University of Massachusetts, Amherst, MA 01003
<[EMAIL PROTECTED]> http://www.pilgrim.umass.edu/%7Esrivasta/>

Re: Compiling the kernel..

[Richard . Dansereau]

Craig Sanders writes:
> 
> 
> On Thu, 23 May 1996 [EMAIL PROTECTED] wrote:
> 
> > I tried the procedure you (and a couple of others) suggested.  I currently
> > have debian 0.93R6 installed and am trying to compile the kernel from
> > devel/source-1.3.64-0.deb
> 
> You've got the wrong kernel version.  These instructions only apply to
> recent kernel versions, 1.3.97 or later.
> 
> > I also tried doing "make zImage" I get 
> > gcc -D__KERNEL__ -I/usr/src/linux-1.3.64/include -Wall -Wstrict-prototypes 
> > -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -m486 -malign-loops=2 
> > -malign-jumps=2 -malign-functions=2 -DCPU=586  
> > -DNFS_ROOT="\"/tftpboot/%s\"" -c -o init/main.o init/main> 
> .c
> > cc1: Invalid option `align-loops=2'
> > cc1: Invalid option `align-jumps=2'
> > cc1: Invalid option `align-functions=2'
> > make: *** [init/main.o] Error 1
> > 
> > I do have gcc version 2.6.3 so I don't think that should be a problem.
> > Any ideas?
> 
> No idea.  As a wild guess i'd suspect that maybe you're trying to compile
> an ELF kernel with an a.out only gcc.

This is a possibility.  I will look into that further.

> 
> If this is the case, then you can 'make config' again to de-select the
> "compile kernel as ELF?" option and recompile...or you can upgrade to
> ELF.
> 
> Dale Scheetz ([EMAIL PROTECTED]) has written some good notes on how to
> upgrade from 0.93r6 to 1.1 - he posts them semi-regularly to the debian
> mailing lists - if you follow them to the point of updating to ELF ld.so
> and libc5, then you can upgrade to the latest gcc and libc5-dev, then
> you can compile an ELF kernel.
> 
> Note, you may need to first compile an a.out kernel with ELF binary support
> built in (NOT as a module - ld.so won't let you upgrade to the latest
> version if ELF support is not in the kernel), reboot on that, and then do
> the upgrade as written by Dale.
> 
> 
> 
> I'd suggest upgrading to the beta 1.1, keeping track of (and reporting)
> any bugs which affect you and upgrading only the packages affected as
> fixes come out.  When 1.1 goes from beta to release status, do a full
> upgrade again.
> 
> Debian 1.1 might still be called 'unstable', but that refers more to the
> fact that packages are being upgraded every day with new versions.  As far
> as functionality goes, it's at least as stable and reliable as 0.93r6.
> 
> The hard part is doing the initial upgrade from 0.93r6 to 1.1 - you've
> got to take that slowly and carefully.  As I mentioned, Dale has written
> some very good instructions on how to do this.  If you think about what
> you're doing and pause for a second before hitting the enter key you
> wont run into any trouble.  After that, subsequent upgrades will be no
> hassle at all - it's just the switch from a.out to ELF which makes the
> upgrade a little dangerous if performed without thought.

Is doing a slow upgrade from 0.93R6 to 1.1 a better idea than trying
a clean installation of 1.1?  I actually tried doing a complete wipe
of my hard disk and installing 1.1 from scratch.  Unfortunately, the
packages at that time for lib5-dev, cpp, and gcc kept conflicting
with each other and dselect would not allow me to install them
(even though dselect suggested that I should be able to install thing
properly).  So, I wiped my hard drive and installed 0.93R6 which
went without any problems.  Have installation problems been reported
for lib5-dev that have recently been fixed?


Richard..

-
Richard Dansereau
Email: [EMAIL PROTECTED]  Home page:  http://pobox.com/~rdanse
Electrical and Computer Engineering - University of Manitoba - Canada
-

Re: Compiling the kernel..

[Richard . Dansereau]

Craig Sanders writes:
> 
> 
> On Wed, 22 May 1996 [EMAIL PROTECTED] wrote:
> 
> > This appears to contain the standard kernel release source tree but
> > has a number of additional things (such as a nifty Tcl/Tk GUI for
> > kernel configurations).
> 
> "make xconfig" and "make menuconfig" are a standard part of the linux
> kernel now...has been for most of the 1.3.x series kernels.
> 
> > What is the procedure I should take to compile a kernel under debian
> > and to take into account loadable modules, etc.?
> > 
> > Also, if I want to get newer kernel releases is there a way to
> > integrate it in with the additional Debian changes for /usr/src/linux?
> 
> simplest way is to download "kernel_source-x.x.x.deb", use dpkg to
> install it, and then:
> 
> 1.  cd /usr/src/linux
> 
> 2.  configure the kernel with:
> 
>make config
> -or-
>make menuconfig
> -or-
>make xconfig
> 
> 3.  make dep ; make clean # this step may not be necessary. i'm not
>   # sure if debian.rules already does it or not.
>   # it can't hurt to do it, though...only takes a
>   # few minutes.
> 
> 4.  touch stamp-configure # if you don't do this, then debian.rules
>   # will overwrite your config with the standard
>   # debian kernel_image package config.
> 
> 5.  build the kernel image package:
> 
> ./debian.rules kernel_image
> 
> 
> This procedure will create a kernel_image-x.x.x.i386.deb package in
> /usr/src, which can be installed with dpkg just like any other package.  
> reboot to run the new kernel.
> 
> 
> 
> NOTE: if you are recompiling a kernel which is already installed, you
> will probably want to rm -rf /lib/modules/x.x.x BEFORE you install the
> new kernel.  Otherwise that modules directory will be full of old junk
> from the last compile.
> 
> If you are currently running that version of the kernel, and using those
> modules (i.e. with kerneld or modprobe) then you really should reboot as
> soon as you've installed the new version
> 
> procedure is:
> 
> 1. build kernel version x.x.x
> 2. rm -rf /lib/modules/x.x.x
> 3. dpkg -i kernel_image.x.x.x.deb
> 4. reboot
> 
> Craig
> 


I tried the procedure you (and a couple of others) suggested.  I currently
have debian 0.93R6 installed and am trying to compile the kernel from
devel/source-1.3.64-0.deb

Unfortunately, when I run "./debian.rules kernel_image" I get
make: *** No rule to make target `kernel_image'.  Stop.
Am I doing something wrong?

I also tried doing "make zImage" I get 
gcc -D__KERNEL__ -I/usr/src/linux-1.3.64/include -Wall -Wstrict-prototypes -O2 
-fomit-frame-pointer -fno-strength-reduce -pipe -m486 -malign-loops=2 
-malign-jumps=2 -malign-functions=2 -DCPU=586  -DNFS_ROOT="\"/tftpboot/%s\"" -c 
-o init/main.o init/main.c
cc1: Invalid option `align-loops=2'
cc1: Invalid option `align-jumps=2'
cc1: Invalid option `align-functions=2'
make: *** [init/main.o] Error 1

I do have gcc version 2.6.3 so I don't think that should be a problem.
Any ideas?

Richard..

-
Richard Dansereau
Email: [EMAIL PROTECTED]  Home page:  http://pobox.com/~rdanse
Electrical and Computer Engineering - University of Manitoba - Canada
-

Re: Compiling the kernel..

[Craig Sanders]

On Thu, 23 May 1996 [EMAIL PROTECTED] wrote:

> > The hard part is doing the initial upgrade from 0.93r6 to 1.1 -
>
> Is doing a slow upgrade from 0.93R6 to 1.1 a better idea than trying a
> clean installation of 1.1?

that depends on whether or not you've got data and config files you want
to keep.

Also, being able to upgrade without reformatting is one of the main
benefits of debian - the upgrade from a.out to 1.1 is documented and
tested well enough now that it's reasonably safe. (i say 'reasonably
safe' as a disclaimer against truly astounding acts of creative
incompetence :-)

I've done both clean installations of beta 1.1 and upgrades from 0.93r6
several times on several different machines over the last few months.
Both work fine.  I'd say upgrading is easier because you don't have to
make floppies.

> I actually tried doing a complete wipe of my hard disk and installing
> 1.1 from scratch.  Unfortunately, the packages at that time for
> lib5-dev, cpp, and gcc kept conflicting with each other and dselect
> would not allow me to install them (even though dselect suggested that
> I should be able to install thing properly).  So, I wiped my hard
> drive and installed 0.93R6 which went without any problems.  Have
> installation problems been reported for lib5-dev that have recently
> been fixed?

Version numbers for libc5 and libc5-dev are very important.  They've got to
match exactly.  

e.g. you can't install libc5-5.2.18-3 and libc5-dev-5.2.18-5, they must both
be -5 versions.  I ran into this one myself when I upgraded, and couldn't
figure out what was going on until i noticed that the version numbers were
slightly different.

Make sure your copies of the .deb packages are up to date before
starting the upgrade procedure.  Easiest way to do this is to install
the mirror package and mirror your local debian mirror site (configure
mirror to exclude the source directories if you dont want them and also
the non-i386 binary directories...i.e. get only non-free/, contrib/, and
unstable/binary-i386)

if you don't want to run mirror, just ftp what you need manually.  This
is a lot more work than setting up mirror to do what you want.

Craig

Re: Compiling the kernel..

[Craig Sanders]

On Thu, 23 May 1996 [EMAIL PROTECTED] wrote:

> I tried the procedure you (and a couple of others) suggested.  I currently
> have debian 0.93R6 installed and am trying to compile the kernel from
> devel/source-1.3.64-0.deb

You've got the wrong kernel version.  These instructions only apply to
recent kernel versions, 1.3.97 or later.

> I also tried doing "make zImage" I get 
> gcc -D__KERNEL__ -I/usr/src/linux-1.3.64/include -Wall -Wstrict-prototypes 
> -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -m486 -malign-loops=2 
> -malign-jumps=2 -malign-functions=2 -DCPU=586  -DNFS_ROOT="\"/tftpboot/%s\"" 
> -c -o init/main.o init/main
.c
> cc1: Invalid option `align-loops=2'
> cc1: Invalid option `align-jumps=2'
> cc1: Invalid option `align-functions=2'
> make: *** [init/main.o] Error 1
> 
> I do have gcc version 2.6.3 so I don't think that should be a problem.
> Any ideas?

No idea.  As a wild guess i'd suspect that maybe you're trying to compile
an ELF kernel with an a.out only gcc.

If this is the case, then you can 'make config' again to de-select the
"compile kernel as ELF?" option and recompile...or you can upgrade to
ELF.

Dale Scheetz ([EMAIL PROTECTED]) has written some good notes on how to
upgrade from 0.93r6 to 1.1 - he posts them semi-regularly to the debian
mailing lists - if you follow them to the point of updating to ELF ld.so
and libc5, then you can upgrade to the latest gcc and libc5-dev, then
you can compile an ELF kernel.

Note, you may need to first compile an a.out kernel with ELF binary support
built in (NOT as a module - ld.so won't let you upgrade to the latest
version if ELF support is not in the kernel), reboot on that, and then do
the upgrade as written by Dale.



I'd suggest upgrading to the beta 1.1, keeping track of (and reporting)
any bugs which affect you and upgrading only the packages affected as
fixes come out.  When 1.1 goes from beta to release status, do a full
upgrade again.

Debian 1.1 might still be called 'unstable', but that refers more to the
fact that packages are being upgraded every day with new versions.  As far
as functionality goes, it's at least as stable and reliable as 0.93r6.

The hard part is doing the initial upgrade from 0.93r6 to 1.1 - you've
got to take that slowly and carefully.  As I mentioned, Dale has written
some very good instructions on how to do this.  If you think about what
you're doing and pause for a second before hitting the enter key you
wont run into any trouble.  After that, subsequent upgrades will be no
hassle at all - it's just the switch from a.out to ELF which makes the
upgrade a little dangerous if performed without thought.

Craig

Re: Compiling the kernel..

[Craig Sanders]

On Wed, 22 May 1996 [EMAIL PROTECTED] wrote:

> This appears to contain the standard kernel release source tree but
> has a number of additional things (such as a nifty Tcl/Tk GUI for
> kernel configurations).

"make xconfig" and "make menuconfig" are a standard part of the linux
kernel now...has been for most of the 1.3.x series kernels.

> What is the procedure I should take to compile a kernel under debian
> and to take into account loadable modules, etc.?
> 
> Also, if I want to get newer kernel releases is there a way to
> integrate it in with the additional Debian changes for /usr/src/linux?

simplest way is to download "kernel_source-x.x.x.deb", use dpkg to
install it, and then:

1.  cd /usr/src/linux

2.  configure the kernel with:

   make config
-or-
   make menuconfig
-or-
   make xconfig

3.  make dep ; make clean # this step may not be necessary. i'm not
  # sure if debian.rules already does it or not.
  # it can't hurt to do it, though...only takes a
  # few minutes.

4.  touch stamp-configure # if you don't do this, then debian.rules
  # will overwrite your config with the standard
  # debian kernel_image package config.

5.  build the kernel image package:

./debian.rules kernel_image


This procedure will create a kernel_image-x.x.x.i386.deb package in
/usr/src, which can be installed with dpkg just like any other package.  
reboot to run the new kernel.



NOTE: if you are recompiling a kernel which is already installed, you
will probably want to rm -rf /lib/modules/x.x.x BEFORE you install the
new kernel.  Otherwise that modules directory will be full of old junk
from the last compile.

If you are currently running that version of the kernel, and using those
modules (i.e. with kerneld or modprobe) then you really should reboot as
soon as you've installed the new version

procedure is:

1. build kernel version x.x.x
2. rm -rf /lib/modules/x.x.x
3. dpkg -i kernel_image.x.x.x.deb
4. reboot

Craig