On 08/27/2009 07:49 PM, David Cantrell wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 26 Aug 2009, Dariusz J. Garbowski wrote:
Hi, something that bothers me a bit... More and more system restart
requests with each update (even if one doesn't use the package at the
time).
Is
2009/9/1 Dariusz J. Garbowski thufo...@yahoo.co.uk:
I'm starting to be really bothered by this. Today kdenetwork requires
restart due to... fix Bug 515586 - Kopete: New Messages from changed
resource arrive in new tab/window. Wouldn't login/logout sequence do? And
that only if the user really
On Wed, Sep 2, 2009 at 7:44 PM, Stephen John Smoogensmo...@gmail.com wrote:
I think that the selling point is over-sold. It is true in many case
for servers, but desktops are a much more interconnected system where
updating something deep requires a lot of restarts.. and yes you could
come up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 2 Sep 2009, Dennis J. wrote:
On 08/27/2009 07:49 PM, David Cantrell wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 26 Aug 2009, Dariusz J. Garbowski wrote:
Hi, something that bothers me a bit... More and more system
On 09/02/2009 02:33 PM, David Cantrell wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 2 Sep 2009, Dennis J. wrote:
On 08/27/2009 07:49 PM, David Cantrell wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 26 Aug 2009, Dariusz J. Garbowski wrote:
Hi, something that
David Cantrell wrote:
But I explained in the previous reply how to cycle the interface
using either the network service or NetworkManager. I still view
this as something more technical users will be familiar with and for
the average user, simply rebooting the system is the easiest method.
No,
On Tue, Sep 1, 2009 at 5:07 PM, Matthew
Woehlkemw_tr...@users.sourceforge.net wrote:
No, the easiest method is:
The following updates require their respective services to be restarted for
the updates to take effect. List of services. Proceed? [Yes] [No]
I don't think it makes sense to treat
Colin Walters wrote:
On Tue, Sep 1, 2009 at 5:07 PM, Matthew
Woehlkemw_tr...@users.sourceforge.net wrote:
No, the easiest method is:
The following updates require their respective services to be restarted
for the updates to take effect. List of services. Proceed? [Yes] [No]
I don't
I'm starting to be really bothered by this. Today kdenetwork requires
restart due to... fix Bug 515586 - Kopete: New Messages from changed
resource arrive in new tab/window. Wouldn't login/logout sequence do?
And that only if the user really cared, i.e. was using Kopete and this
bug was really
On Thu, Aug 27, 2009 at 22:54, Matthew
Woehlkemw_tr...@users.sourceforge.net wrote:
Dariusz J. Garbowski wrote:
Hi, something that bothers me a bit... More and more system restart
requests with each update (even if one doesn't use the package at the time).
This is a real shame. One of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 27 Aug 2009, Matthew Woehlke wrote:
Dariusz J. Garbowski wrote:
Hi, something that bothers me a bit... More and more system restart
requests with each update (even if one doesn't use the package at the
time).
This is a real shame. One
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 26 Aug 2009, Dariusz J. Garbowski wrote:
Hi, something that bothers me a bit... More and more system restart requests
with each update (even if one doesn't use the package at the time).
Is this necessary for dhclient and dhcp update
Dariusz J. Garbowski wrote:
Hi, something that bothers me a bit... More and more system restart
requests with each update (even if one doesn't use the package at the
time).
This is a real shame. One of the selling points of Linux is that you
*don't* need to reboot for every little upgrade
Hi, something that bothers me a bit... More and more system restart
requests with each update (even if one doesn't use the package at the time).
Is this necessary for dhclient and dhcp update packages to require restart?
Wouldn't service network restart and service dhcpd restart in the
14 matches
Mail list logo
