Package: care Version: 2.1.0-1 Architecture: i386 Maintainer: Cédric VINCENT Installed-Size: 1300 Filename: ./i386/care_2.1.0-1_i386.deb Size: 538514 MD5sum: f938f20992a159cc4e03b98bbdbaa0ae SHA1: 34beee169b10657cf41fbe2e72d2d84b7e4dda25 SHA256: db69de23a887e723faef7dba03b4d6a7bc92f82502e664711418cb4741b29856 Section: utils Description: Comprehensive Archiver for Reproducible Execution CARE monitors the execution of the specified command to create an archive that contains all the material required to re-execute it in the same context. That way, the command will be reproducible everywhere, even on Linux systems that are supposed to be not compatible with the original Linux system. CARE is typically useful to get reliable bug reports, demonstrations, academic experiences, tutorials, portable applications, minimal rootfs, file-system coverage, ... By default, the reproduced execution uses environment variables and files from the archive, not from the actual Linux system. However, events external to the monitored programs -- like key strokes or network packets -- are not archived; it's up to the user to automatize or document such external interaction. Package: care Version: 2.1.0-1 Architecture: amd64 Maintainer: Cédric VINCENT Installed-Size: 1340 Filename: ./amd64/care_2.1.0-1_amd64.deb Size: 553852 MD5sum: bf84653db879d9d2ba2a9f185903cd01 SHA1: 35960dc1801ed1e78809b08cbdf0af23985a18c4 SHA256: fc7b0c4bee9d63aba6c2343cb5165fe3581892226062a25b773402021cff0021 Section: utils Description: Comprehensive Archiver for Reproducible Execution CARE monitors the execution of the specified command to create an archive that contains all the material required to re-execute it in the same context. That way, the command will be reproducible everywhere, even on Linux systems that are supposed to be not compatible with the original Linux system. CARE is typically useful to get reliable bug reports, demonstrations, academic experiences, tutorials, portable applications, minimal rootfs, file-system coverage, ... By default, the reproduced execution uses environment variables and files from the archive, not from the actual Linux system. However, events external to the monitored programs -- like key strokes or network packets -- are not archived; it's up to the user to automatize or document such external interaction. Package: proot Version: 5.1.0-1 Architecture: i386 Maintainer: Cédric VINCENT Installed-Size: 188 Depends: libc6 (>= 2.3), libtalloc2 (>= 2.0.4~git20101213) Filename: ./i386/proot_5.1.0-1_i386.deb Size: 64078 MD5sum: 390d5fd43d0f8b486bd12ed61c55b923 SHA1: 3f1261f4cef5914eded7c14e239db02d5716a2f1 SHA256: b98a5b51099a4b7b68642b37d7bcd0905f2aa1d6259c268f0f3b6239dae445b6 Section: utils Description: chroot, mount --bind, and binfmt_misc without privilege/setup PRoot is a user-space implementation of chroot, mount --bind, and binfmt_misc. This means that users don't need any privileges or setup to do things like using an arbitrary directory as the new root filesystem, making files accessible somewhere else in the filesystem hierarchy, or executing programs built for another CPU architecture transparently through QEMU user-mode. Also, developers can add their own features or use PRoot as a Linux process instrumentation engine thanks to its extension mechanism. Technically PRoot relies on ptrace, an unprivileged system-call available in every Linux kernel. Package: proot Version: 5.1.0-1 Architecture: amd64 Maintainer: Cédric VINCENT Installed-Size: 2260 Depends: libc6 (>= 2.3), libtalloc2 (>= 2.0.4~git20101213) Filename: ./amd64/proot_5.1.0-1_amd64.deb Size: 76622 MD5sum: 59c32f976fcf0dc44deabe8ad1531641 SHA1: e3831f37ed9868e235dd98723143b236f86bb652 SHA256: cdda77d0b155ab726040fcb766c35e99a2f1744614cae48ee071f9c48e021efd Section: utils Description: chroot, mount --bind, and binfmt_misc without privilege/setup PRoot is a user-space implementation of chroot, mount --bind, and binfmt_misc. This means that users don't need any privileges or setup to do things like using an arbitrary directory as the new root filesystem, making files accessible somewhere else in the filesystem hierarchy, or executing programs built for another CPU architecture transparently through QEMU user-mode. Also, developers can add their own features or use PRoot as a Linux process instrumentation engine thanks to its extension mechanism. Technically PRoot relies on ptrace, an unprivileged system-call available in every Linux kernel. Package: qemu-user-mode Version: 1.6.1-1 Architecture: i386 Maintainer: Cédric VINCENT Installed-Size: 36612 Depends: libc6 (>= 2.11), libglib2.0-0 (>= 2.24.0), zlib1g (>= 1:1.1.4) Filename: ./i386/qemu-user-mode_1.6.1-1_i386.deb Size: 11684256 MD5sum: af199a745b139aa170ae94629ed27e11 SHA1: 1a899b8de3ebf61fe956a660db753f5227e45c72 SHA256: 0f13b8125a44ee02305073f4eb168c34b01d9c0e3dfaa7befeb7d8d3dfb769eb Section: utils Description: QEMU user-mode can launch processes compiled for one CPU on another CPU. Package: qemu-user-mode Version: 1.6.1-1 Architecture: amd64 Maintainer: Cédric VINCENT Installed-Size: 42552 Depends: libc6 (>= 2.11), libglib2.0-0 (>= 2.24.0), zlib1g (>= 1:1.1.4) Filename: ./amd64/qemu-user-mode_1.6.1-1_amd64.deb Size: 12415418 MD5sum: d3b386c521a378f9b92ea161d7c21cfd SHA1: 3f9efb92e60125050ab98d505a3510a5f6712399 SHA256: 895cb73d2aa83304fac98462b7fcc0ba1afb4060798f52f98c1ebcb7faeeb84b Section: utils Description: QEMU user-mode can launch processes compiled for one CPU on another CPU.