On Sun, 2013-05-19 at 18:11 +0300, Πρεκατές Αλέξανδρος wrote:
> In release notes it says:
> 
> "You should not upgrade using telnet, rlogin, rsh, or from an X session 
> managed by xdm, gdm or kdm etc. on the machine you are upgrading. That is 
> because each of those services may well be terminated during the upgrade, 
> which can result in an inaccessible system that is only half-upgraded. Use of 
> the GNOME application update-manager is strongly discouraged for upgrades to 
> new releases, as this tool relies on the desktop session remaining active. "|
> 
> So i wonder why can ubuntu dist upgrade dist from within an X session?

I don't know what's different, but in general you for example can't
backup a complete Linux, while it's running, a way to do it anyway, is
to make a snapshot first and to backup the snapshot, independent from
the system. In general you need to reboot to switch to a new kernel, but
there's a tool that enables to switch the kernel without the need to
restart the computer. IOW, they perhaps have programmed something to
enable this and FWIW, it might be related or not, they don't use
upstart, so a basic component for the startup process already is
completely different to Debian. Perhaps files for services such as
display managers will be stored temporary and copied to the correct
location during a startup and again, upstart is a completely newer
process for startup than Debian's init. How many distros nowadays stay
with this kind of init? I suspect nearly every distro does use upstart
or systemd. You can't compare something old-fashioned like Debian, with
distros that are more modern, closer to upstream. OTOH something e.g.
running in the RAM can be updated and there e.g. is no need to stop X to
update a display manager for a regular backup. What's the source of your
quotation?

Regards,
Ralf


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1368978695.4892.25.camel@archlinux

Reply via email to