New answers tagged devices
2
Have you tried including the MAC addresses in the different ifcfg-ethX files for the various ethernet devices? Additionally you can control which device get's which ethX handle through udev's 60-net.rules file.
For example
# /etc/sysconfig/network-scripts/ifcfg-eth0
# Intel Corporation 82573E Gigabit Ethernet Controller (Copper)
DEVICE=eth0
...
1
You should get hardware address by:
ifconfig -a | grep HWaddr
Or perhaps:
tail -v /sys/devices/*/*/net/eth*/address
# or
tail -v /sys/devices/*/*/*/net/eth*/address
find should have matched.
Also check:
cat /etc/udev/rules.d/70-persistent-net.rules
Se comments below.
2
So far as I know , you need a relatively new release. RHEL 6 seems to support this (Consistent Network Device Naming) though it does need to be specifically enabled on most systems. Fedora 15+ also does this, and, by Fedora 17, it seems to be the default mode.
I don't know exactly when this change was completely adopted and, more important to this question, ...
0
This is largely a historical holdover from days when the operations console was an actual teletype that printed (made indelible marks) on a piece of paper (a thin flexible material made from wood fiber, often white). Over time, these have largely been directed to the syslog and dmesg facilities since very few systems now have an actual console but the ...
0
The /dev/console is an abstraction of the local terminal session - console associated with the monitor plugged into the machine.
Its purpose, mainly on servers, is to provide remote access even if the system is running in single-user mode. Such console is (in most cases) bound to the eth0 device when the eth0 networking is turned off.
3
It represent the bitmask for events supported by the device.
The B in from stands for bitmap.
As you know computers deal in binary, so:
1 = 0001
2 = 0010
3 = 0011
4 = 0100
5 = 0101
...
So if i have a bitmap with value 5 that one would hold bits 0 and 2 in other
word one can give each number a name and check if they correspond to a value.
E.g.
A = 1, ...
2
Short-term solution:
% sudo modprobe dummy
% sudo ip l set dev dummy0 name MyEth11
% sudo ip ad ad 192.168.255.254/30 dev MyEth11
% ip ad show dev MyEth11
14: MyEth11: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN
link/ether 6e:73:12:ad:db:8e brd ff:ff:ff:ff:ff:ff
inet 192.168.255.254/30 scope global MyEth11
% sudo ip l set MyEth11 up
0
The major device number identifies the driver (e.g. IDE disk drive, floppy disk, parallel port, serial port, ...) and the minor number identifies the specific device (i.e., the first floppy would have minor 0, the second would be 1, ...).
3
All devices have a major, minor number pair. The major number is a larger, more generic category (e.g. hard disks, input/output devices etc...) while the minor number is more specific (i.e. tells what bus the device is connected to).
Check the kernel documentation for more examples.
3
Potential Method #1
I think you can do it with these commands:
disable
echo 0 > /sys/bus/pci/slots/$N/power
enable
echo 1 > /sys/bus/pci/slots/$N/power
Where $N is the number of the PCI slot.
lspci -vv may help to identify the device. This is not very well documented...
Potential Method #2
I came across this thread on U&L, similar ...
3
Udev is the system component that determines the names of devices under Linux — mostly file names under /dev, but also the names of network interfaces.
Versions of udev from 099 to 196 come with rules to record the names of network interfaces and always use the same number for the same device. These rules are disabled by default starting from udev 174, but ...
0
This issue has been solved as of systemd v197 with the introduction of persistent naming for network devices.
According to the freedesktop Predictable Network Interface Names page, the kernel simply assigned names based on the order they were probed by the relevant drivers:
The classic naming scheme for network interfaces applied by the kernel is to simply ...
Top 50 recent answers are included
