That's exactly what I do.

As for the overwrite, I was talking about 'make install', NOT your script....

Again, no, it does not do this when /sbin/installkernel is present. If there's no executeable /sbin/installkernel script it will do this, but I was explicitly referring to the case where /sbin/installkernel is present.

If you were talking about the case when no /sbin/installkernel script is present, then you shouldn't have done it in reply to my explanation of how to use the /sbin/installkernel script to speed things along.

But 'make install' will still work, whether or not YOUR script is present, correct?

It is called a 'warning' for a reason.

Let us assume they d/l your script, and copy it to /sbin.

Let us also assume that it does not get chmod to an executable.

Let us assume that they type 'make install' in the kernel source directory.

What happens then?

Take it as a warning, a just in case, a possibilty.

There was NO attempt to slight you, your script, or anything of the sort. Lighten up.

It was a warning. Just in case.

I do apologize that I did not make this clear ('make install' will work without your script, and the following results)in my first post.

However, it can, and does, happen.

See Pats little creatures with big noses and green feet are out again :|

Yes, but, again, this has nothing to do with my script, so it's not appropriate for you to quote what little documentation is necessary for it and cite that as if it were a problem with the script.

In some circles it could also be called a non sequitur.

With the amount of momentum all those assumptions have built up, I figure there's probably room for still more assumptions.

We could just as easily assume that they might well be running these commands from /usr/src/mysql-4.1.19 and are wondering why they've got no vmlinuz file and the menuconfig target didn't work.

We could actually also assume that their house might be on fire, or at this very moment aliens may be poised above it in a cloaked starship, oiling up their new Probulator 3000, in which case a befouled kernel is soon to be the very least of their problems.

Well then don't quote and highlight material that doesn't bear on what you're saying. The whole thing comes off as nearly mystifying, since the whole point of the /sbin/installkernel script is to keep a blind overwrite from happening (and to stop lilo whining about the lack of a -p).

Read the whole post. It is about compiling the kernel.
The OP wanted to compile their kernel.
I pointed out a possible pitfall.
You got all puckered up.
Read my sig about arrogance and perfection.
Lighten up.

You made a post that gave the appearance that what I was suggesting was flawed in a very specific way. You were wrong and you're too bull-headed to admit it. If you were merely posting a "warning" as you claim, there would have been no need to quote my post in the manner that you did.

So... you can just bite me.

Aaaaaand, peace out. Calm down people - this is a help forum not a hissy forum. I think we can all agree that we have been warned and then, if problems arise, we all know where to come for help with the problem.

Yes?