From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: export of SEQNUM to userspace
Date: Wed, 01 Sep 2004 22:36:57 +0000 [thread overview]
Message-ID: <20040901223657.GA24761@vrfy.org> (raw)
In-Reply-To: <20040829203523.GA15526@vrfy.org>
On Tue, Aug 31, 2004 at 02:16:32PM -0400, Greg KH wrote:
> On Sun, Aug 29, 2004 at 10:35:23PM +0200, Kay Sievers wrote:
> > Hi Greg,
> > we want to init HAL with the last emitted hotplug SEQNUM from the
> > kernel. I think of a sysfs file we can read. It would solve the problem
> > of the initial timeout, like we have with udevd too (the very first
> > event is delayed).
>
> Ok, that sounds reasonable.
>
> > What is a proper place to live for this beast?
>
> I'm getting a lot of requests for odd stuff like this in sysfs. Things
> that are "kernel" specific, and aren't associated with any one place
> (things that would end up in /proc/sys/kernel if we didn't have sysfs.)
>
> So, how about /sys/kernel?
Sounds good!
Who should create the kset (or in this case it's a subsystem) for this?
Any hints?
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idP47&alloc_id\x10808&op=click
_______________________________________________
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
next prev parent reply other threads:[~2004-09-01 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 20:35 export of SEQNUM to userspace Kay Sievers
2004-08-31 18:16 ` Greg KH
2004-09-01 22:36 ` Kay Sievers [this message]
2004-09-02 8:10 ` Greg KH
2004-09-03 0:21 ` Kay Sievers
2004-09-03 9:04 ` Greg KH
2004-09-03 9:22 ` Kay Sievers
2004-09-03 13:49 ` Kay Sievers
2004-09-03 17:21 ` Greg KH
2004-10-08 14:43 ` David Zeuthen
2004-10-08 21:05 ` 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=20040901223657.GA24761@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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).