My understanding of the first post is that Raspberry Pi with it's port configured as an input will be the one that remains powered on. Assuming this understanding of the situation is correct then even if the internal pull up resistors were enabled they would not provide enough current to damage the GPIO on the unpowered Raspberry Pi.
Les.
I didn't go into that much detail, but my specific application will be using multiple (up to 10) RPis all networked together. One of the RPis will be acting as the master and will set a discreet output signal to all other RPis to enable or disable the entire system. Because of design constraints I really can't go into, all RPis will need to use the same GPIO pin (set as output on the master and input on all others), and the GPIO pins on all the RPis will be bussed together.
My initial thought was to configure the GPIO on all the slaves as input with internal pullup, and configure the master's GPIO as an output. When I want the system to be enabled, I set the output high or floating. When I want the system to be disabled, I set the output of the master low, which will pull down the GPIOs on all the slaves.
This works great if everything is powered, but since all the GPIOs will be bussed, if one RPi get unpowered, it'll still see 3.3V on that pin which per the previous discussion is undesirable.
Another fly in the ointment is that whatever external circuit I come up with has to be generic. It will live on an external PCB connected to the RPi through the 40 pin header. The external board needs to be the same design regardless of whether the RPi it's connected to is configured as the master, or a slave.
I think I came up with a solution using 2 GPIO pins and a pair of diodes, but I'd be interested in any ideas you may have on how to skin this cat particularly if there is a single GPIO solution.
If my explanation wasn't clear I can upload a diagram to help.
Thanks.