I don't do upgrades like that. I create an image on a local box, and when I'm satisfied, I load the entire image to the remote server, do some config tweaks, and boot the new image.
Typically, I'll backup data to another machine, install the new "upgraded" OS (image), and restore the data. Or, when I get to design the system from the beginning, I will put the OS on a dedicated partition, allowing me to change the OS without changing/risking the data. I've been doing this for a little while. I do appreciate your concern, and your tips were I to try such a risky procedure on a remote machine. I am still interested in hearing any results, good or bad, about 3.0RC2 in a production environment. Thanks, Greg On Jun 18, 2005, at 2:15 PM, Matthias Subik wrote: > update from 2.1 to 3.0 remotely?? > if it works, it would be a miracle. > if you have to upgrade remotely, > remove all packages except the ones needed to boot, > then upgrade, > hope for the best, > (pray, whatever religion you count yourself to) > reboot. > IF the machine comes back: > install packages via swup as usual. > I won't count on it, but it could work. > m > > On 18.06.2005, at 22:20, Gregory S. Youngblood wrote: > > >> Hello, >> >> I'm curious to see if anyone has started to use the 3.0 in >> production machines. I've been testing it about every other week, and >> the current 20050609 release is the best one yet. It actually >> completes installation on my test platform. >> >> Of course, I'm planning to upgrade a remote server, and had hoped to >> go from 2.1 to 3.0, but I'm not sure I have enough confidence in 3.0 >> just yet. I was hoping to hear from some of the others in the >> community to see if they have any experiences with 3.0 in production. >> Especially on AMD based systems. >> >> Thanks, >> Greg >> _______________________________________________ >> tsl-discuss mailing list >> [email protected] >> http://lists.trustix.org/mailman/listinfo/tsl-discuss >> >> > > _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
