[arch-projects] [netcfg] [PATCH 2/2] Add 'last' NETWORKS option (FS#23015)

Jouke Witteveen j.witteveen at gmail.com
Sun Jun 24 18:40:32 EDT 2012

On Fri, Jun 22, 2012 at 11:44 AM, Henrik Hallberg <henrik at k2h.se> wrote:
> On Fri, Jun 22, 2012 at 02:25:28AM +0200, Jouke Witteveen wrote:
>> Can anyone describe a good use case?
> First, it seems like a sane default. I prefer less configuration and
> reasonable behaviour over more configuration and perfect results. This
> would change a configuration item to read up on, test and remember, to
> something that works well enough out-of-the-box.

A somewhat meager argument, since it doesn't tell me when you would
need this functionality.

> Second, when travelling and staying in different places, it would be
> convenient to use this hiberate-like restoration.

Potentially useful indeed, but you can already just list all different
places you go to in NETWORKS and it will connect to the first one that
it can connect to. This works even better than the 'last'
functionality, as it does away with the need to connect manually at
every location change.

> For me, this strikes the balance between convenient and simple, and
> reasonable.  Maybe there's a combination of netcfg-auto-* that does what
> I'm looking for?

Just netcfg-auto-wireless should largely cover your concerns too.

Nevertheless I gave your code some thought and since there was a bug
report for the same issue, I decided to give it a shot.
2.8.5 contains the requested functionality. I started with some minor
changes of your patch, but later decided to do the whole thing in a
single commit.

Thanks for your contribution, without it the functionality would not
have arrived in 2.8.5.

- Jouke

More information about the arch-projects mailing list