netdev - Re: [PATCH] bonding: update docs to correctly reflect arp_ip

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 22 Oct 2008 13:30:25 -0700
From:	Jay Vosburgh <fubar@...ibm.com>
To:	Andy Gospodarek <andy@...yhouse.net>
cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] bonding: update docs to correctly reflect arp_ip_target behavior

Andy Gospodarek <andy@...yhouse.net> wrote:

>The latest version of Red Hat Enterprise Linux 5 doesn't need '+' in
>front of each IP address listed as an arp_ip_target, and correctly
>supports a comma separated list of IP addresses using the current
>version of initscripts.  This patch drops all references to the need for
>a '+' before each IP address and the description now matches the
>behavior.

	Don't the prior versions of RHEL 5 (initscripts, really) still
need the "+"?  If so, I'd prefer to have this say "for initscripts
versions X - Y (RHEL A.B, Fedora Q.Y), do it this way; for versions
since Y (RHEL A.C, Fedora Q.Z), do it this other way."

	I'm not keen on removing information that isn't tied directly to
the bonding driver itself.  I just know somebody will run the latest
mainline kernel on their RHEL 5.mumble and then the documentation will
steer them down the wrong road.

	-J

---
	-Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html