Yes, but this is the way things are which is different from the way things should be and making people buy a new router seems to me more difficult than just not enabling a small string in a file by default, expecially if this string does nothing but causing trouble to new and unexperienced users which are a target I think ubuntu should aim to reach.
That said, I found this bug was introduced and solved in intrepid, reintroduced and solved in jaunty, reintroduced and not solved in karmic.
Well, at least, why should a dhcp3 update override that file? at least I could make an install stable, instead of having to tell all my friend how to edit the file after every update.
Yes, but this is the way things are which is different from the way things should be and making people buy a new router seems to me more difficult than just not enabling a small string in a file by default, expecially if this string does nothing but causing trouble to new and unexperienced users which are a target I think ubuntu should aim to reach.
That said, I found this bug was introduced and solved in intrepid, reintroduced and solved in jaunty, reintroduced and not solved in karmic.
Well, at least, why should a dhcp3 update override that file? at least I could make an install stable, instead of having to tell all my friend how to edit the file after every update.