Re: Bug#284952: The USB block device should be disabled
On Mon, Jan 24, 2005 at 09:53:54AM +0100, Thiemo Seufer wrote: > Horms wrote: > > I have gone through and turned this off for everything except mips, > > for which I am not sure about the structure of the package. > > For mips it is already disabled in the relevant configs. Thanks for clarifying that. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#284952: The USB block device should be disabled
Horms wrote: > I have gone through and turned this off for everything except mips, > for which I am not sure about the structure of the package. For mips it is already disabled in the relevant configs. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284952: The USB block device should be disabled
I have gone through and turned this off for everything except mips, for which I am not sure about the structure of the package. Apoliges in advance to kerenel-image maintainers if I broke anything. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284952: The USB block device should be disabled
On Tue, 2005-01-18 at 12:56 +0900, Horms wrote: > Also, sould I go through and fix the config > in svn, even though I can't build for any of these > architectures? Horms - in general you are welcome to modify the ia64 configs; though you can also just dup a bug & I can handle it before my next upload. I've gone ahead and fixed this one in svn. fyi, the current state of the art for ia64 config handling is to just modify the itanium config & execute the sync_configs target in debian/rules. -- dann frazier <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284952: The USB block device should be disabled
On Tue, Jan 18, 2005 at 01:13:57PM +0900, Horms wrote: > On Tue, Jan 18, 2005 at 04:59:04AM +0100, Sven Luther wrote: > > On Tue, Jan 18, 2005 at 12:56:51PM +0900, Horms wrote: > > > On Mon, Jan 17, 2005 at 12:03:51PM +0100, Frank Lichtenheld wrote: > > > > On Sun, Jan 16, 2005 at 12:33:48PM +0100, Paul van Tilburg wrote: > > > > > The USB block device is known to be experimental and buggy. > > > > > CONFIG_BLK_DEV_UB=m should be set to 'n'. > > > > > > > > > > Since the ub modules takes preference of the old, though working > > > > > usb-storage, hotplug loads ub. Blacklisting ub doesn't help, loading > > > > > usb-storage doesn't work either. > > > > > I really would like for UB to be disable until proven reasonably > > > > > stable. > > > > > > > > Can someone merge this bug with #283852, plz? I'm unsure which of them > > > > to reassign. > > > > I wonder about this, would it not be enough to blacklist the UB generated > > modules in hotplug and/or discover ? > > According to Paul van Tilburg, in Bug#284952 this does not help. > Though he didn't expand on why. Ah, i also have some second-thoughts about this, since we cannot know exactly how the user is loading the modules. I will disable it in the ppc 2.6.9/2.6.10 kernels. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#283852: Bug#284952: The USB block device should be disabled
On Tue, Jan 18, 2005 at 04:59:04AM +0100, Sven Luther wrote: > On Tue, Jan 18, 2005 at 12:56:51PM +0900, Horms wrote: > > On Mon, Jan 17, 2005 at 12:03:51PM +0100, Frank Lichtenheld wrote: > > > On Sun, Jan 16, 2005 at 12:33:48PM +0100, Paul van Tilburg wrote: > > > > The USB block device is known to be experimental and buggy. > > > > CONFIG_BLK_DEV_UB=m should be set to 'n'. > > > > > > > > Since the ub modules takes preference of the old, though working > > > > usb-storage, hotplug loads ub. Blacklisting ub doesn't help, loading > > > > usb-storage doesn't work either. > > > > I really would like for UB to be disable until proven reasonably stable. > > > > > > Can someone merge this bug with #283852, plz? I'm unsure which of them > > > to reassign. > > I wonder about this, would it not be enough to blacklist the UB generated > modules in hotplug and/or discover ? According to Paul van Tilburg, in Bug#284952 this does not help. Though he didn't expand on why. > > The merge thing doesn't work well with the way we > > have multiple source packages for the kernel. > > > > It seems that this problem actually effects the following > > source packages. > > > > kernel-image-2.6.10-alpha-2.6.10 > > kernel-image-2.6.10-ia64-2.6.10 > > kernel-image-2.6.9-amd64-2.6.9 > > kernel-image-2.6.9-ia64-2.6.9 > > kernel-image-2.6.9-sparc-2.6.9 > > kernel-patch-2.6.10-mips-2.6.10 > > kernel-patch-powerpc-2.6.10-2.6.10 > > kernel-patch-powerpc-2.6.9-2.6.9 > > > > Would it be of value to duplicate, say #283852, > > assign one copy to each of these source packages, > > and then merge #283852 with #284952 on one package, > > say kernel-patch-powerpc-2.6.9-2.6.9, where > > at one of the bugs originated. > > > > Also, sould I go through and fix the config > > in svn, even though I can't build for any of these > > architectures? > > Fine with me, but see above. > > Friendly, > > Sven Luther -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284952: The USB block device should be disabled
On Tue, Jan 18, 2005 at 12:56:51PM +0900, Horms wrote: > On Mon, Jan 17, 2005 at 12:03:51PM +0100, Frank Lichtenheld wrote: > > On Sun, Jan 16, 2005 at 12:33:48PM +0100, Paul van Tilburg wrote: > > > The USB block device is known to be experimental and buggy. > > > CONFIG_BLK_DEV_UB=m should be set to 'n'. > > > > > > Since the ub modules takes preference of the old, though working > > > usb-storage, hotplug loads ub. Blacklisting ub doesn't help, loading > > > usb-storage doesn't work either. > > > I really would like for UB to be disable until proven reasonably stable. > > > > Can someone merge this bug with #283852, plz? I'm unsure which of them > > to reassign. I wonder about this, would it not be enough to blacklist the UB generated modules in hotplug and/or discover ? > The merge thing doesn't work well with the way we > have multiple source packages for the kernel. > > It seems that this problem actually effects the following > source packages. > > kernel-image-2.6.10-alpha-2.6.10 > kernel-image-2.6.10-ia64-2.6.10 > kernel-image-2.6.9-amd64-2.6.9 > kernel-image-2.6.9-ia64-2.6.9 > kernel-image-2.6.9-sparc-2.6.9 > kernel-patch-2.6.10-mips-2.6.10 > kernel-patch-powerpc-2.6.10-2.6.10 > kernel-patch-powerpc-2.6.9-2.6.9 > > Would it be of value to duplicate, say #283852, > assign one copy to each of these source packages, > and then merge #283852 with #284952 on one package, > say kernel-patch-powerpc-2.6.9-2.6.9, where > at one of the bugs originated. > > Also, sould I go through and fix the config > in svn, even though I can't build for any of these > architectures? Fine with me, but see above. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284952: The USB block device should be disabled
On Mon, Jan 17, 2005 at 12:03:51PM +0100, Frank Lichtenheld wrote: > On Sun, Jan 16, 2005 at 12:33:48PM +0100, Paul van Tilburg wrote: > > The USB block device is known to be experimental and buggy. > > CONFIG_BLK_DEV_UB=m should be set to 'n'. > > > > Since the ub modules takes preference of the old, though working > > usb-storage, hotplug loads ub. Blacklisting ub doesn't help, loading > > usb-storage doesn't work either. > > I really would like for UB to be disable until proven reasonably stable. > > Can someone merge this bug with #283852, plz? I'm unsure which of them > to reassign. The merge thing doesn't work well with the way we have multiple source packages for the kernel. It seems that this problem actually effects the following source packages. kernel-image-2.6.10-alpha-2.6.10 kernel-image-2.6.10-ia64-2.6.10 kernel-image-2.6.9-amd64-2.6.9 kernel-image-2.6.9-ia64-2.6.9 kernel-image-2.6.9-sparc-2.6.9 kernel-patch-2.6.10-mips-2.6.10 kernel-patch-powerpc-2.6.10-2.6.10 kernel-patch-powerpc-2.6.9-2.6.9 Would it be of value to duplicate, say #283852, assign one copy to each of these source packages, and then merge #283852 with #284952 on one package, say kernel-patch-powerpc-2.6.9-2.6.9, where at one of the bugs originated. Also, sould I go through and fix the config in svn, even though I can't build for any of these architectures? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284952: The USB block device should be disabled
On Sun, Jan 16, 2005 at 12:33:48PM +0100, Paul van Tilburg wrote: > The USB block device is known to be experimental and buggy. > CONFIG_BLK_DEV_UB=m should be set to 'n'. > > Since the ub modules takes preference of the old, though working > usb-storage, hotplug loads ub. Blacklisting ub doesn't help, loading > usb-storage doesn't work either. > I really would like for UB to be disable until proven reasonably stable. Can someone merge this bug with #283852, plz? I'm unsure which of them to reassign. Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284952: The USB block device should be disabled
On Mon, Jan 17, 2005 at 02:17:28PM +0900, Horms wrote: > I thought it already was marked as n. > Does anyone have an objection to making this so? No, please turn it off. I hadn't realized it's turned on either. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284952: The USB block device should be disabled
On Mon, Jan 17, 2005 at 02:17:28PM +0900, Horms wrote: > On Sun, Jan 16, 2005 at 12:33:48PM +0100, Paul van Tilburg wrote: > > Package: kernel-image-2.6.9-powerpc > > Version: 2.6.9-4 > > Followup-For: Bug #284952 > > > > The USB block device is known to be experimental and buggy. > > CONFIG_BLK_DEV_UB=m should be set to 'n'. > > > > Since the ub modules takes preference of the old, though working > > usb-storage, hotplug loads ub. Blacklisting ub doesn't help, loading > > usb-storage doesn't work either. > > I really would like for UB to be disable until proven reasonably stable. > > I thought it already was marked as n. Just to check: --- [EMAIL PROTECTED] dpkg -l kernel-image-2.6.9-powerpc | grep ii ii kernel-image-2.6.9-powerpc 2.6.9-4Linux kernel image for 2.6.9-powerpc [EMAIL PROTECTED] grep DEV_UB /boot/config-2.6.9-powerpc CONFIG_BLK_DEV_UB=m --- > Does anyone have an objection to making this so? I have none. Paul -- Student @ Eindhoven | JID: [EMAIL PROTECTED] University of Technology, The Netherlands | email: [EMAIL PROTECTED] >>> Using the Power of Debian GNU/Linux <<< | GnuPG: finger [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284952: The USB block device should be disabled
On Sun, Jan 16, 2005 at 12:33:48PM +0100, Paul van Tilburg wrote: > Package: kernel-image-2.6.9-powerpc > Version: 2.6.9-4 > Followup-For: Bug #284952 > > The USB block device is known to be experimental and buggy. > CONFIG_BLK_DEV_UB=m should be set to 'n'. > > Since the ub modules takes preference of the old, though working > usb-storage, hotplug loads ub. Blacklisting ub doesn't help, loading > usb-storage doesn't work either. > I really would like for UB to be disable until proven reasonably stable. I thought it already was marked as n. Does anyone have an objection to making this so? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284952: The USB block device should be disabled
Package: kernel-image-2.6.9-powerpc Version: 2.6.9-4 Followup-For: Bug #284952 The USB block device is known to be experimental and buggy. CONFIG_BLK_DEV_UB=m should be set to 'n'. Since the ub modules takes preference of the old, though working usb-storage, hotplug loads ub. Blacklisting ub doesn't help, loading usb-storage doesn't work either. I really would like for UB to be disable until proven reasonably stable. Greetings, Paul -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.9-powerpc Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-image-2.6.9-powerpc depends on: ii initrd-tools 0.1.76 tools to create initrd image for p ii module-init-tools 3.1-rel-2 tools for managing Linux kernel mo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
