On Wed, Mar 09, 2005 at 09:32:58AM +0200, Jari Aalto wrote: > The file format of /etc/exports should allow spaces between the HOST and > DEF. Like from this: > > /tmp 192.168.1.0/28(rw,sync,no_root_squash,sync) > > to this: > > /tmp 192.168.1.0/28 (rw,sync,no_root_squash,sync) > ===== > > This would allow writing more structured entried that can be "lined up" > with other lines.
After contemplating this, I'm not sure it's such a good idea. The problem is that this actually has a meaning; the latter means the same as: /tmp 192.168.1.0/28(sync) *(rw,sync,no_root_squash,sync) Changing that is going to break people's /etc/exports; you can call (foo) => *(foo) a pathological case, but I'm fairly certain 192.168.1.0/28 => 192.168.1.0/28(default options) is in actual use. This would also create an unclear grammar. What would this be? /tmp 127.0.0.1 (async) (async) Backtracking and guessing in the parser would not be popular among upstream, and I'm not sure if it's a good idea polluting the code with it either. :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
