Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:HTTPS and Interstitials. (Score 3, Informative) 546

It really shouldn't work.

The plaintext version of slashdot uses http 301 (moved permanently), which causes the browser to simply skip connecting to the plaintext version the next time and connect directly to the redirected https URL.
Google.com however, uses http 302 (moved), which does not cause this caching to occur, and will work just fine for this purpose.

If Slashdot had used the "Strict-Transport-Security" header as well, your browser should categorically refuse to connect to the plaintext version (after your first connection) until the expiry date has been reached (usually quite a few weeks into the future)

If you can use http://slashdot.org/ the same way you use http://google.com/ your browser has security issues.

Comment Re:Just goes to show. . . (Score 1) 256

Yes, you could write a stopwatch app which runs on the bare metal, without relying on anything but the hardware (OK, and the part of the BIOS which starts the bootloader, unless you want to re-flash the BIOS). However that would be more complicated than you think. You'd have to initialize all the hardware yourself and handle everything on the lowest level.

The BIOS initializes all that is needed for a text-mode stopwatch. It would really not be hard to write in asm.

Doing a GUI stopwatch on the bare metal would be no more complicated than doing a text stopwatch on the bare metal ("CLI" wouldn't exactly apply then, because without some operating system, there would not be a command line to begin with, unless you'd take the unnecessary complication of additionally writing a CLI to run your stopwatch from). Just the data structures to be copied into video RAM would be a bit bigger. But then, the mouse handling code would probably be much simpler than the keyboard handling code you'd need for the text version.

While USB keyboards work in compatibility mode - requiring no USB driver, the same is not true for a mouse. That would require USB drivers. That in it self would be far more complex than writing a text-mode stopwatch.


Submission + - XBMC Hardware-accelerated Android-build available

repvik writes: Yesterday, Ricardo Cerqueira posted this on Google+:
"As I mentioned in a comment for another post, +XBMC is currently undergoing extensive work for native video acceleration in Android. I was about to post my own build (which works on the Nexus Q's OMAP4), when I noticed they have just posted a build based on the same patchset (it's theirs, after all :) Great job, guys!)

So... http://mirrors.xbmc.org/test-builds/android/xbmc-20130118-d2c78f5-android-hwaccel-armeabi-v7a.apk . I've tested this build on Qualcomm S4, OMAP4, Exynos4, and Tegra3, all of them on CM10.1, and got accelerated video on all. Go get it :)"

I've tested it, and it looks great!

Comment Re:SSD Drives (Score 3, Informative) 140

Bare NAND is presented as a block device. NAND SSDs are also presented as block devices. That does not imply that they are equal. SSDs have a controller that does remapping on the fly, in many cases on the fly compression, bad block handlling and much more. Bare NAND does not have that layer. That is why the ACs comment should be moderated informative, and you should be moderated "plain wrong".

Slashdot Top Deals

If you had better tools, you could more effectively demonstrate your total incompetence.