1360259
story
Denovous writes
"WYSE is apparently producing a new Linux thin client based upon the Slackware distribution, instead of Java as originally planned. The client can be started without a network, as the OS resides in 8.5 MB of memory. Check the article out here
"
Windows Beta 3? (Score:1)
Well I thought it was ironic.
It still doesn't really compute, though ... (Score:1)
Dell talked about selling something similar (though that was 2 / 2.5 yrs ago), but it would have run Windows, because Dell hadn't wised up to Linux at that point. I don't think they ever really got made, but the concept is the same as these WYSE terminals
I asked the same question then (working for an ad agency and thereby for Dell) and still have never gotten a really good answer why it would be better to pay more for fewer / lesser components. If I can get a PII with 64MB of RAM, an 8GB hard drive, a 15" monitor and a NIC for $600 (realistic? too conservative? too hopeful?) right now, I could use the hard drive, floppy drive and CD drive for target practice at a shooting range for far less than the privelege of having someone sell me a processor / memory / NIC / monitor combo. And that counts range time.
Is there some aspect to this that I just don't get? What justifies the cost of these things? Getting hundreds of computers custom built, these days, is no big deal -- and you don't have to specify any naughty security / administrative hassles you don't want, right?
Corrections appreciated,
timothy
Re:$600-$800, huh? (Score:1)
Yes it is. (Score:1)
Good ol' Slackware (Score:1)
For once Slackware is put into the lime-light it deserves. It is IMNSHO the most effic^H^H^H^H^H compact distro out so far.
I made my own "thin client" w/ Slacky: a 486/33 with a 204MB HD. I had Slack 4.0, complete Netscape, and all tcp/ip utils running with 50MB of room for userspace and a 10MB swap. Gets ~1Mb/s thru-put off of the wcarchive through our cable modem network. Not bad for obsolete hardware!
Yes it is. (Score:1)
Re:Good ol' Slackware (Score:1)
Which would be fun... for about 50 seconds. 8^)
same with any OS (Score:1)
So it takes you back to the old, "wich is more explotable; M$ or Linux" argument.
So heres your answer: (Score:1)
The USB hardware spec is FIRM. So they can buld that into the box. Only the software needs work, and after they get it going, because the OS is flashable, they can update it.
End of Story.
There's the rub (Score:1)
Re:Flash memory? How? (Score:2)
exploits (Score:2)
It's a Cyrix MediaGX Machine (Score:1)
Anything is better than WindowsCE for thin-client workstations. If it runs linux, all the better. The largest problem of course: Citrix 3.x ICA client (no seemless windows) and no RDP support. It's a better X than NCD's cludge.
The client can be started from memory (flash), but at least the last time I talked with a Wyse rep, it does require a memory upgrade of the box to 16M of RAM. The other cost is the PCMCIA "root" filesystem - those memory cards aren't cheap.
Same thing goes for Netier. They use up to a 300Mhz Cyrix MediaGX machine as well - with harddrive/floppy/pci and other neat goodies as options. It shouldn't be hard to get one of them to run Linux either. Imagine a beowulf cluster made out of those tiny little things.
Still waiting for other neat ports (like StrongARM to the HP Joranada 820), or ANY other *normal* WindowsCE platform that would fight for market share. What would you rather be running on your palmtop?
No different than a JVM bug. (Score:1)
Same situation, really.
Re:quake over thin clients WILL work (Score:2)
First of all I don't know anything about games, I don't play them. But that doesn't mean you can't run a big game on a thin client.
You run the game on the server you connect to, not the thin client. The client only runs X. And OpenGL might be in XFree86 4.0, so if they wait for that, and used it, it would probably really rock.
My work on thin clients has shown me that there are even some preformance gains IF you configure your thin client right. The thin client's CPU and RAM only runs X, and you want a rocking video card (From my experiance doing molecular modeling and such). But, your bottle neck is bandwidth, not video or ram. All the background calculations to tell the video unit what to render are done on the server, if the server is fast, that will be fast. If the thin client has a good video subsystem, it will render the graphics fast. Since the thin client has it's own CPU, and if the video unit is fast, it has the potential to blow away a "complete system" because one box does video, and one does the application, and your not bogging down any one system by doing both on it.
The problems are, 1) you piss off other users that are on that server. 2) you frequently find the bottleneck is the data transfer rate between the server and the thin client (espically on 10baseT or less) 3) Most thin clients just don't have really rocking video subsystems.
Now, at home, I have a Linux box that I call a "server" in a generic sence, that is basically my workstation. I also have a lesser linux box (good video, good monitor, 32M RAM, MilleniumII vid card), that I run just as a thin client off the server. I have found that some applications (particularly that use a lot of CPU time for the application, AND a lot of CPU time for X) are much faster on the thin client.
Best thing to do, is just build your own. Pick up an P60 through P200, slap in a good video card and 8 to 32M ram, and just hang that puppy of a super fast server, and you'll be much happier, and probably pay less, than buying anyones "Thin Client."
Re:exploits (Score:1)
Took my idea! Well maybe... (Score:1)
Well probably not...but maybe they saw some of the notes scribbled in my notebooks. I've been working on a design for *nix based NC's for a few months. My idea is alot similar to theirs (booting from a flash ROM, more than a dumb terminal less than a PC). But I see a problem here, it's too damned expencive. I didn't see a white paper on this thing but they sure charge you up the ass for it. I could build my own box and only pay about 4-500$ each. I'm gonna keep working on my design because I have always enjoyed setting up slim/thin clients for people. I like central administration better than taking care of tons of PC's in an office.
For those of you who keep talking about fat clients with hard drives and floppies and such, remember that they are very expencive, in the short run they are cheaper, but in order to stay current and competitive with the rest of the business world you need to upgrade about every 20 months or so. If I have a thin client that will last me for 5-9 years (thats 500$ or 600 if you're bying a WYSE thin client and only once every 5-9 years excluding server upgrades which should be done every 3 years or so to keep up the speed) as opposed to 600$ every 20 months for PC's which muct be administered all the time (can we say overtime?) you start to see the TCO savings. With a thin client I need to upgrade the software on the server (probably Appliware or Star Office if it's a corporate office) which takes me a fraction of the time it takes me to upgrade dozens of PC's.
"Heat driven" means no moving parts (Score:1)
When they first started putting pentiums into laptops, my office got one. Being an electronics tech, I naturally went crazy and took the damn thing apart. It was liquid cooled! The little pipes coming off the CPU led to a heat exchanger under the keyboard.
I imagine some laptops still use this technology.
Expensive? Cheap? (Score:1)
This machines are more expensive than PCs. $839-600... umm.
Okay, that's the initial price; the real savings come because you update those terminals every 9 years instead of every 9 months (as you would do with PCs). And, since you have everything centralized in a server, it's really easier to keep the software updated and properly set up.
But I still think that's very expensive.
If I buy PCs and set them up to behave just the same way the NCs and terminals do, is there anything the terminals will do that the PCs won't? Can't I still use the same client-server design, having the PCs act just like terminals? A PC is cheaper than this terminals but can do more things... is there anything that keeps me from setting it up to do all the things the terminals (NCs) do and more?
I know, it would be a pain to do with Windows, but I can't see any problems with this centralized design using PCs with Linux (or a BSD) and XWindows instead of NCs. If I find it really useful to keep the applications centralized in a powerful server, what keeps me from doing just that and using PCs as terminals?
So, in the end, PCs can do all the things NCs do, plus a lot more... and are (in this case) cheaper.
Alejo.
Re:Yes it is. (Score:1)
That's what I was implying.
Re:Good ol' Slackware/Damn so old but had to rply (Score:1)
I meant MB as in MegaBytes and Mb/s as in Megabits
per second. I believe I was correct with my
capitalizations, perhaps not.
So, really, it'd be 50MB * 8Mb/1MB / 1Mb/sec = 400 seconds or about 6 and a half minutes of
downloading. Not too much...
...but on the other hand...
it's a 486 that would be pretty slow at doing anything
powerfull to require 20MB of HD space for bins
and data, let alone 50.
Laters
fR0993R
..Linux needs 1/2Life...
Re:Viva La Slackware! (Score:1)
Ooh yes. Though I'm sure I remember them being amber. I also remember them having the nicest keyboards I've ever used.
quake over thin clients (Score:2)
I know I always make every article relevant to quake, but in the big picture, thats what really matters.
USB? (Score:1)
"...the diminutive box is packed with ports, including Universal Serial Bus..."
I didn't think Linux USB was ready for prime time. Is WYSE jumping the gun with this announcement (i.e. vaporware) or have they made source mods that haven't been contributed back?
And speaking of which, is anyone checking up on these "embedded Linux" companies to make sure they are making the source available?
--
"Please remember that how you say something is often more important than what you say." - Rob Malda
Re:USB? (Score:1)
GOOD! (Score:1)
Thanks!!! (relevant but slightly off-topic) (Score:1)
--JT
Low maintenance turnkey solutions. (Score:1)
Time will tell... time will tell...
Not exactly a bargain (Score:1)
Re:Not exactly a bargain (Score:1)
And the only reason that regular PCs do have higher replacement rates than NCs is that they use local resources rather than remote ones, however there's no reason that a PC can't be used as an extra-functional NC.
Water cooled?? I want one. (Score:1)
Yum.. (I really have nothing more to say)
Flash memory? How? (Score:1)
I think you would need a flash module with an IDE or SCSI interface, so it just looked like another disc drive to the rest of the system. Anyone know someone who sells something like this?
I beg to differ.. (Score:1)
As it says, it's not the initial cost that's important. It's the cost savings, over the useable life of the terminal..
...and how many of those E-Machines would you expect to last 5 years?
I'm not saying I agree/disagree (with the article or you). I just think you're taking the article out of context. You're trying to compare apples to oranges.
What if it broke? (Score:1)
What? (Score:1)
"Why don't you do it if you want to play self-appointed security person?"
What on earth are you talking about? I'm not playing self-appointed anything, I'm asking a question.
--
"Please remember that how you say something is often more important than what you say." - Rob Malda
Re:Low maintenance turnkey solutions. (Score:1)
Yay! Goooooo Slackware! (Score:1)
Skip
--------------------
flifson@csdotuctdotacdotza
Re:I beg to differ.. (Score:1)
You can compare apples and oranges - they're both fruit, but one's green, and one's erm orange (its a joke!)
I do think the price is a bit high for a thin client, when you can buy a full PC for the same price.
but you miss part of the point (Score:1)
However, they do have nice things built in like a pc card reader.
They so much easier to manage than PC's, especially winblows PCs
They support a lot of protocols as well.
They probably use 1/100th the power of a normal ATX PC. The savings in costs here alone is justification for some people.
Network World never mentions Linux! (Score:1)
99 little bugs in the code, 99 bugs in the code,
fix one bug, compile it again...
Viva La Slackware! (Score:1)
I'm ranting. The point is there is a place for thin clients, we just have to drop this whole "more is more" mentality on the grounds that it's too simple. We're missing something here.
Oh well, perhaps I just miss the old days curled up in the green glow of a WYSE term hacking useless C progs for shits and giggles. Those where the days!
Re:Yay! Goooooo Slackware! (Score:1)
$600-$800, huh? (Score:1)
I've been looking into building my own linux-based thin clients for distributed processing purposes. I priced all the needed parts for a very hefty machine at less than $300. Maybe they aren't going the x86 route?
Re:What if it broke? (Score:1)
Re:Took my idea! Well maybe... (Score:1)
> clients with hard drives and floppies
> and such, remember that they are very expencive, > in the short run they are
> cheaper, but in order to stay current and
> competitive with the rest of the business
> world you need to upgrade about every 20
> months or so.
Why do I need to upgrade a pc-based X-Terminal?
I am running a HP-Vecta 386sx16 with 8MB RAM and a 100MB Harddisk, build nearly ten years ago, for five years as a X-Terminal with X and linux. It wasn`t always blindingly fast, but good enough for running (displaying?) KDE, Netscape and StarOffice lately.
I really can`t see why I should upgrade the old Vectra, it good enough. And I wont change anything about it until it crumbles to dust. Ok, I might add, that I put up another X-Terminal some weeks ago, a 486dx4-160/32MB-RAM/300MB-Harddrive, but its much more intelligent and even somewhat independent from the server.
slackterms? (Score:1)