Re: update-grub: how to avoid scanning all devices

On 15 Dec 2017 at 13:42, Brian wrote: > Purge os-prober. Thanks, that's exactly what I was looking for. Steve

Re: update-grub: how to avoid scanning all devices

On Fri 15 Dec 2017 at 20:33:29 +0100, Pascal Hambourg wrote: > Le 15/12/2017 à 18:18, Brian a écrit : > > On Fri 15 Dec 2017 at 17:53:57 +0100, Pascal Hambourg wrote: > > > > > . > > > > > > ‘GRUB_OS_PROBER_SKIP_LIST’ > > > > > > Lis

Re: update-grub: how to avoid scanning all devices

Le 15/12/2017 à 18:18, Brian a écrit : On Fri 15 Dec 2017 at 17:53:57 +0100, Pascal Hambourg wrote: . ‘GRUB_OS_PROBER_SKIP_LIST’ List of space-separated FS UUIDs of filesystems to be ignored from os-prober output. For efi chainload

Re: update-grub: how to avoid scanning all devices

On Fri 15 Dec 2017 at 17:53:57 +0100, Pascal Hambourg wrote: > Le 15/12/2017 à 17:40, Brian a écrit : > > On Fri 15 Dec 2017 at 16:31:54 +0100, Pascal Hambourg wrote: > > > > > Le 15/12/2017 à 14:42, Richard Owlett a écrit : > > > > > > > > I have 2 similar problems which wouldn't be solved by d

Re: update-grub: how to avoid scanning all devices

Le 15/12/2017 à 17:40, Brian a écrit : On Fri 15 Dec 2017 at 16:31:54 +0100, Pascal Hambourg wrote: Le 15/12/2017 à 14:42, Richard Owlett a écrit : I have 2 similar problems which wouldn't be solved by disabling os-prober. The common characteristic is wishing to probe all operating systems r

Re: update-grub: how to avoid scanning all devices

On Fri 15 Dec 2017 at 16:31:54 +0100, Pascal Hambourg wrote: > Le 15/12/2017 à 14:42, Richard Owlett a écrit : > > > > I have 2 similar problems which wouldn't be solved by disabling os-prober. > > > > The common characteristic is wishing to probe all operating systems > > residing on on a speci

Re: update-grub: how to avoid scanning all devices

Le 15/12/2017 à 14:42, Richard Owlett a écrit : I have 2 similar problems which wouldn't be solved by disabling os-prober. The common characteristic is wishing to probe all operating systems residing on on a specific physical device. I multi-boot. There may be an OS on any number of mounted d

Re: update-grub: how to avoid scanning all devices

On 12/15/2017 06:43 AM, Pascal Hambourg wrote: Le 15/12/2017 à 13:18, Steve Keller a écrit : When calling update-grub, it scans all devices for operating systems to put into the GRUB config. It even mounts all block devices to do the scan. I'd like to avoid this and let it scan only a number o

Re: update-grub: how to avoid scanning all devices

Le 15/12/2017 à 13:18, Steve Keller a écrit : When calling update-grub, it scans all devices for operating systems to put into the GRUB config. It even mounts all block devices to do the scan. I'd like to avoid this and let it scan only a number of configured directories, in my case only /boot.

Re: update-grub: how to avoid scanning all devices

On Fri 15 Dec 2017 at 13:18:17 +0100, Steve Keller wrote: > When calling update-grub, it scans all devices for operating systems > to put into the GRUB config. It even mounts all block devices to do > the scan. I'd like to avoid this and let it scan only a number of > configured directories, in

Re: update-grub

On Fri, 21 Feb 2014, Ric Moore wrote: > After bending my brains for a day fixing little problems, after > upgrading to Jessie, I'm noticing a weird behavior. > > I have Ubuntu on /dev/sda3 and Debian on /dev/sdb1. When I run > update-grub, it notices the Ubuntu partition yet when I boot, the ol

Re: update-grub

On 21/02/14 20:27, Scott Ferguson wrote: > On 21/02/14 20:06, Ric Moore wrote: >> After bending my brains for a day fixing little problems, after >> upgrading to Jessie, I'm noticing a weird behavior. >> >> I have Ubuntu on /dev/sda3 and Debian on /dev/sdb1. When I run >> update-grub, it notices th

