> If you allow ssh access from the wide internet...
Why would you do that?
My usage case:
SSH in, tunnel to localhost:80 for web admin.
Would it be better to leave the HTTP/HTTPS world-exposed? Probably not.
Note that with a strong root password and usage of a non-standard port will help keep the bots away. Even better if you disable password authentication for SSH and use a key instead.
Now, what I miss is the reset button on the front of the machine. What's up with that?
There's an easy hack for that. Tie the PWR_OK line (it's one of the wires in the ATX connector) to a momentary switch (that opens on push, rather than closes).
Ghetto reset button. It's not even a powercycle type reset either. If you want details or such, check out the ATX specification. Look on page 22, "4.1.3.3 PWR_OK".
For a harder reset, cut the PS_ON# line. This will cause your main rails to drop to neutral, which feed important things like your CPU.
This new javascript stuff is pretty CPU intensive, for a web site. And when you have multiple stories loading in tabs... I wish the script engine was threaded.
When I said "by the compiler" perhaps a better explanation of what I'm thinking of is "by the compiler tools".
This would be less compilation and more analysis. The compiler has already gone and done it's job, although tweaks to the compiler (some nonintuitive... not using inline functions) would help. This would be adding metadata to the binary.
How does it determine when it's worth the effort of doing anything for a particular bit of computation versus just doing it inline and saving the overhead?
The compiler could do this ahead of time. It could spend the time analyzing the program, and write the results out somehow. Assign each chunk a metric of some kind.
This data could then be read at runtime and used to quickly figure out what to do. Based on the hardware, metrics below a certain level could be combined so that you have nothing below a certain granular level... and there is your breakdown. Start running the chunks.
There's no reason that a lot of this work could be done in a time-intensive manner once, instead of a less intensive manner every time it's needed. Think if it as compilation vs interpretation.
How about something similar to what some supercomputers (and the Cell Broadband Engine do) and have one (or more) core(s) (not necessarily the same or similar to the others) dispatching for the rest.
Ie, one specialized core that analyzes the program and dispatches out to the other cores. Rather than sending the actual instructions, just send them their instruction pointers and how far to execute before reporting back.
At the start, putting this in it's own socket (or allowing something like microcode updates) would be wise as this would likely change frequently. Similar to how FPU coprocessors came into play.
Did you even read the whole post? The submitter gives plenty of reasons why they want this. It's their site, they can do what the hell they want. Either provide an answer or something else constructive, or STFU.
Best to only apply this restriction to account creation. Requiring them to be local when they make the account is entirely understandable, but blocking them from logging in while traveling is not.
Local dating site, without having all those phishing jackasses start crawling all over it... that would be a very good reason.
How about restricting acount creation to local IPs based on something like Maxmind or GeoIP, but allow them to log into already existing accounts from elsewhere (for instance, if they are currently out of the area)
Yes but that's a script. Whats the harm in letting someone run a shell script? That script can't do anything they can't do themselves with a little typing.
1. I'm not making any arguments about people. I'm talking about me. 2. I don't want the other songs, I don't care what the cost of the rest is (unless it's $0)
Slashdot Mirror
> If you allow ssh access from the wide internet...
Why would you do that?
My usage case:
SSH in, tunnel to localhost:80 for web admin.
Would it be better to leave the HTTP/HTTPS world-exposed? Probably not.
Note that with a strong root password and usage of a non-standard port will help keep the bots away. Even better if you disable password authentication for SSH and use a key instead.
Now, what I miss is the reset button on the front of the machine. What's up with that?
There's an easy hack for that. Tie the PWR_OK line (it's one of the wires in the ATX connector) to a momentary switch (that opens on push, rather than closes).
Ghetto reset button. It's not even a powercycle type reset either. If you want details or such, check out the ATX specification. Look on page 22, "4.1.3.3 PWR_OK".
For a harder reset, cut the PS_ON# line. This will cause your main rails to drop to neutral, which feed important things like your CPU.
Not if the signature is left to the user to verify. Think if an MD5 sum rather than a gpg sign.
Actually, slashdot COULD use more cores.
This new javascript stuff is pretty CPU intensive, for a web site. And when you have multiple stories loading in tabs... I wish the script engine was threaded.
When I said "by the compiler" perhaps a better explanation of what I'm thinking of is "by the compiler tools".
This would be less compilation and more analysis. The compiler has already gone and done it's job, although tweaks to the compiler (some nonintuitive... not using inline functions) would help. This would be adding metadata to the binary.
That sounds like an ACPI or BIOS bug. Nice!
How does it determine when it's worth the effort of doing anything for a particular bit of computation versus just doing it inline and saving the overhead?
The compiler could do this ahead of time. It could spend the time analyzing the program, and write the results out somehow. Assign each chunk a metric of some kind.
This data could then be read at runtime and used to quickly figure out what to do. Based on the hardware, metrics below a certain level could be combined so that you have nothing below a certain granular level... and there is your breakdown. Start running the chunks.
There's no reason that a lot of this work could be done in a time-intensive manner once, instead of a less intensive manner every time it's needed. Think if it as compilation vs interpretation.
Yet other tasks, that tend to be done on desktops, do scale well. Such as rendering.
Also, audio (and video) production benefits from this very much, but not to the extent as rendering.
But most things that I can think of relate to content production, rather than the scuttwork the 'average' user does.
How about something similar to what some supercomputers (and the Cell Broadband Engine do) and have one (or more) core(s) (not necessarily the same or similar to the others) dispatching for the rest.
Ie, one specialized core that analyzes the program and dispatches out to the other cores. Rather than sending the actual instructions, just send them their instruction pointers and how far to execute before reporting back.
At the start, putting this in it's own socket (or allowing something like microcode updates) would be wise as this would likely change frequently. Similar to how FPU coprocessors came into play.
But he says he's not dead!
The only thing more hilarious than a Python quote, is a string of Python quotes placed together seemingly at random.
That damned thing was my all time favorite, next to the concrete donkey.
... and eventually swings the other way into carelessness.
After 10,000 false alarms, you would start to expect them to be false.
Balance is the answer here, as it is to so many other questions.
We call them frags or frag grenades, short for 'fragmentation grenade'.
Did you even read the whole post? The submitter gives plenty of reasons why they want this. It's their site, they can do what the hell they want. Either provide an answer or something else constructive, or STFU.
Best to only apply this restriction to account creation. Requiring them to be local when they make the account is entirely understandable, but blocking them from logging in while traveling is not.
Local dating site, without having all those phishing jackasses start crawling all over it... that would be a very good reason.
How about restricting acount creation to local IPs based on something like Maxmind or GeoIP, but allow them to log into already existing accounts from elsewhere (for instance, if they are currently out of the area)
For graphics, there is OpenGL. For everything else, there are things like SDL.
There is no real valid excuse to use DirectX, unless that's all you know how to use... which is a different problem all together.
Yes but that's a script. Whats the harm in letting someone run a shell script? That script can't do anything they can't do themselves with a little typing.
Binaries can't be run like that.
Most of /dev/ is not directly readable by users without adding them to various groups.
Check the permissions of the various nodes in /dev/ to see what I mean. That's handled by udev now and is entirely configurable.
That's not anti-aliasing, that's a scaling filter.
Bit different, but the end result (jaggies go away) is still there.
1. I'm not making any arguments about people. I'm talking about me.
2. I don't want the other songs, I don't care what the cost of the rest is (unless it's $0)
Who's to say someone is actually profiting from this?
If I had the skills and a lack of inhibitions, I would put out something like this simply to cause a panic.
I'm glad I'm not that person, 'cause that would be a shitty thing to do.
I think humbled is the antonym of what you're reaching for...
Wrong. Linux is Linux is Linux... GNU is not a part of it.
Sure, they tend to go hand in hand, but I would offer that your hand and your arm are not the same thing (though they usually go together).
It's GNU/Linux because it's a GNU system running on/under the Linux kernel.
Please tell me where I can order a CD with just the songs I want on it?
Oh right, you need to buy the whole package.