Re: Fine. (was: Re: C Non-Programming Non-Challenge)

Liste des GroupesRevenir à ol advocacy 
Sujet : Re: Fine. (was: Re: C Non-Programming Non-Challenge)
De : vallor (at) *nospam* cultnix.org (vallor)
Groupes : comp.os.linux.advocacy
Date : 18. Jun 2024, 00:14:24
Autres entêtes
Message-ID : <pan$ba8b2$eddf74ec$7edbf63f$43784830@cultnix.org>
References : 1 2 3 4 5 6 7 8 9 10
User-Agent : Pan/0.159 (Vovchansk; 873418b; Linux-6.9.5)
On Mon, 17 Jun 2024 15:51:03 -0400, Joel <joelcrump@gmail.com> wrote in
<gq417jh0a5tukhqvcsr416215qdgrkorb6@4ax.com>:

Farley Flud <ff@linux.rocks> wrote:
On 17 Jun 2024 03:38:35 GMT, vallor wrote:
>
Compile time with -j48 and sources on my NAS:
 
real 2371.85 user 16336.41 sys 4707.19
>
What the flamin' fuck!
>
Do you actually mean that it requires 40+ minutes for you to compile a
kernel?
>
I have been compiling kernels for years and it's always been about 2
minutes, at -j8, which includes all the modules.
>
It must be the kernel configuration.  I configure the kernel to include
only the stuff I need and I especially exclude all that security
bullshit.
>
What is the size of your compressed kernel image?  This is the file
named "bzImage" in the kernel source tree.
>
My bzImage, for kernel 6.9.1, is only 3154944 bytes.
>
Note that the "bz" does not necessarily indicate that bzip2 compression
is used.  The particular compression algorithm is set at kernel
configuration.  Mine uses LZMA.
 
 
Why do you guys even do this shit?  My kernels are downloaded as
compiled binaries, already, generic, it doesn't hurt anything.  It's
just like using Windows, but without M$'s crud bloating it.  It's a
dream.

I like wrenching on my OS, like some people wrench on their hot rods.
Might even find a bug, in which case I can a) report it,
b) possibly with a fix.

As I've said numerous times, I build a "kitchen sink" kernel, basically
with all the modules.  _ALL_ the modules, not the subset FF is building.
(I started with the Linux Mint low-latency .config several kernels ago,
and have been migrating that ever since.)

That way, if the compilation spits out a diagnostic for anything,
I'll know about it.

If I wanted to, there's a make target for "localmodconfig" which will set
up the build system to only make the modules that are loaded.  But that
can leave out (say) iptables modules, which would be a pain if I went and
tried to use something new.  So, I build _all_ the modules.

What I would like to do is someday figure out how to build
with -march=native .  Haven't bothered yet, because my machine is already
plenty fast.

Finally, the bottleneck for building the kernel in that last run is
compiling on an NFS share...

$ ll linux-6.9.5/arch/x86/boot/bzImage
-rw-rw-r-- 1 x x 12648960 Jun 16 20:10 linux-6.9.5/arch/x86/boot/bzImage

--
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.9.5 Release: Mint 21.3 Mem: 258G
   "Never test for an error you don't know how to handle."

