On Fri, Jun 22, 2001 at 08:44:51PM +0200, Robert Waldner wrote:
> now do a `make clean` (just to get rid of the modules, mostly) and
make-kpkg clean
> re-do steps 1-3 for the second machine and the third and...
It will complain if you use machines' hostnames in
On Fri, Jun 22, 2001 at 08:17:14PM +0200, MaD dUCK wrote:
> also sprach Bob Nielsen (on Fri, 22 Jun 2001 10:42:23AM -0700):
> > True, but you can/should configure and compile separately for each
> > destination architecture, optimizing appropriately.
>
> so yes, the argument that my athlon (thunde
also sprach Robert Waldner (on Fri, 22 Jun 2001 08:44:51PM +0200):
> now do a `make clean` (just to get rid of the modules, mostly) and
> re-do steps 1-3 for the second machine and the third and...
>
> when you want to re-do for the first machine, just move the appropriate
> .config back, and
On Fri, 22 Jun 2001 20:28:04 +0200, MaD dUCK writes:
>also sprach Robert Waldner (on Fri, 22 Jun 2001 08:20:41PM +0200):
>> you don´t need to maintain seperate trees of the whole source. just
>> `make (menu|x|)config`, then backup the .config-file. that´s where the
>> information you entered/c
also sprach Robert Waldner (on Fri, 22 Jun 2001 08:20:41PM +0200):
> you don´t need to maintain seperate trees of the whole source. just
> `make (menu|x|)config`, then backup the .config-file. that´s where the
> information you entered/chose is kept.
i understand... but when i change the .conf
On Fri, 22 Jun 2001 20:17:14 +0200, MaD dUCK writes:
>also sprach Bob Nielsen (on Fri, 22 Jun 2001 10:42:23AM -0700):
>> True, but you can/should configure and compile separately for each
>> destination architecture, optimizing appropriately.
>
>so yes, the argument that my athlon (thunderbird act
also sprach Bob Nielsen (on Fri, 22 Jun 2001 10:42:23AM -0700):
> True, but you can/should configure and compile separately for each
> destination architecture, optimizing appropriately.
so yes, the argument that my athlon (thunderbird actually) will
outperform the others still holds. but i'd need
also sprach Nathan E Norman (on Fri, 22 Jun 2001 12:42:37PM -0500):
> I fail to see why you think compiling a kernel on an Athlon, but
> optimising for a 486 cos you're installing on a 486 is a problem.
that's what i am doing btw. and sorry, i wasn't possibly thinking
about multiple .debs, just th
On Fri, Jun 22, 2001 at 06:34:25PM +0200, MaD dUCK wrote:
> also sprach Nathan E Norman (on Fri, 22 Jun 2001 11:01:13AM -0500):
> > Well, for one thing, you can compile kernels on your 1GHz Athlon
> > instead of your old 486 :) Since kernel-package creates a package, it
> > can be installed anywhe
On Fri, Jun 22, 2001 at 06:34:25PM +0200, MaD dUCK wrote:
> also sprach Nathan E Norman (on Fri, 22 Jun 2001 11:01:13AM -0500):
> > Well, for one thing, you can compile kernels on your 1GHz Athlon
> > instead of your old 486 :) Since kernel-package creates a package, it
> > can be installed anywhe
On Fri, Jun 22, 2001 at 06:34:25PM +0200, MaD dUCK wrote:
> also sprach Nathan E Norman (on Fri, 22 Jun 2001 11:01:13AM -0500):
> > Well, for one thing, you can compile kernels on your 1GHz Athlon
> > instead of your old 486 :) Since kernel-package creates a package, it
> > can be installed anywhe
also sprach Sean Morgan (on Fri, 22 Jun 2001 12:05:19PM -0400):
> zless /usr/share/doc/kernel-package/Rationale
exaclty what i wanted. thanks!
martin; (greetings from the heart of the sun.)
\ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
--
your fly might be open
also sprach Nathan E Norman (on Fri, 22 Jun 2001 11:01:13AM -0500):
> Well, for one thing, you can compile kernels on your 1GHz Athlon
> instead of your old 486 :) Since kernel-package creates a package, it
> can be installed anywhere.
but i usually choose the appropriate kernel architecture duri
13 matches
Mail list logo