Re: Bug #352758 [revisited]
On Tue, Jan 30, 2007 at 09:05:56PM EST, cga2000 wrote:
> I reported Bug #352758 almost a year ago and never received any
> feedback.
>
> I am not familiar with the debian bug reports system and I am beginning
> to wonder whether I forgot something .. opened the bug report with the
> wrong maintainer group .. etc.
>
> Could someone more knowledgeable than myself take a quick look and
> advise what I could/should do at this point?
Well, almost two years later, I installed a DVD burner in my old laptop
and in order to test it, I burned a couple of debian-derived Linux
LiveCD images -- grml and ubuntu .. in their latest versions.
And it looks like the original problem I reported is still there in
those two current LiveCD's. Neither could configure the "network" ..
since they couldn't find my NIC. One of them even displayed some useful
stuff blaming the issue on my "3CCFEM556" .. I forget the exact message.
I don't know if debian has anything equivalent to these live CD images,
and maybe it has been fixed in recent debian versions?
I realize I can probably modify the iso images on my HD before burning
them to optical media .. see workaround in bug report .. but isn't this
rather annoying that this same "bug/feature" is still around two years
down the line and apparently contaminating other distributions?
There must be a good reason why this wasn't fixed since it's only a
matter of issuing a cp followed by an mv to rename the .cis file .. but
I don't see anything appended to my bug report that explains why it was
not done.
Since I'm neither technically capable nor authorized to do so (and thank
goodness for that) .. am I at fault in some other way and should I
contact the debian developer about this..? Or should I just live with
it, considering that this is pretty old, uninteresting, hardware anyway
and probably not really worth fixing?
Don't take me wrong.. I'm not bitching about the debian developer .. I
can't think of anyone making this a priority .. I'm just trying to
understand a bit better how this all hangs together.
Thanks!
Reply to: