Bryan Kadzban wrote: > Bruce Dubbs wrote: >> IMO, the way to address this is not with a complex set of rules for >> the book or a patch and multiple build method, but a warning about >> the issue and a pointer to a hint or wiki entry to handle the >> specific problem for those few people that need it. > > Now that's not a bad idea. That more or less matches up with what > Alexander was saying earlier today in the ticket about the problem > having multiple solutions. (In his words, the problem is: > >> configuring the network interfaces (i.e., getting the correct udev >> rules and writing the corresponding interface configuration files) > > -- and I'd agree.) It's also similar to his comments about providing > examples of ways to solve the problem (whether those are at the other > end of a wiki link, or a hint link, or right in the book; it probably > doesn't matter a ton), rather than dictating one solution. I do like > that.
OK. It is SVN. It doesn't have to be perfect. I would really like to see you commit what you think is right and we can then work from that to narrow down any outstanding issues. The ticket doesn't have to be closed right away, but from what I can tell, what you have now covers 99% + of users. Lets get that in and then work on the remaining 1%. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
