I hate to say it - but most people who do OSS work for the masses don't get paid for it.
I do packaging for Xen used from hobby users through to Disney - yet I get about $400AUD per year in donations. I also have to go buy my own test hardware (I need UEFI kit atm!).
I understand exactly what Werner means and the challenges faced - but I too don't see a solution for this. OSS has been linked for too long as a 'free solution' - which means nobody puts a currency value on the software and services that are made available to the world. I think its the mental relationship of OSS being 'free' causes it. Nobody blinks an eye to pay $100 for a Windows license - yet go for a $10 donation to an OSS project and people lose their minds...
So yeah - they're nowhere near a mature company - and lets not forget when they forked CyanogenMod and pulled the "You made this?.... I made this!" move when getting venture capital in the first place...
You have to have a free pool to get a 5 star rating. Too bad the ratings companies around the world haven't required decent and free Wi-Fi. Major hotel chains would change their offers in a hurry when they are down rated to a 4 star hotel.
And wait until they start snooping everyones traffic and data mining it... for profit - I mean, reliability monitoring...
On another note, I see you're looking at hotel bookings with another hotel chain at your next destination.........
I think they intend to bring stability and unity to Linux by eliminating modularity and choice.
Nothing so sinister.... The core group of people that made this stuff in the first place is moving on. This leaves the old sticklers that made things work out of decisions and are being replaced with a whole generation of new developers that haven't 'been there, done that, solved it' before. Its a changing of the guard in Linux - and its not looking good.
I read it on the BBC and came here for the discussion - as with any story, if you don't like it, skip it. Nothing is forcing you to read or take part in comments, so why bitch and moan about Slashdot covering something you personally don't like.
People bitch and moan because that is what the internet has devolved to. Look at any forum or discussion site and you'll see the same thing, day in, day out.
The Internet was supposed to be one of mankinds greatest achievements - yet looking at it now, it makes me want to punch random strangers in the face. Social media constantly reminds me how dumb people are, and forums how arrogant humans can be.
I suspect this debacle has been a massive setback for Linux on the desktop. I'm as hardcore an open source you'll find, I haven't run a closed-source OS in over 20 years, but I was almost ready to throw in the towel and install Windows during the height of this!
I did exactly this... I run linux on just about every non-GUI bit of equipment I have - virtualisation, the lot - but everything that I actually have to look at a screen for, I use Windows 7 again. Gnome 3 killed it for me... I have 3 x 24" 1920x1080 screens that Gnome 3 could never handle right. I was running Fedora 20 until Gnome 3.
TBH, XFCE would be perfect IF it was using wayland. The graphics tearing issues I had with my tri-head video card + XFCE was horrible. The sad fact was the only real fix was that XFCE needs newer graphics handling. One day it'll get there - and hopefully one day it becomes nice to use again - but until then, I went back to Windows 7 and the amount of work I actually get done is amazing...
The other benefit is that the dual GPUs (Intel + ATI) in my laptop actually work properly so I can play some TF2 on my laptop in the downtime - with VERY good performance. I couldn't get anywhere near that on Linux - even with the ATI binary drivers.
It boils down to the old adage: "If it ain't broke, don't fix it."
This is exactly right. I was playing with the last lot of RHEL7 betas - the biggest issue I had was that ethernet adapters would randomly fail to start - and systemd would not give any details as to why. Each time I had to log in over a serial console, stop networking, disable the profile, enable the profile again, and start networking. This would work perfectly - until a random time when rebooting later on (and not every reboot) where networking wouldn't come up again.
This is not what admins need - randomly failing network connections. This is also a problem that was fixed decades ago - until systemd causes it again.
Lets ignore the problems with new aims to recreate consoles etc in systemd / userland and ignore / disable the kernel ones. Because that's a great idea *cough*
This is the backup "GPS" system in military aircraft, and what we used before GPS
Not quite... The GPS is used for calibration, then INS is the primary system. For the logic to fall back far enough to use a pure GPS position, a lot of other things have failed....
I can see how a constant stream of telemetry might be cost-prohibitive, but what about a squirt of data consisting of -
- Flight Number - Lat / Long - Airspeed - Groundspeed - Altitude - Compass heeding...sent every five minutes? At least that would give a 'last known' location.
Congratulations - You've just described ADS-B [1] - however its MUCH more often than every 5 minutes - and more airliners already have it. In fact, look at the tracking info from flightradar24.com for the flight in question [2] - then it disappeared... Having yet another bit of tech to combat this is stupid.
You are hemorrhaging users to phones, tablets, OSX, gamers to game consoles, power users to Linux.... pretty much everything that isn't Windows. We told you people were only using Windows because there was no choice, but you failed to listen and use the chance to improve your technology. Now, it's too late. There are other choices, and people are moving to them. To quote B5:
"The avalanche has begun. It is too late for the pebbles to vote."
In a way, I agree - but I can't say that I like KDE or Gnome 3. I ended up settling on XFCE using Fedora 20. It boots fast, everything works as it should (except a PCI DVB card - but I already had a spare USB one that works fine).
Thunderbird for email, Chrome for web browsing, terminal, Steam for my TF2 fix, and it all 'just works' - especially now the open source radeon driver does dynamic power management correctly.
I'm just in the middle of purchasing a new laptop - and the first thing that will happen is it be formatted and Fedora 20 get installed. I've also moved away from Google for contacts / calendar sync and now using OwnCloud (private stuff ftw!), and Dropbox is also replaced by OwnCloud. I'm finally getting to have a say in my OS and data security!
I don't think anyone really cares about binary compatibility.
Apart from anyone wanting to run software certified for RHEL, you mean?
This is where it gets silly.... You worry about the certification for other software, but not the base OS? If the certification is important, then it would be BETTER to use the proper RHEL and not a free 'knockoff'....
What killed the release of CentOS 6 in a timely manner was all the build dependencies. To get an exact binary-compatible RPM for foo.el6 you needed to build it on, say, Fedora 13, with libbar-verisonX.Y.Z.fc13 installed. It wasn't self-hosting or documented how to build el6. Scientific Linux came out much more quickly because they didn't care about binary compatibility.
I don't think anyone really cares about binary compatibility. I cannot think of a single operational advantage that this gives - apart from "narf, the checksums match what I could have paid for". The massive migration away from CentOS in version 6 proved this.
2) CentOS being a closed development group that refuses to accept any help from outsiders. Scientific Linux is another clone of Redhat that was able release their version of Redhat 6 much faster.
Correct - and the team at Scientific Linux are awesome to work with. It is a breath of fresh air from the poison that is the CentOS 'community'.
The employees are out there but they cannot work for chinese slave labor wages, nor do they want that lifestyle.
11 months ago I finished my Commercial Pilots License - I haven't been able to find any work at all since completing it. That was the last time I touched a plane.
The same problem exists. People are expected to splash $100k AUD on their license, then work for ~$25k a year. Not to mention get themselves to jobs on their own dime etc... I hear the same lines "There is a massive pilots shortage!!" - which is absolute bullshit. We just have to take other jobs to pay off the loans etc we took for our training.
It just about gutted my career - but this is the world we live in. Now I'm only casually employed - and making about the same amount as I would as a pilot - while working only a handful of hours.
The way to get the most performance out of iptables is to make each chain as small as possible.
Thats sorta the problem. Even lowend Cisco devices will handle quite lengthy ACL tables without any performance degredation.
No, No they don't. If you look at the packet-per-second performance you get when you put even some basic rules in there, you'll be surprised. Some systems have their PPS rate halved by this...
each adapter gets a configuration attached for starters, then things go from there (VLANs, ACLs, etc.)
iptables -N eth0-in iptables -N eth0-out iptables -A FORWARD -i eth0 -j eth0-in iptables -A FORWARD -o eth0 -j eth0-out
Then create all the rules you need in the specified chain.
The way to get the most performance out of iptables is to make each chain as small as possible. This can quite easily be split up into logical lists for what you actually do - ie:
This way, you can easily branch out and skip a fuckton of rules that will never apply to the packet that is being processed. Usually, you can bring each chain to less than 6 rules. Less rules == less overhead == more performance.
My problem was I was thinking of trimming as an extra thing I had to do - really, it means you have less to do.
The best advice I have ever been given in flying is this: Unload yourself.
What does this mean? Ok, power on, take off roll, reach takeoff safety speed (usually 1.5x stall), rotate, airborne, set your climb attitude. Next thing, trim. With a bit of practice, about 20 seconds after liftoff, you will be trimmed for the climb - this means you can take your hands off the controls and you'll continue to climb at your (usually) 500ft/min. Your speed will be stable, your climb rate will be stable, and you'll keep climbing until you either get disturbed by a gust of wind etc or you change the controls.
Take this time now that you can fly with hands off to glance at your engine instruments - that the RPM is what you expect it to be, oil temps and pressure is ok, airspeed is what you expect, then check your performance again (attitude, power etc). This can all be done within 45 seconds after liftoff. Now you do what any VFR pilot does best - look outside. As you're not struggling to keep the aircraft under control, you can observe what is going on outside. Looking for traffic, obstacles, making sure what you see outside matches the instruments (ie you're climbing, going fast enough etc).
Coming up to your assigned / desired altitude, use the yolk to bring the nose down, power to cruise, trim, trim, trim. Usually up to about 1/2 - 3/4 of a turn on the trim wheel and you're almost able to fly hands off again in seconds.
A good exercise here - trim for the climb, then don't touch the yolk again until you're on final to land. Use the trim for your attitude and rudder for turning. Do the entire circuit using only trim, rudder and throttle. As you would have been taught, the secondary action of yaw is roll - so you'll find you actually start to bank while only using the rudder. It gets tricky - and you'll be all over the place while first trying this - but it is great for learning the relationship as to what you're doing affecting the aircraft.
Anyhow - this isn't flight training 101 on slashdot, but learning to fly has been a highlight of my life - and I'm always happy to share things with people. Feel free to email me if you want to discuss more random things;)
I thought the whole point of those big bright landing landing lights was to illuminate the ground when you're near touch down (and for taxi/takeoff). Runway markers may may it easy to see the runway from afar, but aren't going to be as useful for an untrained pilot to see how fast the plane is approaching the ground since a few fast moving dots of light streaming by aren't the same as a broadly lit surface).
Heh - the 'bright light' called a landing light in a C172 is almost as bright as a single car headlight (if you're lucky, like the high beam). It does sweet fuck all to illuminate the runway. If you're waiting to see the runway via the landing light before you flare, you're going to have a bad time - and probably crater. Larger aircraft have much brighter lights, but the effect is still the same.
Night landings are hard. There are no floodlit runways that I know of in existence. The only form of reference you have is the shape of the lights. There are very few clues of your height or speed by looking outside at night. Night flying kills many - as it is VERY easy to fly straight into the ground because you can't see it - this danger is magnified even more when you are on approach to an airfield - especially if it is one with a 'black hole effect'.
During my night flying assessment, I was required to land at an airport 'void of artificial lighting' - ie only runway lights. As you fly towards the airport, imagine a completely black area with two rows of lights. That is all you have. If you're lucky and there is a full moon, you may be able to make out the ground. I'd say it is one of the hardest things I have ever had to do.
I'm a commercial pilot (who is currently unemployed) - however operating the radio is part of my pre-flight briefing with anyone in the right seat in any G/A aircraft. In this briefing, I also go through what I'll do if we have a radio failure or comms problems - as part of this includes them using the radio (if required). Most people are very attentive - and its with this exact reason in mind - if anything incapacitates me, the least I can do for passenger safety is to get them to talk to someone who can help.
If the person in the right seat is a bit of a fan about flying, I'll teach them a bit about basic flight controls during the flight as well. Most people see if as a bit of fun and enjoy it - but there is a serious reason behind the scenes... The best way to be prepared in aviation is to think ahead.
For less experienced pilots, this is why we always aim to trim an aircraft for the correct attitude and performance as early as possible. The last thing you want to do is to leave the aircraft incorrectly trimmed and have something happen to you. When you step up to jet aircraft, the most important control in the aircraft is the trim. Use it well and often.
Slashdot Mirror
It's a mail reader. That is all it needs to be.
Fixing bugs like the many year old "You have 39423 new messages" when a single message pops into my inbox would be nice.
I hate to say it - but most people who do OSS work for the masses don't get paid for it.
I do packaging for Xen used from hobby users through to Disney - yet I get about $400AUD per year in donations. I also have to go buy my own test hardware (I need UEFI kit atm!).
I understand exactly what Werner means and the challenges faced - but I too don't see a solution for this. OSS has been linked for too long as a 'free solution' - which means nobody puts a currency value on the software and services that are made available to the world. I think its the mental relationship of OSS being 'free' causes it. Nobody blinks an eye to pay $100 for a Windows license - yet go for a $10 donation to an OSS project and people lose their minds...
How did Cyanogen screw over phone makers? Not saying they didn't I just have never heard that.
Where they acted like children:
http://www.engadget.com/2014/1...
The fun continues:
http://phandroid.com/2015/01/2...
And then this:
http://www.knowyourmobile.com/...
So yeah - they're nowhere near a mature company - and lets not forget when they forked CyanogenMod and pulled the "You made this? .... I made this!" move when getting venture capital in the first place...
Cyanogen sold out a LONG time ago..... Then screwed over a few phone manufacturers, and now this. Great track record they have...
You have to have a free pool to get a 5 star rating. Too bad the ratings companies around the world haven't required decent and free Wi-Fi. Major hotel chains would change their offers in a hurry when they are down rated to a 4 star hotel.
And wait until they start snooping everyones traffic and data mining it... for profit - I mean, reliability monitoring...
On another note, I see you're looking at hotel bookings with another hotel chain at your next destination.........
I think they intend to bring stability and unity to Linux by eliminating modularity and choice.
Nothing so sinister.... The core group of people that made this stuff in the first place is moving on. This leaves the old sticklers that made things work out of decisions and are being replaced with a whole generation of new developers that haven't 'been there, done that, solved it' before. Its a changing of the guard in Linux - and its not looking good.
I read it on the BBC and came here for the discussion - as with any story, if you don't like it, skip it. Nothing is forcing you to read or take part in comments, so why bitch and moan about Slashdot covering something you personally don't like.
People bitch and moan because that is what the internet has devolved to. Look at any forum or discussion site and you'll see the same thing, day in, day out.
The Internet was supposed to be one of mankinds greatest achievements - yet looking at it now, it makes me want to punch random strangers in the face. Social media constantly reminds me how dumb people are, and forums how arrogant humans can be.
I suspect this debacle has been a massive setback for Linux on the desktop. I'm as hardcore an open source you'll find, I haven't run a closed-source OS in over 20 years, but I was almost ready to throw in the towel and install Windows during the height of this!
I did exactly this... I run linux on just about every non-GUI bit of equipment I have - virtualisation, the lot - but everything that I actually have to look at a screen for, I use Windows 7 again. Gnome 3 killed it for me... I have 3 x 24" 1920x1080 screens that Gnome 3 could never handle right. I was running Fedora 20 until Gnome 3.
TBH, XFCE would be perfect IF it was using wayland. The graphics tearing issues I had with my tri-head video card + XFCE was horrible. The sad fact was the only real fix was that XFCE needs newer graphics handling. One day it'll get there - and hopefully one day it becomes nice to use again - but until then, I went back to Windows 7 and the amount of work I actually get done is amazing...
The other benefit is that the dual GPUs (Intel + ATI) in my laptop actually work properly so I can play some TF2 on my laptop in the downtime - with VERY good performance. I couldn't get anywhere near that on Linux - even with the ATI binary drivers.
This is what is wrong with SystemD.... Do ONE job, do it well. Not replace the entire ecosystem.....
It boils down to the old adage: "If it ain't broke, don't fix it."
This is exactly right. I was playing with the last lot of RHEL7 betas - the biggest issue I had was that ethernet adapters would randomly fail to start - and systemd would not give any details as to why. Each time I had to log in over a serial console, stop networking, disable the profile, enable the profile again, and start networking. This would work perfectly - until a random time when rebooting later on (and not every reboot) where networking wouldn't come up again.
This is not what admins need - randomly failing network connections. This is also a problem that was fixed decades ago - until systemd causes it again.
Lets ignore the problems with new aims to recreate consoles etc in systemd / userland and ignore / disable the kernel ones. Because that's a great idea *cough*
So the next lot of phishing will come from: róót@gmail.com / Àdministrator@gmail.com or BìllGàtes@gmail.com etc?
Great.
It gets used rarely and the newer software that is to replace it is being written in python - the portability lesson has been learnt.
Python 2 or Python 3? They're not portable between the two versions. Who knows what Python 4 will bring.
This is the backup "GPS" system in military aircraft, and what we used before GPS
Not quite... The GPS is used for calibration, then INS is the primary system. For the logic to fall back far enough to use a pure GPS position, a lot of other things have failed....
I can see how a constant stream of telemetry might be cost-prohibitive, but what about a squirt of data consisting of - ...sent every five minutes? At least that would give a 'last known' location.
- Flight Number
- Lat / Long
- Airspeed
- Groundspeed
- Altitude
- Compass heeding
Congratulations - You've just described ADS-B [1] - however its MUCH more often than every 5 minutes - and more airliners already have it. In fact, look at the tracking info from flightradar24.com for the flight in question [2] - then it disappeared... Having yet another bit of tech to combat this is stupid.
[1] http://en.wikipedia.org/wiki/A... - Bonus: How it works - http://www.airservicesaustrali...
[2] http://theaviationist.com/wp-c...
I moved to KDE on Debian and haven't looked back.
You are hemorrhaging users to phones, tablets, OSX, gamers to game consoles, power users to Linux.... pretty much everything that isn't Windows. We told you people were only using Windows because there was no choice, but you failed to listen and use the chance to improve your technology. Now, it's too late. There are other choices, and people are moving to them. To quote B5:
"The avalanche has begun. It is too late for the pebbles to vote."
In a way, I agree - but I can't say that I like KDE or Gnome 3. I ended up settling on XFCE using Fedora 20. It boots fast, everything works as it should (except a PCI DVB card - but I already had a spare USB one that works fine).
Thunderbird for email, Chrome for web browsing, terminal, Steam for my TF2 fix, and it all 'just works' - especially now the open source radeon driver does dynamic power management correctly.
I'm just in the middle of purchasing a new laptop - and the first thing that will happen is it be formatted and Fedora 20 get installed. I've also moved away from Google for contacts / calendar sync and now using OwnCloud (private stuff ftw!), and Dropbox is also replaced by OwnCloud. I'm finally getting to have a say in my OS and data security!
Security expert Bruce Schneier was found dead in his home. The cause of death is unknown but police are investigating possible foul play.
Thats too much work... They just need to pay some young girl a few grand to say she was raped by him. Oldest trick in the book....
Apart from anyone wanting to run software certified for RHEL, you mean?
This is where it gets silly.... You worry about the certification for other software, but not the base OS? If the certification is important, then it would be BETTER to use the proper RHEL and not a free 'knockoff'....
What killed the release of CentOS 6 in a timely manner was all the build dependencies. To get an exact binary-compatible RPM for foo.el6 you needed to build it on, say, Fedora 13, with libbar-verisonX.Y.Z.fc13 installed. It wasn't self-hosting or documented how to build el6. Scientific Linux came out much more quickly because they didn't care about binary compatibility.
I don't think anyone really cares about binary compatibility. I cannot think of a single operational advantage that this gives - apart from "narf, the checksums match what I could have paid for". The massive migration away from CentOS in version 6 proved this.
2) CentOS being a closed development group that refuses to accept any help from outsiders. Scientific Linux is another clone of Redhat that was able release their version of Redhat 6 much faster.
Correct - and the team at Scientific Linux are awesome to work with. It is a breath of fresh air from the poison that is the CentOS 'community'.
The employees are out there but they cannot work for chinese slave labor wages, nor do they want that lifestyle.
11 months ago I finished my Commercial Pilots License - I haven't been able to find any work at all since completing it. That was the last time I touched a plane.
The same problem exists. People are expected to splash $100k AUD on their license, then work for ~$25k a year. Not to mention get themselves to jobs on their own dime etc... I hear the same lines "There is a massive pilots shortage!!" - which is absolute bullshit. We just have to take other jobs to pay off the loans etc we took for our training.
It just about gutted my career - but this is the world we live in. Now I'm only casually employed - and making about the same amount as I would as a pilot - while working only a handful of hours.
The way to get the most performance out of iptables is to make each chain as small as possible.
Thats sorta the problem. Even lowend Cisco devices will handle quite lengthy ACL tables without any performance degredation.
No, No they don't. If you look at the packet-per-second performance you get when you put even some basic rules in there, you'll be surprised. Some systems have their PPS rate halved by this...
each adapter gets a configuration attached for starters, then things go from there (VLANs, ACLs, etc.)
iptables -N eth0-in
iptables -N eth0-out
iptables -A FORWARD -i eth0 -j eth0-in
iptables -A FORWARD -o eth0 -j eth0-out
Then create all the rules you need in the specified chain.
The way to get the most performance out of iptables is to make each chain as small as possible. This can quite easily be split up into logical lists for what you actually do - ie:
iptables -N 10.1.1.1
iptables -N 10.1.1.2
iptables -N 10.1.1.3
iptables -A FORWARD -i eth0 -d 10.1.1.1 -j 10.1.1.1
iptables -A FORWARD -i eth0 -d 10.1.1.2 -j 10.1.1.2
iptables -A FORWARD -i eth0 -d 10.1.1.3 -j 10.1.1.3
This way, you can easily branch out and skip a fuckton of rules that will never apply to the packet that is being processed. Usually, you can bring each chain to less than 6 rules. Less rules == less overhead == more performance.
My problem was I was thinking of trimming as an extra thing I had to do - really, it means you have less to do.
The best advice I have ever been given in flying is this: Unload yourself.
What does this mean? Ok, power on, take off roll, reach takeoff safety speed (usually 1.5x stall), rotate, airborne, set your climb attitude. Next thing, trim. With a bit of practice, about 20 seconds after liftoff, you will be trimmed for the climb - this means you can take your hands off the controls and you'll continue to climb at your (usually) 500ft/min. Your speed will be stable, your climb rate will be stable, and you'll keep climbing until you either get disturbed by a gust of wind etc or you change the controls.
Take this time now that you can fly with hands off to glance at your engine instruments - that the RPM is what you expect it to be, oil temps and pressure is ok, airspeed is what you expect, then check your performance again (attitude, power etc). This can all be done within 45 seconds after liftoff. Now you do what any VFR pilot does best - look outside. As you're not struggling to keep the aircraft under control, you can observe what is going on outside. Looking for traffic, obstacles, making sure what you see outside matches the instruments (ie you're climbing, going fast enough etc).
Coming up to your assigned / desired altitude, use the yolk to bring the nose down, power to cruise, trim, trim, trim. Usually up to about 1/2 - 3/4 of a turn on the trim wheel and you're almost able to fly hands off again in seconds.
A good exercise here - trim for the climb, then don't touch the yolk again until you're on final to land. Use the trim for your attitude and rudder for turning. Do the entire circuit using only trim, rudder and throttle. As you would have been taught, the secondary action of yaw is roll - so you'll find you actually start to bank while only using the rudder. It gets tricky - and you'll be all over the place while first trying this - but it is great for learning the relationship as to what you're doing affecting the aircraft.
Anyhow - this isn't flight training 101 on slashdot, but learning to fly has been a highlight of my life - and I'm always happy to share things with people. Feel free to email me if you want to discuss more random things ;)
I thought the whole point of those big bright landing landing lights was to illuminate the ground when you're near touch down (and for taxi/takeoff). Runway markers may may it easy to see the runway from afar, but aren't going to be as useful for an untrained pilot to see how fast the plane is approaching the ground since a few fast moving dots of light streaming by aren't the same as a broadly lit surface).
Heh - the 'bright light' called a landing light in a C172 is almost as bright as a single car headlight (if you're lucky, like the high beam). It does sweet fuck all to illuminate the runway. If you're waiting to see the runway via the landing light before you flare, you're going to have a bad time - and probably crater. Larger aircraft have much brighter lights, but the effect is still the same.
Night landings are hard. There are no floodlit runways that I know of in existence. The only form of reference you have is the shape of the lights. There are very few clues of your height or speed by looking outside at night. Night flying kills many - as it is VERY easy to fly straight into the ground because you can't see it - this danger is magnified even more when you are on approach to an airfield - especially if it is one with a 'black hole effect'.
During my night flying assessment, I was required to land at an airport 'void of artificial lighting' - ie only runway lights. As you fly towards the airport, imagine a completely black area with two rows of lights. That is all you have. If you're lucky and there is a full moon, you may be able to make out the ground. I'd say it is one of the hardest things I have ever had to do.
(I am a student pilot, and I fly a Cessna 172)
I'm a commercial pilot (who is currently unemployed) - however operating the radio is part of my pre-flight briefing with anyone in the right seat in any G/A aircraft. In this briefing, I also go through what I'll do if we have a radio failure or comms problems - as part of this includes them using the radio (if required). Most people are very attentive - and its with this exact reason in mind - if anything incapacitates me, the least I can do for passenger safety is to get them to talk to someone who can help.
If the person in the right seat is a bit of a fan about flying, I'll teach them a bit about basic flight controls during the flight as well. Most people see if as a bit of fun and enjoy it - but there is a serious reason behind the scenes... The best way to be prepared in aviation is to think ahead.
For less experienced pilots, this is why we always aim to trim an aircraft for the correct attitude and performance as early as possible. The last thing you want to do is to leave the aircraft incorrectly trimmed and have something happen to you. When you step up to jet aircraft, the most important control in the aircraft is the trim. Use it well and often.