All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] init: I won't write compressed data to a terminal.
Date: Wed, 07 Jul 2010 22:45:46 +0200	[thread overview]
Message-ID: <87630r58cl.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <87aaq358x1.fsf@macbook.be.48ers.dk> (Peter Korsgaard's message of "Wed, 07 Jul 2010 22:33:30 +0200")

>>>>> "Peter" == Peter Korsgaard <jacmet@uclibc.org> writes:

Hi,

 Ossy> After passing init=/bin/sh to the kernel, I ran into a similar error:
 Ossy> [    4.387550] eth0: link up, 100 Mb/s, full duplex, flow control disabled
 Ossy> [    4.716652] Looking up port of RPC 100003/2 on 192.168.1.106
 Ossy> [    4.727962] Looking up port of RPC 100005/1 on 192.168.1.106
 Ossy> [    4.739261] VFS: Mounted root (nfs filesystem) on device 0:12.
 Ossy> [    4.745153] Freeing init memory: 112K
 Ossy> sh: I won't write compressed data to a terminal.
 Ossy> sh: For help, type: `sh --help'.

 Peter> Hmm, Did something overwrite your busybox binary? It should be around
 Peter> ~500KB big.

 Peter> What does strings -n 25 bin/busybox|head give?

Seems like it:

ln -s /bin/bunzip2 sh; ./sh
sh: I won't write compressed data to a terminal.
sh: For help, type: `sh --help'.

I guess something went wrong with the recent conversion of the bzip2
package. Will test.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2010-07-07 20:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 22:16 [Buildroot] init: I won't write compressed data to a terminal Ossy
2010-07-07  0:35 ` Mitch Davis
2010-07-07 20:20   ` Ossy
2010-07-07 20:33     ` Peter Korsgaard
2010-07-07 20:41       ` Ossy
2010-07-07 20:49         ` Peter Korsgaard
2010-07-07 21:39           ` Peter Korsgaard
2010-07-09 19:46             ` Ossy
2010-07-11 18:52               ` Peter Korsgaard
2010-07-07 20:45       ` Peter Korsgaard [this message]
2010-07-07  5:52 ` Peter Korsgaard
2010-07-07  6:14   ` Mitch Davis
2010-07-07 18:00   ` Ossy
2010-07-07 18:59     ` Peter Korsgaard
2010-07-07 20:14       ` Ossy

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=87630r58cl.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.