/dev/static/.dev has been removed

[Scott James Remnant]

On Wed, 2009-01-14 at 13:53 -0800, Steve Langasek wrote:

> On Wed, Jan 14, 2009 at 12:55:46PM +0000, Scott James Remnant wrote:
> 
> > These packages could access the original static /dev through
> > the /dev/.static/dev path.  As many noted, this broke when the kernel
> > gained the ability to have separate access for bind mounts, and this was
> > actually read-only.
> 
> I've failed to parse this.  How did gaining the /ability/ for "separate
> access to bind mounts" break anything?  I haven't noticed breakage with any
> of my bind mounts anywhere - is this specific to linux 2.6.28 and above (all
> my bind mounts are running on systems running older kernels)?
> 
The /dev/static/.dev bind mount is from the root filesystem, and is made
while the root filesystem is read-only.

Previously, when the root filesystem was made writable, the writability
would follow to the bind mount.

Now because the bind mount has separate access rights to what is bound,
when the root filesystem is made writable, the bind mount of it
_remains_read_only_.

You must have seen errors in intrepid of the form:

    udev active, devices will be created in /dev/.static/dev/
    rm: cannot remove `parport0-': Read-only file system
    mknod: `parport0-': Read-only file system


There are alternate ways to fix this, obviously; the chosen one was
simply to drop support for /dev/.static/dev.  This means that /dev on
the root filesystem will only be a set of "standard devices".

Scott
-- 
Scott James Remnant
scott at canonical.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20090115/de6c7251/attachment.pgp