There are answers for these: location, location, location. Since the elevator should be located on the equator, simply build it inland, in geologically and weather stable region like central Africa. Of course, Africa's completely politically unstable and will probably remain so in our lifetimes.
I think the harder problem is space junk. Lots of posts here about how strong the cable needs to be to support the counterweight and cable cars. I think even more important is that the ribbon is going to be shot at with high energy missiles on a regular basis.
Let's say the material can take the occasional shot from a stray nut or hammer at orbital velocity. Or even small iron chunks at super-orbital velocity (meteors). It's still going to need thrusters along the way to dodge the occasional booster rocket, heat shield, or large rock floating by up there.
Stories persist whether true or false and represent the oldest extant (nearly complete) texts in many languages: Genesis, the Epic of Gilgamesh, The Illiad, Beowulf, the Vedas, and the Book of the Dead to name a few.
Many modern humans will know of, part of, or all of at least one of these stories.
Whereas more practical texts have survived, but knowledge of them isn't as widespread. Not a lot of people can recite goat inventory from Ur or lists of Old Kingdom Egyptian rulers.
Ever get the feeling they're building a kludge all over again? Space Shuttle II -- Revenge of Thousands of Glued On Tiles and Strapping It to the Side an Ice-Covered Tank.
There was no way to passively dampen the vibrations? A simpler, cheaper solution? So instead they'll introduce another ton of lift weight and 17 additional motors and batteries to fail.
My prediction: in the first 50 launches this system will fail and the rocket will either shake the astronauts and payload apart (failure to dampen) or spectacularly shake the rocket apart (oscillate lopsidedly or out of synch with the vibrations).
With luck Slashdot will archive this long enough. Given that this is a NASA project, that might not be likely.
Thank you for admitting that programming isn't your thing. Thank you for not subjecting your fellow programmers to years and years of bad code, grumpy job performance, and being a drag on other coders' lives. Thank you for letting our managers hire people who want to do this job, instead of those just killing time.
I'm sure you're a fine person, but thank you for not working here as one of my developers. You are too honest for management or sales, but I'm sure you'll find something good to do.
Now if we can only get other CS majors who shouldn't be programming out of the trenches, life might improve.
Daisy wheel and golf ball? They're not loud when compared to a barrel printer.
Barrel printer? They're not loud when compared to a chain printer. Until 1992 we had an IBM-1403 that we kept around just for re-printing the source code books every month.
(Yes, we kept the source code printed out for taking support calls in the programming department. It was easier to page through the source in book form to find out why things happened than to find the right floppy disks, load up the code, load up the editor, and then page through at 24x80... Documentation? Pffft! Spec? Pshaw!)
We had an upper-case only chain, though. So mixed-case text was always a bit of a puzzle to figure out. Fortunately the programming language was case insensitive.
Even the linefeed/pagefeed was loud.
PS: And don't fuck up the linefeed/carriage return sequence. At 75 inches / second a bad print job could ruin a box of paper in a few minutes.
Maybe he strayed too far over the line, but it's not true that the journalist's feelings about a subject don't matter or are unimportant to the story
Journalists have made entire careers out of producing this kind of schmaltzy crap. Observe..
Hear that? It's the sound of childrers laughter silenced.
That's because tomorrow this old carousel which has delighted young Americans for lo these past six years will be torn down to make way for the future- a store that sells designer mouse pads.
Well, I guess there's no room in this modern world for old Blackie here but if you don't mind this reporter is going for one last ride.
--This is Kent Brockman, reporting.
If you want a real-life example, take someone like Mitch Albom. Please.
Fuller constructed a scale model of the house, which was exhibited in 1929 at Marshall Field's as part of a display of modern furniture. But no full-size version could be produced, because many of the components, including what Fuller called a "radio-television receiver," did not yet exist.
There is a full-scale Dymaxion House: in Dearborn, Michigan at the Henry Ford Museum. That a New Yorker writer couldn't turn that fact up with a quick Google search is disappointing.
Two prototypes were built, and one was modified and lived in for several years by the Graham family. The rebuilt house is made from parts cobbled together from the other two, and some parts that had to be re-manufactured from the original plans. Tours are given through the Dymaxion House in the museum, and I've been several times.
When I bought laptops for the house in January, the same models with XP (instead of Vista) were $50 more each.
The real FAIL came later: Thinking I could just get Vista, save $50, and re-load XP from Genuine XP install media (I had licenses to spare). Turns out XP wouldn't work. There were devices on the laptops (WiFi, sound, etc..) for which there were no XP drivers available. I wound up restoring Vista and spending the $100 I "saved" on an additional GB of memory for each system to make them usable.
That explains a lot in Detroit anyway.
on
The Red Team Wins
·
· Score: 1
This might explain:
The Detroit Red Wings, the closest thing to a winning "dynasty" in the days of free-agency hockey. (4 Stanley Cups in 11 years). (Red & White hockey sweaters.)
And the Detroit Lions... perennial losers, only a handful of playoff appearances in 40 years, and no chance of winning anything anytime in the forseeable future. (Blue & Grey [and black] jerseys)
Or it could be decades of lackluster mis-management by the Lions owners (the Ford family), and a passionate winning attitude from the competent Red Wings owners (the Illich family).
The False God of Backward Compatibility has Microsoft by the short hairs. Even new programming environments like.Net have Win32, Win16, and DOS lurking right around the corner. There's no fresh start anywhere in the Microsoft environment, everything reeks of DOS.
Which would have been find if DOS (Win16, Win32, etc..) were a multi-platform, extensible OS to begin with -- but it wasn't. It was a quick hack that lives on and on.
I'm a developer that works primarily in Windows, with 15 years of heavy-hitting Unix programming experience behind me.
[Now you're splitting hairs like any good software developer: "The software worked fine, it just never deployed because..." -- The project failed.]
The reason muni wifi didn't deploy as widely as expected, does not change the economics of the situation: the cost of the equipment, software, and administration will not come down until enough volume is produced. And a dozen or so major metropolitan areas represents a lot of volume.
However many more have failed in places like Houston, Chicago, San Francisco, Philadelphia, Rhode Island, Orlando, Tempe, Portland, and closer to home (for me) Grand Rapids and Oakland County. This list isn't complete, of course. You could ask Earthlink for a better one...
Community and city-wide wifi projects everywhere are failing. In general they turned out to be more expensive, more cumbersome, and difficult to manage than originally promised. The county-wide wifi program where I lived stopped development last year because the vendor's pricing model proved unworkable (give away low-speed, sell high speed). Other communities are having similar problems.
To think that's *not* going to affect the cost of the remaining projects is just silly. Without the volume, the costs are going to go up for the projects that are still out there left undone.
The rules of the game are *ALWAYS* changing. That's life. We can tell you're upset, but quit your whining.
Is there a difference between "managed code" and "interpreted code"? They seem like two words for the same thing.
IANA Microsoft Language Lawyer, but this is what I think the distinctions are:
Managed Code is code intended for a virtual machine (like MS's CLR or Sun's JVM) that abstracts the hardware instructions away. Instead, the instruction set for the virtual machine is used. The Virtual Machine will provide "devices" and "memory" in a (hopefully) safe and portable way and take care of all of the dirty hardware business itself. Some VM's will actually take the VM instruction and turn it into actual hardware instructions as it's being executed (JIT) for speed, but that's not necessary.
Which isn't to say that Managed Code is a new thing: The USCD-Pascal p-code machine is remembered fondly by many, and the Zork games ran on a Z-Machine.
Interpreted code is a little stickier because it's been around a lot longer and has picked up some additional meanings. It can mean anything from the "Managed Code" described above to parsing (and possibly re-parsing) text lines of BASIC as they're run to process them in a giant state machine which "runs" the program.
Usually, interpreted code implies that there's no abstracted fully virtual machine underneath running the code, but possibly just a big jump-table pointing at native assembly-language (hand-coded or compiled) routines. Perl and Microsoft BASIC (basis of many of the old 8-bit BASICs) are two examples of interpreted code.
I've run into this a few times and it's easy to explain:
In the auto industry there are mechanics, powertrain engineers, and those guys that design bodies and interiors. (No bias from me at all!) You wouldn't want the guy picking paint colors and fabrics for the interiors to design your exhaust manifold; by the same token you don't want the guy who does the casting flow calculations for the engine block figuring out what the front grill should look like. These are not only different professions, but different kinds of professions.
Keep your nose out of the design business, please. If you're a good programmer or admin guy, you don't know much about marketing and have lousy taste. Admitting it is the first step.
You want to decelerate over as long a distance as possible tor educe the requirements on the heat-shield. I guess you must test the whole thing for water-compatibility, but if it is to deal with vacuum, intense heat, and solar wind, I would imagine it should be able to deal with some water.
Leela: Depth at forty five hundred feet. Forty eight hundred. Fifty hundred. Five thousand feet. Professor Farnsworth: Dear Lord, that's over 150 atmospheres of pressure. Fry: How many atmospheres can this ship withstand? Professor Farnsworth:Well it's a spaceship, so I'd say anywhere between zero and one.
approach to fighting spam. Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.)
( ) Spammers can easily use it to harvest email addresses ( ) Mailing lists and other legitimate email uses would be affected ( ) No one will be able to find the guy or collect the money ( ) It is defenseless against brute force attacks ( ) It will stop spam for two weeks and then we'll be stuck with it ( ) Users of email will not put up with it ( ) Microsoft will not put up with it (X) The police will not put up with it, anywhere other than Russia ( ) Requires too much cooperation from spammers ( ) Requires immediate total cooperation from everybody at once ( ) Many email users cannot afford to lose business or alienate potential employers ( ) Spammers don't care about invalid addresses in their lists ( ) Anyone could anonymously destroy anyone else's career or business
Specifically, your plan fails to account for
(X) Laws expressly prohibiting it ( ) Lack of centrally controlling authority for email ( ) Open relays in foreign countries ( ) Ease of searching tiny alphanumeric address space of all email addresses ( ) Asshats ( ) Jurisdictional problems ( ) Unpopularity of weird new taxes ( ) Public reluctance to accept weird new forms of money ( ) Huge existing software investment in SMTP ( ) Susceptibility of protocols other than SMTP to attack ( ) Willingness of users to install OS patches received by email ( ) Armies of worm riddled broadband-connected Windows boxes ( ) Eternal arms race involved in all filtering approaches ( ) Extreme profitability of spam ( ) Joe jobs and/or identity theft ( ) Technically illiterate politicians ( ) Extreme stupidity on the part of people who do business with spammers ( ) Dishonesty on the part of spammers themselves ( ) Bandwidth costs that are unaffected by client filtering ( ) Outlook
and the following philosophical objections may also apply:
( ) Ideas similar to yours are easy to come up with, yet none have ever been shown practical ( ) Any scheme based on opt-out is unacceptable ( ) SMTP headers should not be the subject of legislation ( ) Blacklists suck ( ) Whitelists suck ( ) We should be able to talk about Viagra without being censored ( ) Countermeasures should not involve wire fraud or credit card fraud ( ) Countermeasures should not involve sabotage of public networks ( ) Countermeasures must work if phased in gradually ( ) Sending email should be free ( ) Why should we have to trust you and your servers? ( ) Incompatiblity with open source or open source licenses ( ) Feel-good measures do nothing to solve the problem ( ) Temporary/one-time email addresses are cumbersome ( ) I don't want the government reading my email (X) Killing them that way is not slow and painful enough
Furthermore, this is what I think about you:
( ) Sorry dude, but I don't think it would work. ( ) This is a stupid idea, and you're a stupid person for suggesting it. ( ) Nice try, asshole! I'm going to find out where you live and burn your house down! (X) THANK YOU! ONE DOWN. MANY MORE TO GO.
Tried xrandr. Usual errors about BadMatch Tried xorg.conf Rotate, this and that with RandRRotation, ShadowFB, etc...
Thanks anyway, but I wasn't asking the Lazyweb for a solution. I don't think there is one, it's just not supported by Xorg. Not finding the answer after hours of Googling made the "Free" OS worth a lot less than the $40 I wound up spending for a commercial solution.
I was just pointing out that this release of Xubuntu was really nice from the perspective of someone who used Unix desktops for many years before finally just using them for servers. I couldn't use it in the long run though for lack of hardware support.
I've got a mix of systems at home. Debian, Windows, etc..
For a while my kitchen laptop (a 5 year old old Dell Inspiron) was running Ubuntu G.G. and I found it quite nice to use. This was my first desktop Linux system in about 4 years. It was responsive, easy to find things, and perfect for that application. (Lots of web browsing and some note taking.) I'd still be using it except...
Eventually, though, I had to install XP Home on the system. No amount of research, begging, pleading and tweaking in/etc/X11 could get the LCD display to flip upside-down. Which in the long term was necessary for an under-cabinet mount. $40 for Pivot Pro and re-installing the original XP load was worth the headaches.
I have almost 15 years of.NET experience. Back then we called it Win32.:)
To the GG[*]P:
Kids these days. Bah.
Pay your dues: spend years debugging shitty code, written by stoned company founders, in obsolete languages, on hardware that can only be repaired by buying parts on eBay, on obsolete architectures, for companies that nobody's heard of, in financial trouble, in cities you'd be hard-pressed to find on a map. Don't forget to spend your weekends and holidays learning the system top to bottom. From microcode to reporting. Everything. Learn the business model too. And do it for cut-rate rates just to get the break.
And be happy for it, goddammit.
(My break? Sales tracking, "Mr. R", CADOL, Tiger-8's, minicomputers, Contel, bankrupt 1993, Burton MI, for $17,500/year in 1989. Not much, even then.)
Before that? Data entry clerk at a different company. I punched freight bills all day long. 8 hours/day in a room full of middle aged gossipy women, keying bills of lading. Evenings spent reading the system manuals, learning it inside out, doing whatever I could to optimize my job. When not doing that? Hacking code on whatever computers I could lay hands on. Writing plug-ins for BBS's. Modules for the newly installed local library computers. Laying cable. Assembling desk-side computers.
If you're any good, I'd give you the break.
Don't expect good money and you will get the shittiest jobs I can find. Only become a programmer if it's what you really want to do. Do it for free. If you're in it for the money and a desk job keep moving, boy.
My parents live in the county, I went to university there, and travel there occasionally.
Doña Ana county is home to a boom town -- Las Cruces. And unlike places like California and Las Vegas the boom hasn't died out. Hospitals, shopping, roads, banks, and all kinds of other infrastructure are popping up all over.
Las Cruces (the county seat) is about 45 minutes from El Paso, TX. There's a fairly large university there (NMSU) and no shortage of people looking for work.
Best of all -- for a spaceport -- there's land near this infrastructure. Hundreds of thousands of acres of land, sparsely populated.
Slashdot Mirror
There are answers for these: location, location, location. Since the elevator should be located on the equator, simply build it inland, in geologically and weather stable region like central Africa. Of course, Africa's completely politically unstable and will probably remain so in our lifetimes.
I think the harder problem is space junk. Lots of posts here about how strong the cable needs to be to support the counterweight and cable cars. I think even more important is that the ribbon is going to be shot at with high energy missiles on a regular basis.
Let's say the material can take the occasional shot from a stray nut or hammer at orbital velocity. Or even small iron chunks at super-orbital velocity (meteors). It's still going to need thrusters along the way to dodge the occasional booster rocket, heat shield, or large rock floating by up there.
I saw the blinking favicon, and closed the tab unopened and unread.
Whatever was there wasn't worth the eyestrain.
Mod parent up.
Stories persist whether true or false and represent the oldest extant (nearly complete) texts in many languages: Genesis, the Epic of Gilgamesh, The Illiad, Beowulf, the Vedas, and the Book of the Dead to name a few.
Many modern humans will know of, part of, or all of at least one of these stories.
Whereas more practical texts have survived, but knowledge of them isn't as widespread. Not a lot of people can recite goat inventory from Ur or lists of Old Kingdom Egyptian rulers.
Ever get the feeling they're building a kludge all over again? Space Shuttle II -- Revenge of Thousands of Glued On Tiles and Strapping It to the Side an Ice-Covered Tank.
There was no way to passively dampen the vibrations? A simpler, cheaper solution? So instead they'll introduce another ton of lift weight and 17 additional motors and batteries to fail.
My prediction: in the first 50 launches this system will fail and the rocket will either shake the astronauts and payload apart (failure to dampen) or spectacularly shake the rocket apart (oscillate lopsidedly or out of synch with the vibrations).
With luck Slashdot will archive this long enough. Given that this is a NASA project, that might not be likely.
Sarcasm...off. I mean this:
Thank you for admitting that programming isn't your thing. Thank you for not subjecting your fellow programmers to years and years of bad code, grumpy job performance, and being a drag on other coders' lives. Thank you for letting our managers hire people who want to do this job, instead of those just killing time.
I'm sure you're a fine person, but thank you for not working here as one of my developers. You are too honest for management or sales, but I'm sure you'll find something good to do.
Now if we can only get other CS majors who shouldn't be programming out of the trenches, life might improve.
Daisy wheel and golf ball? They're not loud when compared to a barrel printer.
Barrel printer? They're not loud when compared to a chain printer. Until 1992 we had an IBM-1403 that we kept around just for re-printing the source code books every month.
(Yes, we kept the source code printed out for taking support calls in the programming department. It was easier to page through the source in book form to find out why things happened than to find the right floppy disks, load up the code, load up the editor, and then page through at 24x80... Documentation? Pffft! Spec? Pshaw!)
We had an upper-case only chain, though. So mixed-case text was always a bit of a puzzle to figure out. Fortunately the programming language was case insensitive.
Even the linefeed/pagefeed was loud.
PS: And don't fuck up the linefeed/carriage return sequence. At 75 inches / second a bad print job could ruin a box of paper in a few minutes.
Journalists have made entire careers out of producing this kind of schmaltzy crap. Observe..
If you want a real-life example, take someone like Mitch Albom. Please.
The article is wrong.
There is a full-scale Dymaxion House: in Dearborn, Michigan at the Henry Ford Museum. That a New Yorker writer couldn't turn that fact up with a quick Google search is disappointing.Two prototypes were built, and one was modified and lived in for several years by the Graham family. The rebuilt house is made from parts cobbled together from the other two, and some parts that had to be re-manufactured from the original plans. Tours are given through the Dymaxion House in the museum, and I've been several times.
When I bought laptops for the house in January, the same models with XP (instead of Vista) were $50 more each.
The real FAIL came later:
Thinking I could just get Vista, save $50, and re-load XP from Genuine XP install media (I had licenses to spare). Turns out XP wouldn't work. There were devices on the laptops (WiFi, sound, etc..) for which there were no XP drivers available. I wound up restoring Vista and spending the $100 I "saved" on an additional GB of memory for each system to make them usable.
This might explain:
The Detroit Red Wings, the closest thing to a winning "dynasty" in the days of free-agency hockey. (4 Stanley Cups in 11 years). (Red & White hockey sweaters.)
And the Detroit Lions... perennial losers, only a handful of playoff appearances in 40 years, and no chance of winning anything anytime in the forseeable future. (Blue & Grey [and black] jerseys)
Or it could be decades of lackluster mis-management by the Lions owners (the Ford family), and a passionate winning attitude from the competent Red Wings owners (the Illich family).
The False God of Backward Compatibility has Microsoft by the short hairs. Even new programming environments like .Net have Win32, Win16, and DOS lurking right around the corner. There's no fresh start anywhere in the Microsoft environment, everything reeks of DOS.
Which would have been find if DOS (Win16, Win32, etc..) were a multi-platform, extensible OS to begin with -- but it wasn't. It was a quick hack that lives on and on.
I'm a developer that works primarily in Windows, with 15 years of heavy-hitting Unix programming experience behind me.
Tactical nuclear weapons from space. It's the only way to be sure.
The scans have to be stored for criminal prosecution and accident/incident investigation.
[Now you're splitting hairs like any good software developer: "The software worked fine, it just never deployed because..." -- The project failed.]
The reason muni wifi didn't deploy as widely as expected, does not change the economics of the situation: the cost of the equipment, software, and administration will not come down until enough volume is produced. And a dozen or so major metropolitan areas represents a lot of volume.
There are isolated successes, true.
However many more have failed in places like Houston, Chicago, San Francisco, Philadelphia, Rhode Island, Orlando, Tempe, Portland, and closer to home (for me) Grand Rapids and Oakland County. This list isn't complete, of course. You could ask Earthlink for a better one...
Community and city-wide wifi projects everywhere are failing. In general they turned out to be more expensive, more cumbersome, and difficult to manage than originally promised. The county-wide wifi program where I lived stopped development last year because the vendor's pricing model proved unworkable (give away low-speed, sell high speed). Other communities are having similar problems.
To think that's *not* going to affect the cost of the remaining projects is just silly. Without the volume, the costs are going to go up for the projects that are still out there left undone.
The rules of the game are *ALWAYS* changing. That's life. We can tell you're upset, but quit your whining.
Managed Code is code intended for a virtual machine (like MS's CLR or Sun's JVM) that abstracts the hardware instructions away. Instead, the instruction set for the virtual machine is used. The Virtual Machine will provide "devices" and "memory" in a (hopefully) safe and portable way and take care of all of the dirty hardware business itself. Some VM's will actually take the VM instruction and turn it into actual hardware instructions as it's being executed (JIT) for speed, but that's not necessary.
Which isn't to say that Managed Code is a new thing: The USCD-Pascal p-code machine is remembered fondly by many, and the Zork games ran on a Z-Machine.
Interpreted code is a little stickier because it's been around a lot longer and has picked up some additional meanings. It can mean anything from the "Managed Code" described above to parsing (and possibly re-parsing) text lines of BASIC as they're run to process them in a giant state machine which "runs" the program.
Usually, interpreted code implies that there's no abstracted fully virtual machine underneath running the code, but possibly just a big jump-table pointing at native assembly-language (hand-coded or compiled) routines. Perl and Microsoft BASIC (basis of many of the old 8-bit BASICs) are two examples of interpreted code.
I've run into this a few times and it's easy to explain:
In the auto industry there are mechanics, powertrain engineers, and those guys that design bodies and interiors. (No bias from me at all!) You wouldn't want the guy picking paint colors and fabrics for the interiors to design your exhaust manifold; by the same token you don't want the guy who does the casting flow calculations for the engine block figuring out what the front grill should look like. These are not only different professions, but different kinds of professions.
Keep your nose out of the design business, please. If you're a good programmer or admin guy, you don't know much about marketing and have lousy taste. Admitting it is the first step.
Professor Farnsworth: Dear Lord, that's over 150 atmospheres of pressure.
Fry: How many atmospheres can this ship withstand?
Professor Farnsworth: Well it's a spaceship, so I'd say anywhere between zero and one.
Your post advocates a
( ) technical ( ) legislative ( ) market-based (X) vigilante
approach to fighting spam. Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.)
( ) Spammers can easily use it to harvest email addresses
( ) Mailing lists and other legitimate email uses would be affected
( ) No one will be able to find the guy or collect the money
( ) It is defenseless against brute force attacks
( ) It will stop spam for two weeks and then we'll be stuck with it
( ) Users of email will not put up with it
( ) Microsoft will not put up with it
(X) The police will not put up with it, anywhere other than Russia
( ) Requires too much cooperation from spammers
( ) Requires immediate total cooperation from everybody at once
( ) Many email users cannot afford to lose business or alienate potential employers
( ) Spammers don't care about invalid addresses in their lists
( ) Anyone could anonymously destroy anyone else's career or business
Specifically, your plan fails to account for
(X) Laws expressly prohibiting it
( ) Lack of centrally controlling authority for email
( ) Open relays in foreign countries
( ) Ease of searching tiny alphanumeric address space of all email addresses
( ) Asshats
( ) Jurisdictional problems
( ) Unpopularity of weird new taxes
( ) Public reluctance to accept weird new forms of money
( ) Huge existing software investment in SMTP
( ) Susceptibility of protocols other than SMTP to attack
( ) Willingness of users to install OS patches received by email
( ) Armies of worm riddled broadband-connected Windows boxes
( ) Eternal arms race involved in all filtering approaches
( ) Extreme profitability of spam
( ) Joe jobs and/or identity theft
( ) Technically illiterate politicians
( ) Extreme stupidity on the part of people who do business with spammers
( ) Dishonesty on the part of spammers themselves
( ) Bandwidth costs that are unaffected by client filtering
( ) Outlook
and the following philosophical objections may also apply:
( ) Ideas similar to yours are easy to come up with, yet none have ever
been shown practical
( ) Any scheme based on opt-out is unacceptable
( ) SMTP headers should not be the subject of legislation
( ) Blacklists suck
( ) Whitelists suck
( ) We should be able to talk about Viagra without being censored
( ) Countermeasures should not involve wire fraud or credit card fraud
( ) Countermeasures should not involve sabotage of public networks
( ) Countermeasures must work if phased in gradually
( ) Sending email should be free
( ) Why should we have to trust you and your servers?
( ) Incompatiblity with open source or open source licenses
( ) Feel-good measures do nothing to solve the problem
( ) Temporary/one-time email addresses are cumbersome
( ) I don't want the government reading my email
(X) Killing them that way is not slow and painful enough
Furthermore, this is what I think about you:
( ) Sorry dude, but I don't think it would work.
( ) This is a stupid idea, and you're a stupid person for suggesting it.
( ) Nice try, asshole! I'm going to find out where you live and burn your
house down!
(X) THANK YOU! ONE DOWN. MANY MORE TO GO.
Tried xrandr. Usual errors about BadMatch
Tried xorg.conf Rotate, this and that with RandRRotation, ShadowFB, etc...
Thanks anyway, but I wasn't asking the Lazyweb for a solution. I don't think there is one, it's just not supported by Xorg. Not finding the answer after hours of Googling made the "Free" OS worth a lot less than the $40 I wound up spending for a commercial solution.
I was just pointing out that this release of Xubuntu was really nice from the perspective of someone who used Unix desktops for many years before finally just using them for servers. I couldn't use it in the long run though for lack of hardware support.
I've got a mix of systems at home. Debian, Windows, etc..
/etc/X11 could get the LCD display to flip upside-down. Which in the long term was necessary for an under-cabinet mount. $40 for Pivot Pro and re-installing the original XP load was worth the headaches.
For a while my kitchen laptop (a 5 year old old Dell Inspiron) was running Ubuntu G.G. and I found it quite nice to use. This was my first desktop Linux system in about 4 years. It was responsive, easy to find things, and perfect for that application. (Lots of web browsing and some note taking.) I'd still be using it except...
Eventually, though, I had to install XP Home on the system. No amount of research, begging, pleading and tweaking in
I have almost 15 years of .NET experience. Back then we called it Win32. :)
To the GG[*]P:
Kids these days. Bah.
Pay your dues: spend years debugging shitty code, written by stoned company founders, in obsolete languages, on hardware that can only be repaired by buying parts on eBay, on obsolete architectures, for companies that nobody's heard of, in financial trouble, in cities you'd be hard-pressed to find on a map. Don't forget to spend your weekends and holidays learning the system top to bottom. From microcode to reporting. Everything. Learn the business model too. And do it for cut-rate rates just to get the break.
And be happy for it, goddammit.
(My break? Sales tracking, "Mr. R", CADOL, Tiger-8's, minicomputers, Contel, bankrupt 1993, Burton MI, for $17,500/year in 1989. Not much, even then.)
Before that? Data entry clerk at a different company. I punched freight bills all day long. 8 hours/day in a room full of middle aged gossipy women, keying bills of lading. Evenings spent reading the system manuals, learning it inside out, doing whatever I could to optimize my job. When not doing that? Hacking code on whatever computers I could lay hands on. Writing plug-ins for BBS's. Modules for the newly installed local library computers. Laying cable. Assembling desk-side computers.
If you're any good, I'd give you the break.
Don't expect good money and you will get the shittiest jobs I can find. Only become a programmer if it's what you really want to do. Do it for free. If you're in it for the money and a desk job keep moving, boy.
Impress me, and we'll talk.
And for a better introduction to process creation, I offer:
Mr. Peabody Explains fork()
My parents live in the county, I went to university there, and travel there occasionally.
Doña Ana county is home to a boom town -- Las Cruces. And unlike places like California and Las Vegas the boom hasn't died out. Hospitals, shopping, roads, banks, and all kinds of other infrastructure are popping up all over.
Las Cruces (the county seat) is about 45 minutes from El Paso, TX. There's a fairly large university there (NMSU) and no shortage of people looking for work.
Best of all -- for a spaceport -- there's land near this infrastructure. Hundreds of thousands of acres of land, sparsely populated.
It's a great place to build a spaceport.