Re: How to block kernel updates
On Sun, 9 Feb 2014 01:40:59 +0200 Andrei POPESCU andreimpope...@gmail.com 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 newer kernel packages might actually be safer than upgrading the same kernel, because unless you remove it yourself the old kernel image will still be available and selectable in the grub menu. Unless it messes up the update-grub... -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140209105639.5ce71...@jretrading.com
Re: How to block kernel updates
On Sat, 8 Feb 2014 15:10:09 +1300 Chris Bannister cbannis...@slingshot.co.nz 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 you say, needs quite a chunk How is it risky? I run three or four sid installations. Occasionally a new kernel does not boot, often due to a grub problem. There was a year or so when someone forgot that a separate boot partition is possible three times. The second and third occasions were at least easy to fix once I knew what was happening. Anyway, you're forgetting about security updates. Yes, it wasn't intentional, I forgot to return things to normal once the problem had been fixed. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140208085550.76675...@jretrading.com
Re: How to block kernel updates
On Sat, Feb 08, 2014 at 08:55:50AM +, Joe wrote: On Sat, 8 Feb 2014 15:10:09 +1300 Chris Bannister cbannis...@slingshot.co.nz 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 you say, needs quite a chunk How is it risky? I run three or four sid installations. Occasionally a new kernel does not boot, often due to a grub problem. 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. Hopefully, the average newbie to this list does not run Sid, but giving the impression that APT won't replace kernels as it is a bit risky is incorrect and misleading. APT will happily replace any package you tell it too, including kernels. Of course, for a security patch, the package name doesn't change, just the version -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140208094042.GA14729@tal
Re: How to block kernel updates
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 home partion, your choice, now that you know the pitfalls of choosing the wrong sizes. :) BTW, there is probably more wisdom in the results of a Google search than I could post with just a few minutes thought. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140208095049.GB14729@tal
RE: How to block kernel updates
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 15:10:09 +1300 Chris Bannister cbannis...@slingshot.co.nz 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 you say, needs quite a chunk How is it risky? I run three or four sid installations. Occasionally a new kernel does not boot, often due to a grub problem. 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. Hopefully, the average newbie to this list does not run Sid, but giving the impression that APT won't replace kernels as it is a bit risky is incorrect and misleading. 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. Roelof -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/dub121-w31a238505241730cf42c9ae...@phx.gbl
Re: How to block kernel updates
On Sat, 8 Feb 2014 22:40:43 +1300 Chris Bannister cbannis...@slingshot.co.nz wrote: On Sat, Feb 08, 2014 at 08:55:50AM +, Joe wrote: On Sat, 8 Feb 2014 15:10:09 +1300 Chris Bannister cbannis...@slingshot.co.nz 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 you say, needs quite a chunk How is it risky? I run three or four sid installations. Occasionally a new kernel does not boot, often due to a grub problem. 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. Hopefully, the average newbie to this list does not run Sid, but giving the impression that APT won't replace kernels as it is a bit risky is incorrect and misleading. APT will happily replace any package you tell it too, including kernels. Of course, for a security patch, the package name doesn't change, just the version Yes, which is why the metapackage is necessary if you want to keep up with the latest kernel automatically. 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, but hopefully listbugs shows the worst problems, and I can deal with trouble with minor packages. I do look carefully at new kernels, and have a quick check on the Net to see if anyone else has had problems, so I consider it a risk to upgrade a kernel in sid, or even testing, automatically, given the chance that I will be distracted and fail to notice it. Yes, I realise I should carefully scrutinise every single package before upgrading it, not just kernels, but if you use sid in anger, and there's no point in just keeping it around as a curiosity, then life is too short. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140208100250.33264...@jretrading.com
Re: How to block kernel updates
On Sat, 8 Feb 2014 09:52:17 + Roelof Wobben rwob...@hotmail.com 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 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 should be backing it up anyway. On a server, there is a risk that /var will suddenly explode in size or just enlarge slowly without being managed properly. This cannot be allowed to choke the system and kill it, so at least /var will have a separate partition. The chance of this happening on a workstation, generally rebooted every day and not running external services, is very small. Also, a workstation will normally have a human sitting at the screen most of the time, and a warning of low disc space can be dealt with. I run several partitions on my main workstation, because I experiment a bit, but my mobile installations are single-partition. The main workstation has LVM installed, so I can resize the partitions if necessary. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140208101311.7623e...@jretrading.com
Re: How to block kernel updates
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 updating, for each distro I use. For Arch in addition I should read the news on the homepage, but often I don't do it. Newbies are unable to evaluate what package updates could be very risky, so for Debian they should stay with stable and for Arch they always should read the news first. And they never ever should update Ubuntu :D. Btw. backups are a nice invention ;). A tidy packages cache is useful too. IIRC there's a roll back archive/repository for Debian too, but I don't remember the URL. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1391855057.7009.14.camel@archlinux
Re: How to block kernel updates
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, Feb 08, 2014 at 08:55:50AM +, Joe wrote: On Sat, 8 Feb 2014 15:10:09 +1300 Chris Bannister cbannis...@slingshot.co.nz 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 you say, needs quite a chunk How is it risky? I run three or four sid installations. Occasionally a new kernel does not boot, often due to a grub problem. 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. Hopefully, the average newbie to this list does not run Sid, but giving the impression that APT won't replace kernels as it is a bit risky is incorrect and misleading. 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. Roelof Hi Roelof, My workstation uses Debian GNU/Linux 7 (amd64), and my partition scheme is : Filesystem 1K-blocks Used Available Use% Mounted on rootfs 48059932 19464828 26153756 43% / /dev/md2 1872874484 833246124 944491852 47% /home As you can see the root file system is about 50GB and only 20GB are used. On the other hand directories what are supposed to contains a lot of data are linked to /home like /var/lib/postgresql - /home/postgresql, but you can do the same for valuable data such as git repositories, SVN, etc. Because your disk is only 80GB you may prefer single root partition, but do not forger to make backup when you are going to make a fresh install on the disk. HTH Best regards Georgi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52f6071f.8090...@oles.biz
Re: How to block kernel updates
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 should be backing it up anyway. Yes, one partition has got the advantage that you don't need to care about how to allocate HDD space. Even a separated /home partition isn't needed, _but_ if you e.g. need to read/write data for real-time usage, it might be useful to have a separated drive for this data. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1391855378.7009.18.camel@archlinux
Re: How to block kernel updates
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-0 bpo. I imagine it depends on what it has been told to do: safe-upgrade or full-upgrade. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201402081132.30613.lisi.re...@gmail.com
Re: How to block kernel updates
On Sat, Feb 8, 2014 at 6:32 AM, Lisi Reisz lisi.re...@gmail.com 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 upgraded me automatically from 3.10-x bpo to 3.11-x bpo then to 3.12-0 bpo. I imagine it depends on what it has been told to do: safe-upgrade or full-upgrade. Irrespective of upgrade/safe-upgrade and dist-upgrade/full-upgrade, linux-image won't be bumped up to a later kernel version if you don't have linux-image-arch installed. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=szzbg5ifwg6fh7ho4tknmompofuix0vuuvgwfj_73h...@mail.gmail.com
Re: How to block kernel updates
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-arch 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 the metapackage, but linux-image-3.12-1-amd64 only, than the kernel will not be automatically upgraded. There is no kernel part of this package: File list of package linux-image-amd64 in sid of architecture amd64 /usr/share/bug/linux-image-amd64/presubj /usr/share/doc/linux-image-amd64/NEWS.Debian.gz /usr/share/doc/linux-image-amd64/changelog.gz /usr/share/doc/linux-image-amd64/copyright Only the dependency is important. If you install http://packages.debian.org/sid/linux-image-3.12-1-amd64 without the metapackage, then it never will be upgraded, excepted there should be a version 3.12-2. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1391863615.7009.25.camel@archlinux
Re: How to block kernel updates
On Sat, Feb 8, 2014 at 5:24 AM, Ralf Mardorf ralf.mard...@alice-dsl.net 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 check all of them I always read all package names before updating, for each distro I use. For Arch in addition I should read the news on the homepage, but often I don't do it. Newbies are unable to evaluate what package updates could be very risky, so for Debian they should stay with stable and for Arch they always should read the news first. And they never ever should update Ubuntu :D. My parents upgrade their Ubuntu laptops, iPads, and iPhones the way that most non-technical do, when they're prompted to do so. They don't have any problems and there's no way that they'd be interested in checking package names - or understanding these names if they read them. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SxPC2qfV2taff52LQdgdDL_K1zGxrvppP-fzLJ=dfp...@mail.gmail.com
Re: How to block kernel updates
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-arch 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 the metapackage, but linux-image-3.12-1-amd64 only, than the kernel will not be automatically upgraded. There is no kernel part of this package: File list of package linux-image-amd64 in sid of architecture amd64 /usr/share/bug/linux-image-amd64/presubj /usr/share/doc/linux-image-amd64/NEWS.Debian.gz /usr/share/doc/linux-image-amd64/changelog.gz /usr/share/doc/linux-image-amd64/copyright Only the dependency is important. If you install http://packages.debian.org/sid/linux-image-3.12-1-amd64 without the metapackage, then it never will be upgraded, excepted there should be a version 3.12-2. Perhaps I'm wrong ;). However, a there would be no upgrade to 3.13. I'm not sure about the -2 build of the same kernel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1391863769.7009.27.camel@archlinux
Re: How to block kernel updates
On Sat, 2014-02-08 at 07:48 -0500, Tom H wrote: On Sat, Feb 8, 2014 at 5:24 AM, Ralf Mardorf ralf.mard...@alice-dsl.net 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 check all of them I always read all package names before updating, for each distro I use. For Arch in addition I should read the news on the homepage, but often I don't do it. Newbies are unable to evaluate what package updates could be very risky, so for Debian they should stay with stable and for Arch they always should read the news first. And they never ever should update Ubuntu :D. My parents upgrade their Ubuntu laptops, iPads, and iPhones the way that most non-technical do, when they're prompted to do so. They don't have any problems and there's no way that they'd be interested in checking package names - or understanding these names if they read them. I also had good luck with *buntus, but it's good luck, it could go wrong, I read it all the times on *buntu lists and I definitively disagree regarding to iOS upgrades for my iPad 2. I won the iPad, if I would have bought the iPad, I would be pissed off. And AFAIK it's impossible to downgrade to the last release of iOS that was stable on my iPad. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1391864045.7009.31.camel@archlinux
Re: How to block kernel updates
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 ralf.mard...@alice-dsl.net 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 check all of them I always read all package names before updating, for each distro I use. For Arch in addition I should read the news on the homepage, but often I don't do it. Newbies are unable to evaluate what package updates could be very risky, so for Debian they should stay with stable and for Arch they always should read the news first. And they never ever should update Ubuntu :D. My parents upgrade their Ubuntu laptops, iPads, and iPhones the way that most non-technical do, when they're prompted to do so. They don't have any problems and there's no way that they'd be interested in checking package names - or understanding these names if they read them. I also had good luck with *buntus, but it's good luck, it could go wrong, I read it all the times on *buntu lists and I definitively disagree regarding to iOS upgrades for my iPad 2. I won the iPad, if I would have bought the iPad, I would be pissed off. And AFAIK it's impossible to downgrade to the last release of iOS that was stable on my iPad. A little bit Linux related: There was jackd available for the iPad, but when Apple switched from iOS 6 to iOS 7, they changed something and it's impossible to use jackd now and also impossible for the coders to make jackd available for the iPad again. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1391864613.7009.34.camel@archlinux
Re: How to block kernel updates
On Saturday 08 February 2014 12:29:30 Tom H wrote: On Sat, Feb 8, 2014 at 6:32 AM, Lisi Reisz lisi.re...@gmail.com 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 upgraded me automatically from 3.10-x bpo to 3.11-x bpo then to 3.12-0 bpo. I imagine it depends on what it has been told to do: safe-upgrade or full-upgrade. Irrespective of upgrade/safe-upgrade and dist-upgrade/full-upgrade, linux-image won't be bumped up to a later kernel version if you don't have linux-image-arch installed. quote lisi@Tux-II:~$ aptitude show linux-image-amd64 Package: linux-image-amd64 State: installed Automatically installed: no Version: 3.12+55~bpo70+1 Priority: extra Section: kernel Maintainer: Debian Kernel Team debian-ker...@lists.debian.org Architecture: amd64 Uncompressed Size: 6,144 Depends: linux-image-3.12-0.bpo.1-amd64 Conflicts: linux-image-amd64 Provides: linux-latest-modules-3.12-0.bpo.1-amd64 Description: Linux for 64-bit PCs (meta-package) This package depends on the latest Linux kernel and modules for use on PCs with AMD64, Intel 64 or VIA Nano processors. This kernel also runs on a Xen hypervisor. It supports both privileged (dom0) and unprivileged (domU) operation. lisi@Tux-II:~$# /quote But recently (maybe a week or two?) I did have the earlier kernels installed, so it must upgrade the linux-image it uses - which surely comes in the end to the same thing? I did not install the metapackage deliberately, in fact I didn't know it was there before this thread. I installed kernel 3.10 from backports, which updated automatically first to to 3.11 and then to 3.12. Had I wanted it not to upgrade, would I have needed to search out the metapackage and remove it? Or hold it, of course. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201402081655.31085.lisi.re...@gmail.com
Re: How to block kernel updates
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...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1391882424.7009.49.camel@archlinux
Re: How to block kernel updates
On Sat, Feb 8, 2014 at 11:55 AM, Lisi Reisz lisi.re...@gmail.com wrote: On Saturday 08 February 2014 12:29:30 Tom H wrote: On Sat, Feb 8, 2014 at 6:32 AM, Lisi Reisz lisi.re...@gmail.com 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 upgraded me automatically from 3.10-x bpo to 3.11-x bpo then to 3.12-0 bpo. I imagine it depends on what it has been told to do: safe-upgrade or full-upgrade. Irrespective of upgrade/safe-upgrade and dist-upgrade/full-upgrade, linux-image won't be bumped up to a later kernel version if you don't have linux-image-arch installed. But recently (maybe a week or two?) I did have the earlier kernels installed, so it must upgrade the linux-image it uses - which surely comes in the end to the same thing? I did not install the metapackage deliberately, in fact I didn't know it was there before this thread. I installed kernel 3.10 from backports, which updated automatically first to to 3.11 and then to 3.12. Had I wanted it not to upgrade, would I have needed to search out the metapackage and remove it? Or hold it, of course. What I meant by kernel version was 3.2, 3.10, 3.11, 3.12. So linux-image-am64 in wheezy, wheezy-updates, wheezy/updates, will only pull in minor versions of 3.2. For example the latest upgrade is from 3.2.51-1 to 3.2.54-2. And linux-image-amd64 in wheezy-backports will pull in 3.10, 3.11, 3.12, ... You're given a choic in d-i to install the metapackage or a specific linux-image (perhaps only in expert mode). I'd remove linux-image-amd64 rather than hold it if you don't want your kernel to be upgraded to 3.13 when it becomes available, but I'd check first whether 3.12 will keep on receiving security patches. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SzrFFL=e9=miyjr2u8lsxjx+ogb-ylha30psigunqp...@mail.gmail.com
Re: How to block kernel updates
On Saturday 08 February 2014 20:48:14 Tom H wrote: On Sat, Feb 8, 2014 at 11:55 AM, Lisi Reisz lisi.re...@gmail.com wrote: On Saturday 08 February 2014 12:29:30 Tom H wrote: On Sat, Feb 8, 2014 at 6:32 AM, Lisi Reisz lisi.re...@gmail.com 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 upgraded me automatically from 3.10-x bpo to 3.11-x bpo then to 3.12-0 bpo. I imagine it depends on what it has been told to do: safe-upgrade or full-upgrade. Irrespective of upgrade/safe-upgrade and dist-upgrade/full-upgrade, linux-image won't be bumped up to a later kernel version if you don't have linux-image-arch installed. But recently (maybe a week or two?) I did have the earlier kernels installed, so it must upgrade the linux-image it uses - which surely comes in the end to the same thing? I did not install the metapackage deliberately, in fact I didn't know it was there before this thread. I installed kernel 3.10 from backports, which updated automatically first to to 3.11 and then to 3.12. Had I wanted it not to upgrade, would I have needed to search out the metapackage and remove it? Or hold it, of course. What I meant by kernel version was 3.2, 3.10, 3.11, 3.12. Yes, that is what I took you to mean. So linux-image-am64 in wheezy, wheezy-updates, wheezy/updates, will only pull in minor versions of 3.2. For example the latest upgrade is from 3.2.51-1 to 3.2.54-2. And linux-image-amd64 in wheezy-backports will pull in 3.10, 3.11, 3.12, ... You're given a choic in d-i to install the metapackage or a specific linux-image (perhaps only in expert mode). I've never seen this, and until now would not have known what it was on about. Nor was I given the choice when I installed 3.10 from backports. But it obviously installed the metapackage by default. I'd remove linux-image-amd64 rather than hold it if you don't want your kernel to be upgraded to 3.13 when it becomes available, but I'd check first whether 3.12 will keep on receiving security patches. 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! Thanks for the info. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201402082243.41863.lisi.re...@gmail.com
Re: How to block kernel updates
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 same kernel, because unless you remove it yourself the old kernel image will still be available and selectable in the grub menu. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: How to block kernel updates
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 newer kernel packages might actually be safer than upgrading the same kernel, because unless you remove it yourself the old kernel image will still be available and selectable in the grub menu. Thanks, Andrei. I do usually remove old kernels because I can't see the wood for the trees if there are too many there. At the moment I have again removed the ones I don't have any use for. I used to do so always. Well, keep one older one for if there are problems. But I am still scared of GRUB 2 and can't so easily see what is there as I could with GRUB 1. I must obviously conquer this. takes deep breath Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201402082356.17815.lisi.re...@gmail.com
How to block kernel updates
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.debian.org Archive: http://lists.debian.org/dub121-w24cd4590c0bc6eeb1c3d4cae...@phx.gbl
Re: How to block kernel updates
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': remove, purge, hold, unhold, keep, reinstall These commands are the same as “install”, but apply the named action to all packages given on the command line for which it is not overridden. The difference between hold and keep is that hold will cause a package to be ignored by future safe-upgrade or full-upgrade commands, while keep merely cancels any scheduled actions on the package. unhold will allow a package to be upgraded by future safe-upgrade or full-upgrade commands, without otherwise altering its state. -- Klaus -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52f54f82.6090...@gmail.com
Re: How to block kernel updates
On 7 February 2014 21:19, Roelof Wobben rwob...@hotmail.com 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. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/dub121-w24cd4590c0bc6eeb1c3d4cae...@phx.gbl You can pin or hold them depending on your package manager. I would update your current kernel when updates are available to get security fixes -- rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caozwb-qfed7mgs5h_jy+u5sh97gnq_kmv-p0f2xbxql_c28...@mail.gmail.com
Re: How to block kernel updates
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 is kernel updates, what will happen with other updates if they require additional space ? Best regards Georgi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52f54f8d.2090...@oles.biz
RE: How to block kernel updates
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 rwob...@hotmail.com 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. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/dub121-w24cd4590c0bc6eeb1c3d4cae...@phx.gbl You can pin or hold them depending on your package manager. I would update your current kernel when updates are available to get security fixes -- rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caozwb-qfed7mgs5h_jy+u5sh97gnq_kmv-p0f2xbxql_c28...@mail.gmail.com Thanks, it worked. I use the apt-mark way. Roelof -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/dub121-w31271159afccabb8d23925ae...@phx.gbl
Re: How to block kernel updates
On Fri, 7 Feb 2014 21:37:22 + Roelof Wobben rwob...@hotmail.com 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 On 7 February 2014 21:19, Roelof Wobben rwob...@hotmail.com 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. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/dub121-w24cd4590c0bc6eeb1c3d4cae...@phx.gbl You can pin or hold them depending on your package manager. I would update your current kernel when updates are available to get security fixes -- rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caozwb-qfed7mgs5h_jy+u5sh97gnq_kmv-p0f2xbxql_c28...@mail.gmail.com Thanks, it worked. I use the apt-mark way. Roelof 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 of additional space. The metapackage is used when you specifically want to stay upgraded to the latest of the appropriate type and are willing to fix the occasional problem. And I know it works because I've just remembered that I did exactly that some time ago, to block a particular upgrade I knew would cause trouble. Several kernels have passed by since then...wish me luck when I reboot... -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140207220734.34792...@jretrading.com
Re: How to block kernel updates
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...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1391817171.4466.2.camel@archlinux
Re: How to block kernel updates
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 your primary concern is kernel updates, what will happen with other updates if they require additional space ? https://lists.debian.org/debian-user/2014/02/msg00269.html -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140208020455.GC31249@tal
Re: How to block kernel updates
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 forgetting about security updates. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140208021009.GD31249@tal
Re: How to block kernel updates
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 you have changed. Then I'd do a reinstall and ensure that *THIS* time the / directory has a few G. I personally just use the whole disk most of the time: root@tal:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda536G 34G 182M 100% / udev 10M 0 10M 0% /dev tmpfs50M 332K 50M 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 293M 0 293M 0% /run/shm As you can see I have a bit of juggling to do now and then anyway, but this is just my laptop. I reckon I'd have more problems if I'd set up a partioning scheme. Of course, your usage and requirements may be different. If it is just a basic home desktop, I wouldn't worry. But blocking kernel updates is the wrong way to go, IMNSHO. How can I block them ? There are ways, but why compromise on security? -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140208022907.GE31249@tal
RE: How to block kernel updates
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 + 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 rwob...@hotmail.com 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. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/dub121-w24cd4590c0bc6eeb1c3d4cae...@phx.gbl You can pin or hold them depending on your package manager. I would update your current kernel when updates are available to get security fixes -- rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caozwb-qfed7mgs5h_jy+u5sh97gnq_kmv-p0f2xbxql_c28...@mail.gmail.com Oke, I will do a re-install of my 80G box. What will be a good partition scheme for normal desktop use? Roelof -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/dub121-w4224d8bd81903e11ed3abaae...@phx.gbl
