I have just tried to install dvb-utils in Intrepid and this bug is still
present.
Is there a workaround for this?
--
/dev/.static/dev is mounted ro in intrepid
https://bugs.launchpad.net/bugs/253786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I just installed dvb-utils in intrepid, and the bug is still present.
--
/dev/.static/dev is mounted ro in intrepid
https://bugs.launchpad.net/bugs/253786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
hi folks,
After upgrading to 8.10 my mythtv setup stopped working. running "sudo
dpkg-reconfure mythtv-backend" I notice lots of these errors:
udev active, devices will be created in /dev/.static/dev/
rm: cannot remove `video0-': Read-only file system
mknod: `video0-': Read-only file system
make
I don't know if it means that it would become available in the proposed
updates for intrepid or not. I don't enable that repo. Also, I think we
all got notified that a guy testing the new udev in jaunty still has
this problem with libsensors. Since I have 3 machines with this issue
I have implem
Will this be fixed for Intrepid too?
--
/dev/.static/dev is mounted ro in intrepid
https://bugs.launchpad.net/bugs/253786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
This bug was fixed in the package udev - 136-1
---
udev (136-1) jaunty; urgency=low
One of the biggest changes in this release is that the default rules
are no longer conffiles and are now installed into /lib/udev/rules.d
You may still add your custom rules to /etc/udev/rules.d
i dont see a seperate bug for when mythtv-backend fails while setting up devices
http://pastebin.com/m4e2553f9
stopping and starting udev then a dpkg-reconfigure mythtv-backend
prompted me about created the devices which succeeded this time around.
I imagine this will revert after a reboot and fai
kernel 2.6.27-8 and udev 124-11 didn't fix this problem
--
/dev/.static/dev is mounted ro in intrepid
https://bugs.launchpad.net/bugs/253786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Just a note that "/etc/init.d/udev restart" does not fix this problem;
only stopping and starting the service removes the read-only problem.
--
/dev/.static/dev is mounted ro in intrepid
https://bugs.launchpad.net/bugs/253786
You received this bug notification because you are a member of Ubuntu
[EMAIL PROTECTED]:~$ grep static /proc/mounts
/dev/disk/by-uuid/7b58a11b-972a-4a67-909a-b8e48cb29da5 /dev/.static/dev ext3
ro,errors=remount-ro,data=ordered 0 0
/dev/disk/by-uuid/7b58a11b-972a-4a67-909a-b8e48cb29da5
/var/chroot/hardy/dev/.static/dev ext3 ro,errors=remount-ro,data=ordered 0 0
hth
Appears to have triggered bug #296477 and bug #295510.
--
/dev/.static/dev is mounted ro in intrepid
https://bugs.launchpad.net/bugs/253786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
I was looking into this because it triggered bug 278954.
initramfs bind-mounts /dev to /dev/.static/dev before the init scripts
remount / read-write.
I've been working around the XFS bug with a line in fstab:
/dev/dev/.static/dev bind remount,rw 0 0
This has the side-effect o
They've removed /dev/.static/dev entirely, which is somewhat the
direction I was thinking of taking as well. Jumping through hoops just
to support systems that don't have udev installed isn't worth the
effort, udev is part of our required set of packages.
I'll probably do likewise for 9.04
--
/
** Changed in: udev (Debian)
Status: Unknown => Fix Released
--
/dev/.static/dev is mounted ro in intrepid
https://bugs.launchpad.net/bugs/253786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
This issue is apparently fixed in Debian.
** Bug watch added: Debian Bug tracker #481559
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481559
** Also affects: udev (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481559
Importance: Unknown
Status: Unknown
--
/dev
I wonder whether that's a kernel change?
It's a bind mount of the root filesystem, and previously that bind mount
just had whatever permissions the underlying root filesystem had.
Of course, I know that the kernel recently gained support for bind
mounts being mounted differently - I wonder whethe
16 matches
Mail list logo
