Code: Select all
bash: cannot set terminal process group (-1): inappropriate ioctl for device
bash: no job control in this shellWhy do I get errors for init=/bin/bash linux boot option?
Message
Why do I get errors for init=/bin/bash linux boot option?
It have compiled and installed linux kernel, bash, coreutils from source. I have added init=/bin/bash to linux boot option. During boot I get two errors:
Bash is running, but how can I solve these errors? Why do these errors occur?
You probably need more than just init=/bin/bash.
You most probably need to set up few things before bash can fully act as your init.
You most probably need to set up few things before bash can fully act as your init.
Are you using/creating your custom initramfs?[b]JdeBP[/b] @ unix.stackexchange wrote:As I said at https://unix.stackexchange.com/a/197472/5132, init=/bin/sh doesn't get "API" fileystems mounted, crashes in an ungainly fashion with no cache flush when one types exit (https://unix.stackexchange.com/a/195978/5132), and in general leaves it to the (super)user to manually do the actions that make the system minimally usable.
One of those actions (if you want to use a job control shell, as you apparently do) is acquiring a controlling terminal. /dev/tty isn't an actual terminal device. It's a device that redirects to whatever the opening process' controlling terminal is. If it does not have one, as process #1 does not to begin with (and usually all of the time when a real system manager program is being run as process #1), then opening the device fails.
Your system is too minimal. You need to run a program that sets up a controlling terminal, initializes a proper session, and probably does some of the bare minima of system management such as shutting down properly and cleanly, that then runs your job control shell.
..: Zucca :..
Code: Select all
0100100100100000011000010110110100100000
0100111001100001010011100010000100100000
0100100100100000011000010110110100100000
0110000100100000011011010110000101101110
00100001You'll need to have /dev, /sys and /proc.
Why are you having /bin/bash as init anyway? Do you plan this as an alternative boot option to have a rescue shell?
Why are you having /bin/bash as init anyway? Do you plan this as an alternative boot option to have a rescue shell?
..: Zucca :..
Code: Select all
0100100100100000011000010110110100100000
0100111001100001010011100010000100100000
0100100100100000011000010110110100100000
0110000100100000011011010110000101101110
00100001
- NeddySeagoon
- Administrator
- Posts: 56108
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
colag,
You need at least /dev/console and /dev/null as device special files.
/proc and /sys are handy too.
With init=/bin/bash/, its a very lonely place to be. Just you and bash on a read only root filesystem.
The rest of /dev missing makes life more challenging too.
What will you use it for?
You need at least /dev/console and /dev/null as device special files.
/proc and /sys are handy too.
With init=/bin/bash/, its a very lonely place to be. Just you and bash on a read only root filesystem.
The rest of /dev missing makes life more challenging too.
What will you use it for?
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
- NeddySeagoon
- Administrator
- Posts: 56108
- Joined: Sat Jul 05, 2003 9:37 am
- Location: 56N 3W
colag,
When you get to the bash shell, mount them.
When you get to the bash shell, mount them.
Code: Select all
mount -t proc proc /proc
mount -t sysfs sys /sysRegards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
I have added proc and sys in /etc/fstab. What else should I do?NeddySeagoon wrote:colag,
When you get to the bash shell, mount them.
Code: Select all
mount -t proc proc /proc mount -t sysfs sys /sys
This does not help because you boot into a "naked" bash ... then ALL RC-startup-scripts will not be started ... and THEY do the job of reading /etc/fstab and mounting all. For example:colag wrote:I have added proc and sys in /etc/fstab. What else should I do?
/etc/init.d/sysfs usually mounts your sysfs (in "sysinit"; if you use OpenRC). You must mount it manually if you boot into a bash.
Again the question from @Zucca: Why are you having /bin/bash as init anyway?
Maybe you want to use an initramfs for your needs ? If so, then read first this:
https://wiki.gentoo.org/wiki/User:Pieti ... s_Overview
and then all linked articles.
- GDH-gentoo
- Advocate
- Posts: 2117
- Joined: Sat Jul 20, 2019 7:02 pm
- Location: South America
What are you doing, assembling a Linux From Scratch-like operating system piece by piece?colag wrote:I have installed shadow, sysvinit.
Hard to say without more knowledge about what you have installed so far and what state it currently is in. It is not a Gentoo system, is it?colag wrote:Now after booting, I can see a login prompt. After typing root then Enter, it does not prompt for password. Waiting for sometime, it shows the login prompt again to enter user. I get no prompt for password. Why is this?
Yes, doing init=/bin/sh is a valid, but extreme, way of booting when e. g. the init system is damaged. Or nonexistent in this case? Who knows.
And the error in the OP is unavoidable but harmless, the cause is the one mentioned in Zucca's first reply, i. e. a shell process running as process 1 does not have a controlling terminal; a shell process spawned in the usual way does (e. g. because the agetty program provides one).
Ionen wrote:As a packager I just don't want things to get messier with weird build systems and multiple toolchains requirements though
