Forgot your password?
typodupeerror

+ - Once Slashdot beta has been foisted upon me, what site should I use instead? 2

Submitted by somenickname
somenickname (1270442) writes "As a long time Slashdot reader, I'm wondering what website to transition to once the beta goes live. The new beta interface seems very well suited to tablets/phones but, it ignores the fact that the user base is, as one would expect, nerds sitting in front of very large LCD monitors and wasting their employers time. It's entirely possible that the browser ID information gathered by the site has indicated that they get far more hits on mobile devices where the new interface is reasonable but, I feel that no one has analyzed the browser ID (and screen resolution) against comments modded +5. I think you will find that most +5 comments are coming from devices (real fucking computers) that the new interface does not support well. Without an interface that invites the kind of users that post +5 comments, Slashdot is just a ho-hum news aggregation site that allows comments. So, my question is, once the beta is the default, where should Slashdot users go to?"
Books

Book Review: Digital Archaeology: the Art and Science of Digital Forensics 14

Posted by samzenpus
from the read-all-about-it dept.
benrothke writes "The book Digital Archaeology: The Art and Science of Digital Forensics starts as yet another text on the topic of digital forensics. But by the time you get to chapter 3, you can truly appreciate how much knowledge author Michael Graves imparts. Archaeology is defined as the study of human activity in the past, primarily through the recovery and analysis of the material culture and environmental data that they have left behind, which includes artifacts, architecture, biofacts and cultural landscapes. The author uses archeology and its associated metaphors as a pervasive theme throughout the book. While most archeology projects require shovels and pickaxes; digital archeology requires an entirely different set of tools and technologies. The materials are not in the ground, rather on hard drives, SD cards, smartphones and other types of digital media." Keep reading for the rest of Ben's review.

Comment: Re:I'm amazed... (Score 1) 1737

