From: Christian Jaeger <christian@pflanze.mine.nu>
To: Kyle McMartin <kyle@infradead.org>
Cc: lmage11@twcny.rr.com, David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: IRC?
Date: Wed, 31 Dec 2008 02:40:42 +0100 [thread overview]
Message-ID: <495ACD9A.40804@pflanze.mine.nu> (raw)
In-Reply-To: <20081230033552.GE29678@bombadil.infradead.org>
Kyle McMartin wrote:
> I believe the kernelnewbies folks already have a well-publicized irc
> location... There are typically at least a few developers there.
I quite like the #kernelnewbies since it's the only place I know where I
can ask userspace questions :~D
I'm mostly a userspace developer, my life writing kernel code is
restricted to a couple of tiny drivers and one-line tweaks. And merging
of thirdparty patches. So I don't have much need for asking questions
about kernelspace questions, but frequently I need to know how I
interface to something in the kernel but don't know how (example: how do
I get at the blocksize and size of a block device? (I know the answer
now.) Or what the name of the "sandboxing" feature of Linux was
(seccomp) and how it seemed to have changed interfaces. Getting clarity
with questions like which tool displays which kind of cpu usage ("what
is iowait?"). Getting help when I see strange behaviour like with I/O
almost locking up the machine. Which are the right git trees to get the
kernel. "Is there a way to change the pipe kernel buffer size from user
space
?" "What is a/the 'TSC'?" How to crosscompile (make ARCH=i386). etc. etc.)
I'm almost always feeling guilty misusing that channel for such
questions, but it's the best place I know where I can get answers to
such questions... :) Thanks for anyone there bearing with me.
Christian.
next prev parent reply other threads:[~2008-12-31 1:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 1:19 IRC? lmage11
2008-12-30 1:34 ` IRC? Russell Miller
2008-12-30 1:40 ` IRC? Jesper Juhl
2008-12-30 1:47 ` IRC? lmage11
2008-12-30 3:19 ` IRC? david
2008-12-30 2:23 ` IRC? Kyle Moffett
2008-12-30 2:28 ` IRC? lmage11
2008-12-30 2:07 ` IRC? David Miller
2008-12-30 2:11 ` IRC? lmage11
2008-12-30 2:34 ` IRC? David Miller
2008-12-30 2:46 ` IRC? lmage11
2008-12-30 3:35 ` IRC? Kyle McMartin
2008-12-31 1:40 ` Christian Jaeger [this message]
2008-12-30 17:12 ` IRC? Stefan Richter
2008-12-31 14:01 ` IRC? Rik van Riel
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=495ACD9A.40804@pflanze.mine.nu \
--to=christian@pflanze.mine.nu \
--cc=davem@davemloft.net \
--cc=kyle@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lmage11@twcny.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