[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <495ACD9A.40804@pflanze.mine.nu>
Date: Wed, 31 Dec 2008 02:40:42 +0100
From: Christian Jaeger <christian@...anze.mine.nu>
To: Kyle McMartin <kyle@...radead.org>
CC: lmage11@...ny.rr.com, David Miller <davem@...emloft.net>,
linux-kernel@...r.kernel.org
Subject: Re: IRC?
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists