These cards had a standard size - 80 columns by 25 rows... Now you know why there is such a thing as an IBM 80 x 25 display - one screen could accurately represent a full card
Actually, the standard punch card is 80 columns by 12 rows (rows 0-9, X, and Y). And one card represents just one line, whereas you can get 25 lines on an 80x25 display.
No, that's not correct either. It's a single process, but it's multithreaded. Perhaps you're confused by how LinuxThreads (the old Linux 2.0 thread implementation) created a process per thread. There were some issues with that approach, since processes really weren't meant to be threads. The current Linux thread implementation, NPTL, is much more efficient, and is supported in Linux kernel version 2.6 and later (and I guess some 2.5.x development versions).
No, the whole point of btlaunchmany and btlaunchmanycurses is that you have one process that downloads/seeds a bunch of torrents.
Re:The annoyances of Mozilla products (Windows)
on
Firefox 1.05 Released
·
· Score: 1
Now if the local settings folder was used, then anyone that uses that computer would have access to the cached files, cookies, etc.
No, the NTFS permissions on the %USERPROFILE% directory (i.e.,...\Documents and Settings\SomeUser) default to full control for Administrators, SYSTEM, and the user, nothing for anyone else. "Local Settings" belong to the user on that machine, not all users on that machine.
And if you're running Windows with %USERPROFILE% on a FAT filesystem, you're quite obviously not "trying to keep the computer in a secure environment."
And yet, after all these years, they are still finding buffer overflows in these 8000 lines of code.
You make it sound like zlib was written years ago, and the only changes that have ever been made to it since then have been security fixes. That is incorrect. This particular security bug was not present in version 1.0 of zlib. It wasn't even present in version 1.1. It was introduced in version 1.2.1 of zlib, which has been around for less than two years.
I'm sorry to hear that your son's development has been set back by something. However, I doubt it has anything to do with thimerosal, seeing that the MMR vaccine used in the US, MMR II from Merck, has never contained thimerosal. Thimerosal was used in DTaP (diphtheria, tetanus, and pertussis), hepatitis B, and influenza vaccines.
The same state any non-eutectic alloy is between its freezing and melting points--partly solid and partly liquid.
Anyways, there are plenty of metal alloys that are liquid at or slightly above room temperature.
But even discounting alloys, there's are a few other elemental metals other than mercury that are liquid at room temp (assuming your room has a computer or two to keep it warm): Gallium melts at 29.76 degrees C and Cesium at 28.44 degrees (I'd keep the latter far from my computer though). Rubidium melts at 39.31 degrees, so it'd be liquid at the temperatures today's GPUs reach (but I'd keep that far from my computer too).
The fsync() function shall request that all data for the open file descriptor named by fildes is to be transferred
to the storage device associated with the file described by fildes. The nature of the transfer is implementation-defined.
If _POSIX_SYNCHRONIZED_IO is not defined, the wording relies
heavily on the conformance document to tell the user what can be
expected from the system. It is explicitly intended that a null
implementation is permitted. This could be valid in the case where
the system cannot assure non-volatile storage under any circumstances
or when the system is highly fault-tolerant and the
functionality is not required. In the middle ground between these
extremes, fsync()
might or might not actually cause data
to be written where it is safe from a power failure.
(Emphasis added). If you don't want your hard drive to cache writes, send it a command to turn off the write cache. Don't rely on fsync(). Either that, or hack your kernel so that fsync() will send a SYNCHRONIZE CACHE command to the drive. That'll sync the entire drive cache though, not just the blocks associated with the file descriptor you passed to fsync().
Correct. Because - here's the rub, genius - those diffs are between Safari versions, and therefore they can not be applied directly to KHTML source code. Because Safari is, like, different?
Oh, so Apple should also do the work to integrate their patches in to the current KHTML codebase? For free? Dream on... That's the KHTML developers' job. Zack Rusin is whining like a baby that waaaah, everyone says that Apple's cooperating with him, but they're not. However, he thinks that cooperation means that Apple will send a few developers over and handhold him through every change.
Yes, I realize that integrating the changes will be difficult; I was in a similar situation and had to manually merge in a bunch of code. But it's ludicrous to say that Apple's being uncooperative because they won't provide patches that can be simply merged in to the current codebase.
I had the XP64 beta, and NX bit was *on* by default for everything.
I have the XP x64 release (MSDN version), and NX defaulted to opt-in ("Turn on DEP for essential Windows programs and services only" in MS terminology).
I changed it to opt-out, and the only incompatibility I've seen so far is the QuickBooks 2005 CD autorun thing. Firefox 32-bit and 64-bit both work fine.
Having read the article and looked at your Ocaml code
Glad to hear it... I guess the next step is to look at my name and/or email address. After that, you should see that it's not my article or my Ocaml code.
I know this is Slashdot, but you really should read the article, even if you haven't grown up yet. Your question, "Any chance your implementation is not memoizing?" will be answered once you read the article.
A month later he was moved to a Kandahar prison camp. . ..[is it really that cold on Cuba??? no, but you can always torture people by freezing them with air condition...]
Works fine for me... at least Chinese does (and Japanese, and Korean, and Thai, and Arabic, and Hebrew); I don't have any fonts with Devanagari characters, so neither Mozilla nor Safari could display Hindi. Tested with Mozilla 1.7 and Firefox 1.0 on OSX 10.2.8.
Slashdot Mirror
Actually, the standard punch card is 80 columns by 12 rows (rows 0-9, X, and Y). And one card represents just one line, whereas you can get 25 lines on an 80x25 display.
No, that's not correct either. It's a single process, but it's multithreaded. Perhaps you're confused by how LinuxThreads (the old Linux 2.0 thread implementation) created a process per thread. There were some issues with that approach, since processes really weren't meant to be threads. The current Linux thread implementation, NPTL, is much more efficient, and is supported in Linux kernel version 2.6 and later (and I guess some 2.5.x development versions).
No, the whole point of btlaunchmany and btlaunchmanycurses is that you have one process that downloads/seeds a bunch of torrents.
No, the NTFS permissions on the %USERPROFILE% directory (i.e., ...\Documents and Settings\SomeUser) default to full control for Administrators, SYSTEM, and the user, nothing for anyone else. "Local Settings" belong to the user on that machine, not all users on that machine.
And if you're running Windows with %USERPROFILE% on a FAT filesystem, you're quite obviously not "trying to keep the computer in a secure environment."
You make it sound like zlib was written years ago, and the only changes that have ever been made to it since then have been security fixes. That is incorrect. This particular security bug was not present in version 1.0 of zlib. It wasn't even present in version 1.1. It was introduced in version 1.2.1 of zlib, which has been around for less than two years.
"Native Americans"? I'm a native American, seeing that I was born and raised in America. However, I'm not Indian.
Should've linked to loopback.jpg instead.
Well, it certainly informed me!
Yup, NyQuil brand!
I'm sorry to hear that your son's development has been set back by something. However, I doubt it has anything to do with thimerosal, seeing that the MMR vaccine used in the US, MMR II from Merck, has never contained thimerosal. Thimerosal was used in DTaP (diphtheria, tetanus, and pertussis), hepatitis B, and influenza vaccines.
Lignux! 'cuz there's GNU(tm) inside of every Linux(tm) system, donchaknow?
Sure it does.
Also, the of that page is "404 Not Found". Now that's quality work there!
You fail it. Hard.
wins!
No. It doesn't.
Anyways, there are plenty of metal alloys that are liquid at or slightly above room temperature.
But even discounting alloys, there's are a few other elemental metals other than mercury that are liquid at room temp (assuming your room has a computer or two to keep it warm): Gallium melts at 29.76 degrees C and Cesium at 28.44 degrees (I'd keep the latter far from my computer though). Rubidium melts at 39.31 degrees, so it'd be liquid at the temperatures today's GPUs reach (but I'd keep that far from my computer too).
Oh, so Apple should also do the work to integrate their patches in to the current KHTML codebase? For free? Dream on... That's the KHTML developers' job. Zack Rusin is whining like a baby that waaaah, everyone says that Apple's cooperating with him, but they're not. However, he thinks that cooperation means that Apple will send a few developers over and handhold him through every change.
Yes, I realize that integrating the changes will be difficult; I was in a similar situation and had to manually merge in a bunch of code. But it's ludicrous to say that Apple's being uncooperative because they won't provide patches that can be simply merged in to the current codebase.
I have the XP x64 release (MSDN version), and NX defaulted to opt-in ("Turn on DEP for essential Windows programs and services only" in MS terminology).
I changed it to opt-out, and the only incompatibility I've seen so far is the QuickBooks 2005 CD autorun thing. Firefox 32-bit and 64-bit both work fine.
ROM 3 machine required for the sound clip. Otherwise, you just get a list of the people on the IIGS team.
Glad to hear it... I guess the next step is to look at my name and/or email address. After that, you should see that it's not my article or my Ocaml code.
I know this is Slashdot, but you really should read the article, even if you haven't grown up yet. Your question, "Any chance your implementation is not memoizing?" will be answered once you read the article.
Ah, yes... Kandahar, Cuba. Lovely place.
You idiot. Come back when you learn how to read.
Works fine for me... at least Chinese does (and Japanese, and Korean, and Thai, and Arabic, and Hebrew); I don't have any fonts with Devanagari characters, so neither Mozilla nor Safari could display Hindi. Tested with Mozilla 1.7 and Firefox 1.0 on OSX 10.2.8.