Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Jul 2011 10:56:42 +0200
From:      Polytropon <>
To:        FreeBSD <>
Subject:   Re: Lennart Poettering: BSD Isn't Relevant Anymore
Message-ID:  <>
In-Reply-To: <20110719085529.1671ec7f@scorpio>
References:  <20110717071059.25971662@scorpio> <> <> <> <> <> <> <> <20110718162245.0d426239@scorpio> <20110719032131.GA29635@guilt.hydra> <20110719085529.1671ec7f@scorpio>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Tue, 19 Jul 2011 08:55:29 -0400, Jerry wrote:
> On Mon, 18 Jul 2011 21:21:31 -0600
> Chad Perrin articulated:
> > This is where we find a dividing line between users who want different
> > things.  Yes, you turn on your Win7 laptop (or wake it up) in a coffee
> > shop, and it connects automagically -- in fact, you probably don't
> > even realize it has connected.  Hopefully it connected to the coffee
> > shop's network, and not one of those occasional skimming networks that
> > masquerade as coffe shop networks and exist to harvest login data and
> > the like.  The dividing line between two schools of thought on the
> > matter in this example should be obvious.
> You do realize that all of that is configurable; ie, auto connect,
> preferred network, etcetera. If you have not taken the time to read the
> documentation and properly configure the wireless app correctly then
> why bitch? I am not implying that it is perfect; however, given the
> grave limitations that FreeBSD places on wireless connections;
> specifically lack of drivers, and the inordinate amount of manual
> intervention to accomplish what Microsoft and other OSs, (does the name
> Ubuntu sound familiar) have achieved, it is readily apparent that the
> FreeBSD implementation is trailing the pack.

Want it like this? :-)   --->

But coming back on topic (partially): What's missing in
my opinion is a system-provided user land program or
script for interacting with the driver and the settings
(as well as with "templates" for automated setup). There
_are_ however tools provided by the "big ones" (the big
desktop environments KDE, Gnome, maybe Xfce, haven't
checked) to help configuring wireless adaptors. Of
course this only applies where they are supported by
the OS.

A program I could imagine would be something like the
ppp control program that other programs, typically GUI
ones, could interface with, just as gmencoder interfaces
with the incredible power of mencoder, or gmplayer adds
lots of stuff at the GUI front to the one-size-fits-all
fantastic mplayer. So all DEs or programmers who are
interested in providing a setup tool could interface
with that specific program. So they don't have to
implement "low level things" on their own or even care
for supporting particular adaptors. This tool could
also be integrated in the FreeBSD startup system, and
maybe even activated at pre-install time, so you could
install via Internet, where Internet is provided by a
wireless adaptor that got setup automatically. This
would _also_ have the advantage of providing an
abstraction layer that was OPTIONAL, and if you really
need a better implementation (from a developer's point
of view), you can still do it on your own, interfacing
with the standard system means.

Jerry, see this as an "I agree" in relation to your
statement, given the comment that wireless isn't
relevant to _me_ at the moment. :-)

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

Want to link to this message? Use this URL: <>