Hey Michael,
tried this out on a saucy vm, and it looked good until it died with
receiving incremental file list
fedora-release-19-2.noarch.rpm
sent 47 bytes received 33329 bytes 9536.00 bytes/sec
total size is 32472 speedup is 0.97
warning: fedora-release-19-2.noarch.rpm: Header V3
After perusing the entire script now,
It seems to me that Michael's major contribution is all after the
parts described in my previous post.
In fact, it looks like Michael grafted his good work on to a Fedora
setup script.
If I'm right, then IMO substantial parts of what I posted about
earlier
On Tue, 2013-09-17 at 10:26 -0700, Tony Su wrote:
Regarding
LXC and the use of Linux Bridge devices for configured networking,
At least on openSUSE, LXC is not configured with any /etc/lxc/* by
default, and possibly because I also have libvirt configured to
support LXC (although that is not
Hey Serge,
On Fri, 2013-09-20 at 09:57 -0500, Serge Hallyn wrote:
Hey Michael,
tried this out on a saucy vm, and it looked good until it died with
receiving incremental file list
fedora-release-19-2.noarch.rpm
sent 47 bytes received 33329 bytes 9536.00 bytes/sec
total size is 32472
On Sun, 2013-09-15 at 16:17 -0700, Tony Su wrote:
Hello Michael,
First a comment on problems with systemd you descrbe.
I probably have run into many of the things you itemized, but since my
time is usually focused on something I'm trying to use LXC and not LXC
itself, I usually just drop
Quoting Michael H. Warfield (m...@wittsend.com):
So, all of this has led Serge to list me on the roster for the
LinuxPlumbers conference as the LXC systemd expert. I'll get even
with him later next week for that one...
Lol! Buy you a beer thu night? :)
-serge
Hello Michael,
First a comment on problems with systemd you descrbe.
I probably have run into many of the things you itemized, but since my
time is usually focused on something I'm trying to use LXC and not LXC
itself, I usually just drop any further attempts and move on to find a
workaround(eg
Cool.
I'll block some significant time to look at what you built over the next 3
days.
Tony
--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012,
On Thu, 2013-09-12 at 15:23 -0400, Michael H. Warfield wrote:
All - Especially Tony Su,
Couple of people where I work thought you couldn't do what I was trying
to do, that it was impossible. Oh well. Looks like they were
wrong. :-P It may not be efficient but it can be made to work.
On Mon, 2013-09-09 at 08:58 +0200, Natanael Copa wrote:
On Sun, 08 Sep 2013 20:33:16 -0400
Michael H. Warfield m...@wittsend.com wrote:
With all due respect...
On Sun, 2013-09-08 at 16:08 -0700, Tony Su wrote:
After putting some thought into this,
IMO LXC badly needs a universal
On Monday, September 09, 2013 07:28:43 AM Michael H. Warfield wrote:
In the git-stage current Fedora template, the entire problem is embodied
in the download_fedora function starting around line 201... The
gotcha's are three commands around line 272 after we've identified and
downloaded the
On Sun, 08 Sep 2013 20:33:16 -0400
Michael H. Warfield m...@wittsend.com wrote:
With all due respect...
On Sun, 2013-09-08 at 16:08 -0700, Tony Su wrote:
After putting some thought into this,
IMO LXC badly needs a universal tool with the following features
- A single script should
On Mon, 2013-09-09 at 17:23 +0530, Shridhar Daithankar wrote:
On Monday, September 09, 2013 07:28:43 AM Michael H. Warfield wrote:
In the git-stage current Fedora template, the entire problem is embodied
in the download_fedora function starting around line 201... The
gotcha's are three
Hello Michael,
Yes, I would really appreciate your comments on what I'm attempting to do.
Here is my thought process...
In general, I've found that the problems you describe are all too
common exactly because no one seems to have sat down and taken a close
look at the flow involved in creating
After putting some thought into this,
IMO LXC badly needs a universal tool with the following features
- A single script should be used to run on any HostOS, creating
any supported Container OS. Although this would make the script
extremely large, IMO it would actually be easier to maintain in
With all due respect...
On Sun, 2013-09-08 at 16:08 -0700, Tony Su wrote:
After putting some thought into this,
IMO LXC badly needs a universal tool with the following features
- A single script should be used to run on any HostOS, creating
any supported Container OS. Although this would
16 matches
Mail list logo
