public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: yaird-devel@lists.alioth.debian.org,
	linux-hotplug-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Yaird-devel] [ANNOUNCE] yaird 0.0.12, a mkinitrd based on hotplug concepts
Date: Fri, 9 Dec 2005 11:08:58 +0100	[thread overview]
Message-ID: <20051209100858.GA26472@localhost.localdomain> (raw)
In-Reply-To: <20051209002235.A16206@banaan.localdomain>

On Fri, Dec 09, 2005 at 12:22:35AM +0100, Erik van Konijnenburg wrote:
> Hmm, now that hotplug is being replaced with udev, it's time to come up
> with a new blurb ...

Notice that hotplug or udev or whatever are just the userland tools used to
handle the kernel-side hotplug events, so it is a story of two names, a bit
like initramfs-tools and initramfs :)

Friendly,

Sven Luther


      reply	other threads:[~2005-12-09 10:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 23:22 [ANNOUNCE] yaird 0.0.12, a mkinitrd based on hotplug concepts Erik van Konijnenburg
2005-12-09 10:08 ` Sven Luther [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=20051209100858.GA26472@localhost.localdomain \
    --to=sven.luther@wanadoo.fr \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yaird-devel@lists.alioth.debian.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