Lots of the stuff in the step-by-step factory manuals are unnecessary. Sometimes I swear they put them in to make it look more difficult to non-mechanics. Case in point: Two weeeks ago I changed the timing belt on my VW Passat TD. The service manual says to lock the cam and injection pump (makes sense, we don't want to mess with the timing when we take the belt off) and then to adjust the cam into position within a hundredth of a degree. Excuse me? The smallest amount it CAN be wrong is by a cog and that's several degrees of turn on the cam. It's simply not possible to have the timing off by anything close to the amount of precison the manual required so I happily didn't give a shit, changed the belt and it works fine.
It was probably perfectly possible to change the sparks without touching the rear light cluster on his bike, but you'd have to pull the tank off. I do on mine and we share the same engine, if not body work.
1. There's no such investigation underway in my country. (Hint: I'm not in the UK, check my mail address country code for a clue)
2. I don't get caught when I speed simply because the cameras only shoot pictures from the front and my bike's license plate is at the rear.:-P
3. The correct spelling is "erected". You need to stop basing your spelling on reading Spam.
There's a very good reason why there are a lot of tools that construct documentation from comments: it's usually the most practical way of getting documentation out of the developers.
There are two more ways: The credible threat of an unseen but oft hinted at baseball bat; and the prospect of being sat upon by the 130kg heavy tech writer. I have used both with great success.:-)
Most developers seem to be genetically selected against writing documentation so there needs to be an outside force squeezing it out of them. An extremely thinly veiled threat of physical force works for me, especially when they think it's in jest but can't be really, really sure I won't sit on them one day. After extracting the data, a good tech writer can turn it into usable information by installing the software, using the program and - as an added bonus - give valuable feedback to the developers on usability issues. This feedback loop is largely missing in FOSS, I'm sad to say.
Hey, I'm sure there are people looking for auto-translated Japanese gay porn! Then again, they may wind up with a collection of the good doctor's short stories by mistake...:-D
Sure, there are good uses for copyright, but moderating Slashdot posts is not one of them.
What's your opinion on karma-whoring trolls, who copy/paste someone else's posts hoping to get modded-up?
I think they should be mass-sued for copyright infringement, found guilty and thrown in jail.
Oh, or maybe they should simply be down-modded and hailed with derisive laughter?
Hm. A self-regulating, dynamic and free post market economy or a government-imposed regulatory system that's impossible to enforce? Decisions, decisions...
No copyright is asserted for NASA photographs. If a recognizable person appears in a photo, use for commercial purposes may infringe a right of privacy or publicity. Photos may not be used to state or imply the endorsement by NASA or by any NASA employee of a commercial product, process or service, or used in any other manner that might mislead. Accordingly, it is requested that if a NASA photograph is used in advertising and other commercial promotion, layout and copy be submitted to NASA prior to release.
NASA photos reproduced from this archive should include photo credit to "NASA" or "National Aeronautics and Space Administration" and should include scanning credit to Kipp Teague or other individuals or agencies as noted.
First thing I thought about when I read the story. That sound always made my skin tingle a little. The attention to that little detail. The intro song is great too, BTW.
We need to curb this kind of behaviour early and with all means necessary. If we let him get away with it, soon they'll have you pay them money to go to work, 25 hours a day.
Back when I was doing support, I needed to get in touch with the developer to check a thing. It was in the evening and he'd had some wine (more than some, probably) when he answered the phone. It was great fun, especially as he recalled an exact software setting he'd coded six months earlier. While half drunk (the recalling, not the coding). He was a bit of a genius. I kinda miss him.:-)
He wasn't talking about an ISDN B-channel or a BRI?
A typical BRI (Basic Rate Interface) ISDN setup uses two B-channels (Bearer) and one D-channel (Data). The B-channels are 64 kbps each and IIRC the D-channel is 16kbps. It is possible to merge the B-channels to get one 128 kbps link and it's also possible to use the signaling D-channel to transfer data, but the exact nature of this latter feat escapes me at the moment. A Primary Rate Interface consists of 23 bundled B-channels which can be used as separate voice lines or for data communications. It's mostly used for small- and medium-sized corporations to hook up their PBX as well as datacom to a main trunk. It is often implemented as a T1, but with some added flexibility.
Well, let me just hack into SlashCode (lokkie here, CmdrTacos password is 'pencil', same as BillG's), edit a few lines right about here... And there you go. All done.
'course, you still can't mod and post in the same discussion, so you just have to wait before you can use it. But thanks anyway.;-)
We learned our "admin" skills playing around with C64's.
So did I. But I contend that most people can differentiate between what was basically a multifunction games console with a command line and a networked computer (yes, I know that there are network cards for the C=64 now). Especially people responsible for designing and implementing security solutions into operating systems. Please remember that this discussion did not center around end-users, but rather how operating systems are designed - with security in mind or not. I would sincerely hope that no one coding a modern OS kernel has retained those bad habits you speak of. The grumpy old gits (like me) got an education at a university or similar institution of learning where we were exposed to multi-user systems from the onset and the younger ones has grown up with the Internet, learning to ph34r remote exploits.
The ones that grew up with C= 64s, managed to avoid educational facilities, ignored learning from the Internet these last 20 years and still go on to writing operating system code today should thankfully be very, very few.
Why are we pushing research/business paradigms into the HOME computing experience?
Because it is very valuable for my gf to be able to have her own desktop, her own browser bookmarks and her own e-mail login clearly separated from mine. This may come as a shock to many Slashdotters, but most homes do not consist of a male geek in the basement and a set of clueless parents above; but rather a man, woman, 2.4 children and/or a cat/dog/pet halibut named Eric. All of them want their own login.
I suppose it's cheaper to develop ONE OS rather than two, but it's still annoying.
Tell that to Microsoft. They have separated their Windows line ever since Windows 95 and NT 3.5 AS. 98/NT4, ME/2000 Pro, XP Home/Professional and now that First Smoke Reduced Edition. Not to mention the embedded and pocket versions and all the different servers; Advanced Server, Server, DataCenter Edition, Terminal Server Edition, Enterprise Edition Server and Internet Virus Server with Extra Buttfuck Edition... Hell, there are almost more Windows versions than Linux distros, and those a just a few hundred fewer than all the grains of sand in the Sahara desert.
OK, I made up that last server as I went along, but you gotta admit that it can't be very far off.;-)
Slashdot Mirror
Oh, you got it alright. You post, therefore you are.
It was probably perfectly possible to change the sparks without touching the rear light cluster on his bike, but you'd have to pull the tank off. I do on mine and we share the same engine, if not body work.
1. There's no such investigation underway in my country. (Hint: I'm not in the UK, check my mail address country code for a clue) :-P
2. I don't get caught when I speed simply because the cameras only shoot pictures from the front and my bike's license plate is at the rear.
3. The correct spelling is "erected". You need to stop basing your spelling on reading Spam.
Some of them are. But most of them are placed so they can generate maximum revenue, just as the regular speed traps are.
Check if there's a cable or something in the fan. Or just rip the fan out. That's gonna hurt it less than being smothered with a pillow.
There are two more ways: The credible threat of an unseen but oft hinted at baseball bat; and the prospect of being sat upon by the 130kg heavy tech writer. I have used both with great success. :-)
Most developers seem to be genetically selected against writing documentation so there needs to be an outside force squeezing it out of them. An extremely thinly veiled threat of physical force works for me, especially when they think it's in jest but can't be really, really sure I won't sit on them one day. After extracting the data, a good tech writer can turn it into usable information by installing the software, using the program and - as an added bonus - give valuable feedback to the developers on usability issues. This feedback loop is largely missing in FOSS, I'm sad to say.
So, who'd want to be Preem Poster? ;-)
Sure, there are good uses for copyright, but moderating Slashdot posts is not one of them.
I think they should be mass-sued for copyright infringement, found guilty and thrown in jail.
Oh, or maybe they should simply be down-modded and hailed with derisive laughter?
Hm. A self-regulating, dynamic and free post market economy or a government-imposed regulatory system that's impossible to enforce? Decisions, decisions...
First thing I thought about when I read the story. That sound always made my skin tingle a little. The attention to that little detail. The intro song is great too, BTW.
Nope and no. It was in Sweden, actually.
We need to curb this kind of behaviour early and with all means necessary. If we let him get away with it, soon they'll have you pay them money to go to work, 25 hours a day.
Dance on his grave and sing Hallelujah!
Back when I was doing support, I needed to get in touch with the developer to check a thing. It was in the evening and he'd had some wine (more than some, probably) when he answered the phone. It was great fun, especially as he recalled an exact software setting he'd coded six months earlier. While half drunk (the recalling, not the coding). He was a bit of a genius. I kinda miss him. :-)
His wife called, she wants her panties back.
A typical BRI (Basic Rate Interface) ISDN setup uses two B-channels (Bearer) and one D-channel (Data). The B-channels are 64 kbps each and IIRC the D-channel is 16kbps. It is possible to merge the B-channels to get one 128 kbps link and it's also possible to use the signaling D-channel to transfer data, but the exact nature of this latter feat escapes me at the moment. A Primary Rate Interface consists of 23 bundled B-channels which can be used as separate voice lines or for data communications. It's mostly used for small- and medium-sized corporations to hook up their PBX as well as datacom to a main trunk. It is often implemented as a T1, but with some added flexibility.
Oh, he knows full well which side of his bread has all the butter on it and who does the buttering. Mmmm, butter...
And then my dog ate it.
"Call the US Naval Observatory for the exact time"
There are many missing mod options. Maybe someone should write a book? "Slashdot: The Missing Mod Options". I'll talk to O'Reilly about that.
Well, I did claim that B was true. But I agree, I should have gotten a few +1 Informative and a -1 Fucking Obvious instead. ;-)
Guybrush Threepwood.
Exactly. :-D
Nah, I'm cool now. But thanks for your concern. :-)
'course, you still can't mod and post in the same discussion, so you just have to wait before you can use it. But thanks anyway. ;-)
So did I. But I contend that most people can differentiate between what was basically a multifunction games console with a command line and a networked computer (yes, I know that there are network cards for the C=64 now). Especially people responsible for designing and implementing security solutions into operating systems. Please remember that this discussion did not center around end-users, but rather how operating systems are designed - with security in mind or not. I would sincerely hope that no one coding a modern OS kernel has retained those bad habits you speak of. The grumpy old gits (like me) got an education at a university or similar institution of learning where we were exposed to multi-user systems from the onset and the younger ones has grown up with the Internet, learning to ph34r remote exploits.
The ones that grew up with C= 64s, managed to avoid educational facilities, ignored learning from the Internet these last 20 years and still go on to writing operating system code today should thankfully be very, very few.
Why are we pushing research/business paradigms into the HOME computing experience?
Because it is very valuable for my gf to be able to have her own desktop, her own browser bookmarks and her own e-mail login clearly separated from mine. This may come as a shock to many Slashdotters, but most homes do not consist of a male geek in the basement and a set of clueless parents above; but rather a man, woman, 2.4 children and/or a cat/dog/pet halibut named Eric. All of them want their own login.
I suppose it's cheaper to develop ONE OS rather than two, but it's still annoying.
Tell that to Microsoft. They have separated their Windows line ever since Windows 95 and NT 3.5 AS. 98/NT4, ME/2000 Pro, XP Home/Professional and now that First Smoke Reduced Edition. Not to mention the embedded and pocket versions and all the different servers; Advanced Server, Server, DataCenter Edition, Terminal Server Edition, Enterprise Edition Server and Internet Virus Server with Extra Buttfuck Edition... Hell, there are almost more Windows versions than Linux distros, and those a just a few hundred fewer than all the grains of sand in the Sahara desert.
OK, I made up that last server as I went along, but you gotta admit that it can't be very far off. ;-)