<?xml version="1.0" encoding="UTF-8"?>
<hash>
  <event-id type="integer">2009</event-id>
  <updated-at>08/18/2009</updated-at>
  <biography nil="true"></biography>
  <title>Network Device Naming</title>
  <submitted-at>06/19/2009</submitted-at>
  <website nil="true"></website>
  <id type="integer">78</id>
  <description>Network devices have but a single name, and for systems with &gt; 1 NIC, it's probably wrong.  System administrators have long believed that 'eth0' was meaningful (i.e. it is the NIC that the system booted from, or is the first NIC on the motherboard of a system).  However, for many reasons, this name is arbitrary, and may change from boot to boot.  We need network device name aliases, just as we do for disk devices (/dev/disk/by-label/..., /dev/disk/by-uuid/...), so we can provide several meaningful names to network devices also.</description>
  <presenter nil="true"></presenter>
  <user-id nil="true"></user-id>
  <affiliation nil="true"></affiliation>
  <created-at>06/19/2009</created-at>
</hash>
