I finally found the cause of this pesky bug!
At some point, an aptitude full-upgrade seemed to fix this problem.
But not always.
The problem is that I could never come up with a consistent failure
scenario. Well, today, I finally did. It turns out
that, for me, the failure only occurs when
Stephen Powell wrote:
I finally found the cause of this pesky bug!
At some point, an aptitude full-upgrade seemed to fix this problem.
That was probably at times that sysconfig-hardware was broken... A next
fixed version of that package would have reintroduced your problem.
The problem is
On Wed, 3 Feb 2010 11:53:47 -0500 (EST), Frans Pop wrote:
They are not mystery files at all. They are part of sysconfig-hardware and
their exact purpose is to bring up devices during system boot!
I'm sure that they are no mystery to you, but they *were* a mystery
to me until you explained
Stephen Powell wrote:
So whenever a dynamically linked device showed up using one of the
device numbers 0400-0403, sysconfig-hardware was convinced it needed
to be brought online immediately! What I don't understand is why,
when it is *manually* varied offline *after* being brought online
4 matches
Mail list logo
