On May 13, Ronan Brunner wrote:
> Just did a fresh install using testing, and got this udev bug. DOA.
> Upgraded to unstable and I still cannot get any usb or ethernet
> connectivity. A very serious bug and cannot believe it is still around.
Because it is not. You are probably experiencing #624
Just did a fresh install using testing, and got this udev bug. DOA.
Upgraded to unstable and I still cannot get any usb or ethernet
connectivity. A very serious bug and cannot believe it is still around.
Your message dated Mon, 11 Apr 2011 01:34:33 +
with message-id
and subject line Bug#621036: fixed in udev 167-2
has caused the Debian Bug report #621036,
regarding udev should not assume that /run works just because it exists
to be marked as done.
This means that you claim that the problem
jidanni wrote:
> Why don't you take out the network next time too so I can't write such nasty
> notes.
Well you're lucky. On my system it *did* take out the network...
Couldn't fix it until I got my hands on someone else's computer to learn
what the problem (and workaround) was.
Drew
--
Well gosh, you fellows took out my
*YouTube sound
*Trackpoint
Why don't you take out the network next time too so I can't write such nasty
notes.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
> reassign 621036 udev
Bug #621036 [base-files] base-files creates an unuseable /run, breaking udev
and the whole system
Bug reassigned from package 'base-files' to 'udev'.
Bug No longer marked as found in versions base-file
reassign 621036 udev
retitle 621036 udev should not assume that /run works just because it exists
thanks
I have just dropped /run in base-files 6.3.
But this is still a bug in udev. I still believe it makes no sense to
treat /run as if it was functional "just because it exists".
I will be more t
There are additional issues after installing base-files 6.2 and udev 167-1.
On the first reboot after the upgrade, udev /does/ start but does not start
correctly; manually killing the three 'udev --daemon' processes and restarting
udev via '/etc/init.d/udev start' appears as if it mostly works, a
Hi everyone,
On Mi, 06 Apr 2011, Santiago Vila wrote:
> So, the issue now is: Can I expect an udev release fixing this in a day or
> two?
I think my main reason of the post was to explain and make clear to
other users that downgrading both udev and base-files fixes the
problem. Downgrading udev
#issue 1: udev failing during boot
The bug is in the sysv init script for udev:
It has set -e and
if [ -d /run/ ]; then
mkdir -p /run/udev/rules.d/
create_dev_root_rule /run/udev/
else
This will obviously fail when /run is ro, the script will exit and as a
consequence udevd is
On Apr 06, Santiago Vila wrote:
> So, the issue now is: Can I expect an udev release fixing this in a day or
> two?
Well, can I expect an initscripts release fixing this in a day or two?
--
ciao,
Marco
signature.asc
Description: Digital signature
On Wed, 6 Apr 2011, Marco d'Itri wrote:
> On Apr 06, Norbert Preining wrote:
>
> > Does the maintainer of soemthing like *base-files* at least *once*
> > reboot into his own machine before he uploads? It seems not so, that
> > is a bug that does effect everyone as far as I see.
> In his defense,
On Wed, Apr 06, 2011 at 08:18:06PM +0900, Norbert Preining wrote:
> Follow up to this bug report: downgrading base-files and rm -rf /run
> did help and get me back a running system.
>
>
> Does the maintainer of soemthing like *base-files* at least *once*
> reboot into his own machine before he up
On Apr 06, Norbert Preining wrote:
> Does the maintainer of soemthing like *base-files* at least *once*
> reboot into his own machine before he uploads? It seems not so, that
> is a bug that does effect everyone as far as I see.
In his defense, the bug only causes problems after udev is upgraded.
Follow up to this bug report: downgrading base-files and rm -rf /run
did help and get me back a running system.
Does the maintainer of soemthing like *base-files* at least *once*
reboot into his own machine before he uploads? It seems not so, that
is a bug that does effect everyone as far as I se
found 621036 6.2
thanks
Hi. I Don't want to interfere with the bug assignement but I'm tagging this
as found so that apt-listbugs can signal it and avoid other people to
install a package which can make their systems unusable!
Regards.
Andrea De Iacovo
On Wed, 6 Apr 2011, Marco d'Itri wrote:
> reassign 621036 base-files
> retitle 621036 base-files creates an unuseable /run, breaking udev and the
> whole system
> affects 621036 udev
> block 620995 with 621036 620191
> thanks
>
> On Apr 06, Gianluigi Tiesi wrote:
>
> Indeed this happens becaus
Processing commands for cont...@bugs.debian.org:
> reassign 621036 base-files
Bug #621036 [udev] udev fails to load modules at startup: cannot create
/run/udev//root-link-rule: Read-only file system
Bug reassigned from package 'udev' to 'base-files'.
Bug No longer mark
reassign 621036 base-files
retitle 621036 base-files creates an unuseable /run, breaking udev and the
whole system
affects 621036 udev
block 620995 with 621036 620191
thanks
On Apr 06, Gianluigi Tiesi wrote:
Indeed this happens because your system has /run/ but it is not
writeable. udev does no
Package: udev
Version: 167-1
Severity: grave
Tags: sid
I've just upgraded udev from 166-1 to 167-1, but udev is not anymore able
to load modules, e.g. network cards
166-1 was ok
but now even downgrading (dpkg -i of 166-1) udev does not solve the problem
(I've also called update-initramfs)
I thi
20 matches
Mail list logo
