Postscript to my previous post: For those who don't know, "the start of the UNIX epoch" is the reference time that time_t's count from. The time_t value returned by time(2) is the number of seconds since the start of the UNIX epoch.
That time is 00:00:00 UTC, January 1, 1970. In most time zones, that time is actually some time during the day December 31, 1969.
It's not so arbitrary when you consider that many applications (esp. commandline shells) have adopted Emacs-like bindings for editing for years. I remember being introduced to these keybindings back in the 1993 time-frame, and they were already well established then.
Emacs is a pretty good standard to follow since it's been a staple of UNIX environments for, oh, 20+ years, hasn't it?
That won't fix the backspace/delete issue. You need to "stty erase ^H" or "stty erase ^?" depending on which one your terminal sends. On the Solaris side, the ^H and ^? might actually need to be the control character. On the Linux side, you can type caret-H and caret-? as two characters.
I personally have everything here set up to send and expect ^H.
In xterm, you can pick BS or DEL (^H or ^?) by Control-Left-Click and toggling "Backarrow Key (BS/DEL)". In gnome-terminal, there's an option under "Settings" for toggling that, although it appears they refer to the Backspace key as "Delete."
I've personally never understood why Linux would send ASCII DEL (Delete) for the backspace key, and the DEC sequence "Remove" for the Delete key. I guess the DEC VT-100 set that standard. I've got my boxes configured to send ASCII BS (Backspace) in response to the Backspace key, and ASCII DEL (Delete) in response to the Delete key.
And yes, on my keyboard, those keys are labeled "Backspace" and "Delete."
What was really annoying back in school were the old AT&T SysV machines for which ^? was the interrupt character (instead of ^C). Get on a misconfigured terminal, and you better be a good typist...
Yes, you always want to remove the gauze from your hard-drive before destroying it. Otherwise, it might catch on fire during the melting step (#4).
I'm sure Karl Freidrich appreciates the hint.
Of course, if you're not accustomed to the shell game that Cygwin plays with all your files, it could become very confusing.
I stopped building stuff with Cygwin a long time ago for that reason. I still have it on my HD for a handful of tools, but really I should consider building those all with MinGW so that path interpretation works a little more sanely.
It's a known, regular transmission, and is thus easily filtered and/or accounted for in the design of the other instrumentation. (This is in contrast to the sporadic, uncoordinated transmissions of consumer devices that are not under the control of the plane manufacturer.)
If designed properly, it could output a short burst of commands over a short period of time (like, say, over a 2 minute period during the safety briefing while the plane is taxiing) that says "Shut off for at least ## minutes", where ## is the expected duration of the flight. Further broadcast would not be necessary until ## expires.
Phones would power up after the timeout to a half-awake state--receive only, no broadcast or tower searching--looking to see of a damping refresh is happening that would extend their sleep. Thus, if you get stuck on the runway or in a holding pattern, you wouldn't get this sudden burst of cell-phone activity near the end of the flight.
Alternately, phones that have been put to sleep by the beacon would only power up to the "half-awake" state afterwards only, for some period longer than the specified ##, and a separate beacon in the jetway and/or the terminal would be able to cancel this compliant state.
I've wanted one of these for a long time. Put them in classrooms, lecture halls, airplanes and movie theaters, PLEASE!!! I've long said we should have something like this.
It would be even better if this feature was built into GSM, PCS or whatever standard, so that you could further tell the phone to turn off. This would be useful on airplanes and in other environments where cellphone use is restricted or prohibited.
I'm not sure where you'd find it, but you might make some headway searching for "anticipatory scheduler" on kerneltrap.org. This scheduler was discussed multiple times on that site.
In the last month and a half, I've literally received about 2 gigabytes of virus/worm mail in my UNIX-based mailbox. (Actually, it's an AIX box at my ISP.)
Anyway, I noticed that most of these come from a rather small set of "From:" addresses, and my (now cancelled) email address, im14u2c@primenet.com, was one of them. Did any of you receive large quantities of email wastage with that forged "From:" address?
Here's a short list of forged From: addresses I saw repeatedly on these virus/worm spam, in decreasing order of occurrence:
im14u2c@primenet.com
ollie@sis.com.tw
lcs@sis.com.tw
LI>jgarzik@mandrakesoft.com
cmhuang@sis.com.tw
lcchang@sis.com.tw
lola@sexnet.com
abuse@gov.us
support@symantec.com
I noticed sis.com.tw got hit pretty hard, as did Jeff Garzik! I think they must've scraped these out of the SiS900 driver in the Linux kernel.
I'm regretting that suggestion I made to Ollie on how to speed up his CRC routine.
Evidence of binary similarity could be sufficient to persuade a judge to compel disclosure of source code as part of a discovery process.
So, no, you won't win a trial with the binary evidence alone, but you might win a motion to compel disclosure. The whole "probable cause" notion--it's enough to get a search warrant but not enough to convict.
Slashdot Mirror
Postscript to my previous post: For those who don't know, "the start of the UNIX epoch" is the reference time that time_t's count from. The time_t value returned by time(2) is the number of seconds since the start of the UNIX epoch. That time is 00:00:00 UTC, January 1, 1970. In most time zones, that time is actually some time during the day December 31, 1969.
Which happens to be the start of the UNIX epoch, too. (Well, at least in most timezones.)
You realize that XADS is just 11 miles up the street from the Worlds Largest Ball of Paint?
Coincidence? I think not....
--Joe(PS. In case that Yahoo! Maps link doesn't work after a bit, note that XADS is in Anderson, IN, and WLBP is in Alexandria, IN.)
It's not so arbitrary when you consider that many applications (esp. commandline shells) have adopted Emacs-like bindings for editing for years. I remember being introduced to these keybindings back in the 1993 time-frame, and they were already well established then.
Emacs is a pretty good standard to follow since it's been a staple of UNIX environments for, oh, 20+ years, hasn't it?
--JoeThat won't fix the backspace/delete issue. You need to "stty erase ^H" or "stty erase ^?" depending on which one your terminal sends. On the Solaris side, the ^H and ^? might actually need to be the control character. On the Linux side, you can type caret-H and caret-? as two characters.
I personally have everything here set up to send and expect ^H.
In xterm, you can pick BS or DEL (^H or ^?) by Control-Left-Click and toggling "Backarrow Key (BS/DEL)". In gnome-terminal, there's an option under "Settings" for toggling that, although it appears they refer to the Backspace key as "Delete."
I've personally never understood why Linux would send ASCII DEL (Delete) for the backspace key, and the DEC sequence "Remove" for the Delete key. I guess the DEC VT-100 set that standard. I've got my boxes configured to send ASCII BS (Backspace) in response to the Backspace key, and ASCII DEL (Delete) in response to the Delete key.
And yes, on my keyboard, those keys are labeled "Backspace" and "Delete."
What was really annoying back in school were the old AT&T SysV machines for which ^? was the interrupt character (instead of ^C). Get on a misconfigured terminal, and you better be a good typist...
--JoeYou know, you can just middle-click anywhere in the HTML pane to paste your URL. At least, that works in Mozilla.
The point you missed is that the advertisers are equally shady, and can just go "belly up" and start over with a "new" company.
The two were made for each other. It's truly beautiful.
Sure! "I once was a spammer, but now I'm legit. I run an opt-in Majordomo list."
Hell, I thought that's what DOS 3.3 did every time it couldn't read a sector...
Good... I wasn't the only one to notice. :-)
I think he's been looking for WiFi in several wrong places.
--JoeYes, you always want to remove the gauze from your hard-drive before destroying it. Otherwise, it might catch on fire during the melting step (#4). I'm sure Karl Freidrich appreciates the hint.
--JoeOf course, if you're not accustomed to the shell game that Cygwin plays with all your files, it could become very confusing.
I stopped building stuff with Cygwin a long time ago for that reason. I still have it on my HD for a handful of tools, but really I should consider building those all with MinGW so that path interpretation works a little more sanely.
--JoeWell, kinda like Maslow's Hierarchy of Needs, we have Slashdot's Hierarchy of Stress Relief.
--JoeTwo rebuttals:
Phones would power up after the timeout to a half-awake state--receive only, no broadcast or tower searching--looking to see of a damping refresh is happening that would extend their sleep. Thus, if you get stuck on the runway or in a holding pattern, you wouldn't get this sudden burst of cell-phone activity near the end of the flight.
Alternately, phones that have been put to sleep by the beacon would only power up to the "half-awake" state afterwards only, for some period longer than the specified ##, and a separate beacon in the jetway and/or the terminal would be able to cancel this compliant state.
Make sense?
--JoeI've wanted one of these for a long time. Put them in classrooms, lecture halls, airplanes and movie theaters, PLEASE!!! I've long said we should have something like this.
It would be even better if this feature was built into GSM, PCS or whatever standard, so that you could further tell the phone to turn off. This would be useful on airplanes and in other environments where cellphone use is restricted or prohibited.
--JoeIIRC, it was a soldier that was caught drinking while on duty.
Ok, someome please tell me I'm not the only one who heard Lawrence's voice from Office Space, yelling "Hey Peter! Check out Channel 9! Breast exam!"
--JoeI'm not sure where you'd find it, but you might make some headway searching for "anticipatory scheduler" on kerneltrap.org. This scheduler was discussed multiple times on that site.
--JoeIt is new with respect to 2.4.x. The anticipatory scheduler was introduced 2.5.x-mm and made its way into the kernel by the time 2.6 was released.
In the last month and a half, I've literally received about 2 gigabytes of virus/worm mail in my UNIX-based mailbox. (Actually, it's an AIX box at my ISP.)
Anyway, I noticed that most of these come from a rather small set of "From:" addresses, and my (now cancelled) email address, im14u2c@primenet.com, was one of them. Did any of you receive large quantities of email wastage with that forged "From:" address?
Here's a short list of forged From: addresses I saw repeatedly on these virus/worm spam, in decreasing order of occurrence:
I noticed sis.com.tw got hit pretty hard, as did Jeff Garzik! I think they must've scraped these out of the SiS900 driver in the Linux kernel.
I'm regretting that suggestion I made to Ollie on how to speed up his CRC routine.
--Joe...neither one of which is relevant or useful under SOLARIS.
My girlfriend won't buy the post-Ford Volvos. As for the SAABs, I also get a discount... :-)
Right now, though, I have my heart set on a nice Holden^WPontiac GTO. I may not get another chance to buy a car like that for awhile.
--JoeMy girlfriend drives a Volvo (her second, so far), so no worries there...
My dad works at GM (I think my grandfather also did)--I still drive GM cars.
Evidence of binary similarity could be sufficient to persuade a judge to compel disclosure of source code as part of a discovery process.
So, no, you won't win a trial with the binary evidence alone, but you might win a motion to compel disclosure. The whole "probable cause" notion--it's enough to get a search warrant but not enough to convict.
PS. IANAL.
--JoeNot to be picky, but comments usually don't show up in the binary executable. char* string initializers will though....
--Joe