I don't understand why they didn't make it a 3.5 hour movie, or a two-parter. There's just too much information/detail/moving-up-the-laddering in the book to compress it down to 2 hours.
I'm hoping there's an extended director's cut that pushes it out to 3 hours+.
rdesktop and NX both support video and audio as well. Over E10 lines, youtube video is watchable at 360p/480p (1024x768 virtual screen res). Going above that, though, is painful.
Personally, I'd prefer it if we started with "daylight saving time" as the baseline, and then went *ahead* an hour in the fall, and *back* an hour in the spring.
That way, it would actually be light outside in the evenings in the winter, and it would actually be dark outside in the evenings in the summer.
Who cares whether or not its light out in the morning, we're all going to be indoors with the lights on anyway (getting ready for work/school, at work/school). Let's get light when it's needed (evenings in winter) and darkness when it's needed (evenings in the summer).
It's annoying as hell to have "midnight" be when sunset occurs in the summer. And even worse that sunset occurs before 6pm in the winter.
I don't care what they replace it with, so long as there's a flag/switch/option somewhere to make the boot deterministic and identical across systems and across boots.
We run ~5000 diskless clients using Debian, booting via PXE/TFTP and mounting all filesystems via NFS.
With Debian 5, everything ran perfectly. With Debian 7, the boot is now very racy and too many things depend on the speed of the network (some services start before their dependencies are ready). We actually had to turn on verbose boot messages in order to slow things down enough for everything to boot correctly. We're testing the "don't run in parallel" flag now to see if that fixes things.
It's virtually impossible to debug a concurrent/parallel boot system, as every boot is just slightly different from the last. With the original sysvinit system, where things ran in series, one after another, it was very easy to find problems and fix things.
We don't care if the computer takes an extra 15-30 seconds to boot; we boot everything in the morning via WoL before classes start, and they are rarely booted during the day. What we do care about is being able to debug problems and make things work the same, time after time after time.
Upstart doesn't sound like it helps much in this area. Don't know about SystemD.
Except that PDF.js is crap, especially in Firefox. It's a pig, slow, and doesn't work with any of the PDFs we deal with on a daily basis (province-wide school reporting system).
What really sucks about this change is that every school in the province now has to manually click the java applet window multiple times per day to access the province-wide school information system.
There are many independent ISPs, but they all run through the infrastructure of Bell or Rogers.
Except when it runs through the infrastructure for Telus, Shaw, NorthWestTel, SaskTel, the fibre ISPs on the West Coast, CableTron (I think, whatever it is that Quebec has), the maritimes telcos, etc.
There's a hell of a lot more to the telecommunications industry in Canada than just Bell and Rogers. That may be all you poor saps in Ontaria have; but there's more to Canada than just Ontario (as much as you may not like to think so).
They're grinding the bugs into flour and combining it with whatever the local flour is (corn, wheat, whatever), thus fortifying it with iron and protein. And it's gluten-free to boot (if added to already gluten-free flour).
No mention of using 100% insect flour, though.
Will be interesting to see if their "bug-fortified" flour will be less expensive than plain flour.
Ever see a commercial for Linux on TV? Nobody's even heard of it and have no idea their Android phone runs it, let alone knows that it has more features and better ease of use. Every non-nerd I know talks about "that damned computer" when the computer's not the problem, the OS is.
Actually, yes, I have, even way up here in Canada! IBM ran a bunch of ads a few years back that trumpeted their use of Linux. They didn't really explain what Linux was, and the ads didn't really promote any products, but I do remember them, and Linux was mentioned.
The problem was that he made the same mistake that most of us geeks on here make - projection. He thought that people wanted smart phones to be little computers. Most of the commenters on here want the same thing - a little unix box that they can ssh with and such. He led MS down a path of making little pocket computers, complete with Start menus and everything.
Please! Someone bring back the pocket computer, complete with keyboard!
Someone needs to take the guts of the LG Optimus G/Nexus4, or the LG G2/Nexus5 and add a keyboard. Something like the one on the Motorola Photon Q, although with the proper symbols above the number keys. That would be the ultimate in "pocket computability".
Motorola had a chance to corner the market on these, but they locked themselves into exclusive contracts with Verizon, lagged way behind in hardware specs, and then just gave up.
I had really high hopes that the new Google-owned Motorola would release a high-quality, high-spec, leading-edge phone with a hardware keyboard. Alas, 'twas not to be.:(
FreeBSD (and Linux) were already in a "one compiler to rule them all" situation, aka GCC. At least with FreeBSD 9 there were two compilers in the base install (GCC, LLVM), and you have the option of keeping GCC in 10 if you really want.
rsync 2.x was horribly slow as it would scan the entire source looking for changed files, build a list of files, and then (once the initial scan was complete) would start to transfer data to the destination.
rsync 3.x starts building the list of changed files, and starts transferring data right away.
Unless you are changing a tonne of files between each rsync, it shouldn't take more than a few minutes using rsync 3.x to backup a 1 TB drive. Unless it's an uber-slow PoS drive, of course.:)
We use rsync to backup all our remote school servers. Very rarely does a single server backup take more than 30 minutes, and that's for 4 TB of storage using 500 GB drives (generally only a few GB of changed data). And that's across horrible ADSL links with only 0.768 Mbps upload speeds!
You're missing the point. The point is *not* can the device still be used with the latest and greatest software. The point is that you *cannot* get the older versions of software that run just fine on the device!
Very big difference!
At least with Android, old versions of apps are still available in the Play Store, and the Play Store will select the latest version supported by your OS version automatically for you. Factory reset your device, and you can still install apps on it and keep using it.
On iOS, only the latest version is available in the App Store. And if your OS version is too old to support that app, tough shit. Factory reset your device, and now you can no longer install any apps, thus making it a paperweight.
Grab a PC from the 90s, download an OS from the 90s, download apps from the 90s, and everything will work.
Grab an iPhone/iPod Touch from before 2010... and nothing.
Rogers (way up North here in Canada) ran a contest a year or so ago asking people to post their fastest LTE downloads. A lot of them were over 90 Mbps (Rogers theoretical LTE limit is 150 Mbps). Granted, that was all in the Toronto, ON area, but it was consistent.
Out here in the West, I got a consistent 50 Mbps in the Vancouver area. And co-workers get 70-odd Mbps on Bell in Kamloops.
Exactly! There's nothing worse than a dept (or school, in our case) going out and spending $15,000+ on iPads, AppleTVs, computers, etc and then calling up IT after it's arrived with rush/emergency workorders to get it to work on our network.:( And then complaining to the highest-ups that IT screwed everything up.
If you would have involved IT from the get-go, it would go a lot smoother, and we could make recommendations for equipment that will work with the existing setup, allocate tech time to prep everything, and have it running smoothly right away. But, no, they try to do an end-run around IT, get a bunch of crap that breaks everything, and then wonder why it takes so long to fix everything.
I like having a forward/back dropdown so that I can see where I am in my back/forward history and select how far forward or back to go next. I had to install the addon Backward/Forward History Dropdown 0.2.4 to get this functionality back.
Why do you need an extension for that? Just right-click the back arrow, and the list appears. Right-click the front arrow, and the list appears.
It tells you when it's low, but it doesn't tell you how far you can go on that amount of fuel. It's very easy to do a calculation in your head based on MPG to figure out, and next to impossible to do based on L/100Km.
"If you think you care so much about metric, why can't you tell me how many liters per 100 km your car takes? Its *your* car... no one is stopping you."
Because L/100Km is the stupised metric ever invented by man!
Which is easier:
- take the size of your tank in L, multiply by "Km/L" rating of the car, and get how far you can drive on a tank of gas.
(or, for you Yanks, take the size of your tank in gal, multiple by "miles/gal" rating of the car, and get how far you can drive on a tank of gas), or
- take the size of your tank in L, divide by "L" portion of the "L/100Km" rating, multiply by 100, and eventually figure out how many units of 100 Km you can drive on a tank of gas, although you'll most likely just wing it after banging your head against the steering wheel
I really don't care how many litre it takes to drive 100 Km -- I want to know how far I can drive on a full tank of gas!
Slashdot Mirror
I don't understand why they didn't make it a 3.5 hour movie, or a two-parter. There's just too much information/detail/moving-up-the-laddering in the book to compress it down to 2 hours.
I'm hoping there's an extended director's cut that pushes it out to 3 hours+.
rdesktop and NX both support video and audio as well. Over E10 lines, youtube video is watchable at 360p/480p (1024x768 virtual screen res). Going above that, though, is painful.
Personally, I'd prefer it if we started with "daylight saving time" as the baseline, and then went *ahead* an hour in the fall, and *back* an hour in the spring.
That way, it would actually be light outside in the evenings in the winter, and it would actually be dark outside in the evenings in the summer.
Who cares whether or not its light out in the morning, we're all going to be indoors with the lights on anyway (getting ready for work/school, at work/school). Let's get light when it's needed (evenings in winter) and darkness when it's needed (evenings in the summer).
It's annoying as hell to have "midnight" be when sunset occurs in the summer. And even worse that sunset occurs before 6pm in the winter.
I don't care what they replace it with, so long as there's a flag/switch/option somewhere to make the boot deterministic and identical across systems and across boots.
We run ~5000 diskless clients using Debian, booting via PXE/TFTP and mounting all filesystems via NFS.
With Debian 5, everything ran perfectly. With Debian 7, the boot is now very racy and too many things depend on the speed of the network (some services start before their dependencies are ready). We actually had to turn on verbose boot messages in order to slow things down enough for everything to boot correctly. We're testing the "don't run in parallel" flag now to see if that fixes things.
It's virtually impossible to debug a concurrent/parallel boot system, as every boot is just slightly different from the last. With the original sysvinit system, where things ran in series, one after another, it was very easy to find problems and fix things.
We don't care if the computer takes an extra 15-30 seconds to boot; we boot everything in the morning via WoL before classes start, and they are rarely booted during the day. What we do care about is being able to debug problems and make things work the same, time after time after time.
Upstart doesn't sound like it helps much in this area. Don't know about SystemD.
Why not just pick up a pack of DVD labels, print onto them from any printer (it's just label paper) and then stick it on the DVD?
Except that PDF.js is crap, especially in Firefox. It's a pig, slow, and doesn't work with any of the PDFs we deal with on a daily basis (province-wide school reporting system).
What really sucks about this change is that every school in the province now has to manually click the java applet window multiple times per day to access the province-wide school information system.
Except when it runs through the infrastructure for Telus, Shaw, NorthWestTel, SaskTel, the fibre ISPs on the West Coast, CableTron (I think, whatever it is that Quebec has), the maritimes telcos, etc. There's a hell of a lot more to the telecommunications industry in Canada than just Bell and Rogers. That may be all you poor saps in Ontaria have; but there's more to Canada than just Ontario (as much as you may not like to think so).
Well, not quite. "brainwashing" has a specific meaning, and is very different from the act of "brain washing" which is what this article is about.
One is actually washing the brain, the other is warping ones thinking internally.
Draft beer == giant kegs of beer connected via hoses to the taps at the bar, poured into pint glasses when ordered.
As opposed to bottled or canned beer.
That's been done, although it was African killer bees genetically engineered to take over the minds of those they sting. Wasn't completely horrible.
http://www.trunews.com/flour-made-insects-wins-1m-mcgill-team/
They're grinding the bugs into flour and combining it with whatever the local flour is (corn, wheat, whatever), thus fortifying it with iron and protein. And it's gluten-free to boot (if added to already gluten-free flour).
No mention of using 100% insect flour, though.
Will be interesting to see if their "bug-fortified" flour will be less expensive than plain flour.
Actually, yes, I have, even way up here in Canada! IBM ran a bunch of ads a few years back that trumpeted their use of Linux. They didn't really explain what Linux was, and the ads didn't really promote any products, but I do remember them, and Linux was mentioned.
Please! Someone bring back the pocket computer, complete with keyboard!
Someone needs to take the guts of the LG Optimus G/Nexus4, or the LG G2/Nexus5 and add a keyboard. Something like the one on the Motorola Photon Q, although with the proper symbols above the number keys. That would be the ultimate in "pocket computability".
Motorola had a chance to corner the market on these, but they locked themselves into exclusive contracts with Verizon, lagged way behind in hardware specs, and then just gave up.
I had really high hopes that the new Google-owned Motorola would release a high-quality, high-spec, leading-edge phone with a hardware keyboard. Alas, 'twas not to be. :(
FreeBSD (and Linux) were already in a "one compiler to rule them all" situation, aka GCC. At least with FreeBSD 9 there were two compilers in the base install (GCC, LLVM), and you have the option of keeping GCC in 10 if you really want.
IOW, you're complaint is baseless and backwards.
Since when does Firefox use kwallet? Never had on any of my KDE installs, whether FreeBSD or Linux, binary package or compiled from source.
You're holding it wrong. ;)
rsync 2.x was horribly slow as it would scan the entire source looking for changed files, build a list of files, and then (once the initial scan was complete) would start to transfer data to the destination.
rsync 3.x starts building the list of changed files, and starts transferring data right away.
Unless you are changing a tonne of files between each rsync, it shouldn't take more than a few minutes using rsync 3.x to backup a 1 TB drive. Unless it's an uber-slow PoS drive, of course. :)
We use rsync to backup all our remote school servers. Very rarely does a single server backup take more than 30 minutes, and that's for 4 TB of storage using 500 GB drives (generally only a few GB of changed data). And that's across horrible ADSL links with only 0.768 Mbps upload speeds!
Going disk-to-disk should be even faster.
Hepatitis is a virus, not a bacteria. We're discussing bacteria here. Viral infections are a whole other ball of wax.
You're missing the point. The point is *not* can the device still be used with the latest and greatest software. The point is that you *cannot* get the older versions of software that run just fine on the device!
Very big difference!
At least with Android, old versions of apps are still available in the Play Store, and the Play Store will select the latest version supported by your OS version automatically for you. Factory reset your device, and you can still install apps on it and keep using it.
On iOS, only the latest version is available in the App Store. And if your OS version is too old to support that app, tough shit. Factory reset your device, and now you can no longer install any apps, thus making it a paperweight.
Grab a PC from the 90s, download an OS from the 90s, download apps from the 90s, and everything will work.
Grab an iPhone/iPod Touch from before 2010 ... and nothing.
Do you see the difference yet?
So? Being exposed to a variety of bacteria is actually GOOD for the immune system. How can you fight off what you've never been exposed to?
This whole germ-a-phobia is what's making the world sick!
Rogers (way up North here in Canada) ran a contest a year or so ago asking people to post their fastest LTE downloads. A lot of them were over 90 Mbps (Rogers theoretical LTE limit is 150 Mbps). Granted, that was all in the Toronto, ON area, but it was consistent.
Out here in the West, I got a consistent 50 Mbps in the Vancouver area. And co-workers get 70-odd Mbps on Bell in Kamloops.
Exactly! There's nothing worse than a dept (or school, in our case) going out and spending $15,000+ on iPads, AppleTVs, computers, etc and then calling up IT after it's arrived with rush/emergency workorders to get it to work on our network. :( And then complaining to the highest-ups that IT screwed everything up.
If you would have involved IT from the get-go, it would go a lot smoother, and we could make recommendations for equipment that will work with the existing setup, allocate tech time to prep everything, and have it running smoothly right away. But, no, they try to do an end-run around IT, get a bunch of crap that breaks everything, and then wonder why it takes so long to fix everything.
Like ... ?
You can't make a statement like "Chrome also does a LOT of stuff wrong" without listing at least one item.
I like having a forward/back dropdown so that I can see where I am in my back/forward history and select how far forward or back to go next. I had to install the addon Backward/Forward History Dropdown 0.2.4 to get this functionality back.
Why do you need an extension for that? Just right-click the back arrow, and the list appears. Right-click the front arrow, and the list appears.
It tells you when it's low, but it doesn't tell you how far you can go on that amount of fuel. It's very easy to do a calculation in your head based on MPG to figure out, and next to impossible to do based on L/100Km.
"If you think you care so much about metric, why can't you tell me how many liters per 100 km your car takes? Its *your* car... no one is stopping you."
Because L/100Km is the stupised metric ever invented by man!
Which is easier:
- take the size of your tank in L, multiply by "Km/L" rating of the car, and get how far you can drive on a tank of gas.
(or, for you Yanks, take the size of your tank in gal, multiple by "miles/gal" rating of the car, and get how far you can drive on a tank of gas), or
- take the size of your tank in L, divide by "L" portion of the "L/100Km" rating, multiply by 100, and eventually figure out how many units of 100 Km you can drive on a tank of gas, although you'll most likely just wing it after banging your head against the steering wheel
I really don't care how many litre it takes to drive 100 Km -- I want to know how far I can drive on a full tank of gas!