linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mbuesch@freenet.de>
To: Greg KH <greg@kroah.com>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 018 release
Date: Fri, 20 Feb 2004 12:48:19 +0000	[thread overview]
Message-ID: <200402201348.29745.mbuesch@freenet.de> (raw)
In-Reply-To: <20040219191315.GB10527@kroah.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 19 February 2004 20:13, you wrote:
> On Thu, Feb 19, 2004 at 10:59:32AM -0800, Greg KH wrote:
> > I've released the 018 version of udev.  It can be found at:
> >  	kernel.org/pub/linux/utils/kernel/hotplug/udev-018.tar.gz
> 
> As of this release, I've been running with udev managing my /dev for me
> exclusively on my main email and development machine.  This is a major
> milestone for udev and it proves that it is a viable solution.

I'm running udev for some time now on my main development
machine and it works (almost) great.
Thanks Greg and all the others who made it possible!

But I've a little issue left. My parallel port doesn't show
up in /udev. I guess it's because of missing sysfs support?
I'm running linux-2.6.3.
I did not find an entry for the parallel port in sysfs.
If I create the device node manually I can access lp.

- -- 
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFANgIcFGK1OIvVOP4RAlMNAJ4zv/qII8xajnelmmgCw7efVJqjTwCfVs4D
/7k2jBdxoXYwSIHn+iSreYA=/yKw
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&opÌk
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2004-02-20 12:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 18:59 [ANNOUNCE] udev 018 release Greg KH
2004-02-19 19:13 ` Greg KH
2004-02-20 12:48   ` Michael Buesch [this message]
2004-02-20 23:56     ` Greg KH
2004-02-19 19:16 ` HOWTO use udev to manage /dev Greg KH
2004-02-19 19:36   ` James Simmons
2004-02-19 19:46     ` Greg KH
2004-02-19 20:21   ` James Simmons
2004-02-19 20:28     ` Greg KH
2004-02-20  0:52     ` Andries Brouwer
2004-02-20 23:57       ` Greg KH
2004-02-19 21:35   ` James Simmons
2004-02-19 22:22   ` Frédéric L. W. Meunier
2004-02-19 22:25     ` Frédéric L. W. Meunier
2004-02-19 23:07     ` Greg KH
2004-02-19 23:46       ` Frédéric L. W. Meunier
2004-02-19 23:56         ` Greg KH
2004-02-20  0:51           ` Frédéric L. W. Meunier
2004-02-20  1:09             ` Frédéric L. W. Meunier
2004-02-20  1:54             ` Greg KH
2004-02-20  2:28               ` Frédéric L. W. Meunier
2004-02-20  7:44                 ` Frédéric L. W. Meunier
2004-02-21 17:42   ` Marco d'Itri
2004-02-22  0:30   ` Frédéric L. W. Meunier
2004-02-21 17:20 ` [ANNOUNCE] udev 018 release Prakash K. Cheemplavam
2004-02-24  1:49   ` 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=200402201348.29745.mbuesch@freenet.de \
    --to=mbuesch@freenet.de \
    --cc=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --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;
as well as URLs for NNTP newsgroup(s).