SparkyLinux Now Lets Users Test Drive Linux Kernel 4.7, Here's How to Install It
Just one day after the announcement of the GA release of the Linux 4.7 kernel, the SparkyLinux developers inform their users that they can now test drive the new kernel from the unstable repository.
Clear Linux Is Among the First Distros to Adopt Kernel 4.7, X.Org Server 1.18.4
Today, July 26, 2016, Softpedia was informed by the Clear Linux team about the availability of new software updates for the GNU/Linux operating system designed for the Intel architecture.
With nine days to go, Microsoft really, really wants you to claim your free upgrade to Windows 10. Come to think of it, Microsoft has really, really wanted you to upgrade your Windows 7 or 8.1 PC to Windows 10 for more than a year, and backed it with the GWX subsystem -- first installed by KB 3035583 in March 2015, 15 months ago.
In case you ever wanted to have a Node.js window manager, there's now one that works for X11 environments that works on Chrome OS, Debian, and friends.
After working for several weeks on our WikiRating:Google Summer of Code project Davide, Alessandro and I have slowly reached up to the level where we can now visualize the entire project in its final stages.
More than a week ago I blogged about the new GUI made with GtkBuilder and Glade . Now, I will talk about what has changed since then with the GUI and also the new functionality that has been added to it.
I will start with the new "transition" page which I've added for the key download phase. Before going more in depth, I have to say that the app knows at each moment in what state it is, which really helps in adding more functionality.
During the last weeks, the openSUSE board and others expressed their concern about the current state of some openSUSE infrastructure: especially the reaction times to change something in the setup were mentioned multiple times. Looks like we lost some administrators and/or contact points at SUSE who helped out in the past to eliminate problems or work together with the community.
As result, there was a meeting held during the openSUSE Conference 2016, including some SUSE employees and openSUSE community members to discuss the current situation and search for some possible solutions. The discussion was very fruitful and we’d like to share some of the results here to inform everyone and actively ask for help. If you want to join us, the openSUSE heroes, do not hesitate to contact us and join an incredible team!
Docker is growing by leaps and bounds, and along with it, its ecosystem. Being light, the predominant container deployment involves running just a single app or service inside each container. Most software products and services are made up of at least several such apps/services. We all want all our apps/services to be highly available and fault tolerant. Thus, Docker containers in an organization quickly start popping up like mushrooms after the rain. They multiply faster than rabbits.While, in the beginning, we play with them like cute little pets, as their numbers quickly grow we realize we are dealing with a herd of cattle, implying we’ve become cowboys. Managing a herd with your two hands, a horse, and a lasso will only get you so far. You won’t be able to ride after each and every calf that wonders in the wrong direction. To get back to containers from this zoological analogy—operating so many moving pieces at scale is impossible without orchestration—this is why we’ve seen the rise of Docker Swarm, Kubernetes, Mesos, CoreOS, RancherOS, and so on.
A massive transformation is underway in the way we manage IT infrastructure. More companies are looking for improved agility and flexibility. They are moving from traditional server stacks to cloudy infrastructure to support a new array of applications and services that must be delivered at breakneck pace in order to remain competitive.
Yet Bob does not believe the devops hammer should be used on anything that looks remotely like a nail. Accounting systems, supply chain management systems, warehouse management systems, and so on do not benefit from the constant modification enabled by devops. Those are bound by precise, interlocking processes along with granular permissions and regulations. Here, continuous change invites disaster of the type that ITIL-huggers and OCM (organizational change management) proponents fear most.