Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×

Submission + - Nmap team releases 5 gigapixel favicon map 1

iago-vL writes: From the creators of Nmap comes the largest survey of this its kind ever performed: the favicon.ico files of over a million Web sites were scanned, compiled, and sorted to create a 5 gigapixel image, blowing their 2010 survey out of the water! It's searchable, zoomable, and incredibly fun to play with! Can you find Slashdot without cheating? (Hint: it's near Facebook)

Submission + - Wireshark switches to Qt (wireshark.org)

An anonymous reader writes: Beginning with Wireshark 1.11.0 the project has switched its user interface library from GTK+ to Qt. "Both libraries make it easy for developers write applications that will run on different platforms without having to rewrite a lot of code. GTK+ has had a huge impact on the way Wireshark looks and feels and on its popularity but it doesn’t cover our supported platforms as effectively as it should and the situation is getting worse as time goes on."

Comment Re:No plans for LLVM (Score 2) 102

Because GCC doesn't have a static analyzer (you do analyze your code, right?) LLVM's analyzer (Clang's scan-build) is very good. Visual C++'s analyzer was crap a few releases ago but even it is getting better. I like GCC but it has a lot of catching up to do in this regard. And no, "-Wall" isn't nearly the same.

Linux

Submission + - ntpd timebomb on modern linuxes (serverfault.com)

Bronster writes: "On recent linux kernels, ntpd prepares the kernel for the upcoming insertion of a leapsecond — which under some circumstances can trigger a livelock. At least Redhat and Debian users are confirmed to be at risk on busy servers."
Bug

Submission + - Leapsecond is here! Are your systems ready or going to crash? (redhat.com) 1

Tmack writes: The last time we had a leapsecond, sysadmins were taken a bit by surprise when a random smattering of systems locked up (including Slashdot itself) due to a kernel bug causing a race condition specific to the way leapseconds are handled/notified by ntp. The vulnerable kernel versions (prior to 2.6.29) are still common amongst older versions of popular distributions (Debian Lenny, RHEL/Centos 5) and embeded/black-box style appliances (Switches, load balancers, spam filters/email gateways, NAS devices, etc). Several vendors have released patches and bulletins about the possibility of a repeat of last time. Are you/your team/company ready? Are you upgraded or are you going to bypass this by simply turning off NTP for the weekend?

Slashdot Top Deals

Ya'll hear about the geometer who went to the beach to catch some rays and became a tangent ?

Working...