Upgrading method
Hi,
I am still at that intense early learning stage. I keep these two
machines at home firmly in "stable". I upgrade regularly with dselect
and add and remove packages as I come to terms with all this.
Recently I have started to wonder how all this works with a major
change, such as when "woody" becomes "stable". Will I just find that
when I upgrade my packages one day that I have gone from "potato" to
"woody"?
That in itself is fine by me, but does the dselect method work for
changes of kernel and similar key files?
If the kernel is changed am I then going to have to edit lilo by hand?
Does it replace the default kernel? Does it remove the old one?
None of these things bother me too much, I just want to know what to
expect. I have read what I can find, but can't quite tease out the
answers I am looking for.
Basically, when there is a new stable version, what does the
"stable-only" user have to do to remain current?
Oh yes, I have one other question. I was in conversation with someone
recently and might have misunderstood what was said, but when a package
is reported in the "debian-security-announce" list, does and
"update-upgrade" get the package from the stable group, or is there, as
was suggested to me a separate site for security fixes that I should
have in my sources list?
I really like this way of staying up-to-date, but I just want to make
sure I am doing it right, and making the most of the maintainers efforts
Keith
--
------------------------------------------------------------------------
keith_oconnell@bigfoot.com (Keith O'Connell)
------------------------------------------------------------------------
Reply to: