On Sun, 13 Dec 1998, Ed Cogburn wrote:
> Thanks Dan, I thought it was just me. I reported transient errors with
> apt/dpkg. Do the errors start with 'General Protection: 000000' or
> 'General failure: 0000' or something like that?
I don't know if I'm any help. I've never gotten any thing like that.
> In my original post, I believed dselect/apt/dpkg were being pushed
> beyond their capabilities. Dpkg is being swamped by packages, now more
> than 2700. However, the errors, from my point of view, are far more
> common when running dselect with apt as the access method.
I haven't used apt. I'm too stuck in my ways. A couple of months ago
(with slink/frozen) I could run dselect/dpkg into the ground, and the only
problems I'd get were dependency related. Recently I've been getting
segfaults, since I've install off a hamm CD.
> It was the first time I've seen a hard
> kernel crash outside of the X win system.
Wow. That sucks, I've had the entire system go down on me as a part
of this, but I can't say why it hasn't. As so added wierdness to my
problem, when I wrote the list emacs was bombing out with a segfault when
I'd quit. Now it works fine. I hope this doesn't turn into to hours
reboot cycle that make windows work so well. :(
> Like you this is something I've only seen recently, I don't remember
> having these kinds of problems back with Deb 1.3.1.
Well, actually I had a hamm/frozen that I upgraded through
slink/frozen, and I had no problems. Now I have hamm/stable, and it
blows. My problems are not specific to dselect. I just noticed it there
first I think because I was doing a lot of installing.
Question one question. Could you tell if the General Protection/failure
messages were from dselect, or the kernel. I have never had the pleasure.
Dan
