fakechroot
fakechroot copied to clipboard
dex4er
gives a fake chroot environment
I'm creating this merge request to keep track of the patch stack we carry in Debian on top of fakechroot 2.20.1. These are mostly the same patches that are also...
On Debian unstable armhf and glibc 2.37 I get this build failure: ``` /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 -Werror=implicit-function-declaration...
based on `man execvp` in ubuntu linux > If the header of a file isn't recognized (the attempted execve(2) failed with the error ENOEXEC), these functions will execute the shell...
I took a [(piece-of-crap) benchmarks](https://codeberg.org/eownerdead/proot-vs-fakechroot) of chroot, proot, fakechroot and bubblewrap. It shows that fakeroot and proot are nearly twice as slow as chroot, but fakechroot is a bit faster....
I am trying to run [udocer](https://github.com/indigo-dc/udocker) on AWS lambda using arm64 but it's giving error of not able to find libfakechroot-Alpine-3-arm64.so, libfakechroot-Alpine-arm64.so. Anyone can help me in getting all these...
Fixes https://github.com/dex4er/fakechroot/issues/114
It is already almost two years since last release and in git repo is ATM commited +1k commits. It would be really good to make new release .. please :)
## steps to reproduce crash.c ```c #include #include #include int main(int argc, char **argv) { char foo[4]; readlink("/etc/localtime", foo, atoi(argv[1])); return 0; } ``` `cc -O1 -D_FORTIFY_SOURCE=2 -o crash crash.c`...
Hi, this time build fails in all arches i.e. i686, x86_64, aarch64, ppc64le and s390x [1] it can be reproduced in Fedora 38 beta. Removing -d option make test pass...
Steps to reproduce (inside the fakechroot): ```shell $ mkdir foo $ touch foo/bar $ rm -r foo rm: cannot remove '/foo': Is a directory ``` ``` $ echo foo >...