From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compiling for different CPU but same architecture
Date: Fri, 1 Aug 2014 08:53:51 +0100 [thread overview]
Message-ID: <20140801085351.02b6bf18@digimed.co.uk> (raw)
In-Reply-To: <1406872796.1957.1.camel@wraeth.id.au>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
On Fri, 01 Aug 2014 15:59:56 +1000, wraeth wrote:
> systemd-nspawn is quite a useful utility for working in a chroot -
> almost a complete virtual machine without the overhead.
>
> I also came across a handy introduction to it [1] too, by none other
> than rich0 (one of our esteemed devs) - it's worth a read (particularly
> when you try using it without DEVPTS_MULTIPLE_INSTANCES set - that was
> fun!).
>
> [1]
> http://rich0gentoo.wordpress.com/2014/07/14/quick-systemd-nspawn-guide/
I saw that a couple of weeks ago and thought "I'll try that when I get
time". The time needed turned out to be about 5 minutes, it's so much
easier than using a chroot.
--
Neil Bothwick
WinErr 014: Keyboard locked - Try anything you can think of.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-08-01 7:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 3:53 [gentoo-user] Compiling for different CPU but same architecture Nilesh Govindrajan
2014-08-01 5:46 ` Canek Peláez Valdés
2014-08-01 5:59 ` wraeth
2014-08-01 7:53 ` Neil Bothwick [this message]
2014-08-01 8:01 ` Nilesh Govindrajan
2014-08-01 8:09 ` Neil Bothwick
2014-08-01 8:23 ` wraeth
2014-08-01 8:25 ` Nilesh Govindrajan
2014-08-01 8:37 ` wraeth
2014-08-01 11:45 ` Jc García
2014-08-01 11:51 ` Neil Bothwick
2014-08-01 12:00 ` Jc García
2014-08-01 12:22 ` Nilesh Govindrajan
2014-08-01 13:04 ` Jc García
2014-08-01 12:29 ` Nilesh Govindrajan
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=20140801085351.02b6bf18@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@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