linux-kernel - Re: Unable to continue testing of 2.6.25

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]

Message-Id: <1203459307.20298.6.camel@brick>
Date:	Tue, 19 Feb 2008 14:15:07 -0800
From:	Harvey Harrison <harvey.harrison@...il.com>
To:	Frans Pop <elendil@...net.nl>
Cc:	Adrian Bunk <bunk@...nel.org>, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Unable to continue testing of 2.6.25

On Tue, 2008-02-19 at 22:55 +0100, Frans Pop wrote:
> On Sunday 17 February 2008, Adrian Bunk wrote:
> > The real problem is that the kernel seems to lack functionality you
> > require for doing some work.
> 
> Not sure how you reached that conclusion.
> 
> > Why does your work on the Debian Installer depend on VirtualBox and
> > can't be done with what the kernel already ships?
> 
> The fact that VirtualBox does not (yet) work for me with 2.6.25 means that 
> I'm unable to run 2.6.25 on my main desktop and do any real work. Rebooting 
> my desktop whenever I want to use VirtualBox is just not a realistic 
> option.
> That in turn means that I cannot do any more testing of 2.6.25, because most 
> of the testing I do consists of just using a new kernel and critically 
> observing the behavior of my system. As I've caught a fair number of bugs 
> that way for the past few releases, I'd say that's a useful contribution.

And it will be just as valuable when you stay with 2.6.24 finding bugs
there.

And once VirtualBox has been updated to work with 2.6.25, you can test
2.6.25.

Harvey

--
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/