[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48B7FAEC.80206@kernel.org>
Date: Fri, 29 Aug 2008 15:34:36 +0200
From: Tejun Heo <tj@...nel.org>
To: Kay Sievers <kay.sievers@...y.org>
CC: Greg KH <greg@...ah.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
David Zeuthen <david@...ar.dk>
Subject: Re: [PATCH 2/2] uevent: handle duplicate uevent_var keys properly
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists