On Thu, Mar 29, 2007 at 11:29:05PM -0400, Bill Nottingham wrote:
> Greg KH ([EMAIL PROTECTED]) said:
> > > If interfaces have to change, so be it. But changing the rules for
> > > using them years after it's implemented and then claiming "you didn't
> > > read the instructions" is pretty lame.
>
Greg KH ([EMAIL PROTECTED]) said:
> > If interfaces have to change, so be it. But changing the rules for
> > using them years after it's implemented and then claiming "you didn't
> > read the instructions" is pretty lame.
>
> That documentation has been in the kernel tree for almost a full year:
On Wed, Mar 28, 2007 at 08:41:38PM -0400, Bill Nottingham wrote:
> Greg KH ([EMAIL PROTECTED]) said:
> > If you follow the rules in Documentation/ABI/testing/sysfs-class your
> > program will not have any problems.
>
> Oh, of *course*. We add interfaces and then claim years later,
> after code
On Wed, Mar 28, 2007 at 08:41:38PM -0400, Bill Nottingham wrote:
Greg KH ([EMAIL PROTECTED]) said:
If you follow the rules in Documentation/ABI/testing/sysfs-class your
program will not have any problems.
Oh, of *course*. We add interfaces and then claim years later,
after code has been
Greg KH ([EMAIL PROTECTED]) said:
If interfaces have to change, so be it. But changing the rules for
using them years after it's implemented and then claiming you didn't
read the instructions is pretty lame.
That documentation has been in the kernel tree for almost a full year:
It has a
On Thu, Mar 29, 2007 at 11:29:05PM -0400, Bill Nottingham wrote:
Greg KH ([EMAIL PROTECTED]) said:
If interfaces have to change, so be it. But changing the rules for
using them years after it's implemented and then claiming you didn't
read the instructions is pretty lame.
That
Greg KH ([EMAIL PROTECTED]) said:
> If you follow the rules in Documentation/ABI/testing/sysfs-class your
> program will not have any problems.
Oh, of *course*. We add interfaces and then claim years later,
after code has been written, "Oh, you shouldn't be using that!" in
documentation.
Greg KH ([EMAIL PROTECTED]) said:
If you follow the rules in Documentation/ABI/testing/sysfs-class your
program will not have any problems.
Oh, of *course*. We add interfaces and then claim years later,
after code has been written, Oh, you shouldn't be using that! in
documentation. Meanwhile,
On Tue, Mar 27, 2007 at 11:17:43PM -0400, Bill Nottingham wrote:
> Kay Sievers ([EMAIL PROTECTED]) said:
> > >If you *do* try to use one of these names, the rename will succeed...
> > >partway. The link in /sys/class/net is renamed, the directory is
> > >not (as it obviously can't rename on top
Kay Sievers ([EMAIL PROTECTED]) said:
> >If you *do* try to use one of these names, the rename will succeed...
> >partway. The link in /sys/class/net is renamed, the directory is
> >not (as it obviously can't rename on top of whatever is already there.)
> >Various networking tools then break in
Kay Sievers ([EMAIL PROTECTED]) said:
If you *do* try to use one of these names, the rename will succeed...
partway. The link in /sys/class/net is renamed, the directory is
not (as it obviously can't rename on top of whatever is already there.)
Various networking tools then break in assorted
On Tue, Mar 27, 2007 at 11:17:43PM -0400, Bill Nottingham wrote:
Kay Sievers ([EMAIL PROTECTED]) said:
If you *do* try to use one of these names, the rename will succeed...
partway. The link in /sys/class/net is renamed, the directory is
not (as it obviously can't rename on top of whatever
On 3/20/07, Bill Nottingham <[EMAIL PROTECTED]> wrote:
I was fiddling with the 'new' (no CONFIG_SYSFS_DEPRECATED) layout
and ethernet device names, and noticed that the new layout effectively
restricts the availability of certain device names.
By making a directory for the ethernet device name
On 3/20/07, Bill Nottingham [EMAIL PROTECTED] wrote:
I was fiddling with the 'new' (no CONFIG_SYSFS_DEPRECATED) layout
and ethernet device names, and noticed that the new layout effectively
restricts the availability of certain device names.
By making a directory for the ethernet device name in
I was fiddling with the 'new' (no CONFIG_SYSFS_DEPRECATED) layout
and ethernet device names, and noticed that the new layout effectively
restricts the availability of certain device names.
By making a directory for the ethernet device name in the parent
device, you no longer can use any name that
I was fiddling with the 'new' (no CONFIG_SYSFS_DEPRECATED) layout
and ethernet device names, and noticed that the new layout effectively
restricts the availability of certain device names.
By making a directory for the ethernet device name in the parent
device, you no longer can use any name that
16 matches
Mail list logo
