Linux Container Development
 help / color / mirror / Atom feed
From: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
Cc: Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [PATCH] liblxc: lxc-debian expects missing directories
Date: Thu, 05 Feb 2009 01:59:03 -0800	[thread overview]
Message-ID: <1233827943.28338.49.camel@localhost> (raw)
In-Reply-To: <1233826174.28338.30.camel@localhost>

On Thu, 2009-02-05 at 01:29 -0800, Matt Helsley wrote:
> On Thu, 2009-02-05 at 10:20 +0100, Daniel Lezcano wrote:
> > Matt Helsley wrote:
> > > lxc-debian fails unless the directories a given rootfs needs already
> > > exist. To fix this without relying on any particular function call order
> > > we can do: mkdir -p `dirname PATH/TO/FILE`
> > > before actually making the file.
> > >
> > > Signed-off-by: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> > > ---
> > >   
> > Do you have an example on how that happens ?
> 
> Configure lxc with a non-/ prefix:
> 
> ./configure --prefix=/usr

This explanation is wrong, sorry.

The patch isn't necessary -- take a look at the one that handles
debootstrap interruption/failure. Basically debootstrap would fail
(apache doesn't exist in lenny I found out) and I'd have to go cleaning
up lxc-debian directories by hand before I could retry. If I missed
something one time then then lxc behaved oddly. This got me past some of
that odd behavior (only to fail later of course).

Cheers,
	-Matt

  reply	other threads:[~2009-02-05  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05  9:05 [PATCH] liblxc: lxc-debian expects missing directories Matt Helsley
2009-02-05  9:20 ` Daniel Lezcano
     [not found]   ` <498AAF77.20906-GANU6spQydw@public.gmane.org>
2009-02-05  9:29     ` Matt Helsley
2009-02-05  9:59       ` Matt Helsley [this message]
2009-02-05 10:21         ` Daniel Lezcano

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=1233827943.28338.49.camel@localhost \
    --to=matthltc-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=daniel.lezcano-GANU6spQydw@public.gmane.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