public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <prh@gotadsl.co.uk>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re: Installing into a 32-bit chroot?
Date: Wed, 07 Sep 2005 09:00:41 +0100	[thread overview]
Message-ID: <431E9E29.70308@gotadsl.co.uk> (raw)
In-Reply-To: <1126037681.10070.47.camel@thor.tres.org>

Tres Melton wrote:

> Somewhere in this thread is the mention of ssh to run a 32 bit program.
> That is a poor solution in my opinion.  The suggestion was made to mount
> the /tmp dirs and other things and I do this at boot.  Further I have
> written a program that will allow any user (approved by the sudoers file
> in the chroot and the regular root) to run any program from wherever
> they are without the headache of becoming root, etc..  Here ya go:
> 
> #!/bin/bash
> #
> #  Written and Copyright by Tres Melton (2005)
> #
> #  Run a 32 bit program from 64 bit space
> #
> #       If parameters given then execute the command instead of /bin/bash
> #       If no parameters then create a new 32 bit chroot jail shell
> #
> 
> JAIL_DIR="/mnt/sdb3/Gentoo-32"
> 
> if [ $# -eq 0 ] ; then
>   echo "Starting 32 bit shell..."
>   /bin/linux32 sudo chroot ${JAIL_DIR} /usr/bin/sudo -u "#${UID}" bash -c "( cd ~ ; /bin/bash )"
> else
>   echo "Starting a 32 bit shell to run \"$*\""
>   /bin/linux32 sudo chroot ${JAIL_DIR} /usr/bin/sudo -u "#${UID}" bash -c "( cd ~ ; $* )"
> fi
> 
> Hope that helps some.  Regards,

Certainly does - thanks Tres.

-- 
Rgds
Peter Humphrey
Linux Counter 5290, Aug 93.
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2005-09-07  8:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-04 16:02 [gentoo-amd64] Installing into a 32-bit chroot? Peter Humphrey
2005-09-04 21:14 ` [gentoo-amd64] " Duncan
2005-09-06 20:14   ` Tres Melton
2005-09-07  8:00     ` Peter Humphrey [this message]
2005-09-07 14:09     ` Billy Holmes
2005-09-05  1:56 ` [gentoo-amd64] " David Fellows
2005-09-05  3:08   ` Barry.SCHWARTZ

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=431E9E29.70308@gotadsl.co.uk \
    --to=prh@gotadsl.co.uk \
    --cc=gentoo-amd64@lists.gentoo.org \
    /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