Package Details: clean-chroot-manager 2.227-1

Git Clone URL: https://aur.archlinux.org/clean-chroot-manager.git (read-only, click to copy)
Package Base: clean-chroot-manager
Description: Wrapper for managing clean chroot builds with local repo therein.
Upstream URL: https://github.com/graysky2/clean-chroot-manager
Licenses: MIT
Conflicts: clean_chroot_manager
Replaces: clean_chroot_manager
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 64
Popularity: 0.24
First Submitted: 2013-08-18 16:52 (UTC)
Last Updated: 2024-05-16 16:47 (UTC)

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 Next › Last »

graysky commented on 2015-03-29 11:56 (UTC)

Bump to v2.66-1 Changelog: Minor updates to man page. Commit: https://github.com/graysky2/clean-chroot-manager/compare/v2.65...v2.66

graysky commented on 2015-02-05 22:53 (UTC)

Bump to v2.65-1 Changelog: Add zsh-completion and cosmetic fix-up of Makefile. Commit: https://github.com/graysky2/clean-chroot-manager/compare/v2.64...v2.65

graysky commented on 2015-01-27 12:33 (UTC)

Bump to v2.64-1 Changelog: Fix user detect under tmux and urxvt. Commit: https://github.com/graysky2/clean-chroot-manager/compare/v2.61...v2.64

graysky commented on 2015-01-24 16:07 (UTC)

Bump to v2.62-1 Changelog: Minor note added to skel. Commit: https://github.com/graysky2/clean-chroot-manager/compare/v2.61...v2.62

graysky commented on 2015-01-15 21:37 (UTC)

Execute commands in the chroot? This package merely controls the devtools scripts for building in a clean environment... what you want is out of scope. I believe you want a totally separate package for that called schroot. See the wiki. https://wiki.archlinux.org/index.php/Schroot EDIT: wait, guess we need to define what you wanna do... just doing operations in the clean-chroot can be done as you posted below I believe... if however you wanna have a sandbox in a chroot, and run something from within it, that is what schroot can do.

ceri commented on 2015-01-15 21:33 (UTC)

@graysky That works too, but I wanted to figure out how to execute commands in the chroot in any case.

graysky commented on 2015-01-15 20:58 (UTC)

I have a line in /etc/fstab setting up the tmpfs: tmpfs /scratch tmpfs nodev,size=28G 0 0 And I have systemd create the two dirs for me with /etc/tmpfiles.d/tmpfs_dirs.conf which contains: d /scratch/.chroot64 0755 facade users - d /scratch/.chroot32 0755 facade users -

coderkun commented on 2015-01-15 16:27 (UTC)

graysky: How do you set the tmpfs up and make sure that it is built at boot?

graysky commented on 2015-01-15 15:22 (UTC)

Or just nuke and rebuild your chroot.. My system has quite a bit of RAM so I actaully put $CHROOT in tmpfs which is good for several reasons, speed, no wear to my ssd, and it always gets built freshly when I reboot.

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 Next › Last »