Slightly OT: The current issue of Rolling Stone magazine (with Bob Dylan on the cover) has a feature about racism against Muslims in America, and has a photograph of wooden "twin towers" that people built at Harvard (?) to scrawl opinions on regarding the terrorist attacks. You can clearly see "Free Skylarov" written on the left tower.
No, the termcap and TERM variable describe a terminal; they don't control it. Changing the TERM variable will not have any effect on what xterm sends when you hit (for example) F1, nor will it make xterm understand whatever fancy line-drawing characters the SCO box sends to it.
Yeah, you can fire off $2 sheets of Polaroid instead!:-)
Seriously, I would think that the benefit is your time and the opportunity. If you go home and develop your sheet film, and something was wrong, at best you have to go back and shoot again. At worst, the opportunity is gone forever.
All of those party-goers will move on to something new, but indeed my first reaction on reading this was concern for the LF photographers.
I parsed that as "that's what the 'Compost' key is for anyway", and immediately thought, "Compost key? Don't you mean that silly Windows key?". *sigh*. Must go home and have some coffee or something.
Actually, when I used a Windows keyboard, I did map one of the silly Windows keys to "Compose." The circle is complete.
I never understood why people hate the extra keys. They gave you things to bind "Compose" and so forth to.
Another reason to use a GUI editor! You can just find the character on the web and paste it in.
And why would this require a GUI editor? It works just fine with vi(1) in an xterm, and probably works just fine at the FreeBSD console with moused as well (or whatever the Linux equivalent is).
On the other hand, that's what the "Compose" key is for anyway.
Oh, and FWIW, you should never enter you ATM PIN at a POS terminal. If your card has a Visa/MC logo, use it as a credit card instead.
How so? Have there been cases that the POS recorded the PINs? I've refused to use an ATM card with a VISA/MC logo as they are not protected by a PIN or anything else, as far as I can tell. My bank assures me that I can dispute fraudulent purchases, but by the time I do that, my checks will have bounced and my creditors will be pissed, since the bad guys would have stolen real money from my checking account, instead of against my credit line.
plus, is it really faster to
swipe, enter a PIN and wait for authorization, than it is to get $2.15 change from a 5?
I think it's pretty close, given that you can usually do the swiping and the PIN while the clerk is busy scanning your purchases. Even if I only buy 4 or 5 things at the store, I can usually be done with my part before the clerk finishes scanning them.
but at least one ought to be able to ensure that it is exploit-free! Memory copies and buffer length checks are not the hardest thing in the world to find.
And the article specifically says that it's a race, not a buffer overrun. But I guess reading can be hard, even if you're so l33t that finding all the exploitable bugs in an operating system is as easy as cooking ramen noodles.
Here's a dime... go buy some realistic expectations.
Yeah, if you want to insist that everyone in the world speak American. Some people are from places like England, where they do not talk it good like we do.
Yes, I cited both sky brightness and seeing in my original post as the reasons you do HDF from space. My point was just that long integrations are just as possible from the ground.
Both HST and ground-based "long exposures" are the result of adding shorter numerous shorter exposures. This is necessary because you don't want to fill up your pixels with sky counts, and also because cosmic rays will cause hot spots that you want to eliminate by not including CR-zapped pixels when you add up the short exposures. See the observing log for the Hubble Deep Field; the Texp field gives the individual exposure time in seconds. All of the exposures in a given filter (F300W, F450W, F606W, F814W) were then added to give the "long exposure" image. Calibration data (bias and dark frames) were interespersed with the science exposures.
48 hours of exposure of one piece of sky; try doing that with a ground based telescope
Uh, there's no reason you can't do that from the ground. But the result will be less useful because you're fighting much brighter skies and the image will be blurred by the atmosphere ("seeing").
time_t is not meant for storing arbitrary dates. It's meant for storing UNIX-relevant things like the current time and the boot time and file timestamps. Use struct tm or something if you need other dates and times.
time_t is signed because time(3) is documented to return -1 if there is an error.
Not just Central California. We saw vivid crimson curtains at Palomar Observatory tonight, at 33 degrees north latitude. One of the night assistants reports last seeing them here around 1981, and to a much lesser degree.
Slashdot Mirror
Slightly OT: The current issue of Rolling Stone magazine (with Bob Dylan on the cover) has a feature about racism against Muslims in America, and has a photograph of wooden "twin towers" that people built at Harvard (?) to scrawl opinions on regarding the terrorist attacks. You can clearly see "Free Skylarov" written on the left tower.
No, the termcap and TERM variable describe a terminal; they don't control it. Changing the TERM variable will not have any effect on what xterm sends when you hit (for example) F1, nor will it make xterm understand whatever fancy line-drawing characters the SCO box sends to it.
Yeah, you can fire off $2 sheets of Polaroid instead! :-)
Seriously, I would think that the benefit is your time and the opportunity. If you go home and develop your sheet film, and something was wrong, at best you have to go back and shoot again. At worst, the opportunity is gone forever.
All of those party-goers will move on to something new, but indeed my first reaction on reading this was concern for the LF photographers.
Actually, when I used a Windows keyboard, I did map one of the silly Windows keys to "Compose." The circle is complete.
I never understood why people hate the extra keys. They gave you things to bind "Compose" and so forth to.
And why would this require a GUI editor? It works just fine with vi(1) in an xterm, and probably works just fine at the FreeBSD console with moused as well (or whatever the Linux equivalent is).
On the other hand, that's what the "Compose" key is for anyway.
I thought stripping was a form of recovery, actually. Or at least watching stripping is. Now striping, on the other hand...
Not even Fortran programmers?
I don't know... the mainstream press sure spent a lot of time covering George W. Bush's job change.
You're the "usage police" or the "semantic police," not the "grammar police." So am I.
Because insurance fraud is a federal crime.
And the article specifically says that it's a race, not a buffer overrun. But I guess reading can be hard, even if you're so l33t that finding all the exploitable bugs in an operating system is as easy as cooking ramen noodles.
Here's a dime... go buy some realistic expectations.
Yeah, if you want to insist that everyone in the world speak American. Some people are from places like England, where they do not talk it good like we do.
Who the hell moderated this "Informative"?
Yes, I cited both sky brightness and seeing in my original post as the reasons you do HDF from space. My point was just that long integrations are just as possible from the ground.
Both HST and ground-based "long exposures" are the result of adding shorter numerous shorter exposures. This is necessary because you don't want to fill up your pixels with sky counts, and also because cosmic rays will cause hot spots that you want to eliminate by not including CR-zapped pixels when you add up the short exposures. See the observing log for the Hubble Deep Field; the Texp field gives the individual exposure time in seconds. All of the exposures in a given filter (F300W, F450W, F606W, F814W) were then added to give the "long exposure" image. Calibration data (bias and dark frames) were interespersed with the science exposures.
On a similar note, see the scheduling constraints for the various filters.
We routinely take 1800 second exposures of a field over a span of months or years until we have 8 hours or more of total exposure.
Saying "mate in 5" means that you will lose in 5 moves or fewer, no matter what you do. It's a little late to think of it as helpful advice.
time_t is not meant for storing arbitrary dates. It's meant for storing UNIX-relevant things like the current time and the boot time and file timestamps. Use struct tm or something if you need other dates and times.
time_t is signed because time(3) is documented to return -1 if there is an error.
Why would you put a fuse or circuit breaker in a house? Why not just draw less current?
There are astronomical institutions which are not degree-granting, but are in the .edu domain.
www.noao.edu, www.stsci.edu, www.nrao.edu...Her name was Tink, IIRC.
Heh, the troll who mocks the picture of me having fun at USENIX used MSIE to get it! Pot, kettle, schmoo.
Not just Central California. We saw vivid crimson curtains at Palomar Observatory tonight, at 33 degrees north latitude. One of the night assistants reports last seeing them here around 1981, and to a much lesser degree.