On Sun, 10 Apr 2011 22:03:36 -0400
Johan Kullstam kullstj...@verizon.net wrote:
Apologies for following up to myself, but I thought I should say that
when I added /run myself the 2.6.38 kernel booted without problems.
So... is this udev167-1 safe to upgrade to on Wheezy (base-files 6.1), or
On 04/12/2011 03:32 PM, Andrej Kacian wrote:
On Sun, 10 Apr 2011 22:03:36 -0400
Johan Kullstamkullstj...@verizon.net wrote:
Apologies for following up to myself, but I thought I should say that
when I added /run myself the 2.6.38 kernel booted without problems.
So... is this udev167-1 safe
On Fri, 8 Apr 2011 11:44:17 +0100
Anthony Campbell a...@acampbell.org.uk wrote:
On 08 Apr 2011, Anthony Campbell wrote:
After an upgrade today to base-files 6.3 I rashly assume things would be
fixed, but not so. My /run is no longer there but now the 2.6.38 kernels
won't boot - they stop at
Andrej Kacian andrej+deb...@kacian.sk writes:
On Fri, 8 Apr 2011 11:44:17 +0100
Anthony Campbell a...@acampbell.org.uk wrote:
On 08 Apr 2011, Anthony Campbell wrote:
After an upgrade today to base-files 6.3 I rashly assume things would be
fixed, but not so. My /run is no longer there but
On 06 Apr 2011, Benjamí Villoslada wrote:
A Dimecres 06 Abril 2011 16:30:08, Wolodja Wentland va escriure:
I assume that you are actually trying to fix a different bug, namely one
introduced by the premature installation of base-files 6.2 which created
the /run directory. The fastest fix is
On 08 Apr 2011, Anthony Campbell wrote:
After an upgrade today to base-files 6.3 I rashly assume things would be
fixed, but not so. My /run is no longer there but now the 2.6.38 kernels
won't boot - they stop at the nouveau driver. Luckily I still had a
2.6.37 kernel which isn't affected.
Last Udev version have an important error:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621087
Where can I find and download the previous 166 version?
Thanks!
Regards,
--
Benjamí
http://blog.bitassa.cat
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
On 2011-04-06 16:13 +0200, Benjamí Villoslada wrote:
Last Udev version have an important error:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621087
Where can I find and download the previous 166 version?
On snapshot.debian.org. Alternatively, you can rm -rf /run and restart
udev.
Sven
On Wed, Apr 06, 2011 at 04:13:36PM +0200, Benjamí Villoslada wrote:
Last Udev version have an important error:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621087
Where can I find and download the previous 166 version?
http://snapshot.debian.org/package/udev/166-1/
Note that downgrading
On Wed, Apr 06, 2011 at 04:20:24PM +0200, Sven Joachim wrote:
On 2011-04-06 16:13 +0200, Benjamí Villoslada wrote:
Last Udev version have an important error:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621087
Where can I find and download the previous 166 version?
On
On Wed, Apr 06, 2011 at 16:13 +0200, Benjamí Villoslada wrote:
Last Udev version have an important error:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621087
Where can I find and download the previous 166 version?
You can get them from: http://snapshot.debian.org/package/udev/166-1/
I
not empty and I had to remove it manually.
Good to see you here Roger. I handled the bug by downgrading udev, libudev,
libgudev-1.0-0 to 166-1 and base-files to 6.1, but am not sure if that is
actually the best way to deal with it. I guess that the underlying problem
(initscripts) has to be solved first
A Dimecres 06 Abril 2011 16:30:08, Wolodja Wentland va escriure:
I assume that you are actually trying to fix a different bug, namely one
introduced by the premature installation of base-files 6.2 which created
the /run directory. The fastest fix is probably to just remove /run and be
done
unfortunately not work for me because
/run was not removed due to being not empty and I had to remove it manually.
Good to see you here Roger. I handled the bug by downgrading udev, libudev,
libgudev-1.0-0 to 166-1 and base-files to 6.1, but am not sure if that is
actually the best way
14 matches
Mail list logo