by Hawke (#44274621) Attached to: George Zimmerman Acquitted In Death of Trayvon Martin

Which may be why Zimmerman's defense didn't invoke SYG.

IMHO, there was not proof beyond a reasonable double that Zimmerman was on top. It's quite possible he was on the bottom, and was legitimately scared for his life. From what I know from the trial, I don't think I'd have convicted either.

On the other hand, from what I know from the trial, I also wouldn't have convicted TM if TM had managed to kill Zimmerman. It's a crappy situation for everyone.

Comment: Re:Silver Bullet (Score 1) 172

by Hawke (#43998681) Attached to: SSDs: The New King of the Data Center?

You're assuming that the drive failures are independent. His point is that they might not be: the common cause may be write cycles.

Let's say that a drive under your write patterns will last 9 months. (Bad wear leveling algo, combined with very re-write heavy data structures?). You put 5 of them in a raid 5 enclosure, all brand new drives. 9 months later, they all fail within minutes of each other. Whoops, lost your data.

If they fail for different reasons, you're more likely to be safe. If they all fail from wearing out the ability to erase cells, you're more likely to be hosed, until you've swapped out enough to randomize the write count./p?

Comment: Re:Virtual books are retarded. (Score 4, Insightful) 108

by Hawke (#42095299) Attached to: O'Reilly Discounts Every eBook By 50%
You posted this in reply to an O'Reilly promotion. You know, the one company who's ebook format is "unencrypted PDF". That one. The one company that CAN NOT take your book away. Where the book won't change unless you want it to. Where you can keep it on your own HD for as long as you can and no one will even know.

That company.

Comment: Re:I think that's all college students (Score 1) 823

by Hawke (#41767673) Attached to: Ask Slashdot: Rectifying Nerd Arrogance?

"Did you put the disk in the DVD drive?"

Excuse me for being a horrible pedant, but I would also get confused if you told me to put a disk into the DVD drive. That drive takes discs... the ones that are visibly circular and have no case.

Ahem. Back to your point, and sorry for making the point of the original article.

Comment: Mine went Read-Only (Score 1) 510

by Hawke (#41671395) Attached to: Ask Slashdot: How Do SSDs Die?

I had a small OCZ SSD of some variety in my foo-server (which mounted the NAS for all the important changing data). One day I realized that / had gone ready-only days earlier. Console showed a write failure to the journal (ext3).

Rebooted it, and it worked for ~1 day. Reformatted (managed system, I have no idea if there was data corruption. Didn't seem to be any, but I didn't look for any) and it worked for around 1 week. At that point I gave up and replaced it. It had lasted for just over a year when it failed.

The two Intel SSDs I've bought have not failed yet, nor has another OCZ brand SSD (Vertex3, fwiw).

Comment: Re:Mod parent up. (Score 1) 1154

by Hawke (#41268033) Attached to: Ask Slashdot: How Would You Fix the Linux Desktop?
I wrote an interface to OSS back in ... 98? Something like that. It was dead simple to use: configure device, write sound data. Done.

Handling underflow/overflow was also so easy (write ahead as much as the device will take. Use an IOCTL when you need to stop... because the buffer won't run out for several seconds) that it amazes me that buffer sizes apparently have to be configurable in current sound-using applications. Crazy.

Comment: Re:It's not broken. (Score 5, Insightful) 1154

by Hawke (#41264687) Attached to: Ask Slashdot: How Would You Fix the Linux Desktop?
(Hey man, long time no see)

This. Like Enry, I've been using linux since pre-1.0. Unlike him, I've lost my desire to constantly upgrade versions.

The "KDE/Gnome are both Windows 95/XP look-alikes" era was probably the top of the usability as far as I can tell. Newer KDE never got back to the same level of usability, and newer gnome makes me turn giant and green. (Look, my monitor is not 1024x768. Stop making UI decisions that only work on tiny-ass monitors.)

And unlike most here, I think that is reasonable. Normal people won't use Linux until the app they want is only available on it... and that won't happen until the developer likes it enough to run it as their default platform. So YES, make it nice for neckbeards first. And once it's (back to being) nice for the neckbeards, THEN go ahead and try and make it nice for your grandmother too... but DO NOT break it for the neckbeards.

And then you declare the basic desktop DONE for 3 years or so, and work on apps. Maintain the desktop in terms of bug fixes, and internal reworks and anything else you need to do, but religiously keep interfaces static for 3-10 years. And instead of going all 2nd system on the interface, work on other things. Maybe those are easier app-building tools? Maybe those are actually just killer apps. Maybe those are better tools for configuring the system, or for managing large numbers of desktops. Maybe that's "work on something completely different that doesn't affect the desktop". Whatever. Maybe that's "work on something completely different, like servers". I don't really care, as long as you stop breaking perfectly working desktops.

Comment: Re:Apple's lack of support for Retina Displays (Score 4, Interesting) 277

by Hawke (#40727601) Attached to: Linux 3.5 Released
Kinda off subject here, but ...

Your standard app was not written for silly-high DPR. You could show this on linux too: take your desktop, and crank the DPI to 300 or so, so that the X server thinks your screen is only 5" across. Now move far enough away from it that a 12 point font looks reasonable, and then look at how stupid apps look. Icons are microscopic (because they're defined in fixed pixel sizes). Layouts between menubars and borders look stupid (natural spacing was defined in fixed pixel sizes).

So Apple's approach here is to tell the application that the screen is 1440x900. Any primitives that can be scaled ("place the string 'pants' in font 'Helvitica', size 12pt, at X,Y". "Draw this 2kx2k pixmap in this 500px x 500px space") are then rendered to the screen's native resolution. Things that can't be scaled aren't ("draw this 96x96 pixmap here, in this 96x96 space"). Some apps then look horrible, some look great.

I personally would have rather they just let apps look like crap, and told people to fix their darn apps, but I can understand why they didn't.

Comment: My initial list (Score 1) 280

by Hawke (#40189371) Attached to: I typically interact with X-many OSes per day:
Mac, Linux, Windows, FreeBSD variant (all at work. At home, Linux)
IOS (tablet), Android (phone)
Linux in my television, Tivo, and game console.
Whatever the heck RTOS runs my car, car's GPS, my work telephone, microwave, the badge-swipe system at work, and my work monitor (no, not joking. Darn thing can lock up, and has a boot screen)

That's all I'm coming up with on a daily basis.

Less often, ATMs, routers (Mostly linux), NAS devices, smart-switches (didn't seem like a linux box, but had some copyright lines in the packaging) and anything else with a UI more complex than a mechanical watch. Increasingly, EVERYTHING has an OS: I'm sure it won't be long until someone finds a reason to put a fancy UI on a charcoal grill; and then all future grills will have an OS.

Comment: Re:Exactly why we don't need IPv6 (Score 2) 329

by Hawke (#40103453) Attached to: Sales of Unused IPv4 Addresses Gaining Steam

and then once they've excavated what your MAC address is, telling your router to route traffic to your node is trivial.

Could you further explain this attack vector, cause I've not really understood it so far. The bad guy has your IP address. Exactly what is the additional harm in letting him know your MAC address?

I understand the issue of "probable iphone MAC => iphone specific vulnerabilities", but that doesn't seem to be what you're talking about here. (And really, that's not a significant barrier to the attacker anyway. You did something that let him see your IP address: the odds are quite good that he already could figure out your OS more reliably than using a MAC -> OS mapping)

People are always available for work in the past tense.

Working...