Skip to main content
yum or apt-get?

I have been a avid FreeBSD supporter, and before that NetBSD. I started using NetBSD in 1995, and moved to using mostly FreeBSD in 1997. At work as I moved to larger and larger companies, I used way more Linux (Aside from the 80% Windows). Getting more and more busy I started to appreciate the simplicity of Linux and upgrading versus the painstaking upgrading in FreeBSD. Yes FreeBSD is better, but do I have time to compile all of the software and kernels, and do upgrades which are multistep?

build world
build kernel

versus a single command like yum or apt-get?

I really like yum in comparison to the other Linux upgrade systems that RedHat has used before. The problem is that you can't use Yum to move from something like Fedora Core 4 to Fedora Test 5. They say that they are adding this functionality into the upgrade system, but it will be beta for a while, and not really trustworthy yet.

This is why apt rocks, and there is nothing that does as good as job. Its tried and true and just plain works well. The alien commands to rebuild rpms and such works like a charm (not 100% accurate). That's why on my personal servers I run Debian, and love apt. That's where I am now on the lay on the free *NIX land.

Let me know what you guys think?


Popular posts from this blog

Misunderstanding "Open Tracing" for the Enterprise

When first hearing of the OpenTracing project in 2016 there was excitement, finally an open standard for tracing. First, what is a trace? A trace is following a transaction from different services to build an end to end picture. The latency of each transaction segment is captured to determine which is slow, or causing performance issues. The trace may also include metadata such as metrics and logs, more on that later. Great, so if this is open this will solve all interoperability issues we have, and allow me to use multiple APM and tracing tools at once? It will help avoid vendor or project lock-in, unlock cloud services which are opaque or invisible? Nope! Why not? Today there are so many different implementations of tracing providing end to end transaction monitoring, and the reason why is that each project or vendor has different capabilities and use cases for the traces. Most tool users don't need to know the implementation details, but when manually instrumenting wi

NPM is Broken

As someone who bought and implemented NPM solutions, covered them as an analyst, and now watches the industry, one cannot help but notice that NPM(D) is broken. According to Gartner themselves, the data center is rapidly changing, the data center is going away, m aybe not as quickly as Capp states, but it’s happening. This is apparent by the massive public cloud growth posted by Amazon, Microsoft, and Google in their infrastructure businesses. This means that traditional appliance-based NPMD offerings will not work, nor will traditional ways of collecting packet data. Many of the flow offerings do not handle the new types of flows which these services generate, but most importantly they do not understand the internet, which is the most important part of assuring services in cloud hosted environments. The network itself is not just moving to overlay a-la NSX and ACI, it's moving inside of orchestrated containers, and new proxy/load balancing systems typically built off component

F5 Persistence and my 6 week battle with support

We've been having issues with persistence on our F5's since we launched our new product. We have tried many different ways of trying to get our clients to stick on a server. Of course the first step was using a standard cookie persistence which the F5 was injecting. All of our products which use SSL is being terminated on the F5, which makes cookie work fine even for SSL traffic. After we started seeing clients going to many servers, we figured it would be safe to use a JSESSIONID cookie which is a standard Java application server cookie that is always unique per session. We implemented the following Irule (slightly modified in order to get more logging): (registration is free) when HTTP_REQUEST { # Check if there is a JSESSIONID cookie if {[HTTP::cookie "JSESSIONID"] ne ""}{ # Persist off of the cookie value with a timeout of 2 hours (7200 seconds) p