On 26 Jan 2013, at 15:28, Michael Scherer wrote:
Le samedi 26 janvier 2013 à 15:20 -0500, Mike Pinkerton a écrit :
On 26 Jan 2013, at 13:09, Chris Murphy wrote:
On Jan 26, 2013, at 10:45 AM, Mike Pinkerton
<pseli...@mindspring.com> wrote:
If you could SSH into fedup during its "offline" period and get
real time feedback about what it is doing and any errors it
encounters, and perhaps the ability to fix any problems when it
finishes but before it attempts to reboot, then it would be less
scary for remote upgrades.
I haven't tried 'systemctl start sshd' during the upgrade to see
what happens; it's probably not totally benign to do this, since
ssh will be upgraded, but it seems a lot safer, vastly so, than a
live yum update while a server is running.
Would it work for the network and sshd to be run from the initramfs
rather than the file system that is being updated?
Then you need to have the network configuration, etc. This can be
done,
but for now, the feature is not in dracut, see this bug for a similar
request for encrypted root :
https://bugzilla.redhat.com/show_bug.cgi?id=524727
That bug looks like a superset of what would be needed to run the
network and sshd from the initramfs.
As for network configuration, in the past (I haven't tried it with
F18's new Anaconda), one could do a VNC-enabled install by passing a
minimal network configuration (interface and IP address), as well as
a VNC password, on the kernel line. Perhaps for a ssh-enabled fedup,
one could do something similar, passing an interface and IP address
to fedup, possibly as well as a one-time use ssh password and a
"permitted" remote IP address block from which one could connect.
How those persist across the reboot -- whether fedup writes those to
the kernel line in grub.conf as one would do with a remote VNC
install, or they are written into the initramfs -- would be a question.
--
Mike
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
