[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150111170220.GD3999@openwall.com>
Date: Sun, 11 Jan 2015 20:02:20 +0300
From: croco@...nwall.com
To: owl-dev@...ts.openwall.com
Subject: Re: Re: [owl-users] Owl 3.1-stable
On Sun, Jan 11, 2015 at 07:48:53PM +0300, gremlin@...mlin.ru wrote:
> On 2015-01-11 19:00:17 +0300, croco@...nwall.com wrote:
>
> >> That's why I've introduced the ability to override the
> >> configuration with a /etc/rc.d/rc.network script in recently
> >> published owl-startup package
> > Such ability is good for people who prefer to do everything
> > manually.
>
> The primary reason for doing that was the need to build more
> complex configurations than a single ethernet link.
Well, it is possible to have as many interfaces as you want without the
need of overriding the Owl default networking startup; furthermore, 'setup'
and 'settle' are able to configure as many interfaces as you wish, both
physical cards and aliases. I recall several years ago Solar was impressed
that, after he started (remotely) a new machine, configured two ethernets,
and the 'settle' picked the configuration of them both when the time came.
However, I perfectly understand you: more automation always means less
flexibility.
--
Croco
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
