[BusyBox] 0.47 - Can't mount /proc

Bob Van Gulick rvangulick at navicent.com
Mon Oct 9 15:07:32 UTC 2000


Hi Eric...

Thanks for your response to my question.  From what I can tell, /proc is
being
mounted via a script with mount -a.  Regardless of how it's being mounted, I
can
type 'mount -a' or 'mount /proc' and get the same failure as at bootup time.
Here's whats in my fstab:

/ # cat /etc/fstab
/proc /proc proc defaults 0 0

In trying to debug this, I've put some printf's in the mount code.  I
printed out what
parameters are being passed into the function:

/ # mount -a
mount: blockDevice=/proc, dir=/proc,filesystemType=proc,flags=       0
mount: str_flags=,useMtab=0,fakeIt=1,mtab_opts=,whineOnErrors=0
mount: non automount!
mount: Mounting /proc on /proc failed: Bad address
/ #

Since this worked in 0.45, kernel 2.3.99, perhaps it has something to do
with my .config
on 2.4.pre9.  I have CONFIG_PROC_FS set on.  Any other defines you know of
that
have to be on for this to work?

Thanks,
Bob

----- Original Message -----
From: "Erik Andersen" <andersen at lineo.com>
To: "Bob Van Gulick" <rvangulick at navicent.com>
Cc: <busybox at busybox.net>
Sent: Friday, October 06, 2000 4:54 PM
Subject: Re: [BusyBox] 0.47 - Can't mount /proc


> On Fri Oct 06, 2000 at 04:38:05PM -0500, Bob Van Gulick wrote:
> > Greetings...
> >
> > First time post here, so shed me some slack :-)
> >
> > I am in the process of developing an embedded mips kernel and using
busybox 0.47
> > as a standalone shell.  I've recently upgraded to 0.47 from 0.45 (I also
upgraded my
> > kernel to 2.4.pre9 from 2.3.99 causing the upgrade.)  My problem is that
I can no
> > longer mount /proc in 0.47.  0.45 everything worked fine.  Here is the
message I get
> > when I mount /proc:
> >
> >   Mounting /proc on /proc failed: Bad address
> >
> > Hopefully this is a simple thing to fix as I need /proc mounted in order
to do anything
> > with my DHCP code.
>
> Is /proc being mounted manually, or via a script?  Are you running
'mount -a'
> (with an appropriate /etc/fstab entry) or something else?  What exactly
was the
> command you ran?  What does /etc/fstab have in it?
>
>  -Erik
>
> --
> Erik B. Andersen   email:  andersen at lineo.com
> --This message was written using 73% post-consumer electrons--
>






More information about the busybox mailing list