'chroot' is an isolation/security mechanism. It doesn't allow programs running within it to access anything except the kernel and the programs/libraries within the chroot. For what you are doing, think of it as a file system tree that you can test most of your boot environment (short of booting) prior to needing to actually boot it. And because it is just a command away, it is fast to change and experiment.
On Thu, Dec 28, 2017 at 8:13 AM, Richard Owlett <[email protected]> wrote: > Those are among the pages that confused me long ago. > > They, without adequate background, say to use "chroot". > My visualization of using debootstrap is to place Debian on a write only > medium. > The descriptions of "chroot" I've seen imply it's a crude VM like thingy. > > > > On 12/28/2017 09:30 AM, David Bridges wrote: > >> Search for debootstrap, the link provided earlier was for an extremely >> old version of Debian although a search for dbootstrap debian | debian >> dbootstrap in search engines finds current documentation >> >> debootstrap wiki page >> https://wiki.debian.org/Debootstrap >> >> Current Debian install guide >> https://www.debian.org/releases/stable/amd64/index.html.en >> >> debootstrap section in current install guide >> https://www.debian.org/releases/stable/amd64/apds03.html.en#idm46300556 >> 432288 >> >> To me this doesn't really sound like what you are looking for but only >> you can know for sure. >> >> -- >> David >> >> > > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
