The moral of this story is: 1) The TSA and assorted related three letter agencies don't give a crap about due process or warrants anyways
The owner of the laptop had even been arrested previously and given testimony regarding his activities.
Ahem, TFA says Yang was arrested and provided testimony, Kim is the subject of this ruling. He never implicated himself in anything and it is only by reference from Yang that he was noticed and investigated. The part about the investigating officer having zero suspicion that he would actually be involved in criminal activity during his stay but only thought that if Kim might have this search would find it, as well as hopefully recording proof of Yang's comments and interactions. If this man was a threat, the fact he was not monitored in any sense of the word during his stay negates that.
Fishing expedition on a device that the agent clearly knew in advance would be a rich store of information using a procedure and supposed exemption that cannot be justified on exit from the country.
The Executive Branch certainly seems afraid of terrorists, and the DoJ gets to define it as they please. This is like writing your own job description to say you can focus on whatever you've decided is important, and your boss' instructions can be overruled when you think you've got more important things to do. Is this a blank cheque-book or is there still a balance between the branches?
If you spend any time working in a reasonably sized It organisation (my four systems at home apply for me, YMMV), you will realise that release management cannot be overstated. Of course if you accept unstable updates system-wide you're going to experience pain, but why on earth are you setting that as a default for something you rely on?
I often build ~amd64 packages, but only because I'm after specific features/fixes in that release, and am uninterested in bleeding-edge elsewhere. Of course the biggest reason I like Gentoo is early access to new versions of packages without dependency hell, but you're understating that benefit simply because you've gone gung-ho. While the ebuilds are not supposed to break (if I understand correctly, the tilde is for applicaiton bugs), you're still off the reservation.
I fail to see the problem. Oh, and if you keep insisting on this approach, may I suggest btrfs for hassle-free rollback? I wouldn't even contemplate a system-wide ~ update without establishing a known checkpoint to fall back on. This seems a problem of your own creation.
It's not dead, but it's no longer free. I work with three volunteer organisations - they're not charities but social groups geared towards helping expats get settled in my city. Membership management, event planning and budgeting, publications and flyers. All were easy to collaborate on with Google Apps, but even the (seemingly) small subscription fees are a burden when we're explicitly non-profit and loosely organised. We could have two active users one month, ten the next, so no single pricing plan option is appropriate without serious overhead and/or possible overspend.
Very unfortunate.
Some people still think there are two parties in Washington instead of two faces of the same party, the Money Party.
Some people are happy to accept that two political parties are all that are required to represent the 3rd largest (by population and expanse) country in the world, with only China governed less diversely at a comparable scale.
Urban and rural poor, wilderness areas of desert forest ice and mountain rivalling countries in expanse, high-finance manipulators, middle-class commuters, academia, greens, industrialists, religious fundamentals of dozens of variants, secular scientists - in Americaland every person in these and all other groups all fit neatly into exactly one of two world-views - Red vs Blue.
The rest of the western world have no idea why Americans think this is acceptable.
Oh, and I've always remembered 3.141592653589. My mother's phone number is a complete mystery...
Here, I'm using Storage System to refer to a design rather than a product.
While filesystems are a good point to look at, I'd be much more interested in the one thing almost all concurrent systems contend over: spindles (or more correctly, drive heads). Partitioning workloads onto separate spindles or SSDs makes a lot more sense than twiddling over the finer points of a filesystem. Serial read/write is well-suited to even slow SATA drives though YMMV, while high-concurrency OLTP DBs benefit from SSD. I can't think of a benchmark that shows any significant performance difference between the headline filesystems when you're not talking about SSD, and if you have the cash to go SSD for all your storage perhaps you should get a professional to advise you better?
You will have many recoverable tape errors.