From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: running queue processes
Date: Mon, 04 May 2015 12:41:52 -0400 [thread overview]
Message-ID: <5547A150.80901@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1505040431530.30646@Device-040570>
On 2015-05-04 04:45 AM, Robert P. J. Day wrote:
> On Sun, 3 May 2015, Nicholas Krause wrote:
>
>>
>>
>> On May 3, 2015 9:16:27 AM EDT, Ruben Safir <ruben@mrbrklyn.com> wrote:
>>> On 05/03/2015 08:47 AM, Nicholas Krause wrote:
>>>> remember there being information about this topic being in the Linux
>>> programming interface in chapters 26 through 28. Furthermore find a
>>> copy of this book as it's a rather good reference for when you need
>>> questions like this answered.
>>>
>>>
>>> which book?
>
>>> The book is called the Linux programming interface and the chapters
>>> related to this question are chapters 26 or 27 I believe.
>
> nick, this is another reason your contributions to this forum (and
> pretty much every other one you're on) are so frequently valueless --
> you rarely give a complete or useful answer.
>
> i suspect the book you're referring to is michael kerrisk's "the
> linux programming interface", http://man7.org/tlpi/index.html (a book
> to which i have actually contributed corrections,
> http://man7.org/tlpi/errata/index.html), which is a reference you
> *could* have provided but, instead, you chose to leave just this
> maddeningly half-vague reference to a book and some chapter numbers.
>
> it's an annoying habit with you, nick -- someone asks a well-formed
> and specific question and, because you always want to be the first one
> to jump in with an answer to burnish your credentials, your reply is
> typically something like, "i think there's a system call that does
> what you want, you should look it up."
>
> your eagerness to leap in and be the first one to be helpful
> typically means your contributions are vague, vacuous, incomplete and,
> in some cases, simply wrong. but rather than take the time to
> research the question so that your response is actually *helpful*, you
> prefer to contribute little more than, "i think this thing might help
> what you're working on, you should check the man page."
>
> you're not doing your reputation any favours.
>
> rday
>
Rday,
Yet everything I ask a question I get a similar response like do your homework or read more rather
then any help. Clearly I understand with my older questions why but all of my questions now are
similar in nature to this so there is no reason for that.
Nick
prev parent reply other threads:[~2015-05-04 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 15:20 running queue processes Mustafa Hussain
2015-05-03 12:47 ` Nicholas Krause
2015-05-03 13:16 ` Ruben Safir
2015-05-03 17:42 ` Nicholas Krause
2015-05-04 8:45 ` Robert P. J. Day
2015-05-04 16:41 ` nick [this message]
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=5547A150.80901@gmail.com \
--to=xerofoify@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).