I use Fedora 64 bits on my workstation but I need 32 bits chroot of Debian. It is easy to do. Create the chroot following the instructions from: http://blog.parahard.com/2013/03/creating-debian-chroot-inside-fedora.html The first difference is that you need to add --arch=i386 to the debootstrap command. Then for entering the chroot add linux32 as the first argument after sudo. Something like: $ sudo linux32 chroot debian-wheezy After that even uname -a will show 32 bits instead of 64. The linux32 tool is on the util-linux Fedora package.
I use Fedora on the Desktop but I need to do some development on Debian. chroots gives you no performance overhead, while virtual machines gives you CPU and memory insulation. Also the chroot is only a directory on my development tree. I'm using Fedora 17 on my workstation and Debian 7 inside the chroot. The debootstrap command will save the files on the directory debian7-chroot/ under the current directory. 1 - Install debootstrap and dpkg on Fedora: Fedora # yum install debootstrap dpkg 2 - Create the basic Debian: Fedora # debootstrap wheezy debian7-chroot/ http://ftp.fr.debian.org/debian 3 - Enter your new Debian: Fedora # chroot /path/to/destdir 4 - Install additional useful packages: debian-chroot: # apt-get install locales less vim openssh-server sudo aptitude 5 - Configure openssh server to start server on port 2222: debian-chroot: # vi /etc/ssh/sshd_config Chage: Port 22 To: Port 2222 6 - Change root password debian-chroot: # p...
Coccinellery is a gallery of semantic patches made to inspire users of Coccinelle. Currently the semantic patches comes from patches we have submitted to the Linux Kernel. We are working on improving Coccinellery and your suggestions and contributions are welcome. http://coccinellery.org/ "Coccinelle is a program matching and transformation engine which provides the language SmPL (Semantic Patch Language) for specifying desired matches and transformations in C code. Coccinelle was initially targeted towards performing collateral evolutions in Linux. Such evolutions comprise the changes that are needed in client code in response to evolutions in library APIs, and may include modifications such as renaming a function, adding a function argument whose value is somehow context-dependent, and reorganizing a data structure. Beyond collateral evolutions, Coccinelle is successfully used (by us and others) for finding and fixing bugs in systems code." From: http://coc...
Comments