From: Albert Hopkins <marduk@letterboxes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT virtual stuff] gentoo vm appliance
Date: Thu, 23 Jun 2011 12:52:00 -0400 [thread overview]
Message-ID: <1308847923.3979.3.camel@localhost.localdomain> (raw)
In-Reply-To: <4E036A80.2040802@gmail.com>
On Thursday, June 23 at 12:32 (-0400), Matthew Finkel said:
> On 06/23/11 07:15, Albert Hopkins wrote:
> >
> > On Thursday, June 23 at 00:35 (-0400), Matthew Finkel said:
> >
> >> Oh, don't get me wrong, that's one reason I use qcow2 myself, but it's
> >> either something he would have to deal with when he received it or the
> >> conversion would increase the size of the disk image that would be
> >> shipped to him.
> > Yes, of course a raw image file will typically be bigger than a
> > compressed qcow, just as an unpacked stage4..tar.bz2 file is going to be
> > bigger than the original archive. But in terms transferability,
> > compressed qcows are more efficient since they only include *used*
> > blocks and they are compressed. I can convert the image into any of a
> > number of formats, but the issue then is it will be bigger, and thus
> > take me longer to upload it and the OP to download it
> Yup, exactly :-)
>
I've uploaded a (390MB) vmdk. I've been told by someone that it works
with vmware (not sure what version).
This was build just a few minutes ago with the latest stage3 tarball and
the latest portage snapshot.
http://starship.python.net/crew/marduk/base.vmdk
The root password is blank. It will force you to change it on first
login.
next prev parent reply other threads:[~2011-06-23 16:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 21:52 [gentoo-user] [OT virtual stuff] gentoo vm appliance Harry Putnam
2011-06-22 22:32 ` Mark Knecht
2011-06-22 23:58 ` [gentoo-user] " Harry Putnam
2011-06-22 22:49 ` [gentoo-user] " kashani
2011-06-22 23:59 ` [gentoo-user] " Harry Putnam
2011-06-23 0:11 ` [gentoo-user] " Albert Hopkins
2011-06-23 1:31 ` Matthew Finkel
2011-06-23 2:14 ` Albert Hopkins
2011-06-23 4:35 ` Matthew Finkel
2011-06-23 11:15 ` Albert Hopkins
2011-06-23 16:32 ` Matthew Finkel
2011-06-23 16:52 ` Albert Hopkins [this message]
2011-06-25 17:10 ` Albert Hopkins
2011-06-27 23:47 ` James Wall
2011-06-28 0:46 ` Albert Hopkins
2011-06-28 3:44 ` James Wall
2011-06-28 13:07 ` Albert Hopkins
2011-06-28 14:32 ` James Wall
2011-06-28 14:57 ` Albert Hopkins
2011-06-28 16:19 ` Albert Hopkins
2011-07-01 15:36 ` [gentoo-user] " Harry Putnam
2011-07-01 15:50 ` Harry Putnam
2011-07-01 15:55 ` Albert Hopkins
2011-07-01 16:06 ` Albert Hopkins
2011-07-01 16:42 ` Harry Putnam
2011-07-01 17:56 ` Albert Hopkins
2011-07-01 19:10 ` Harry Putnam
2011-07-01 20:01 ` Alex Schuster
2011-07-01 20:02 ` Albert Hopkins
2011-07-01 22:44 ` James Wall
2011-07-01 23:23 ` Albert Hopkins
2011-07-02 0:22 ` Harry Putnam
2011-07-02 0:37 ` Albert Hopkins
2011-07-01 17:59 ` Albert Hopkins
-- strict thread matches above, loose matches on Subject: below --
2011-06-23 1:16 [gentoo-user] " Pandu Poluan
2011-06-23 2:16 ` Albert Hopkins
2011-06-23 7:54 ` Joost Roeleveld
2011-06-23 11:18 ` Albert Hopkins
2011-06-23 11:45 ` Joost Roeleveld
2011-06-23 13:12 ` Albert Hopkins
2011-06-23 14:13 ` Pandu Poluan
2011-06-23 16:49 ` Joost Roeleveld
2011-06-23 14:11 ` Pandu Poluan
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=1308847923.3979.3.camel@localhost.localdomain \
--to=marduk@letterboxes.org \
--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