[BusyBox] TAKE 2: Message on Startup: "sh: can't access tty; job control turned off"
Stewart Brodie
stewart.brodie at pace.co.uk
Thu Jan 9 04:49:04 UTC 2003
In message <20030108182104.GA8294 at codepoet.org>
Erik Andersen <andersen at codepoet.org> wrote:
> On Wed Jan 08, 2003 at 05:52:42PM +0000, Stewart Brodie wrote:
> > > Hmm. Interesting. Have you syslog? If have, what giving messages: "Starting
> > > pid %d, console %s: '%s'\n", getpid(), a->terminal, cmdpath);
> > >
> > > /dev/console or /dev/ttySN?
> >
> > It reports /dev/console
>
> Then you are running your shell on /dev/console. You cannot get
> working job control on /dev/console without hacking the kernel --
> the kernel removes CTTY from /dev/console.
Right! I have now rewritten my inittab file to leave the first field blank
and everything seems to be working properly. I guess what has happened is
that init's behaviour has been changed (probably fixed) and that I was just
getting away with with having all the first fields set to 'console' before.
It now reports that it is starting the processes on /dev/ttyS0 which is where
the console really is.
--
Stewart Brodie, Senior Software Engineer
Pace Micro Technology PLC
645 Newmarket Road
Cambridge, CB5 8PB, United Kingdom WWW: http://www.pacemicro.com/
More information about the busybox
mailing list