[K12OSN] TC wifi initializtion - concept

[Roger Nutbeam]

I've have some clients on regular desktops that have to run X over
wireless, and it just sucks. And this is only with a couple of desktops
using wireless.


On Tue, Apr 8, 2014 at 11:08 AM, Roger Nutbeam <gnutbeam at gmail.com> wrote:

> I concur. Latency is just terrible on wireless.
>
>
> On Mon, Apr 7, 2014 at 9:54 PM, Terrell Prude' Jr. <
> microman at cmosnetworks.com> wrote:
>
>> No way in heck I would want TC's on wireless.  It's a hub.  X11 screen
>> updates can suck up to 73 Mbit/sec when playing TuxType (I did this
>> measurement about 10 years ago and re-confirmed it about 5 years ago).  As
>> much as the wireless hype may be going on now, there's just no way an LTSP
>> architecture can be successful on a hub, be that hub wireless or wired.
>>  Well, not if you intend to use the full complement of educational apps,
>> that is.  And don't even *think* about anything that uses Flash, for the
>> same reason.
>>
>> LibreOffice'll work OK.  So will Gedit or even Firefox, provided there
>> aren't a lot of screen updates.  But relatively static (as far as screen
>> updates go) apps like that are about it.  Putting LTSP on wireless is a
>> recipe for failure, given current wireless technology.
>>
>> --TP
>>
>>
>> On 04/05/2014 07:01 AM, Barry R Cisna wrote:
>>
>>> Hello All,
>>>
>>> I asked this quite some time ago and didn't get any response so just
>>> throwing this idea out again.
>>> (Maybe there is a project doing what I would like to achieve with wifi
>>> on tc's and I do not know of it,also?)
>>>
>>> Situation,and hopefully a remedy:
>>>
>>> 1) At this point it seems that a big downfall of using tc's is no
>>> bootable wifi initialization & association possibility with any
>>> surrounding AP's in the boot process.
>>>
>>> 1a) Has anyone ever thought of incorporating an "option" by adding the
>>> code in the system bios to add a parameter for wifi association to "an"
>>> access point along with password if needed .
>>>
>>> This would be very much the same scenario as when we used to add an
>>> etherboot chip to the nics on tc's back in the day (before pxe became
>>> prevelant), only using the "native" bios chip rather than an add on
>>> chip.
>>>
>>> In other words to get away from having to actually have an add
>>> on,bootable media,onto any given TC system,,such as having to hang an
>>> usb stick or slap a cd in to achieve wifi initialization  and
>>> association to a given AP.
>>>
>>> It just seems very odd with the length of time,that wifi has been a
>>> 'must have' on any network device that a TC vendor has not even come up
>>> with an spec for just this?
>>>
>>> Thanks,
>>> Barry
>>>
>>>
>>> _______________________________________________
>>> K12OSN mailing list
>>> K12OSN at redhat.com
>>> https://www.redhat.com/mailman/listinfo/k12osn
>>> For more info see <http://www.k12os.org>
>>>
>>
>> _______________________________________________
>> K12OSN mailing list
>> K12OSN at redhat.com
>> https://www.redhat.com/mailman/listinfo/k12osn
>> For more info see <http://www.k12os.org>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/k12osn/attachments/20140408/4228170b/attachment.htm>