linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: James Don <JDon@spacebridge.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: RAMDISK IMAGES(2): ash has no job control ??? ... can't acces s tt y; job control turned off
Date: Mon, 13 Jan 2003 16:19:49 +0100	[thread overview]
Message-ID: <20030113151954.CB784C608E@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 13 Jan 2003 09:57:12 EST." <DB0585C9F6F9D411BE8F00D0B7896A4CC0603E@SNCMAIL>


In message <DB0585C9F6F9D411BE8F00D0B7896A4CC0603E@SNCMAIL> you wrote:
>
> Ps I have SELF and ELDK downloaded ... but never installed ELDK ... should
> the patch be in SELF (it seems not to be)?

As mentioned before, the ELDK includes a modified (newer) version  of
SELF, which is based on binaries already available in the ELDK. So it
uses the standard login binary, which includes the patch.

The SELF image can be  found  in  /opt/eldk/<cpu_type>/images/  ;  it
installs from the SELF RPM.


Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
It is not best to swap horses while crossing the river.
- Abraham Lincoln

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

  reply	other threads:[~2003-01-13 15:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13 14:57 RAMDISK IMAGES(2): ash has no job control ??? ... can't acces s tt y; job control turned off James Don
2003-01-13 15:19 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-14  1:00 James Don
     [not found] <DB0585C9F6F9D411BE8F00D0B7896A4CC0603B@SNCMAIL>
2003-01-12 22:39 ` Wolfgang Denk
2003-01-12 19:34 James Don
2003-01-12 20:19 ` Wolfgang Denk

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=20030113151954.CB784C608E@atlas.denx.de \
    --to=wd@denx.de \
    --cc=JDon@spacebridge.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).