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
| ||
|
Message-ID: <bdfc5d6e0709121240u2e8367cbx620d4d03194f1e85@mail.gmail.com> Date: Wed, 12 Sep 2007 15:40:04 -0400 From: "Andy Gospodarek" <andy@...yhouse.net> To: "Jay Vosburgh" <fubar@...ibm.com> Cc: netdev@...r.kernel.org Subject: Re: [PATCH] bonding: update some distro-specific documentation On 9/12/07, Jay Vosburgh <fubar@...ibm.com> wrote: > Andy Gospodarek <andy@...yhouse.net> wrote: > > >I could do that, or we could just take this as-is and get initscripts > >fixed up to account for this. Does that seem reasonable? > > Changing initscripts is fine, too, but is there then going to be > some (perhaps small) installed base for which the documentation will be > incorrect? > Sure, but it could be wrong if we updated the kernel doc again after initscripts was fixed and some chose not to update initscripts on their boxes. There could be a note about running a particular version of initscripts, but I'd rather not start down the path of turning the kernel doc into something that looks like distro release notes. Either way it seems like there could be a chance for something to be out of sync, so I guess we just have to pick the one that seems 'least bad.' I'd vote for whatever creates the fewest kernel patches. ;-) - 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
Powered by blists - more mailing lists