Thank you for help so far!

I found Instructions by Patrick Volkerding (author of Slackware) at
http://mirror.tech.oru.se/pub/slackw...0.1/bootdisks/

Patrick Volkerding instruction after "To compile a custom kernel,
follow these steps" says work in /usr/src/linux while compiling.
But is conflict: /usr/src/linux/README says "Do NOT use the
/usr/src/linux area!" Which instruction is correct?

Also, is Patrick Volkerding 10.1 instructions acceptable for 10.2?
I could not on web find Patrick Volkerding 10.2 instructions.

When exiting make menuconfig, screen says "Next, you may run
'make bzImage', 'make bzdisk', or 'make install'. Patrick
Volkerding instructions say make dep ; make clean ; make bzImage.
For learning: what do "make dep ; make clean" steps do?

Also, what is differences between:
make install
make bzImage
make zImage
make image
make bzdisk
make zdisk
make zlilo

Is available tutorial / man / howto explaining menuconfig options?

In comp.os.linux.misc Vardan Kushnir <sophim@pol.ru>:

[..]

> When exiting make menuconfig, screen says "Next, you may run
> 'make bzImage', 'make bzdisk', or 'make install'. Patrick
> Volkerding instructions say make dep ; make clean ; make bzImage.
> For learning: what do "make dep ; make clean" steps do?

Read the Makefile, those steps are obsolete with kernel 2.6:

depend dep:
@echo '*** Warning: make $@ is unnecessary now.'

As the Makefile says.

> Also, what is differences between:
> make install
> make bzImage
[..]

For starters, just read the Makefile and see what it does, it's
plain text.

> Is available tutorial / man / howto explaining menuconfig options?

There's built-in help for most options if you run 'make
menuconfig'.

With 2.6, after configuring, tend to simply type 'make rpm' on
rpm based distro. ;-)

Good luck

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 366: ATM cell has no roaming feature turned on,
notebooks can't connect

Michael Heiming <michael+USENET@www.heiming.de> says...

>Read the Makefile, those steps are obsolete with kernel 2.6:

I did not say I was compiling kernel 2.6.

I am compiling kernel 2.4.31, which is current on Slackware 10.2.

On Sat, 22 Oct 2005 10:46:37 +0000, Vardan Kushnir <sophim@pol.ru> wrote:
>
>I found Instructions by Patrick Volkerding (author of Slackware) at
>http://mirror.tech.oru.se/pub/slackw...0.1/bootdisks/
>
>Patrick Volkerding instruction after "To compile a custom kernel,
>follow these steps" says work in /usr/src/linux while compiling.
>But is conflict: /usr/src/linux/README says "Do NOT use the
>/usr/src/linux area!" Which instruction is correct?

Read what Linus says:
http://uwsg.iu.edu/hypermail/linux/k...07.3/0587.html

http://slackworld.berlios.de/03/kuac.html
Though majorly clunky presentation at the moment, may be of use

http://www.digitalhermit.com/linux/kernel.html
Seems to be one of the better pages out there, I've not done a survey
for some months.

>Also, is Patrick Volkerding 10.1 instructions acceptable for 10.2?
>I could not on web find Patrick Volkerding 10.2 instructions.
>
>When exiting make menuconfig, screen says "Next, you may run
>'make bzImage', 'make bzdisk', or 'make install'. Patrick
>Volkerding instructions say make dep ; make clean ; make bzImage.
>For learning: what do "make dep ; make clean" steps do?

For now, just accept they build a kernel, some steps may be skipped,
depending on ... various things.

Grant.

On Sat, 22 Oct 2005 13:27:12 +0200, Michael Heiming <michael+USENET@www.heiming.de> wrote:

Hey Michael,

>With 2.6, after configuring, tend to simply type 'make rpm' on
>rpm based distro. ;-)

Cross-posting that into aols is bound to wind up some pipe-smokin'
penguins. )

Grant.

