You claim you don't understand, so let me spell it out for you:
The/. community generally looks favorably on increased liberty, privacy, free software and innovation. Software patents are disfavored because, being developers, Slashdotters know that it doesn't take a whole lot of time to implement such patents.
So, by that measure:
Apple releases Darwin: good Google unifies user agreement and user data: bad Apple sues Samsung on design patents: good Apple refuses to pay for hardware patents: bad Apple bricks jailbreakers: bad HTC restricts modding: bad Samsung allows modding: good
You'd have a point if these were totally worthless patents being used against Apple. That would be a what's good for the goose is good for the gander situation.
But these are hardware patents, real stuff about interacting with physics, like radio waves, not the shape of a rectangle that a dev can hack out in a few hours.
That's not what he was talking about. The reason it's funny is because it touches on something true: the fact that Linux doesn't wake up from suspend on some of the multitudinous hardware out there. I myself had this problem on brandname (HP) desktop, until I went and customized suspend with blacklist.conf.
But you should at least be able to browse the available servers, right? What I see is the community will continue to put out buggy Windows interop software because M$ can't just hand over the AD source.
Anyway, like I said in another place in the discussion, the Linux community seems to have went about this wrong.
It would have been better to come up with a networking addon for Windows clients to allow them to easily browse and connect to resources provided by Linux servers in a hierarchical domain arrangement (basically, Domain Name System). So: ibm.com, fl.ibm.com, miami.fl.ibm.com, files1.miami.ibm.com, etc.
Auth handed by OpenLDAP and Kerberos. Remote login by RADIUS.
Some of that stuff would need some polishing around the edges plus integration, but again, writing your own Windows client DLL should seem to be much easier than divining and decoding messages passed around an AD network.
Also: it would have been nice to really think outside the box. Like, how about allowing users to browse resources instead of being concerned with which server a resource happens to reside on?
It seems that it would almost be easier drop reverse engineering the Windows network server to allow standard Windows clients to use Samba, and instead:
Create a new Windows client network DLL which can be installed on Windows clients to be able to access resources provided by Linux servers running LDAP and friends.
No More Network Browsing In Windows based AD you can still browse a network, Samba3 had this but Samba4 does not. So, you will not see your domain, or browse machines in the domain.
Samba4 and Homes The [homes] share and the browseable directive don't work as expected.
Cannot contact any KDC for requested realm: unable to reach any KDC in realm $DOMAIN This is a DNS related issue, it's likely the above SRV records are not present, fix your DNS.
The first one is kind of major, I would think: You can't even browse a network?!
I don't know if you were being sarcastic, but Steve Jobs didn't pay taxes like you or I: he was paid $1 in salary, and the rest in stock, which has different tax implications, and (AFAIK) a capital gains tax rate of 15%, much lower than for wages.
The poster didn't say whether his instructor had a problem with a Windows client/Linux server setup or with a Linux network in general.
E.g., what if you just cut Win clients out of the picture? Just have straight up Linux. Would he still have a problem?
Secondly, if you did have straight Linux, what kind of software stack would you have?
How well does LDAP work when you get to the nitty gritty? Is Kerberos something you'd be using? What's the best NAS? FreeNAS? 7 or 8? Or NAS4Free? Just a Linux box running NAS-type packages?
You seem like you would have enough information to really let the rest of us know something (like specific versions of servers and clients) and what exactly happened as opposed to a cryptic remark.
No, he's not arguing against "science". Science is the pursuit of knowledge. Engineering is application of science toward an end.
And business is application of engineering towards a profit.
Mini-nuclear plants run by universities are for science. Nuclear power plants are for business.
The largest nuclear operator in the US is Exelon, with operations in 47 states. It is a publicly-traded corporation, which means it is responsible to the shareholders for quarterly earnings. It's not responsible for any possible massive devastation because the US government handles that by socializing the risk (crony capitalism).
Exelon engages in mergers, acquisitions offers, and all the rest you'd expect any corporation to do.
"In 2009, the Nuclear Regulatory Commission announced its plan for a $65,000 fine against Exelon for permitting its contracted security guards that were guarding its Peach Bottom Nuclear Generating Station, a two-reactor nuclear plant located in Delta, Pennsylvania to sleep on the job."
You claim you don't understand, so let me spell it out for you:
The /. community generally looks favorably on increased liberty, privacy, free software and innovation. Software patents are disfavored because, being developers, Slashdotters know that it doesn't take a whole lot of time to implement such patents.
So, by that measure:
Apple releases Darwin: good
Google unifies user agreement and user data: bad
Apple sues Samsung on design patents: good
Apple refuses to pay for hardware patents: bad
Apple bricks jailbreakers: bad
HTC restricts modding: bad
Samsung allows modding: good
You'd have a point if these were totally worthless patents being used against Apple. That would be a what's good for the goose is good for the gander situation.
But these are hardware patents, real stuff about interacting with physics, like radio waves, not the shape of a rectangle that a dev can hack out in a few hours.
Hot/cold cycle? I thought most ECUs are are somewhere in the dash/under the driver/etc, with, ahem, wires connecting to the rest of the car.
Why should (or can) the Federal government be concerned with with a hobbyist fixing his own car? That's not interstate commerce.
That's not what he was talking about. The reason it's funny is because it touches on something true: the fact that Linux doesn't wake up from suspend on some of the multitudinous hardware out there. I myself had this problem on brandname (HP) desktop, until I went and customized suspend with blacklist.conf.
Right, that's what you do. But what about (l)users?
Or, I guess you could set up a simple HTML page per department that lists links to the resources that they normally need.
For those who can't be bothered to even read the summary, this is not more censorship, it can actually be seen as less.
Instead of deleting the tweet whole, they'll be logging the deletions at Chilling Effects.
So what do your users do? Type in network locations?
\\blah\whatever\something ?
Sounds Linuxy.
What taxes would those be? $333 tax on the first sale of the APPLE for $1000?
I thought we were talking about Apple and Jobs in this century.
See here.
http://en.wikipedia.org/wiki/One-dollar_salary
This approach also means that you don't pay any payroll taxes.
Well, OK, granted for personal machines.
But you should at least be able to browse the available servers, right? What I see is the community will continue to put out buggy Windows interop software because M$ can't just hand over the AD source.
Anyway, like I said in another place in the discussion, the Linux community seems to have went about this wrong.
It would have been better to come up with a networking addon for Windows clients to allow them to easily browse and connect to resources provided by Linux servers in a hierarchical domain arrangement (basically, Domain Name System). So: ibm.com, fl.ibm.com, miami.fl.ibm.com, files1.miami.ibm.com, etc.
Auth handed by OpenLDAP and Kerberos. Remote login by RADIUS.
Some of that stuff would need some polishing around the edges plus integration, but again, writing your own Windows client DLL should seem to be much easier than divining and decoding messages passed around an AD network.
Also: it would have been nice to really think outside the box. Like, how about allowing users to browse resources instead of being concerned with which server a resource happens to reside on?
It seems that it would almost be easier drop reverse engineering the Windows network server to allow standard Windows clients to use Samba, and instead:
Create a new Windows client network DLL which can be installed on Windows clients to be able to access resources provided by Linux servers running LDAP and friends.
Your link itself noted glitches in Samba4:
The first one is kind of major, I would think: You can't even browse a network?!
Leaving aside the question of personal rights applying to nonnatural entities, the fourth and eighth amendments would only apply to US entities.
The overseas corporations (Apple Caymans or whatever) would not have US legal protection.
I don't know if you were being sarcastic, but Steve Jobs didn't pay taxes like you or I: he was paid $1 in salary, and the rest in stock, which has different tax implications, and (AFAIK) a capital gains tax rate of 15%, much lower than for wages.
The poster didn't say whether his instructor had a problem with a Windows client/Linux server setup or with a Linux network in general.
E.g., what if you just cut Win clients out of the picture? Just have straight up Linux. Would he still have a problem?
Secondly, if you did have straight Linux, what kind of software stack would you have?
How well does LDAP work when you get to the nitty gritty? Is Kerberos something you'd be using? What's the best NAS? FreeNAS? 7 or 8? Or NAS4Free? Just a Linux box running NAS-type packages?
Single signon?
You seem like you would have enough information to really let the rest of us know something (like specific versions of servers and clients) and what exactly happened as opposed to a cryptic remark.
So, yeah, I'm up for spending $2000 to "assist" political candidates to the netherworld.
Apple had it coming. Couldn't happen to a better bunch of folks.
I hope iFone socks it to them (and it looks like they plan to).
>The "taking" of the FRAND patent is balanced by the fact that Apple are *paying* for its use.
When did that happen? Apple only offered to pay $1 going forward. So, again, when did apple pay?
Why would they want to resell to themselves?
Puerile. Childish.
From Latin puer, "boy".
I'm trying to understand what you're saying. Google made $1.5 bil or so from iOS because of ads, right?
So why would you say they only made $10mil on ads from Android?
The two platforms have roughly the same number of users these days.
OK, it's official, "app" is known to the State of California to be defined as a "mobile application".
OK, but they're talking about the revenue that Google gets from displaying ads next to Google News.
Yet, Google doesn't display ads in Google News.
So what are they even talking about?
No, he's not arguing against "science". Science is the pursuit of knowledge. Engineering is application of science toward an end.
And business is application of engineering towards a profit.
Mini-nuclear plants run by universities are for science. Nuclear power plants are for business.
The largest nuclear operator in the US is Exelon, with operations in 47 states. It is a publicly-traded corporation, which means it is responsible to the shareholders for quarterly earnings. It's not responsible for any possible massive devastation because the US government handles that by socializing the risk (crony capitalism).
Exelon engages in mergers, acquisitions offers, and all the rest you'd expect any corporation to do.
By the way, Newsmax says the US couldn't fund a Fukushima-style disaster; that's not an enviro left-wing site.
"In 2009, the Nuclear Regulatory Commission announced its plan for a $65,000 fine against Exelon for permitting its contracted security guards that were guarding its Peach Bottom Nuclear Generating Station, a two-reactor nuclear plant located in Delta, Pennsylvania to sleep on the job."