On Thu, Aug 30, 2018 at 7:09 PM, Stephen Hemminger <step...@networkplumber.org> wrote: > On Thu, 30 Aug 2018 18:41:14 -0300 > Dan Gora <d...@adax.com> wrote: > >> On the other hand, the "write to /sys" method is a bit more simple and >> confines the changes to the user space library. If we're confident >> that the /sys ABI is stable and not going to be changed going forward >> it seems like a valid alternative. > > See Documentation/ABI/testing/sysfs-class-net
yeah, but it's in the 'testing' directory :) >From Documentation/ABI/README: testing/ This directory documents interfaces that are felt to be stable, as the main development of this interface has been completed. The interface can be changed to add new features, but the current interface will not break by doing this, unless grave errors or security problems are found in them. Userspace programs can start to rely on these interfaces, but they must be aware of changes that can occur before these interfaces move to be marked stable. Programs that use these interfaces are strongly encouraged to add their name to the description of these interfaces, so that the kernel developers can easily notify them if any changes occur (see the description of the layout of the files below for details on how to do this.) Like I said, I'm ok with using this if that's what everyone wants to do. d
