We need keys and host passwords checked as authentication types without having to revert to PAM hackery. Just how many systems have been exploited because some root process found a way to read some .ssh/keys and then hopped to other systems with no human intervention.

Where they acted like children:
http://www.engadget.com/2014/1...

The fun continues:
http://phandroid.com/2015/01/2...

And then this:
http://www.knowyourmobile.com/...

So yeah - they're nowhere near a mature company - and lets not forget when they forked CyanogenMod and pulled the "You made this? .... I made this!" move when getting venture capital in the first place...

Cyanogen sold out a LONG time ago..... Then screwed over a few phone manufacturers, and now this. Great track record they have...

Why not 20 digit number where wrong numbers all answer and charge the caller? That would fix telemarketing forever.

And wait until they start snooping everyones traffic and data mining it... for profit - I mean, reliability monitoring...

On another note, I see you're looking at hotel bookings with another hotel chain at your next destination.........

You have to have a free pool to get a 5 star rating. Too bad the ratings companies around the world haven't required decent and free Wi-Fi. Major hotel chains would change their offers in a hurry when they are down rated to a 4 star hotel.

Laser cutters are now good enough to make aluminum or brass CDs.

Punch cards readers are rare but there are programs to take scanned cards and tell you what is on them.

No support for 32 bit OS X either. Don't people know how to build fat binaries anymore?

Yet if the OS isn't broken so bad it needs patches every few weeks, then I don't need to make that decision.

IT is to support my business. It isn't my business. Downtime due to idiot coders who didn't test new features that I don't need isn't good for my business.

If your page isn't fully loaded in less than 2 seconds over a real world network without using cache, potential clients have will leave before the 1st page load.

If you can write pages that load fast, keep doing the custom work. If your pages are slow, fix it or fix your technique.

We buy the Solaris 9 patch support. The changes for this cycle are 1) TimeZone files updated, 2) Fix to zip and 3) Java fixes

The last kernel patch which required a reboot was 122300-68 from June 2013.

My Solaris 11.2 box gets rebooted way too often to replace other production servers and its better than Sol 10.

Someone at Oracle should learn the difference between an operating system and an operating environment and making sure the OS is rock solid.

My early Jr High computer books included things such a picture of a pigeon hole as a repression of memory. It used the classical "input/processing/storage/output" model. Flow charts where used to demonstrate breaking a problem down into parts that the computer can cope with.

ZFS is miserable on things that assume overwritten blocks will stay where they are on the disk. Some people even count on that to able scrub data. Is there a simple ioctl/fctl that allows that to be turned off in ZFS? no. There should also be an ioctl saying "this file needs to start on a physical block, not be encrypted, and it would be very cool if it was in the 1st gig of the disk, and can you tell me what real sector you can allocate for it?" because computer still need to boot.

Why wasn't there a zfsdump / zfsrestore that wrapped up the send / receive from day one? Even if /usr/lib/fs/zfs/fsck was a shell script wrapper around something else, it would have indicated a clue about where this stuff should fit in the grad scheme of things.

Not everyone uses ufsdump to make backups, I use it to verify the contents of some files on the disk.

or make use of &&

cd /tmp && cd $SOMEPLACE && do_dangerous_work

Of course having code do rm * tends to question why they don't know which files they need to purge in the 1st place.

Nothing so sinister.... The core group of people that made this stuff in the first place is moving on. This leaves the old sticklers that made things work out of decisions and are being replaced with a whole generation of new developers that haven't 'been there, done that, solved it' before. Its a changing of the guard in Linux - and its not looking good.