/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
Richard Price <[EMAIL PROTECTED]> wrote:
>
> Can anyone tell me what is going on? Note, I am proficient enough to
> patch kernels etc as long as I have the instructions in front of me.
Okay, here are some instructions:
Different patches are, well, different. However, they usually have a
format that looks like this:
> diff -uNr -x *.o -x .* linux-2.2.5-clean/Makefile linux/Makefile
>
> --- linux-2.2.5-clean/Makefile Mon Apr 19 18:38:31 1999
> +++ linux/Makefile Sat May 1 19:14:42 1999
This is telling you what command was used to produce the patch, and what
the names of the patched files are. The important thing to notice here
is the exact pathname given. Here, the pathname is "linux/Makefile".
For this patch to work best, it needs to be run from a location where a
file named "linux/Makefile" can be found.
Since most distributions put the kernel source code in a directory
called /usr/src/linux, the best place to patch a kernel is from the
/usr/src directory. Then the "linux/" paths will be valid.
With this information you can then run the commands:
cd /usr/src
patch -p0 -s < /path/to/patch/file
The "-p0" option tells the patch utility to use the entire pathname. If
you run patch from the proper directory, as I describe above, this means
that the patch utility will never stop and ask you which file you want
to patch. You probably don't know the answer anyway. :)
The "-s" options makes patch run silently, which is better than getting
screenfuls of "Hmmm..." and "This looks kinda like a patch" and "Hunk 3
succeeded" types of messages, which only make sense to people who are
fluent with C and programming and patching. With the "-s" option, patch
will only tell you about things that go wrong. If NOTHING AT ALL is
printed out then... you have a successful patch! If you get messages
about rejects, well... you're in trouble, and some of that C knowledge
would be required to figure out what happened and why.
>From your description of the output, it sounds like the patch utility
didn't actually change any of your files. That's good. It means you
should be able to patch successfully and have it work. The worst thing
is if a patch process is started, then interrupted, so some of the
patches have taken effect, and others haven't. Hate it when that
happens; it takes a lot of work to recover.
--
[EMAIL PROTECTED] (Fuzzy Fox) || "Nothing takes the taste out of peanut
sometimes known as David DeSimone || butter quite like unrequited love."
http://www.dallas.net/~fox/ || -- Charlie Brown
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
