3 private links
The runtime symbol bindings can be displayed by setting LD_DEBUG=bindings:
the search paths of each symbol lookup can be displayed by setting LD_DEBUG=symbols. If this is combined with a bindings request, you can obtain a complete picture of the symbol relocation process.
Dynamically linked shared libraries are an important aspect of GNU/Linux®. They allow executables to dynamically access external functionality at run time and thereby reduce their overall memory footprint (by bringing functionality in when it's needed). This article investigates the process of creating and using dynamic libraries, provides details on the various tools for exploring them, and explores how these libraries work under the hood.
This article explores some of the Linux architectures that support real-time characteristics and discusses what it really means to be a real-time architecture. Several solutions endow Linux with real-time capabilities, and in this article I examine the thin-kernel (or micro-kernel) approach, the nano-kernel approach, and the resource-kernel approach. Finally, I describe the real-time capabilities in the standard 2.6 kernel and show you how to enable and use them.
There are a couple groups of settings below. The first couple go in /etc/sysctl.conf or /etc/sysctl.d/filename.conf.
What is pretty is NetworkManager 0.9.10; it’s like the lightning-quick racing yacht that Larry Ellison doesn’t have and really, really wants, but which somehow also adds a Triple-E-Class-worth of new features just for you.
The course was aimed at C developers who wanted an introduction to both general UNIX-style user-space and Linux kernel development with a focus on embedded systems issues. The course is aimed at two 8-hour days, and is pretty packed in even then.
Recover from a rm -rf at root
Another story: http://lug.wsu.edu/node/414
chmod a+rwX -R
This document looks at the numerous and interesting ways the Linux kernel 2.6 interacts with user space programs. We explain sockets, procfs (and similar virtual filesystems), creating new Linux system calls, as well as mundane file and memory handling.
More on userspace interfaces: http://www.ibm.com/developerworks/library/l-kernel-memory-access/
So what exactly is a container and how is it different from hypervisor-based virtualization? To put it simply, containers virtualize at the operating system level, whereas hypervisor-based solutions virtualize at the hardware level. While the effect is similar, the differences are important and significant, which is why I'll spend a little time exploring the differences and the resulting differences and trade-offs.
Mettre son projet en production, c’est la galère. Tellement que mille méthodes on vu le jour pour automatiser tout ça. Chef, salt, fabric, des script bash, virtualenv, git hooks, etc.
Après, il y a ceux qui utilisent des VM. Qui ont leur propres outils d’automatisation type Vagrant.
Et comme ça suffit pas, des services ce sont mis en place pour faciliter la mise en prod dans le cloud comme heroku, gondor…
Malgré ça, Max fait encore beaucoup de truc à la main parce que “ça marche jamais comme prévu”. Pas très scalable.
Dernièrement, grâce à notre cher Cortex, j’ai découvert un projet écrit en Go nommé Docker, qui propose encore une autre approche du problème.
for i in pidof python
; do cat /proc/$i/cmdline | tr "\0" " " | sed "s/$/ $i\n/"; done
Useful when you have permission problem on which permission policykit handles. (network disk mounting power management ...)