[Bug 7207] Improving ZIP drive support
bugzilla-daemon at bugzilla.ubuntu.com
bugzilla-daemon at bugzilla.ubuntu.com
Tue Sep 27 16:02:28 UTC 2005
Please do not reply to this email. You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=7207
Ubuntu | linux
ben.collins at ubuntu.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
------- Additional Comments From ben.collins at ubuntu.com 2005-09-27 17:02 UTC -------
Ok, so the drive actually works, correct? The thing here is that from my point
of view (the kernel maintainer) I just have to assure that it works. Making
things look better from the GUI isn't a bug the kernel maintainer handles.
Honestly, when I read your report, I was expecting terrible terrible things, but
I think you are over dramatizing the problems. Sure, it doesn't look good from
the UI, and that's a user issue we don't wont, but it wasn't horrible and maddening.
There's several issues I can outline from your report:
1) ppa does not get autoloaded. This is likely because paraport is such a dated
interface, and it doesn't lend itself easily to autodetection. This will
probably not get fixed.
2) I think ide-floppy was actually loaded, you said you did load it (guessing
modprobe) and it didn't change anything, plus the drive would not have shown
under "Computer" unless it was already loaded. So that's a non-issue. Modprobe
would exit with no messages if the module was already loaded.
3) Partitions not getting automounted. My guess here is that the driver or the
drive is not getting or handling signals for media change. This is much like a
CD drive. I'm guessing this should work, and maybe the driver handles it, but
since zipdrives are so old, and not many people use them anymore, there's not
been much maint on the driver itself. I'll look into this.
4) Eject. This surely is a bug, and one which I'll look into.
--
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the kernel-bugs
mailing list