[gmail] 1.1.3 is up.

[Chey]

Maybe i'm seeing a different problem than you guys are speaking
of...here is what i am seeing.

I have an initrd image and the linuxrc script does a 'mount -a'
directly after a 'pivot_root' on the following fstab:

proc        /proc           proc    defaults                0   0
devpts          /dev/pts                devpts
defaults,gid=5,mode=620 0       0
sysfs           /sys                    sysfs   defaults
                 0       0

The problem is (only in 1.1.3) no matter what the last entry is, mount
-a spits out an error telling me it couldn't mount (/sys in this
example) it. I don't have that problem in 1.1.2. The weird this is, it
actually mounts all entries even though i get an error.

Thx,
Chey


On 5/19/06, Rob Landley <rob at landley.net> wrote:
> On Thursday 18 May 2006 10:45 am, Marc Leeman wrote:
> > > Yep, I found that tmpfs annoyance some time ago as well.  I wasn't sure
> > > that it was really a mount issue, so I just quit putting any tmpfs
> > > entries in my fstab, or at the very least gave them a noauto.  I have
> > > other startup scripts take care of them.
> >
> > Just tested it and it was in 1.1.2 too (and earlier since I used the
> > mount.c from pre-1.1.1). It's not 1.1.3 related.
>
> It's because busybox mount does exactly what it's told, and if you say mount
> this again it does.  It's the kernel that filters out redundant overmounts if
> you call mount -a twice, but apparently it's not doing that for tmpfs...
>
> Rob
> --
> Never bet against the cheap plastic solution.
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox
>