As a coder in illinois who's currently trying to implement/ implemented a PACER like system for 70 of the 102 counties. Cost is really not a problem. Who pays the cost is, and most attorneys at this time are not big fans of tech. We're starting to get some success in the state, but it's slow coming. We have better luck with out of county Attorneys than local ones, since they can't just walk across the street to file something. In the last 5 years, a large number of our courts have started scanning everything, and in the last year or so, we've had a good amount of success at getting them to put all of the documents online. Currently it's only the attorneys of record who can see those documents though due to IL supreme court rules.

Your calendar thing cracks me up though, we implemented and ical feed for all of our courts 10+ years ago. This is per attorney or judge, or police officer btw.
Of the 70 counties where this is available, we have 1 user of it..... out of 74692 attorneys. I keep hoping that the younger generation of attorneys, and their secretaries) coming into office in the last few years will have higher technical expectations than the old farts who are leaving, but only time will tell.

I guess my point is that the tech is there, the courts have put it into place and paid for it, but the attorneys just don't have the desire to use it, much less share the cost.

subtle... and funny..

I think you're dead on with #2, but I doubt anyone will ever say that violent behavior caused video games....

In Florida 23.32% of African Americans were disenfranchised I think it's safe enough to assume that they are a block unto themselves.

DING! Get that man, or woman, a prize! I think "outrage fatigue" is a very important piece of the pie as far as DHS and taking away our privacy goes. The more fatigue the more they can take away.

We're actually moving away from blade servers to standalone servers. You can get so many cores on a chip now that each set of 8 blades can be replaced by 1 2U server. Each server has a number of raided 2.5" drives that we use with glusterfs for redundancy between servers which we then re-export over Fiber channel so that we can get rid of our dedicated FC arrays, yet continue to use the FC infrastructure we have in place.

I have fiber in my house as well; not Google, but got an opportunity and took it. It's a new house and we ran cat 5e everywhere. Maybe some day I'll regret not running cat 6, but I doubt it. I just recently put the ends on the cables, and stopped using wireless for everything. It's made a huge difference, and well worth it. It's not uncommon for 5 people to be streaming something different at the same time, and the wireless just couldn't handle it. Depending, you might be able to replace all of you phone lines with ethernet. You can always use an RJ11 in an RJ45 jack and just decide at the patch panel what it's going to be, phone or ethernet. If this isn't a new house, chances are you have a bunch of unused phone jacks just taking up wall space. And depending, you might just be able to pull the ethernet using the old phone line.

good luck

really good to know...

yes.... yes that's it exactly... oh well... was funny in my head...

I can see the benefits of course. Doesn't mean it shouldn't be modular. So this one thing or that one thing can be replaced when something comes along that is better for someone. And why not just have a better way of doing this through /proc/xxx/fd?

Thanks. I've read this before. But not currently switching to RHEL7, so have obviously forgotten everything that isn't relevant to my day to day trials. But thanks again for the reminder.

It's nice to think that a whole hosts of angles are ding as I write this reply on my oh so very audible Model M. It's the click that does it for me.

I haven't seen a lot of pressure yet. With RHEL6 the urge to switch came on fast. Esp with regards to virtualization and what not. I haven't gotten the sense that RHEL7 has a whole lot of "must have now" tech in it, as opposed to the amount of systemd fear it has. Based on some quick googling, systemd can be configured to send your log files over syslog so that takes care of most of my corporate compliance concerns. I don't think the systemd folks have done a good jobs educating people on how it can fit into existing workflows. Esp. against all of the noise out there. I don't really know if it's even possible to fit it in with everything. But I guess we'll find out. I currently have no opinion, I see some benefits as well as some drawbacks.

I guess that's sort of my issue as well. Why isn't systemd modular. If They want to fix all of the problems that's great. But isn't there a way we can just use the pieces we want. I get that they've effectively made a standard API for all of the init processes to talk to each other and start up and all of that magic stuff. Terminals, Security, logins et all. There's a big mess there. No one will deny that. But it would have been nice if they'd actually defined a formal API for all of this, that we could do things differently if needed. Personally, I'm gonna stick to my RHEL6x servers till I get a good sense of the fallout from all of this. I wouldn't be surprised if someone forks RHEL6 or Debian at this point just keep systemd out of the way.

what really sux, is that for most people, here in the southern part of the US, no matter how much they want to, they can't hear or speak the difference in pen vs. pin. That why we call them stick pins, and not just pins..