Well, first I'd point you at the Amateur Radio Relay Leagues's website - www.arrl.org.
That said:
You need to lock the problem in a bit more. If you are just looking for FM radio LO's, you'd be looking in the range of about 70-125 MHz (assuming 10.7 MHz IF, high and low side injection).
For an omnidirectional antenna, you'd be looking at a discone. For a directional antenna, that wide, you'd probably want to use a log-periodic as a yagi would be too narrow band.
Then, if you are looking for signals, a sensitive spectrum analyzer or communications service monitor - I'd suggest looking for a used IFR-1200S, IFR-1200Super, or IFR-COM-120B, but I'm biased as hell since I helped design the 120B. Check eBay (gag). Don't buy a 1200 dash-nothing or 1200-a - it does not have the spectrum analyzer in it. If you can find a 1200SRA that would be even better, but I don't think No Such Agency has given those up.
For DF work - IF you get a strong enough signal, then you can use something like a Ramsey electronics kit DF rig. You can also look up Fox hunting for more information.
Simplest way to scratch that itch - Get a ham ticket, find your nearest club, and sit at the feet of the Elmers.
The way a modern superheterodyne radio works is like this:
You want to listen to a radio frequency at F1. The radio creates a local oscillator (or LO) frequency of F2, such that abs(F2-F1) = F3, where F3 is a fixed, intermediate frequency (or IF). A common IF for FM radios is 10.7 MHz, and a common IF for AM radios is 455 kHz. By pulling the signal to a fixed frequency the rest of the radio's design can be better optimized and simpler.
Now, F2 can be either F1+F3 or F1-F3, it make little difference. So one way to confuse the system would be to retune the radio so that it uses "the other IF" - i.e. if the radio is using F2=F3+F1, retune the guts so that it uses F2=F1-F3.
Alternatively, replace the IF strip to change F2, and then retune the radio appropriately - if the sign's systems assume an IF of 10.7 MHz, and you are using an IF of 9.7 MHz, that will confuse the sign. The difficulty there is getting components designed for a non-standard frequency. If the radio is using the old "tuned slug" design this isn't so bad, but if the radio is using a crystal filter you are looking at custom crystals.
However, there is no need for the LO to be coupled to the world - the first stages of the radio can amplify the RF and decouple the first LO mixer from the world. It just takes a bit more work on the sheilding of the radio - you use a milled block of aluminum rather than foil sheilds. I know, since that is what I do for a living - design radios (well, radio test gear, which is a special case of the class Radio)
However, building a jamming oscillator at the needed frequencies to scramble this sign, while completely illegal, is also trivial - buy a cheap FM transmitter kit and retune it slightly. Of course, by causing interference you are in violation of FCC part 15 rules, and will get nailed if you get caught, so don't, 'mkay?
If it bothers you, just don't listen to the radio.
Back in the days of telegraph, Western Union would get a lot of job applicants.
In the waiting room for the job interview, there would be a clicking sound - the sound of a sender repeating over and over "If you can understand this, go through the unmarked door" in Morse.
Folks who just sat there didn't get jobs as telegraph operators.
The reason this is being done is the same damnfool reason too many decisions are made - the idea that this touchscreen tech is "cool" and "sexy" (I am put in mind of IBM ad - "Cool costs me money").
Then there is the drive of the US media - witness the 2000 elections - "With 0% of the vote in, we predict a landslide for Gore".
There is no meaningful reason we MUST have the election results within hours of the vote - that is why the vote is in November and the transfer of office in January.
Personally, I wish there were a legal BAN on ALL poll predictions for the entire day of the election. They can talk about the election being held, they can talk about how many people are turning out, they can talk about Michael Jackson's Daycare date for all I care, but NO PROJECTIONS OF THE OUTCOME.
The reason they don't want to use ethanol is precisely BECAUSE it is the same as alcohol.
If they use ethanol, they have to treat the refills just as they would have to treat vodka - they cannot sell it to anybody under-age, they have to have a liquor license to sell it, they got to prison if they violate the rules.
That is why you don't see pure ethanol at the gas pump, that is why you won't see ethanol fuel for fuel cells.
Now, the COULD try to design the fuel cell to run on ethanol, as well, and leave the fact as a "back door" sort of issue, but any fuel they sell will have to be denatured in some form. The easiest way is to use methanol.
I don't understand why the story poster differentiates between a "three button mouse" and a scroll wheel mouse in which the wheel is the third button.
True, some scroll mice have the problem that the wheel will generate scroll events when the scroll wheel is clicked. If this is a problem, then simply configure X to NOT recognize such events. Voi la - a three button mouse.
It was the INTERVIEWEE who consistently mispronounced the company name.
As in, "There is no way in hell I really worked there, as I would know better how to pronounce the company name if I did - I am bullshitting you, and if you hire me you are hiring a bullshitter who never worked at Bombardier".
Just because a system does not use WEP does not mean it is insecure.
I've been playing with a WAP - my intention is to firewall it to the point that the only things you can do are DNS, DHCP, VPN, and accessing a password-protected HTTP proxy with bandwidth throttling.
The only thing WEP would do in such a case is prevent somebody from sniffing the proxy's password from the air, and if I cared I would just move the proxy over to HTTPS.
Just as WEP != secure, !WEP != !secure.
So all the "OMFG! 73% of all the APs we sniffed weren't using WEP, therefore 73% of all APs aren't secured" is somewhat flawed reasoning.
Granted, it is likely pretty close to the truth. But it is not guaranteed to be the truth.
OK, then - Mozilla stores POST responses in disk cache. Why, when no sane person should ever need to store a POST response for more than a couple of pageview later is beyond me, but take it as read.
That still not not change the other statements that I made - that a seperate disk caching program, available to all programs, with an API sufficient to allow for the issues you raised, would benefit the system by allowing a consistent, unified disk cache to all programs.
First of all, you may have noticed that in all of my messages I was quite clear about the difference between "disk cache" and "memory cache" - the example of the post you use is a memory cache issue, and you might have noticed that I did not say that Mozilla should not have a memory cache, only a disk cache.
Your second point also falls under this catagory.
Your third statement is not a point.
The point I made in my first statement was that the DISK cache (read my post again. Then read this again. Once again, DISK cache) should not be a part of Mozilla but a seperate entity available to the whole system.
Bah - we had one of the "blank" cards supplied written up with the following rule: Cobalt jacketed bomb Triple yeild (applies to each warhead on MX) May be applied to 100M on final strike for automatic destruction of world.
Made a great deterrent force: "OK, folks - See this: 100M , cobalt. Do not target me."
Of course, you still had to "spin the spinner, call your shot, Nuke War ties your genes in a knot". Really frustrating to get a Dud or Out of Fuel.
Michael Jackson IS Saddam Hussein, or rather Saddam is Michael.
You see, Saddam needed a place to hide. A new identity, as unlike his current one as possible.
So, he had Michael killed (by dropping him in plastic solvent), located the same incompetent plastic surgeon Michael has been using, and had himself made to look like Michael.
Actually, my point was that by creating a seperate cache program, they could bring the benefits of this to ALL platforms, *nix or not.
And by the way - MacOS is Unix.
The biggest single mistake Netscape made back in the day was to NOT realize that by providing a set of small sharp tools to the Windows programmers, they left the market open to Microsoft, who did exactly that. This is something they are trying to correct with Mozilla, by providing things like Gecko and the Netscape portable runtime libraries, but if they were to provide a unified disk caching library they could begin to provide a real benefit to Windows users.
I follow the Tivo discusson forums, and there is one good reason Tivo may not want these images distributed.
The images for different Tivos are slightly different - a Phillips unit is not quite the same as a Sony, a DTivo is different than a stand alone Tivo, and of course Series II Tivos are MIPS rather than PPC based.
The common use case for these images goes something like this:
Joe L. Usr tries to upgrade his system. He, of course, does not back up his system. He adds a drive and botches the process.
Joe figgrs he will just download a new image and "fix" his system. So he pulls down the first image he can find, and BAM! his Tivo is now not merely broken, but toast.
Now, the upgrade sites actually require you to tell them what hardware you have, and thus (one hopes) can insure you get the correct image.
So Tivo MAY want to prevent folks from moron-izing their systems, but not have a problem with folks that don't have a history of doing so.
I don't understand why Mozilla has ANY form of disk caching built in in the first place - that is not the way of Unix.
Let a seperate program do the disk caching (e.g. Squid). Let Moz and any other program use that program. Thus, everybody benefits from the cache.
Just like in the latest released of libresolve (the DNS library for *nix systems) now has the "lightweight resolver" which is a small caching resolver library, so that applications that stupidly keep asking to resolve the same address don't load down the nameservers.
The way of Unix - "small, sharp tools" or "one job, one program" is not just for geeks - it makes for a more robust system as the programs can be optimized to do what they do VERY WELL.
In order to check out the SVG support, I build my own image of Moz from the mainline CVS branch a couple of weeks ago.
The SVG isn't included for good reason - in its current state it is next to useless. Moz natively supports SVG right now as much as Microsoft natively supports the POSIX API - just enough to claim it, not enough to be useful.
However, IF you have the machine and the connection to do so, I suggest building your own - they have greatly improved the build process. Compiling moz with "-Os -march=athlon-xp -mfpmath=sse,376" has greatly improved the speed of Moz on my machine - but YMMV.
Got'em both, and a second copy of NE given to me by somebody.
I love seeing the look in those Magic: The Gathering weenies eyes when I show them how big my Nuke deck is! "I see your Force of Nature, and raise you an MX with a 100!"
Slashdot Mirror
All I can say is, send in your CV to our HR department.
. cf m
http://www.aeroflex.com/aboutus/employment/jobs
Personally, ***I'D*** like to see some more Test guys, to help write autotests.
But I don't hire people.
You wouldn't want to transmit on the IF, but on the 1st LO freq - so you'd want to transmit somewhere between 70MHz and 125 MHz.
If you have an aviation band HT you could use that, or if you have a military rig, but otherwise your HF rig won't do any good.
Well, first I'd point you at the Amateur Radio Relay Leagues's website - www.arrl.org.
That said:
You need to lock the problem in a bit more. If you are just looking for FM radio LO's, you'd be looking in the range of about 70-125 MHz (assuming 10.7 MHz IF, high and low side injection).
For an omnidirectional antenna, you'd be looking at a discone. For a directional antenna, that wide, you'd probably want to use a log-periodic as a yagi would be too narrow band.
Then, if you are looking for signals, a sensitive spectrum analyzer or communications service monitor - I'd suggest looking for a used IFR-1200S, IFR-1200Super, or IFR-COM-120B, but I'm biased as hell since I helped design the 120B. Check eBay (gag). Don't buy a 1200 dash-nothing or 1200-a - it does not have the spectrum analyzer in it. If you can find a 1200SRA that would be even better, but I don't think No Such Agency has given those up.
For DF work - IF you get a strong enough signal, then you can use something like a Ramsey electronics kit DF rig. You can also look up Fox hunting for more information.
Simplest way to scratch that itch - Get a ham ticket, find your nearest club, and sit at the feet of the Elmers.
You are almost right, but not quite.
The way a modern superheterodyne radio works is like this:
You want to listen to a radio frequency at F1.
The radio creates a local oscillator (or LO) frequency of F2, such that abs(F2-F1) = F3, where F3 is a fixed, intermediate frequency (or IF). A common IF for FM radios is 10.7 MHz, and a common IF for AM radios is 455 kHz. By pulling the signal to a fixed frequency the rest of the radio's design can be better optimized and simpler.
Now, F2 can be either F1+F3 or F1-F3, it make little difference. So one way to confuse the system would be to retune the radio so that it uses "the other IF" - i.e. if the radio is using F2=F3+F1, retune the guts so that it uses F2=F1-F3.
Alternatively, replace the IF strip to change F2, and then retune the radio appropriately - if the sign's systems assume an IF of 10.7 MHz, and you are using an IF of 9.7 MHz, that will confuse the sign. The difficulty there is getting components designed for a non-standard frequency. If the radio is using the old "tuned slug" design this isn't so bad, but if the radio is using a crystal filter you are looking at custom crystals.
However, there is no need for the LO to be coupled to the world - the first stages of the radio can amplify the RF and decouple the first LO mixer from the world. It just takes a bit more work on the sheilding of the radio - you use a milled block of aluminum rather than foil sheilds. I know, since that is what I do for a living - design radios (well, radio test gear, which is a special case of the class Radio)
However, building a jamming oscillator at the needed frequencies to scramble this sign, while completely illegal, is also trivial - buy a cheap FM transmitter kit and retune it slightly. Of course, by causing interference you are in violation of FCC part 15 rules, and will get nailed if you get caught, so don't, 'mkay?
If it bothers you, just don't listen to the radio.
Did anybody else think that Saddam, before he was shaven and cleaned up, looked a lot like Ted Kaczynski, the Unabomber?
Back in the days of telegraph, Western Union would get a lot of job applicants.
In the waiting room for the job interview, there would be a clicking sound - the sound of a sender repeating over and over "If you can understand this, go through the unmarked door" in Morse.
Folks who just sat there didn't get jobs as telegraph operators.
The reason this is being done is the same damnfool reason too many decisions are made - the idea that this touchscreen tech is "cool" and "sexy" (I am put in mind of IBM ad - "Cool costs me money").
Then there is the drive of the US media - witness the 2000 elections - "With 0% of the vote in, we predict a landslide for Gore".
There is no meaningful reason we MUST have the election results within hours of the vote - that is why the vote is in November and the transfer of office in January.
Personally, I wish there were a legal BAN on ALL poll predictions for the entire day of the election. They can talk about the election being held, they can talk about how many people are turning out, they can talk about Michael Jackson's Daycare date for all I care, but NO PROJECTIONS OF THE OUTCOME.
To what should they change it?
Booze Battery?
Vodka Wattsa?
Gin-erator (or En-Gin)?
The reason they don't want to use ethanol is precisely BECAUSE it is the same as alcohol.
If they use ethanol, they have to treat the refills just as they would have to treat vodka - they cannot sell it to anybody under-age, they have to have a liquor license to sell it, they got to prison if they violate the rules.
That is why you don't see pure ethanol at the gas pump, that is why you won't see ethanol fuel for fuel cells.
Now, the COULD try to design the fuel cell to run on ethanol, as well, and leave the fact as a "back door" sort of issue, but any fuel they sell will have to be denatured in some form. The easiest way is to use methanol.
I don't understand why the story poster differentiates between a "three button mouse" and a scroll wheel mouse in which the wheel is the third button.
True, some scroll mice have the problem that the wheel will generate scroll events when the scroll wheel is clicked. If this is a problem, then simply configure X to NOT recognize such events. Voi la - a three button mouse.
No, read it again.
It was the INTERVIEWEE who consistently mispronounced the company name.
As in, "There is no way in hell I really worked there, as I would know better how to pronounce the company name if I did - I am bullshitting you, and if you hire me you are hiring a bullshitter who never worked at Bombardier".
Just because a system does not use WEP does not mean it is insecure.
I've been playing with a WAP - my intention is to firewall it to the point that the only things you can do are DNS, DHCP, VPN, and accessing a password-protected HTTP proxy with bandwidth throttling.
The only thing WEP would do in such a case is prevent somebody from sniffing the proxy's password from the air, and if I cared I would just move the proxy over to HTTPS.
Just as WEP != secure, !WEP != !secure.
So all the "OMFG! 73% of all the APs we sniffed weren't using WEP, therefore 73% of all APs aren't secured" is somewhat flawed reasoning.
Granted, it is likely pretty close to the truth. But it is not guaranteed to be the truth.
cd slashtroll ./make
cvs rdiff -r chimp -r human genome | patch -p1
Yet again the grand tradition of
So
Happy
It's
Thursday
is upheld by Microsoft security bugs.
And of course, now that Microsoft is releasing patches on Tuesday, we also have
So
Happy
It's
Tuesday
as well.
Kudos to Microsoft!
OK, then - Mozilla stores POST responses in disk cache. Why, when no sane person should ever need to store a POST response for more than a couple of pageview later is beyond me, but take it as read.
That still not not change the other statements that I made - that a seperate disk caching program, available to all programs, with an API sufficient to allow for the issues you raised, would benefit the system by allowing a consistent, unified disk cache to all programs.
First of all, you may have noticed that in all of my messages I was quite clear about the difference between "disk cache" and "memory cache" - the example of the post you use is a memory cache issue, and you might have noticed that I did not say that Mozilla should not have a memory cache, only a disk cache.
Your second point also falls under this catagory.
Your third statement is not a point.
The point I made in my first statement was that the DISK cache (read my post again. Then read this again. Once again, DISK cache) should not be a part of Mozilla but a seperate entity available to the whole system.
Bah - we had one of the "blank" cards supplied written up with the following rule:
Cobalt jacketed bomb
Triple yeild (applies to each warhead on MX)
May be applied to 100M on final strike for automatic destruction of world.
Made a great deterrent force:
"OK, folks - See this: 100M , cobalt. Do not target me."
Of course, you still had to "spin the spinner, call your shot, Nuke War ties your genes in a knot". Really frustrating to get a Dud or Out of Fuel.
But it was GREAT on an MX-100!
Wrong, on several levels.
First, you don't cache POST requests.
Second, an external cache can most certainly return whether an object is in cache or not using standard HTTP If-Modified-Since semantics.
Third, an external cache program need not be limited to HTTP.
Michael Jackson IS Saddam Hussein, or rather Saddam is Michael.
You see, Saddam needed a place to hide. A new identity, as unlike his current one as possible.
So, he had Michael killed (by dropping him in plastic solvent), located the same incompetent plastic surgeon Michael has been using, and had himself made to look like Michael.
Actually, my point was that by creating a seperate cache program, they could bring the benefits of this to ALL platforms, *nix or not.
And by the way - MacOS is Unix.
The biggest single mistake Netscape made back in the day was to NOT realize that by providing a set of small sharp tools to the Windows programmers, they left the market open to Microsoft, who did exactly that. This is something they are trying to correct with Mozilla, by providing things like Gecko and the Netscape portable runtime libraries, but if they were to provide a unified disk caching library they could begin to provide a real benefit to Windows users.
I follow the Tivo discusson forums, and there is one good reason Tivo may not want these images distributed.
The images for different Tivos are slightly different - a Phillips unit is not quite the same as a Sony, a DTivo is different than a stand alone Tivo, and of course Series II Tivos are MIPS rather than PPC based.
The common use case for these images goes something like this:
Joe L. Usr tries to upgrade his system. He, of course, does not back up his system. He adds a drive and botches the process.
Joe figgrs he will just download a new image and "fix" his system. So he pulls down the first image he can find, and BAM! his Tivo is now not merely broken, but toast.
Now, the upgrade sites actually require you to tell them what hardware you have, and thus (one hopes) can insure you get the correct image.
So Tivo MAY want to prevent folks from moron-izing their systems, but not have a problem with folks that don't have a history of doing so.
I don't understand why Mozilla has ANY form of disk caching built in in the first place - that is not the way of Unix.
Let a seperate program do the disk caching (e.g. Squid). Let Moz and any other program use that program. Thus, everybody benefits from the cache.
Just like in the latest released of libresolve (the DNS library for *nix systems) now has the "lightweight resolver" which is a small caching resolver library, so that applications that stupidly keep asking to resolve the same address don't load down the nameservers.
The way of Unix - "small, sharp tools" or "one job, one program" is not just for geeks - it makes for a more robust system as the programs can be optimized to do what they do VERY WELL.
In order to check out the SVG support, I build my own image of Moz from the mainline CVS branch a couple of weeks ago.
The SVG isn't included for good reason - in its current state it is next to useless. Moz natively supports SVG right now as much as Microsoft natively supports the POSIX API - just enough to claim it, not enough to be useful.
However, IF you have the machine and the connection to do so, I suggest building your own - they have greatly improved the build process. Compiling moz with "-Os -march=athlon-xp -mfpmath=sse,376" has greatly improved the speed of Moz on my machine - but YMMV.
Per my post in the other /. thread on this sort of subject:
Nuke War.
Gotta be Nuke War.
Got change for 25 million people?
Got'em both, and a second copy of NE given to me by somebody.
I love seeing the look in those Magic: The Gathering weenies eyes when I show them how big my Nuke deck is! "I see your Force of Nature, and raise you an MX with a 100!"