In comp.os.linux.misc Vardan Kushnir <sophim@pol.ru> wrote:
> Patrick Volkerding instruction after "To compile a custom kernel,
> follow these steps" says work in /usr/src/linux while compiling.
> But is conflict: /usr/src/linux/README says "Do NOT use the
> /usr/src/linux area!" Which instruction is correct?


Both. What's the problem? Both have advantages and disadvantages. It's
up to you to decide.

Personally I would never compile anything below /usr in situ! Make a
copy elsewhere.

> Also, is Patrick Volkerding 10.1 instructions acceptable for 10.2?

Anything is acceptable, anytime, to those who want to accept it.

> When exiting make menuconfig, screen says "Next, you may run
> 'make bzImage', 'make bzdisk', or 'make install'. Patrick

Fine.

> Volkerding instructions say make dep ; make clean ; make bzImage.

No difference.

> For learning: what do "make dep ; make clean" steps do?

Man make. Read a book.

> Also, what is differences between:
> make install
> make bzImage
> make zImage
> make image
> make bzdisk
> make zdisk
> make zlilo

Lots.

> Is available tutorial / man / howto explaining menuconfig options?

It comes with help!

Peter

In comp.os.linux.misc Vardan Kushnir <sophim@pol.ru>:



> Michael Heiming <michael+USENET@www.heiming.de> says...

>>Read the Makefile, those steps are obsolete with kernel 2.6:

> I did not say I was compiling kernel 2.6.

> I am compiling kernel 2.4.31, which is current on Slackware 10.2.

Again, read the Makefile to see what those steps do, those are
needed to compile 2.4.x.

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 110: The rolling stones concert down the road
caused a brown out

Vardan Kushnir wrote:

> Also, what is differences between:
> make install

Potential dangerous. Copies the kernel image and System.map to /boot and
runs /sbin/lilo. But if you made a mistake while you build the kernel your
system might not be able to boot.

> make bzImage

This creates a compressed kernel image that might fit on a floppy.

> make zImage

Obsolete. A compressed image, but not as compressed as bZimage.

> make image

Creates a uncompressed kernel image.

> make bzdisk

Creates a boot disk without root filesystem or lilo.

> make zdisk

Obsolete. Use 'make bzdisk' instead.

> make zlilo

Obsolete.
--
Thomas O.

This area is designed to become quite warm during normal operation.

Vardan Kushnir wrote:
> Thank you for help so far!
>

Guide to rolling your own kernel:

http://www.cmm.uklinux.net/steve/kernelhow.html

This is one way of doing it. He explains in an
entertaining and "newbie-friendly" way.

Another (and better?) place to look and read is in
the file README (allways have a look at those before
dealing with sourcecode) in your kernel-source folder.
For more specific subjects, look in your kernels
Documentation directory.

You do not need to work/compile in the /usr/src area,
you can do the compiling as a normal user in your
home directory. Only the install part or manual
copying of the compiled kernel to /boot, and copying
of the compiled modules directory to /lib/modules needs
to be done as root.

Remember from the "Newbie's Top Ten Commands" link
i gave you earlier:

" If you are not root, you can NOT hose your system! You can blow 7
shades of sh** out of your user account and render it dead or at least
very sick indeed. But if you login as a different user, all will be
well. Login as "root" and screw up, and well, it could be a sad day for
you. So keep saying, "Do I need to be root to do this?", if not, dont!!"

That is a very good advice!

And of course the modifying of your bootloader
also needs to be done as root (allways remember
to *run* lilo after making kernelchanges, if that
is your(?) choise of bootloader).



--
Software is not manufactured, it is something you write and publish.
Keep Europe free from software patents, we do not want censorship
by patent law on written works.

On Sat, 22 Oct 2005 10:46:37 +0000, Vardan Kushnir wrote:

> When exiting make menuconfig, screen says "Next, you may run
> 'make bzImage', 'make bzdisk', or 'make install'.

for 2.6 kerneèl it's enough make menuconfig (or make xconfig)
make
make install