From: Michael Shmulevich <michaels@jungo.com>
To: unlisted-recipients:; (no To-header on input)
Cc: busybox@opensource.lineo.com,
"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: [BusyBox] 0.48 - Can't mount /proc
Date: Thu, 11 Jan 2001 09:28:28 +0200 [thread overview]
Message-ID: <3A5D609C.2080201@jungo.com> (raw)
In-Reply-To: 20010110122159.A24714@lineo.com
Erik,
No, doesn't help.
bash# mount proc /proc -t proc
mount: Mounting proc on /proc failed: Unknown error 716878944
Maybe people in mips-linux know something about this?
Erik Andersen wrote:
> On Wed Jan 10, 2001 at 08:39:15PM +0200, Michael Shmulevich wrote:
>
>> Hello,
>>
>> This is my first mail to this list, but I have already seen similar
>> question being unanswered.
>> I am developing an embedded system based on MIPS board. I am
>> cross-compiling the BusyBox 0.48 on x86 with gcc 2.90.29 (egcs 1.0.3a).
>>
>> While trying to mount /proc either atomatically in script or by hand,
>> the command fails with following message:
>>
>> bash# mount /proc -t proc
>> mount: Mounting none on /proc failed: Unknown error 716878944
>
>
> mount proc /proc -t proc
>
> -Erik
>
> --
> Erik B. Andersen email: andersen@lineo.com
> --This message was written using 73% post-consumer electrons--
WARNING: multiple messages have this Message-ID (diff)
From: Michael Shmulevich <michaels@jungo.com>
Cc: busybox@opensource.lineo.com,
"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: [BusyBox] 0.48 - Can't mount /proc
Date: Thu, 11 Jan 2001 09:28:28 +0200 [thread overview]
Message-ID: <3A5D609C.2080201@jungo.com> (raw)
Message-ID: <20010111072828.udjTpmnGuxAXV-6qi_r7WaqzarOaKr4abTM-E5G7MxM@z> (raw)
In-Reply-To: 20010110122159.A24714@lineo.com
Erik,
No, doesn't help.
bash# mount proc /proc -t proc
mount: Mounting proc on /proc failed: Unknown error 716878944
Maybe people in mips-linux know something about this?
Erik Andersen wrote:
> On Wed Jan 10, 2001 at 08:39:15PM +0200, Michael Shmulevich wrote:
>
>> Hello,
>>
>> This is my first mail to this list, but I have already seen similar
>> question being unanswered.
>> I am developing an embedded system based on MIPS board. I am
>> cross-compiling the BusyBox 0.48 on x86 with gcc 2.90.29 (egcs 1.0.3a).
>>
>> While trying to mount /proc either atomatically in script or by hand,
>> the command fails with following message:
>>
>> bash# mount /proc -t proc
>> mount: Mounting none on /proc failed: Unknown error 716878944
>
>
> mount proc /proc -t proc
>
> -Erik
>
> --
> Erik B. Andersen email: andersen@lineo.com
> --This message was written using 73% post-consumer electrons--
next parent reply other threads:[~2001-01-11 7:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A5CAC53.60700@jungo.com>
[not found] ` <20010110122159.A24714@lineo.com>
2001-01-11 7:28 ` Michael Shmulevich [this message]
2001-01-11 7:28 ` [BusyBox] 0.48 - Can't mount /proc Michael Shmulevich
2001-01-11 11:48 ` Erik Andersen
2001-01-11 12:04 ` Florian Lohoff
2001-01-11 15:52 ` Quinn Jensen
2001-01-11 15:52 ` Quinn Jensen
2001-01-16 7:13 ` Ralf Baechle
2001-01-11 20:25 ` Ralf Baechle
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=3A5D609C.2080201@jungo.com \
--to=michaels@jungo.com \
--cc=busybox@opensource.lineo.com \
--cc=linux-mips@oss.sgi.com \
/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