From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-August/018355.html | 97 ++++++++++++++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-August/018355.html (limited to 'zarb-ml/mageia-dev/2012-August/018355.html') diff --git a/zarb-ml/mageia-dev/2012-August/018355.html b/zarb-ml/mageia-dev/2012-August/018355.html new file mode 100644 index 000000000..02ef834ca --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018355.html @@ -0,0 +1,97 @@ + + + + [Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3) + + + + + + + + + +

[Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3)

+ Pascal Terjan + pterjan at gmail.com +
+ Wed Aug 29 16:13:17 CEST 2012 +

+
+ +
On Wed, Aug 29, 2012 at 3:06 PM, Thierry Vignaud
+<thierry.vignaud at gmail.com> wrote:
+> On 29 August 2012 15:46, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>>> Is there any migration to do in drakx and ldetect because of this?
+>>
+>> Oh yeah I meant to send a message to the list about this.
+>>
+>> Yeah because we're now on kernel 3.5 we can no longer do certain things
+>> relating to this mount point.
+>>
+>> IIRC some ldetect stuff used it and some of the 3G and/or
+>> printer/scanner stuff might also depend on it and need to be migrated
+>> too. I don't know that code very well, but I know some folks complained
+>> when we stopped mounting it by default, so I've no doubt that it's use
+>> is lurking somewhere!
+>>
+>> I would guess that in some cases /dev/bus/usb/ might be sufficient for
+>> what is needed.
+>
+> Humm...
+> I've still around a patch making ldetect using libusb.
+> Sadly, we're missing some data...
+> Basically we would miss the kernel driver name binded with each usb device.
+>
+> We cannot workaround it since libusb misses with the ability to either
+> query the sysfs device path or to got the Port number
+> ("Port" in /proc/bus/usb/devices).
+> (I miss the Port number in order to compute the
+> /sys/bus/devices/usb/foobar path)
+>
+> W/o that I cannot retrieve the modalias which would help me to get the kernel
+> driver name.
+>
+> I guess I'll have to resurect that work and try harder to find some
+> workaround...
+
+Why not using sysfs for everything directly?
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1