Sounds like they might have found a practical exploit for one of the many bugs in the Core/2 that OpenBSD were throwing a fit about when it was released. Maybe they were right.
Telling end users to write their own code is more like telling someone to solve part of a 50,000 word crossword puzzle. Not everyone with a car has the tools to build their own, after all.
That's actually pretty easy to work around. Just modify mlock() and friends so that mfree() causes their allocated memory to get zeroed out. You'd only need to do it once in the kernel since every piece of security-sensitive code uses mlock already - to avoid exactly this problem with swap space.
The way Ada is different is that it makes writing incorrect code extremely hard. Comparing it to C is sort of like comparing Postgres with MySQL 4.0; you can write awful, sloppy code using both, but Postgres comes with built-in and relatively painless syntax to validate every bit of data that goes in, out, and through. Ada is more or less the same. The whole point of the language is to let you say "should never happen" in the code, instead of in the comments.
What you've just described is the update system Gentoo has used for years. And they're notably missing from the list of distros tested (but then again, that list includes Debian twice...)
What sort of idiot uses their sound card's line out to record youtube audio, when they could just download the flv using any one of 10 billion methods and run mplayer -dumpaudio on it to get the original mp3?
No. Won't work. The only thing that "Windows CE" and "Windows XP" have in common is having the word "Windows" appearing in their names. As other have pointed out both don't even run on the same architecture (x86, AMD64 and Itanium for WinXP ; ARM, MIPS and SuperH for WinCE).
I've used CE on a Via x86 within the past month, so that assumption's not entirely true.
Re:That might betray the presence of a hidden volu
on
TrueCrypt 6.0 Released
·
· Score: 1
They won't need to look that far, the fact your laptop doesn't run windows or OS X will give them an excuse to detain you for hours.
If you look at the complexity of the WDDM and yet how applications, from GDI and Win32 to OpenGL/DirectX and even overlays look like they did on XP, yet are being processed and drawn by a very new engine and work virtually flawlessly it is quite a feat. As Vista isn't just taking bitmaps of the Windows like KDE is doing or OS X does, but the WDDM shoves a lot of old drawing technology through the 3D GPU, from some basic GDI functions to font rendering and even offers up the 3D GPU for decompressing bitmaps when older applications read and draw them.
Interesting. That sounds a lot like what Xgl was doing in 2004.
I've been waiting for this release, but after one of the higher-access Gentoo devs was caught using dev servers to attack a competing distro (and resorting to name-calling afterwards) I'm not sure if I can trust them any more.
I find Cleartype unreadable with any amount of tweaking. Even on a DVI connection, I have to turn it off or I get eyestrain. The antialiasing in other OSes doesn't have this effect on me. I'd prefer a 200dpi screen though.
From what I understand of the GPL, as long as anyone else is able to hack the code by buying themselves a dev kit at fair price (the $1000) then it's OK. If you were actively preventing anyone else from getting access to the developer stuff (say by charging $15m for it) then that'd be not OK.
Sounds like they might have found a practical exploit for one of the many bugs in the Core/2 that OpenBSD were throwing a fit about when it was released. Maybe they were right.
Telling end users to write their own code is more like telling someone to solve part of a 50,000 word crossword puzzle. Not everyone with a car has the tools to build their own, after all.
Or maybe the OS on your router? From my DG834:
Yeah, it's unmodified stock firmware, but then it's never crashed or failed on me so I see no reason to change.
That's actually pretty easy to work around. Just modify mlock() and friends so that mfree() causes their allocated memory to get zeroed out. You'd only need to do it once in the kernel since every piece of security-sensitive code uses mlock already - to avoid exactly this problem with swap space.
You're missing the point. The real benefit here isn't that they're 4% more efficient, it's that they use 1/150th of the copper.
The way Ada is different is that it makes writing incorrect code extremely hard. Comparing it to C is sort of like comparing Postgres with MySQL 4.0; you can write awful, sloppy code using both, but Postgres comes with built-in and relatively painless syntax to validate every bit of data that goes in, out, and through. Ada is more or less the same. The whole point of the language is to let you say "should never happen" in the code, instead of in the comments.
Serious question: has anyone ever considered using git for the portage tree? Most of that stuff is part of its design.
What you've just described is the update system Gentoo has used for years. And they're notably missing from the list of distros tested (but then again, that list includes Debian twice...)
What sort of idiot uses their sound card's line out to record youtube audio, when they could just download the flv using any one of 10 billion methods and run mplayer -dumpaudio on it to get the original mp3?
So... what does that make my router's firewall? It's exactly the same as the one on my PC, and I'm pretty sure that's software.
How many people really have their OSes set to spin down disks when not in use?
I try to, but at the same time my OS writes log data to disk every few minutes so it never really happens.
XML was created to look like SGML but with more strict parsing rules. The rest of those TLAs you list were created out of sadism.
27 bytes should be enough f
No. Won't work. The only thing that "Windows CE" and "Windows XP" have in common is having the word "Windows" appearing in their names. As other have pointed out both don't even run on the same architecture (x86, AMD64 and Itanium for WinXP ; ARM, MIPS and SuperH for WinCE).
I've used CE on a Via x86 within the past month, so that assumption's not entirely true.
They won't need to look that far, the fact your laptop doesn't run windows or OS X will give them an excuse to detain you for hours.
Nobody I know of has cut short travel plans because of the terrorism threat
How many people do you know that have changed travel plans to avoid the TSA harassment? There's your terrorist threat.
Sounds like you want D.
What if your office runs Windows, Mac OS X, Symbian OS, Debian, Plan 9, Red Hat, MS-DOS and OpenBSD?
You're fucked either way. Ever tried developing a complex web app that runs on even 7 out of the 8 of the above?
The open source community needs to stop bitching about Microsoft and start writing better software.
They did, that's why you posted that list - isn't it?
If you look at the complexity of the WDDM and yet how applications, from GDI and Win32 to OpenGL/DirectX and even overlays look like they did on XP, yet are being processed and drawn by a very new engine and work virtually flawlessly it is quite a feat. As Vista isn't just taking bitmaps of the Windows like KDE is doing or OS X does, but the WDDM shoves a lot of old drawing technology through the 3D GPU, from some basic GDI functions to font rendering and even offers up the 3D GPU for decompressing bitmaps when older applications read and draw them.
Interesting. That sounds a lot like what Xgl was doing in 2004.
I've been waiting for this release, but after one of the higher-access Gentoo devs was caught using dev servers to attack a competing distro (and resorting to name-calling afterwards) I'm not sure if I can trust them any more.
I find Cleartype unreadable with any amount of tweaking. Even on a DVI connection, I have to turn it off or I get eyestrain. The antialiasing in other OSes doesn't have this effect on me.
I'd prefer a 200dpi screen though.
Except for the ones who let Microsoft dictate their hardware purchases, 512MB and a 1GHz CPU are still enough.
From what I understand of the GPL, as long as anyone else is able to hack the code by buying themselves a dev kit at fair price (the $1000) then it's OK. If you were actively preventing anyone else from getting access to the developer stuff (say by charging $15m for it) then that'd be not OK.