public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steen Eugen Poulsen <sep@lix-world.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] genkernel vs kernel manual compilation
Date: Fri, 31 Aug 2007 22:14:17 +0200	[thread overview]
Message-ID: <46D87699.8050400@lix-world.net> (raw)
In-Reply-To: <64e8d2f20708311007k2368f317m79f487e24639a46a@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2319 bytes --]

Ryan Sims skrev:
> I think Volker's point about genkernel not making things easier is
> just that it seems to be a source of confusion and complexity in this

Go read his post please, he is making things up and blaming the tool for
an idiot using it wrong.

He somehow thinks that genkernel is autoconfiggenrartorsuperai, It
isn't, it's a simple script to easily handle repeated compiles of kernels.

Anyone can write scripts to do the same or claim they don't mind writing
the same command over and over every time they handle a kernel compile,
but to turn around and use that fact to attack and descridit genkernel
so viciously done in this thread is nothing but FUD.


And to the lies:

Lie:
because I have seen more than one non-booting totally f* up kernel
created by
genkernel. I won't touch it ever again. If something sucked in the past,
the
change is great that it sucks again in the future. Plus it doesn't really
make things easier, does it?


Thats a LIE, genkernel DOES not have ANY inteligence to create .config
for kernels, why is he spreading FUD about it creating "f* up" kernels.

In /usr/share/genkernel you will find *TEMPLATES* that can be used, but
they aren't LiveCD setups to create all round kernels, it's possible
they should be, but at the moment they are rough templates you can use
to make a .config.


Lie 2: It doesn't make things easier.

It does make things easier, again he is confusing automagic .config
creation with what genkernel can help with. The tool automate the task
involved in compiling kernels and/or maintaining multiple
configurations. And the Vol fellow really should start using genkernel
as his comment clearly demonstrate he does not take appropriate caution
to ensure that the kernel source is in a sane state between compiles.

The kernel make file is very complicated and fragile, genkernels propper
step is *NOT* idiocy, but done because it avoid bugging the kernel
compile. (WARNING! Don't start doing mrproppers manually, it erase the
.config file, something that --save-config option of genkernel handles
so you don't loss your configuration)

All the rest of his hate drivel is based on this kind of made up FUD
against it and he is not alone, you see this hate FUD being spread all
over about a decent tool, the author(s) deserve better treatment than this.

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3412 bytes --]

  parent reply	other threads:[~2007-08-31 20:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070830184238.0e18d880@pataki.bogus.net>
     [not found] ` <200708302351.44562.volker.armin.hemmann@tu-clausthal.de>
     [not found]   ` <20070831012035.2177385c@pataki.bogus.net>
     [not found]     ` <200708310414.30036.volker.armin.hemmann@tu-clausthal.de>
     [not found]       ` <20070831132353.15682d4f@pataki.bogus.net>
2007-08-31 13:41         ` [gentoo-user] genkernel vs kernel manual compilation Ryan Sims
2007-08-31 19:00           ` Arnau Bria
2007-08-31 20:09             ` Ryan Sims
2007-09-01 13:47               ` Arnau Bria
2007-09-01 18:54                 ` Arnau Bria
2007-08-31 21:33             ` Volker Armin Hemmann
2007-08-31 13:45         ` Volker Armin Hemmann
     [not found]   ` <342e1090708301509g17c2abe3k11e43b4ca2b10d8b@mail.gmail.com>
     [not found]     ` <200708310417.54047.volker.armin.hemmann@tu-clausthal.de>
2007-08-31 15:54       ` Steen Eugen Poulsen
2007-08-31 17:07         ` Ryan Sims
2007-08-31 17:25           ` Volker Armin Hemmann
2007-08-31 20:14           ` Steen Eugen Poulsen [this message]
2007-08-31 21:07             ` Daniel da Veiga
2007-08-31 21:38             ` Volker Armin Hemmann
2007-08-31 21:54               ` Daniel da Veiga
2007-09-01  2:30                 ` Volker Armin Hemmann
2007-08-31 21:44             ` Ryan Sims
2007-08-31 22:22               ` Steen Eugen Poulsen
2007-08-31 22:44                 ` Ryan Sims
2007-08-31 22:53                   ` [gentoo-user] [OT] " Dan Farrell
     [not found] ` <64e8d2f20708301116i13b705bdhfa8c30bf708033a6@mail.gmail.com>
     [not found]   ` <200708302037.01039.f.philipp@addcom.de>
     [not found]     ` <64e8d2f20708301152q5ffd5376hda7d77f667280db7@mail.gmail.com>
     [not found]       ` <20070831010931.1cc0eefd@pataki.bogus.net>
2007-08-31 23:52         ` [gentoo-user] " Александър Л. Димитров
2007-09-01  8:57 ` [gentoo-user] " Marc Blumentritt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46D87699.8050400@lix-world.net \
    --to=sep@lix-world.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox