Slashdot videos: Now with more Slashdot!
The University of Utah was one of the original ARPANET nodes back in the '70s, so there's been some tech out there for a while now.
The other part of the problem is that Sacramento's biggest claims to fame at this point are that it's the state capital of California (*shrug*) and it's kind of close to the Bay Area (so is Vallejo, Vacaville and Antioch). The climate is miserable (think Texas weather, only with a little less humidity, no hurricanes and without the weird bugs), the neighborhoods are extremely hit-and-miss, the culture is getting better but is still more or less non-existent, California's tax and business codes are pretty obnoxious, the physical infrastructure in Sacramento isn't quite Stockton bad but there's definitely room for improvement... yeah. Sacramento's not bad, but it's not good, either.
Don't get me wrong, I think Sacramento will get some startups to set up shop there. Some of them will probably succeed. I don't think they're going to take over the world out there, though. Venture capitalists would rather go to Denver, Seattle, Portland or Las Vegas than Sacramento, and if you're going by plane, you're not saving that much time by going to Sacramento over either of those other places.
I'm concerned that iXsystems and the community is biting off a bit more than they can chew - Canonical's having issues getting Unity out the door and, though I don't have either of their financials in front of me, my assumption would be that Canonical is a much bigger company with a much bigger community of developers behind them. However, if PC-BSD is going to get the stability and ease of use that's necessary to be a compelling desktop alternative for all but a few hobby enthusiasts, they're either going to have to maintain a BSD-friendly port of KDE or roll their own desktop manager.
For those of you from Europe or those just generally not from the area, here's what's basically happening:
There is only one paved road to the Black Rock Desert - Nevada State Route 447 - which is only useful for most people if you take it heading southbound since that's the fastest way to an interstate (that's American for "large freeway") and is also the only direct route to Reno (nearest major airport) and the Bay Area. The total population served by this road is maybe 1,000 (I'm feeling generous), so the road is built accordingly - it's a two-lane highway that's generally straight thanks to the local geography but makes a rather firm point to go right through the middle of what habitation there is in the area (notably, Nixon and Wadsworth). The few towns served by the highway are consequently bisected by it - thus, if the highway gets overwhelmed, it's impossible for residents of the town to cross the street. Also, adding insult to injury, there's not a tremendous amount of freeway or onramp capacity once the highway reaches the freeway (no cloverleaf or anything), so excessive oncoming traffic can cause localized traffic issues on the freeway, too.
In short, Burning Man needs to somehow evacuate over 50,000 people using infrastructure built for less than 1,000 within 24 hours, and do in a way that doesn't paralyze the lives of every single town in the area. No matter how you look at that problem, people are going to have to wait - the only question is whether people are waiting with their keys in the ignition, whether they're waiting for their license plate number to come up, or some other means of queue management. It's either that or try to convince everyone to drive through Cedarville and Alturas to go home, not that they're equipped to deal with any significant traffic themselves.
Seriously though, TeamViewer is fine. The point of LogMeIn was that, if you needed remote access to another user's PC but they weren't technically savvy, you could walk them through it without too much trouble. SSH tunnels and proper VPNs are certainly preferable if you're in charge of both ends of the connection, but if you're not, TeamViewer, Jump Desktop, and the like get the job done without too much fuss.
Having seen a few custom Access jobs in my time, I can tell you first-hand that, more often than not, you're lucky if the data is normalized, much less organized in any sane, sensible way. I've seen tables where there are "Serial Number 1", "Serial Number 2", and "Serial Number 3" fields, for example, because "nobody has more than three pieces of equipment". So, now you're faced with having to get that data halfway normalized, or at least document how you could normalize it, and then you have to map it up against the new solution's schema and hope and pray they have a set of tables that are designed to hold the data you're looking for.
Thankfully, there's a really easy way to manage that, even for smaller companies. Bring in a part-time consultant periodically (say, for a couple hours every month) as an insurance policy. For the brief period they're there, have them focus on documentation and chatting up the sysadmin. As an added bonus, maybe have them check backups, server logs and the like to ensure the sysadmin isn't falling asleep at their desk. Another bonus is that, if the sysadmin has a large project planned that they could use some additional temporary headcount on, you have someone else with some institutional knowledge lying around.
For the record, I just tried to RunAs appwiz.cpl from my PC and it worked just fine. Of course, the nice thing about Windows 7 is I don't even have to RunAs my Control Panel widgets - if I need administrative access, it will ask for an administrator user name and password when I open it and then escalate for me, saving me from having to remember what options require administrative access and what ones don't. Y'know, like a proper gksudo-type tool should.
I won't miss XP, is what I'm saying.
The argument of "But...But...But... Polio!" is not a valid argument for a Chicken Pox vaccine.
No, but Shingles is. Vaccinate against Chicken Pox (which is usually fairly mild) and you get a two-for-one deal out of it.
Want to know what's profitable? Iron lungs. They're expensive and you're hooked on them for, if you're lucky, only a month or two while your body recovers from polio. If you're unlucky, you're hooked on them for life. Know what's less profitable? A single prick in the arm containing a vaccine that, even at the highest markup, costs less than 1/10,000th of a modern day life support system and prevents the disease that lands you in the iron lung in the first place.
Critical thinking - how does it work?!