From: Andreas Dilger <adilger@turbolabs.com>
To: Andrew Ebling <kernelhacker@lineone.net>
Cc: kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org
Subject: Re: suggestions for new kernel hacking-HOWTO
Date: Sat, 25 Aug 2001 12:09:35 -0600 [thread overview]
Message-ID: <20010825120935.H16615@lynx.no> (raw)
In-Reply-To: <998602169.405.21.camel@elixr.jfreak>
In-Reply-To: <998602169.405.21.camel@elixr.jfreak>; from kernelhacker@lineone.net on Thu, Aug 23, 2001 at 10:29:27PM +0100
On Aug 23, 2001 22:29 +0100, Andrew Ebling wrote:
> - How do I... ?
> - Print messages to kernel logs
> - create a new module
> - Add a system call
> - write ioctls
> - Add a /proc entry
> - Write a driver for a new device
> - Add an option to the kernel configuation
Be sure to add notes about why NOT to add new system calls, ioctls, /proc
entries, etc. It seems that the popular way to communicate to the kernel
these days is to be able to read/write data to the kernel device driver
via opening a device, or exporting a pseudo filesystem with information.
> I'm interested in hearing from seasoned kernel hackers (on what
> should/shouldn't go in this HOWTO) and newbies (what is particularly
> puzzling or not clear when setting out), hence the cross posting of this
> message.
Check out kernelnewbies.org as well, no point in re-inventing the wheel.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
prev parent reply other threads:[~2001-08-25 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 21:29 suggestions for new kernel hacking-HOWTO Andrew Ebling
2001-08-24 6:27 ` Arnaldo Carvalho de Melo
2001-08-24 14:28 ` Pragnesh Sampat
2001-08-25 14:01 ` Rusty Russell
2001-08-25 18:09 ` Andreas Dilger [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=20010825120935.H16615@lynx.no \
--to=adilger@turbolabs.com \
--cc=kernelhacker@lineone.net \
--cc=kernelnewbies@nl.linux.org \
--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