Sivaram Neelakantan <nsivaram....@gmail.com> wrote: > On Sat, Oct 10 2015,Sven Hartge wrote: >> Sivaram Neelakantan <nsivaram....@gmail.com> wrote:
>>> Is it enough that I change all references to stretch to sid in >>> sources.list and do the dist-upgrade to switch to sid? >> a) remove the references to security.debian.org. There is no security >> support for Sid. > umm,that so? oh well,now having 2nd thoughts Security problems are normally fixed through normal uploads to Unstable by the maintainer of the package. In most cases problems are fixed quite fast if the upstream releases a fixed version and the maintainer uploads it to unstable. But there is no dedicated security team as for the stable release and thus the packages in unstable can lag behind security wise a bit. And if there is a big transition going on (like the GCC5 and libstdc++ transition) then it may take a longer time until a fixed package can be uploaded to unstable. (And if the maintainer is MIA then you may not get an updated package at all. But this is a rare case.) >> b) be aware that Sid can and will be broken at times. You should know >> how to boot into rescue mode or how to use a rescue CD/DVD/USB key >> to repair your system, if needed. > I know it will be broken but I don't know enough debian sysadmin to > manage rescue stuff...yet. Right now, running off a VM. Is there > something that I can read to familiarise myself as to what to do when > things go kaput? Familiarise yourself with the rescue modes of systemd and on how to use "chroot" after having booted from a rescue CD to be able to manipulate your system back into a working state. Also being able to manually use mdadm and the LVM tools if you use those in your system is valuable. Grüße, Sven. -- Sigmentation fault. Core dumped.
