i recently switched from sprint to ting and it was painless. kept my two smartphones, ported the numbers, and my monthly bill dropped from $135/month to $33/month (for two lines). the customer account section of their website is a model of simplicity and effectiveness. the only downside is that it's not unlimited - the more you use the more you pay, especially for data. but texts are cheap and if you're like us and have wifi most of the time it's a killer deal. HIGHLY recommended.
I've set up a thin client network in a lab environment and have learned a few things about how to make it work:
1. Start off with the K12ltsp.org CDs - use the installation as a reference for setting up DHCP, TFTP, and other services on your own later.
2. Once you're comfortable with that, try a regular distro with the LTSP packages. They really are easy to install and require only minor tweaking to run properly.
3. I've had terrific success with old Dell Optiplex desktops, you can buy them on eBay all day long for under $100. The ones I use are P166 w/ 32MB ram, 2MB onboard video (enough for 16 bit 1024x768) and 3com 905 or Intel Pro/100 network cards. Unplug the HD and CDROM, you don't need them and the PC is virtually silent without them. Make a boot floppy from the rom-o-matic website and away you go.
4. Don't skimp and use 10Mb networking, spend a few extra bucks and get 100Mb switches. Not for the throughput, but rather the reduced latency. Not a huge difference, but when you figure that every pixel update, every mouse twitch, and every keystroke has to traverse the network the latency is noticable.
Once you see how incredibly easy a thin client network is to setup and manage, you'll never go back to fat workstations. Have fun!
I was in England a year or two ago, working in Romford just outside the M25 around London. Driving through a village called Brentwood one day, I spotted a sign outside a little pub called the Horse and Groom. Naturally, I had to stop inside and inquire (and enjoy a pint or two of bitter). Turns out, according to one of the locals, that Adams grew up in or around Brentwood, and therefore used the pub name Horse and Groom in the first book. Surprisingly, only a few patrons that day even knew who Douglas Adams was, despite being what I would consider to be a local celebrity. Someone even said to me that if I enjoyed HGTTG I would also appreciate Red Dwarf, which was quite popular in Britian but never caught on big in the States (and I had never heard of it before). How right they were...
So on behalf of the crowd at the Horse and Groom, so long Douglas, we'll all miss you.
bravo, well said. i'll join you in a moment of silence for the men and women who have, and still do, put their lives on the line in the name of science and discovery every day.
Instead of focusing so much on making faster and faster processors, is anyone giving attention to developing code that isn't so bloated and inefficient it requires such massive hardware? Not nearly as glamorous, but at the rate things are going pretty soon I'll need a 5 GHz CPU and 2 gigs of RAM just to run my damn coffee machine.
Starting about six weeks ago, I could no longer send mail from any of my Yahoo accounts using Outlook Express 5 (admit it, if you have to use Windows, OE5 is a good client) and my home dial-up Earthlink account. I could send, however, using an identical setup at work, where we have a dedicated frame connection. Other freinds of mine have reported similar problems. It seems that Yahoo SMTP servers will not accept connections from certain blocks of IP addresses (anyone got a line on why this might be?) After changing the outgoing mail server setting from SMTP.MAIL.YAHOO.COM to MAIL.EARTHLINK.NET, everything works fine. Worth a try for anyone struggling with Yahoo email.
Slashdot Mirror
i recently switched from sprint to ting and it was painless. kept my two smartphones, ported the numbers, and my monthly bill dropped from $135/month to $33/month (for two lines). the customer account section of their website is a model of simplicity and effectiveness. the only downside is that it's not unlimited - the more you use the more you pay, especially for data. but texts are cheap and if you're like us and have wifi most of the time it's a killer deal. HIGHLY recommended.
007: free radicals?
m: yes, toxins that destroy the body and brain. caused by eating too much red meat and white bread, and too many dry martinis.
007: (ponders) then i shall cut out the white bread sir.
"'We've stayed very pure,' Mr. Negroponte said."
i'v said it before and i'll say it again, you can't get a little bit pregnant.
you can't get a little bit pregnant
you manage your servers using vnc? that's a pity. i manage all of mine using pssh on my treo 650 :)
i love the fact that the slideshow presentation is available in Open Office format (.sxi)
sure would love to see more of this in the real world.
I've set up a thin client network in a lab environment and have learned a few things about how to make it work:
1. Start off with the K12ltsp.org CDs - use the installation as a reference for setting up DHCP, TFTP, and other services on your own later.
2. Once you're comfortable with that, try a regular distro with the LTSP packages. They really are easy to install and require only minor tweaking to run properly.
3. I've had terrific success with old Dell Optiplex desktops, you can buy them on eBay all day long for under $100. The ones I use are P166 w/ 32MB ram, 2MB onboard video (enough for 16 bit 1024x768) and 3com 905 or Intel Pro/100 network cards. Unplug the HD and CDROM, you don't need them and the PC is virtually silent without them. Make a boot floppy from the rom-o-matic website and away you go.
4. Don't skimp and use 10Mb networking, spend a few extra bucks and get 100Mb switches. Not for the throughput, but rather the reduced latency. Not a huge difference, but when you figure that every pixel update, every mouse twitch, and every keystroke has to traverse the network the latency is noticable.
Once you see how incredibly easy a thin client network is to setup and manage, you'll never go back to fat workstations. Have fun!
well, with your bad back bruce you shouldn't be throwing anybody...
isn't there some sort of authentication strategy that says three types of keys exist:
1. sonething you know (password)
2. something you have (keycard, etc)
3. something you are (fingerprint, retina)
and that any serious authentication method should use at least two of the three?
I was in England a year or two ago, working in Romford just outside the M25 around London. Driving through a village called Brentwood one day, I spotted a sign outside a little pub called the Horse and Groom. Naturally, I had to stop inside and inquire (and enjoy a pint or two of bitter). Turns out, according to one of the locals, that Adams grew up in or around Brentwood, and therefore used the pub name Horse and Groom in the first book. Surprisingly, only a few patrons that day even knew who Douglas Adams was, despite being what I would consider to be a local celebrity. Someone even said to me that if I enjoyed HGTTG I would also appreciate Red Dwarf, which was quite popular in Britian but never caught on big in the States (and I had never heard of it before). How right they were... So on behalf of the crowd at the Horse and Groom, so long Douglas, we'll all miss you.
that is easily the funniest thing i've ever read on /.
good one!
bravo, well said. i'll join you in a moment of silence for the men and women who have, and still do, put their lives on the line in the name of science and discovery every day.
Instead of focusing so much on making faster and faster processors, is anyone giving attention to developing code that isn't so bloated and inefficient it requires such massive hardware? Not nearly as glamorous, but at the rate things are going pretty soon I'll need a 5 GHz CPU and 2 gigs of RAM just to run my damn coffee machine.
Starting about six weeks ago, I could no longer send mail from any of my Yahoo accounts using Outlook Express 5 (admit it, if you have to use Windows, OE5 is a good client) and my home dial-up Earthlink account. I could send, however, using an identical setup at work, where we have a dedicated frame connection. Other freinds of mine have reported similar problems. It seems that Yahoo SMTP servers will not accept connections from certain blocks of IP addresses (anyone got a line on why this might be?) After changing the outgoing mail server setting from SMTP.MAIL.YAHOO.COM to MAIL.EARTHLINK.NET, everything works fine. Worth a try for anyone struggling with Yahoo email.