Date Sujet#  Auteur
15 Jun 24 * C Programming Challenge69Farley Flud
15 Jun 24 +* Re: Another Feeb Fail. Poseurs Indeed. (was: C Programming Challenge)4Tyrone
15 Jun 24 i`* Re: Another Feeb Fail. Poseurs Indeed. (was: C Programming Challenge)3Diego Garcia
16 Jun 24 i +- Re: Another Feeb Fail. Poseurs Indeed. (was: C Programming Challenge)1candycanearter07
16 Jun 24 i `- Re: Another Feeb Fail. Poseurs Indeed.1DFS
15 Jun 24 +* Re: C Programming Challenge2Chris Ahlstrom
15 Jun 24 i`- Re: C Programming Challenge1Joel
15 Jun 24 `* Re: C Programming Challenge62Farley Flud
16 Jun 24  +* Re: C Programming Challenge2Farley Flud
16 Jun 24  i`- Re: C Programming Challenge1Stéphane CARPENTIER
16 Jun 24  `* Re: C Non-Programming Non-Challenge (was: C Programming Challenge)59Tyrone
16 Jun 24   +* Re: C Non-Programming Non-Challenge (was: C Programming Challenge)56vallor
16 Jun 24   i+- Re: C Non-Programming Non-Challenge (was: C Programming Challenge)1vallor
16 Jun 24   i`* Re: C Non-Programming Non-Challenge54DFS
17 Jun 24   i `* Re: C Non-Programming Non-Challenge53vallor
17 Jun 24   i  +* Re: C Non-Programming Non-Challenge37%
17 Jun 24   i  i+* Re: C Non-Programming Non-Challenge2vallor
17 Jun 24   i  ii`- Re: C Non-Programming Non-Challenge1%
17 Jun 24   i  i`* Fine. (was: Re: C Non-Programming Non-Challenge)34vallor
17 Jun 24   i  i `* Re: Fine. (was: Re: C Non-Programming Non-Challenge)33Joel
18 Jun 24   i  i  `* Re: Fine. (was: Re: C Non-Programming Non-Challenge)32vallor
18 Jun 24   i  i   `* Re: Fine. (was: Re: C Non-Programming Non-Challenge)31Farley Flud
18 Jun 24   i  i    +* Re: Fine. (was: Re: C Non-Programming Non-Challenge)29vallor
19 Jun 24   i  i    i+* Re: Fine.25%
19 Jun 24   i  i    ii`* Re: Fine.24vallor
19 Jun 24   i  i    ii +- Re: Fine.1%
19 Jun 24   i  i    ii +* Re: Fine.20%
19 Jun 24   i  i    ii i+* Re: Fine.9vallor
19 Jun 24   i  i    ii ii+* Re: Fine.7Joel
19 Jun 24   i  i    ii iii+* Re: Fine.2vallor
19 Jun 24   i  i    ii iiii`- Re: Fine.1Chris Ahlstrom
19 Jun 24   i  i    ii iii+- Re: Fine.1Joel
19 Jun 24   i  i    ii iii+- Re: Fine.1rbowman
19 Jun 24   i  i    ii iii`* Re: Fine.2vallor
19 Jun 24   i  i    ii iii `- Re: Fine.1%
19 Jun 24   i  i    ii ii`- Re: Fine.1%
19 Jun 24   i  i    ii i+* Re: Fine.7Joel
19 Jun 24   i  i    ii ii`* Re: Fine.6%
19 Jun 24   i  i    ii ii `* Re: Fine.5vallor
19 Jun 24   i  i    ii ii  `* Re: Fine.4%
19 Jun 24   i  i    ii ii   `* Re: Fine.3vallor
19 Jun 24   i  i    ii ii    `* Re: Fine.2%
19 Jun 24   i  i    ii ii     `- Re: Fine.1%
19 Jun 24   i  i    ii i+- Re: Fine.1%
19 Jun 24   i  i    ii i+- Re: Fine.1Joel
19 Jun 24   i  i    ii i`- Re: Fine.1rbowman
19 Jun 24   i  i    ii +- Re: Fine.1Chris Ahlstrom
20 Jun 24   i  i    ii `- Re: Fine.1vallor
19 Jun 24   i  i    i`* Re: Fine. (was: Re: C Non-Programming Non-Challenge)3Farley Flud
19 Jun 24   i  i    i `* Re: Fine.2vallor
19 Jun 24   i  i    i  `- Re: Fine.1Chris Ahlstrom
22 Jun 24   i  i    `- Re: Fine. (was: Re: C Non-Programming Non-Challenge)1Stéphane CARPENTIER
17 Jun 24   i  +* Re: C Non-Programming Non-Challenge2DFS
17 Jun 24   i  i`- Re: C Non-Programming Non-Challenge1vallor
17 Jun 24   i  +- Re: C Non-Programming Non-Challenge1Farley Flud
18 Jun 24   i  `* Re: C Non-Programming Non-Challenge12DFS
19 Jun 24   i   `* Re: C Non-Programming Non-Challenge11vallor
19 Jun 24   i    +- Re: C Non-Programming Non-Challenge1%
19 Jun 24   i    +* Re: C Non-Programming Non-Challenge6Farley Flud
19 Jun 24   i    i+- Re: C Non-Programming Non-Challenge1Chris Ahlstrom
20 Jun 24   i    i`* Re: C Non-Programming Non-Challenge4candycanearter07
22 Jun 24   i    i `* Re: C Non-Programming Non-Challenge3Stéphane CARPENTIER
23 Jun 24   i    i  `* Re: C Non-Programming Non-Challenge2candycanearter07
23 Jun 24   i    i   `- Re: C Non-Programming Non-Challenge1Stéphane CARPENTIER
19 Jun 24   i    +- [OT] Re: C Non-Programming Non-Challenge1vallor
19 Jun 24   i    +- Re: C Non-Programming Non-Challenge1rbowman
20 Jun 24   i    `- Re: C Non-Programming Non-Challenge1candycanearter07
16 Jun 24   `* Re: C Non-Programming Non-Challenge (was: C Programming Challenge)2rbowman
16 Jun 24    `- Re: C Non-Programming Non-Challenge1Tyrone

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal