In message <[EMAIL PROTECTED]> you write:
> Or even better, if you are going to patch, do a 'cp -rl', and your new
ITYM cp -al, and the main benifit (for me) is that diff -urN takes ~10
seconds (cold cache), rather than minutes.
Rusty.
--
Premature optmztion is rt of all evl. --DK
-
To
In message [EMAIL PROTECTED] you write:
Or even better, if you are going to patch, do a 'cp -rl', and your new
ITYM cp -al, and the main benifit (for me) is that diff -urN takes ~10
seconds (cold cache), rather than minutes.
Rusty.
--
Premature optmztion is rt of all evl. --DK
-
To unsubscribe
On 02.02 Ken Moffat wrote:
> Hi guys,
> I guess I'm doing something stupid, so please can somebody point it out
> and put me out of my misery ?
>
> Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
> any errors. Then I realised it had all the object files from my
Dick, and Mark, thanks. It's compiling nicely now. We learn by experience.
Cheers, Ken
> Not to worry. In your new Linux directory tree do:
>
> cd include
> mv asm /tmp # or /usr/src, someplace temporary.
>
> cd .. # Back to Linux
> cp .config .. # Save your configuration
> make
> Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
> any errors. Then I realised it had all the object files from my last
> compile, so I thought "make mrproper" was called for. It did a little,
> then
You copied the link and turned it into its contents
> rm:
On Fri, 2 Feb 2001, Mark Hahn wrote:
> > I guess I'm doing something stupid, so please can somebody point it out
> > and put me out of my misery ?
>
> don't use cp to copy kernel trees unless you use -s.
>
Thanks for the advice, Mark. I'll give it a go in a minute (got to log off
this box and
On Fri, 2 Feb 2001, Ken Moffat wrote:
> Hi guys,
> I guess I'm doing something stupid, so please can somebody point it out
> and put me out of my misery ?
>
> Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
> any errors. Then I realised it had all the object files
Hi guys,
I guess I'm doing something stupid, so please can somebody point it out
and put me out of my misery ?
Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
any errors. Then I realised it had all the object files from my last
compile, so I thought "make mrproper"
Hi guys,
I guess I'm doing something stupid, so please can somebody point it out
and put me out of my misery ?
Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
any errors. Then I realised it had all the object files from my last
compile, so I thought "make mrproper"
On Fri, 2 Feb 2001, Ken Moffat wrote:
Hi guys,
I guess I'm doing something stupid, so please can somebody point it out
and put me out of my misery ?
Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
any errors. Then I realised it had all the object files from
On Fri, 2 Feb 2001, Mark Hahn wrote:
I guess I'm doing something stupid, so please can somebody point it out
and put me out of my misery ?
don't use cp to copy kernel trees unless you use -s.
Thanks for the advice, Mark. I'll give it a go in a minute (got to log off
this box and
Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
any errors. Then I realised it had all the object files from my last
compile, so I thought "make mrproper" was called for. It did a little,
then
You copied the link and turned it into its contents
rm: include/asm:
Dick, and Mark, thanks. It's compiling nicely now. We learn by experience.
Cheers, Ken
Not to worry. In your new Linux directory tree do:
cd include
mv asm /tmp # or /usr/src, someplace temporary.
cd .. # Back to Linux
cp .config .. # Save your configuration
make mrproper #
On 02.02 Ken Moffat wrote:
Hi guys,
I guess I'm doing something stupid, so please can somebody point it out
and put me out of my misery ?
Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
any errors. Then I realised it had all the object files from my last
14 matches
Mail list logo
