On November 26, [EMAIL PROTECTED] said:
> The next time i'm physically near the machine, i'll try reseating
> the battery to clear it up, and report back if that clears my
> problem.
Woohoo! It worked!
Before shutting it down to reseat the battery, i removed the rtc-dev
module, which let me hav
On Mon, Nov 27, 2006 at 03:13:21PM -0700, Gordon Farquharson wrote:
> Unless you built your own installer image to use packages from
> unstable, or manually switched to unstable packages after the install,
> you would not have been affected by the bug. And if you are using
> unstable, you shouldn't
Hi Phil
On 11/27/06, Philip Armstrong <[EMAIL PROTECTED]> wrote:
So, a polite request: next time, would you mind putting up a bug
report so that people can have some warning that there might be a
problem? (OK, I should probably have posted to the list to enquire
earlier myself...)
Unless you
> No, I sent a email to the package maintainer instead :-) He has fixed
> the problem in the repository version of nslu2-utils.
Do you know how many times I reflashed my (lovely new) nslu2 last week
and ran the Debian installer again to get back to a working system? A
lot, that's how many. (Yes, I
Daniel Kahn Gillmor wrote:
> Another use of bug reports (especially ones about bugs that make
> machines unbootable, and would therefore be critical) is to keep
> packages from filtering down into testing while they're in a dangerous
> state.
Package maintainers file RC bugs to prevent this kind o
On November 26, [EMAIL PROTECTED] said:
> Yeah, I know, but I was discussing the problem via email, so in this
> case, apart from the reason you mention above, there was no reason
> to file a bug report.
Another use of bug reports (especially ones about bugs that make
machines unbootable, and wou
Hi Daniel
On 11/26/06, Daniel Kahn Gillmor <[EMAIL PROTECTED]> wrote:
OK, good to know. posting it as a bug as well would be helpful for
those of us who check these things before considering an upgrade. i
know i'd be interested in the details.
Yeah, I know, but I was discussing the problem
Hi Gordon--
On November 25, [EMAIL PROTECTED] said:
> No, I sent an email to the package maintainer instead :-)
OK, good to know. posting it as a bug as well would be helpful for
those of us who check these things before considering an upgrade. i
know i'd be interested in the details.
> Yes.
Hi Daniel
On 11/25/06, Daniel Kahn Gillmor <[EMAIL PROTECTED]> wrote:
yikes! Are you sure? Has this been reported as a bug yet?
No, I sent an email to the package maintainer instead :-) He has fixed
the problem in the repository version of nslu2-utils
(http://svn.debian.org/wsvn/pkg-nslu2-u
Hi Gordon--
On November 25, [EMAIL PROTECTED] said:
> I have tested this version of the kernel, and it works, so switching
> to it shouldn't be a problem. I wouldn't switch the rest of the
> system to packages from unstable just yet - for instance, there
> appears to be a problem with the version
Hi Daniel
On 11/25/06, Daniel Kahn Gillmor <[EMAIL PROTECTED]> wrote:
I'd like to try to upgrade to the new kernel
(linux-image-2.6.18-3-ixp4xx), but i want to make sure i can recover
properly if something goes wrong.
I have tested this version of the kernel, and it works, so switching
to it
I'm very pleased with the progress of the debian arm port. My NSLU2
is running fine, and i'm looking forward to seeing it become an
official stable release with the etch transition.
I'd like to try to upgrade to the new kernel
(linux-image-2.6.18-3-ixp4xx), but i want to make sure i can recover
p
12 matches
Mail list logo
