You can bundle up little kids pretty effectively. The very old is the real problem--the ideal solution would seem to be some form of casual on-demand travel. Sized between a minivan and a passenger van, cheaper than calling a taxi because it would cover a given area and just pick up people needing a ride from the shelter to their dwelling.
Everything I've heard says that talking on a phone (hands free or not) is more distracting than other things because the person on the other end is actively demanding your attention and can't tell what's going on in the environment around the car.
You can tune out the radio or music when you need attention on the road. Passengers physically in the car can see that the driver is busy driving and wait until things calm down again before continuing the conversation.
Of course there are people that can use communications technology responsibly while driving--but most people can't. I suppose one option would be to cut all insurance coverage if there was a phone active in the vehicle at the time of an accident...
University is for learning. The idea is that you open the textbook on your own to gain a deeper understanding of the topic than you had time to cover in class.
I'm a telecommuter. Have been for quite a few years. The work machine belongs to my company. I did splurge on a nicer screen and keyboard than they provided though.
If you're worried about it scanning your network, you need a better home router.
Both of them work fine, I run Fedora on my work laptop with the original Win7 install running in a VM inside vmplayer. The corporate IT folks can even log in to my Win7 VM to do stuff with no idea that it's a VM.
I got a touchpad on firesale because I wasn't willing to spend the current going rate on a tablet. I still think an iPad is overpriced for what you get. The fact that others haven't been able to do it for less doesn't change my perception.
If the touchpad hadn't gone on sale, I probably still wouldn't have a tablet.
Someone with tech ability programs it with things like "watch tv", "watch bluray", "listen to radio", "watch laptop". The person using it just hits the appropriate activity on the touchscreen and it starts up the right pieces of gear and configures all the physical buttons on the remote appropriately. As long as you use that remote for everything then you're good.
I got a refurb for half price, works really well. We no longer need to deal with six separate remotes.
I'm currently working primarily in C and shell scripting. I do mostly linux kernel and low-level OS platform development and support. There's no shortage of work.
Fortran is great for number crunching...the design of the language makes it easy to optimize. C/C++ compilers have improved to the point where you could probably get equivalent performance, but it's unlikely you could do much better without using the extended SIMD instruction sets.
As an end-user there are only a few things you can do:
1) Reduce the outgoing tcp queue size. 2) Reduce the tx ring buffer size in the network device driver 3) Set your router's upstream quality-of-service settings to throttle your upstream data transmission rate to just less than your upstream bandwidth.
Alternately, if you only have one heavy user of upstream bandwidth you could do something like what is described at "http://wanners.net:8000/blog/2011/05/zapping-upload-bufferbloat-with-one-command/". Basically throttling the upstream bandwidth directly on the machine in question rather than on the router.
Each hop has its own buffer. Endpoints can fix their own buffers, but they can't do anything about buffering in the next hop. If something changes in the network to reduce the available bandwidth, the ideal behaviour is for packets to start getting dropped right away so that the originator gets notified of the drop and can slow itself down to compensate.
If some device in the core network just buffers up seconds worth of packets instead of droping them it destroys the ability of the sender to adapt to the changing conditions.
Someone calculated that for Great Britain to use wind power they'd need to convert half the lakes in the country to energy storage--pumping water uphill with wind power then turning turbines when the wind died down. They also get so little sun that it would be more effective for them to lease land in the African desert and transmit the power back home.
Apparently we could for tens of billions constantly pump sulfur dioxide into the upper atmosphere. This would reflect sunlight and lower the earth's temperature.
It's so much cheaper than throwing trillions of dollars at fusion that I am nearly certain it's what we'll end up doing.
If everyone lived with those principles, we'd basically be robbing resources from our kids. By those standards there's no incentive to think long-term.
As mentioned earlier, things like caching DNS server, QoS, and IPsec are generally done in software, as are things like making USB-connected external drives available as network storage. Often bridging between wired and wireless is done in software as well--my wndr3700 is way, way faster connecting between my wired and wireless networks than my old D-Link was.
I've been using "ip" for at least 8 years now...it actually allows you to assign multiple IP addresses to a single network device. I don't know how anyone lives with ifconfig anymore.
At home depot it means that they'll meet (or beat) a lower price from another store on an identical item.
You can bundle up little kids pretty effectively. The very old is the real problem--the ideal solution would seem to be some form of casual on-demand travel. Sized between a minivan and a passenger van, cheaper than calling a taxi because it would cover a given area and just pick up people needing a ride from the shelter to their dwelling.
Everything I've heard says that talking on a phone (hands free or not) is more distracting than other things because the person on the other end is actively demanding your attention and can't tell what's going on in the environment around the car.
You can tune out the radio or music when you need attention on the road. Passengers physically in the car can see that the driver is busy driving and wait until things calm down again before continuing the conversation.
Of course there are people that can use communications technology responsibly while driving--but most people can't. I suppose one option would be to cut all insurance coverage if there was a phone active in the vehicle at the time of an accident...
It boggles my mind that this thing didn't self-destruct for exactly this reason.
University is for learning. The idea is that you open the textbook on your own to gain a deeper understanding of the topic than you had time to cover in class.
I'm a telecommuter. Have been for quite a few years. The work machine belongs to my company. I did splurge on a nicer screen and keyboard than they provided though.
If you're worried about it scanning your network, you need a better home router.
Both of them work fine, I run Fedora on my work laptop with the original Win7 install running in a VM inside vmplayer. The corporate IT folks can even log in to my Win7 VM to do stuff with no idea that it's a VM.
I got a touchpad on firesale because I wasn't willing to spend the current going rate on a tablet. I still think an iPad is overpriced for what you get. The fact that others haven't been able to do it for less doesn't change my perception.
If the touchpad hadn't gone on sale, I probably still wouldn't have a tablet.
First, select two page view: view->page display->two up
Then, change your full screen preferences: edit->preferences->full screen->fill screen with one page at a time (uncheck)
Now when you go to full screen mode you'll get two pages.
Someone with tech ability programs it with things like "watch tv", "watch bluray", "listen to radio", "watch laptop". The person using it just hits the appropriate activity on the touchscreen and it starts up the right pieces of gear and configures all the physical buttons on the remote appropriately. As long as you use that remote for everything then you're good.
I got a refurb for half price, works really well. We no longer need to deal with six separate remotes.
And soon it will be down to two.
I'm currently working primarily in C and shell scripting. I do mostly linux kernel and low-level OS platform development and support. There's no shortage of work.
Fortran is great for number crunching...the design of the language makes it easy to optimize. C/C++ compilers have improved to the point where you could probably get equivalent performance, but it's unlikely you could do much better without using the extended SIMD instruction sets.
As an end-user there are only a few things you can do:
1) Reduce the outgoing tcp queue size.
2) Reduce the tx ring buffer size in the network device driver
3) Set your router's upstream quality-of-service settings to throttle your upstream data transmission rate to just less than your upstream bandwidth.
Alternately, if you only have one heavy user of upstream bandwidth you could do something like what is described at "http://wanners.net:8000/blog/2011/05/zapping-upload-bufferbloat-with-one-command/". Basically throttling the upstream bandwidth directly on the machine in question rather than on the router.
Each hop has its own buffer. Endpoints can fix their own buffers, but they can't do anything about buffering in the next hop. If something changes in the network to reduce the available bandwidth, the ideal behaviour is for packets to start getting dropped right away so that the originator gets notified of the drop and can slow itself down to compensate.
If some device in the core network just buffers up seconds worth of packets instead of droping them it destroys the ability of the sender to adapt to the changing conditions.
Feel free to try it out yourself...I have and the problem is real.
Someone calculated that for Great Britain to use wind power they'd need to convert half the lakes in the country to energy storage--pumping water uphill with wind power then turning turbines when the wind died down. They also get so little sun that it would be more effective for them to lease land in the African desert and transmit the power back home.
Apparently we could for tens of billions constantly pump sulfur dioxide into the upper atmosphere. This would reflect sunlight and lower the earth's temperature.
It's so much cheaper than throwing trillions of dollars at fusion that I am nearly certain it's what we'll end up doing.
If everyone lived with those principles, we'd basically be robbing resources from our kids. By those standards there's no incentive to think long-term.
I've seen reasonable estimates of the max long-term sustainable human population at something like 300 million people, certainly under a billion.
If we keep going like we are, we're going to hit catastrophic population die-off.
It runs fine in firefox on linux
Person of Interest
Terra Nova
Lost Girl
Grimm
As mentioned earlier, things like caching DNS server, QoS, and IPsec are generally done in software, as are things like making USB-connected external drives available as network storage. Often bridging between wired and wireless is done in software as well--my wndr3700 is way, way faster connecting between my wired and wireless networks than my old D-Link was.
If you have write access to the log file you can delete/change the entry you care about and then re-hash all the entries after that.
I've been using "ip" for at least 8 years now...it actually allows you to assign multiple IP addresses to a single network device. I don't know how anyone lives with ifconfig anymore.