public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Allen Curtis" <acurtis@onz.com>
To: "Patrick Allaire" <pallaire@gameloft.com>,
	"David Woodhouse" <dwmw2@infradead.org>
Cc: "Björn Eriksson" <mdeans@algonet.se>, linux-mtd@lists.infradead.org
Subject: RE: From 2.4.9 to CVS ???
Date: Fri, 4 Jan 2002 09:04:48 -0800	[thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFGEDBDDAA.acurtis@onz.com> (raw)
In-Reply-To: <9A1957CB9FC45A4FA6F35961093ABB8406456EDF@srvmail-mtl.montreal.ubisoft.org>

Try putting a couple kprint() statements in init/main.c where it is trying
to load init. That is how I found the problem. (Did you check the loader?)
The problem I had was that the executable was found but a suitable loader
was not.....

> -----Original Message-----
> From: linux-mtd-admin@lists.infradead.org
> [mailto:linux-mtd-admin@lists.infradead.org]On Behalf Of Patrick Allaire
> Sent: Friday, January 04, 2002 9:01 AM
> To: David Woodhouse; Patrick Allaire
> Cc: Björn Eriksson; linux-mtd@lists.infradead.org
> Subject: RE: From 2.4.9 to CVS ???
>
>
> I really dont understand ... I have a sh link in /bin ... but it is not
> found by the kernel ... and my cramfs didnt changed a bit !!!
>
> in /bin, I have a link : sh -> busybox
>
> Patrick Allaire
> mailto:pallaire@gameloft.com
> If you can see it, but it's not there, it's virtual.
> If you can't see it, but it is there, it's hidden.
> It you can't see it and it isn't there, it's gone.
>
>
>
> > -----Original Message-----
> > From: David Woodhouse [mailto:dwmw2@infradead.org]
> > Sent: January 4, 2002 11:54 AM
> > To: Patrick Allaire
> > Cc: Björn Eriksson; linux-mtd@lists.infradead.org
> > Subject: Re: From 2.4.9 to CVS ???
> >
> >
> >
> > pallaire@gameloft.com said:
> > >  No I dont have 'bad cramfs magic' !!! I tought it could be the case
> > > ... but I looked at the mkcramfs.c from the 2.4.9 and 2.4.17 version
> > > and there is no difference So the generated code should be
> > the same.
> >
> > P'raps we started paying attention to execute bits on
> > libraries between
> > 2.4.9 and 2.4.17? I thought we did that a long time ago though.
> >
> > Put a statically linked shell in the cramfs and boot with
> > that as init.
> > Then try running /sbin/init and see what errors you get.
> >
> >
> > --
> > dwmw2
> >
> >
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

  parent reply	other threads:[~2002-01-04 17:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04 17:01 From 2.4.9 to CVS ??? Patrick Allaire
2002-01-04 17:01 ` David Woodhouse
2002-01-04 17:04 ` Allen Curtis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-04 19:07 Patrick Allaire
2002-01-04 18:38 Patrick Allaire
2002-01-04 16:51 Patrick Allaire
2002-01-04 16:54 ` David Woodhouse
2002-01-04 16:19 Patrick Allaire
2002-01-04 16:24 ` Allen Curtis
2002-01-04 16:40 ` Björn Eriksson

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=NCBBIINEHIPFGJPLBEIFGEDBDDAA.acurtis@onz.com \
    --to=acurtis@onz.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mdeans@algonet.se \
    --cc=pallaire@gameloft.com \
    /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