Quoting Matthew Palmer ([email protected]): > However, if link detection fails, the user isn't notified. I've done this > because link detection isn't universal (ethtool-lite is known not to work on > wireless interfaces, for example), and I don't want to break things for > those users. However, it is possible that the user selected the wrong > interface > or the cable isn't plugged in, so it'd be nice if the user could be notified > about this. > > Need to do the following: > > * A new boolean template, like netcfg/static_link_detection_failed, that > says something like "${interface} has been successfully configured, but no > link has been detected. This could be because your NIC doesn't support > link detection, or you may have selected the wrong NIC or the cable is > unplugged. Would you like to continue using this NIC, or go back and > choose another?"
Seems fair.
A few wording suggestions before you propose a template text
- this should be "sublevel 2" (put :sl2: in the right place, see
other templates for examples) as this is something that's likely to
show up in default installs....but only in some situations
- forget about double spaces after dots..:-)
- avoid "NIC"
- avoid interrogative form in the long description
- avoid ${interface} at the beginning of a sentence (bad
capitalization)
- CC debian-l10n-english when working on the template's text
signature.asc
Description: Digital signature
