Great points. It's sure feels like a more cut-and-dry issue legally than the typical scenario of a potential employer finding a picture of a particularly debaucherous night from the past. Scary as it may be, it's not hard to envision legislation sometime in the future that would address archiving bankruptcy and foreclosure info (disregarding the practicality of enforcement, of course).
Same here. Until Hardy was released it was too difficult to replace Windows 100% for the entire household. But as of last year, Ubuntu (and Wine) has become polished enough for serious work as well as for the wife and kid.
What's interesting is that satisfying the non-technical user like yourself and my wife+kid was always the bigger problem. Needless to say, to a competent programmer/IT person, any Linux distro is easily manageable so switching back to Windows wouldn't be a consideration. It's satisfying the non-techie that was the biggest stumbling block for me. But it yielded a huge payoff in time savings by not having to deal with the constant Windows issues that crop up. Things just work now given that Windows is a distant memory.
Can I make a friendly suggestion? It's obvious you're curious enough to want to figure this stuff out. But based on your comments about not knowing that / refers to root (same as DOS, btw, cd \dir1 on current drive), symlinks, aliases, etc., there's a high potential that you're going to really mess things up at some point. Especially when that lack of knowledge is coupled with sudo. I've been there.
Pick up a book like "A Practical Guide to Linux" (ISBN 0-13-147823-0) and spend a weekend working through the first half of the book. That will set a solid foundation for the basic concepts and cover most of the questions in your post like directory structure, permissions, etc.
Next learn the basics of VIM, maybe 5 or 10 commands cover most editing tasks. Insert mode will be absolutely infuriating at first but don't back off and resort to a gui editor...it will be a hindrance in the long run.
Then pick a topic at random and concentrate on how it works. Figure out the concept of mounts by looking at fstab, for example. Try some simple sed or awk commands. Proceed on to simple shell scripts and customizing.bashrc, etc.
You can handle it; just take your time to make sure you really understand what's going on. Be tenacious and don't gloss over things. It won't take long to see just how suffocating the Windows mindset is. The flexibility on the *nix side of the fence is pretty amazing. It's a great feeling once it clicks; you won't want to go back.
To sum up, the GUI warts aren't as important as you think once you understand the shell and filesystem.
Two points: 1) I'd modify the gp's statement to say "responsible regulation." The investment banking leverage ratio was regulated; the increase from 15:1 to 33:1 by Donaldson/Cox was the cause of Bear's failure whereby their management went overboard with leverage.
2) The increase in loan originations was due to the massive reduction in interest rates per Greenspan's attempt to pull the economy out of the 2000-2 fall.
Not sure what this "social justice" babble is referring to.
Or, for mass effect, do random drivebys on unsecured wifi routers. Torrent some unencrypted goodies through the connection so there's real proof in the ISP's logs that infringement happened.
Then report the address of the hapless blokes. It may only take a couple dozen instances in the average sized city to achieve the desired effect.
Cutting off internet access to a bunch of Joe Consumers (who spend over a hundred bucks a month on their cable bill) is a big deal and would guarantee mainstream coverage of the monitoring issue.
For some reason I always liked listening to Paul Harvey. It was kind of a game to figure out what product he was going to pitch during the seqway. The Rest of the Story was usually interesting too. It's somewhat surprising that a site hasn't popped up using this format, somehow, some way.
Probably start with Drupal on top of the evaluation list. Yeah the usual PHP gripes apply. But coming from a programmer's mindset, the framework always seems to make sense to me. The others felt kludgy in one way or another. YMMV.
Currently around 20% EQE with PHOLED sounds right.
IIRC a UDC SBIR report from a few years ago stated to meet the DOE goal of 150lm/W, an EQE of almost 60% would need to be reached. That includes advances for reducing the supply voltage and other variables.
40% for 100lm/W was the goal by 2010/11 using microlens/optocoupling techniques.
1) The optimal solution right now is flourescent blue combined with PHOLED red and green (phosphorescent). It's unclear right now how much PHOLED is being used in Sony's sets.
PHOLED is important primarily for power consumption which is why OLED screens are showing up more frequently in mobile devices. Nokia recently mandated that their suppliers have supply capability for OLED. Samsung is the major proponent of using PHOLED although LG and others are on board with materials+royalty contracts in place.
2) Samsung's recent statements about larger screen sizes (30"+) being far into the future seem to be due to two issues. First, although current LCD lines can be relatively easily retrofitted to produce OLED panels, production capacity is just starting to be scaled.
Second, and probably more importantly, the major LCD panel manufacturers have a major investment to be paid off in the later gen lines that recently came online.
3) The major issues facing OLED right now are packaging, lifetime and defect rate. The molecules degrade rapidly when exposed to oxygen/moisture so much tighter packaging is required (largely solved). Blue lifetime (both molecule sizes) was a problem in the past, 30k+ hours is now realistic. Defect rate applies to larger panels and is why 30"+ screens will be prohibitively expensive for now (Samsung has produced prototypes though so it isn't vaporware).
4) PHOLED can reach 100% EQE, flourescent around 25%. PMOLED is still viable but PHOLED should (imho) be the ideal molecule in the future. PHOLED deep blue with adequate lifetime is still the major hurdle, sky blue is ready to go.
5) OLED isn't just display. Lighting is arguably a larger market in the long run. Current specs are around 50lm/W but 100lm/W PHOLED has been successfully demonstrated. 150lm/W is pushing the envelope but not unrealistic.
GE is pushing its roll-to-roll initiative. Philips is aggressively heading toward commercial production. OLED lighting offers lower power consumption, temperature tunability, flexibility, flat panel replacement and fault tolerance (in the respect that a hole in the middle of the panel won't take out the entire structure). Universal Display recently received a grant with Armstrong to engineer tiles for commercial use.
6) OLED's appeal is not just a better display and flexibility; thickness (sub-1mm) and transparency are important factors for future designs and mass acceptance as a technology (Youtube has many videos about the Samsung prototypes).
7) The technology is way past the prototype stage, like where FED and SED have been stuck. Kodak, Dupont, BASF and every Japanese and Korean company you can name are involved (i.e. heavily investing) in OLED. Not to mention that the Chinese are going online this year in a big way. Will it replace LCD for display? Not any time soon. The question is not how many applications there are to make it viable, it's how soon these apps will gain critical mass in the marketplace.
The data server had only one purpose: maintaining the journalspace database. There were no other web sites or processes running on the server, and it would be impossible for a software bug in journalspace to overwrite the drives, sector by sector.
The list of potential causes for this disaster is a short one. It includes a catastrophic failure by the operating system (OS X Server, in case you're interested), or a deliberate effort. A disgruntled member of the Lagomorphics team sabotaged some key servers several months ago after he was caught stealing from the company; as awful as the thought is, we can't rule out the possibility of additional sabotage.
First, it's somewhat lame/unprofessional to list "sabotage" as a possibility. Even if it's the strongest possibility. Adding the OSX comment and that a bug in their code is impossible is even lamer.
More importantly, if the key servers were sabotaged months ago, the first thing that I'd want to do is make a full image stored in multiple offsite locations. Ignorance of the RAID/backup issue is one thing, but knowing that the sabateur could have sprinkled the db with crap is even scarier.
Smells like there's more to the story than this. Or not.
Ben Stein also believes some wacky things about the markets and has been published in the NYT. Including issues regarding the credit crisis and that shorts sellers were responsible for market declines this year.
Doug Kass decomposed him pretty well in a series of articles:
what clause 6.2 appears to say is that if AMD gets taken over or goes bankrupt, Intel has the right to end AMD's right to use Intel's patents and copyrights after sixty days notice. This would seem to mean AMD couldn't make x86 processors anymore.
So the arms race isn't so cut-and-dry because x86 is so pervasive. Any competitor would likely find themselves in the same situation as AMD because Intel holds the licensing trump card. Imagine being the startup trying to negotiate a fair arrangement under those conditions (i.e. where they could be truly competitive with Intel down the road).
Slashdot Mirror
Great points. It's sure feels like a more cut-and-dry issue legally than the typical scenario of a potential employer finding a picture of a particularly debaucherous night from the past. Scary as it may be, it's not hard to envision legislation sometime in the future that would address archiving bankruptcy and foreclosure info (disregarding the practicality of enforcement, of course).
Hot lesbian termite sex?
I dunno. Maybe.
Same here. Until Hardy was released it was too difficult to replace Windows 100% for the entire household. But as of last year, Ubuntu (and Wine) has become polished enough for serious work as well as for the wife and kid.
What's interesting is that satisfying the non-technical user like yourself and my wife+kid was always the bigger problem. Needless to say, to a competent programmer/IT person, any Linux distro is easily manageable so switching back to Windows wouldn't be a consideration. It's satisfying the non-techie that was the biggest stumbling block for me. But it yielded a huge payoff in time savings by not having to deal with the constant Windows issues that crop up. Things just work now given that Windows is a distant memory.
Close, but no cigar...
Last post!
Can I make a friendly suggestion? It's obvious you're curious enough to want to figure this stuff out. But based on your comments about not knowing that / refers to root (same as DOS, btw, cd \dir1 on current drive), symlinks, aliases, etc., there's a high potential that you're going to really mess things up at some point. Especially when that lack of knowledge is coupled with sudo. I've been there.
Pick up a book like "A Practical Guide to Linux" (ISBN 0-13-147823-0) and spend a weekend working through the first half of the book. That will set a solid foundation for the basic concepts and cover most of the questions in your post like directory structure, permissions, etc.
Next learn the basics of VIM, maybe 5 or 10 commands cover most editing tasks. Insert mode will be absolutely infuriating at first but don't back off and resort to a gui editor...it will be a hindrance in the long run.
Then pick a topic at random and concentrate on how it works. Figure out the concept of mounts by looking at fstab, for example. Try some simple sed or awk commands. Proceed on to simple shell scripts and customizing .bashrc, etc.
You can handle it; just take your time to make sure you really understand what's going on. Be tenacious and don't gloss over things. It won't take long to see just how suffocating the Windows mindset is. The flexibility on the *nix side of the fence is pretty amazing. It's a great feeling once it clicks; you won't want to go back.
To sum up, the GUI warts aren't as important as you think once you understand the shell and filesystem.
Fwiw.
Two points:
1) I'd modify the gp's statement to say "responsible regulation." The investment banking leverage ratio was regulated; the increase from 15:1 to 33:1 by Donaldson/Cox was the cause of Bear's failure whereby their management went overboard with leverage.
2) The increase in loan originations was due to the massive reduction in interest rates per Greenspan's attempt to pull the economy out of the 2000-2 fall.
Not sure what this "social justice" babble is referring to.
Or, for mass effect, do random drivebys on unsecured wifi routers. Torrent some unencrypted goodies through the connection so there's real proof in the ISP's logs that infringement happened.
Then report the address of the hapless blokes. It may only take a couple dozen instances in the average sized city to achieve the desired effect.
Cutting off internet access to a bunch of Joe Consumers (who spend over a hundred bucks a month on their cable bill) is a big deal and would guarantee mainstream coverage of the monitoring issue.
Or something like that.
"...because the Obama Administration hasn't appointed a Secretary of Commerce yet..."
That reads like the administration has been lax in getting the position filled. Hopefully the third time's a charm:
http://voices.washingtonpost.com/thefix/2009/02/locke_to_commerce.html?hpid=topnews
For some reason I always liked listening to Paul Harvey. It was kind of a game to figure out what product he was going to pitch during the seqway. The Rest of the Story was usually interesting too. It's somewhat surprising that a site hasn't popped up using this format, somehow, some way.
Oh, and my Bose radio sounds incredible.
Disagree. I'd rather my kid got a case of gout from Linux than a virus from using Windows.
Of course neither is as bad as the swelled cranium that results from using a Mac...
So "Humor Analysis and Identification" is a 300-level class?
Probably start with Drupal on top of the evaluation list. Yeah the usual PHP gripes apply. But coming from a programmer's mindset, the framework always seems to make sense to me. The others felt kludgy in one way or another. YMMV.
Argh. Yes, thank you.
Currently around 20% EQE with PHOLED sounds right.
IIRC a UDC SBIR report from a few years ago stated to meet the DOE goal of 150lm/W, an EQE of almost 60% would need to be reached. That includes advances for reducing the supply voltage and other variables.
40% for 100lm/W was the goal by 2010/11 using microlens/optocoupling techniques.
A few points about OLED:
1) The optimal solution right now is flourescent blue combined with PHOLED red and green (phosphorescent). It's unclear right now how much PHOLED is being used in Sony's sets.
PHOLED is important primarily for power consumption which is why OLED screens are showing up more frequently in mobile devices. Nokia recently mandated that their suppliers have supply capability for OLED. Samsung is the major proponent of using PHOLED although LG and others are on board with materials+royalty contracts in place.
2) Samsung's recent statements about larger screen sizes (30"+) being far into the future seem to be due to two issues. First, although current LCD lines can be relatively easily retrofitted to produce OLED panels, production capacity is just starting to be scaled.
Second, and probably more importantly, the major LCD panel manufacturers have a major investment to be paid off in the later gen lines that recently came online.
3) The major issues facing OLED right now are packaging, lifetime and defect rate. The molecules degrade rapidly when exposed to oxygen/moisture so much tighter packaging is required (largely solved). Blue lifetime (both molecule sizes) was a problem in the past, 30k+ hours is now realistic. Defect rate applies to larger panels and is why 30"+ screens will be prohibitively expensive for now (Samsung has produced prototypes though so it isn't vaporware).
4) PHOLED can reach 100% EQE, flourescent around 25%. PMOLED is still viable but PHOLED should (imho) be the ideal molecule in the future. PHOLED deep blue with adequate lifetime is still the major hurdle, sky blue is ready to go.
5) OLED isn't just display. Lighting is arguably a larger market in the long run. Current specs are around 50lm/W but 100lm/W PHOLED has been successfully demonstrated. 150lm/W is pushing the envelope but not unrealistic.
GE is pushing its roll-to-roll initiative. Philips is aggressively heading toward commercial production. OLED lighting offers lower power consumption, temperature tunability, flexibility, flat panel replacement and fault tolerance (in the respect that a hole in the middle of the panel won't take out the entire structure). Universal Display recently received a grant with Armstrong to engineer tiles for commercial use.
6) OLED's appeal is not just a better display and flexibility; thickness (sub-1mm) and transparency are important factors for future designs and mass acceptance as a technology (Youtube has many videos about the Samsung prototypes).
7) The technology is way past the prototype stage, like where FED and SED have been stuck. Kodak, Dupont, BASF and every Japanese and Korean company you can name are involved (i.e. heavily investing) in OLED. Not to mention that the Chinese are going online this year in a big way. Will it replace LCD for display? Not any time soon. The question is not how many applications there are to make it viable, it's how soon these apps will gain critical mass in the marketplace.
Google for further information.
From TFL:
The data server had only one purpose: maintaining the journalspace database. There were no other web sites or processes running on the server, and it would be impossible for a software bug in journalspace to overwrite the drives, sector by sector.
The list of potential causes for this disaster is a short one. It includes a catastrophic failure by the operating system (OS X Server, in case you're interested), or a deliberate effort. A disgruntled member of the Lagomorphics team sabotaged some key servers several months ago after he was caught stealing from the company; as awful as the thought is, we can't rule out the possibility of additional sabotage.
First, it's somewhat lame/unprofessional to list "sabotage" as a possibility. Even if it's the strongest possibility. Adding the OSX comment and that a bug in their code is impossible is even lamer.
More importantly, if the key servers were sabotaged months ago, the first thing that I'd want to do is make a full image stored in multiple offsite locations. Ignorance of the RAID/backup issue is one thing, but knowing that the sabateur could have sprinkled the db with crap is even scarier.
Smells like there's more to the story than this. Or not.
Chris Farley died way too young. For the younger mods that might not get the reference:
http://www.jibjab.com/view/142675
due to changes in the earth's albedo.
Guess Venus is starting to show her age.
Uranus looks kinda cute though.
I sometimes use a fake mother's maiden name also. But as others have noted, the difficulty is knowing when you lied.
The key is to pick a name that makes the CSR chuckle after seeing your answer in the system. Then it's a slam dunk that you used the fake name.
In case you're wondering, I was conceived by Mary Magdalene.
If you're running your OS inside a web browser, what is the web browser running on?
vi, of course.
5318008
The true king of beghilos, and one that I think about at least 50 times a day.
You're referring to Jill. Her name is mentioned in one of the commercials.
Feel free to embarrass me appropriately for knowing that factoid.
Ben Stein also believes some wacky things about the markets and has been published in the NYT. Including issues regarding the credit crisis and that shorts sellers were responsible for market declines this year.
Doug Kass decomposed him pretty well in a series of articles:
http://www.thestreet.com/story/10400657/1/kass-ben-stein-blames-you.html
http://www.thestreet.com/story/10403672/1/kass-eat-my-shorts-ben-stein.html
Stein is the new Dvorak.
An interesting aside wrt AMD. Apparently AMD's license for the x86 instruction set has a massive "catch":
http://www.overclockers.com/tips01276/
what clause 6.2 appears to say is that if AMD gets taken over or goes bankrupt, Intel has the right to end AMD's right to use Intel's patents and copyrights after sixty days notice. This would seem to mean AMD couldn't make x86 processors anymore.
The direct findlaw doc link:
http://contracts.corporate.findlaw.com/agreements/amd/intel.license.2001.01.01.html
So the arms race isn't so cut-and-dry because x86 is so pervasive. Any competitor would likely find themselves in the same situation as AMD because Intel holds the licensing trump card. Imagine being the startup trying to negotiate a fair arrangement under those conditions (i.e. where they could be truly competitive with Intel down the road).
Only if they've "seen the light".
And here we all thought PJ was going to have to start looking for a new job soon.
:)
She would have had plenty of time to find one...IBM offers excellent severance packages.