Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

F-22 Avionics Require Inflight Reboot

chrisd posted more than 11 years ago | from the ctrl-alt-boom dept.

Technology 587

An anonymous reader writes "The Atlanta Journal & Constitution is fronting a lengthy piece on the USAF's new F-22 and its upcoming shootout with the existing fleet of F-15's & 16's. One line in the article really jumped out at me: 'When avionics problems crop up now, pilots must restart the entire system as if rebooting a personal computer.' I did some googling, and this is about as much as I could find: The hardware backbone for the system is the Hughes Common Integrated Processor, which, in turn, appears to be built around the Intel i960 CPU. I couldn't find a name for the operating system, but it appears to be written in about one and a half million lines of Ada code; more on the Ada hardware integration and Ada i960 compilers is here. Any Slashdotters working on this project? If so, why do you need the inflight reboot? PS: Gamers will be interested to learn that nVidia's Quadro2 Go GPU and Wind River's VxWorks Operating System are melded in the F-22's Multi-Function Display."

cancel ×
This is a preview of your comment

No Comment Title Entered

Anonymous Coward 1 minute ago

No Comment Entered


Well the in-flight reboot is required.. (-1, Troll)

Anonymous Coward | more than 11 years ago | (#3928787)

..when ACs do the FIRST POST thingy! Yahoo!

Yes! FP for tha ACs! (-1, Offtopic)

Anonymous Coward | more than 11 years ago | (#3929013)

CLIT can kiss my ass [adultgamereviews.com].

F-22 BSOD... (1, Funny)

Toasty16 (586358) | more than 11 years ago | (#3928792)

...Blue Skies of Death

Re:F-22 BSOD... (1, Funny)

Verizon Guy (585358) | more than 11 years ago | (#3928849)

I wonder if there are Ctrl, Alt, and Del buttons on the F-22 cockpit console?

Re:F-22 BSOD... (3, Funny)

Anonymous Coward | more than 11 years ago | (#3928957)

I wonder if there are Ctrl, Alt, and Del buttons on the F-22 cockpit console?

Sure, Ctrl is on the right control panel, Alt on the left, and Delete on the stick. :-)

Re:F-22 BSOD... (1)

H3XA (590662) | more than 11 years ago | (#3928986)

nah.... it is recommended that you radio Tech Support to be stepped though the diagnostic checklist of fault finding to discover the best course of action...... if you live long enough - C-A-D is pointless when the system AND the plane has crashed.

- HeXa

uhmm (-1, Offtopic)

Anonymous Coward | more than 11 years ago | (#3928793)


Microsoft (-1, Troll)

Anonymous Coward | more than 11 years ago | (#3928794)

Rumour has it that microsoft was involved in the development.

odd (-1, Troll)

muon1183 (587316) | more than 11 years ago | (#3928799)

I thought windows was the only operating system that crashed all of the time and needed to be restarted. Maybe they should have gone with something more tried and true, like *nix, rather than writing their own custom code. Rebooting the computer while flying a fighter jet sounds awfully foolish to me. What happens if the computer crashes durring combat.

Re:odd (0, Troll)

Verizon Guy (585358) | more than 11 years ago | (#3928843)

Maybe they should have gone with something more tried and true, like *nix, rather than writing their own custom code.

No offense, but... eat a dick.

*nix is not the solution to everything, no matter how much you may think this is the case.

F-22 Display Units (0, Troll)

Cardhore (216574) | more than 11 years ago | (#3928802)

That's what happens when you use ADA. If it was in Scheme we'd have no problem.

Openoffice 1.0.1 was released a few days ago and it didn't make the headlines. However, development releases of Linux do. Strange, eh?

Re: F-22 Display Units (1, Redundant)

Black Parrot (19622) | more than 11 years ago | (#3928845)

> That's what happens when you use ADA.

FYI, "ADA" is the American Dental Association.

You may be confusing it with the programming language, Ada, named after Ada Byron, Lady Lovelace, Lord Byron's daughter.

Hope it doesn't hang (0, Redundant)

BlindSpot (512363) | more than 11 years ago | (#3928803)

My system (Windows ME) hangs every time I try to use Restart. I hope their avionics system is more stable, or those pilots are in trouble...

Re:Hope it doesn't hang (0)

Anonymous Coward | more than 11 years ago | (#3928920)

you seriously use ME???

You sir, are a fucking fuckwit.

Why a reboot - because the creators are bozos (2, Interesting)

putaro (235078) | more than 11 years ago | (#3928805)

Long ago a friend of mine was working on an add-in computer driven compass for the F-16 for a big defense contractor. She called me up looking for graphics algorithms (she was the junior engineer on the project). She was fighting with her boss who wanted to install an FPU to speed up their circle drawing routine (this drew the compass rose onto the screen) while she thought they could speed it up by switching algorithms. Why did her boss want an FPU - well, because software sine and cosine routines were too slow. (BTW, the circle was always the same size and just the tick marks actually moved).

Bresenham's (2)

EnglishTim (9662) | more than 11 years ago | (#3928824)

Please tell me you told her about Bresenham's integer circle drawing algorithmn...

Re:Bresenham's (1)

Isle (95215) | more than 11 years ago | (#3928853)

Please tell me, they stopped redrawing the whole thing..

If it is static why try to render it at all?

How I solved this for a heads up display - 15 ya (5, Insightful)

jerryasher (151512) | more than 11 years ago | (#3928861)

Sine, cosine? Assuming you have a line draw routine and a raster display, none of that is needed.

About fifteen years ago for a prototype heads up display I had the same exact problem: draw the tick marks for a compass rose with no memory and no time. There was no scaling of the circle, only rotation about a fixed center.

After some though, what I did was to store in a table the tickmark endpoints for 45 degrees of arc (I recall it being 22.5 and not 90 degrees) for all the displayable rotations of that arc. Then at runtime, my compass rose routine would exploit the symmetry of the situation to determine the endpoints of all the other displayable tickmarks.

It used very little memory since at any point in time we only displayed tick marks at 5 degree intervals. Therefore 45 degrees of those would be 9 tick marks, or 18 ints (two ints per tickmark). At 5 degree intervals with a resolution of 1 degree, you only need a table of 5 x those 18 ints, or 90 ints all told.

I always loved the 3am epiphany!

Re:How I solved this for a heads up display - 15 y (2)

jerryasher (151512) | more than 11 years ago | (#3928874)

Ah, 3am then, but now I'm all done by midnight.

I needed four ints per tickmark then or most likely 180 ints all told. Of course you should be able to make these shorts as store not actual points, but vertical and horizontal offsets from the center of the rose.

Re:Why a reboot - because the creators are bozos (0)

Anonymous Coward | more than 11 years ago | (#3928896)

My favorite circle-drawing trick is one even faster than bresenham's in many cases, single-stepping from one line to another is just calculating sequentially-calculatable values for the squares of the X and Y, so other than one squaring operation (radius squared) the entire algo turns into two adds, and two subs, to get the X/Y coords for each step of the circle, then single axis-aligned lines between them.

Of course, if you're dealing with anti-aliased circles, all of it still works, just gets a little wonky on the math and runs out of registers on an x86-alike, need a 68k or Arm-series CPU to pull it off easilly, needs about 10 ot 11 registers to do it all in-register then, including anti-aliasing.

I had to say it... (1)

qnonsense (12235) | more than 11 years ago | (#3928806)

Not to be cliche or anything, and I'm sure you could see this one coming a million miles away,

but what happens when it crashes?


Re:I had to say it... as well (0)

Anonymous Coward | more than 11 years ago | (#3928831)

Sorry, username/password incorrect, plase try again
*damn* what was that new password?

Re:I had to say it... (5, Funny)

Anonvmous Coward (589068) | more than 11 years ago | (#3928908)

Not to be cliche or anything, and I'm sure you could see this one coming a million miles away,

but what happens when it crashes?

This reminds me of some trouble I got into in high-school once: Anybody remember Channel 1? It started around 1990-1, and it was a news channel that some schools got. Each episode had a trivia question just before a commercial break.

One day, they asked "What is the most common cause of plane crashes?". I hastily and enthusiastically responded "gravity!!" I got in real serious trouble that day, I forgot that the teacher was also a pilot. The real answer was 'human error', which I had illustrated that day when my teacher shot me down to the principal's office.

Finally! (3, Funny)

decaying (227107) | more than 11 years ago | (#3928807)

My years of Comp Sci with Ada as the language of choice (Uni's not mine).... I struggled with it, and grew to hate it.....

At least I know who uses the bloody thing.... The tutors never could.....

Re:Finally! (3, Insightful)

Jeppe Salvesen (101622) | more than 11 years ago | (#3928931)

Ada is excellent for this sort of stuff. It's been designed for implementing anal designs. That is exactly what is required in military systems.

I also thought Ada is a good language for teaching in Uni. You don't like it, but it will teach you a lot of important concepts, from its strong typing amongst other things.

That being said, it's not the right tool for most software development being done currently.

Boeing's Avionics press release (5, Informative)

Perdo (151843) | more than 11 years ago | (#3928809)

Boeing, responsible for integrating the F-22 Raptor's advanced avionics, has been testing software packages in both its avionics integration lab, or AIL, since 1998, and on its 757 Flying Test Bed, or FTB, since March 1999.
Both the AIL and FTB are helping reduce avionics risks and contain development costs by enabling extensive evaluation and troubleshooting before full avionics are ever installed on the F-22. Testing in the AIL and aboard the 757 FTB has allowed for early delivery of avionics Operational Flight Packages, or OFPs, to the F-22 test aircraft.

To date, Boeing has completed more than 21,000 hours of avionics testing in the AIL and 800 hours on the FTB.

Despite an accelerated delivery schedule for the year 2000 to support the Defense Acquisition Board, or DAB, requirements, the Boeing Avionics Integration team was able to integrate, test and deliver all Operational Flight Programs, or OFP's, ahead of plan. This included delivery of the Block 1.2 OFP on July 5, 2000, and Block 2/3S OFP on July 20, 2000. The AIL was also able to deliver the Block 3.0 OFP Engineering version to the Avionics Flying Test Bed aircraft a month ahead of schedule (Sept. 4, 2000) to allow for early testing and maturing of the OFP, which resulted in the first demonstration of multi-sensor fusion (Sept. 13, 2000).

The most significant accomplishment of the AIL for 2000 was the delivery of the Block 3.0 OFP, the first fully integrated avionics package, to F-22 aircraft 4005 on Nov. 21. This was a critical milestone since the Block 3.0 OFP was the first complete avionics software package to be flown on the F-22 aircraft, one of the most challenging DAB milestones accomplished to date.

The Boeing Avionics' Systems Engineering team's performance testing on the radar has resulted in all Test Performance Measurements, or TPMs, meeting or exceeding specification requirements. A significant milestone was reached on Nov. 15, 2000, when Raptor 4004 conducted its first flight, and targets were successfully detected and tracked in the air. Performance of the radar system was described as "eye-watering" by the pilot who flew the mission. A second major milestone occurred on Jan. 5, 2001, when Raptor 4005 flew for the first time utilizing Avionics Block 3.0 with the full complement of Radar Modes incorporated. Once again, targets were detected and tracked at long range, and the radar performance was outstanding.

Avionics Radar and Power Supplies Production activities continue to be a high priority. All shipments for PRTV I have been completed, PRTV II shipments are well under way, and hardware manufacturing for Lot 1 has begun. In the area of affordability, the implementation of Boeing-funded process improvements on several components of the radar/power supply systems, to include the T/R module and circulators, have been a tremendous success. The predicted cost savings have been substantiated in the first three production contracts and the targeted cost savings of $350 million dollars over the production life have been legitimized.

The next critical avionics milestone is delivery of Block 3.1 avionics. Block 3.1 will provide additional functionality to the F-22 Raptor and allow it to accomplish a significant amount of flight testing. Block 3.1 is scheduled to be delivered to Lockheed Martin this fall.

Overall, the F-22 avionics program is very much on target in the areas of performance, cost and schedule. The avionics packages have been performing exceptionally well, and all major milestones have been met on or ahead of schedule.

Re:Boeing's Avionics press release (3, Insightful)

philipsblows (180703) | more than 11 years ago | (#3928859)

According to what this says, the avionics package meets or exceeds expectations. Now, this is not an MS bash, but I can recall of the top of my head that our intelligence services have database software that can only search on one term that probably met or exceeded expectations, and there's that ship that had to be towed back to port due to some NT failures.

Now this is more of an MS bash... people have come to expect system failures, and I've read admissions that 5-9's uptime is just too difficult and expensive a goal, and so-on, and of course this mostly points to MS desktop and server software. I wonder if people who sit at desks and write specs all day for military projects decided that only having to reboot now and then exceeds expectations as set by people not flying in the aircraft.

I'll probably get modded down, but I just think this sort of thing (Boeing's press release, the actual performance as reported, and the overall state of technology in our government) is a bit troubling and it doesn't appear to be getting better.

Re:Boeing's Avionics press release (4, Interesting)

Anonvmous Coward (589068) | more than 11 years ago | (#3928921)

"Now this is more of an MS bash... people have come to expect system failures, and I've read admissions that 5-9's uptime is just too difficult and expensive a goal, and so-on, and of course this mostly points to MS desktop and server software"

That's an interesting read, my company chose Windows 2000 for stability as desktop machines, and we're doing fine. 19 desktops and laptops, all running 2k. My job is to maintain them, and I find way too much time to post on Slashdot. ;)

We've also got an NT4 webserver running IIS, and it's been up for 3 months. It would have been up longer except I had to shut the box down to move it.

I'll tell you something, it was a huge relief to go to 2000 from 98. Nobody bugs me about anything anymore. We have computers running all weekend processing video data. We haven't had an 'over the weekend crash'. We'll have 4 video files going at once, two per processor, and they'll all be done by Monday. As you can see, we beat our machines pretty hard sometimes.

*Thought it'd be nice for you to hear from somebody who's had good experiences with MS for a change.*

I've drifted off topic a bit. Sorry. The point I'm basically making is that Windows 2000 is a fine OS and would probably be up to the job, at least run-time wise. I know that comment's going to draw criticism, but oh well. I've worked around a ton of these machines for the last two years and you're not going to change my mind about it. Heck, I have a computer in my bedroom right now capturing TV shows as a home-brew Tivo. Hasn't been rebooted in over a month. Not bad given how buggy the TV drivers are. Heh.

Re:Boeing's Avionics press release (2)

forgoil (104808) | more than 11 years ago | (#3928990)

Those who would criticise you must be pretty stupid. You simply tell your experience with win2k. I have found it to be a very stable OS as well, and any problems have more usually been a case of bad hardware/drivers in my experience.

Windows XP has also been really stable for me (and others). I have 10 days of uptime right now, without a problem. I only reboot for updates, and I do that at convienient times. The server 10 feet away only boots when need to fiddle with its hardware (behind a firewall after all). Win2k is just as stable as the two debian machines besides it.

Stop thinking that all windowses are as stable as Win9x, it is just not true. It would be like saying MacOS X is crashing all the time because MacOS 7.x did. Lying after all doesn't give good arguments in the long run. Let it be sufficient to say that Linux is stable and leave it at that, don't make such a point out of it being more stable than Win9x, nobody is speaking about how well Linux 1.2 does these days do they?

That said, I just installed Gentoo 1.3b at home, all the other distros are now 0wned;)

IMHO the USAF has more acronyms than M$ (1, Funny)

InsMonkey (324276) | more than 11 years ago | (#3928885)

Apparently one cannot even speculate about modern weaponry without falling victim to TMFA (Too Many Fucking Acronyms). I've often debated over who's TMFA was worse: Micro$oft or the guv'ment. Perdo here is really making a strong case for the latter.

Re:IMHO the USAF has more acronyms than M$ (0)

Anonymous Coward | more than 11 years ago | (#3928945)

The only thing they have more of is forms.

Re:IMHO the USAF has more acronyms than M$ (2, Flamebait)

Perdo (151843) | more than 11 years ago | (#3928956)

Microsoft Acronyms:

http://www.microsoft.com/hwdev/resources/glossar y. asp

Government and Military acronyms:

http://www.ulib.iupui.edu/subjectareas/gov/docs_ ab brev.html

And the Winner is:

Not us.

Please reboot... (5, Funny)

Subcarrier (262294) | more than 11 years ago | (#3928812)

Apparently, the reboot is only necessary after discharging ammunition. The hardware configuration wizard will pop up and instruct the pilot to reboot the system in order to activate the changes.

Re:Please reboot... (2)

Anonvmous Coward (589068) | more than 11 years ago | (#3928926)

He missed his target anyway. The pilot didn't realize he had to be logged in as Administrator to fire the guns in the first place.

Duh.. (4, Funny)

Malduin (207683) | more than 11 years ago | (#3928813)

If it requires an inflight reboot, there's no doubt what OS it's running. Gotta be Win98. I can see the MS tech support call now..

MS Support: "Thank you for calling Microsoft Customer support. How may I help you?"
Pilot: "Uhh.. I'm spiraling towards the earth, both my engines are out, and my display says 'General Protection Fault' in white text on a blue background."
MS Support: "And what is the system model?"
Pilot: "The the F-22 jet.."
MS Support: "Oh yes, there are known issues that we will not admit to with that particular system. To temporarily fix the problem, simply reboot. Or, if the 5 minute boot time is too long, may I personally recommend that you eject. However, you will have to purchase another license of Windows 98 for $1000 since jet fighter crashes are not a valid reason to receive a new license."
Pilot: "@#$*(! Microsoft!"
MS Support: "Thank you and have a nice day!"

Re:Duh.. (1)

yatest5 (455123) | more than 11 years ago | (#3928934)

If it requires an inflight reboot, there's no doubt what OS it's running. Gotta be Win98. I can see the MS tech support call now

Yay, first irrelevant MS post! It even states what the OS is written in.

Re:Duh.. (5, Funny)

sql*kitten (1359) | more than 11 years ago | (#3928940)

If it requires an inflight reboot, there's no doubt what OS it's running.

RH support: Thanks for calling Red Hat! How may we help you?
Pilot: "Uhh.. I'm spiraling towards the earth, both my engines are out, and my display says 'kernel panic' in white text on a black background."
RH Support: "And what is the system model?"
Pilot: "The the F-22 jet.."
RH support: If you read linux-kernel-bugtraq, you will see that you should have patched your kernel to 2.4.19-pre-alpha-revision-d before takeoff. But no problem, this is Linux after all. Do you have another F22 on your LAN? Just telnet in from there, su to root and restart sendmail.
Pilot: @#$*! Redhat! I'm switching to Debian if I survive!
RH support: Can I interest you in any RHAT?

Re:Duh.. (5, Funny)

Bartmoss (16109) | more than 11 years ago | (#3929009)

telnet? on a wlan? better use ipsec, or the enemy will have your f-22's passwords in no time.

F-22 HUD Display: "Your System has been 0wned."


[xdfgf] Porn: Animal Sex (-1, Troll)

Anonymous Coward | more than 11 years ago | (#3928815)

I lived in the upper floor of one of those converted houses on the
south side of town. It was one of those changing neighborhoods so
it was real cheap rent. My landlord had the bottom floor and I had
the second floor. It was a great place because it was cheap and the
only thing wrong with it was I could hear his damn dog barking at
night at everything thing that moved. I wondered why the
Sergeant couldn't keep his damn dog quite at night. Every time
they dog would carry on all night I thought I was determined I
would stop by and complain on the way to work. By morning I
never had the guts to face the Sergeant. He would always be out
early sitting on the porch with Bruno his dog. The dog would lay
there chained and they both just watch people coming and going.
They never seemed to move except when Sarge would take a sip
of beer or the dog would wag his tale.

Looking at the Sergeant it seemed like such a waste. He was
retired but he was still one hell of a hunk. When he had retired
from the force he had moved back to his parents empty house. He
told me at first he wanted to sell it but with the neighborhood
going the way it was he could never get what it was worth. Well I
hoped he would keep it for a long time because it was cheap rent.
Besides I loved looking at that horny bastard running around in his
skivvies. The one thing he had in conmen with that dam dog of
his was they were both really hung and horny beasts. Well once at
work I would put all that our of my mind. That night when I got
off the bus I could see the flashing lights in front of the house.
Rushing in I saw the Sergeant on a gurney being lifted into the
ambulance. Grabbing my hand he begged me to take care of his

I thought Damn him, now I was going to half to be Bruno's
nursemaid. Going in I was at least glad the door to his apartment
didn't lock. The Sergeant had never put locks on any of the doors.
The only door that locked was the front door. For all practical
purposes the house was still a single family dwelling. As soon as I
pushed open the French doors into the living room Bruno was on
me licking my face. It was as if he knew I'd come in to take care
of him. As moved toward the kitchen Bruno followed behind
nosing my ass. Pushing him away I rummaged around finding this
big bag of dog food. Pouring some of the food into his dish I
looked at him and added more. He was one damn big beast.

After giving him water I left the door to the sergeants apartment
and went to my place to eat. I had hoped to shower and go out
cruising tonight but carrying on with that damn dog had taken so
much time. Now all I could do was take a quick shower, have a
couple of beers and watch television. I was in my shower when I
remembered seeing that big TV set the Sergeant had in his living
room. Pulling on my PJ's and padding down to his apartment I
slipped into his apartment. Bruno was at the door waiting for me.
Leading him to the kitchen door I let him out to do his duty. Then
rummaging in the Sergeants refrigerator I found a well stocked
supply of beer. Well I figured if I am going to baby-sit his dog I
might as well drink his beer.

I was just about to close the box when I spotted a line of little
bottles on the shelf on the refrigerator door. Picking up one of
them I had to laugh. The old bastard had a years supply of rush on
hand. I bet he was every girls nightmare or delight with that horse
cock of his. I had just settled down to find something to watch
when I heard Bruno scratching on the door. Getting up and letting
the dog in I went back to find something to watch. I was surprised
the Sergeant didn't have cable or a dish. That was when I spotted
the Video tapes. Pulling out a couple of them I damn near shit.
They were all porno tapes of men. Going through them I knew I
was going to have a real good time tonight. Pushing in a tape
called Foxhole buddies I sat back and relaxed with a beer. As the
credits and warning sped past I began to get a hard-on just thinking
of that old bastard and his porno tapes. Pushing my Pajamas down
I sat there naked as the action began on the screen. Damn he had a
good tape, I wondered how many more of them was in there.
Getting up and crawling over I began checking out the supply of
tapes. Then I felt that wonderful feeling of a tongue working my
ass. It felt so good I spread my legs giving him a good shot at my
ass. That was my big mystake and the damn dog took that to be
submission and he was on my ass with his paws around my sides.
That damn beast was trying to fuck me.

Trying to push him off the dog let out a low growl and I realized
there was no fighting him if I didn't want to be bitten. Bowing my
head I though how bad could it be getting fucked by a dog. He
fished and poked around a few seconds and then I felt him make
entry. It was real strange as he pumped and wiggled getting into
me. Spreading my legs wider and kneeling forward my head on the
ground I gave him his best shot. Finally he was in and pumping
and I was loving it. That's when it started, I felt the swelling of his
knot and I knew I was in deep shit. Trying to pull away it was two
late, he'd tied to me. Gritting my teeth from the pain of the knot
swelling in me he began his staccato pumping filling me with his

I never realized it took a dog so long to cum but he kept at me for
the better part of a half hour. Finally turning on me we were butt
to butt and then he began slipping out of my ass. Coming around
and licking at my face he lay down beside me. He had accepted
me as his bitch now. Moving into the bathroom I began washing
my as. I was seeping his cum and my ass was sore as hell. Finally
getting cleaned up I went back to the TV. Somehow watching two
studs fucking wasn't that exciting now, I had just been the bitch for
a Doberman. Sliding down to the floor and putting my arms
around Bruno he looked up and me and licking my face sent to
sleep. I lay next to him until the tape finished and decided to call it
a night. It had been one wild experience tonight.

I went to sleep then like a little baby, if anything I liked being a
bitch for that damn dog. It was about midnight when I felt this
tongue on my face and waking I started to say something when his
tongue slipped into my mouth, Damn it all to hell now the dog
was French kissing me. Laughing then I began licking and sucking
back. I was a real first class bitch. Sliding out of bed and
spreading my legs I was going to give him what he wanted. I
knew what to expect now and when I felt the swelling of his knot I
just gritted my teeth waiting for that hot lush filling of cum as he
began fucking me. We stayed coupled for a long time and then
when he turned and pulled out of me he began licking me clean.
Shivering from the thrill of his course tongue I'd never been on
such a trip in my life and I loved it.

Pulling Bruno up in bed then we both went into a deep sleep. He
had me up at dawn to let him out and then after giving him
breakfast I told him I had to go to work. God, now I was talking to
the damn dog like he understood me. All that day at work I though
about being a bitch for that dog. I know I should have been
ashamed but I really liked being fucked by a dog. I even liked
kissing him. Stopping at a Wendy's for some burgers and fry's I
was eager to get home to Bruno. As I let myself in he was on me
in a flash. Laughing and dropping my food I hurried to let him out.
He was out and back in a flash. I knew damn well why he wanted
back in. Reaching down and feeling his cock as it began coming
out of its sheath

I began stripping telling him we would be in real
trouble when the Sergeant came home. Getting on my knees he
was on me in a second. As his paws came around me I could feel
him working his cock into my ass. I was getting good at being his
bitch. It was when we were tied and he was pumping my ass I
heard the front door opening. I tried to pull out first, and Bruno
started growling, then when I tried to crawl away he just hung on
and I pulled him across the kitchen floor still fucking me. That
was when I saw these boots and then looking up saw the grinning
face of the Sergeant. You really are taking care of Bruno aren't
you boy. As he moved toward us Bruno let out a growl warning
him to stay away from his bitch. Chuckling he sat down at a
kitchen chair and just watched. I was mortified as he just sat there
watching me getting my ass fucked by his dog.

Finally Bruno turned and as his knot went down released me. I
was going to stand when he pushed me back down saying he
wanted sloppy seconds. He was out of his fatigues in a second and
naked ready for action. Staying on my knees then and spreading
my legs I felt his cock sliding into my ass. He was really and
animal as he rammed his cock into me and as he began slamming
into me like a bitch in heat. Bruno not to be outdone by his master
and mounted my face and began working his cock into my mouth.
Holding the knot back I let him fuck my mouth. We stayed like
that on the floor as he continued to cum again and again saying I
was the best piece of ass he'd ever had. Finally pulling out of me I
could stand then. I had been so damn hot I had shot my load all
over the floor and Bruno was cleaning it up now.

The Sergeant then went over to the counter and pulling a drawer
open pulled out a collar. Putting it around my neck he asked me if I
wanted to be their bitch. As we sat there that evening he said I
should bring my things down and live with him and we would rent
the upstairs. Laughing I suggested we might like to put locks on
the doors now. Over that next week we fell into an easy routine. At
night Bruno would fuck me and then the Sergeant always got
sloppy seconds. Then we would watch Videos and when we would
to bed and the Sergeant would fuck the hell out of me. He was all
man and I was all bitch. I began to think of him now as my master.
When the Sergeant showed the upstairs apartment to this young
man I was thrilled when the man ask if he could bring his dog.
Pulling me close to him he said he had a male dog and a bitch and
we loved dogs.

They guy looked at Bruno and then at me with my dog collar and
with a smile said he understood. Perhaps he could breed his dog to
the bitch. Sergeant said that should work out just fine with him.
Then the guy said he thought he was going to love living here.

If Slashdotters were working on this... (1, Funny)

Anonymous Coward | more than 11 years ago | (#3928816)

they sure wouldn't be able to say anything about it.

Drivers? (1)

Stonent1 (594886) | more than 11 years ago | (#3928819)

Yeah and all the flight sim pilots claim that getting shot down was due to lag induced by running an old set of Detonator drivers and not by getting sniped.

Re: Drivers? (3, Funny)

Black Parrot (19622) | more than 11 years ago | (#3928858)

> Stonent Imagine a Beowulf cluster of whatever this story is about!

They already thought of that. You see, while they rarely mention it at air shows, the realy reason airplanes fly in formation is because those "formations" are actually high-availability clusters for their avionics software.

who knows about obscure custom computing? (0)

Anonymous Coward | more than 11 years ago | (#3928822)

This guy does [slashdot.org]. This guy does!

You're digging hard... (1)

Ironpoint (463916) | more than 11 years ago | (#3928823)

But nope, can't find Win98 here. Sorry, maybe check those cash registers at target. I think maybe those bank signs that tell the temperature might run in Win95. You'll find something.

Why FreeBSD is dying by poopbot (-1)

adexonq (587094) | more than 11 years ago | (#3928829)

The End of FreeBSD

[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]

When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.

Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.

FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.

It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.

So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.


I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.

From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.

There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.

Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.

Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?


To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.

To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's when you get distracted by the politickers that they sideline you. The tireless work that you perform keeping the system clean and building is what provides the platform for the obsessives and the prima donnas to have their moments in the sun. In the end, we need you all; in order to go forwards we must first avoid going backwards.

To the paranoid conspiracy theorists - yes, I work for Apple too. No, my resignation wasn't on Steve's direct orders, or in any way related to work I'm doing, may do, may not do, or indeed what was in the tea I had at lunchtime today. It's about real problems that the project faces, real problems that the project has brought upon itself. You can't escape them by inventing excuses about outside influence, the problem stems from within.

To the politically obsessed - give it a break, if you can. No, the project isn't a lemonade stand anymore, but it's not a world-spanning corporate juggernaut either and some of the more grandiose visions going around are in need of a solid dose of reality. Keep it simple, stupid.

To the grandstanders, the prima donnas, and anyone that thinks that they can hold the project to ransom for their own agenda - give it a break, if you can. When the current core were elected, we took a conscious stand against vigorous sanctions, and some of you have exploited that. A new core is going to have to decide whether to repeat this mistake or get tough. I hope they learn from our errors.


I started work on FreeBSD because it was fun. If I'm going to continue, it has to be fun again. There are things I still feel obligated to do, and with any luck I'll find the time to meet those obligations.

However I don't feel an obligation to get involved in the political mess the project is in right now. I tried, I burnt out. I don't feel that my efforts were worthwhile. So I won't be standing for election, I won't be shouting from the sidelines, and I probably won't vote in the next round of ballots.

You could say I'm packing up my toys. I'm not going home just yet, but I'm not going to play unless you can work out how to make the project somewhere fun to be again.

= Mike


To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. -- Theodore Roosevelt

- posted by poopbot: crapflooding since 7/8/02

T1U9gAGg0d Post #345

Lockheed's Avionics Press Release (2)

Perdo (151843) | more than 11 years ago | (#3928830)

The requirements for the F-22's avionics system are derived from the F-22 Weapon System Concept, the guiding design principles for the aircraft's overall design. The integrated avionics system is one of the essential elements, along with stealth, maneuverability and supercruise, which will give the F-22 the tactical advantage against the threats of the future.

The F-22's avionics suite features extensive use of very high-speed integrated circuit technology, common modules and high-speed data buses. The avionics suite is an advanced integrated system that allows the pilot to concentrate fully on the mission, rather than on managing the sensors.

The avionics system is now flying on the F-22, and the advanced Block 3.0 software, which provides nearly full sensor and avionics functionality, began testing on the Raptor in early 2001.

Technologies incorporated in the F-22 include:

A common integrated processor (CIP), a central "brain" with the equivalent computing throughput of two Cray supercomputers

Shared low-observable antennas

Ada software

Expert systems

Advanced data fusion cockpit displays

Integrated electronic warfare system (INEWS) technology

Integrated communications, navigation and identification (CNI) avionics technology

Fiber optic data transmission.

Re:Lockheed's Avionics Press Release (2, Informative)

Perdo (151843) | more than 11 years ago | (#3928910)

"A common integrated processor (CIP), a central "brain" with the equivalent computing throughput of two Cray supercomputers"

Um.. No:

ftp://download.intel.com/design/i960/perform/272 95 003.pdf

(Intel's i860 performance brief)

Re:Lockheed's Avionics Press Release (2)

KILNA (536949) | more than 11 years ago | (#3929028)

They didn't say which two Crays. Perhpas a couple of 'em while powered-off?

F-22 "avionics" (4, Interesting)

sluggie (85265) | more than 11 years ago | (#3928832)

Sorry, but if you have to reboot the ENTIRE avionics system of a F-22 you're fucked to say mildly.

This plane is always in a controlled stall, the movements of the rudder to prevent it from crashing are calculated every second this bird flys, the pilot just decides in which directions the plane goes, but the task of keeping it up is left to the CPU.

So, if you just "reboot" this sucker for a second the plane would plummet like a stone, no matter how strong it's pushed forward by the engine or what the pilot does.

What I can imagine that the pilot would have to restart some none vital components of the main computer.
Such as the timing of the green/red flashlights or his seat heating. ;)

Re:F-22 "avionics" (1)

Isle (95215) | more than 11 years ago | (#3928868)

The aerodynamics system is seperate. It is the weapon system they need to reboot.

(I dont think the aerodynamic/anti-stall system even has a general processor or an operating system.)

Re:F-22 "avionics" (5, Informative)

Moofie (22272) | more than 11 years ago | (#3928878)

The flight controls are run by totally different hardware. It's the sensor and weapons systems that are at issue here.

Typically, when aero geeks talk about avionics, we're not talking about the flight control systems, even though those systems are now "aviation electronics".

Is this bad? Yes. Does it need to be fixed? You betcha. But don't worry about the planes not being able to keep the pointy end into the wind. That part seems to be working fine.

As an aside, the little anecdote about the test pilot intentionally making RADICAL configuration changes in-flight (moving fuel around, opening weapon bay doors, and wacky control inputs) producing only an easily-recoverable spin is a testament to the airplane's superb design. I mean, you do stupid things in ANY airplane and it'll bite you. The sign of a really GOOD airplane is that it then forgives you and doesn't splatter you all over the terrain.

Re:F-22 "avionics" (5, Informative)

PD (9577) | more than 11 years ago | (#3928882)

You sure about that? A stall is a condition in which the airflow over the wing becomes turbulent and separates from the upper surface of the wing. That destroys lift until the smooth airflow is restored.

To say that the F-22 is in a controlled stall is just ridiculous. The proper way to state things is that the F-22 has relaxed static stability, which has nothing to do with a stall.

Re:F-22 "avionics" (2)

sluggie (85265) | more than 11 years ago | (#3928901)

Alright I'm sorry, since english is not my native language I ceased to get the right definition of stall.

What I meant to say was that the CPU always has to do litle rudder movements to prevent it from falling down, or the other way round: the pilot wouldn't be able to keep the plane up with his stick alone.

And yeah, I know there's some subliminal punchline in "keep the plane up with his stick" ;)

Re:F-22 "avionics" (2)

Grab (126025) | more than 11 years ago | (#3929048)

Not a "stall". A stall is where the plane flies too slow, the wings no longer produce enough lift to keep it in the air, and the thing basically just drops out of the sky.

The processor doing its little movements just means that it's an unstable system. Nothing new there, the SR-71 also requires an active control system to keep it going in a straight line, and that was designed 20-some years ago.


It's a safety feature. (5, Funny)

Black Parrot (19622) | more than 11 years ago | (#3928833)

Everyone knows that frequent reboots prevents crashes.

Re:It's a safety feature. (0)

Anonymous Coward | more than 11 years ago | (#3928903)

I'm not sure if you were kidding but that's exactly why it's being done.

I'm surprised that there aren't more people here who work on life-critical realtime embedded systems and would point this out. Because it is impossible to write faultless non-trivial code (admit it!), it's a standard practise to have the system reset itself once in a while. Of course the reset time is nothing like on your ordinary PC, but is measured in milliseconds.

Similar to Mars Pathfinder (5, Interesting)

Deton8 (522248) | more than 11 years ago | (#3928837)

In 1997 the Mars Pathfinder probe had a problem with VxWorks and priority inversion. Perhaps the F22 is having something similar -- whenever you have a RTOS, the designer must try to anticipate when it's safe to block real time interrups and when it isn't. I don't know anything about the F22, but it's easy to imagine that it has hundreds of input sources with all sorts of latency requirements. AFAIK, it all comes down to some humans trying to balance these conflicting needs. Clearly they don't always get it right.

Re:Similar to Mars Pathfinder (5, Informative)

ebbe11 (121118) | more than 11 years ago | (#3928913)

In 1997 the Mars Pathfinder probe had a problem with VxWorks and priority inversion.

Priority inversion is never caused by the OS, only by the interrupt/task priority design. So VxWorks shouldn't be blamed here.

There are RTOS'es that try to avoid priority inversion by temporarily raising the priority of the blocking task to the same priority as the task being blocked. This may at first look like a good solution but if the priority bumping happens too often, "medium priority" tasks may get starved because the low priority task is really running at high priority.

Perhaps the F22 is having something similar -- whenever you have a RTOS, the designer must try to anticipate when it's safe to block real time interrups and when it isn't.

Blocking interrupts may mean missing interrupts. This is a very dangerous thing to do in hard realtime systems, because what you don't know may not only hurt you but may actually kill you. If it is necessary to disable interrupts to get the system running, the system design is horribly flawed.

Re: Why do you need the inflight reboot? (5, Funny)

back@slash (176564) | more than 11 years ago | (#3928838)

It's so todays pilots feel more at home with their fighter jets computer of course, having grown up with 90's software. You haven't seen the changes to communication protocal yet have you?

typical conversation between pilots
pilot1: u missed ur target fag u suck
pilot2: stfu idiot i'll kik ur ass
pilot1: lol ill show u how to shoot missles loser... im gonna get that camper anti-aircraft fag
pilot2: haha u missed 2... u couldnt even hit ur fat momma

and so forth....

Re: Why do you need the inflight reboot? (2)

Anonvmous Coward (589068) | more than 11 years ago | (#3928929)

They're having trouble recruiting new pilots today because they're sick of campers sitting there using their anti-aircraft guns.

Redundant (4, Interesting)

Perdo (151843) | more than 11 years ago | (#3928850)

The flight control computers are 7x redundant and distributed throughout the airframe. It's the new radar and v3.0 combat avionics that need "rebooting"

Re:Redundant (1)

UranusReallyHertz (567776) | more than 11 years ago | (#3928930)

7 times redundency? Wow. Wonder what the mean time between failure is.

Re:Redundant (0)

Anonymous Coward | more than 11 years ago | (#3929000)

This just means /bin/laden can get 7 times as many buffer overflows at once on our jets with one script kiddie's tool of destruction.

Re:Redundant (1)

yatest5 (455123) | more than 11 years ago | (#3929036)

7 times redundency? Wow. Wonder what the mean time between failure is.

I'm pretty sure the 7x redundancy is not to combat software crashes but to combat bullets taking out the computers.

Reset button broken... (1)

JanusFury (452699) | more than 11 years ago | (#3928855)

The idea of one of these with a broken reset button, adds a whole new meaning to the word 'crash'. In fact, it's more like 'crash and explode, charring everything within a 1000 foot radius'. Yay.

Midair (1)

Quantum Singularity (594841) | more than 11 years ago | (#3928860)

And just what we'll happen when you reboot in Midair? I guess you can't run any programs. When I get in to the Air Force, I'm bringin Linux and BSD with me!

really? (1)

mojo-raisin (223411) | more than 11 years ago | (#3928866)

Here, the planes are pushed beyond normal limits by test pilots who cartwheel them through the sky at high altitudes and race at supersonic speeds a few feet above the Pacific.

Man - that would make pod-racing looking like drag-racing snails... 750+mph just feet above the ocean?! Imagine the wake behind that beast.

Contractor Breakdown for F-22 (4, Informative)

gmanske (312125) | more than 11 years ago | (#3928873)

For a good breakdown of who (LM, Boeing, others) supply what, have a look here [fas.org].

Also, can anyone confirm if OSA is the name of the referenced ADA software project (1.7 million lines etc...)


imagine this (5, Funny)

drDugan (219551) | more than 11 years ago | (#3928886)

I've lost him -- where is he?

On your six -- coming hard. Four
hundred. Losing airspeed! He's on
your six and closing fast!
Hard left! HARD LEFT!

Maverick jerks the stick left, and the F-14 takes an
astonishing turn. Jester ROARS past into a wide arc.

Great move. Great

He should've had me.

Take it down. Let's bug out of
here. Call for a draw.

No way. Let's reboot. I'll nail him this time.
Going vertical.

yeah i heard (0)

Anonymous Coward | more than 11 years ago | (#3928889)

when the nato bombed serbia, sometimes they hit civilian houses because of such errors.

know what?
war sucks

There Is Something Rotten in Software Engineering (2, Interesting)

Louis Savain (65843) | more than 11 years ago | (#3928895)

Why do you need the inflight reboot?

Because that is the nature of complex algorithmic systems. An algorithmic system is temporally inconsistent and unstable by nature. Using the algorithm as the basis of software construction is an ancient practice pioneered by Lady Ada Lovelace and Charles Babbage. It is the fundamental reason why dependable software systems are so hard to produce.

There is something rotten at the core of software engineering. Software functionality should not be fundamentally different from hardware functionality. Software should emulate hardware and serve as an extension to it. It should only provide the two things that are lacking in hardware: flexibility and ease of modification. The only way to solve the reliability crisis is to abandon the bad practice of using algorithms as the basis of software construction and to adopt a pure signal-based paradigm. More details can be found at the links below:

Project COSA [gte.net]

Moderation Funny(+1)? (2)

Cryptnotic (154382) | more than 11 years ago | (#3929001)

This isn't a joke. Read the linked pages, moderators. There is a rather large amount of thought and theory behind the ideas presented.

Of course, any computer can be thought of as a signal processing device. It has input (the sequence of bits in the program code and data storage and external input (e.g., keyboard, mouse, network, etc)), state (memory, registers, etc), and output (display, sound card, printer ports, disk, network, etc).

Re:There Is Something Rotten in Software Engineeri (2)

plaa (29967) | more than 11 years ago | (#3929056)

Because that is the nature of complex algorithmic systems. An algorithmic system is temporally inconsistent and unstable by nature. Using the algorithm as the basis of software construction is an ancient practice pioneered by Lady Ada Lovelace and Charles Babbage. It is the fundamental reason why dependable software systems are so hard to produce.

This reminds me of a story [slashdot.org] on Slashdot a few years ago about the process of writing the software that contols space shuttles. Still an interesting read.

(As timothy writes: These guys are "pretty thorough" the way Vlad the Impaler was "a little unbalanced." I could have certainly sometimes saved a lot of time using similar bug-documenting stuff.)

i960 in PC's (2, Interesting)

Ratso Baggins (516757) | more than 11 years ago | (#3928897)

More than 10 years ago I first saw a i960 dev board, and I thought "YUM! I can't wait for PC's to use them..." But they haven't. Anyone have any valid conjecture as to why?

Re:i960 in PC's (2, Informative)

OrangeSpyderMan (589635) | more than 11 years ago | (#3928950)

A good number of RAID controller cards used them, and have done for a while now. They are in PCs all over the world as we speak.

Re:i960 in PC's (2)

John Miles (108215) | more than 11 years ago | (#3928955)

If I remember right, some of the first commercial RAID boards ("Dell Drive Array") used the i960.

Can't think of anything else, though. The i860 and i960 were supposed to take over the planet at one point, but it never seemed to happen.

Re:i960 in PC's (1)

loddington (263358) | more than 11 years ago | (#3928988)

Compaq's RILOE (remote insight lights out edition) remote control cards use it. It seems nice enough and has only required 1 reboot in 12 months.

What Happened to the YF23 (0)

turgid (580780) | more than 11 years ago | (#3928900)

Northrop Grumman's competitor was the YF23, which was rumoured to be superior in some areas to the YF22. I've been looking on Google for info and all I can find is nonsense about black projects and flying saucers. Does anyone have any links to real information?

Drivers? (2, Funny)

zentu (584197) | more than 11 years ago | (#3928911)

So, uh when do they update the drivers for the displays, and when do they know that there was a problem with them? Pilot: Air traffic contol, come in. Air Triaffic contoler: We read you Pilot. What's your problem. P: The heads up display is going fuzzy, any clue what may be wrong?. ATC: Let me see, what version of the Windows F22 are you running? P: The version my machanic put in. ATC: So do you see the blinky red light in the left corner? P: No, I see a green one on the upper right. ATC: Well, you need to come back to base then, you have the old drivers. P: O.K. I will turn around now. ATC: Oh, by the way, the problem with your version is that the ground is actually off by six feet, becareful. P:WTF? Is it up or down? ATC: it varyies, by the driver version....

grrr (2, Insightful)

yatest5 (455123) | more than 11 years ago | (#3928961)

If so, why do you need the inflight reboot?

Is this how low slashdot has sunk? Someone can't be assed to research themselves the answer to a question so they post it to our x million readership?

Or maybe it's just another shameless editor troll for reams and reams of the same tired old offtopic MS / Windows 98 / BSOD jokes?

Jesus, is there any chance of getting any intelligent replies? I checked out kuro5shin recently and was surprised at how intelligent most of the posts are.

Anyway, mod me down because I haven't slagged MS, whatever.

Unfortunately, they are using Ada (3, Flamebait)

Florian Weimer (88405) | more than 11 years ago | (#3928964)

Since they use Ada, this war machine will actually work, despite more 1.5 million lines of source code running it. That's sad, why couldn't they use C, C++ or even Java for such projects, where failure might actually benefit mankind?

Ada? Still using that pile of junk! Sheech! (1)

SWTP (550956) | more than 11 years ago | (#3928973)

Oh well old habits die hard I guess.

When these guys start to adapt the research from AI low level bug's etc instead of unfuzzy logic of the "Do this" and "crash", the concept of reboot or give up and start completly over can finaly be removed. Then self repair correcting for damge problems can finaly be added giving the pilot or who ever a better chance of surviving. Basicaly a way to heal itself so to speak.

Flight Simulators (0)

Anonymous Coward | more than 11 years ago | (#3928981)

One question: Is this feature going to be carried across to the F22 sims?

If so, how will it be implemented, cos I reckon my PC could do a pretty accurate version...

Entropy? (2)

Bastian (66383) | more than 11 years ago | (#3928993)

I seem to remember hearing somewhere that the avionics system on the F-22 uses a neural net of some sort. In my experience, some kinds of neural networks can develop this creeping flakiness as a result of a sort of entropy in the weightings on each neuron. Since neural nets are subtle enough that it would be nigh-impossible to get rid of this cruft on the fly, the best way I can think of to fix problems is to simply reset all of the weights to a default value.

The best analogy of this that I can think of is to say that it's similar to a reboot, even though it doesn't necessarily require shutting the entire system down for a period of time.

Of course, like all hearsay, this doesn't make a whole lot of sense when you think of it. . . I'm not aware of any reason why they would put a neural net that continues to learn while it is being used in control of the avionics system, but then again a lot of technologies I see make no sense to me. . .

Ada ? (1)

DarkDust (239124) | more than 11 years ago | (#3929010)

The part from globalsecurity.com (that one that says the system has about 1.7 millions lines of Ada code) says this:

Ninety percent of the software is written in Ada, the Department of Defense's common computer language. Exceptions to the Ada requirement are granted only for special processing or maintenance requirements.

This means the developers were forced to use Ada, but why ? To me, it seems some suits think it's especially "safe" for some reason, does anyone know more about that ?

But I think you can try to make a programming language as "safe" as you want, it won't prevent you from implementing bugs, it just causes a false sense of safety instead which can be even more dangerous, IMHO.

somewhere up in blue skies... (2)

tanveer1979 (530624) | more than 11 years ago | (#3929012)

Alert, i have crashed please reboot


Last time you rebooted it was due to a crash ..

  • 1.reboot in safe mode(no missiles)
  • 2.reboot electronics only
  • 3.Reboot in parachute mode
__parachute mode__

Illegal instruction at address FFCFFFCC

  • 1. Start praying
  • 2. SEnd email to mom
  • 3. Wait

ould not connect to mail server

  • 1. retry
  • 2.Abort
  • __2__
  • Illegal instruction at address blah blah So you want to die:

    • 1. With fireworks on ground
    • 2. In ocean

    I wont listen to you i a going to crahs now.. 4 5 3 2 1 . . . Failed to crash :-(

    and so the pilot walks home safely :-)

how disappointing (1)

neurovish (315867) | more than 11 years ago | (#3929026)

I first read the article title as "F-22 Avionics Require Inflight Robot"...at which point visions of R2 units on USAF craft started dancing in my head. I got 1/2-way through the article without seeing any mention of an astromech droid before I realized I read the title wrong...how disappointing

Reboot - a true story (1)

djelovic (322078) | more than 11 years ago | (#3929062)

Even though they get a lot of bad press, the only reason why the planes fly are Boeing and Airbus. If it were up to pilots the planes would crash more often that Windows 95 boxes.

I remember sitting inside a Lufthansa plane on the Munich airport waiting for the plane to taxi. Sudenly we hear this very loud noise from somewhere below. The plane doesn't move and the noise goes on for 10 minutes or so. Then it suddenly stops and after a short pause the pilot gets on the intercom:

(Strong German accent:) "Ladies and Gentlemen: We had zi small problem witz one of our computerz. But now we've rezetet it and everything seemz to be OK."

After a short pause he adds:

"It waz very cold tonight here on zi ground, zat must have cauzed it."

Oh shit.
Load More Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Sign up for Slashdot Newsletters
Create a Slashdot Account