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: Sun, 12 Jan 2003 23:39:34 +0100	[thread overview]
Message-ID: <20030112223939.26B2CC608E@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sun, 12 Jan 2003 15:58:30 EST." <DB0585C9F6F9D411BE8F00D0B7896A4CC0603B@SNCMAIL>


In message <DB0585C9F6F9D411BE8F00D0B7896A4CC0603B@SNCMAIL> you wrote:
>
> 2.) I added line "ttyS1::askfirst:-/bin/sh" to inittab ... and I get
> "Bummer, can't open /dev/ttyS1" ... which was funny enough to make me blow
> coffee out my nose ... whats this tty normally used for?

It is you who defines the use of the serial ports on your board -  we
cannot answer this question.

> 3.) I added line "ttyS0::askfirst:-/bin/sh" to inittab ... and that seems to
> work ...
>
> Three leads to a question ... here it is ...
>
> Should I change 'libbb.h' to open /dev/ttyS0 instead of ttyS ... see line

You probably don't want to make your ramdisk  image  dependend  on  a
specific  board / tty use.

If you look closer at our ELDK you will find that it contains a small
modification to  "login"  (calling  of  TIOCSCTTY  ioctl)  which  was
necessary  to  allow  for  using  /dev/console  as the default serial
console device specified in inittab. See the
build/target_rpms/util-linux/SOURCES/login-eldk.patch
file in the ELDK build environment.

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
Nothing in progression can rest on its original plan. We may as  well
think  of  rocking  a grown man in the cradle of an infant.
- Edmund Burke

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

       reply	other threads:[~2003-01-12 22:39 UTC|newest]

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