On 5/14/14, The Wanderer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
...
> three months, but I dist-upgrade to testing at least once every two or
> three weeks.)
>
> - --
>The Wanderer
>
> Secrecy is the beginning of tyranny.
Ahhh .. so .. like, who are you?
I know secrecy is
On Wednesday 14 May 2014 12:44:36 The Wanderer wrote:
> They do appear to, but in my experience, not uncommonly when running a
> dist-upgrade that includes a linux-image* upgrade something will get
> messed up about the order of events; the script will get run at the
> wrong time, and then not get
@lists.debian.org
> Subject: Re: reboot required after linux-image upgrade?
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> They do appear to, but in my experience, not uncommonly when running a
> dist-upgrade that includes a linux-image* upgrade something will get
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/14/2014 02:55 AM, Reco wrote:
> Hi.
>
> On Tue, May 13, 2014 at 08:40:11PM -0400, Theodore Alcapotaxis wrote:
>
>> Before you reboot, do you need to issue the command sudo
>> update-grub ??
>
> Every linux-image package should contain a pos
On Wed, 14 May 2014 07:59:25 + (UTC)
Curt wrote:
Hello Curt,
>is run as part of the install; however, I don't know whether in synaptic
>et. al. the same information is available for observation.
In Synaptic, one has to set preferences to "Apply changes in a terminal
window" to be able to
On Mi, 14 mai 14, 07:59:25, Curt wrote:
>
> I've asked myself the same question as the OP, but as I use apt at the
> command line I can observe the terminal output and see that update-grub
> is run as part of the install; however, I don't know whether in synaptic
> et. al. the same information is
On 2014-05-14, Reco wrote:
> Hi.
>
> On Tue, May 13, 2014 at 08:40:11PM -0400, Theodore Alcapotaxis wrote:
>> Before you reboot, do you need to issue the command sudo update-grub ??
>
> Every linux-image package should contain a post-install script which
> will invoke grub-install without human i
Hi.
On Tue, May 13, 2014 at 08:40:11PM -0400, Theodore Alcapotaxis wrote:
> Before you reboot, do you need to issue the command sudo update-grub ??
Every linux-image package should contain a post-install script which
will invoke grub-install without human intervention.
Reco
--
To UNSUBSCRIBE
On 14/05/14 04:30, Ric Moore wrote:
> On 05/13/2014 06:01 AM, Ralf Mardorf wrote:
>> On Tue, 2014-05-13 at 11:58 +0200, Ralf Mardorf wrote:
>>> in order for Linux to use the new kernel
>>
>> JFTR Linux is the kernel. I'm aware that you're talking about the
>> compete install, most of us call it Lin
Before you reboot, do you need to issue the command sudo update-grub ??
> - Original Message -
> From: staticsafe
> Sent: 05/14/14 02:39 AM
> To: debian-user@lists.debian.org
> Subject: Re: reboot required after linux-image upgrade?
>
> On 5/13/2014 05:51,
On 5/13/2014 05:51, ML mail wrote:
> Hi,
>
> I just upgraded my debian wheezy linux-image from 3.2.54 to 3.2.57 using
> apt-get update/upgrade and was wondering if I need to reboot my system or not
> in order for Linux to use the new kernel?
>
> Cheers
>
>
Yes, you need to reboot.
--
static
On 05/13/2014 06:01 AM, Ralf Mardorf wrote:
On Tue, 2014-05-13 at 11:58 +0200, Ralf Mardorf wrote:
in order for Linux to use the new kernel
JFTR Linux is the kernel. I'm aware that you're talking about the
compete install, most of us call it Linux, but correct is, that the
kernel is Linux and
On Tue, 2014-05-13 at 12:01 +0200, Ralf Mardorf wrote:
> On Tue, 2014-05-13 at 11:58 +0200, Ralf Mardorf wrote:
the OP wrote :D
> > in order for Linux to use the new kernel
>
> JFTR Linux is the kernel. I'm aware that you're talking about the
> compete inst
On Tue, 2014-05-13 at 11:58 +0200, Ralf Mardorf wrote:
> in order for Linux to use the new kernel
JFTR Linux is the kernel. I'm aware that you're talking about the
compete install, most of us call it Linux, but correct is, that the
kernel is Linux and nothing else.
--
To UNSUBSCRIBE, email to
On Tue, 2014-05-13 at 02:51 -0700, ML mail wrote:
> I just upgraded my debian wheezy linux-image from 3.2.54 to 3.2.57
> using apt-get update/upgrade and was wondering if I need to reboot my
> system or not in order for Linux to use the new kernel?
You need to reboot! This is not absolutely true,
Hi,
I just upgraded my debian wheezy linux-image from 3.2.54 to 3.2.57 using
apt-get update/upgrade and was wondering if I need to reboot my system or not
in order for Linux to use the new kernel?
Cheers
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "uns
16 matches
Mail list logo
