On 8/7/07, Shawn <[EMAIL PROTECTED]> wrote:
> Dan Nicholson wrote:
> > On 8/4/07, Shawn <[EMAIL PROTECTED]> wrote:
> >
> >> 2. 6.23, p. 1. A typo in the first paragraph.
> >
> > s/used used/used/'. Thanks. I also reworded it to not be so awkward.
> > How would you like to be referenced in the Changelog?
> Ha, for such a small thing. You must be kidding. :p
Too late :)
> >> 3. 7.13.1. A minor point, but the description of the finding in
> >> /etc/udev/rules.d/70-persistent-net.rules did not match what I
> >> found. What I found was a single line (other than comments) that
> >> assigned a name (eth0) by MAC address. Also, in this same section
> >> there is a typo (I think). Anyhow, my rule looks like this.
> >> SUBSYSTEM=="net", DRIVERS=="?*",
> >> ATTRS{address}=="00:00:00:00:00:00", NAME="eth0"
> >
> > So, each device gets two lines: a comment description, then a udev
> > rule. So, I guess it should be clearer that the first line is a
> > comment. The rule looks correct and matches the description that I
> > see. All you're missing is an ATTRS{type}, and it's described as
> > optional. Which part exactly doesn't match what you expected?
>
> 7.13. Configuring the network script.
> "Each NIC takes up two lines in the file. The first line is a
> description of the NIC itself..."
>
> Not in my output. Then...
>
> "This line is a comment; neither the hardware ID nor the driver..."
>
> "This line is a comment;" is throwing me off. Looking at my output I
> might say:
>
> "The file consists of a header and one or more rules. The header is a
> comment that describes how the file was created. Each line in the header
> is preceded by a "#" and can be safely ignored. Following the header are
> the Udev rules, one or more lines for each NIC. Examining each rule, we
> will notice that each NIC is assigned a unique name (e.g. NAME="eth0").
> The "NAME" key is assigned the device name of the NIC."
OK, that makes a little more sense. I think I'll try to clean it up to
be more specific about what you'll see. Especially since you only have
one interface, it's not as obvious what's what. That's probably the
case for most people, too.
And actually what's happening is that the rule is reassigning the
device name for the interface. Since we're not guaranteed to get the
same name from the kernel when there are multiple interfaces, the
rules match on MAC address and then assign NAME. This allows you to
have persistent names eth0, eth1, etc. (or whatever you feel like
calling them).
> Since I only have one NIC, I cannot validate the "one or more lines"
> statement. Maybe each rule consists of only one line? So I said "one or
> more lines" to cover my ...
Here's what it looks like on my desktop. I have two interfaces: wired
and firewire. This ensures that my wired interface is always eth0.
Here it's pretty clear that there's the block of comments at the top
and then each device has a comment followed by a rule.
$ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:18:f3:02:3a:cd",
NAME="eth0"
# Firewire device 0011d8000035e0ac)
SUBSYSTEM=="net", DRIVERS=="?*",
ATTRS{address}=="00:11:d8:00:00:35:e0:ac", NAME="eth1"
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
