From: Christof Klaiber <christof.klaiber@merath-maschinen.de>
To: buildroot@busybox.net
Subject: [Buildroot] Shell-Weirdness
Date: Thu, 20 Mar 2008 14:06:07 +0100 [thread overview]
Message-ID: <1206018367.6470.7.camel@luder> (raw)
I built buildroot from svn for i486 and try to run it in qemu.
~/qemu/bin/qemu -hda binaries/uclibc/rootfs.i686.ext2 -kernel
project_build_i686/uclibc/linux-2.6.24.3/arch/i386/boot/bzImage -append
root=/dev/hda
After booting the kernel, it complains about not finding /etc/init.d/rcS
- where did it go? It used to be there in earlier times.
Then I can activate a shell by hitting Enter.
The shell works fine, but whenever I try to enter a command which
contains a "-", I get an error message or the shell blocks.
e.g.
/ # ls -l
-> terminal blocks
somtimes I can use <ctrl>-c to escape, sometimes I have to quit qemu.
Any suggestions, why this can happen?
Regards,
Christof
next reply other threads:[~2008-03-20 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 13:06 Christof Klaiber [this message]
2008-03-20 17:05 ` [Buildroot] Shell-Weirdness John Voltz
2008-03-20 17:10 ` Nigel Kukard
2008-03-20 17:12 ` Nigel Kukard
2008-03-20 17:32 ` John Voltz
2008-03-25 7:12 ` [Buildroot] [BR-AVR32] Shell-Weirdness Hans-Christian Egtvedt
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=1206018367.6470.7.camel@luder \
--to=christof.klaiber@merath-maschinen.de \
--cc=buildroot@busybox.net \
/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