Embedded Linux, Bad inittab entry

comp.os.linux.embedded - Linux operating system on embedded hardware.


Embedded Linux >> Bad inittab entry

by Luke Albers » Tue, 24 Aug 2004 03:09:50 GMT

Hey everyone

I am making a very small system that fits on a 128MB CF card, and
think I have it in a almost bootable state. This morning was the first
time I tried booting it on the SBC that I am using, and it starts
loading up, but I get the following message:

Bad inittab entry: id:3:initdefault:
Bad inittab entry: rc::bootwait:/sbin/rc boot

I am using busybox if that might have anything to do with it.
Also, I couldnt figure out how to cross compile it, since I dont want to
use uClibc. When I select cross compilation in the config, it defaults
to uClibc. I do not know how to compile it for i386, so it is compiled
for 686. So, i guess the problem could be that they are not compiled
for the right architecture, but i know that some of the other busybox
commands work. What does someone else think?

I dont know what this means and can't figure it out on google. If
anyone can at least tell me what this means and point me in the right
direction, I would be very grateful

Top

Embedded Linux >> Bad inittab entry

by Luke Albers » Tue, 24 Aug 2004 03:45:03 GMT


I think this has something to do with the problem as well:

when i do /sbin/rc sysinit in the chroot on my own system:


localhost / # /sbin/rc sysinit
* ERROR: runlevel sysinit does not exist; exiting...
localhost / #


/sbin/rc boot and default both do something, but whatever it is it
doesnt work in the chroot and it messes up the Xterm.

BTW this system was based off of a Gentoo stage 1 tarball


Top

Embedded Linux >> Bad inittab entry

by Luke Albers » Tue, 24 Aug 2004 05:00:16 GMT


> Bad inittab entry: id:3:initdefault:
> Bad inittab entry: rc::bootwait:/sbin/rc boot
>
> I am using busybox if that might have anything to do with it.

I think that since I am using busybox init I need to have a different
inittab since it works differently. However, I cant figure out how to
make the inittab that works with busybox init and gentoo's scripts.

Does this sound right? Does anyone know how to do this?

Top

Bad inittab entry

by kai-martin knaak » Tue, 24 Aug 2004 07:54:54 GMT





It might very well be. The init command contained in busybox understands
just a tiny subset of what is possible with the ordinary version.
If you look into the comments of my inittab-file you see, that
"initdefault" and "bootwait" are not in the list of supported actions.
Where did you get your /etc/inittab file from?

Can you just post your /etc/inittab ?


Why not? uclibc allows for pretty small systems. In my case I have only
4Mb of memory and the system fits into just about 2MB. This already
includes a webserver and the ability to communicate via tcp/ip.


In any case you need a properly configured gcc-toolchain with your desired
target compiled in.

---<(kaimartin)>--

PS: The /etc/inittab o my SBC looks like this:
--------------------------8<--------------------
# /etc/inittab
#
# Copyright (C) 2001 Erik Andersen < XXXX@XXXXX.COM >
#
# modifiziert for lara -<(kmk)>-
#
# Note: BusyBox init doesn't support runlevels. The runlevels field is
# completely ignored by BusyBox init. If you want runlevels, use
# sysvinit.
#
# Format for each entry: <id>:<runlevels>:<action>:<process>
#
# id == tty to run on, or empty for /dev/console
# runlevels == ignored
# action == one of sysinit, respawn, askfirst, wait, and once
# process == program to run

# main rc script
::sysinit:/etc/init.d/rcS

# main setup program
::respawn:-/bin/sh

# convenience shell
#tty2::askfirst:-/bin/sh

# set up stuff for logging
null::sysinit:/bin/dmesg > /dev/tty4
#tty3::respawn:/usr/bin/tail -f /var/log/messages
#tty4::respawn:/usr/bin/tail -f /proc/kmsg

# Stuff to do for the 3-finger salute
::ctrlaltdel:/sbin/reboot

# Stuff to do before rebooting
null::shutdown:/bin/umount -a -r
null::shutdown:/sbin/swapoff -a
----------------->8-----------------------

--
Kai-Martin Knaak
XXXX@XXXXX.COM
gpg-key: http://pgp.mit.edu :11371/pks/lookup?search=kai-martin&op=index&exact=on


Top

Bad inittab entry

by Ian Stirling » Sun, 29 Aug 2004 05:54:23 GMT




Have you tried booting the CF card on a PC?
CF to IDE adaptors are nearly free.

In general, busybox stuff is less tolerant of errors/whitespace
than others.
Have you read the busybox init manpages again?

Top
Similar Threads

1. Bad inittab entry ??? 

Hey everyone

I am making a very small system that fits on a 128MB CF card, and
think I have it in a almost bootable state. This morning was the first
time I tried booting it on the SBC that I am using, and it starts
loading up, but I get the following message:

Bad inittab entry: id:3:initdefault:
Bad inittab entry: rc::bootwait:/sbin/rc boot

I am using busybox if that might have anything to do with it.

I dont know what this means and can't figure it out on google. If
anyone can at least tell me what this means and point me in the right
direction, I would be very grateful

2. AIX5.2 /etc/inittab entries not run after ssh entry

3. inittab entry run a process with another userid 

Hi,

I have an entry in inittab as
xxx:5:respawn:su user -c '/home/local/bin/brassd -d >/dev/null 2>&1'

After adding this entry i did init q and the output from
ps -aef |grep brassd showed

root 28553 1 0 13:38 ? 00:00:00 su user -c /home/local/bin/brassd -d
>/dev/null 2>&1
user   28554 28553  0 13:38 ? 00:00:00 ksh -c /home/local/bin/brassd -d
>/dev/null 2>&1
user   28555 28554  2 13:38 ?        00:00:00 /home/local/bin/brassd -d

But for the same inittab entry in aix, HP and Sun i only see the third
entry. Is this normal in linux? For the use default login shell is ksh.
Thanks in advance.

4. Question about inittab entry

5. weird behavior when "cons" entry is near the end of /etc/inittab 

Hello All,

I'm running into some very strange and very hard to reproduce issue
with mksysb installs. When "cons" entry is towards the end of the
inittab (after the run levels, etc.), I get all sorts of funky
problems, specifically all my "sys0" settings are the default (i.e.
extremley low value for maxuproc, etc.). When I change these, the
settings get changed back to these low default values. When I move
"cons" up in the inittab, the changes survive reboots. When you move
"cons" back down in the file, the issue is not reproducible... This has
happened to me on multiple installations, using different AIX 5.3
mksysb's......

Any thoughts on what's cause "cons" to mess up the ODM?

-Chris

6. inittab entries and "respawing too rapidly"

7. swap_dup: Bad swap file entry 76747774 with kernel 2.4.26+patch_kraxel-2.4.26

8. Bad swap file entry