actually, based on the (little) i know about this protocol, i believe it could be easily spoofed. The originator could make it look like 127.0.0.1 if he wanted to.
Your father doesn't know what he's talking about. Power quality is a MAJOR issue. Any place with large amounts of inductive loads (ie fluorescent lights, motors, etc) can easily triple their electrical bill by not having a good power factor. It is standard practice for electrical companies to charge extra if your power factor is bad as well. What he may be referring to is heaters. A heater is not an inductive load, so it will already have a power factor close to unity. However, in a large building with lots of motors/fans/air conditioning, power factor is a very important consideration. And if you get into an industrial setting, you would have to be completely insane not to care about power quality.
I have been using a setup similar to this for quite some time, only mine is based on fvwm. I find fvwm works _very_ well because of its high amount of configurability. Most people don't realize the power that fvwm has. You can pretty much program in whatever behavior you want.
My window borders are 1 pixel wide, grey for inactive, red for active. I have 4 virtual screens which I switch between with either the keyboard or the mouse (edge flip resistance is toggled between 0 and infinity with a keystroke). Window manager commands are all bound to alt or ctrl + mouse buttons. For example, alt+left mouse button moves a window, alt+right resizes. Similar things go for maximize (vert, horiz, both), iconify, window list, etc.
Why do I like it this way you ask?
-low overhead, fvwm is stinkin' fast!
-efficient, everything can be done without having to go thru menus or fumble for shortcut keys, just one hand on mouse, one on keyb. (of course you can use just keyd too, but mouse is nicer for moving windows etc)
-screen space, 1 pixel borders and no menus/bars/etc save TONS of space. I have tried no borders at all, but that gets pretty confusing!
-looks nice, it does actually look cool. nice and efficient looking.
I haven't tried the WM refered to in the article, but I doubt it's as configurable as fvwm. Might be worth checking out if the fvwm config file scares you:)
Actually, 10 G isn't as crazy as you think. Think how much time the actual acceleration occurs for. Another way to look at it is impulse. I=FT (Impulse = force * time). Also known as change in momentum. The impulse of sitting in a chair is very small. The acceleration is quite large (velocity goes from some value to zero in a short period of time). You could say there are 2 limits of acceleration the body can take. 1 short period, 1 long period. Long period would be where you see things like blacking out etc. Short period is the kind of thing you see in car crashes etc. The body can take a lot more if its a very brief event.
I'm sorry to say it, but because of 9/11 I will not be visiting the US again any time soon. I recently went on a weekend camping trip with a busload of people from my church. At the boarder, we had to leave 5 people behind (after much hassle for the rest of us as well). 3 of these brought it on themselves by not having their ID. The other 2 were students from Korea. I was almost not allowed thru because I don't have a passport and my birth certificate was at my parents, 5 hours out of the way. With all the border hassle, there is no way we are doing that trip again.
Ummmm......the linux kernel _IS_ modular if you compile everything as modules. What do you think many distributions like redhat or mandrake are doing? You can quite successfully use their percompiled kernels on almost any system.
The whole point of kernel configuration is that you can actually not compile what you don't need and you can make a kernel perfectly suited to your system. Without modules if you don't have a reason for them. If you never change anything, why would you need to have module supporting sitting around in your kernel?
Agreed, but you can still have your analysis take this into account. You just need to take the human factor into account. Some sort of neural net or similar learning system could be used.
As others have pointed out, these "calculations" are completely meaningless and wrong. It doesn't take much current to cause damage. Another thing to note is that current through your body is not the only danger involved with tesla coils. Hearing protection is a must for large coils. Good fresh air flow is needed. Eye damage can result from the watching the arcs on larger coils. Another intersting thing is that the human body is not equally vulnerable to all frequencies (and I don't just mean skin effect). Low frequency AC (60Hz is actually quite bad) is worse for you than DC. High frequencies aren't as bad until you get sufficiently high, and there they are worse than low frequencies. So while skin effect may offer you some protection, if you get that high frequency AC going through heart/spine/brain/etc, it will most definately harm you.
which is usually not much more than the human hearing range. And passing really high frequencies to speakers tends to make them rip themselves apart. Plus if you are using a soundcard, that is a limitation already. It will most likely have a filter on it. Plus you can only get so high of a frequency with 48Khz sampling. I'm not sure what the typical limitation of a PC speaker circuit is, but they might be capable of going higher. Of course a piezo buzzer would be the proper way to produce high frequency tones. You should be able to connect one to the PC speaker output easily enough.
What we need is a better analysis of what exactly the weak points and strong points of these compression algorithms are. Perhaps some kind of a test involving compression noise with many different patterns and such. A test could be designed using noise and sine waves in different ways that would test all aspects of the compression. Then do an FFT on the result and compare to the original. This would yield results that are much more useful to the developers, rather than just saying which is best.
Skipping is not a nuances, thats the DJ screwing up. The nuances I'm talking about are what creates the actual sound when you are, say, scratching. A large part of what you hear is not the music itself, but artifacts. Especially at slow speeds, vinyl sounds VERY different from other methods. To remove that aspect is like trying to simulate an orchestra using sampled midi. Just doesn't cut the mustard.
Is it just me or are break, continue and goto all considered to be evil programming practices (with the exception of break in a switch structure)? And switch isn't at all necessary if you have if and else (you can make a switch structure out of those). Lack of pointers and integers may or may not be a problem, I don't really know much about the language.
are completely stupid. Yes the MP3 player has its place, but it will never replace vinyl for one simple reason. Turntables are an instrument. Sure mp3's are nice if all you are doing is just playing music, but in my world that is not DJ'ing. If you ever watch a DMC competition, you will understand precisely what I mean. The only way I can possible see digital replacing vinyl is in the digital turntable systems we see emerging now, but those are still VERY far from taking over. Until all the nuances of vinyl can be simulated very well, these products are neat, but not a replacement for the good 'ol turntable.
Now that said, I DO firmly believe that digital has a big place with ["true"] DJ's. The sampling, effects, and synthesizing possibilities are immense. Especially of interest are computer instruments. The Gameboy teddy bear from a while back comes to mind as simple example. Digital technology certainly can be an amazing in the hands of a musician, but its strength is not in replacing vinyl but rather in creating whole new possibilities. Some of the most amazing music emerges when a combination of digital and analog instruments are used. Each has its strengths.
No, what they are saying is that their random number generator is very random. If you have a perfectly randomly generated bell curve set of numbers, it makes it easier to reconstruct the original data. Think of an audio signal for example. If you have a sine wave (your data) mixed with white noise (perfectly random), you can quite easily pick out the sine wave. Its the one frequency that is louder than all the rest. However, if instead of white noise you have noise that is not perfectly random, you will not see a clear sine wave, but several different frequencies.
An IDS is not a replacement for these steps, it is IN ADDITION to them. An IDS is not supposed to secure your network, it is supposed to let you know when something unusual is going on. If something odd happens on my network, I want to know about it. Don't you?
i never said they did consume more power.
actually, based on the (little) i know about this protocol, i believe it could be easily spoofed. The originator could make it look like 127.0.0.1 if he wanted to.
who says the sender is going to listen for these replies?
Your father doesn't know what he's talking about. Power quality is a MAJOR issue. Any place with large amounts of inductive loads (ie fluorescent lights, motors, etc) can easily triple their electrical bill by not having a good power factor. It is standard practice for electrical companies to charge extra if your power factor is bad as well. What he may be referring to is heaters. A heater is not an inductive load, so it will already have a power factor close to unity. However, in a large building with lots of motors/fans/air conditioning, power factor is a very important consideration. And if you get into an industrial setting, you would have to be completely insane not to care about power quality.
I have been using a setup similar to this for quite some time, only mine is based on fvwm. I find fvwm works _very_ well because of its high amount of configurability. Most people don't realize the power that fvwm has. You can pretty much program in whatever behavior you want.
:)
My window borders are 1 pixel wide, grey for inactive, red for active. I have 4 virtual screens which I switch between with either the keyboard or the mouse (edge flip resistance is toggled between 0 and infinity with a keystroke). Window manager commands are all bound to alt or ctrl + mouse buttons. For example, alt+left mouse button moves a window, alt+right resizes. Similar things go for maximize (vert, horiz, both), iconify, window list, etc.
Why do I like it this way you ask?
-low overhead, fvwm is stinkin' fast!
-efficient, everything can be done without having to go thru menus or fumble for shortcut keys, just one hand on mouse, one on keyb. (of course you can use just keyd too, but mouse is nicer for moving windows etc)
-screen space, 1 pixel borders and no menus/bars/etc save TONS of space. I have tried no borders at all, but that gets pretty confusing!
-looks nice, it does actually look cool. nice and efficient looking.
I haven't tried the WM refered to in the article, but I doubt it's as configurable as fvwm. Might be worth checking out if the fvwm config file scares you
just my 00000010 cents
_ruby_ lasers? somehow i don't think so.
Actually, 10 G isn't as crazy as you think. Think how much time the actual acceleration occurs for. Another way to look at it is impulse. I=FT (Impulse = force * time). Also known as change in momentum. The impulse of sitting in a chair is very small. The acceleration is quite large (velocity goes from some value to zero in a short period of time). You could say there are 2 limits of acceleration the body can take. 1 short period, 1 long period. Long period would be where you see things like blacking out etc. Short period is the kind of thing you see in car crashes etc. The body can take a lot more if its a very brief event.
I'm sorry to say it, but because of 9/11 I will not be visiting the US again any time soon. I recently went on a weekend camping trip with a busload of people from my church. At the boarder, we had to leave 5 people behind (after much hassle for the rest of us as well). 3 of these brought it on themselves by not having their ID. The other 2 were students from Korea. I was almost not allowed thru because I don't have a passport and my birth certificate was at my parents, 5 hours out of the way. With all the border hassle, there is no way we are doing that trip again.
Ummmm......the linux kernel _IS_ modular if you compile everything as modules. What do you think many distributions like redhat or mandrake are doing? You can quite successfully use their percompiled kernels on almost any system.
The whole point of kernel configuration is that you can actually not compile what you don't need and you can make a kernel perfectly suited to your system. Without modules if you don't have a reason for them. If you never change anything, why would you need to have module supporting sitting around in your kernel?
ogg can do an arbitrary number of channels.
I bet it would run faster still on fvwm or twm or no window manager at all.
Agreed, but you can still have your analysis take this into account. You just need to take the human factor into account. Some sort of neural net or similar learning system could be used.
As others have pointed out, these "calculations" are completely meaningless and wrong. It doesn't take much current to cause damage. Another thing to note is that current through your body is not the only danger involved with tesla coils. Hearing protection is a must for large coils. Good fresh air flow is needed. Eye damage can result from the watching the arcs on larger coils. Another intersting thing is that the human body is not equally vulnerable to all frequencies (and I don't just mean skin effect). Low frequency AC (60Hz is actually quite bad) is worse for you than DC. High frequencies aren't as bad until you get sufficiently high, and there they are worse than low frequencies. So while skin effect may offer you some protection, if you get that high frequency AC going through heart/spine/brain/etc, it will most definately harm you.
It's available along with other skins on their webpage (xine.sf.net). I take it you hate the new one as much as I do :)
So you've checked every single one have you?
New Hope of course......who doesn't know that?
which is usually not much more than the human hearing range. And passing really high frequencies to speakers tends to make them rip themselves apart. Plus if you are using a soundcard, that is a limitation already. It will most likely have a filter on it. Plus you can only get so high of a frequency with 48Khz sampling. I'm not sure what the typical limitation of a PC speaker circuit is, but they might be capable of going higher. Of course a piezo buzzer would be the proper way to produce high frequency tones. You should be able to connect one to the PC speaker output easily enough.
What we need is a better analysis of what exactly the weak points and strong points of these compression algorithms are. Perhaps some kind of a test involving compression noise with many different patterns and such. A test could be designed using noise and sine waves in different ways that would test all aspects of the compression. Then do an FFT on the result and compare to the original. This would yield results that are much more useful to the developers, rather than just saying which is best.
Skipping is not a nuances, thats the DJ screwing up. The nuances I'm talking about are what creates the actual sound when you are, say, scratching. A large part of what you hear is not the music itself, but artifacts. Especially at slow speeds, vinyl sounds VERY different from other methods. To remove that aspect is like trying to simulate an orchestra using sampled midi. Just doesn't cut the mustard.
Is it just me or are break, continue and goto all considered to be evil programming practices (with the exception of break in a switch structure)? And switch isn't at all necessary if you have if and else (you can make a switch structure out of those). Lack of pointers and integers may or may not be a problem, I don't really know much about the language.
are completely stupid. Yes the MP3 player has its place, but it will never replace vinyl for one simple reason. Turntables are an instrument. Sure mp3's are nice if all you are doing is just playing music, but in my world that is not DJ'ing. If you ever watch a DMC competition, you will understand precisely what I mean. The only way I can possible see digital replacing vinyl is in the digital turntable systems we see emerging now, but those are still VERY far from taking over. Until all the nuances of vinyl can be simulated very well, these products are neat, but not a replacement for the good 'ol turntable.
Now that said, I DO firmly believe that digital has a big place with ["true"] DJ's. The sampling, effects, and synthesizing possibilities are immense. Especially of interest are computer instruments. The Gameboy teddy bear from a while back comes to mind as simple example. Digital technology certainly can be an amazing in the hands of a musician, but its strength is not in replacing vinyl but rather in creating whole new possibilities. Some of the most amazing music emerges when a combination of digital and analog instruments are used. Each has its strengths.
My 00000010 cents.
No, what they are saying is that their random number generator is very random. If you have a perfectly randomly generated bell curve set of numbers, it makes it easier to reconstruct the original data. Think of an audio signal for example. If you have a sine wave (your data) mixed with white noise (perfectly random), you can quite easily pick out the sine wave. Its the one frequency that is louder than all the rest. However, if instead of white noise you have noise that is not perfectly random, you will not see a clear sine wave, but several different frequencies.
And how do you formally describe a zipper or velcro? A method for fastening clothing where...
I do see what you are getting at though.
An IDS is not a replacement for these steps, it is IN ADDITION to them. An IDS is not supposed to secure your network, it is supposed to let you know when something unusual is going on. If something odd happens on my network, I want to know about it. Don't you?
What do I have to do around here to get a few frickin' sharks with lasers on their heads, huh?