From: adam8157@gmail.com (Adam Lee)
To: kernelnewbies@lists.kernelnewbies.org
Subject: rootfile system porting for FPGA [/bin/sh: can't access tty; job control turned off]
Date: Mon, 7 May 2012 22:01:14 +0800 [thread overview]
Message-ID: <20120507140114.GA4817@adam-laptop> (raw)
In-Reply-To: <CAFxuAafVd5WdE=TgVTFLY-zJKbH5uo1RFS+HB4E7EA9CC9Zsgw@mail.gmail.com>
On Mon, May 07, 2012 at 06:21:05PM +0530, pcuser p wrote:
> I am ending up in the shell prompt with the message as below:
> "entered linuxrc script"
> "/bin/sh: can't access tty; job control turned off
> / $"
>
> my kernel commad line is
> "mem=32M console=ttySAC0,115200 root=/dev/ram0 init=/linuxrc initrd=
> 0x80800000,8M user_debug=31"
In my kernel command line(with busybox), init=/sbin/init, I drop
commands into /etc/profile.
> Below are my /linuxrc and /etc/inittab file contents
> linuxrc:
>
> #!/bin/sh
> /bin/echo "entered linuxrc script"
> /bin/sh
> exec /sbin/init
Don't run sh before init, this makes the warning.
> /etc/inittab:
>
> # Run gettys in standard runlevels
> 3:2345:respawn:/sbin/getty 115200 ttySAC0
>
runlevels makes no sense here, but it should be OK.
And, I use busybox to build the rootfs for kernel debugging:
https://github.com/adam8157/kernel-studio
the rootfs making script is at here right now:
https://github.com/adam8157/kernel-studio/blob/master/mkrootfs
Might helps.
--
Regards,
Adam Lee
--------------------------------
E-mail: adam8157 at gmail.com
Website: http://adam8157.info
--------------------------------
next prev parent reply other threads:[~2012-05-07 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 12:51 rootfile system porting for FPGA [/bin/sh: can't access tty; job control turned off] pcuser p
2012-05-07 13:42 ` Anirban Roy
2012-05-07 13:42 ` Mandeep Sandhu
2012-05-07 14:01 ` Adam Lee [this message]
2012-05-08 12:43 ` pcuser p
2012-05-08 13:03 ` Adam Lee
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=20120507140114.GA4817@adam-laptop \
--to=adam8157@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).