Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #203158

Re: Setting up a chroot on a Jessie system to compile a program using sid

From "Alexander V. Makartsev" <avbetev@gmail.com>
Newsgroups linux.debian.user
Subject Re: Setting up a chroot on a Jessie system to compile a program using sid
Date 2018-12-08 09:00 +0100
Message-ID <x2FGN-6gz-1@gated-at.bofh.it> (permalink)
References <x2BDb-3QQ-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On 08.12.2018 8:36, rhkramer@gmail.com wrote:
> This is sort of a continuation of the thread started with the post 
> "Recommendation for Virtual Machine and Instructions to set it up?" 
>
> (https://lists.debian.org/debian-user/2018/12/msg00144.html)
>
> Aside: the programmer has been able to send me a binary which does work on my 
> Jessie system, but, never-the-less, I plan to start experimenting with either 
> a chroot or VM environment to run either sid or a recent Ubuntu release so 
> that I can compile / build the binary myself.
>
> The machine I want to do this on does not have any unallocated partitions / 
> disk space.  There are two partitions, currently used for other purposes, that 
> I could free up to use for the chroot (or, later, VM) by moving files around.
>
> The Question:
>
> One of the partitions I could free up is 16 GB, the other is 54 GB -- I'd 
> rather free up and use the smaller one, but I'm wondering if that will be big 
> enough?
>
You are over-complicating things. You can build chroot in just a
separate folder using debootstrap.
chroot is not fully fledged VM in meaning of hardware abstraction. It is
just a way to make files (executables, libraries, settings) inside a
folder "/opt/chroot-sid-amd64/" *believe* they are in "/".
So if you change some settings inside chroot "/etc/" they will actually
be changed in "/opt/chroot-sid-amd64/etc/". This is why chroot is
convenient to try things, install tons of -dev and dependency packages
without cluttering or breaking actual working system.
I recommend to read manuals for "debootstrap" and also "schroot" can
make creating multiple chroot-ed environments more straight forward,
eliminating the need to setup some settings manually, such as bind mount
system partitions like "/sys" into chroot.

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀ 

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Setting up a chroot on a Jessie system to compile a program using sid rhkramer@gmail.com - 2018-12-08 04:40 +0100
  Re: Setting up a chroot on a Jessie system to compile a program  using sid Andy Smith <andy@strugglers.net> - 2018-12-08 08:50 +0100
  Re: Setting up a chroot on a Jessie system to compile a program using  sid "Alexander V. Makartsev" <avbetev@gmail.com> - 2018-12-08 09:00 +0100
    Re: Setting up a chroot on a Jessie system to compile a program using sid rhkramer@gmail.com - 2018-12-08 15:30 +0100
      Re: Setting up a chroot on a Jessie system to compile a program  using sid Roberto C. Sánchez <roberto@debian.org> - 2018-12-08 16:20 +0100
      Re: Setting up a chroot on a Jessie system to compile a program using  sid "Alexander V. Makartsev" <avbetev@gmail.com> - 2018-12-08 16:30 +0100
      Re: Setting up a chroot on a Jessie system to compile a program using  sid Carl Fink <carlf@panix.com> - 2018-12-08 17:30 +0100
  Re: Setting up a chroot on a Jessie system to compile a program using  sid David Christensen <dpchrist@holgerdanske.com> - 2018-12-08 19:40 +0100

csiph-web