From: Karsten Scheibler <laml@unusedino.de>
To: linux-assembly@vger.kernel.org
Subject: Re: init.asm - 0.03 (19-Jun-2002) - asmutils 0.18
Date: Fri, 30 May 2008 22:34:54 +0200 [thread overview]
Message-ID: <20080530203539.AB96F7B24@gw.unusedino.de> (raw)
In-Reply-To: <481B7763.50605@verizon.net>
Hello,
>> If I use another type of sh, for example ash from busybox I get the
>> following error and no segfault: "can't access tty, job control turned
>> off".
>
> From the Busybox FAQ:
>
> --------------------
> Why do I keep getting "sh: can't access tty; job control turned off"
> errors? Why doesn't Control-C work within my shell?
>
> Job control will be turned off since your shell can not obtain a
> controlling
> terminal. This typically happens when you run your shell on
> /dev/console.
> The kernel will not provide a controlling terminal on the /dev/console
> device. Your should run your shell on a normal tty such as tty1 or
> ttyS0
> and everything will work perfectly. If you <em>REALLY</em> want your
> shell
> to run on /dev/console, then you can hack your kernel (if you are into
> that
> sortof thing) by changing drivers/char/tty_io.c to change the lines
> where
> it sets "noctty = 1;" to instead set it to "0". I recommend you
> instead
> run your shell on a real console...
> -------------------
Bodo haven't you got my mail from april ?
i've sent you a test program in C to determine if the controlling tty
stuff would fix the problem ... haven't got an answer so far from you
karsten
next prev parent reply other threads:[~2008-05-30 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 15:36 init.asm - 0.03 (19-Jun-2002) - asmutils 0.18 Bodo Giannone
2008-05-01 9:32 ` Frank Kotler
2008-05-02 12:12 ` Faré
2008-05-02 15:46 ` Bodo Giannone
2008-05-02 20:19 ` Frank Kotler
2008-05-30 20:34 ` Karsten Scheibler [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-29 16:08 Bodo Giannone
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=20080530203539.AB96F7B24@gw.unusedino.de \
--to=laml@unusedino.de \
--cc=linux-assembly@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).