There are many serial port redirectors out there, typically used with telnet server (ethernet to serial) boxes like the SitePlayer Telnet, some of the Lantronix stuff, and stuff from Equinox and Digi. These are very common for remote out-of-band console port admin of switches and routers.
I never used RIPTerm; on the PC I later used Telix, but I used ANSITerm on my TRS-80 Model 4D with hi-res card. I still occasionally fire up the old Tandy 1400LT 8088 DOS laptop and use Telix for console work, and I still have a TRS-80 Model 4P (with an HxC floppy emulator) and use Mel Patrick's FASTTERM as well as my own ANSITerm (hi-res board required.....). Makes some interesting conversation in a datcenter to roll in with a TRS-80 4P in tow...... But it makes a reasonable terminal for many uses.
I ran my part-time BBS in Atlanta on that Model 4, too, incidentally.
Lots of good memories meeting lots of interesting people. More interesting than Facebook; typically more civilized than Reddit, Slashdot, 4Chan, or pretty much anything else of today.
I ran a BBS in Atlanta in the mid-80's. Was very fun. Until joining Eskimo North (still online!) had not used a multi-user BBS. That was one of the draws of the BBS scene; single-user by nature, most of the time, and replies were far slower in coming..... 8/N1, The Greene Machine, Tandy Trader, Cornucopia, among many others. I still have a print of a 1987 dial-in list from Atlanta, and I was involved in many of them.
BBSing got me into uucp and running my own C-News leaf node attached to Eskimo North. Fun days. Usenet was the next step, really, beyond the dial-up BBS. Especially in terms of loss of civility; alt.flame, alt.barney.must.die.die.die, etc. Discussion of new group creation, some of the interesting things in alt.folklore.computers, and good times in comp.sys.tandy.
I have read it, back in 2009, around Christmastime. While Wheeler's dissertation is impressive, his own list of challenges (Section 8, page 118) is fairly extensive, and many of those challenges apply to the embedded development reality (most notably, the alternative compiler necessary to create the diversity). As an ECU is an embedded, and likely a rather proprietary, platform, it is likely that an alternative compiler would not be available.
As long as you can build it youself, and the checksums match what's in the ECU, then this issue doesn't exist
Hmm, you must be new here. Please see Ken Thompson's 'Reflections on Trusting Trust' ( https://dl.acm.org/citation.cf... ) and come back once you're properly enlightened.
Sounds like segment three of the 15th episode of the mid-80's revival of The Twilight Zone to me. See: https://en.wikipedia.org/wiki/...
The comments about religion are petty spot-on, too; in essence, this makes the universe merely a figment of God's imagination..... our the figment of a computer simulation.....
Mixbus is a full-on professional DAW and sounds absolutely fantastic. I run Mixbus on CentOS 7 and everything works perfectly, for as many tracks as I want to throw at it.
Regardless of number of processes or threads total only X can run at any given timeslice, where X equals the number of CPU's/cores (virtual cores for HT) that you have. Finding the RF signature for a context switch would not be hard, since it is so repetitious.
One of the key concepts to realize with 'van Eck phreaking' is that no shielding provides infinite attenuation at all frequencies. Even solid copper shielding has a finite, if very large, attenuation. With a cryogenic-cooled HEMT or similar front-end and a high gain antenna, the requirements for shielding could be as high as an attenuation of 100dB or more (copper screen is good for 30dB or so typically).
A cryo HEMT front-end isn't that far out of reach, even on pennies, as dry ice can get the temps low enough to foil thin shielding, and thicker shielding can be defeated with liquid nitrogen temps. Specialized near-field antennas that work on magnetic induction principles foil even the thickest pure copper, tin, or aluminum shielding; you need a ferromagnetic shield (mu metal is good) in addition to the copper to shield then.
Vent holes are the hardest, as you then want copper honeycomb material to act as 'waveguide beyond cutoff' attenuators. Slots and gaps of any kind can act as antennas; the Parkes radio telescope, for instance, has a webcam that required a very special enclosure where even the screw spacing had to be controlled. (see http://www.atnf.csiro.au/outre... for details).
While I do have mod points, I need to post this. I regularly see 1,000ms ping RTT on my otherwise reasonably fast (7/.5) DSL service when I have a lot of upstream traffic, and that ping RTT is to the router's gateway, a single hop away. My boss, who is on a 50/5 cable service, has consistent 1,000ms ping RTT to his next-hop. RTT for other packets varies according to protocol and IP target, showing some QoS queueing going on.
My DSL RTT to the next hop varies between a couple of ms to 1,000 ms depending on upstream traffic amount; determining my location based on that would be foolish.
If you want to pay more than $5 there are several eBay auctions for RPiZ running right now. Yes, Adafruit is out of stock on them, but they're not the only source, again, if you're willing to pay more than $5.
They already have control; 47 CFR Part 15 covers this completely.
While you can write whatever code you would like, and you can compile it with no worries, if that code causes interference above and beyond Part 15 rules it is a violation of the regulations for that code to be run if the device running that code is within the jurisdiction of the FCC (USA and its possessions). If you have a license, you are covered by the particular section of 47 CFR that covers your particular license, and you must abide by that license and its covering regulations (code for a TV broadcast transmitter, for instance, has a whole separate set of restrictions).
If a device possesses an intentional radiator of RF it is covered by one or more FCC regulations (in the US; internationally it's covered by the ITU and its vast portfolio of regulations). Many of the provisions of various regulations in 47 CFR are there because of ITU regulations, incidentally, including many in Part 15.
I'm not Bruce, but several people within certain Bureaus of the FCC do indeed understand Open Source. Even as far back as the '90's one of the engineers in the former Mass Media Bureau (deals with broadcasters) actually published some Open Source code showing how to use Fortran as a CGI program for websites..... they also have released a large quantity of code over the years.
One thing to remember about government agencies is that they are made up of people; the question isn't whether the agency knows anything, it's whether the people employed by that agency know.
Whether or not you believe in young-earth creationism or intelligent design has nothing to do with your aptitude in non-biology sciences and in engineering. I know a number of rather bright electronics and computer folk who are also YE creationists.
Given enough power on the transmit laser, you can blow out more than the sfp. Research the term 'fiber fuse' or watch https://www.youtube.com/watch?... for a hilarious holiday themed destruction of fiber with excessive light. (There are other videos on youtube; this one is just too funny to pass up.
The legislative boat already sailed, in 1934, with the passage of the Communications Act of 1934, that both created the FCC and specifically authorized it to craft regulations to do exactly what they are doing with this without further action by Congress. Congress has further amended the Communications Act over the years, one of the largest amendments being in 1996. Congress, by power vested in our elected representatives and with the approval of the President (in 1934, that was of course FDR; in 1996, it would have been Clinton) explicitly delegated regulatory authority to the FCC to do this. And thus Title 47 of the Code of Federal Regulations was born.
Gate capacitance on a junction FET (not all FET's are MOSFETs) and base to emitter capacitance on a typical bipolar are comparable. However, the best-case use for a bipolar is a cool little magnetic device called a transfluxer (no, I am not making that up; see US Patent number 4,459,653 for the 'bifluxer' variant and the citations to the original, Google's link is https://www.google.com/patents... ). A transfluxer-based inverter is very close to being as efficient as a MOSFET design. (And, don't worry, that patent expired nearly 20 years ago.)
Insulated-gate bipolar transistors (IGBTs) are the closest thing to the ideal; FETs in general are voltage-controlled resistors, and at least up until the HEXFET (by Intersil as I recall) invention had substantially higher output impedance than the typical bipolar; bipolars, especially when connected as emitter followers, have very low output impedance but likewise relatively low input impedance. The IGBT is the best of both worlds for high powers and finds pervasive use in the power control industry.
But MOSFETs are good enough for most things. Well, except that the transfer functions are different, just as different as bipolar, point-contact, unijunction, and all other transistors (transit resistors, after all) are from the firebottles they replaced (firebottle, glassFET, valve, tube, whatever you want to call those wonderful vacuum (or gas) based controllers of current....).
(yeah, I am an EE.....got out of EE and into IT to do a bit of stress-reduction.... and, yes, it worked.)
Slashdot Mirror
Hmm, and a couple of years ago I priced out a Dell Precision workstation with 1TB of RAM. The 1TB RAM alone listed at around $38,000.
What, you want it soaked in a mixture of ClF3 and FOOF , then rinsed in Piranha Solution?
Why not just burn in an oxygen- carbon subnitride fire?
Instead of 'evil hypervisor' think 'Intel Management Engine.'
There are many serial port redirectors out there, typically used with telnet server (ethernet to serial) boxes like the SitePlayer Telnet, some of the Lantronix stuff, and stuff from Equinox and Digi. These are very common for remote out-of-band console port admin of switches and routers.
I never used RIPTerm; on the PC I later used Telix, but I used ANSITerm on my TRS-80 Model 4D with hi-res card. I still occasionally fire up the old Tandy 1400LT 8088 DOS laptop and use Telix for console work, and I still have a TRS-80 Model 4P (with an HxC floppy emulator) and use Mel Patrick's FASTTERM as well as my own ANSITerm (hi-res board required.....). Makes some interesting conversation in a datcenter to roll in with a TRS-80 4P in tow...... But it makes a reasonable terminal for many uses.
I ran my part-time BBS in Atlanta on that Model 4, too, incidentally.
Lots of good memories meeting lots of interesting people. More interesting than Facebook; typically more civilized than Reddit, Slashdot, 4Chan, or pretty much anything else of today.
I ran a BBS in Atlanta in the mid-80's. Was very fun. Until joining Eskimo North (still online!) had not used a multi-user BBS. That was one of the draws of the BBS scene; single-user by nature, most of the time, and replies were far slower in coming..... 8/N1, The Greene Machine, Tandy Trader, Cornucopia, among many others. I still have a print of a 1987 dial-in list from Atlanta, and I was involved in many of them.
BBSing got me into uucp and running my own C-News leaf node attached to Eskimo North. Fun days. Usenet was the next step, really, beyond the dial-up BBS. Especially in terms of loss of civility; alt.flame, alt.barney.must.die.die.die, etc. Discussion of new group creation, some of the interesting things in alt.folklore.computers, and good times in comp.sys.tandy.
I have read it, back in 2009, around Christmastime. While Wheeler's dissertation is impressive, his own list of challenges (Section 8, page 118) is fairly extensive, and many of those challenges apply to the embedded development reality (most notably, the alternative compiler necessary to create the diversity). As an ECU is an embedded, and likely a rather proprietary, platform, it is likely that an alternative compiler would not be available.
Try again.
As long as you can build it youself, and the checksums match what's in the ECU, then this issue doesn't exist
Hmm, you must be new here. Please see Ken Thompson's 'Reflections on Trusting Trust' ( https://dl.acm.org/citation.cf... ) and come back once you're properly enlightened.
We still do. (I'm waiting on a four, three, or two digit ID to chime in.....
Sounds like segment three of the 15th episode of the mid-80's revival of The Twilight Zone to me. See: https://en.wikipedia.org/wiki/...
The comments about religion are petty spot-on, too; in essence, this makes the universe merely a figment of God's imagination..... our the figment of a computer simulation.....
Mixbus is a full-on professional DAW and sounds absolutely fantastic. I run Mixbus on CentOS 7 and everything works perfectly, for as many tracks as I want to throw at it.
Regardless of number of processes or threads total only X can run at any given timeslice, where X equals the number of CPU's/cores (virtual cores for HT) that you have. Finding the RF signature for a context switch would not be hard, since it is so repetitious.
One of the key concepts to realize with 'van Eck phreaking' is that no shielding provides infinite attenuation at all frequencies. Even solid copper shielding has a finite, if very large, attenuation. With a cryogenic-cooled HEMT or similar front-end and a high gain antenna, the requirements for shielding could be as high as an attenuation of 100dB or more (copper screen is good for 30dB or so typically).
A cryo HEMT front-end isn't that far out of reach, even on pennies, as dry ice can get the temps low enough to foil thin shielding, and thicker shielding can be defeated with liquid nitrogen temps. Specialized near-field antennas that work on magnetic induction principles foil even the thickest pure copper, tin, or aluminum shielding; you need a ferromagnetic shield (mu metal is good) in addition to the copper to shield then.
Vent holes are the hardest, as you then want copper honeycomb material to act as 'waveguide beyond cutoff' attenuators. Slots and gaps of any kind can act as antennas; the Parkes radio telescope, for instance, has a webcam that required a very special enclosure where even the screw spacing had to be controlled. (see http://www.atnf.csiro.au/outre... for details).
Note that I'm not just talking about PCs.
Heh, time for TEMPEST. But isn't this what the spread-spectrum bus modes are supposed to help reduce?
While I do have mod points, I need to post this. I regularly see 1,000ms ping RTT on my otherwise reasonably fast (7/.5) DSL service when I have a lot of upstream traffic, and that ping RTT is to the router's gateway, a single hop away. My boss, who is on a 50/5 cable service, has consistent 1,000ms ping RTT to his next-hop. RTT for other packets varies according to protocol and IP target, showing some QoS queueing going on.
My DSL RTT to the next hop varies between a couple of ms to 1,000 ms depending on upstream traffic amount; determining my location based on that would be foolish.
If you want to pay more than $5 there are several eBay auctions for RPiZ running right now. Yes, Adafruit is out of stock on them, but they're not the only source, again, if you're willing to pay more than $5.
But the TRS-80 Model II ARCnet board was indeed a piece of work. Grep the comp.sys.tandy archives on google groups for ARCnet one day.
They already have control; 47 CFR Part 15 covers this completely.
While you can write whatever code you would like, and you can compile it with no worries, if that code causes interference above and beyond Part 15 rules it is a violation of the regulations for that code to be run if the device running that code is within the jurisdiction of the FCC (USA and its possessions). If you have a license, you are covered by the particular section of 47 CFR that covers your particular license, and you must abide by that license and its covering regulations (code for a TV broadcast transmitter, for instance, has a whole separate set of restrictions).
If a device possesses an intentional radiator of RF it is covered by one or more FCC regulations (in the US; internationally it's covered by the ITU and its vast portfolio of regulations). Many of the provisions of various regulations in 47 CFR are there because of ITU regulations, incidentally, including many in Part 15.
I'm not Bruce, but several people within certain Bureaus of the FCC do indeed understand Open Source. Even as far back as the '90's one of the engineers in the former Mass Media Bureau (deals with broadcasters) actually published some Open Source code showing how to use Fortran as a CGI program for websites..... they also have released a large quantity of code over the years.
One thing to remember about government agencies is that they are made up of people; the question isn't whether the agency knows anything, it's whether the people employed by that agency know.
Whether or not you believe in young-earth creationism or intelligent design has nothing to do with your aptitude in non-biology sciences and in engineering. I know a number of rather bright electronics and computer folk who are also YE creationists.
Been quite a while since we've had a Battlestar Galactica thread.......
Given enough power on the transmit laser, you can blow out more than the sfp. Research the term 'fiber fuse' or watch https://www.youtube.com/watch?... for a hilarious holiday themed destruction of fiber with excessive light. (There are other videos on youtube; this one is just too funny to pass up.
The legislative boat already sailed, in 1934, with the passage of the Communications Act of 1934, that both created the FCC and specifically authorized it to craft regulations to do exactly what they are doing with this without further action by Congress. Congress has further amended the Communications Act over the years, one of the largest amendments being in 1996. Congress, by power vested in our elected representatives and with the approval of the President (in 1934, that was of course FDR; in 1996, it would have been Clinton) explicitly delegated regulatory authority to the FCC to do this. And thus Title 47 of the Code of Federal Regulations was born.
But of course I had to misremember intersil when I meant International Rectifier (HEXFET is a trademark of I-R, by the way).
Gate capacitance on a junction FET (not all FET's are MOSFETs) and base to emitter capacitance on a typical bipolar are comparable. However, the best-case use for a bipolar is a cool little magnetic device called a transfluxer (no, I am not making that up; see US Patent number 4,459,653 for the 'bifluxer' variant and the citations to the original, Google's link is https://www.google.com/patents... ). A transfluxer-based inverter is very close to being as efficient as a MOSFET design. (And, don't worry, that patent expired nearly 20 years ago.)
Insulated-gate bipolar transistors (IGBTs) are the closest thing to the ideal; FETs in general are voltage-controlled resistors, and at least up until the HEXFET (by Intersil as I recall) invention had substantially higher output impedance than the typical bipolar; bipolars, especially when connected as emitter followers, have very low output impedance but likewise relatively low input impedance. The IGBT is the best of both worlds for high powers and finds pervasive use in the power control industry.
But MOSFETs are good enough for most things. Well, except that the transfer functions are different, just as different as bipolar, point-contact, unijunction, and all other transistors (transit resistors, after all) are from the firebottles they replaced (firebottle, glassFET, valve, tube, whatever you want to call those wonderful vacuum (or gas) based controllers of current....).
(yeah, I am an EE.....got out of EE and into IT to do a bit of stress-reduction.... and, yes, it worked.)