Re: update-grub

On 21/02/14 20:06, Ric Moore wrote: > After bending my brains for a day fixing little problems, after > upgrading to Jessie, I'm noticing a weird behavior. > > I have Ubuntu on /dev/sda3 and Debian on /dev/sdb1. When I run > update-grub, it notices the Ubuntu partition yet when I boot, the old > s

Re: Update GRUB to GRUB2 / Lenny to Squeeze

Tom H wrote: > On Sun, Jun 6, 2010 at 5:30 PM, lrhorer wrote: > You can't load modules for grub-probe. > > But you can for grub-install. > > The default modules that I have in a Sid VM for an install without > mdraid or lvm are: > minicmd, true, loadenv, extcmd, test,

Re: Update GRUB to GRUB2 / Lenny to Squeeze

On Sun, Jun 6, 2010 at 5:30 PM, lrhorer wrote: You can't load modules for grub-probe. But you can for grub-install. The default modules that I have in a Sid VM for an install without mdraid or lvm are: minicmd, true, loadenv, extcmd, test, sh, normal, charset, te

Re: Update GRUB to GRUB2 / Lenny to Squeeze

>>> You can't load modules for grub-probe. >>> >>> But you can for grub-install. >>> >>> The default modules that I have in a Sid VM for an install without >>> mdraid or lvm are: >>> minicmd, true, loadenv, extcmd, test, sh, normal, charset, terminal, >>> crypto, boot, part_msdos, ext2, fshelp, bio

Re: Update GRUB to GRUB2 / Lenny to Squeeze

lrhorer wrote: > > I upgraded a box from "Lenny" to "Squeeze", but the update of > GRUB to > GRUB2 failed. I've cobbled together a procedure which I think will work and which is (I hope) safe: 1. Comment out the entries for /dev/md1 in /etc/fstab and /etc/mdadm/mdadm.c

Re: Update GRUB to GRUB2 / Lenny to Squeeze

>>> You can't load modules for grub-probe. >>> >>> But you can for grub-install. >>> >>> The default modules that I have in a Sid VM for an install without >>> mdraid or lvm are: >>> minicmd, true, loadenv, extcmd, test, sh, normal, charset, terminal, >>> crypto, boot, part_msdos, ext2, fshelp, bio

Re: Update GRUB to GRUB2 / Lenny to Squeeze

On Sat, Jun 5, 2010 at 9:57 PM, lrhorer wrote: > Tom H wrote: > >> On Sat, May 29, 2010 at 8:56 PM, lrhorer wrote: >>> >>> I upgraded a box from "Lenny" to "Squeeze", but the update of GRUB to >>> GRUB2 failed.  The box is running a pair of IDE hard drives with >>> three partitions each.  Each pa

Re: Update GRUB to GRUB2 / Lenny to Squeeze

Tom H wrote: > On Sat, May 29, 2010 at 8:56 PM, lrhorer wrote: >> >> I upgraded a box from "Lenny" to "Squeeze", but the update of GRUB to >> GRUB2 failed.  The box is running a pair of IDE hard drives with >> three partitions each.  Each partition on each drive is a RAID1 >> mirror of the same p

Re: Update GRUB to GRUB2 / Lenny to Squeeze

On Sat, May 29, 2010 at 8:56 PM, lrhorer wrote: > > I upgraded a box from "Lenny" to "Squeeze", but the update of GRUB to > GRUB2 failed.  The box is running a pair of IDE hard drives with three > partitions each.  Each partition on each drive is a RAID1 mirror of the > same partition on the other

Re: update-grub and chroot

Hi, thanks everyone for the reply, On Sat, 18 Oct 2008 10:17:23 +0200, Shams Fantar wrote: >> I'm wondering if it is possible to update the grub menu.lst in the >> chroot with update-grub to reflect its appropriate kernel to boot from. >> > . . . You > should update your menu.lst outside the

Re: update-grub and chroot

T o n g wrote: > Hi, > > I tried to update my grub menu.lst in the chroot system using update- > grub, but it doesn't work. > > I'm wondering if it is possible to update the grub menu.lst in the chroot > to reflect its appropriate kernel to boot from. > > thanks > > Show us your error message

