Actually, it's acceptable to use the traditional, common Germanic (versus Romantic) prefixes and suffixes with any word if it does not already have an established form in the part of speech or with the altered meaning required. -hood, -wise, -ish/-esque, -ing, -est, -er, -ing, -y, etc. Some more recent prefixes and suffixes are generally considered acceptable, at least outside of formal writing, too. Everything assimilated into Middle English is, really; it's just that some assimilations in recent Modern English are still considered unacceptable in formal writing, which is understandable. A handful of Middle-English-era Romance assimilations are -al, -ment, -ic, -ion, -tion, -er, -ive, -able, -or, -ity, and one common Greek assimilation into early Modern English is -ism. Now, don't forget that typically the root word's language of origin has to match the suffix's most recent language of origin before assimilation into English (careful, one suffix listed had been in proto-Germanic, Old French, Middle French, Sanskrit, Old German, High Germanic, Latin, and Old Norse, but was assimilated into Old English from Old German), and that you have to follow the same patterns that existing, established words do, so as to avoid consonantal clusters that do not occur in English... (amongstment strengthtion, anyone?)
Oh, and my on-topic 2-cents: isn't this what freenet is for? Just don't post who you are, or why you're posting on freenet. Don't create any timing-trail, either, to make anyone think it might be *you* who posted this interesting piece of code on freenet.
I don't think artificial gender lines for clubs are a good thing. The various scouting and campfire/outdoors groups should just re-brand themselves as various types of character-building and skill-building clubs; BSA could tend to target more activities and skills boys would be interested in, while Girl Scouts could target the activities and skills girls would be interested in. Neither would discriminate, so [just stereotyping here:] tomboys who would be happier with boy-scouting could go that direction, and the less-"tough"/more-effeminate boys who would be happier with the Girl Scouts could go that way. (Again, I emphasize that those are *stereotypes*... I don't really believe the division would ideally be just like that! In fact, having boys and girls learn skills and traits traditionally associated with the opposite gender and breaking social gender role molds in the process is really neat imho.) That being said, the chaperoning issue is still a problem, with the way our society handles gender privacy and bathroom issues (not that our system is necessarily bad, but it could probably use some improvement - see #1 for something I disagree with, and #2 for an amusing comic on that subject - I think having more unisex and family bathrooms would be preferable, with several private, individual bathrooms for every multi-person unisex one). Chaperoning could be handled more by the parents voting rather than by gender-grouping [how many intersex parents are there for the intersex children who self-identity as intersex rather than male or female? *grin*]. There are plenty of adults of both genders who treat all children with respect and would never dream of harming them, and these adults would make fine chaperones for any children, to the extent that those children and their parents are comfortable. {:prepares self for flames:}
I've often found that I cannot bring myself to believe many things in the Bible, but neopaganism holds my interest. I also equate "God + Goddess" with the whole of the Universe (or David Lewis' multiverse) instead of believing in a supernatural God. It works for me, and doesn't require me to believe in any "voodoo."
The second link only needs two bjt's (1 npn, 1 pnp) and 5x 10kOhm. Even from the local radio shack, $8.99 for a small solderless breadboard, $6.99 for a 100' spool of solid 22awg wire, $2.99 for a 15-pack of 2n2222 npn's, $2.59 for a 15-pack of 2n3904 pnp's, $0.99 for a 5-pack of 1/8W 10kOhm@5%, and $1.99 for a female DB-9 crimp connector is only $24.54 (before any sales tax). If you can solder, you can save $7 by going with the 417-hole pre-etched PCB, and you can probably de-solder any NPN, PNP, and five 10k's from old busted electronics (dead CRT is a good example: fewer SMD's and more lead-ed/through-hole components; and for that matter, you can probably break off part of a PCB from a CRT, de-solder all the components, and use the traces already etched to save the cost of a PCB). If you have a few feet of solid 18-24AWG wire around the house, you can save $6.99; solid wire may be harder to find in small consumer electronics, but is still not hard to find in random broken appliances (and if you're soldering it, you can just use stranded wire from any random old cable or consumer device). For the DB-9, you can always chop in half any cable that plugged into a serial port (you'll need to figure which pin goes with which wire---use an ohmmeter, or if you don't have that, a voltmeter (many battery checkers are basically voltmeters) and a battery, or if you don't have that, improvise by using a flashlight with the battery cover opened (turn flashlight switch on, insert wire/pin into DB-9 hole being traced and connect to the open side of the batteries, and then try each of the wires in the cable to complete the electrical connection normally completed by the battery cover until it lights up)); it'll almost definitely have stranded wire inside, so for a solderless breadboard you'll have to use a piece of solid wire and solder them or, without solder, twist the ends together well, wrap tightly in electrical tape (duct tape can be substituted if you have no electrical tape) until of sufficient thickness, and screw into a wire cap (the kind used to connect two household internal power wires together) to keep pressure on the connection. You can forego the screw caps if you wrap very, very tightly with good tape and aren't worried about the connection holding forever.
Getting solid wire, sewing needles, or the points of safety pins to stick in the holes (not the big ones, but the small rectangular ones next to each big hole) of the OBDII connector usually works. If you don't have luck with that, you can re-bend some paper clips into a U-shape of appropriate width or use the curled end of a safety pin of appropriate size.
Really, any computer geek with patience can probably do this for zero cost;) Even without a soldering iron, you can probably locate a section of PCB (again from CRT etc) with one NPN and one PNP BJT and without any surface-mounted components, remove other components by cutting the leads (keep in mind that longer leads might be snipped as close as possible to their component so as to create points for easy connection to wires) with wire cutters (or fingernail clippers, in a pinch), and cut unneeded traces carefully with an x-acto or razor blade (or by carefully sawing with a serrated kitchen knife, like a steak knife, in a pinch). The only part that you may have to dig around for is a cable with a female DB-9 connector at one end, and you may be able to get around that by squeezing the needed pins from the male DB-9 serial port between the insulating sheath and copper core of some wire by pushing the wire down onto the pin with small needle-nosed pliers (or tweezers in a pinch). Honestly, with a few hours and some old electronics that can be sacrificed, it's very jury-riggable, though like the parent poster states, you may need to pay a little more for decent housing and an actual OBDII plug.
What Dave said: "Open the pod bay doors, HAL." What HAL heard: "Open the hot babe pornz, HAL."
HAL's speech recognition and morality programming* combined to give the famous reply, "I'm sorry, Dave. I'm afraid I can't do that." HAL knew certain things would have been too titillating to an all-ages film audience in 1968.
* Only for the film version. In the book version, it would have caused undue frustration to the reader, unable to see what Bowman was viewing. In that case, it was HAL's etiquette programming.
I'm leaving two free variables: what keep-the-beat task to use, and what syncopation/accentuation task to use. I'm expecting the drummer to be able to freely switch among many combinations on the fly, which is how I'm requiring it to be two tasks, and not just another learned merged-task. Of course, if you learn a particular combination of those two (e.g. for a particular song), then, yep, it becomes one task. Ask any drummer that sings and plays drums at the same time if he/she can sing the same part overtop of a different, arbitrary combination of keeping-the-beat and syncopation/accentuation, and you'll see him/her trying to focus on three tasks at once.
With practice, singing and drumming through a particular song will because (mostly) an isolated, single task---that's the point where nothing bizarre occurring onstage will throw the drummer off from singing or drumming, unless he/she is experimenting with a task combination that hasn't been yet learned as a single task (singing a different harmony part when another vocalist in the band is out sick, for example).
When you practice doing two tasks simultaneously, they become a new, single task. How do good drummers play syncopated beats? You learn a multitude of "keeping the beat" tasks involving many combinations of common patterns on the bass drum, hi-hat, and ride cymbal, then you learn a variety of syncopated beat tasks to play "overtop" of the other task. (You also have to learn strategies for performing these tasks at the same time, especially when you have to borrow a foot or hand from the keeping-the-beat task for an accentuated part and then un-borrow it; however, my point---namely, for a good drummer, many complex patterns involving multiple limbs, when practiced sufficiently, become simply "one task"---still stands.)
Oooh! I just had a *brilliant* idea! Instead of protecting the driver by putting several feet of car engine between him and the front of the vehicle, why not put the driver out *right at the front*, in the position of vulnerability, and split up the engine into halves, sticking either half on the left and right side of the car? That way, the driver will surely be careful to look where he is going, but if someone runs the red light and T-bones him, he'll be okay.
Now, who wants to lend me some $ so I can file some patents?
I'm not sure about the wireless hacking from a laptop mentioned in TFS, but, as far as RF transmissions, these things can generate plenty of spread-spectrum modulation EMF when modulating the 240kHz signal carrier on wire. There's a good discussion about eliminating ground loops so as to avoid broadcasting the signal as a source of interference at the Technical Library; I suppose one could always use an inductionreceiver to go the other direction, using a loopantenna. Obviously, modification of the above designs is needed for target frequency band. AM radio circuits might be a good place to start, too. Actually, there are tons of good MW box loop designs that already go well below 240kHz; that page includes a calculator, and playing with some quick numbers suggests a 48cmX65cm frame [=56.5cm side length] for a 16-turn coil extending 21cm in length in parallel with four 470pF caps gives us resonance at 245kHz. Of course, with 20% tolerance ceramic discs, you may want to replace one of the 470's with a 4-40pF variable cap in parallel with anywhere from a 150pF to a 39pF paralleled with a 560pF, depending on how low or high the 470's are measuring.
Computer memory, in an abstract sense, tends to be looked at in a hierarchical way: * Registers * Caches * RAM * Secondary storage (swap)
A filesystem is a datastructure, arguably just nominally imposed on a dedicated swap-space of sorts. When you buy a gig of RAM, you expect 2^30 bytes, not 10^9 bytes. I've never understood why HD think that their "secondary storage" does not belong under the paradigm of "computer memory" when talking about sizing, despite the fact that all modern OS's use swap space, and filesystems are all data structures whose constituents tend to fall on word boundaries.
Yeah, this is really old stuff. I think I saw malware attacks using this at least as early as 1998. I had not done much sockets programming at that point, but once I saw it, I immediately started studying the RFCs, and was like, "hey, neat!" I think every single IP-address-parsing routine and IP-address-matching-regex I've written since then has always been designed to handle this and tested against every form of it. I really don't understand why there could be any software out there at this point that would have any problems, but I suppose it is arrogant to assume every other programmer has my mindset. Oh well, I guess that means I can use it as a selling point for my own code, then:-P
Knows a lot? Are you sure?;) It has a lot more to do with the pattern of resonance from vocal tract length than base pitch, which is possibly why pitch-shifting the whole spectrum often doesn't seem to change the perceived gender of a voice very well. Playing with resonance through tongue and larynx positioning and hearing the changes producable in timbre without changing the fundamental pitch is quite fascinating to me, esp. as a clasically-trained singer [among other reasons]. Lynn Conway, one of the key engineers behind VLSI technology, is a transwoman who feminized her voice through careful practice and self-study, according to the above WP link.
Yeah, but the task has to seem/ostensibly/ completable in 60 seconds, or else nobody's heart is really going to be in it for the cool million. -- Actually, they should just give the techs a stack of perfboard, some spools of cable, a book of schematics, a huge bucket of NAND and XOR chips, a box of tiny circular ferrite cores, and some wire-wrapping tools. You get a bonus if you get the Unibus timings right on the first try.:-D
Exactly. I enjoy how many sites block the user-agent string for wget. This is easily remedied with tagging --user-agent "Mozilla/4.0 (compatible; definitely-not-yoo-git)". Since wget politely will obey robots.txt, though, to do recursive downloading, you really ought to remember to change this compile-time "option" by carefully commenting out the appropriate code. (What?! You're installing a binary you didn't compile yourself?!);)
I've always enjoyed randomizing identification information. My/etc/issue.net (in the days of telnet) used to be fed by a daemon that would print login banners from ULTRIX, VMS, SunOS4, BSD 4.3, CRAY Unicos, etc. The automated script kiddie banner-scanners of the day used to have lots of fun with that, let me tell ya. (sshd's Banner option isn't as flexible, just static text... it's disappointing, because the various gettys always had @ and \ options. I did used to modify my getties to extend those options though, so, I've played with extending my sshd for an field-substituting banner message. For the record, if you're curious about extending OpenSSHd, since it loads the banner file into a static text area at startup: You can have a config-file-rehash or SIGHUP-style routine reload the bannerfile. If you want to do load-average numbers in your banner, you can have the daemon wake up every 60 secs and get that info from/proc or appropriate kcalls for your OS and put them in appropriate static vars. Replace the call to print the banner on connect with something like: alloc larger temp buffer (if fail, bail with an error) and do substitutitions up to the buffer length, ensure NUL-term'd, tell connection-handler code to write that buf, and plan to dealloc when the connection-handler code no longer expects to need to push any more text from that buffer to that accepted sock (the tricky part, iirc from the opensshd code!))
Yeah... this might be some sort of miscommunication. Mickey Mouse's lawyers might not have really understood the implications of a BSD license. I wouldn't be surprised if the Ptex site disappears, nothing further ever arrives along the lines of open-source code, and Disney's lawyers attempt to find loopholes to get mirrors of the Ptex source taken down.
Disney has always held tight controls over their IP, and while the BSD license gives them a lot of control over what *they* do with Ptex, it gives the community a lot of control over what the *community* does with Ptex, provided any forking coders properly acknowledge the original authors and abide by the set (albeit minimal) of constraints provided by the BSD license.
[Obligatory IANAL, so any groklaw aficianados, feel free to correct, clarify, or serve me with a court-order comprising one Clue Stick (TM).]
The research out there on neural regrowth in adults is very interesting, because, yes, the classical empirical evidence is that damaged neurons go into apoptosis and are cleaned up by glial cells.
My girlfriend has atypical trigeminal neuralgia and underwent an unsuccessful microvascular decompression on the brainstem (wherein a venous structure was deconstructed and cauterized, a venule was padded with teflon, and a minor arteriole was resectioned and cauterized), followed by a more-successful partial sensory rhizotomy to resection the nerve in Meckel's cave via a 60% cut that ideally would hit most of the group-C fibers. The outcome of the rhizotomy is interesting, because it seemed to take care of the mandibular nerve pain while leading to a very odd outcome. In the vast, vast majority of partial sensory rhizotomies on cranial nerves (meaning more-or-less the ~99% who do not have the horrid-sounding outcome known as anaesthesia dolorosa), the loss of sensation eventually diminishes, as the nerve undergoes restructuring. There seems to be very little information in popular medical literature on the restructuring process, and as I don't have access to any specialized journals (for neurology, neurosurgery, etc.), I cannot find much information; however, it seems to perhaps involve rapid branching of the dendrites in parallel with apoptosis and glial clean-up of damaged neurons. In >90% of rhizotomies, there is little discomfort during this process. My girlfriend is one of the "lucky few" (and by that I mean that her neurosurgeons, Dr. Sekula and Dr. Jannetta, who himself pioneered microvascular decompression and other techniques for trigeminal neuralgia of both types and various types of hemifacial spasm, at Allegheny General Hospital, said they could not even remember the last time they had seen the effect she is experiencing) to have severe discomfort during the restructuring process. This discomfort is a dysthesia characterized by intense sensations of all types from the cranial nerve. She is experiencing sensations of pressure, nociception, touch, and proprioception in all branches of the trigeminal nerve, meaning not only the major three branches (ophthalmic, maxillary, and mandibular), but the minor branches out of Meckel's cave as well. In addition to that, she is having branching across into adjacent cranial nerves. These sensations range from moderately intense to maximally intense (meaning she is experiencing at times the same sensations someone would have if their skull was being crushed to pulp, or face was being cut deeply open in many places, etc.), but at least they can be controlled somewhat by extremely high levels of antiseizure medication. Between the sensations and medication, though, she is effectively completely disabled while the nerve undergoes this type of healing. The good news is that her neurosurgeons have never seen, either themselves or in any journals, a case of this that does not resolve when the restructuring reaches its end-stage, which occurs after six to twelve months. The intermediate time, though, is Hell for her. I would love to see more research done on this, as I would be curious to see if various signalling mechanisms are not genetically nominal in the <10% of cranial nerve rhizotomy patients who have this type of post-procedural effect.
Please, let's continue the research on SOCS3 here, and the other research being done out there on the various other known signalling mechanisms.
Oh hell, just register [add-accent-to-previous-letter]bankofamerica.com. There are tons of ways to abuse unicode, as many security papers have already discussed.
Hardware checks need to be in place, even if that makes more operating training required to recover from common hardware fault conditions.
For any dose above normal, two separate keys should have to be turned, separated in time by 30 minutes (so if a hospital was stupid enough to give the same person both keys, they have a half hour to think). Any dosage above normal should require being entered three times.
People can sleepwalk through their job. If they're doing something potentially dangerous, it's not unreasonable to set up their job so that their environment wakes them up before they make a possible serious mistake.
The problem is, if myspace admits "oops, we screwed up, we'll fix it," they mean they'll fix it for the squeaky wheel that complained, not in general. We won't see any reform of policies from this. It'll take a LOT more squeaky wheels for the ideal type of change to occur... it's just not profitable otherwise.
Agreed that the GP is using faulty logic. However, "Even if it's not true causing pollution is not good" is something worth studying further.
Oceans fix CO2 and plants metabolize CO2 to O2 (well-known facts). CO2 is a greenhouse gas of sorts (known fact). Humans pump out a not-insignificant amount of CO2 through industrial processes (known fact). Whether we're messing up the climate or not is something we can never really prove, either way; rather, it's a question of whether investing the money in improving industrial processes to be more efficient in their recycling of CO2 production. I think the whole climate change propaganda is missing the point on this.
"We have Java, as well as Python and various other languages on Linux for the niche Mono wants to fill."
I like to see open software offer a compatible option for every closed system. This may in many ways be somewhat futile as it's forever chasing something that can never be realized, but that's the flip-side of the point: to keep closed systems on their toes. If there's an open solution for *everything*, even for closed problems, nobody can argue that open software is incapable of helping with closed system X Y or Z.
("Utilize" has a more specific meaning than "use". "Use" means you're just working with something, for better or worse; "utilize" means you're making practical or profitable use of something. Arguably, you could say that any good teacher-student relationship implies that any skill a student uses for the goals of the course is put to *good* use, so "utilize" would be unnecessary complexity; but, maybe the submitter was trying to draw attention to the idea that this wasn't simply a read-stories-for-fun class. True, the usage is a little redundant, still, as using a skill or a strategy implies putting it to good use, unless the usage is implicitly or explicitly stated as bad. I realize "utilize" is drastically overused. Sorry if I'm giving the submitter the benefit of the doubt, but, hey... if you get to nitpick, I get to nitpick, too!)
I've seen some posts suggesting particular authors or stories, and an excellent post suggesting that maybe analyzing the classification of the material would offer more insight and useful long-term experience. On the first item, please find a couple good short stories by Asimov; he shouldn't be overlooked. On the second item, a detailed literary analysis could encapsulate several goals, and could be done over the length of the course in short segments. One of my high school literature teachers made us write a literary analysis of a novel with many, many short segments (some sharing no overlap). I found that this gave me a lot of insight into the work of fiction I chose (Philip K. Dick's 'A Scanner Darkly'), in terms of both extrinsic nature of my perception and the deconstruction of the novel's writing, and aspects of the story-world both internal and external to the words on the pages.
For the literary analysis, maybe the students should be prepped within the first few days for their project, and being given the suggestion of thinking carefully about how the project would pan out for several books of their choosing. After a week's thought, they could narrow the books down to ones that would be good to analyze (not necessarily their all-time-favorites, make that clear), and you could review the books and recommend which one of their final groups of choices seemed the best to analyze. This way, the student doesn't get stuck with a crappy (though perhaps still fun) fictional work when trying to do analysis. To discourage putting things off to the last minute, the project would not need to be a term paper but rather just a coherent study of the book, done in sections. Give the students a few weeks to read the books carefully, after familiarizing them with the types of things they'll need to be watching for. Then, the analysis can be done in stages, presenting the goals of each stage in detail after the last stage has been turned in. You'd want to avoid long works, since they may need to re-read large parts of the book for each stage. Each stage can also include a paragraph on how that part of the analysis relates to the theme of the course in terms of the book and in terms of the type of analysis itself.
Doing a detailed literary analysis in high school changed the way I read books forever. I have much more appreciation for well-written literature now.
Slashdot Mirror
Actually, it's acceptable to use the traditional, common Germanic (versus Romantic) prefixes and suffixes with any word if it does not already have an established form in the part of speech or with the altered meaning required. -hood, -wise, -ish/-esque, -ing, -est, -er, -ing, -y, etc. Some more recent prefixes and suffixes are generally considered acceptable, at least outside of formal writing, too. Everything assimilated into Middle English is, really; it's just that some assimilations in recent Modern English are still considered unacceptable in formal writing, which is understandable. A handful of Middle-English-era Romance assimilations are -al, -ment, -ic, -ion, -tion, -er, -ive, -able, -or, -ity, and one common Greek assimilation into early Modern English is -ism. Now, don't forget that typically the root word's language of origin has to match the suffix's most recent language of origin before assimilation into English (careful, one suffix listed had been in proto-Germanic, Old French, Middle French, Sanskrit, Old German, High Germanic, Latin, and Old Norse, but was assimilated into Old English from Old German), and that you have to follow the same patterns that existing, established words do, so as to avoid consonantal clusters that do not occur in English... (amongstment strengthtion, anyone?)
Oh, and my on-topic 2-cents: isn't this what freenet is for?
Just don't post who you are, or why you're posting on freenet. Don't create any timing-trail, either, to make anyone think it might be *you* who posted this interesting piece of code on freenet.
I don't think artificial gender lines for clubs are a good thing. The various scouting and campfire/outdoors groups should just re-brand themselves as various types of character-building and skill-building clubs; BSA could tend to target more activities and skills boys would be interested in, while Girl Scouts could target the activities and skills girls would be interested in. Neither would discriminate, so [just stereotyping here:] tomboys who would be happier with boy-scouting could go that direction, and the less-"tough"/more-effeminate boys who would be happier with the Girl Scouts could go that way. (Again, I emphasize that those are *stereotypes*... I don't really believe the division would ideally be just like that! In fact, having boys and girls learn skills and traits traditionally associated with the opposite gender and breaking social gender role molds in the process is really neat imho.)
That being said, the chaperoning issue is still a problem, with the way our society handles gender privacy and bathroom issues (not that our system is necessarily bad, but it could probably use some improvement - see #1 for something I disagree with, and #2 for an amusing comic on that subject - I think having more unisex and family bathrooms would be preferable, with several private, individual bathrooms for every multi-person unisex one). Chaperoning could be handled more by the parents voting rather than by gender-grouping [how many intersex parents are there for the intersex children who self-identity as intersex rather than male or female? *grin*]. There are plenty of adults of both genders who treat all children with respect and would never dream of harming them, and these adults would make fine chaperones for any children, to the extent that those children and their parents are comfortable.
{:prepares self for flames:}
I've often found that I cannot bring myself to believe many things in the Bible, but neopaganism holds my interest. I also equate "God + Goddess" with the whole of the Universe (or David Lewis' multiverse) instead of believing in a supernatural God.
It works for me, and doesn't require me to believe in any "voodoo."
The second link only needs two bjt's (1 npn, 1 pnp) and 5x 10kOhm.
Even from the local radio shack, $8.99 for a small solderless breadboard, $6.99 for a 100' spool of solid 22awg wire, $2.99 for a 15-pack of 2n2222 npn's, $2.59 for a 15-pack of 2n3904 pnp's, $0.99 for a 5-pack of 1/8W 10kOhm@5%, and $1.99 for a female DB-9 crimp connector is only $24.54 (before any sales tax). If you can solder, you can save $7 by going with the 417-hole pre-etched PCB, and you can probably de-solder any NPN, PNP, and five 10k's from old busted electronics (dead CRT is a good example: fewer SMD's and more lead-ed/through-hole components; and for that matter, you can probably break off part of a PCB from a CRT, de-solder all the components, and use the traces already etched to save the cost of a PCB). If you have a few feet of solid 18-24AWG wire around the house, you can save $6.99; solid wire may be harder to find in small consumer electronics, but is still not hard to find in random broken appliances (and if you're soldering it, you can just use stranded wire from any random old cable or consumer device). For the DB-9, you can always chop in half any cable that plugged into a serial port (you'll need to figure which pin goes with which wire---use an ohmmeter, or if you don't have that, a voltmeter (many battery checkers are basically voltmeters) and a battery, or if you don't have that, improvise by using a flashlight with the battery cover opened (turn flashlight switch on, insert wire/pin into DB-9 hole being traced and connect to the open side of the batteries, and then try each of the wires in the cable to complete the electrical connection normally completed by the battery cover until it lights up)); it'll almost definitely have stranded wire inside, so for a solderless breadboard you'll have to use a piece of solid wire and solder them or, without solder, twist the ends together well, wrap tightly in electrical tape (duct tape can be substituted if you have no electrical tape) until of sufficient thickness, and screw into a wire cap (the kind used to connect two household internal power wires together) to keep pressure on the connection. You can forego the screw caps if you wrap very, very tightly with good tape and aren't worried about the connection holding forever.
Getting solid wire, sewing needles, or the points of safety pins to stick in the holes (not the big ones, but the small rectangular ones next to each big hole) of the OBDII connector usually works. If you don't have luck with that, you can re-bend some paper clips into a U-shape of appropriate width or use the curled end of a safety pin of appropriate size.
Really, any computer geek with patience can probably do this for zero cost ;) Even without a soldering iron, you can probably locate a section of PCB (again from CRT etc) with one NPN and one PNP BJT and without any surface-mounted components, remove other components by cutting the leads (keep in mind that longer leads might be snipped as close as possible to their component so as to create points for easy connection to wires) with wire cutters (or fingernail clippers, in a pinch), and cut unneeded traces carefully with an x-acto or razor blade (or by carefully sawing with a serrated kitchen knife, like a steak knife, in a pinch). The only part that you may have to dig around for is a cable with a female DB-9 connector at one end, and you may be able to get around that by squeezing the needed pins from the male DB-9 serial port between the insulating sheath and copper core of some wire by pushing the wire down onto the pin with small needle-nosed pliers (or tweezers in a pinch). Honestly, with a few hours and some old electronics that can be sacrificed, it's very jury-riggable, though like the parent poster states, you may need to pay a little more for decent housing and an actual OBDII plug.
http://www.elec-intro.com/obd-schematic schematic for ODBII to RS232. You can pick from a MAX232-based solution or an op-amp based approach. Use a solderless breadboard if you're not good at soldering or to test the circuit first to make sure it'll work for your car.
http://prj.perquin.com/obdii/ another ODBII to RS232 using just a few transistors.
For a slightly safer approach using optoisolators, try http://www.planetfall.com/cms/content/opendiag-obd-ii-schematics-pcb-layout
With freediag, you should be good to go.
What Dave said: "Open the pod bay doors, HAL."
What HAL heard: "Open the hot babe pornz, HAL."
HAL's speech recognition and morality programming* combined to give the famous reply, "I'm sorry, Dave. I'm afraid I can't do that." HAL knew certain things would have been too titillating to an all-ages film audience in 1968.
* Only for the film version. In the book version, it would have caused undue frustration to the reader, unable to see what Bowman was viewing. In that case, it was HAL's etiquette programming.
I'm leaving two free variables: what keep-the-beat task to use, and what syncopation/accentuation task to use. I'm expecting the drummer to be able to freely switch among many combinations on the fly, which is how I'm requiring it to be two tasks, and not just another learned merged-task. Of course, if you learn a particular combination of those two (e.g. for a particular song), then, yep, it becomes one task. Ask any drummer that sings and plays drums at the same time if he/she can sing the same part overtop of a different, arbitrary combination of keeping-the-beat and syncopation/accentuation, and you'll see him/her trying to focus on three tasks at once.
With practice, singing and drumming through a particular song will because (mostly) an isolated, single task---that's the point where nothing bizarre occurring onstage will throw the drummer off from singing or drumming, unless he/she is experimenting with a task combination that hasn't been yet learned as a single task (singing a different harmony part when another vocalist in the band is out sick, for example).
When you practice doing two tasks simultaneously, they become a new, single task. How do good drummers play syncopated beats? You learn a multitude of "keeping the beat" tasks involving many combinations of common patterns on the bass drum, hi-hat, and ride cymbal, then you learn a variety of syncopated beat tasks to play "overtop" of the other task. (You also have to learn strategies for performing these tasks at the same time, especially when you have to borrow a foot or hand from the keeping-the-beat task for an accentuated part and then un-borrow it; however, my point---namely, for a good drummer, many complex patterns involving multiple limbs, when practiced sufficiently, become simply "one task"---still stands.)
Oooh! I just had a *brilliant* idea!
Instead of protecting the driver by putting several feet of car engine between him and the front of the vehicle, why not put the driver out *right at the front*, in the position of vulnerability, and split up the engine into halves, sticking either half on the left and right side of the car? That way, the driver will surely be careful to look where he is going, but if someone runs the red light and T-bones him, he'll be okay.
Now, who wants to lend me some $ so I can file some patents?
I'm not sure about the wireless hacking from a laptop mentioned in TFS, but, as far as RF transmissions, these things can generate plenty of spread-spectrum modulation EMF when modulating the 240kHz signal carrier on wire.
There's a good discussion about eliminating ground loops so as to avoid broadcasting the signal as a source of interference at the Technical Library; I suppose one could always use an induction receiver to go the other direction, using a loop antenna. Obviously, modification of the above designs is needed for target frequency band. AM radio circuits might be a good place to start, too.
Actually, there are tons of good MW box loop designs that already go well below 240kHz; that page includes a calculator, and playing with some quick numbers suggests a 48cmX65cm frame [=56.5cm side length] for a 16-turn coil extending 21cm in length in parallel with four 470pF caps gives us resonance at 245kHz. Of course, with 20% tolerance ceramic discs, you may want to replace one of the 470's with a 4-40pF variable cap in parallel with anywhere from a 150pF to a 39pF paralleled with a 560pF, depending on how low or high the 470's are measuring.
[Disclaimer: I am an RF amateur.]
Computer memory, in an abstract sense, tends to be looked at in a hierarchical way:
* Registers
* Caches
* RAM
* Secondary storage (swap)
A filesystem is a datastructure, arguably just nominally imposed on a dedicated swap-space of sorts.
When you buy a gig of RAM, you expect 2^30 bytes, not 10^9 bytes. I've never understood why HD think that their "secondary storage" does not belong under the paradigm of "computer memory" when talking about sizing, despite the fact that all modern OS's use swap space, and filesystems are all data structures whose constituents tend to fall on word boundaries.
Yeah, this is really old stuff. I think I saw malware attacks using this at least as early as 1998. I had not done much sockets programming at that point, but once I saw it, I immediately started studying the RFCs, and was like, "hey, neat!" :-P
I think every single IP-address-parsing routine and IP-address-matching-regex I've written since then has always been designed to handle this and tested against every form of it. I really don't understand why there could be any software out there at this point that would have any problems, but I suppose it is arrogant to assume every other programmer has my mindset.
Oh well, I guess that means I can use it as a selling point for my own code, then
Knows a lot? Are you sure? ;)
It has a lot more to do with the pattern of resonance from vocal tract length than base pitch, which is possibly why pitch-shifting the whole spectrum often doesn't seem to change the perceived gender of a voice very well.
Playing with resonance through tongue and larynx positioning and hearing the changes producable in timbre without changing the fundamental pitch is quite fascinating to me, esp. as a clasically-trained singer [among other reasons].
Lynn Conway, one of the key engineers behind VLSI technology, is a transwoman who feminized her voice through careful practice and self-study, according to the above WP link.
Yeah, but the task has to seem /ostensibly/ completable in 60 seconds, or else nobody's heart is really going to be in it for the cool million. :-D
--
Actually, they should just give the techs a stack of perfboard, some spools of cable, a book of schematics, a huge bucket of NAND and XOR chips, a box of tiny circular ferrite cores, and some wire-wrapping tools. You get a bonus if you get the Unibus timings right on the first try.
And you didn't write a perl script to download e-mail from the web interface? Shame on you! Your slashdot license is revoked! ;)
Exactly. I enjoy how many sites block the user-agent string for wget. This is easily remedied with tagging --user-agent "Mozilla/4.0 (compatible; definitely-not-yoo-git)". ;)
Since wget politely will obey robots.txt, though, to do recursive downloading, you really ought to remember to change this compile-time "option" by carefully commenting out the appropriate code. (What?! You're installing a binary you didn't compile yourself?!)
I've always enjoyed randomizing identification information. My /etc/issue.net (in the days of telnet) used to be fed by a daemon that would print login banners from ULTRIX, VMS, SunOS4, BSD 4.3, CRAY Unicos, etc. The automated script kiddie banner-scanners of the day used to have lots of fun with that, let me tell ya. /proc or appropriate kcalls for your OS and put them in appropriate static vars. Replace the call to print the banner on connect with something like: alloc larger temp buffer (if fail, bail with an error) and do substitutitions up to the buffer length, ensure NUL-term'd, tell connection-handler code to write that buf, and plan to dealloc when the connection-handler code no longer expects to need to push any more text from that buffer to that accepted sock (the tricky part, iirc from the opensshd code!))
(sshd's Banner option isn't as flexible, just static text... it's disappointing, because the various gettys always had @ and \ options. I did used to modify my getties to extend those options though, so, I've played with extending my sshd for an field-substituting banner message. For the record, if you're curious about extending OpenSSHd, since it loads the banner file into a static text area at startup: You can have a config-file-rehash or SIGHUP-style routine reload the bannerfile. If you want to do load-average numbers in your banner, you can have the daemon wake up every 60 secs and get that info from
Yeah... this might be some sort of miscommunication. Mickey Mouse's lawyers might not have really understood the implications of a BSD license. I wouldn't be surprised if the Ptex site disappears, nothing further ever arrives along the lines of open-source code, and Disney's lawyers attempt to find loopholes to get mirrors of the Ptex source taken down.
Disney has always held tight controls over their IP, and while the BSD license gives them a lot of control over what *they* do with Ptex, it gives the community a lot of control over what the *community* does with Ptex, provided any forking coders properly acknowledge the original authors and abide by the set (albeit minimal) of constraints provided by the BSD license.
[Obligatory IANAL, so any groklaw aficianados, feel free to correct, clarify, or serve me with a court-order comprising one Clue Stick (TM).]
Man, I was always trying to figure out why Maxo-Texas's vacation time exhibited characteristics of "funny math" the first year he was there!
The research out there on neural regrowth in adults is very interesting, because, yes, the classical empirical evidence is that damaged neurons go into apoptosis and are cleaned up by glial cells.
My girlfriend has atypical trigeminal neuralgia and underwent an unsuccessful microvascular decompression on the brainstem (wherein a venous structure was deconstructed and cauterized, a venule was padded with teflon, and a minor arteriole was resectioned and cauterized), followed by a more-successful partial sensory rhizotomy to resection the nerve in Meckel's cave via a 60% cut that ideally would hit most of the group-C fibers. The outcome of the rhizotomy is interesting, because it seemed to take care of the mandibular nerve pain while leading to a very odd outcome. In the vast, vast majority of partial sensory rhizotomies on cranial nerves (meaning more-or-less the ~99% who do not have the horrid-sounding outcome known as anaesthesia dolorosa), the loss of sensation eventually diminishes, as the nerve undergoes restructuring. There seems to be very little information in popular medical literature on the restructuring process, and as I don't have access to any specialized journals (for neurology, neurosurgery, etc.), I cannot find much information; however, it seems to perhaps involve rapid branching of the dendrites in parallel with apoptosis and glial clean-up of damaged neurons. In >90% of rhizotomies, there is little discomfort during this process. My girlfriend is one of the "lucky few" (and by that I mean that her neurosurgeons, Dr. Sekula and Dr. Jannetta, who himself pioneered microvascular decompression and other techniques for trigeminal neuralgia of both types and various types of hemifacial spasm, at Allegheny General Hospital, said they could not even remember the last time they had seen the effect she is experiencing) to have severe discomfort during the restructuring process. This discomfort is a dysthesia characterized by intense sensations of all types from the cranial nerve. She is experiencing sensations of pressure, nociception, touch, and proprioception in all branches of the trigeminal nerve, meaning not only the major three branches (ophthalmic, maxillary, and mandibular), but the minor branches out of Meckel's cave as well. In addition to that, she is having branching across into adjacent cranial nerves. These sensations range from moderately intense to maximally intense (meaning she is experiencing at times the same sensations someone would have if their skull was being crushed to pulp, or face was being cut deeply open in many places, etc.), but at least they can be controlled somewhat by extremely high levels of antiseizure medication. Between the sensations and medication, though, she is effectively completely disabled while the nerve undergoes this type of healing. The good news is that her neurosurgeons have never seen, either themselves or in any journals, a case of this that does not resolve when the restructuring reaches its end-stage, which occurs after six to twelve months. The intermediate time, though, is Hell for her. I would love to see more research done on this, as I would be curious to see if various signalling mechanisms are not genetically nominal in the <10% of cranial nerve rhizotomy patients who have this type of post-procedural effect.
Please, let's continue the research on SOCS3 here, and the other research being done out there on the various other known signalling mechanisms.
Oh hell, just register [add-accent-to-previous-letter]bankofamerica.com. There are tons of ways to abuse unicode, as many security papers have already discussed.
On the hardware locks, I couldn't agree more.
Hardware checks need to be in place, even if that makes more operating training required to recover from common hardware fault conditions.
For any dose above normal, two separate keys should have to be turned, separated in time by 30 minutes (so if a hospital was stupid enough to give the same person both keys, they have a half hour to think). Any dosage above normal should require being entered three times.
People can sleepwalk through their job. If they're doing something potentially dangerous, it's not unreasonable to set up their job so that their environment wakes them up before they make a possible serious mistake.
The problem is, if myspace admits "oops, we screwed up, we'll fix it," they mean they'll fix it for the squeaky wheel that complained, not in general. We won't see any reform of policies from this. It'll take a LOT more squeaky wheels for the ideal type of change to occur... it's just not profitable otherwise.
Agreed that the GP is using faulty logic. However, "Even if it's not true causing pollution is not good" is something worth studying further.
Oceans fix CO2 and plants metabolize CO2 to O2 (well-known facts). CO2 is a greenhouse gas of sorts (known fact). Humans pump out a not-insignificant amount of CO2 through industrial processes (known fact). Whether we're messing up the climate or not is something we can never really prove, either way; rather, it's a question of whether investing the money in improving industrial processes to be more efficient in their recycling of CO2 production. I think the whole climate change propaganda is missing the point on this.
"We have Java, as well as Python and various other languages on Linux for the niche Mono wants to fill."
I like to see open software offer a compatible option for every closed system. This may in many ways be somewhat futile as it's forever chasing something that can never be realized, but that's the flip-side of the point: to keep closed systems on their toes. If there's an open solution for *everything*, even for closed problems, nobody can argue that open software is incapable of helping with closed system X Y or Z.
("Utilize" has a more specific meaning than "use". "Use" means you're just working with something, for better or worse; "utilize" means you're making practical or profitable use of something. Arguably, you could say that any good teacher-student relationship implies that any skill a student uses for the goals of the course is put to *good* use, so "utilize" would be unnecessary complexity; but, maybe the submitter was trying to draw attention to the idea that this wasn't simply a read-stories-for-fun class. True, the usage is a little redundant, still, as using a skill or a strategy implies putting it to good use, unless the usage is implicitly or explicitly stated as bad. I realize "utilize" is drastically overused. Sorry if I'm giving the submitter the benefit of the doubt, but, hey... if you get to nitpick, I get to nitpick, too!)
I've seen some posts suggesting particular authors or stories, and an excellent post suggesting that maybe analyzing the classification of the material would offer more insight and useful long-term experience.
On the first item, please find a couple good short stories by Asimov; he shouldn't be overlooked. On the second item, a detailed literary analysis could encapsulate several goals, and could be done over the length of the course in short segments.
One of my high school literature teachers made us write a literary analysis of a novel with many, many short segments (some sharing no overlap). I found that this gave me a lot of insight into the work of fiction I chose (Philip K. Dick's 'A Scanner Darkly'), in terms of both extrinsic nature of my perception and the deconstruction of the novel's writing, and aspects of the story-world both internal and external to the words on the pages.
For the literary analysis, maybe the students should be prepped within the first few days for their project, and being given the suggestion of thinking carefully about how the project would pan out for several books of their choosing. After a week's thought, they could narrow the books down to ones that would be good to analyze (not necessarily their all-time-favorites, make that clear), and you could review the books and recommend which one of their final groups of choices seemed the best to analyze. This way, the student doesn't get stuck with a crappy (though perhaps still fun) fictional work when trying to do analysis.
To discourage putting things off to the last minute, the project would not need to be a term paper but rather just a coherent study of the book, done in sections. Give the students a few weeks to read the books carefully, after familiarizing them with the types of things they'll need to be watching for. Then, the analysis can be done in stages, presenting the goals of each stage in detail after the last stage has been turned in.
You'd want to avoid long works, since they may need to re-read large parts of the book for each stage. Each stage can also include a paragraph on how that part of the analysis relates to the theme of the course in terms of the book and in terms of the type of analysis itself.
Doing a detailed literary analysis in high school changed the way I read books forever. I have much more appreciation for well-written literature now.