public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Sharing /home and swap
Date: Wed, 28 Dec 2011 14:01:23 +0800	[thread overview]
Message-ID: <1325052084.1630.1066.camel@bunyip> (raw)
In-Reply-To: <4EFAAB1E.6020803@wht.com.au>

bunyip ~ # esearch VirtualBox
[ Results for search key : VirtualBox ]
[ Applications found : 8 ]

*  app-emulation/virtualbox
      Latest version available: 4.0.12
      Latest version installed: [ Not Installed ]
      Size of downloaded files: 67,936 kB
      Homepage:    http://www.virtualbox.org/
      Description: Family of powerful x86 virtualization products for
enterprise as well as home use
      License:     GPL-2

...


I'd recommend vbox then ... just works.  Almost as easy as dual boot and
less risk to the base system (i.e., getting the disk order wrong on
install and overwriting the existing OS) - by the way sharing your home
directory (vs /home as a different user) is fraught - many apps use
different configs depending on versions - 'evolution' for instance could
really break your email as later versions switch to a database format
and subsequent versions fiddle with it.

Install it, open vbox-manager from the menu and create a new VM with
whatever specs you want, put the CD for suse in and point the Vbox CD to
it in setup and "go".  You might need to read up on kernel options for
virtualisation if you have a customised kernel vs genkernel to get the
best (almost native) performance.

Love vms for dev work - snapshot it regularly so you can wind back the
clock when necessary ...

BillK

 

-----Original Message-----
From: Andrew Lowe <agl@wht.com.au>
Reply-to: gentoo-user@lists.gentoo.org
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Sharing /home and swap
Date: Wed, 28 Dec 2011 13:37:34 +0800

On 28/12/2011 1:30 PM, W.Kenworthy wrote:
> If its only one app, why not use a small vm (qemu, vbox etc.)? - best of
> both worlds.

Basically because I've done nothing with these thingies and have no 
experience with them and therefore didn't think of them...... Might be 
worth looking into - got a link to a "20 words or less" intro?

>
> Also, why only on Suse? - you can often work around differences with
> ld-preload and other tricks.

The third party app is under development, I'm tying some stuff into it, 
and things are a bit fluid at the moment. I think basically taking a 
couple of hours to set something up once and that's it is quicker than 
trying to work around library problems that will arise in an ongoing manner.

>
>
> BillK
>


	Andrew





      reply	other threads:[~2011-12-28  6:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28  2:21 [gentoo-user] Sharing /home and swap Andrew Lowe
2011-12-28  2:28 ` Adam Carter
2011-12-28  2:32   ` Andrew Lowe
2011-12-28  2:37 ` Nilesh Govindarajan
2011-12-28  2:49   ` Pandu Poluan
2011-12-28  5:26     ` Andrew Lowe
2011-12-28  5:40       ` Michael Mol
2011-12-28  9:14       ` Neil Bothwick
2011-12-28  2:44 ` [gentoo-user] " Nikos Chantziaras
2011-12-28  2:46 ` [gentoo-user] " Peter Humphrey
2011-12-28  5:30 ` W.Kenworthy
2011-12-28  5:37   ` Andrew Lowe
2011-12-28  6:01     ` W.Kenworthy [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=1325052084.1630.1066.camel@bunyip \
    --to=billk@iinet.net.au \
    --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