linux-kernel - Re: x86: 4kstacks default

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, 23 Apr 2008 01:41:09 -0400
From:	Daniel Hazelton <dhazelton@...er.net>
To:	david@...g.hm
Cc:	Denys Vlasenko <vda.linux@...glemail.com>,
	Romano Giannetti <romanol@...omillas.es>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: x86: 4kstacks default

On Wednesday 23 April 2008 01:25:27 david@...g.hm wrote:
> On Wed, 23 Apr 2008, Daniel Hazelton wrote:
> > On Wednesday 23 April 2008 01:03:11 Denys Vlasenko wrote:
> >> On Tuesday 22 April 2008 20:20, Romano Giannetti wrote:
> >>> On Sun, 2008-04-20 at 11:44 -0400, Daniel Hazelton wrote:
> >>>> Since the second-most-common reason for stack overages is
> >>>> ndiswrapper... Well, with there being so much more hardware now
> >>>> supported directly by the linux kernel...
> >>>
> >>> How would I like you being right... Atheros AR5008, AR5414 PHY, "not
> >>> yet here". It's almost one year now since I bought this laptop, and
> >>> till now it's the cable or ndiswrapper. But yes, it's going better. For
> >>> my first wifi laptop I waited two and a half years, now it seems that
> >>> in a bit more than one there will be an open source driver...
> >>>
> >>> I know all the trouble ndiswrapper signify. But I see also that people
> >>> around me with a laptop and linux use more ndiswrapper than a real
> >>> driver, so... be gentle with it.
> >>
> >> Nobody knows how much potential development is not done because
> >> "you can make your wifi work with ndiswrapper".
> >
> > I've got to agree with that sentiment. Once a working solution is found,
> > no matter how crappy, it seems that almost all development stops.
>
> and nobody knows how many people are running linux instead of windows
> becouse they were able to use ndiswrapper to get things running. most of
> those people contributed nothing to the kernel, but they all contributed
> to Linux, if nothing else as examples that Linux is a reasonable option
> (and some percentage of those users have contrinbuted to other opensource
> projects that they would probably never have bumped into if they were
> running windows instead)
>
> I know we will never convince each other, but we do need to recognise that
> there is another valid point of view.

And who knows how many more people would be running Linux if they didn't need 
ndiswrapper at all?

And how much better would it be if the drivers were native linux code and were 
fully supportable because of that?

There are many, many reasons why it'd be better if ndiswrapper didn't exist as 
a solution or if development on native solutions continued on at the level it 
would without ndiswrapper. 

DRH

-- 
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
--
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/