The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
To: Johannes Weiner <hannes@saeurebad.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix kernel thread names that might offend users.
Date: Wed, 02 Apr 2008 04:28:51 +0400	[thread overview]
Message-ID: <47F2D343.3060009@gmail.com> (raw)
In-Reply-To: <87r6dps3db.fsf@saeurebad.de>

Johannes Weiner wrote:
> More and more GNOME users (especially Ubuntu) get confused by their
> process list showing several process names that seem to indicate
> KDE-related services.
> 
> To settle things down a bit on the bugtrackers, this patch renames all
> offending kernel threads into something that goes better with
> GNOME-based systems.
> 
> Since KDE is essentially dead, the thread-names are not made
> compile-time configurable but rather just renamed completely here to
> fit modern distributions. 
> 
> Signed-off-by: Johannes Weiner <hannes@saeurebad.de>
> ---
> 
> Please note that these hard-coded names are going to be removed soon
> completely in another patch series that makes kernel thread names more
> `themable' in the sense that users may supply a format string in
> /proc/sys/kernel/kthread_fmt which allows having customizable names
> like "-=[acpid]=-" or similar.
> 
> Also, please let me know if I forgot something. 

Did you forget to send this patch yesterday in which case this would have
been more suitable for April 1st?

Dmitri

  parent reply	other threads:[~2008-04-02  0:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 20:54 [PATCH] Fix kernel thread names that might offend users Johannes Weiner
2008-04-01 22:18 ` Randy Dunlap
2008-04-01 22:30   ` Andreas Schwab
2008-04-02  0:28 ` Dmitri Vorobiev [this message]
2008-04-02  3:21   ` Jan Engelhardt
2008-04-02  2:36 ` Henrique de Moraes Holschuh
2008-04-02 14:02 ` linux-os (Dick Johnson)
2008-04-02 15:16   ` Johannes Weiner
2008-04-02 17:21     ` linux-os (Dick Johnson)
2008-04-02 22:41       ` Chris Friesen

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=47F2D343.3060009@gmail.com \
    --to=dmitri.vorobiev@gmail.com \
    --cc=hannes@saeurebad.de \
    --cc=linux-kernel@vger.kernel.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