search for: chrootabl

...the archive, copy over /etc/resolv.conf, >> bind-mount /dev and /proc, chroot into the directory, and get >> going right away. The point of my first post was to ask about licencing. Regardless of whether I'm sending out a bootable ISO, or a QEMU disk image, or a tarred up chrootable directory, I'm re-distributing Open Source code and/or binaries, which I assume requires appropriate pointers to where they can be obtained. -- Walter Dnes <waltdnes at waltdnes.org>

...is why febootstrap 3.x really excited me until realizing it is for supermin appliances only. What issues and challenges have you already encountered doing something like this? It would be nice, but perhaps impossible to find a mostly distribution neutral way of doing these things. Creating a "chrootable" filesystem and then running image-minimizer seems like a decent plan of attack for me. [1] https://fedoraproject.org/wiki/Ovirt_Node -- Jeff Schroeder Don't drink and derive, alcohol and analysis don't mix. http://www.digitalprognosis.com

On Sat, Feb 11, 2017 at 08:06:49AM -0500, Jonathan Billings wrote > Wouldn't this be easier done as a mock chroot? I realize you're > not building RPMs, but you could use the chroot for building any > software, and on any arbitrary CentOS or Fedora system. 1) Not everybody runs Fedora/Redhat/CentOS 2) The builds I'm doing are targetted at distros, like Puppy linux,

I am a new rsync user and it has been going fine as to nightly rsyncs. On one of the scripts I am getting two kind of errors: 1. @ERROR: chroot failed rsync: connection unexpectedly closed (34 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) and also on the same script to another server, I get no errors but the files are not being mirrored on the