From: mandeepsandhu.chd@gmail.com (Mandeep Sandhu)
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 19:12:52 +0530 [thread overview]
Message-ID: <CAC+QLdRZ+kCDOR3NxojdxG4uuhOg4X=S1zti2VcZOC_EN2xz=g@mail.gmail.com> (raw)
In-Reply-To: <CAFxuAafVd5WdE=TgVTFLY-zJKbH5uo1RFS+HB4E7EA9CC9Zsgw@mail.gmail.com>
> my kernel commad line is
> "mem=32M console=ttySAC0,115200 root=/dev/ram0 init=/linuxrc
> initrd=0x80800000,8M user_debug=31"
>
> Below are my /linuxrc and /etc/inittab file contents
> linuxrc:
>
> #!/bin/sh
> /bin/echo "entered linuxrc script"
> /bin/sh
No need to run shell here, your /sbin/init actually points to the the
busybox binary. You juts need to instruct the system to run getty on
the console which will launch the login program. login will further
provide you with a shell to type cmds etc.
> exec /sbin/init
This should point to /bin/busybox
>
>
> /etc/inittab:
>
> # Run gettys in standard runlevels
> 3:2345:respawn:/sbin/getty 115200 ttySAC0
Busybox init did not used support runlevels (not sure of the latest
versions). I'm running BB 1.16.2 and that has the following line for
spawning getty on the console:
tts/0::respawn:/sbin/getty -L tts/0 115200
Try adding this line to inittab (modify according to your setup).
BTW, what version of BB are you running?
HTH,
-mandeep
>
>
>
> Can some experts suggest how to fix this two problems and get a shell prompt
> working?
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
next prev parent reply other threads:[~2012-05-07 13:42 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 [this message]
2012-05-07 14:01 ` Adam Lee
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='CAC+QLdRZ+kCDOR3NxojdxG4uuhOg4X=S1zti2VcZOC_EN2xz=g@mail.gmail.com' \
--to=mandeepsandhu.chd@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).