chroot_package_run(1)

πŸ“¦
version 9.9 Β· 3 versions
, in debian bookworm, ubuntu jammy, ubuntu noble

πŸ’… chroot_package_run(1) πŸ’…

okay bestie, welcome to the chroot_package_run manual, section 1 of the man pages, and honestly? she's a whole vibe. sit down, grab a strawberry πŸ“, and let's get you fluent.


✨ NAME ✨

chroot_package_run β€” repeat a program within the package, with a lil assist from chroot 🫢


🌸 SYNOPSIS 🌸

chroot_package_run --package-path your-package-path [command]

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea β˜• β€” when chroot gets pulled in to help you repeat one experiment, some very specific common directories get remounted into the package. which ones? /proc, /dev, /net, /sys, /var, /misc and /selinux. and the catch? they only get remounted if they exist on your local filesystem. no cap, that's the rule.

the way that she keeps it tidy though β€” after you finish all your tests inside chroot_package_run, every single one of those remounted directories gets unmounted. clean girl energy 🧼✨

and if you don't hand her a command at all? no stress. you just get dropped into a /bin/sh shell instead. iconic behaviour, truly πŸ‘‘


πŸ’– OPTIONS πŸ’–

  • -p, --package-path β€” the path of the package. like, where your package actually lives πŸ“
  • -e, --env-list β€” the path of the environment file, where every line is formatted as <key>=<value>. (Default: package-path/env_list) πŸŽ€
  • -h, --help β€” show this help message. she's helpful like that πŸ’β™€οΈ

⭐ EXIT STATUS ⭐

on success, returns zero. on failure, returns non-zero. simple as that, fr fr.


🌈 EXAMPLES 🌈

say you wanna repeat one program within one package at /tmp/package, inside a bash shell. bestie, you run:

% chroot_package_run --package-path /tmp/package /bin/bash

after the execution of this command, one shell will be returned, where you can repeat your original program. after everything is done, exit chroot_package_run:

% exit

you can also directly set your command as the arguments of chroot_package_run. in this case, chroot_package_run will exit automatically after the command is finished, and you do not need to use exit to exit. however β€” and this is the important part, don't skip it β€” your command must belong to the original command set executed inside parrot_run and preserved by parrot_package_create. πŸ‘€

% chroot_package_run --package-path /tmp/package ls -al

here is a short instruction about how to make use of parrot_run, parrot_package_create and chroot_package_run to generate one package for your experiment and repeat your experiment within your package. three steps, bestie, let's go πŸšΆβ™€οΈ

Step 1: run your program under parrot_run and use --name-list and --env-list parameters to record the filename list and environment variables.

% parrot_run --name-list namelist --env-list envlist /bin/bash

after the execution of this command, you can run your program inside parrot_run. at the end of step 1, one file named namelist containing all the accessed file names and one file named envlist containing environment variables will be generated. after everything is done, exit parrot_run:

% exit

Step 2: use parrot_package_create to generate a package.

% parrot_package_create --name-list namelist --env-path envlist --package-path /tmp/package

at the end of step 2, one package with the path of /tmp/package will be generated. slay πŸ’…

Step 3: repeat your program within your package.

% chroot_package_run --package-path /tmp/package /bin/bash

after the execution of this command, one shell will be returned, where you can repeat your original program. after everything is done, exit chroot_package_run:

% exit

the Cooperative Computing Tools are Copyright (C) 2005-2019 The University of Notre Dame. this software is distributed under the GNU General Public License. see the file COPYING for details. πŸ“œ


πŸ”₯ SEE ALSO πŸ”₯


ok that's the whole page, bestie, you ate that 🍽️✨ go forth and repeat your experiments with main character energy.

that's the wrap from CCTools 8.0.0 DEVELOPMENT β€” mwah, take care of her πŸ’œπŸ¦‹

πŸ“¦ where this page comes from