On 4 May 2011 03:10, Matt Wheeler m...@funkyhat.org wrote:
As I've mentioned before on the ayatana list I think this would do more harm
than good. As others have already said, just about everything bar Mozilla
stuff will continue to work fine if it's left running, and warning people
that a
Colin Law wrote:
Not arguing one way or the other but I suspect that if an upgrade that
requires a reboot is performed, but the reboot is delayed, that the
security hole may well likely not be plugged till the reboot is
performed.
Well, the holes in the kernel wont be plugged until the next
As I've mentioned before on the ayatana list I think this would do more harm
than good. As others have already said, just about everything bar Mozilla
stuff will continue to work fine if it's left running, and warning people
that a particular upgrade will require a reboot is likely to put some of
On 2011-04-21, Tyler J. Wagner wrote:
On Thu, 2011-04-21 at 16:52 +0100, Paul Willis wrote:
sudo apt-get update sudo apt-get upgrade -y
...my server it needs a reboot.
Of course, if you're doing it at the command line, it's pretty easy to
tell if a reboot is required. If the kernel
On 27 April 2011 13:06, Adam Funk a24...@ducksburg.com wrote:
I've had the reboot message after upgrading libc6 (not every time,
though) and libssl (every time, I think). I really wish aptitude or
at least the GUI update manager would warn me *in advance* when a
package upgrade will require a
On 27 April 2011 13:06, Adam Funk a24...@ducksburg.com wrote:
I really wish aptitude or
at least the GUI update manager would warn me *in advance* when a
package upgrade will require a reboot, as it can be very inconvenient
to find out afterwards when you're in the middle of something.
When
On 2011-04-27, Colin Law wrote:
On 27 April 2011 13:06, Adam Funk a24...@ducksburg.com wrote:
I really wish aptitude or
at least the GUI update manager would warn me *in advance* when a
package upgrade will require a reboot, as it can be very inconvenient
to find out afterwards when you're
On Wed, 2011-04-27 at 13:27 +0100, Colin Law wrote:
When this happens is it necessary to reboot fairly urgently or is it
ok to delay this till a convenient time. In other words is there a
significant difference between delaying the update because it will ask
for a reboot, and delaying the
Colin Law wrote:
When this happens is it necessary to reboot fairly urgently or is it
ok to delay this till a convenient time.
As far as I've noticed, Mozilla software is all that has any complaints
about being upgraded while running, and then left running.
I frequently go days between
Hi
Occasionally, after running...
sudo apt-get update sudo apt-get upgrade -y
...my server it needs a reboot. Trouble is I don't see the *** System restart
required *** message until next time I log in.
I usually log out and back in again straight after running the update but I'm
sure there
On 21 April 2011 16:52, Paul Willis paul.wil...@me.com wrote:
Occasionally, after running...
sudo apt-get update sudo apt-get upgrade -y
...my server it needs a reboot. Trouble is I don't see the *** System restart
required *** message until next time I log in.
I usually log out and back
On Thu, 2011-04-21 at 16:52 +0100, Paul Willis wrote:
sudo apt-get update sudo apt-get upgrade -y
...my server it needs a reboot.
Of course, if you're doing it at the command line, it's pretty easy to
tell if a reboot is required. If the kernel upgraded, reboot. If not,
you don't have to.
12 matches
Mail list logo
