public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Corey" <corey@bitworthy.net>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] unable to chroot
Date: Fri, 17 Nov 2006 17:10:44 -0700	[thread overview]
Message-ID: <200611171710.44274.corey@bitworthy.net> (raw)
In-Reply-To: <789d27b10611171445i627118d2raaabf2e2cd16cba1@mail.gmail.com>

On Friday 17 November 2006 15:45, Hanni Ali wrote:
> A few people have been having problems with this recently
> 
> could I ask what version of crossdev you are using I just checked a new
> build and I've hit the same problem
> 

sys-devel/crossdev-0.9.17-r2


I think in my case it's very likely to be user-error, I do appreciate any
assistance!


Beers,

Corey



-- 
gentoo-embedded@gentoo.org mailing list



  reply	other threads:[~2006-11-18  0:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 21:35 [gentoo-embedded] unable to chroot Corey
2006-11-17 22:15 ` Mike Frysinger
2006-11-17 22:45   ` Hanni Ali
2006-11-18  0:10     ` Corey [this message]
2006-11-18  0:08   ` Corey
2006-11-18  6:35 ` Corey

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=200611171710.44274.corey@bitworthy.net \
    --to=corey@bitworthy.net \
    --cc=gentoo-embedded@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