03-07-2012
The next reboot, the udev rules are loaded appropriately based on PCI Bus ID, forcing the names to exist as intended.
PCI slots do not reorder themselves. This is especially an important distinction when dealing with enterprises that have a custom configuration, that for the purposes of homogony and manageability require this level of consistency.
I'm not pulling this out of my rump, it is what the last few companies I have worked for have done, specifically to make sure that consistent device names were kept.
Using the PCI Bus ID will not change so long as the controller is not damaged or the slot is not changed, and it should not be. If it is, it is as simple as changing the persistent naming rule in udev, which would have been changed in the case of a failed card if you used MAC addresses instead of BUS ID, but this saves that effort if the slot is reused, so long as you don't add a controller with a different number of physical ports (like a 2 port NIC to a 4 port NIC). However, most field services reps will replace a failed card in the open slot the previous card had occupied, preventing an outage or problem.
Last edited by mark54g; 03-07-2012 at 01:42 PM..
Reason: clarity and additional info
6 More Discussions You Might Find Interesting
1. IP Networking
Hi sir,
i want to make such programe which takes MAC(Ethernet) address of any host & give me its IP address.......
but i'm nt getting that how i can pass the MAC address to Frame........
Please give me an idea for making such program...
Thanks & regards
Krishna (3 Replies)
Discussion started by: krishnacins
3 Replies
2. HP-UX
Hi, I'm using HPUX 11.11 on Vizualize B180L
our productive machines have 64 bit kernel
# file vmunix
vmunix: ELF-64 executable object file - PA-RISC 2.0 (LP64)
I got one test system, which should have the same HW (i was told it is the same HW)
hpuxtest:/stand-->file... (3 Replies)
Discussion started by: funksen
3 Replies
3. Red Hat
Hi all,
I'm looking to cover a corner case for an upcoming test cycle. Is there a way to boot a RedHat Advanced Server 4 (update 3) installed on a Power PC machine to use a 32 bit kernel? This would be similar to what is done here -> https://www.unix.com/aix/26204-aix-platform.html
I've done... (0 Replies)
Discussion started by: philrau
0 Replies
4. Linux
I can't control the partion order during install.
For example i need.
hda5 /var 1GB
hda6 /opt 2GB
I created them in such order but OS adjust them to
hda5 /opt 2GB
hda6 /var 1GB
It is frustrating during install, I pretty sure I can order the partion as i like... (0 Replies)
Discussion started by: honglus
0 Replies
5. Linux
Hello,
I am using CentOS 5.8 x64 server for our one of internal application which is developed on PHP and Mysql as DB.
Currently there are 8-10 instances deployed on this server some of them are rarely used.
Below is the H/W specification fort the same :-
Procesor :- Intel(R) Xeon(R) CPU ... (6 Replies)
Discussion started by: sunnysthakur
6 Replies
6. IP Networking
four interfaces with ifconfig
all interfaces have the same mac. If is not set for unique.
but it still works.
what difference does it make to have all macs the same or different? (4 Replies)
Discussion started by: rrodgers
4 Replies
LEARN ABOUT OPENSOLARIS
mac_none
MAC_NONE(4) BSD Kernel Interfaces Manual MAC_NONE(4)
NAME
mac_none -- null MAC policy module
SYNOPSIS
To compile the null policy into your kernel, place the following lines in your kernel configuration file:
options MAC
options MAC_NONE
Alternately, to load the sample module at boot time, place the following line in your kernel configuration file:
options MAC
and in loader.conf(5):
mac_none_load="YES"
DESCRIPTION
The mac_none policy module implements a sample MAC policy that has no effect on access control in the system. Unlike mac_stub(4), none of
the MAC entry points are defined.
Label Format
No labels are defined for mac_none.
SEE ALSO
mac(4), mac_biba(4), mac_bsdextended(4), mac_ifoff(4), mac_lomac(4), mac_mls(4), mac_partition(4), mac_portacl(4), mac_seeotheruids(4),
mac_stub(4), mac_test(4), mac(9)
HISTORY
The mac_none policy module first appeared in FreeBSD 5.0 and was developed by the TrustedBSD Project.
AUTHORS
This software was contributed to the FreeBSD Project by Network Associates Labs, the Security Research Division of Network Associates Inc.
under DARPA/SPAWAR contract N66001-01-C-8035 (``CBOSS''), as part of the DARPA CHATS research program.
BUGS
See mac(9) concerning appropriateness for production use. The TrustedBSD MAC Framework is considered experimental in FreeBSD.
While the MAC Framework design is intended to support the containment of the root user, not all attack channels are currently protected by
entry point checks. As such, MAC Framework policies should not be relied on, in isolation, to protect against a malicious privileged user.
BSD
December 1, 2002 BSD