Clouds, Computers and Composites: The New Crisis in Aviation

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Clouds, Computers and Composites: The New Crisis in Aviation
# 1  
Old 07-06-2009
Clouds, Computers and Composites: The New Crisis in Aviation

by Manuel Garcia, Jr., Counterpunch.org The recent loss of Air France Flight 447, an Airbus A330-200, has raised many doubts among the flying public and even some aviation professionals about the safety of the newest generation of passenger airplanes. These new airliners have composite materials replacing metal for many structural elements and control surfaces, and they [...]

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Solaris

Minor (I hope!) Crisis - E450 will not power up

UNIX Friends, Came in this morning to a downed E450 - thought it had been a power disaster. But wasn't! Machine had apparently shut itself down. All three power supplies are double-green, and case interlock switch is closed... As this is the first time we've had such a catastrophic(?)... (5 Replies)
Discussion started by: Dr Lou
5 Replies

2. Virtualization and Cloud Computing

Computing in the Clouds with AWS

Tim Bass 07-25-2008 02:34 AM The admin*team at The UNIX Forums*have been considering moving the UNIX and*Linux*Forums to the clouds - the Amazon Web Services (AWS) cloud.* Amazon EC2 is one option to scale the forums, which is a*LAMP application.* Amazon EC2 allows*us to rent dedicated... (3 Replies)
Discussion started by: Linux Bot
3 Replies

3. Virtualization and Cloud Computing

The Attack of the Spiders from the Clouds

Tim Bass 07-31-2008 08:09 AM We have seen a lot of discussions of cloud computing in the news recently, as a technology to permit “users to access technology-enabled services*without knowledge of, expertise with, nor control over the technology infrastructure that supports them.”* *This sound... (0 Replies)
Discussion started by: Linux Bot
0 Replies

4. UNIX for Dummies Questions & Answers

help : crisis situation !!

Hi I had deleted important files from my company server :( the server is HPUX and i don't know how to undo rm command or how to restore the files .. iam appreciate for any help Thanx ... (5 Replies)
Discussion started by: Eisa
5 Replies

5. Shell Programming and Scripting

Bourne Shell Scripting CRISIS

:( :( :( G'day all This is a desperate call to those out there who know anything about Bourne Shell scripting, as I'm in the middle of a crisis Pleae E-Mail me if you believe you can help (No spamming please) The sooner the better, if you're an aussie that lives in Victoria, I'll even... (20 Replies)
Discussion started by: Aussie_Bloke
20 Replies
Login or Register to Ask a Question
SVK::Command::Info(3)					User Contributed Perl Documentation				     SVK::Command::Info(3)

NAME
SVK::Command::Info - Display information about a file or directory SYNOPSIS
info [PATH | DEPOTPATH]... OPTIONS
-R [--recursive] : descend recursively DESCRIPTION
For example, here's the way to display the info of a checkout path: % svk info ~/dev/svk Checkout Path: /Users/gugod/dev/svk Depot Path: //svk/local Revision: 447 Last Changed Rev.: 447 Last Changed Date: 2006-11-28 Copied From: /svk/trunk, Rev. 434 Merged From: /svk/trunk, Rev. 445 You can see the result has some basic information: the actual depot path, and current revision. Next are advanced information about copy and merge source for this depot path. The result of "svk info //svk/local" is almost the same as above, except for the "Checkout Path:" line is not there, because you are not referring to a checkout path. Note that the revision numbers on "Copied From:" and "Merged From:" lines are for the source path (//svk/trunk), not the target path (//svk/local). The example above state that, //svk/local is copied from the revision 434 of //svk/trunk, and //svk/local was merged from the revision 445 of //svk/trunk. Hence if you do a "svk log -r 434 //svk/local", svk would tell you that //svk/local does not exist at revision 434. So far there is no easy way to tell the actual revision number of //svk/local right after a copy or merge. If the target is a depot path, or the corresponding depot path of the target checkout path is actually a mirroring path, the output of this command will look like this: % svk info //svk/trunk Depot Path: //svk/trunk Revision: 447 Last Changed Rev.: 445 Mirrored From: svn://svn.clkao.org/svk, Rev. 1744 So you can see this depot path is mirrored from a remote repository, and so far mirrored up to revision 1744. perl v5.10.0 2008-08-04 SVK::Command::Info(3)