From: Tejun Heo <tj@kernel.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Greg KH <greg@kroah.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Zeuthen <david@fubar.dk>
Subject: Re: [PATCH 2/2] uevent: handle duplicate uevent_var keys properly
Date: Fri, 29 Aug 2008 15:34:36 +0200 [thread overview]
Message-ID: <48B7FAEC.80206@kernel.org> (raw)
In-Reply-To: <1220016439.24737.18.camel@lgn.site>
Hello,
Kay Sievers wrote:
>> For OSS emulation, it didn't really matter. For cases where it matters,
>> I think easier path to take would be let the userland emulation set up a
>> directory containing pseudo files and just override DEVPATH to it.
>> Would that work?
>
> No, I don't think so, it's a too bad hack. the SUBSYSTEM key, the entry
> in the class/bus directory, and the target of the symlink in the device
> directory _must_ match. Everything else asks for serious trouble, by the
> inconsistency it creates.
I'm afraid trying to do that from kernel side would require more scary
hack as CUSE will need to push in random device under unsuspecting
parent / class. Maybe we can add a variable to indicate an emulated
device or to tell udev/hal whatever to use alt root for sys hierarchy or
just consider sysfs is not available? I think this problem can be
settled between userland programs.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-08-29 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 16:30 [PATCH 1/2] uevent: don't pass envp_ext[] as format string in kobject_uevent_env() Tejun Heo
2008-08-28 16:31 ` [PATCH 2/2] uevent: handle duplicate uevent_var keys properly Tejun Heo
2008-08-28 16:49 ` Greg KH
2008-08-28 17:00 ` Tejun Heo
2008-08-28 17:33 ` Greg KH
2008-08-29 7:48 ` Kay Sievers
2008-08-29 8:02 ` Tejun Heo
2008-08-29 13:27 ` Kay Sievers
2008-08-29 13:34 ` Tejun Heo [this message]
2008-08-29 13:54 ` Kay Sievers
2008-08-29 15:00 ` Tejun Heo
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=48B7FAEC.80206@kernel.org \
--to=tj@kernel.org \
--cc=david@fubar.dk \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.