All the panels from the Silicon Valley DevOps Days are now online. A huge round of applause for InfoQ for putting this entire event online and making it available to the world.
If you want a glimpse into the next 10 years of system administration as a career path, you need to get up to speed now so it doesn't take you by surprise in the coming years.
Randy Pausch, you may recall, became infamous because of his dying "Last Lecture". Just tonight I happened to come across a talk he did on Time Management, "because time is all we have." As he particularly pointed out, "you may have less of it than you think." Time management tips from a dying man, who better to speak on the subject?
Whats shocking to me is that the talk is not philosophical, rather its 1 hour 16 minutes of non-stop practical pointers, ideas and applications.
Randy Pausch Lecture: Time Management
I think my chief takeaway was that time is, and should be treated as, a precious commodity. If you are spending time, it should be on something worthy of that sacrifice. What this also implies is that if someone wants my time, I should ensure they are using my time wisely. Time is not an infinite resource.
This point is particularly key to me because I am a wanna-be perfectionist. I will drag on and on and on for days, weeks, months trying to think something through before truly devoting myself to it. For code this means that I want to be able to visualize all the logic before I start writting. Now, this is an entirely flawed concept, because any reasonably complex program is going to have more lines of code in it that you can keep in your head. Therefore, when I try to visualize everything I'm actually just moving from visualizing one small part to another, and loosing something during the mental context switch. I should instead just start writing the program and then deciding ahead of time to improve it later. This is essentially my version of "a working program today is better than a perfect program in a year".
I'm reminded of a phrase I cooked up with Tamarah (my wife, the lovely women above) several years ago. When discussing something emotional and complex, you can spend a lot of time thinking over and re-thinking the right way in which to phrase it to provide clarity. But this is exceptionally hard to do and very time consuming. Therefore, when we see eachother in this "I'm not sure how to put it..." pause, we will say: "Badly... and work from there." So we work in drafts, making it clear that the first draft is probably horrifically inaccurate and wrong, but we'll work towards clarity together and in doing so get a clearer picture of the topic than we'd ever get from the perfect one line explanation.
For sysadmins I find this really hard. It seems all we sysadmins are both perfections and ADHD at the same time. I wish I were exaggerating, but most of us really actually are clinically hyperactive... its a job qualification. The problem is that while we can keep a lot of plates spinning, we're very bad (on the whole) of providing timely delivery with high quality, unless an external force demands it. This is why sysadmins have to have managers. Geeks without overlords will do amazing things and deliver very few of them. (The description of a good overlord is an excessive left for the reader.)
I digress. I personally recommend watching this video repeatedly, say every 3 months. I re-watch David Allen's GTD talk at Google every couple months already. I always find something new in it and it's a great reminder to get back on the wagon. More importantly, personal management is dry and tedious, so hearing enthusiastic guys like David Allen or even Tony Robbins (say what you will, his TED talk was fantastic) can be a real pick-me-up.
This morning at 8:19AM Pacific, the OGB passed:
Whereas Oracle has continued ignore requests to appoint a liaison to work with the OGB concerning the future of OpenSolaris development and our community, and Whereas Oracle distributed an email to its employees on Aug 13 2010 that set forth Oracle's decision to unilaterally terminate the development partnership between Oracle and the OpenSolaris Community, and Whereas, without the continued support and participation of Oracle in the open development of OpenSolaris, the OGB and the community Sun/Oracle created to support the open Solaris development partnership have no meaning, and Whereas the desire and enthusiasm for continuing open development of the OpenSolaris code base has clearly passed out of Oracle's (and thus this community's) hands into other communities,
Be it Resolved that the OpenSolaris Governing Board hereby collectively and individually resigns, noting that under the terms of the OpenSolaris Charter section 1.3.5 the responsibility to appoint an OGB passes to Oracle.
Also see the OGB Call Agenda.
Nova, my first daughter, is now 6 and Glenn, my first son, is now 5. As a GeekDad I ensure to bathe them in geeky goodness. I've been thankful that Glenn is obsessed with Lego. The kool thing about it is that of course, I get to help him, so its just a great time.
This got me thinking back to my own youth. I had a box of Lego's but not a lot of sets. The one that I did get was in 1988, when my parents got me perhaps my favorite (but forgotten until recently) toy of youth: the Lego Technic 8865 "Test Car".
That set was amazing. I proudly displayed it on my shelf in my room, both because of my pride in building it as well as just how outright kool it is.
Since that time Technic has grown up as much as I have. Take a look at the Technic Lego 8421 Mobile Crane:
So tempted to buy that.
But most fun of all... this week Glenn is in a one-week Lego Pre-Engineering class. For 3 hours a day they geek out and build all manner of fun stuff.
One thing I'll throw out there for Dad's... Lego has an Education dept: Lego Education. Of particular interest to Tamarah and I, is they have a complete Homeschool Curriculum and various kids, including robotics kits, for education. A really amazing resource for parents.
Damon Edwards (DTO Solutions) & John Willis (Opscode) are the two guys really pumping out the "good news" of devops. They started a new podcast, Devops Cafe several weeks ago. Already on episode 8, having featured guests such as John Allspaw, R.I. Pienaar, Andrew Shafer, and more. Highly recommended.
Whats interesting is that John & Damon really aware of an outcry from the community, that is: "How do all these devops shops do it!!" We want to emulate them, know what tools they have, how they use them, what works, what doesn't, etc. So to facilitate just that, they started a videocast sub-series called: Open Mic.
Open Mic 1: DevOps Metrics and Dashboards at Shopzilla from dev2ops.org on Vimeo.
In the first episode, they take us into Shopzilla, where Juan Paul Ramirez shows us their tools, metrics, and talks extensively about how they got to where they are. Excellent content!
If you haven't already seen, perhaps the most popular talk this year at Velocity, "A Day in the Life of Facebook", in which the Facebook Ops team introduces us to their tools and organization.
Whats really great here is that we're not share deeper information about how we're doing things, such that we can be a community of organizations. In the past, only a handful would really share and they were always far removed from useful pratice. I really hope this trend continues.
Big thanks to John and Damon for helping fuel that fire!
A very sad day indeed... Planet Solaris is dead. Just another in a long line of bad signs. Please use Planet.OpenSolaris.org instead. A big thanks to David Edmondson for running planetsolaris.org for so long.
I am partly responsible. Sorry to everyone that the blog has been so quiet lately. Given that state of Solaris right now, its unclear what is dead and what is alive. It feels futile to blog about features that may never really be viable. Couple that with OpenSolaris which still hasn't delivered and the fact that many of the features that need documenting are really pretty uninteresting to me (ie: IPS/AI).
The exodus still continues. Lots of engineers have left Sun and many more are considering leaving. I'm told by folks that its not a huge problem because while the big name guys are leaving, the real down in the trench do-ers are still there and working away. But it certainly is disheartening.
The most recent news out there was that Oracle yanked HP's OEM License, so if you run Solaris on HP Prolient servers, your hosed. See? Not a lot of positive stuff for me to blog about.
Personally, I've been more interested recently with the growing 'Devops' movement and IT standards. I've spent a lot of time in ITILv3, ISO 20K/27K, CobiT 4.1, COSO, NIST SP800-53, etc, etc, etc. A whole new and interesting world to me because I came to it instead of a company hoisting it on me against my will.
I have several articles to get out for SearchDataCenter which I'll plug here, and then will start rolling new content out here in a bit.
There are a lot of monitoring tools and frameworks out there. Some are expensive (such as HP OpenView) some are free (such Nagios). All of them have a niche to fill. Zenoss looks pretty. Nagios is will supported and highly extensible. Up.time and WhatsUp Gold are easy to get going. They've all got their thing. As such, I spend a lot of time evaluating and re-evaluating them. The one I circle back on most commonly is Zabbix.
Zabbix won't win a beauty pageant... its ugly, lets face it. But once you get beyond that its all raw power. Its agent based making it easy to extend. Monitoring something new doesn't require writting some plugin or writing a complex XML description, its just a simple single line in the agent config. It supports alerting through email, jabber, or SMS natively and is capable of doing fine grained escalations. It graphs everything, so there is no need to have Cacti or Munin or some custom RRDtool setup in addition. It is the only monitoring tool/framework that I'm aware of that natively handles IPMI, both for monitoring and actions. It has proxy capabilities for monitoring into hard to reach places (such as a small branch office) and can be multi-teered to control several sites from one point of control. The list goes on and on. Zabbix truly is the state of the art in monitoring.... and its free!
But... its not entirely the most intuitive tool to use. Several core concepts must be fully understood to be effective with Zabbix or its a big confusing mess.. power that can't be harnessed.
So a very fortunate thing happened to me. I wanted to do a large proof of concept based on Zabbix 1.8.2 but needed to refresh on some basics, when it so happens that Packet Publishing tells me they'd like me to review Zabbix 1.8 Network Monitoring. While a strange coincidence, I wasn't sure if this was a blessing or not. Most books on monitoring tools are abstract for the first 4-5 chapters, then have a really crappy installation chapter, followed by several chapters on topics that never seem to be what you actually need to do. That is to say, useless.
Thankfully, Zabbix 1.8 Network Monitoring is perhaps the most practical book I've ever read. I'd dare say that if I wrote a book on Zabbix it'd be pretty much the same. There is no lengthy flow of abstract BS, its essentially a systematic walkthrough of Zabbix from beginning to end. The first chapter is how to preform a full installation, hitting on the various options and capabilities impacted by them. Then chapter two moves onto configuration, ending with getting your first alert. So, you've got Zabbix fully installed, configured, and alerting, and thats just the first 2 chapters! Thats the way technical books should be. :)
The book is laced with screenshots and CLI examples at all turns. It really is a walkthrough, and author Rihards Olups shows you ever step. This is especially important because most of the real configuration in Zabbix is via a web interface, and its confusing to navigate unless you have a picture of what you should be seeing. Its all there, which means you don't need to frantically flip pages in front of a screen trying to figure out how he did this or that.
It has a great chapter on reporting and another on graphing. I was really pleased that these we're lumped together or breezed over. They are key capabilities and are given plenty of space.
There is also a great chapter on troubleshooting (appendix actually), which will help you in any areas that cause you to stumble initially.
If you want to get going with Zabbix and don't want to waste time, this book will save you days. As I mentioned before, Zabbix is configured differently that the traditional tools out there, so you need a keen understanding of core concepts, such as "Hosts", "Items", and "Templates". You can piece it together from the (poor) Zabbix manual and experimentation, your you can just buy the book and get going.
Now.... that said, there are only two shortcomings to the book.
The first is that it can, at times, be a little too fluff-less. There are times a little up-front explanation could have been enhanced before just jumping into it and explaining as he goes along. But that will really be dependent upon your learning style. If you want to get Zabbix going, its great, but if you just want to read about it, its not so easy to just jumping in and out of the text to understand concepts. Again, its a walkthrough, not an overview (such as O'Reilly books, which tell you a lot about it but typically not enough about how to actually make it happen.)
My second nitpick is that distributed monitoring isn't really explored fully. There is a chapter on monitoring remote sites using proxies, but an additional chapter on complex mult-site installation featuring not just proxies, but also parent-child servers, would have been very welcome. I'm not sure if it was left out because of its complexity or some other reason. Perhaps he's setting himself up for a sequel covering advanced topics. May have even been due to the length, the book is 428 pages and is really dense material.
The book runs $45 which is pretty standard. The PDF ebook is $33, which is a little steep imho, but like I said, this book really will save you days... so it'll pay for itself in an hour or two. Incidentally, it looks great on my iPad. :) See the full list of contents and get a sample chapter here: Zabbix 1.8 Network Monitoring. Buy it direct or you can pick up direct from the publisher or at Amazon, or if you're in the Silicon Valley don't forget to help out the brothers at Digital Guru.
I'll throw out a personal thank you to Rihards Olups for the way he wrote this book. His approach was fantastic, and as a technical writer myself I really like the way he tackled it. It takes a special mindset to write so clearly and concisely, and I really appreciate that.
hostid's on SPARC are handy things because through the PROM they are tied directly to the hardware. On Solaris X86, not so much. They are "soft hostids", software emulated and essentially randomly generated. Because of this fact, it is easy for an upgrade or accidental deletion to wipe out the hostid and potentially cause you problems.
This post applies only to Nevada based installs post-snv_100. Or, more specifically, following the integration of "PSARC/2007/078 Hostid for X86 systems". For information about the sysinit module and how things worked on X86 prior to snv_100, please see the excellent post The dark side of the source - hostids by Frank Hofmann.
So the hostid is generated during installation and stored in /etc/hostid. This file contains 2 lines, a comment line and the encoded hostid. A valid hostid is 7 hex chars or less, padded to 8 hex numbers. Therefore, 0x0fffffff (zero followed by 7 f's) is valid, whereas 0xffffffff (zero followed by 8 f's) is not. To be clear again, these are hex numbers, not ASCII characters.
To set it we first edit /etc/hostid with vi to remove the second line, such that only the comment on line 1 remains. (Backup the hostid file if you think you might want it again later, or if your just playing around). Then we use a bit of PERL (based on an extraction from the method of the hostid service) to add in the encoded hostid. To make it effective update the boot archive (always do this manually! don't assume reboot will do it!) and reboot:
# echo "0x0ddb00b5" | /usr/perl5/bin/perl -e 'print("""); while(<STDIN>){chop;tr/!-~/P-~!-O/;print $_;} print(""n"); exit 0;' >> /etc/hostid
# sync;sync
# bootadm update-archive
updating /platform/i86pc/amd64/boot_archive
updating /platform/i86pc/boot_archive
# sync;sync;reboot
When the box comes up you'll have your new hostid!
[root@am1-ja710-36 ~]# hostid 0ddb00b5
If for some reason you get a hostid of 00000000 or a warning that the hostid is invalid, you either got the value too large or encoded it wrong in /etc/hostid. Check that you pasted the code above properly and try it again.
Please note, I assume you're not doing this to be naughty. I only spent time to figure this out because I had several systems which for some reason got stuck with 00000000 hostid's (likely because something went wrong during jumpstart).
On the list of those who hate IPS, I am the first. Even so, it is a very long list, and one that will grow longer and longer as it ceases to effect hobbiest and early adopters and because a reality in a proper Solaris GA release.
While IPS has been around for some time now, only recently did I actually fully understand its purpose. In meeting with an engineer at Sun (whom I shall not name) I started into my years old "Why IPS is an abomination" rant. However, during this vigorous back and forth debate, it finally clicked fully in my mind exactly why Solaris Engineering wants IPS so desperately. And, furthermore, why I am trying in vain to kill it.
You'll recall back in time, when dinosaurs roamed the earth, that Bart Smaalder's posted Rethinking Patching. This has been the real key, and I've known that, but some reason his point was lost on me in the midst of his "Dim Sum" analogy and the takeaway phrase that ensued: "No more dim sum patching". I'm sure some people really understood this and embraced it, but as for myself and many others I've talked with over the years, we somehow missed the essence of what he was pointing out and what its full ramifications would be.
Lets put the "dim sum" analogy away. What he's getting at here is that Solaris patch management is and has been for a long time, a complete disaster. No one will dispute that. Proper patching requires that the environment be in a known consistent state such that it doesn't inadvertently cause additional unexpected problems. But when you are installing dozens, perhaps hundreds, of patches over a period of time the OS become a tangled mess. The practical reality is that administrators reject "Patch early, patch often" for the more reliable "Don't fix it if it ain't broken."
All that gets so much worse when people don't simply patch the systems as Sun tells them to (through maintenance updates) but instead pick-n-pull only patches they want. Doing any kind of intelligent patch management is almost impossible because there are so many various dependencies and possible conflicts, only a handful of which that Sun even knows about.
Therefore, IPS first and foremost is about solving that very problem of patch management and going from one known state to another known state.
That's it. It's not about being easier to use (but that is a selling point). It's not about being more like Linux (but that is a selling point). It's not about moving from a bunch of DVD's to a network repository (but that is a selling point). It's all about unf**king patch management on Solaris for enterprise customers.
But, its not just about IPS. UFS isn't an option for your root file system anymore; why? Because ZFS Boot Environments (BE's) which allow point-in-time rollback following an update is just as critical to patch management and establishing "steady state" as IPS is.
Same thing goes for Sparse Zones. Managing dependencies between the Zones and the Global Zone is complex, IPS makes it even more so. Therefore, because IPS can already manage non-root images and ZFS Boot Environments can be extended to Zones, why not simply embrace the same model there. Those of who would say, "Keep zones simple, let me manage the deps!" is like a customer saying "I still like the old pick-n-pull model, please let me continue."
Also, although many of us value Sparse Zones for their security... Solaris Engineering (on the whole) see's them primarily as a way to conserve disk space. Therefore, they will contend, ZFS Dedup relieves them of the requirement to support Sparse Zones.
For those of you who, like myself, want IPS removed from Solaris completely.... we're almost certainly out of luck. The ONNV source code was changed, circa snv_130, to stop producing SysV packages from the Makefiles. It's all IPS-ified now. That is why SX:CE died. Prior to that point, SysV packages would be produced from a build and they would be converted into IPS packages, this is why the IPS package names were the same as the legacy SysV packages (SUNWsomething). With that major code change in place, its not simply of matter of flicking the switch back to SysV.
Because Jumpstart is a harness around SysV packages, it dies. You'll notice that a single-user install from CD/DVD is actually just a local jumpstart... its the same process essentially. So when the old installer was replaced with Caiman (originally billed as an easy-to-use graphical installer), it now had to pickup the slack. Since retrofitting Jumpstart for IPS would essentially invalidate the work done on Caiman, it was extended to become AI, the Automated Installer.
So you can see that in untangling the patching mess, we've created a whole new breed of technologies which are simply a different kind of mess. And this isn't one we can just petition to have removed. Solaris Engineering is right to try to ease the suffering of enterprise customers, and should be applauded for their valiant efforts to go the distance to solve it... even if it causes untold new problems for customers.
So, this isn't about the continual Linux-ification of Solaris... tha'ts why they didn't choose Yum or some other existing Linux packaging system. This is about patching. And if you, like myself, just accept that explanation and take it to heart, all the other weird and bizarre changes they are making seem to make sense. (We may still violently disagree, but they make sense.)
Splunk 4.1 has arrived and really raises the bar for an already amazing tool. Several new key features have been added that make it worth an immediate upgrade:
The big killer-app for me that takes Splunk to a whole new place is the Real-time Search feature. You can enter a search string like usual and then set a time period, such as 1 minute. Then you will see events rolling in, real-time. At the end of the specified period the results clear and you see the next period of results start rolling in real time.
This feature is just absolutely amazing... its like an intelligent web-based analytical tail/grep of your logs! This is great for not just identifying problems but also verifying that you've fixed a problem or for use during debugging sessions. Did that config change really stop the 404's? Have those errors actually stopped coming or do you need to keep working? This feature is a must-have for all sysadmins.
You can check out the list of new features and see videos about them on the What's New in Splunk 4.1 page.
One of the perks of working for a jazzy startup like Joyent who's had a good year: free iPad's for all. Our Christmas bonus from Joyent. w00t. So I pre-ordered mine and got it today, as promised by Apple.
So, lets get down to brass tax: its an oversized iPhone. No more, no less. There is no expansion slot for storage, just the same buttons and I/O port as the iPhone. It looks the same, feels the same, works the same.
Now, bearing that in mind. There are some things that iPhone could do, but it was a bit ridiculous as iPhone size. My favorite example is the iSSH application which allows you to SSH to a server. Its a great app, but on an iPhone its so small its only a gimmicky sort of app that might be useful in a dire emergency but otherwise is just for show. VNC apps are the same. Even some financial apps with charts... they work on iPhone but its just too small. These are the apps that shine on iPad, provided there is an upgraded version which natively takes advantage of the screen real estate.
The same goes for video. Video on iPhone is fine, but its really tiny. Given the choice between viewing on iPhone or your laptop, you'll choose your laptop every time. With iPad the size is perfect for viewing and the portability is great.
Again, this applies to books/pdf's, etc. The iPhone was just too small. With iPad you have plenty of viewing area and its more comfortable because of the larger fonts and more text per page.
If you, like myself, have wanted a device to carry all your PDFs on, this is definately it. Download the "GoodReader" app. You can transfer PDFs to your iPad using a variety of methods and view them from a library. I've loaded all the Solaris, NIST, CIS, etc manuals and several PDF books I've downloaded from Safari to it and they look great.
There have been two big concerns about iPad, so lets dig into those.
The first is that its backlit. Meaning, its harsh on the eyes and therefore not a viable eBook reader. This is true as expected. The brightness is on par with the iPhone and while reading news and skimming books is fine, reading for hours on end will burn out your eyes just like a monitor.
The second is about the usability of the on-screen full size QWERTY keyboard. I was shocked! It works beautifully! When I typed my first sentence I expected to have gotten every other letter wrong, but to my surprise it was spot on the first time. The only trick is to not think about it... just touch type and don't look, and you'll be fine. I'm sure there is some magic in there doing minor corrections based on what you meant to press versus really did, but whatever they did it is brilliant. Absolutely positively no issues typing on it at full speed.
So, should you fork out $500 for one? IMHO, no. At least, not yet. When all the apps are iPad native, it'll be great, but for now it needs more time. This is only day one, and they are converting quick, but give it time.
If you are an iPhone addict and use it for news, video and browsing a lot, then you absolutely will love the iPad. However, if you primarily use your iPhone as a phone, use the maps, and maybe use some apps for checking your bank account, then wait. That is to say... if you use your iPhone as though it weren't a mobile device, then congrats, iPad is what you've wanted.
The biggest downer is that many of the apps are releasing "Tablet Versions", where you have to buy the new app, typically at double the price. "Things" for iPad is a new purchase and is $20. Thats just a joke. iSSH, thankfully, was a free upgrade. Watch that space carefully. Also, more serious business apps are coming, such as OmniGraffle, but its a $50 app! That's insane, imho. You'll see the app wars really come alive in the next couple months.
Hot on the heals of Oracle's revamp of Solaris support, the licensing agreement for free downloads of Solaris have changed. Infoworld broke the news on Friday.
The Licensing Information pertains to "software on this Web site", and states:
"You may use Solaris only in one of the following ways: (1) if you have obtained a system from Sun or one of Sun’s partners that includes a license for Solaris , you have a perpetual right under that license to use only the version that was installed on the system (no right to use updates, or upgrades to Solaris is included unless you acquire a service plan that includes this right); or (2) under a valid, existing license for Solaris and properly acquired Sun service plan that includes rights to updates or upgrades to Solaris; or (3) under the trial use terms below to which you must agree before downloading Solaris."
And here's the part that hurts:
"Please remember, your right to use Solaris acquired as a download is limited to a trial of 90 days, unless you acquire a service contract for the downloaded Software."
Ouch. So Solaris 10, as predicted, is a free download just like Oracle 11g R2, but its nothing more than a trial. Wanna run it longer, gotta pay.
This makes the future of OpenSolaris (as a distro) all the more important. It may continue on as the no-cost alternative to Solaris to keep users at bay.... or it might die a horrible death and leave the community looking to non-Sun/Oracle distros such as Nexenta, Schillix, and Belenix.
We're getting more of a taste as to the "new reality". Most of the news is of the "Surprised, but knew this was coming" variety.
Motley Fool has a good write-up about the Oracle earnings announcement and how Sun's impacting the bottom line as well as changes coming. Some of the include getting rid of all unprofitable resale deals, such as Veritas and Hitachi products.
CIO Mag dips into the new "All or Nothing" support model being adopted. The policy (PDF) states: "when acquiring technical support, all hardware systems must be supported (e.g., Oracle Premier Support for Systems or Oracle Premier Support for Operating Systems) or unsupported."
The policy goes on with all sorts of horrors, such as heavy penalties 90-days after contract lapse, including "your hardware system must be qualified as service-ready before technical support can be reinstated" and "The reinstatement fee is equal to 150% of the last-paid support fee, or 150% of the list technical support price for the covered hardware system, prorated from the date technical support is being ordered back to the date technical support lapsed". Ouch.
So how do you offer a product for free and then ensure that people pony up the cash? This sounds like the way. I haven't seen anything about OS support for non-Sun systems (Dell, HP, etc) but I would assume they would have to support at least some of them due to prior agreements over the last couple years.
I'm sure we'll be learning even more very soon. One thing is clear, Solaris just got too expensive for the SMB. The low income customer base that Sun's tried to build up over the last couple years is SOL.
Also... your desktop is getting old... Get some new wallpaper. If those don't fit your style, try VladStudio.
root@quatro src$ uname -a SunOS quatro 5.11 snv_133 i86pc i386 i86pc Solaris root@quatro src$ pkg search gcc Segmentation Fault (core dumped) root@quatro src$ exit exit benr@quatro src$ pkg search gcc Segmentation Fault benr@quatro src$ pfexec pkg search gcc INDEX ACTION VALUE PACKAGE description set GCC pkg:/SUNWgccruntime@3.4.3-0.97 description set GCC pkg:/developer/gcc/gcc-libgfortran@4.3.3-0.133 description set GCC pkg:/developer/gcc/gcc-libssp@4.3.3-0.133 description set GCC pkg:/developer/gcc/gcc-libgcc@4.3.3-0.133
Why does IPS still suck? Seriously, we can't catch errors before segfaulting? And people wonder why I claim that IPS and AI are so immature. I just can't wait for Oracle to cram this down my throat.
I want SX:CE back. Anybody in MPK17 listening!?!? Stop telling customers they are stupid for using post-install scripts, stop pontificating about how you know better. ZFS made claims to rightness and proved itself. IPS has yet to convince me.... its had years, and still has yet.