All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: ok, so now my dynamically-linked minit starts after all.  argh.
Date: Fri, 11 Jun 2004 10:27:00 +0300	[thread overview]
Message-ID: <40C95EC4.8040504@intracom.gr> (raw)
In-Reply-To: <Pine.LNX.4.58.0406101346490.18563@localhost.localdomain>


Robert P. J. Day wrote:

>  gack.  after doing a thorough clean of my software tree, and rebuilding
>with a dynamically-linked minit, well, it works.  go figure.
>
>RAMDISK: Compressed image found at block 0
>VFS: Mounted root (ext2 filesystem).
>Mounted devfs on /dev
>Freeing unused kernel memory: 52k init
>Trying run_init_process with /sbin/minit
>FIFOs opened successfully.
>About to start default service.
>(hang)
>
>  in other words, i'm back where i was many days ago -- kernel booting,
>getting to minit, minit starting, then hanging.  but that's ok, given that
>i *expected* things to go south once i got to user space, based on
>previous postings here.
>
>  so, my best strategy at this point would seem to be to do the occasional
>"bk pull", and rebuild to see when i get to go further in user space.  i
>have no clue why a dynamically-linked minit suddenly started to work.
>("no, really, i didn't change anything.  honest." :-)
>
>  i'll be watching for new and exciting developments.
>
>rday
>
>
>
>
>
If you don't happen to have the magical card that Tom seems to have
you also need to comment out the update_mmu_cache function and
replace it with at empty define.

:)

Regards

Pantelis


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2004-06-11  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-10 17:52 ok, so now my dynamically-linked minit starts after all. argh Robert P. J. Day
2004-06-11  7:27 ` Pantelis Antoniou [this message]

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=40C95EC4.8040504@intracom.gr \
    --to=panto@intracom.gr \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rpjday@mindspring.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.