My method of soldering IC's to a board is simple and IPC approved
What's IPC? FWIW, I'm definitely no expert, but I did take a course in surface mount soldering at the local community college (just for geek knowledge reasons:), and we were taught to do it the way you describe.
Anyways, the course has been useful... I fixed a cellphone that had a tiny capacitor come loose (and I mean tiny--0.5mm x 0.5mm x 1.0mm). Also replaced a broken 0.5mm pitch FPC connector (admittedly, I did lift a pad while removing the old one... it was a pad that wasn't connected to anything though; just a small bit of metal).
Ah, I got the impression from the article that there was only one preserved pup... but last year's article has more details and does say that they have DNA from three individuals.
You might try setting your calculator so that it doesn't round to integer. 3141592799 is prime. 31415927299 / 3 = 1047197599 + 2/3.
P.S. Another thing worthy of a Nature article... an integer is evenly divisible by 3 if the sum of its digits is evenly divisible by 3. 3+1+4+1+5+9+2+7+9+9=50. 5+0=5. 5 is not evenly divisible by 3. Therefore neither is 31415927299.
P.P.S. 1047197600 has two zeros at the end. If you multiply it by any integer, the product will have at least two zeros at the end. Therefore a trivial inspection would show that 3*1047197600 != 3141592799.
Hey, I think I found a pattern to the prime numbers!!!1!! While I admit I haven't had a chance to try them all, it looks like primes greater than 3 are of the form 6n-1 or 6n+1, where n is an integer.
Plus, the "important information" section of today's patch [apple.com] has the same language about sendmail and OpenSSL.
Hmm, interesting... my guess is that's just some overzealous copy and paste from the previous security update.
Now, as for which OpenSSL bug this is for... my/usr/lib/libssl.* and/usr/lib/libcrypto.* are still dated 03/03. Here's a list of the files included in the update:
./usr/bin/make_printerdef Tue Mar 18 18:40:38 2003 ./usr/bin/make_smbcodepage Tue Mar 18 18:40:40 2003 ./usr/bin/make_unicodemap Tue Mar 18 18:40:42 2003 ./usr/bin/nmblookup Tue Mar 18 18:40:43 2003 ./usr/bin/rpcclient Tue Mar 18 18:40:41 2003 ./usr/bin/smbcacls Tue Mar 18 18:40:43 2003 ./usr/bin/smbclient Tue Mar 18 18:40:35 2003 ./usr/bin/smbcontrol Tue Mar 18 18:40:38 2003 ./usr/bin/smbpasswd Tue Mar 18 18:40:39 2003 ./usr/bin/smbspool Tue Mar 18 18:40:36 2003 ./usr/bin/smbstatus Tue Mar 18 18:40:37 2003 ./usr/bin/testparm Tue Mar 18 18:40:36 2003 ./usr/bin/testprns Tue Mar 18 18:40:37 2003 ./usr/libexec/httpd/libssl.so Tue Mar 18 11:33:25 2003 ./usr/sbin/nmbd Tue Mar 18 18:40:34 2003 ./usr/sbin/smbd Tue Mar 18 18:40:33 2003 ./usr/sbin/swat Tue Mar 18 18:40:35 2003
So it looks like OpenSSL itself wasn't updated--only mod_ssl for Apache. It's now at version 2.8.13, with fixes for the RSA timing attack. Seems like they should've instead upgraded OpenSSL itself to the version that always turns on RSA blinding.
BTW, you might want to take a look at what Google has to say about romanization wo o. In particular, the first hit says, "The Romanization is "o", but some people use "wo" instead."
Some of us don't sit around all day waiting to reply to people on Slashdot. Why would I run "No, Japanese understand!" through babelfish? If I used the fish, I'd feed it proper English.
It looks like proper Japanese to me... There are many ways to romanize Japanese--the particle "wo" is often romanized as "o". And while you've shown me that you're quite impolite, that's you, not me.
iie... nihongo o wakarimasu yo.
wo3 ye3 dong3 zhong1wen2.
(why did Slashdot disable Unicode HTML entities? Tried to post in UTF-8, but got the stupid Lameness filter encountered. Post aborted!
Reason: Please use fewer 'junk' characters.)
Dump has been the standard Unix backup program for decades... I don't use Linux, but if I did, I'd consider it a bug that dump didn't work properly.
Seems to me that Linus (or another kernel hacker) should fix the ext2 race condition reported in that thread, rather than blithely dismiss the problem with, "dump was a stupid program in the first place."
Of course FP can be implemented on a 6502... AppleSoft BASIC, written by MicroSoft and included in the ROM of all but the earliest Apple ][s (and available on floppy or cassette for the ones that didn't have it in ROM), had floating point routines, including trig functions, log, and square root.
Someone should start a BSD C/C++ compiler project
on
RMS Turns 50
·
· Score: 2, Insightful
My background is math, not CS, but I'm led to believe that writing a compiler (or at least the core of one) is a standard thing to do for undergrad CS students... some enterprising hacker should write a bare-bones C compiler and release it under the BSD license. It seems to me that if it were well-designed, plenty of hackers would be glad to help out with the optimizer, writing backends for other CPUs, etc... and perhaps after a few years, the compiler would be solid enough for the *BSDs to switch to as their default compiler.
Re:Goddamn GNU/Linux people
on
RMS Turns 50
·
· Score: 1
I began a bit of a project to see how easy it is to compile the BSD toolchain to run under Linux. Guess what, it's not that hard at all.
Cool, I've been wanting to make a BSD/Linux distro too (for the same reasons as you), but haven't had the time... NetBSD has done a lot of work recently to get their system cross-buildable on other OSes, such as Linux. Perhaps that'll help some...
I don't think it's important what the instruction is named... sure, the 6502 doesn't have an instruction named "ADD", but it has add and subtract instructions--"ADC" and "SBC". It's like complaining the 80x86 doesn't have a "LDA" instruction... how are you gonna load your A register without LDA??? Oh, MOV AX... never mind.
Now, the IBM 1620 didn't have hardware addition. You had to load in a lookup table that contained the answers to "2+2", "2+3", etc...
...but I do remember it's fairly different from standard TCP/IP.
You're trying to compare two things that aren't exactly comparable:) TCP/IP is a different layer from Token Ring in the ISO view of things... TCP is layer 4, IP is layer 3. Token Ring is layer 1 and 2, like Ethernet. In other words, you should be comparing TR to Ethernet, not to TCP/IP.
You can run TCP/IP over a Token Ring network, just get a TR network interface card. Just like you can run TCP/IP over a serial line, FDDI, SONET, etc...
Slashdot Mirror
BBEdit is a Mac program... there are only 3 Macs in the state of Idaho, so the per-computer rate would actually be quite good.
See, this is why I have excellent karma and get modded up constantly, while you poor karma and have to resort to posting at 0.
What's IPC? FWIW, I'm definitely no expert, but I did take a course in surface mount soldering at the local community college (just for geek knowledge reasons :), and we were taught to do it the way you describe.
Anyways, the course has been useful... I fixed a cellphone that had a tiny capacitor come loose (and I mean tiny--0.5mm x 0.5mm x 1.0mm). Also replaced a broken 0.5mm pitch FPC connector (admittedly, I did lift a pad while removing the old one... it was a pad that wasn't connected to anything though; just a small bit of metal).
Every computer needs a lighter!
Ah, I got the impression from the article that there was only one preserved pup... but last year's article has more details and does say that they have DNA from three individuals.
You do realize that all clones will have the same gender... right?
Yes! Fields Medal! Now!! Before I get too old for it...
Bah, s/31415927299/3141592799/g...
P.S. Another thing worthy of a Nature article... an integer is evenly divisible by 3 if the sum of its digits is evenly divisible by 3. 3+1+4+1+5+9+2+7+9+9=50. 5+0=5. 5 is not evenly divisible by 3. Therefore neither is 31415927299.
P.P.S. 1047197600 has two zeros at the end. If you multiply it by any integer, the product will have at least two zeros at the end. Therefore a trivial inspection would show that 3*1047197600 != 3141592799.
5=6*1-1, 7=6*1+1, 11=6*2-1, 13=6*2+1, 17=6*3-1, 19=6*3+1, ..., 3141592799=6*523598800-1, 3141592801=6*523598800+1, ...
Pretty cool, huh? So where's my Field's Medal? Or at least I should get published in Nature for this!
Hmm, interesting... my guess is that's just some overzealous copy and paste from the previous security update.
Now, as for which OpenSSL bug this is for... my /usr/lib/libssl.* and /usr/lib/libcrypto.* are still dated 03/03. Here's a list of the files included in the update:
So it looks like OpenSSL itself wasn't updated--only mod_ssl for Apache. It's now at version 2.8.13, with fixes for the RSA timing attack. Seems like they should've instead upgraded OpenSSL itself to the version that always turns on RSA blinding.
Dude, don't let your critical updates just sit there in your taskbar... install them!
BTW, you might want to take a look at what Google has to say about romanization wo o. In particular, the first hit says, "The Romanization is "o", but some people use "wo" instead."
It looks like proper Japanese to me... There are many ways to romanize Japanese--the particle "wo" is often romanized as "o". And while you've shown me that you're quite impolite, that's you, not me.
Yes, while I admit I had no idea who he was from the picture, I read the caption. Which is how I knew he was a Danish guy.
wo3 ye3 dong3 zhong1wen2.
(why did Slashdot disable Unicode HTML entities? Tried to post in UTF-8, but got the stupid
Lameness filter encountered. Post aborted!
Reason: Please use fewer 'junk' characters.)
What do you call a person who speaks three languages?
--Trilingual
And a person who speaks two languages?
--Bilingual
And a person who speaks only one language?
--American.
Learn another language, and I'm sure you'll find plenty of sites without a US slant to them.
At least you can laugh at the picture of some Danish guy :)
Seems to me that Linus (or another kernel hacker) should fix the ext2 race condition reported in that thread, rather than blithely dismiss the problem with, "dump was a stupid program in the first place."
void factor_prime(int num)
{
if (!is_prime(num))
err(1, "Number is not prime");
printf("Factors of %d: 1 %d\n", num, num);
}
Of course FP can be implemented on a 6502... AppleSoft BASIC, written by MicroSoft and included in the ROM of all but the earliest Apple ][s (and available on floppy or cassette for the ones that didn't have it in ROM), had floating point routines, including trig functions, log, and square root.
My background is math, not CS, but I'm led to believe that writing a compiler (or at least the core of one) is a standard thing to do for undergrad CS students... some enterprising hacker should write a bare-bones C compiler and release it under the BSD license. It seems to me that if it were well-designed, plenty of hackers would be glad to help out with the optimizer, writing backends for other CPUs, etc... and perhaps after a few years, the compiler would be solid enough for the *BSDs to switch to as their default compiler.
Cool, I've been wanting to make a BSD/Linux distro too (for the same reasons as you), but haven't had the time... NetBSD has done a lot of work recently to get their system cross-buildable on other OSes, such as Linux. Perhaps that'll help some...
Now, the IBM 1620 didn't have hardware addition. You had to load in a lookup table that contained the answers to "2+2", "2+3", etc...
You're trying to compare two things that aren't exactly comparable :) TCP/IP is a different layer from Token Ring in the ISO view of things... TCP is layer 4, IP is layer 3. Token Ring is layer 1 and 2, like Ethernet. In other words, you should be comparing TR to Ethernet, not to TCP/IP.
You can run TCP/IP over a Token Ring network, just get a TR network interface card. Just like you can run TCP/IP over a serial line, FDDI, SONET, etc...
Nobody's talking about putting it into the OpenBSD tree. Besides, who cares what Theo thinks?