public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Ben Brenson <benbrenson89@googlemail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: PRoot experiments
Date: Fri, 20 Oct 2017 02:21:19 -0700 (PDT)	[thread overview]
Message-ID: <543a11a3-f3e2-4194-911a-c876099076e1@googlegroups.com> (raw)
In-Reply-To: <1508489537.13007.4.camel@denx.de>


[-- Attachment #1.1: Type: text/plain, Size: 2254 bytes --]

Am Freitag, 20. Oktober 2017 10:52:27 UTC+2 schrieb Claudius Heine:
>
> Hi, 
>
> On Fri, 2017-10-20 at 10:18 +0200, 'Ben Brenson' via isar-users wrote: 
> > Yes, but chroot itself is not working, which is called from 
> > multistrap when 
> > creating a rootfs with same architecture as the host system. 
>
> As far as I understand, Alex ignored this chroot issue, because he 
> triggers the package configuration manually using proot at the end. 
>
> > I also didn't specify a setupscript and my multistrap.conf looks as 
> > follows: 
> > 
> > [General] 
> > noauth=false 
> > unpack=true 
> > bootstrap=debian-stretch 
> > aptsources=debian-stretch 
> > 
> > [debian-stretch] 
> > source=http://deb.debian.org/debian 
> > suite=stretch 
> > components=main contrib non-free 
> > packages= 
> > 
> > 
> > May it be possible to provide a self contained version of multistrap? 
> > Or 
> > would that be a No-Go? 
>
> Since the multistrap project is dead, it would be ok to have a few 
> patches on it to make it fit our purpose IMO. But we are more inclined 
> to move to some other more supported bootstrapping mechanism. Maybe try 
> to put some of our needed features into upstream project. Time spend 
> there might be better used than trying to ride a dead horse. 
>
> Cheers, 
> Claudius 
>
> -- 
> DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk 
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany 
> Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: c...@denx.de 
> <javascript:> 
>
>             PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153 
>                               Keyserver: hkp://pool.sks-keyservers.net



Ok,

Since the multistrap project is dead, it would be ok to have a few 
> patches on it to make it fit our purpose IMO. But we are more inclined 
> to move to some other more supported bootstrapping mechanism. Maybe try 
> to put some of our needed features into upstream project. Time spend 
> there might be better used than trying to ride a dead horse.  
>

Are there any proposals or ideas, yet?
Sounds for me like, having a mixture of multistrap and proot (at least no 
chroot) or somthing like that, would fit better to our needs.

Regards,
Benedikt
 


[-- Attachment #1.2: Type: text/html, Size: 3893 bytes --]

      reply	other threads:[~2017-10-20  9:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 12:29 Alexander Smirnov
2017-10-19  8:59 ` Henning Schild
2017-10-19 10:10 ` Ben Brenson
     [not found] ` <b0082bee-94d7-48c6-8582-93efc4171b59@googlegroups.com>
2017-10-19 10:14   ` Alexander Smirnov
2017-10-19 10:39     ` Claudius Heine
2017-10-19 10:44       ` Benedikt Niedermayr
2017-10-19 11:08         ` Claudius Heine
2017-10-19 11:15           ` Benedikt Niedermayr
2017-10-19 11:37             ` Alexander Smirnov
2017-10-19 11:36           ` Benedikt Niedermayr
2017-10-19 11:40             ` Alexander Smirnov
2017-10-19 13:37               ` Ben Brenson
2017-10-20  8:18               ` Ben Brenson
2017-10-20  8:52                 ` Claudius Heine
2017-10-20  9:21                   ` Ben Brenson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=543a11a3-f3e2-4194-911a-c876099076e1@googlegroups.com \
    --to=benbrenson89@googlemail.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox