mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Kurt H Maier <khm-lists@intma.in>
To: musl@lists.openwall.com
Subject: Re: Best place to discuss other lightweight libraries?
Date: Wed, 24 Apr 2013 00:43:06 -0400	[thread overview]
Message-ID: <20130424044306.GA68573@intma.in> (raw)
In-Reply-To: <20130424023739.GC20323@brightrain.aerifal.cx>

On Tue, Apr 23, 2013 at 10:37:39PM -0400, Rich Felker wrote:
> 
> Because you don't have a keyboard, you have a 3-4" touchscreen. And
> you want it to keep working as you move from place to place without
> any interaction.
> 

If you don't have a keyboard, you likely also don't have physical
ethernet via rj-45, and even if you do, there's no reason to spam
wakeups checking if it's plugged in.  touch-only devices have touch-only
interfaces, which can easily include a 'switch to wired' button instead
of a daemon eating your battery.

setting physical links aside, wpa_supplicant can manage roaming fine.  I
should clarify that I think wpa_supplicant could do with a massive
wrecking ball, but it has a lot of good functionality that obviates a
ton of overengineered networkmanager-type software.  The trick will be
removing the garbage or implementing the good stuff in a slightly less
horrendous fashion.

In fact, I'm firmly of the opinion that complete signal loss is the
*only* time a system should monkey with the network; one of my least
favorite things is my phone aggressively dropping 3G so it can switch
to wifi, dumping my ssh sessions and filesystem mounts in the process. 

> Agree, but it still needs to be solved, even if the solution requires
> frequent updates to be fully effective. With decent heuristics though
> I think it could be fully automated for most sites with just a few
> exceptions for really weird ones..

I think the ideal solution is for network administrators to stop
pretending hijacking sessions is acceptable, but until an automated
solution exists I enjoy all the hate they get from users.

> Agreed. I think really most users should _always_ be running in an
> environment where only root sees the real network interfaces and
> applications just see a virtual network routed through the real one.

This doesn't necessarily solve anything from the user's standpoint
unless he's trained to use the feature appropriately, but it would
enable system designers to get uncomfortably clever in ways that can
make system behavior damn hard to predict.  Having said that, there is
software available on plan 9 called aan - 'any available network' - that
works this way and can be very useful.

khm


  reply	other threads:[~2013-04-24  4:43 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21 16:30 LM
2013-04-21 20:17 ` Rob Landley
2013-04-21 20:24 ` Rob Landley
2013-04-24 11:39   ` LM
2013-04-25 19:30     ` Rob Landley
2013-04-21 23:26 ` Isaac Dunham
2013-04-22 14:53 ` Rich Felker
2013-04-22 15:21   ` Luca Barbato
2013-04-22 16:40     ` LM
2013-04-22 16:47       ` Daniel Cegiełka
2013-04-22 22:07         ` Rich Felker
2013-04-23 12:50           ` LM
2013-04-23 14:40             ` John Spencer
2013-04-23 14:58               ` Rich Felker
2013-04-22 19:31       ` Luca Barbato
2013-04-22 23:24       ` Rob Landley
2013-04-22 23:31         ` Rich Felker
2013-04-23  0:54           ` Rob Landley
2013-04-23  1:46             ` Rich Felker
2013-04-23  5:04               ` Isaac Dunham
2013-04-23 13:47                 ` Rich Felker
2013-04-23 21:25                   ` Luca Barbato
2013-04-23 21:50                   ` Kurt H Maier
2013-04-24  2:37                     ` Rich Felker
2013-04-24  4:43                       ` Kurt H Maier [this message]
2013-04-24 13:37                         ` Rich Felker
2013-04-24  0:50                   ` idunham
2013-04-24  6:11                 ` Rob Landley
2013-04-22 21:52     ` Rich Felker
2013-04-22 22:42       ` Luca Barbato
2013-04-22 23:06         ` Rich Felker
2013-04-23  0:26           ` Luca Barbato
2013-04-23  2:14             ` Rob Landley
2013-04-23 19:07               ` Strake
2013-04-23 19:24                 ` Daniel Cegiełka
2013-04-23 21:33                   ` Szabolcs Nagy
2013-04-24 12:12                     ` Zvi Gilboa
2013-04-23 21:34               ` Luca Barbato
2013-04-24 11:18                 ` Daniel Cegiełka
2013-04-24 11:48                   ` Kurt H Maier
2013-04-24 12:32                     ` Daniel Cegiełka
2013-04-24 13:38                       ` Rich Felker
2013-04-24 13:55                         ` Daniel Cegiełka
2013-04-24 13:37                     ` go support (was: Best place to discuss other lightweight libraries?) John Spencer
2013-04-24 13:39                       ` Rich Felker
2013-04-24 16:33                       ` Kurt H Maier
2013-04-24 15:47                     ` Best place to discuss other lightweight libraries? Szabolcs Nagy
2013-04-24 19:17                       ` Rich Felker
2013-04-25  6:40                         ` Szabolcs Nagy
2013-04-25 19:37                     ` Rob Landley
2013-04-24 13:28                   ` go support (was: Best place to discuss other lightweight libraries?) John Spencer
2013-04-24 13:42                     ` Rich Felker
2013-04-24 14:06                   ` Best place to discuss other lightweight libraries? Christian Neukirchen
2013-04-29 11:41                     ` Daniel Cegiełka
2013-04-29 16:31                       ` Go (was: [musl] Best place to discuss other lightweight libraries?) John Spencer
2013-04-29 16:44                         ` Daniel Cegiełka
2013-04-23  0:31       ` Best place to discuss other lightweight libraries? Rob Landley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130424044306.GA68573@intma.in \
    --to=khm-lists@intma.in \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).