Re: update-grub and chroot

Hi, On Sat, Oct 18, 2008 at 03:05:52AM +, T o n g wrote: > Hi, > > I tried to update my grub menu.lst in the chroot system using update- > grub, but it doesn't work. > > I'm wondering if it is possible to update the grub menu.lst in the chroot > to reflect its appropriate kernel to boot fr

Re: update-grub problem

> However, that script DOES exist in the stated path. So what gives with > this? That path ("usr/sbin/update-grub") is relative to the current directory of the process using it. You probably want "/usr/sbin/update-grub". -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a su

Re: update-grub problem

What is the current working directory when this script gets run. You told it usr/sbin/update-grub not /usr/sbin/update-grub Note the difference. I still don't know why this is necessary. During the most recent kernel upgrade in Etch, I watched carefully for the usual warning message about not

Re: update-grub problem

John Fleming wrote: I'm trying to install linux-image-2.6.18-6-686 using apt-get. I recently made the recommended change in /etc/kernel-img.conf to include: postinst_hook = usr/sbin/update-grub postrm_hook = usr/sbin/update-grub When I run the apt-get install, the configuration fails with

Re: update-grub problem

On Wed, May 14, 2008 at 09:43:14PM -0400, John Fleming wrote: > I'm trying to install linux-image-2.6.18-6-686 using apt-get. I recently > made the recommended change in /etc/kernel-img.conf to include: > > postinst_hook = usr/sbin/update-grub > postrm_hook = usr/sbin/update-grub > > When I run

Re: update-grub problem

On Wed May 14 2008 18:43:14 John Fleming wrote: > I'm trying to install linux-image-2.6.18-6-686 using apt-get. I recently > made the recommended change in /etc/kernel-img.conf to include: > > postinst_hook = usr/sbin/update-grub > postrm_hook = usr/sbin/update-grub > > When I run the apt-get inst

Re: update-grub help, menu.lst is not changing

Thanks, i have tried this and it worked. On Nov 14, 2007 11:14 PM, Florian Kulzer <[EMAIL PROTECTED]> wrote: > On Wed, Nov 14, 2007 at 22:50:07 +0800, Louie Miranda wrote: > > Sorry about this newbie stuff question. > > But, last full Debian way of configuration i was in was in the lilo days > an

Re: update-grub help, menu.lst is not changing

On Wed, Nov 14, 2007 at 22:50:07 +0800, Louie Miranda wrote: > Sorry about this newbie stuff question. > But, last full Debian way of configuration i was in was in the lilo days and > Grub was still new. > > It has been a while since.. > > OK, here goes.. > > I have edited /boot/grub/menu.lst >

Re: Re: Update-grub not listing latest kernel first

OK Hans, thanks for confirming that. John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Update-grub not listing latest kernel first

John Talbut wrote: I have just done another kernel recompile and when I ran update-grub it listed the previous version of the kernel first (thereby making it the default kernel to boot). I give my kernels a version according to the date on which I compiled them, i.e.: vmlinuz-2.6.21-11sep7 v

Re: update-grub on aptitude install of new linux image...

On 12/1/05, Florian Ernst <[EMAIL PROTECTED]> wrote: > Hello *, > > On Wed, Nov 30, 2005 at 08:52:37PM -0600, Javier-Elias Vasquez-Vivas wrote: > > I'm wondering how to make update-grub automatically when ever a new > > linux image gets installed, whether from debian stock or generated > > through

Re: update-grub on aptitude install of new linux image...

Hello *, On Wed, Nov 30, 2005 at 08:52:37PM -0600, Javier-Elias Vasquez-Vivas wrote: > I'm wondering how to make update-grub automatically when ever a new > linux image gets installed, whether from debian stock or generated > through make-kpkg. Might be just editing a config file or something? /

Re: update-grub hangs

On Sun, 25 Apr 2004 16:40:34 +0200, Michael Sullivan wrote: > I'm trying to install a low-latency kernel and managed to get through > the whole process, but when I ran update-grub, it finds my old kernels > but not the new one. To me looks more your / a kernel problem than a grub-problem. Rebo