On Sun, 9 Feb 2014 01:40:59 +0200
Andrei POPESCU wrote:
> On Sb, 08 feb 14, 22:43:41, Lisi Reisz wrote:
> >
> > I'm quite happy to let it go on upgrading itself as it has so far.
> > If I mess with it I shall only cause myself problems. The
> > developers know way more than I do!
>
> Installin
On Saturday 08 February 2014 23:40:59 Andrei POPESCU wrote:
> On Sb, 08 feb 14, 22:43:41, Lisi Reisz wrote:
> > I'm quite happy to let it go on upgrading itself as it has so
> > far. If I mess with it I shall only cause myself problems. The
> > developers know way more than I do!
>
> Installing n
On Sb, 08 feb 14, 22:43:41, Lisi Reisz wrote:
>
> I'm quite happy to let it go on upgrading itself as it has so far. If
> I mess with it I shall only cause myself problems. The developers
> know way more than I do!
Installing newer kernel packages might actually be safer than upgrading
the s
On Saturday 08 February 2014 20:48:14 Tom H wrote:
> On Sat, Feb 8, 2014 at 11:55 AM, Lisi Reisz
wrote:
> > On Saturday 08 February 2014 12:29:30 Tom H wrote:
> >> On Sat, Feb 8, 2014 at 6:32 AM, Lisi Reisz
> >>
> >
> > wrote:
> >>> On Saturday 08 February 2014 09:40:43 Chris Bannister wrote:
>
On Sat, Feb 8, 2014 at 11:55 AM, Lisi Reisz wrote:
> On Saturday 08 February 2014 12:29:30 Tom H wrote:
>> On Sat, Feb 8, 2014 at 6:32 AM, Lisi Reisz
> wrote:
>>> On Saturday 08 February 2014 09:40:43 Chris Bannister wrote:
AFAIUI, if the package has a different name, as newer releases
On Sat, 2014-02-08 at 16:55 +, Lisi Reisz wrote:
> Had I wanted it not to upgrade, would I have needed to search
> out the metapackage and remove it? Or hold it, of course.
No need to hold the package, removing it should be all that's needed.
--
To UNSUBSCRIBE, email to debian-user-requ.
On Saturday 08 February 2014 12:29:30 Tom H wrote:
> On Sat, Feb 8, 2014 at 6:32 AM, Lisi Reisz
wrote:
> > On Saturday 08 February 2014 09:40:43 Chris Bannister wrote:
> >> AFAIUI, if the package has a different name, as newer releases
> >> of kernels do, then APT won't consider it an update, it
On Sat, 2014-02-08 at 13:54 +0100, Ralf Mardorf wrote:
> On Sat, 2014-02-08 at 07:48 -0500, Tom H wrote:
> > On Sat, Feb 8, 2014 at 5:24 AM, Ralf Mardorf
> > wrote:
> > > On Sat, 2014-02-08 at 10:02 +, Joe wrote:
> > >>
> > >> The risk is about having that happen without noticing. Generally,
On Sat, 2014-02-08 at 07:48 -0500, Tom H wrote:
> On Sat, Feb 8, 2014 at 5:24 AM, Ralf Mardorf
> wrote:
> > On Sat, 2014-02-08 at 10:02 +, Joe wrote:
> >>
> >> The risk is about having that happen without noticing. Generally, I
> >> keep an eye on what sid is updating, but even this long afte
On Sat, 2014-02-08 at 13:46 +0100, Ralf Mardorf wrote:
> On Sat, 2014-02-08 at 07:29 -0500, Tom H wrote:
> > linux-image won't be bumped up to a later kernel version if you don't
> > have "linux-image-" installed.
>
> Let's make a real job of it.
>
> Metapackage:
> http://packages.debian.org/sid/
On Sat, Feb 8, 2014 at 5:24 AM, Ralf Mardorf wrote:
> On Sat, 2014-02-08 at 10:02 +, Joe wrote:
>>
>> The risk is about having that happen without noticing. Generally, I
>> keep an eye on what sid is updating, but even this long after a
>> release, it's still tens of megabytes a day. I don't c
On Sat, 2014-02-08 at 07:29 -0500, Tom H wrote:
> linux-image won't be bumped up to a later kernel version if you don't
> have "linux-image-" installed.
Let's make a real job of it.
Metapackage:
http://packages.debian.org/sid/linux-image-amd64
dep: linux-image-3.12-1-amd64
If you don't install
On Sat, Feb 8, 2014 at 6:32 AM, Lisi Reisz wrote:
> On Saturday 08 February 2014 09:40:43 Chris Bannister wrote:
>>
>> AFAIUI, if the package has a different name, as newer releases of
>> kernels do, then APT won't consider it an update, it is just
>> another package.
>
> aptitude has just upgrade
On Saturday 08 February 2014 09:40:43 Chris Bannister wrote:
> AFAIUI, if the package has a different name, as newer releases of
> kernels do, then APT won't consider it an update, it is just
> another package.
aptitude has just upgraded me automatically from 3.10-x bpo to 3.11-x
bpo then to 3.12
On Sat, 2014-02-08 at 10:13 +, Joe wrote:
> As Chris and others have said elsewhere, one partition is generally OK
> on a workstation. You might keep /home on a separate one, to make
> reinstallation a little easier if it becomes necessary, but if you're
> keeping valuable data in /home, you sh
On 02/08/2014 11:52 AM, Roelof Wobben wrote:
>
>> Date: Sat, 8 Feb 2014 22:40:43 +1300
>> From: cbannis...@slingshot.co.nz
>> To: debian-user@lists.debian.org
>> Subject: Re: How to block kernel updates
>>
>> On Sat
On Sat, 2014-02-08 at 10:02 +, Joe wrote:
> The risk is about having that happen without noticing. Generally, I
> keep an eye on what sid is updating, but even this long after a
> release, it's still tens of megabytes a day. I don't check all of them
I always read all package names before upda
On Sat, 8 Feb 2014 09:52:17 +
Roelof Wobben wrote:
>
>
> Im not the average newbie and Im running jessie now.
>
> Can anyone tell me a good partition scheme for a 80G disk so im not
> running again in problems.
>
As Chris and others have said elsewhere, one partition is generally OK
on a
On Sat, 8 Feb 2014 22:40:43 +1300
Chris Bannister wrote:
> On Sat, Feb 08, 2014 at 08:55:50AM +, Joe wrote:
> > On Sat, 8 Feb 2014 15:10:09 +1300
> > Chris Bannister wrote:
> >
> > > On Fri, Feb 07, 2014 at 10:07:34PM +, Joe wrote:
> > > > You can also remove any kernel metapackage e.g.
> Date: Sat, 8 Feb 2014 22:40:43 +1300
> From: cbannis...@slingshot.co.nz
> To: debian-user@lists.debian.org
> Subject: Re: How to block kernel updates
>
> On Sat, Feb 08, 2014 at 08:55:50AM +, Joe wrote:
>> On Sat, 8 Feb 2014
On Sat, Feb 08, 2014 at 07:57:51AM +, Roelof Wobben wrote:
> Oke,
>
> I will do a re-install of my 80G box.
>
> What will be a good partition scheme for normal desktop use?
Did you read my previous post?
I'd just give it the whole disk - one partition. Although, you may want
a separate hom
On Sat, Feb 08, 2014 at 08:55:50AM +, Joe wrote:
> On Sat, 8 Feb 2014 15:10:09 +1300
> Chris Bannister wrote:
>
> > On Fri, Feb 07, 2014 at 10:07:34PM +, Joe wrote:
> > > You can also remove any kernel metapackage e.g. linux-image-amd64.
> > > Apt will not normally attempt to replace what
On Sat, 8 Feb 2014 15:10:09 +1300
Chris Bannister wrote:
> On Fri, Feb 07, 2014 at 10:07:34PM +, Joe wrote:
> > You can also remove any kernel metapackage e.g. linux-image-amd64.
> > Apt will not normally attempt to replace whatever kernel you have
> > installed, as it is a bit risky, and as
> From: rwob...@hotmail.com
> To: debian-user@lists.debian.org
> Subject: RE: How to block kernel updates
> Date: Fri, 7 Feb 2014 21:37:22 +
>
>
>> Date: Fri, 7 Feb 2014 21:27:37 +000
On Fri, Feb 07, 2014 at 09:19:59PM +, Roelof Wobben wrote:
> Hello,
>
> I want to block the kernel updates because they cannot be installed ny lack
> of space.
I think that is the wrong solution. Personally, I'd do a reinstall in
your position. I'd backup home AND any configuration files yo
On Fri, Feb 07, 2014 at 10:07:34PM +, Joe wrote:
> You can also remove any kernel metapackage e.g. linux-image-amd64. Apt
> will not normally attempt to replace whatever kernel you have
> installed, as it is a bit risky, and as you say, needs quite a chunk
How is it risky? Anyway, you're forge
On Fri, Feb 07, 2014 at 11:26:37PM +0200, Georgi Naplatanov wrote:
> On 02/07/2014 11:19 PM, Roelof Wobben wrote:
> > Hello,
> >
> > I want to block the kernel updates because they cannot be installed ny lack
> > of space.
> >
> > How can I block them ?
>
> if the problem is disk space why you
On Fri, 2014-02-07 at 22:07 +, Joe wrote:
> wish me luck when I reboot...
You don't need luck.
JFTR, additional few bytes will be released after deleting modules
in /lib/modules/ resp. after removing dkms entries for removed kernel
versions.
--
To UNSUBSCRIBE, email to debian-user-requ...
On Fri, 7 Feb 2014 21:37:22 +
Roelof Wobben wrote:
>
> > Date: Fri, 7 Feb 2014 21:27:37 +
> > Subject: Re: How to block kernel updates
> > From: rc.rattusrat...@gmail.com
> > To: debian-user@lists.debian.org
>
> Date: Fri, 7 Feb 2014 21:27:37 +
> Subject: Re: How to block kernel updates
> From: rc.rattusrat...@gmail.com
> To: debian-user@lists.debian.org
>
> On 7 February 2014 21:19, Roelof Wobben wrote:
>> Hello,
>>
>>
On 02/07/2014 11:19 PM, Roelof Wobben wrote:
> Hello,
>
> I want to block the kernel updates because they cannot be installed ny lack
> of space.
>
> How can I block them ?
>
> Roelof
Hi Roelof,
if the problem is disk space why your primary concern i
On 7 February 2014 21:19, Roelof Wobben wrote:
> Hello,
>
> I want to block the kernel updates because they cannot be installed ny lack
> of space.
>
> How can I block them ?
>
> Roelof
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Troub
On 07/02/14 21:19, Roelof Wobben wrote:
Hello,
I want to block the kernel updates because they cannot be installed ny lack of
space.
How can I block them ?
Roelof
One way is to put a particular package version on "hold". See for
instance 'man aptitude':
r
Hello,
I want to block the kernel updates because they cannot be installed ny lack of
space.
How can I block them ?
Roelof
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.de
34 matches
Mail list logo
