public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Meino Christian Cramer <Meino.Cramer@gmx.de>
To: gentoo-user@lists.gentoo.org, wireless@tampabay.rr.com
Subject: Re: [gentoo-user] Re: Labeling reiserfs partitions
Date: Fri, 04 Aug 2006 19:43:42 +0200 (CEST)	[thread overview]
Message-ID: <20060804.194342.74741367.Meino.Cramer@gmx.de> (raw)
In-Reply-To: <loom.20060804T185848-169@post.gmane.org>

From: James <wireless@tampabay.rr.com>
Subject: [gentoo-user] Re: Labeling reiserfs partitions
Date: Fri, 4 Aug 2006 17:16:29 +0000 (UTC)

> Alexander Skwar <listen <at> alexander.skwar.name> writes:
> 
> 
> > Janusz Bossy wrote:
> > > You can always run mkreiserfs and, after that, restore 
> > > the data with reiserfsck.
> 
> > Hm - is it possible to kick such lamers like Janusz?
> 
> > Alexander Skwar
> 
> Sure, I was temporarily 86'd from the list for being
> a 'bone-head' about iptables.........
> 
> I'm still hard-headed, I just try to keep 'issues'
> to myself........
> 
> On another note, frequent  creation and updates to 
> wikis allows for quick responses to these sort
> of recurring questions.  If the talented
> folks create such wiki pages, the bone-heads could 
> easily learn to refer questions to the wikis in
> lieu of all of this repetition, and misguided
> responses.... Furthermore, ordinary gentoo-linux
> readers could volunteer to maintain these wikis,
> thus reducing the burden on the pool-o-genius.....
> Perhaps a tool like eix/esearch that first
> (priortizes) searches for official/unofficial wiki-responsed 
> to these common questions?
> 
> Furthermore, it would attract more folks to Gentoo.
> 
> hth,
> 
> James

There are three common problems left for those like me asking
"repetitioned questions":

1.) Most search engines of wikis are as "bone-headed" as those trying 
    to answer the question like the above example. Search engines dont 
    understand any context.

2.) For one not being a native English speaker it is often difficult
    to get the right words for the right match.

3.) Sometimes one can describe the problem without the faintest idea
    of any keyword to be filled into such [CENSORED] search engines.

Without the evolution of search engine into finding enginges mailing
lists will exist, where questions are answered more than once.

Kind regards,
mcc
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-08-04 17:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04  9:43 [gentoo-user] Labeling reiserfs partitions Meino Christian Cramer
2006-08-04  9:57 ` Janusz Bossy
2006-08-04 12:43   ` WARNING ! " Meino Christian Cramer
2006-08-04 12:59     ` Dirk Heinrichs
2006-08-04 13:05     ` Neil Bothwick
2006-08-04 13:43       ` Meino Christian Cramer
2006-08-04 13:54         ` Dirk Heinrichs
2006-08-04 17:55           ` Richard Fish
2006-08-04 14:32         ` Neil Bothwick
     [not found]   ` <44D350BA.3030504@mid.message-center.info>
2006-08-04 17:16     ` [gentoo-user] " James
2006-08-04 17:43       ` Meino Christian Cramer [this message]
2006-08-04 19:17         ` James
2006-08-04 22:43           ` Neil Bothwick
2006-08-04 17:49   ` [gentoo-user] " Richard Fish

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=20060804.194342.74741367.Meino.Cramer@gmx.de \
    --to=meino.cramer@gmx.de \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=wireless@tampabay.rr.com \
    /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