IIRC in the original telnet protocol the list of keys that prompt synchronization with the server is negotiable. Normally that would be carriage return, and going to a full-screen editor would disable local echo, but adding tab to the list when in a shell should be trivial.
Until about 1996 I regularly used a Minitel (v23, http://en.wikipedia.org/wiki/Minitel) 75 bps upload, no chance of it keeping up even with a crappy keyboard!
Make it easy for your boss to say, "I guess public speaking isn't his thing." You'll likely never again be asked to do a big presentation.
And never get promoted either, because a great part of a high-level job is presenting your analysis, your point of view, your decisions, and the options you or the attendees have, and doing it in as clear and engaging a manner as possible. In fact I could even argue that in managers it's even more important than being good at the underlying job, because managers have technical guys to do the drudge work.
It's the story of the guy sued in small claims court about payment for a book. The book is "Kidnapped" by Robert Louis Stevenson. The computer misfiles it in major crimes, and the guy finds himself on death row for kidnapping Mr Stevenson -- after Mr Stevenson is deceased.
c64 emulators work really well. Just the other day I finished the first game I ever got. It was too difficult, but with snapshots I finally managed to see and hear the final show!
Both MasterCard and Visa are on the list. I'd be happy with American Express or Diners Club or whatever, but living in Europe there's not much else than those two.
WoT is a short little series you should be able to finish on the flight.
Only if his flight takes a year or so and he can get the last book delivered to his seat!
For those who don't know, the first Wheel of Time book was released in 1990 and number 14 (which should be the last one) is currently predicted for late 2012.
The 'guestimation' strategy fails at question 5 that has two answers that are very close to each other ($203.00 and $208.80). However, my mathematical instincts tell me that 203.00 is an unlikely outcome when multiplying with 29. I used a calculator to confirm my guess (as allowed by the test).
Rely on your instincts not your calculator; there's actually a catch there. It's probably designed specifically for students who stop division at the decimal point . . . or engineers who miss setting the scale with bc!
$ bc -q 288/40*29 203 - hey that is one of the four possible answers! scale=5 288/40*29 208.80000 - but not the *right* answer....
The average COBOL programmer is also much older than the average Java programmer.
Maybe, but I work with a lot of COBOL programmers. Most of them are young and very good. While it's easy, it would be an error to assume that age is good. I have stared in horror at a fiftyish COBOL contract programmer displaying such blatant incompetence that we evoked a firing on the spot (in reality it took a few weeks). We think the person in question had no computer experience at all, but had been placed by the contract agency after a week or so of COBOL and nothing else . . .
The Feds didn't like this...specifically for their contractors...the guys just plain worked too much.
Well my employer will not pay me overtime unless my boss says there's work to do that for some reason merits overtime! If he doesn't, I can stay late all I want, but I won't be paid a cent more. Is the federal government different somehow?
Very true, except you don't need a horrible commute. Having telecommuted for years, I think you have to have a clear disconnect between work and home. I have a five-minute drive (or a really relaxing 30-minute walk if I feel like it). It's long enough to make a real break, and that's all I needed.
However do not forget the TIME it takes to backup and wipe. I hope your disks are not too big! If they are, you might want to partition them to use only a small part of the disk.
More to the point, what is the aim of your requirements? Maybe you would be better served by
- diskless workstations
- encrypted disks
- encrypted partition with the key in the boot partition (wipe the 1 MB partition containing the key and bingo you've wiped your 3TB disk)
I've seen for myself that hard disks that run for a long time (years) have problems starting up again after a power off. I've long supposed that it had to do with some bearings wearing out or oil getting used up. RAID is of course the correct answer to that, but even if I have to offline a service for some reason, I've gotten into the habit of not powering off the second side of a HA pair until the first one is safely back up.
An average of 4.74 for people connected to FaceBook. So? There are lots of people NOT connected to FaceBook. If anything this finding actually gives weight to the value 6 for everyone on the planet!
What would also be worth exploring is exposing them to a MRI.
Does "Worth" imply that you are prepared to pay for the damage to the MRI machine?
FWIW, my method would be to take the things apart, smash the platters with a hammer (inside a bag to avoid splinters), and that's it. Maybe OP wants to avoid the NSA reading his disks, but somehow I doubt that anyone is going to come along with an electron microscope to analyze the pieces.
<quote>That's when I soldered a cable to hook my CBM 1541 disk drive up to a DOS box</quote>
There are different cable wirings, and the ones that work with modern computers seems disagreeable to make (you need uncommon components that I think would be hard to get except in quantity, etc.) I found a guy on ebay who apparently makes lots of them. Cable works a treat.
And when will one be able to one's own CA for one's own domain... I'd be prepared to pay good money for verification of my example.com cert, as long as it can sign certs for NNN.example.com, instead of either buying/getting a cert for every single NNN, or getting a wildcard cert for *.example.com. But no, the common name is just a string, nothing learned from the distributed nature of DNS.
Microsoft employed capability researcher Jonathan Shapiro for some time, but not any more. I wonder if that's because they decided it was too hard, unfeasible, never wanted caps at all, or some other reason. Caps would definitely be a way to defeat several if not most classes of bugs. In fact I have never encountered another method of computer security that seems credible.
Roaming is a pain. It' a pain to choose a closed network, a closed network with a well-known password, a passwordless open network or several passwordless networks that will redirect you to a captive portal that can ask you for different sums of money or your address and the number of your passport (true story). That is before you consider that anyone in your vicinity can configure your expected SSID and middle-man your password and everything else. Ask yourselves where you want mobile access to be in ten or twenty years. Answer: hassle-free. You may want to choose your hotspot based on performance or price or simply because it's yours, but roaming far from home in an era of not-quite-ubiquitous Internet, you most probably just want one that works.
Redesign authentication using client certificates so that the user's ISP can authenticate the user directly for any hotspot. The hotspots would simply keep a list of approved CA certificates. You'd insert the name of the ISP's authentication servers into the ISP CA certificate into the client certificate.
You could add in a option for mandatory VPN direct to the ISP. It could be made mandatory by the user or by the hotspot. The hotspot provider would then not have to keep user logs and worry about responsibility and source ports and otherwise identifying abuse. The user would have his VPN, his own IP address, could roam almost seamlessly over hotspots belonging to different owners, and would not care about choosing the hotspot based upon the confidence that the hotspot operator will not sniff or use a sniffable upstream.
You could add in a fee (advertised through the SSID?) that would be put on the user's ISP bill and transferred to the hotspot operator. The ISP would need the address to send the money, but that can also be put in the authentication procedure. If the connection is mandatory VPN there can't even be disputes about the amount to bill, since the hotspot and the ISP should have the same amount.
<NICE> This is what you get when important functions are written by people who do not have the slightest inkling of what network security is about. You can put loads of $$$ into planning and design into specifying authentication, and it all falls down because the grunt who actually does the work doesn't have a clue. </NICE> <REALISTIC> Probably the grunt without a clue is the smartest guy over there.
I know some employers who don't care what degree you've got, as long as you've got one.
So do I, and that includes at least one nation-state with several million "employees". Namely France. For a lot of state jobs, you pass a "concours". It's like an exam, you get graded, but there are a fixed number of openings, and the best grades get the jobs. Mostly it's employment for life. But in order to be allowed to sit a "concours" you need a degree, the minimum level of the degree depending on the job . . . a degree that does *not* have to have any relation at all with the job you're trying for.
IIRC in the original telnet protocol the list of keys that prompt synchronization with the server is negotiable. Normally that would be carriage return, and going to a full-screen editor would disable local echo, but adding tab to the list when in a shell should be trivial.
Until about 1996 I regularly used a Minitel (v23, http://en.wikipedia.org/wiki/Minitel) 75 bps upload, no chance of it keeping up even with a crappy keyboard!
Make it easy for your boss to say, "I guess public speaking isn't his thing." You'll likely never again be asked to do a big presentation.
And never get promoted either, because a great part of a high-level job is presenting your analysis, your point of view, your decisions, and the options you or the attendees have, and doing it in as clear and engaging a manner as possible. In fact I could even argue that in managers it's even more important than being good at the underlying job, because managers have technical guys to do the drudge work.
Sounds to me like social services just found the guy's name involved in a child porn investigation and assume he's dangerous.
The days when Computers Don't Argue are coming!
It's the story of the guy sued in small claims court about payment for a book. The book is "Kidnapped" by Robert Louis Stevenson. The computer misfiles it in major crimes, and the guy finds himself on death row for kidnapping Mr Stevenson -- after Mr Stevenson is deceased.
No surprise I left them later that year.
Frankly, I would have tendered my resignation in that hospital bed.
Bad move. Definitely wait until you get out of the hospital before resigning!
c64 emulators work really well. Just the other day I finished the first game I ever got. It was too difficult, but with snapshots I finally managed to see and hear the final show!
I want an hourly income of $55,600 too. I don't understand why they only work one hour a year, in their place I'd work a whole day!
Both MasterCard and Visa are on the list. I'd be happy with American Express or Diners Club or whatever, but living in Europe there's not much else than those two.
WoT is a short little series you should be able to finish on the flight.
Only if his flight takes a year or so and he can get the last book delivered to his seat!
For those who don't know, the first Wheel of Time book was released in 1990 and number 14 (which should be the last one) is currently predicted for late 2012.
And The Diamond Age is excellent for thinking about what might happen once we get nano-scale machines.
The 'guestimation' strategy fails at question 5 that has two answers that are very close to each other ($203.00 and $208.80). However, my mathematical instincts tell me that 203.00 is an unlikely outcome when multiplying with 29. I used a calculator to confirm my guess (as allowed by the test).
Rely on your instincts not your calculator; there's actually a catch there. It's probably designed specifically for students who stop division at the decimal point . . . or engineers who miss setting the scale with bc!
$ bc -q
288/40*29
203 - hey that is one of the four possible answers!
scale=5
288/40*29
208.80000 - but not the *right* answer....
The average COBOL programmer is also much older than the average Java programmer.
Maybe, but I work with a lot of COBOL programmers. Most of them are young and very good. While it's easy, it would be an error to assume that age is good. I have stared in horror at a fiftyish COBOL contract programmer displaying such blatant incompetence that we evoked a firing on the spot (in reality it took a few weeks). We think the person in question had no computer experience at all, but had been placed by the contract agency after a week or so of COBOL and nothing else . . .
The Feds didn't like this...specifically for their contractors...the guys just plain worked too much.
Well my employer will not pay me overtime unless my boss says there's work to do that for some reason merits overtime! If he doesn't, I can stay late all I want, but I won't be paid a cent more. Is the federal government different somehow?
Very true, except you don't need a horrible commute. Having telecommuted for years, I think you have to have a clear disconnect between work and home. I have a five-minute drive (or a really relaxing 30-minute walk if I feel like it). It's long enough to make a real break, and that's all I needed.
Definitely PXE.
However do not forget the TIME it takes to backup and wipe. I hope your disks are not too big! If they are, you might want to partition them to use only a small part of the disk.
More to the point, what is the aim of your requirements? Maybe you would be better served by
- diskless workstations
- encrypted disks
- encrypted partition with the key in the boot partition (wipe the 1 MB partition containing the key and bingo you've wiped your 3TB disk)
I've seen for myself that hard disks that run for a long time (years) have problems starting up again after a power off. I've long supposed that it had to do with some bearings wearing out or oil getting used up. RAID is of course the correct answer to that, but even if I have to offline a service for some reason, I've gotten into the habit of not powering off the second side of a HA pair until the first one is safely back up.
No, he is not dangerously close. He is aware. He realizes that he does not need to spend lots to get photos good enough for him.
*This* is a guy bitten by the equipment bug: The 1 percent takes up photography
An average of 4.74 for people connected to FaceBook. So? There are lots of people NOT connected to FaceBook. If anything this finding actually gives weight to the value 6 for everyone on the planet!
What would also be worth exploring is exposing them to a MRI.
Does "Worth" imply that you are prepared to pay for the damage to the MRI machine?
FWIW, my method would be to take the things apart, smash the platters with a hammer (inside a bag to avoid splinters), and that's it. Maybe OP wants to avoid the NSA reading his disks, but somehow I doubt that anyone is going to come along with an electron microscope to analyze the pieces.
<quote>That's when I soldered a cable to hook my CBM 1541 disk drive up to a DOS box</quote>
There are different cable wirings, and the ones that work with modern computers seems disagreeable to make (you need uncommon components that I think would be hard to get except in quantity, etc.) I found a guy on ebay who apparently makes lots of them. Cable works a treat.
And when will one be able to one's own CA for one's own domain... I'd be prepared to pay good money for verification of my example.com cert, as long as it can sign certs for NNN.example.com, instead of either buying/getting a cert for every single NNN, or getting a wildcard cert for *.example.com. But no, the common name is just a string, nothing learned from the distributed nature of DNS.
Microsoft employed capability researcher Jonathan Shapiro for some time, but not any more. I wonder if that's because they decided it was too hard, unfeasible, never wanted caps at all, or some other reason. Caps would definitely be a way to defeat several if not most classes of bugs. In fact I have never encountered another method of computer security that seems credible.
Roaming is a pain. It' a pain to choose a closed network, a closed network with a well-known password, a passwordless open network or several passwordless networks that will redirect you to a captive portal that can ask you for different sums of money or your address and the number of your passport (true story). That is before you consider that anyone in your vicinity can configure your expected SSID and middle-man your password and everything else. Ask yourselves where you want mobile access to be in ten or twenty years. Answer: hassle-free. You may want to choose your hotspot based on performance or price or simply because it's yours, but roaming far from home in an era of not-quite-ubiquitous Internet, you most probably just want one that works.
Redesign authentication using client certificates so that the user's ISP can authenticate the user directly for any hotspot. The hotspots would simply keep a list of approved CA certificates. You'd insert the name of the ISP's authentication servers into the ISP CA certificate into the client certificate.
You could add in a option for mandatory VPN direct to the ISP. It could be made mandatory by the user or by the hotspot. The hotspot provider would then not have to keep user logs and worry about responsibility and source ports and otherwise identifying abuse. The user would have his VPN, his own IP address, could roam almost seamlessly over hotspots belonging to different owners, and would not care about choosing the hotspot based upon the confidence that the hotspot operator will not sniff or use a sniffable upstream.
You could add in a fee (advertised through the SSID?) that would be put on the user's ISP bill and transferred to the hotspot operator. The ISP would need the address to send the money, but that can also be put in the authentication procedure. If the connection is mandatory VPN there can't even be disputes about the amount to bill, since the hotspot and the ISP should have the same amount.
<NICE>
This is what you get when important functions are written by people who do not have the slightest inkling of what network security is about. You can put loads of $$$ into planning and design into specifying authentication, and it all falls down because the grunt who actually does the work doesn't have a clue.
</NICE>
<REALISTIC>
Probably the grunt without a clue is the smartest guy over there.
I know some employers who don't care what degree you've got, as long as you've got one.
So do I, and that includes at least one nation-state with several million "employees". Namely France. For a lot of state jobs, you pass a "concours". It's like an exam, you get graded, but there are a fixed number of openings, and the best grades get the jobs. Mostly it's employment for life. But in order to be allowed to sit a "concours" you need a degree, the minimum level of the degree depending on the job . . . a degree that does *not* have to have any relation at all with the job you're trying for.