fortunatly for IBM and Linux the work done "in kernel" for the new threading stuff was done by the people who did NPTL, NGPT was done in a way to NOT touch the kernel (or in really minimal ways, i forget exactly) on purpose.
later when NPTL went and put in the much needed changes for a more scalable threading arch. NGPT changed their implementation to make use of it. meaning no external patches needed for IBM's stuff.
that and NGPT will not be the default userspace threading system since NPTL is in glibc already.
I work in information and network security, and I'd say that you aren't really solving TOO much with your suggestion of fingerprint, MAC address, etc
reducing the ability for outsiders to influence access isn't solving much?
The problem is not people figuring out people's passwords. I'd just like to pose: What happens when a buffer overflow is discovered in the biometric information acceptance daemon?
stop using bad programming practices and allow for dynamic length buffers, or at the very least use checked length function calls.
security is a multi prong problem that demands multiple solutions, saying that one solution doesn't solve all the issues is a no duh type statement.
just run apt-cache search scsi all those utilities (and more) are returned along with a brief description which is enough to say THIS IS WHAT YOU WANT if you know what you want in terms of functionality.
>Konq isn't a stand alone application. It shares >code. So, while Moz may seem bigger, if you look at >everything Konq uses in order to function, this >tight little app... well... probably isn't.
since the link for the parser is dated 2000 it's a bit confusing as to why this is news. However the 3.4 changelog (yes, 2 versions away for both features) meantions both. http://gcc.gnu.org/gcc-3.4/changes.html
no, that is not an issue, C has a standard ABI, the only thing that would cause problems is a precompile full module w/ 2.95 and a precompiled full kernel w/ 3.2, recompiling the source hooks that nvidia provides is enough.
note: I moded this informative, because while its a poor answer to the question it's a reply to, i think it answers many questions other readers may have.
Plus, has it occured to anyone that the rash of security "problems" from MS might be due to the fact that they really are getting serious about security over there
so why does IE have 20 open security issues still?
considering c1 doesn't compile c++ compliant code half the time, especially dealing w/ nice features like template's and of course the ever stupid for loop scope bug,
who cares how fast it is since you have to change your code.
Slashdot Mirror
Differential X Protocol Compressor
http://vigor.nu/dxpc/
>Funny, but nobody else had such unusual compiler
>requirements.
except for QT, and KDE. G++ was broken as of 3.0 up untill 3.2. known, documented bug.
well, 24 hrs redone 3 times to make it funny.
fortunatly for IBM and Linux the work done "in kernel" for the new threading stuff was done by the people who did NPTL, NGPT was done in a way to NOT touch the kernel (or in really minimal ways, i forget exactly) on purpose.
later when NPTL went and put in the much needed changes for a more scalable threading arch. NGPT changed their implementation to make use of it. meaning no external patches needed for IBM's stuff.
that and NGPT will not be the default userspace threading system since NPTL is in glibc already.
reducing the ability for outsiders to influence access isn't solving much?
The problem is not people figuring out people's passwords. I'd just like to pose: What happens when a buffer overflow is discovered in the biometric information acceptance daemon?
stop using bad programming practices and allow for dynamic length buffers, or at the very least use checked length function calls.
security is a multi prong problem that demands multiple solutions, saying that one solution doesn't solve all the issues is a no duh type statement.
just run apt-cache search scsi all those utilities (and more) are returned along with a brief description which is enough to say THIS IS WHAT YOU WANT if you know what you want in terms of functionality.
>Konq isn't a stand alone application. It shares >code. So, while Moz may seem bigger, if you look at >everything Konq uses in order to function, this >tight little app... well... probably isn't.
KHTML is much smaller than gecko
since the link for the parser is dated 2000 it's a bit confusing as to why this is news. However the 3.4 changelog (yes, 2 versions away for both features) meantions both.
http://gcc.gnu.org/gcc-3.4/changes.html
they only need documentation if they're using the language, they can't use the language w/out the download, the download contains the documentation.
no, that is not an issue, C has a standard ABI, the only thing that would cause problems is a precompile full module w/ 2.95 and a precompiled full kernel w/ 3.2, recompiling the source hooks that nvidia provides is enough.
why would linux want to run freebsd when it can run linux?
http://user-mode-linux.sourceforge.net/
but hopefully this gets it past the retarded filter.
s tudio.asp
camstudio found on codeproject
http://www.codeproject.com/tools/cam
free, with source.
note: I moded this informative, because while its a poor answer to the question it's a reply to, i think it answers many questions other readers may have.
i read your faq, the main advantages (localization and interaction) that you list DO exist in deb's.
works fine on moz 1.2
http://www.boost.org
besides, do you really think it's the IDE that makes your competitors more competitive? I do crossplatform day in day out, its NOT THAT HARD
apt-get install libapache-mod-perl
hint: learn to type faster than 3 words a minute and you're all set
And that Debian releases a security notice for every flaw found in every (over 10k) packages that they maintain.
MS on the other hand offen ignores security issues (21 open security problems with IE.) and do not maintain as many packages.
so why does IE have 20 open security issues still?
the same thing.
what driver are you using?
just use CUPS, cupsomatic from linux-print and the hpijs driver from on sourceforge (from HP) my HP 960c prints very, very, very well.
using debian the setup is extreamly simple too
considering c1 doesn't compile c++ compliant code half the time, especially dealing w/ nice features like template's and of course the ever stupid for loop scope bug,
who cares how fast it is since you have to change your code.
you already gave them permission when you agreed to point 12 of the license
people who want something besides html?
because his opinions are interesting while yours are not.