People who can't feel pain aren't necessarily insensitive to temperature, or other pain-associated senses like pressure. This depends upon what neural pathways are effected by whatever disorder the person has.
Some people won't reflexively snatch their hand away, because it doesn't hurt, but will still be aware that their hand is "too hot", based on previous experience of how hot their hand can safely be.
Aside: People insensitive to pain and temperature often die of fever at a young age because their body doesn't know to sweat.
Given that reaching the nearest viable Lagrange Point is going to mean going at least 150K miles rather that the three to four hundred currently needed for LEO I think Radiation Shielding is the least of their problems given how ridiculously expensive it is getting into space to start off with
Orbital mechanics does not work that way. Expense doesn't simply scale with distance.
Getting to LEO requires ~10km/s of delta-v, whilst going from there to L4/5 requires an additional ~4km/s, which could be undertaken using highly fuel efficient ion or VASIMR engines.
The fuel required to for the second leg of the journey wouldn't be more than a single percent of the total fuel for the trip, which could take a few months.
If you want to get there really quickly you could do it in nine days using traditional chemical engines, at the expense of three times the fuel. You might reasonably do that for light but perishable things like fresh food or astronauts.
Sure, if you mine it and dump it all on the market at once.
In reality, anyone able to pull off a commercially viable asteroid mining operation probably has enough savvy that they wouldn't just flood the market: they'd control the supply to keep prices just below that of available terrestrial sources.
This is really no different from De Beers controlling the price of diamonds, or OPEC controlling the price of oil.
The bug report was that XDG_RUNTIME_DIR was cleared when su was run in "login" mode, not when it was run in environment-preserving mode.
pam_systemd correctly preserves XDG_RUNTIME_DIR when it is run in environment-preserving mode.
When run in login mode - where su's manpage says leads to an environment which inherits only TERM - it doesn't inherit XDG_RUNTIME_DIR.
Lennart said that it wasn't clear what su should do in this situation. Actually, it's quite clear. su - must construct an environment containing only TERM, HOME, SHELL, USER, LOGNAME, and PATH. That's been the case since UNIX SVR4, at the latest.
So, per su's manpage it must not set XDG_RUNTIME_DIR in login mode, even though setting it would probably be useful behaviour. This is the bit where su is a broken concept: it is required not to produce an authentic login environment even if you ask it for one. If that doesn't quality as confusing, I don't really know what does.
Somehow Lennart refusing to modify pam_systemd so that su no longer behaves as manpages have promised it does since at least 1988 is interpreted as Lennart having no respect for Unix tradition. Just another anti-Lennart circle-jerk.
What on Earth does the NY Post think "secret" means? Not only does the administration admit they're making this database, they've said it will be partially open to the public. That isn't a secret database. That's the opposite of a secret database.
I'd love to see the real stats, but the government only shares minorities killed not the other way around.
You might have more of a point if this were true.
Re:wrong wrong wrong about copyleft
on
On Being Pro-GPL
·
· Score: 1
6c is the wrong clause.
6b is the clause which initially gives one the right to distribute object code without source, and must be accompanied by an offer to give (or make available) the source to "anyone who possesses the object code".
6c permits you to distribute object code you received under clause 6b without taking on responsibility for providing the source.
But anyone with a PC can hack whatever,whoever whenever and answer to no one?
Uh, no. That's already illegal.
The proposed changes to the law are sufficiently broad as to potentially make it illegal for me to notify a non-US software vendor about a security flaw I found in their software when probing it on my own computer.
Nah, issues are licenses. BSD etc is permissive, but the GPL is not moving things ahead anymore because big corporations are 'freebie-ing' their stuff, in some cases with a few restrictions. If 'free' software only allows to build 'free' software it will succumb to very cheap, very good "for pay" tools. The one that broke Linux as a dev platform for me was GSL not being LGPL.
GSL is GPL on all platforms, so what could that have to do with Linux's suitability for development?
From what I understand, MySQL truncated the input passed in without throwing any complaints that data was being lost.
That is MySQL's default behaviour. It can be put in strict mode, where truncated fields aren't silently ignored (and various other validity and sanity checks aren't bypassed). Ideally, this would be MySQL's default mode, but WordPress doesn't work in strict mode.
So, I do not think it is as simple as saying it is MySQL's fault. WordPress is complicit in its failure.
Any reputable cloud provider would disconnect any of their customers deemed to be hosting illegal content.
Even if it's not illegal in their home country? Cloud providers wouldn't have many customers left if they disconnected anyone hosting content that was illegal in another country.
The two sentences which all the "news" articles are based on - but which nobody links to - from Google's "announcement" of the change:
Starting April 21, we will be expanding our use of mobile-friendliness as a ranking signal. This change will affect mobile searches in all languages worldwide and will have a significant impact in our search results.
They couldn't get sued by gamers for breaching a contract with game producers!
I don't believe Valve have entered into any contract with me to let me download my game library without DRM in any particular situation.
That they will not legally bind themselves to their promise to me suggests to me that they don't actually have any binding agreements with the game producers that would give them this authority.
It's hardly surprising. Do you really imagine EA or Ubisoft (or any other major publisher-developer) would permit Steam to do this with their games?
Why are you using ZASFraction when you are testing a difference? Shouldn't it be ZASdifference or a ratio test?
You require an essay on why that particular variable was used? If I write area = PI * radius ** 2, do I need to explain why I used pi instead of e?
At some point you have to accept that your comments can't start with Euclid's elements and work up from there: you have to assume the reader has some prior knowledge. Once you accept that, it's just a question of where you draw the line.
If this code is about ZASes and their staging, and you don't know what ZAS is, perhaps you need to familiarize yourself with what the code is about at a high level before you can expect to be able to understand lines picked at random.
D- at best in school, rejected from source control at code read in industry. I'd hate to be supporting your shit.
Meanwhile, in the real world, code like this gets checked in to source control in professional development environments all the time.
*I say worthless because while I haven't used locked screens recently I remember a few years ago I bypassed an Xfree86 lockscreen by force closing the X11 session using ctrl+alt+backspace. The end result is X restarting and dropping me onto the desktop logged in as the user.
I can't believe that this would happen unless the computer is configured to automatically log in, in which case you already don't care about security.
In a secure X11 environment it should be that ctrl+alt+backspace leaves you at a login screen. Or does nothing because it's been disabled so that a random passer-by can't throw away all your unsaved changes.
My original argument was that I speculated that if we went by the rules of straw men, then one might assume that by the same rules, Sony would be eligible to do some freeloading too.
Slashdot Mirror
I was merely observing that allowing "rm -rf /" to work is prohibited, not that it was impossible in general to break a computer...
Actually, it's precisely defined. POSIX requires rm to ignore an argument which is the root directory.
People who can't feel pain aren't necessarily insensitive to temperature, or other pain-associated senses like pressure. This depends upon what neural pathways are effected by whatever disorder the person has.
Some people won't reflexively snatch their hand away, because it doesn't hurt, but will still be aware that their hand is "too hot", based on previous experience of how hot their hand can safely be.
Aside: People insensitive to pain and temperature often die of fever at a young age because their body doesn't know to sweat.
Given that reaching the nearest viable Lagrange Point is going to mean going at least 150K miles rather that the three to four hundred currently needed for LEO I think Radiation Shielding is the least of their problems given how ridiculously expensive it is getting into space to start off with
Orbital mechanics does not work that way. Expense doesn't simply scale with distance.
Getting to LEO requires ~10km/s of delta-v, whilst going from there to L4/5 requires an additional ~4km/s, which could be undertaken using highly fuel efficient ion or VASIMR engines.
The fuel required to for the second leg of the journey wouldn't be more than a single percent of the total fuel for the trip, which could take a few months.
If you want to get there really quickly you could do it in nine days using traditional chemical engines, at the expense of three times the fuel. You might reasonably do that for light but perishable things like fresh food or astronauts.
Sure, if you mine it and dump it all on the market at once.
In reality, anyone able to pull off a commercially viable asteroid mining operation probably has enough savvy that they wouldn't just flood the market: they'd control the supply to keep prices just below that of available terrestrial sources.
This is really no different from De Beers controlling the price of diamonds, or OPEC controlling the price of oil.
Ripped off by getting better performance than they would have if the emissions controls were in 'test mode' all the time?
Citation needed.
The bug report was that XDG_RUNTIME_DIR was cleared when su was run in "login" mode, not when it was run in environment-preserving mode.
pam_systemd correctly preserves XDG_RUNTIME_DIR when it is run in environment-preserving mode.
When run in login mode - where su's manpage says leads to an environment which inherits only TERM - it doesn't inherit XDG_RUNTIME_DIR.
Lennart said that it wasn't clear what su should do in this situation. Actually, it's quite clear. su - must construct an environment containing only TERM, HOME, SHELL, USER, LOGNAME, and PATH. That's been the case since UNIX SVR4, at the latest.
So, per su's manpage it must not set XDG_RUNTIME_DIR in login mode, even though setting it would probably be useful behaviour. This is the bit where su is a broken concept: it is required not to produce an authentic login environment even if you ask it for one. If that doesn't quality as confusing, I don't really know what does.
Somehow Lennart refusing to modify pam_systemd so that su no longer behaves as manpages have promised it does since at least 1988 is interpreted as Lennart having no respect for Unix tradition. Just another anti-Lennart circle-jerk.
Rocket exhausts are not "virtual". They very much exist.
What has Rider Bills ever done to you?
What on Earth does the NY Post think "secret" means? Not only does the administration admit they're making this database, they've said it will be partially open to the public. That isn't a secret database. That's the opposite of a secret database.
I'd love to see the real stats, but the government only shares minorities killed not the other way around.
You might have more of a point if this were true.
6c is the wrong clause.
6b is the clause which initially gives one the right to distribute object code without source, and must be accompanied by an offer to give (or make available) the source to "anyone who possesses the object code".
6c permits you to distribute object code you received under clause 6b without taking on responsibility for providing the source.
Is this true on London Overground trains? On the trains I take in the south, the plugs are clearly labelled as only for mobile phones or laptops.
But anyone with a PC can hack whatever ,whoever whenever and answer to no one?
Uh, no. That's already illegal.
The proposed changes to the law are sufficiently broad as to potentially make it illegal for me to notify a non-US software vendor about a security flaw I found in their software when probing it on my own computer.
Nah, issues are licenses. BSD etc is permissive, but the GPL is not moving things ahead anymore because big corporations are 'freebie-ing' their stuff, in some cases with a few restrictions. If 'free' software only allows to build 'free' software it will succumb to very cheap, very good "for pay" tools. The one that broke Linux as a dev platform for me was GSL not being LGPL .
GSL is GPL on all platforms, so what could that have to do with Linux's suitability for development?
From what I understand, MySQL truncated the input passed in without throwing any complaints that data was being lost.
That is MySQL's default behaviour. It can be put in strict mode, where truncated fields aren't silently ignored (and various other validity and sanity checks aren't bypassed). Ideally, this would be MySQL's default mode, but WordPress doesn't work in strict mode.
So, I do not think it is as simple as saying it is MySQL's fault. WordPress is complicit in its failure.
Any reputable cloud provider would disconnect any of their customers deemed to be hosting illegal content.
Even if it's not illegal in their home country? Cloud providers wouldn't have many customers left if they disconnected anyone hosting content that was illegal in another country.
They are.
The two sentences which all the "news" articles are based on - but which nobody links to - from Google's "announcement" of the change:
Starting April 21, we will be expanding our use of mobile-friendliness as a ranking signal. This change will affect mobile searches in all languages worldwide and will have a significant impact in our search results.
They couldn't get sued by gamers for breaching a contract with game producers!
I don't believe Valve have entered into any contract with me to let me download my game library without DRM in any particular situation.
That they will not legally bind themselves to their promise to me suggests to me that they don't actually have any binding agreements with the game producers that would give them this authority.
It's hardly surprising. Do you really imagine EA or Ubisoft (or any other major publisher-developer) would permit Steam to do this with their games?
I've seen people reference systemd "throwing away log messages" several times now. I've never seen a straightforward description of the problem.
Is this referring to all log levels having the same size limit, so debug messages can push out emerg messages from earlier?
WTF? Terrible.
Fast enough for what?
What is ZAS?
Why are you using ZASFraction when you are testing a difference? Shouldn't it be ZASdifference or a ratio test?
You require an essay on why that particular variable was used? If I write area = PI * radius ** 2, do I need to explain why I used pi instead of e?
At some point you have to accept that your comments can't start with Euclid's elements and work up from there: you have to assume the reader has some prior knowledge. Once you accept that, it's just a question of where you draw the line.
If this code is about ZASes and their staging, and you don't know what ZAS is, perhaps you need to familiarize yourself with what the code is about at a high level before you can expect to be able to understand lines picked at random.
D- at best in school, rejected from source control at code read in industry. I'd hate to be supporting your shit.
Meanwhile, in the real world, code like this gets checked in to source control in professional development environments all the time.
*I say worthless because while I haven't used locked screens recently I remember a few years ago I bypassed an Xfree86 lockscreen by force closing the X11 session using ctrl+alt+backspace. The end result is X restarting and dropping me onto the desktop logged in as the user.
I can't believe that this would happen unless the computer is configured to automatically log in, in which case you already don't care about security. In a secure X11 environment it should be that ctrl+alt+backspace leaves you at a login screen. Or does nothing because it's been disabled so that a random passer-by can't throw away all your unsaved changes.
Unless you can get an administrator to log in.
Your façade rather falls apart when they actually do press "del", I think.
My original argument was that I speculated that if we went by the rules of straw men, then one might assume that by the same rules, Sony would be eligible to do some freeloading too.
FTFY