[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#224742: Related to this issue...

On Sun, 28 Dec 2003 13:32:21 +1000, Anthony Towns
<aj@azure.humbug.org.au> wrote:
>On Sat, Dec 27, 2003 at 09:43:27AM +0100, Enrico Zini wrote:
>> There are IMHO.  To resume them:
>>  1) Parameterless lines can be useful when a parameter made no sense
>Parameterless lines do *nothing* more than a line with a dummy parameter
>in this case.

They do a considerably better job in being readable for a human.

>>  4) I showed you examples of other programs accessing
>>     /etc/network/interfaces and proposed considering a wider role for it
>No changes to the file are necessary for that to happen; and more
>importantly the file belongs to ifupdown, and if other programs wish to
>use it, they get to follow ifupdown's rules. If you want a configuration
>file that works differently, you get to create one of your own.

/e/n/i does a pretty good job of being a central place for
network-interface-related configuration data.

>> For the records, a proposed way to handle this could be:
>"Ask for the feature. Get told how to do it differently. Do it differently."

Gee. How nice it is to work with Philip Hazel.


-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber          |   " Questions are the         | Mailadresse im Header
Karlsruhe, Germany  |     Beginning of Wisdom "     | Fon: *49 721 966 32 15
Nordisch by Nature  | Lt. Worf, TNG "Rightful Heir" | Fax: *49 721 966 31 29

Reply to: