From: Martin Schlemmer <azarah@gentoo.org>
To: Greg KH <greg@kroah.com>
Cc: clemens@dwf.com, linux-hotplug-devel@lists.sourceforge.net,
KML <linux-kernel@vger.kernel.org>,
reg@orion.dwf.com
Subject: Re: [ANNOUNCE] udev 003 release
Date: Tue, 21 Oct 2003 05:38:02 +0200 [thread overview]
Message-ID: <1066707482.10221.243.camel@nosferatu.lan> (raw)
In-Reply-To: <20031021024322.GA29643@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
On Tue, 2003-10-21 at 04:43, Greg KH wrote:
> > > The naming will be consistant from now on. Next release will be 004,
> > > followed by 005, and so on. Remember, version numbers mean nothing :)
> > >
> >
> > Well, if you had an 0.2 already, 003 sorda comes and screw the pooch
> > (if trying to work with a package manager - although it seems we are
> > OK with ours seeing 003 as the later) :)
>
> Exactly, switching this early is fine by all of the package managers
> I've looked at. Does this mean you have a udev gentoo package
> somewhere?
>
Been in the tree for about a week - removed it though (0.2), so only
have 003 presently. I also missed the /etc/hotplug.d/default/ symlink,
so initial integration needs tweaking.
So far have not had any complaints, except for minimal support at this
stage, but hey, its still early in the game =)
Also, I am using ramfs for now to do the device nodes, and have not
looked at minimal /dev layout, although I guess it is not that minimal,
as even the input drivers lack udev (sysfs) support currently it seems.
Wat was the last eta for initramfs again ?
> > > Of course you need a kernel patch for the sound class that is only
> > > available in my kernel tree right now for sound devices to work with
> > > udev...
> > >
> >
> > Need help testing ? :) (Yes, I am a lazy bastard, and a patch against
> > test8 would help if you needed the testing)
>
> I need to get these class patches out sometime soon, been too busy
> lately...
>
NP, thanks anyhow.
Thanks,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-21 3:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 5:56 [ANNOUNCE] udev 003 release Greg KH
2003-10-17 6:32 ` Clemens Schwaighofer
2003-10-17 17:57 ` clemens
2003-10-17 18:19 ` Greg KH
2003-10-17 18:27 ` Greg KH
2003-10-21 0:39 ` Martin Schlemmer
2003-10-21 0:50 ` Greg KH
2003-10-21 1:11 ` Martin Schlemmer
2003-10-21 2:43 ` Greg KH
2003-10-21 3:38 ` Martin Schlemmer [this message]
2003-10-21 17:44 ` Greg KH
2003-10-21 20:20 ` Martin Schlemmer
2003-10-21 20:56 ` Greg KH
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=1066707482.10221.243.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=clemens@dwf.com \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reg@orion.dwf.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