Alexander Hall alexan...@beard.se wrote:
IIRC, isn't there a few distinct (non-ifconfig-compatible) cases we
handle specially, and the rest is passed as-is to ifconfig?
Is it?
Okay, I've looked at the netstart code again. It messes with any
lines where
* the first word is dhcp, rtsol, inet,
On Nov 26, 2012, at 9:44 PM, Christian Weisgerber na...@mips.inka.de wrote:
Todd T. Fries t...@fries.net wrote:
If there are desires to improve this (I hear Naddy grumbling!) then the
stomach to break backwards compat must be present, or suggestions on how
to do it without breaking
On 26 November 2012 22:06, Stuart Henderson s...@spacehopper.org wrote:
On 2012/11/26 17:40, Jason McIntyre wrote:
anyway...i still dislike the idea of just saying order matters. also,
could someone really expect the file to not be parsed top down
Yes, I think they might; people are used to
On Tue, Nov 27, 2012 at 10:25:39AM +0200, Gregory Edigarov wrote:
On 11/27/2012 09:03 AM, Claudio Jeker wrote:
On Mon, Nov 26, 2012 at 05:36:20PM -0700, Theo de Raadt wrote:
If there are desires to improve this (I hear Naddy grumbling!) then the
stomach to break backwards compat must be
On 2012/11/26 22:24, Christian Weisgerber wrote:
Mark Kettenis:
I don't really see what this buys us. You still have to maintain the
backwards compat code. You'll end up with an inconsistent mess of
hostname.if and if.whatever files. And all of this to fix what exactly?
To preserve
Stuart Henderson s...@spacehopper.org wrote:
On 2012/11/26 22:24, Christian Weisgerber wrote:
[...]
After some further reflection, I think I agree with sthen.
I am mostly happy with hostname.if, but I would find it useful
to have a nicer syntax that allows ignoring other parsing and
feeds
To pass a line directly to ifconfig and prevent it from being
interpreted as a packed format, use !ifconfig \$if flags.
Yes.
(I think I may change my files to !ifconfig ... format
now, it's ugly but it will avoid errors; not least because
then I can use /prefix notation rather
On 11/27/12 16:20, Christian Weisgerber wrote:
Stuart Henderson s...@spacehopper.org wrote:
On 2012/11/26 22:24, Christian Weisgerber wrote:
[...]
After some further reflection, I think I agree with sthen.
I am mostly happy with hostname.if, but I would find it useful
to have a nicer
On 2012/11/27 23:50, Alexander Hall wrote:
IIRC, isn't there a few distinct (non-ifconfig-compatible) cases we
handle specially,
yes, but it's the important ones: inet and inet6.
inet by itself is pretty easy, it's the default anyway so you can
just write 11.22.33.44/28 directly in
On Mon, Nov 26, 2012 at 04:30:47PM +0200, Paul Irofti wrote:
Be more specific about the order of interpretation. Okay?
diff --git share/man/man5/hostname.if.5 share/man/man5/hostname.if.5
index b07459f..aa8446f 100644
--- share/man/man5/hostname.if.5
+++ share/man/man5/hostname.if.5
@@
On Mon, Nov 26, 2012 at 12:11 PM, Andres Perera andre...@zoho.com wrote:
don't know about OP, but yesterday i was surprised when rtlabel had to
be specified after inet
just double checked; s/after/before
ifconfig(8) section on rtlabel bears no mention about the order
before rearranging, lines
On Mon, Nov 26, 2012 at 04:26:12PM +, Jason McIntyre wrote:
On Mon, Nov 26, 2012 at 04:30:47PM +0200, Paul Irofti wrote:
Be more specific about the order of interpretation. Okay?
diff --git share/man/man5/hostname.if.5 share/man/man5/hostname.if.5
index b07459f..aa8446f 100644
---
On Mon, Nov 26, 2012 at 04:26:12PM +, Jason McIntyre wrote:
On Mon, Nov 26, 2012 at 04:30:47PM +0200, Paul Irofti wrote:
Be more specific about the order of interpretation. Okay?
diff --git share/man/man5/hostname.if.5 share/man/man5/hostname.if.5
index b07459f..aa8446f 100644
---
On Mon, Nov 26, 2012 at 07:19:23PM +0200, Paul Irofti wrote:
On Mon, Nov 26, 2012 at 04:26:12PM +, Jason McIntyre wrote:
On Mon, Nov 26, 2012 at 04:30:47PM +0200, Paul Irofti wrote:
Be more specific about the order of interpretation. Okay?
diff --git share/man/man5/hostname.if.5
On Mon, Nov 26, 2012 at 05:40:06PM +, Jason McIntyre wrote:
On Mon, Nov 26, 2012 at 07:19:23PM +0200, Paul Irofti wrote:
On Mon, Nov 26, 2012 at 04:26:12PM +, Jason McIntyre wrote:
On Mon, Nov 26, 2012 at 04:30:47PM +0200, Paul Irofti wrote:
Be more specific about the order of
On Mon, Nov 26, 2012 at 01:58:45PM -0500, Kenneth R Westerback wrote:
does dhcp nwid foo wpakey bar give you problems too? because
hostname.if(5) suggests it should not:
A DHCP-configured network interface setup consists of
dhcp options
There have been problems
Penned by Kenneth R. Westerback on 20121126 12:58.45, we have:
| On Mon, Nov 26, 2012 at 05:40:06PM +, Jason McIntyre wrote:
| On Mon, Nov 26, 2012 at 07:19:23PM +0200, Paul Irofti wrote:
| On Mon, Nov 26, 2012 at 04:26:12PM +, Jason McIntyre wrote:
|On Mon, Nov 26, 2012 at
Jason McIntyre j...@kerhand.co.uk wrote:
On Mon, Nov 26, 2012 at 07:19:23PM +0200, Paul Irofti wrote:
On Mon, Nov 26, 2012 at 04:26:12PM +, Jason McIntyre wrote:
On Mon, Nov 26, 2012 at 04:30:47PM +0200, Paul Irofti wrote:
Be more specific about the order of interpretation. Okay?
Todd T. Fries t...@fries.net wrote:
If there are desires to improve this (I hear Naddy grumbling!) then the
stomach to break backwards compat must be present, or suggestions on how
to do it without breaking backwards compat must be suggested.
My suggestion is two-fold:
* Introduce a new
From: na...@mips.inka.de (Christian Weisgerber)
Date: Mon, 26 Nov 2012 20:44:45 + (UTC)
Todd T. Fries t...@fries.net wrote:
If there are desires to improve this (I hear Naddy grumbling!) then the
stomach to break backwards compat must be present, or suggestions on how
to do it
On 2012/11/26 17:40, Jason McIntyre wrote:
anyway...i still dislike the idea of just saying order matters. also,
could someone really expect the file to not be parsed top down
Yes, I think they might; people are used to config files being read
and parsed before being applied, and because this
Mark Kettenis:
I don't really see what this buys us. You still have to maintain the
backwards compat code. You'll end up with an inconsistent mess of
hostname.if and if.whatever files. And all of this to fix what exactly?
To preserve my sanity every time I need to figure out how to bring
If there are desires to improve this (I hear Naddy grumbling!) then the
stomach to break backwards compat must be present, or suggestions on how
to do it without breaking backwards compat must be suggested.
My suggestion is two-fold:
* Introduce a new format. This new format will ignore #
On Mon, Nov 26, 2012 at 05:36:20PM -0700, Theo de Raadt wrote:
If there are desires to improve this (I hear Naddy grumbling!) then the
stomach to break backwards compat must be present, or suggestions on how
to do it without breaking backwards compat must be suggested.
My suggestion is
24 matches
Mail list logo
