Greg KH <[EMAIL PROTECTED]> writes:
> We need our own namespace for these devices, and we have it today
> already. Look if you enable CONFIG_SYSFS_DEPRECATED, or on a pre-2.6.19
> machine at what shows up in the pci device directories:
> -r--r--r-- 1 root root 4096 2007-02-18 13:06 vendor
Inte
On Sun, Feb 18, 2007 at 03:52:05PM -0700, Eric W. Biederman wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
>
> > On Sun, Feb 18, 2007 at 08:55:20AM -0700, Eric W. Biederman wrote:
> >> User space is allowed to rename network devices to anything any name
> >> not currently taken by another network de
Greg KH <[EMAIL PROTECTED]> writes:
> On Sun, Feb 18, 2007 at 08:55:20AM -0700, Eric W. Biederman wrote:
>> User space is allowed to rename network devices to anything any name
>> not currently taken by another network device.
>>
>> However when I now do something like:
>>
>> ip link set eth0 na
On Sun, Feb 18, 2007 at 08:55:20AM -0700, Eric W. Biederman wrote:
>
> I believe the culprit is 43cb76d91ee85f579a69d42bc8efc08bac560278.
>
> For some reason network devices are now showing up under the pci
> device tree, in directories that have something other than network
> devices.
>
> # ls
I believe the culprit is 43cb76d91ee85f579a69d42bc8efc08bac560278.
For some reason network devices are now showing up under the pci
device tree, in directories that have something other than network
devices.
# ls -l /sys/class/net/eth0
lrwxrwxrwx 1 root root 0 Feb 17 23:19 /sys/class/net/eth0 ->
