From: Andrew Buehler <abuehler.kernel@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Pinter <oliver.pntr@gmail.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>,
SCSI development list <linux-scsi@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: USB regression (and other failures) in 2.6.2[45]* - mostly resolved
Date: Wed, 20 Feb 2008 13:27:13 -0500 [thread overview]
Message-ID: <47BC7101.4060501@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0802201213260.5630-100000@iolanthe.rowland.org>
On 2/20/2008 12:15 PM, Alan Stern wrote:
> On Wed, 20 Feb 2008, Andrew Buehler wrote:
>> Hmm. One thing which just sprang to mind, in the stab-in-the-dark
>> category: in 2.6.24.2, launching the program on some machines gave
>> warnings along the lines of "this program is using a deprecated
>> ioctl, please convert it to SG_IO" (which I naturally cannot do
>> since it's closed and I don't have the source),
>
> You can ask the program's author to update it.
It's provided by Novell, with whom I have no direct contact and am not
presently authorized to speak on behalf of my organization. From what I
have read about the history of their support on this program and these
discs, I do not expect that they would be willing to support it except
in environments which they provide in monolithic form; it would be
possible for me to copy an updated version of the program out of such an
environment to use in my own customized one, but I am not certain that
they have even created such an updated version, and in any case
obtaining it would almost certainly require buying the latest version of
Novell ZENworks - which my organization is certainly not prepared to do
at the present time.
In other words: I don't think that's likely to be practical in the
present instance. If you have reason to believe otherwise (past positive
experience with Novell, for instance), I'd be glad to hear it.
>> I'm not sure I expressed myself clearly. I do not think the problem
>> is with the different kernels. I think the problem is with the
>> different configurations. I am asking if there are any established
>> techniques for comparing differences between config files from
>> widely different kernels.
>
> Not as far as I know.
Oh, well... thanks anyway.
Is there any place (aside from maybe the kernel changelog, which
contains a whole lot - if not several lots - of unrelated information)
where I could find a list of config-symbol name additions, changes,
deletions and meaning changes by version or by date? That would at least
let me build a mapping between the symbols in the older config and the
ones in the new one, which is about where I would have to start.
--
Andrew Buehler
next prev parent reply other threads:[~2008-02-20 18:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 21:45 USB regression (and other failures) in 2.6.2[45]* Andrew Buehler
2008-02-16 14:32 ` Oliver Pinter
2008-02-16 15:20 ` Alan Stern
2008-02-16 16:46 ` Andrew Buehler
2008-02-16 17:16 ` Alan Stern
2008-02-16 21:33 ` Andrew Buehler
2008-02-16 23:11 ` Alan Stern
2008-02-17 1:12 ` Andrew Buehler
2008-02-17 3:35 ` Alan Stern
2008-02-17 16:21 ` Andrew Buehler
2008-02-19 20:35 ` USB regression (and other failures) in 2.6.2[45]* - mostly resolved Andrew Buehler
2008-02-20 15:50 ` Alan Stern
2008-02-20 17:06 ` Andrew Buehler
2008-02-20 17:15 ` Alan Stern
2008-02-20 18:27 ` Andrew Buehler [this message]
2008-02-20 19:29 ` Alan Stern
2008-02-21 16:05 ` Andrew Buehler
2008-02-21 16:36 ` Alan Stern
2008-02-21 17:17 ` Greg KH
2008-02-21 19:43 ` Andrew Buehler
2008-02-21 20:02 ` Alan Stern
2008-02-17 4:10 ` [OT] GMail (was USB regression (and other failures)...) Joseph Fannin
2008-02-17 10:55 ` USB regression (and other failures) in 2.6.2[45]* Sergey Vlasov
2008-02-17 7:20 ` Paul Jackson
2008-02-17 16:17 ` Andrew Buehler
2008-02-17 16:20 ` Paul Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47BC7101.4060501@gmail.com \
--to=abuehler.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox