On Sat, Oct 10, 2009 at 12:03:27AM +0200, Michael Thayer wrote: > On Fri, 2009-10-09 at 07:46 -0700, Greg KH wrote: > > > The way that I have done things so far rather disregards > > > the advice in Documentation/sysfs-rules.txt; I have a feeling though > > > that that advice is somewhat outdated. Would it be possible to update > > > that file to reflect current wisdom? > > > > I don't understand, what documentation needs to be updated? > OK, re-reading it I think I may have misunderstood what I read > previously. The point which was immediately causing me pain was that it > seemed to me you were saying that /sys/block was going away, which would > have been a shame, since it is one of the bits that has stayed the same > almost from the beginning. I take it though that all the future changes > mentioned in that document are long done. /sys/block will go away some day, you are correct. > > You might want to look into using libudev if you are relying on sysfs > > device usages, it is future-proofed a lot for some of the changes that > > will be happening to the sysfs layout in the next few years. > Doesn't help me, as I need something that will work with older kernel > versions as well. Might be worth my taking a look at though. Otherwise > I will just fix whatever breaks when that happens. I think libudev will work with older kernel versions, you might want to try it out. good luck, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
