linux-kernel - Re: ketchup script and 3.0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 08 Jun 2011 00:22:29 +0300
From:	Stratos Psomadakis <psomas@....ntua.gr>
To:	Matt Mackall <mpm@...enic.com>
CC:	david@...g.hm, linux-kernel@...r.kernel.org,
	Frank Kingswood <frank@...gswood-consulting.co.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: ketchup script and 3.0

On 06/07/2011 11:59 PM, Matt Mackall wrote:
> On Tue, 2011-06-07 at 13:50 -0700, david@...g.hm wrote:
>> On Tue, 7 Jun 2011, Matt Mackall wrote:
>>
>>> But my point is that if we have adhoc transitions, we will encounter the
>>> "fix all the scripts and websites" pain at every transition. And tools
>>> that are managed via distros and the like can literally take years to
>>> get into the hands of users. It'd be nice if the copy of ketchup shipped
>>> in <enterprise distro> just worked 3 years from now because 4.0 wasn't a
>>> surprise.
>> if you special case 2.4->2.6, and make the default that 4.0 > 3.x, 5.0 > 
>> 4.x, etc won't things 'just work' for the forseeable future?
> No, because you sometimes want to know what 2.6.39++ is and what 3.0--
> is.
>
> For instance, to upgrade from 2.6.37.2 to 3.1.2, ketchup will want to
> download, cache, and apply:
>
> patch-2.6.37.2 (reversed!)
> patch-2.6.38
> patch-2.6.39
> patch-3.0 ?? <- hopefully Linus will make a delta against 2.6.39!
> patch-3.1
> patch-3.1.2
Well, if this is a ketchup-only issue (and there's no other need for
defining at which point major numbers are going to inc), we could find a
solution/workaround (to future-proof it, without the need of constant
updating of the code with every major release), but it'll probably be
uglier, and I think that what Matt proposed is better.

Anyway, when this issue is clarified, I'll try to fix the code, in order
to handle next major releases, without requiring code changes.

Thanks,

-- 
Stratos Psomadakis
<psomas@....ntua.gr>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/