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: 538546 MD5sum: ebe6c0683900b748b357611144d68d64 SHA1: a5916701135e58826ac3f61a95394c9f5e912ffb SHA256: 36a308005025f56a9ae31eea308d2b7728b0a635a3fad787ba2660e408ae3537 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: 4d30482df367b494b20360cb4a1542cc SHA1: cccdbbd06d3e6cdec1a2fd3081b170098563d81f SHA256: 0e5d11651e9d4358bb7b39cabe56fe5c4eedb37819cc4c0a9e217da267c2fd34 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: 65278 MD5sum: 3044404c4ccdf2f45265c537b76ae0ba SHA1: d77fa300972349e4681d6a9736474a87a777ba48 SHA256: f6d6284108334fbfafcb92311100fc9ab8044a48be78947d45b78f0fc7fd3816 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: 78214 MD5sum: a7791f1d5e92feb0ef7fd61406236937 SHA1: b65077fe5efd486259fd7d160665850bf21ac68e SHA256: 87fecd8bd835caae70fca80721f62238915c3c27c7951574fef862cb711b09f4 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: 36616 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: 11681358 MD5sum: 2713593adc595399390656daac89c4f5 SHA1: c86257ee35b251cc6bcc7c773dc521c3cc1ae2ad SHA256: 4ced7c63e606ac2886c00b2941bdda1720f368992544bc0e814e28bade46020a 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: 42548 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: 12413628 MD5sum: df37c0901ad2824cf4a0c4ebdbe81dcc SHA1: 404b8c2cf26b51c0c1ebff55ec27b13746c104d0 SHA256: 7f27de6278c9c7f95ee81b6a6ef119f91068b557cfdf486dc764cc09b66306f2 Section: utils Description: QEMU user-mode can launch processes compiled for one CPU on another CPU.