Re: SID: update-grub ---Warning: os-prober will not be executed to detect other bootable partitions.

On Thu 09 Dec 2021 at 08:28:37 (-0800), Peter Ehlert wrote: > the full error message at the end of update-grub: > > Warning: os-prober will not be executed to detect other bootable partitions. > Systems on them will not be added to the GRUB boot configuration. > Check GRUB_DI

SID: update-grub ---Warning: os-prober will not be executed to detect other bootable partitions.

the full error message at the end of update-grub: Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Question: why would this desirable? it's totall

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

filesystems include ext4? > > Filesystem instances, not filesystem types. > You can skip filesystems if you know their UUIDs. But e.g. an unreported > filesystem on a removable device won't be skipped. No removable device devices here. A machine with four ext4 partitions; noth

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

drive (intended to be multi-boot) for an unrelated machine. When I install the grub adds all OS from the "host" machine. By default, os-prober is installed and used by GRUB. So, after the installation you must boot the new system, disable os-prober or filter out its output as above an

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 n

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

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 > configure

update-grub: how to avoid scanning all devices

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. Scanning all devices is annoying be

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

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

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

update-grub

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 selection for Ubuntu is no longer ther

Re: Understanding output from update-grub with md

ce. Or so I thought. After updating installing latest 7.4 > kernel and rebooting I noticed it was running an older kernel. Output from > update-grub suggested that two unused spares somehow had older versions of > the / partition. I added them back as hot spares and then made them >

update-grub hangs when starting with systemd

Anyone know why update-grub would hang when started with systemd? Here is a successful normal run after booting with sysvinit: $ sudo update-grub Generating grub.cfg ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-3.11-2-amd64 Found

Re: how does update-grub choose the root filesystem

grub on both /dev/sda and /dev/sdb to boot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything abo

Re: how does update-grub choose the root filesystem

ot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. "grub-install /dev/sdX" use

Re: how does update-grub choose the root filesystem

dev/md0 comprising > /dev/sda1 and an empty slot. My desire is to install grub on both /dev/sda > and /dev/sdb to boot up from /dev/md0. When that is working I will retire > /dev/sdb1 and add it as the second component of /dev/md0. > > The magic appears to be in grub-mkconfig (wrappe

Re: how does update-grub choose the root filesystem

boot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. I want to achieve the mi

Re: how does update-grub choose the root filesystem

ing I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. I want to achieve the mimimum of downtime on the machine I am tryin

Re: how does update-grub choose the root filesystem

s the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. I want to achieve the mimimum of downtime on the machine I am trying to make this work on, and am worried that

Re: how does update-grub choose the root filesystem

On Wed, Jul 4, 2012 at 7:22 PM, Alan Chandler wrote: > > I am trying to figure out how to move my current rootfs to raid1 (its just a > partition at the moment). > > The plan is to make a a raid device, copy the current root fs in to it - but > I then need to tell grub to set up this up as the roo

how does update-grub choose the root filesystem

I am trying to figure out how to move my current rootfs to raid1 (its just a partition at the moment). The plan is to make a a raid device, copy the current root fs in to it - but I then need to tell grub to set up this up as the root for the boot. How do I do this? -- Alan Chandler http://w

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On 13/07/10 01:58 AM, Tom H wrote: > > Quite frankly, I thought that this had been fixed (I read it on either > the Debian or Ubuntu bug reporting system), but I came across this > problem last year and the script was looking for initrds of the form > "initrd.img-..." and therefore ignored "initra

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On Tue, Jul 13, 2010 at 2:02 AM, Sven Joachim wrote: > On 2010-07-13 07:45 +0200, H.S. wrote: > >> On 13/07/10 01:28 AM, Tom H wrote: >>> >>> Yes. The Fedora/RHEL initrd names are not recognized by Debian/Ubuntu's >>> grub... > > It should work in os-prober 1.39. Thanks for the info. As I said i

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On 2010-07-13 07:45 +0200, H.S. wrote: > On 13/07/10 01:28 AM, Tom H wrote: >> >> Yes. The Fedora/RHEL initrd names are not recognized by Debian/Ubuntu's >> grub... It should work in os-prober 1.39. > I see. Could you briefly explain why is that? Because Fedora uses initramfs$something as the

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On Tue, Jul 13, 2010 at 1:45 AM, H.S. wrote: > On 13/07/10 01:28 AM, Tom H wrote: >> On Tue, Jul 13, 2010 at 12:37 AM, H.S. wrote: >>> >>> It is missing the initrd line. Without that line the kernel does not >>> boot and panics and halts. >>> >>> I have to put the correct stanza myself in /etc/gr

Re: Why does not update-grub detect Fedora 13 installation?

g about grub-legacy here. > Any system that you install after Debian is added (in my experience) > or should be added to grub2's menu after update-grub is run. If you have os-prober installed, that is. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On 13/07/10 01:28 AM, Tom H wrote: > On Tue, Jul 13, 2010 at 12:37 AM, H.S. wrote: >> >> It is missing the initrd line. Without that line the kernel does not >> boot and panics and halts. >> >> I have to put the correct stanza myself in /etc/grub.d/40_custom to get >> the correct grub entry which

Re: Why does not update-grub detect Fedora 13 installation?

hould be added to grub2's menu after update-grub is run. -- 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/aanlktilmnipfuo3yugc519t4ibov2nihtrf5lbryb...@mail.gmail.com

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On Tue, Jul 13, 2010 at 12:37 AM, H.S. wrote: > On 12/07/10 03:07 PM, H.S. wrote: >> >> Curiously though, update-grub is now detecting Fedora 13! It was not > > Well, I wrote that too soon. > > Here is what update-grub puts in /boot/grub > /grub.cfg regard

Re: [SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

On 12/07/10 03:07 PM, H.S. wrote: > > Curiously though, update-grub is now detecting Fedora 13! It was not Well, I wrote that too soon. Here is what update-grub puts in /boot/grub /grub.cfg regarding the Fedora 13 installation: ### men

Re: Why does not update-grub detect Fedora 13 installation?

On 07/12/2010 12:17 PM, H.S. wrote: On a newly installed Debian Testing system, I installed Fedora 13 in a partition but chose not to install the boot loaded since I wanted to use Debian's boot loader for all OSes. Now when I do update-grub in Debian, it detects all OSes installed in the

[SOLVED] Re: Why does not update-grub detect Fedora 13 installation?

led either! And yet all my OSes, barring F13, > are being probed alright. So this makes me wonder, does grub-pc even use > it while probing for OSes? I just checked again and os-prober is intalled on my system. I am not sure why I missed this earlier. Curiously though, update-grub is now detect

Re: Why does not update-grub detect Fedora 13 installation?

ou install _after_ Debian will not automagically show up in the menu. You'll probably have to add it by hand then. >> but grub2 uses it in /etc/grub.d/30_os-prober. > > Which seems to be a script/routine that first checks for the availability > of "os-prober". So it

Re: Why does not update-grub detect Fedora 13 installation?

tems, Debian installer auto-detected my other linux OS (openSUSE 10.3) and added to "/boot/grub/menu.lst", I had to do nothing :-? > but grub2 uses it in /etc/grub.d/30_os-prober. Which seems to be a script/routine that first checks for the availability of "os-prober". So

Re: Why does not update-grub detect Fedora 13 installation?

On 2010-07-12 19:41 +0200, Camaleón wrote: > On Mon, 12 Jul 2010 19:22:29 +0200, Sven Joachim wrote: > >> On 2010-07-12 19:09 +0200, Camaleón wrote: >> >>> Also, take a look into the bugs that have already filled for grub-pc: >>> >>> http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=grub-pc >>

Re: Why does not update-grub detect Fedora 13 installation?

On 12/07/10 01:41 PM, Camaleón wrote: > On Mon, 12 Jul 2010 19:22:29 +0200, Sven Joachim wrote: > >> On 2010-07-12 19:09 +0200, Camaleón wrote: >> >>> Also, take a look into the bugs that have already filled for grub-pc: >>> >>> http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=grub-pc >> >> s/

Re: Why does not update-grub detect Fedora 13 installation?

On 12/07/10 01:22 PM, Sven Joachim wrote: > On 2010-07-12 19:09 +0200, Camaleón wrote: > >> Also, take a look into the bugs that have already filled for grub-pc: >> >> http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=grub-pc > > s/grub-pc/os-prober/ > > Foreign operating systems are (suppose

Re: Why does not update-grub detect Fedora 13 installation?

On Mon, 12 Jul 2010 19:22:29 +0200, Sven Joachim wrote: > On 2010-07-12 19:09 +0200, Camaleón wrote: > >> Also, take a look into the bugs that have already filled for grub-pc: >> >> http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=grub-pc > > s/grub-pc/os-prober/ > > Foreign operating syste

Re: Why does not update-grub detect Fedora 13 installation?

On 2010-07-12 19:09 +0200, Camaleón wrote: > Also, take a look into the bugs that have already filled for grub-pc: > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=grub-pc s/grub-pc/os-prober/ Foreign operating systems are (supposed to be) detected by os-prober, so if Fedora 13 does not

Re: Why does not update-grub detect Fedora 13 installation?

On 12/07/10 01:09 PM, Camaleón wrote: > > I think windows OS falls apart (as there are no "vmlinuz" files to > detect) but fedora9 should be the same case than Fedora13, provided that > is also located in a different disk. > > When you run the "update-grub&qu

Re: Why does not update-grub detect Fedora 13 installation?

On Mon, 12 Jul 2010 12:24:44 -0400, H.S. wrote: > On 12/07/10 12:15 PM, Camaleón wrote: >> I don't know so much how the "new beast" (GRUB2) works, but if "man >> update-grub¹" is right, it will detect all the "vmlinuz" files that are >>

Re: Why does not update-grub detect Fedora 13 installation?

On 12/07/10 12:15 PM, Camaleón wrote: > On Mon, 12 Jul 2010 00:17:53 -0400, H.S. wrote: > > (...) > >> Now when I do update-grub in Debian, it detects all OSes installed in >> the hard drives connected to the system, but does not detect Fedora 13. >> I had to man

Re: Why does not update-grub detect Fedora 13 installation?

On Mon, 12 Jul 2010 00:17:53 -0400, H.S. wrote: (...) > Now when I do update-grub in Debian, it detects all OSes installed in > the hard drives connected to the system, but does not detect Fedora 13. > I had to manually add the stanza lines for F13 to get its option in the > gr

Why does not update-grub detect Fedora 13 installation?

On a newly installed Debian Testing system, I installed Fedora 13 in a partition but chose not to install the boot loaded since I wanted to use Debian's boot loader for all OSes. Now when I do update-grub in Debian, it detects all OSes installed in the hard drives connected to the system

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

be nor grub-install (for GRUB 2) will exist.  I can't pass > parameters to a binary that doesn't exist.  Passing them to the same > respective file for GRUB legacy won't help, either. If you don't have grub-install, you are missing grub-common, upon which grub-pc depends.

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

Update GRUB to GRUB2 / Lenny to Squeeze

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 drive. The first partitions on both drives are m

grub2, update-grub, /etc/grub.d

grub2 (provided by package grub-pc) Suppose you want to add something like "vga=791" to the linux line of one of the stanzas auto-configured by update-grub. What is the debian way to do this? I know how to edit the grub.cfg file to do this, but won't this file be replaced by t

Re: grub2, update-grub, /etc/grub.d

On Sat, Sep 26, 2009 at 11:36:00AM -0400, Hugh Lawson wrote: > grub2 (provided by package grub-pc) > > Suppose you want to add something like "vga=791" to the linux line of > one of the stanzas auto-configured by update-grub. > > What is the debian way to do thi

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

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. > &

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

update-grub and chroot

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 -- Tong (remove underscore(s) to rep

Re: Warning before running update-grub (was: Filing bug reports in Debian)

On Tuesday 14 October 2008, Eduardo M KALINOWSKI wrote: > Hal Vaughan wrote: > > Instead of just calling > > update-grub, a script could have said, "This update will > > re-write /boot/grub/menu.lst. Press return to continue." That > > would have bee

Re: Warning before running update-grub (was: Filing bug reports in Debian)

Hal Vaughan wrote: > Instead of just calling > update-grub, a script could have said, "This update will > re-write /boot/grub/menu.lst. Press return to continue." That would > have been enough (although giving a choice of continuing or not would > have been nice, t

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

update-grub problem

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 the error

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

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

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/upd

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 > &

update-grub problem

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 the error

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

gt; > > > # this following lines, remove! > > > #title Debian GNU/Linux, kernel 2.6.18-4-686 (single-user > mode) > > > #root(hd0,1) > > > #kernel /boot/vmlinuz-2.6.18-4-686 root=/dev/hda2 ro single > > > #initrd /boo

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

t=/dev/hda2 ro single > > #initrd /boot/initrd.img-2.6.18-4-686 > > #savedefault > > > > ### END DEBIAN AUTOMAGIC KERNELS LIST > > > > And after typing update-grub, that whole line goes back to being > UN-commented. How can i edit that permanently? I ha

update-grub help, menu.lst is not changing

l 2.6.18-4-686 (single-user mode) > #root(hd0,1) > #kernel /boot/vmlinuz-2.6.18-4-686 root=/dev/hda2 ro single > #initrd /boot/initrd.img-2.6.18-4-686 > #savedefault > > ### END DEBIAN AUTOMAGIC KERNELS LIST > And after typing update-grub, that whole

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

Update-grub not listing latest kernel first

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 vmlinuz-2.6.21-18jul7

update-grub path change

After the today Grub update (Sid): - I must remove the full paths from /etc/kernel-img.conf or - I must change the paths because update-grub now is in /usr/sbin/ instead of /sbin/ My doubt is because this apt-listchanges note: -- grub (0.97-16) unstable

Re: Where is the script update-grub located?

David R. Litwin wrote: I have the same problem, and there allready is a thread about it, but without any hopes. I didn't try update-grub because i don't think this is the problem, but if you find something please post ... Which thread is this? I should like

Re: Where is the script update-grub located?

I have the same problem, and there allready is a thread about it, butwithout any hopes. I didn't try update-grub because i don't think this is the problem, but if you find something please post ...Which thread is this? I should like to read it.-- —A watched bread-crumb never boils.—My h

Re: Where is the script update-grub located?

I have the same problem, and there allready is a thread about it, but without any hopes. I didn't try update-grub because i don't think this is the problem, but if you find something please post ... Andrei -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "u

Re: Where is the script update-grub located?

On Monday, 12 December 2005 at 23:36:03 -0500, David R. Litwin wrote: > > In any case, I think anyway that update-grub could not work from > > Windows, since it's a Linux program, right? > > > I was wondering about that myself. I thought it best to at least try it,

Re: Where is the script update-grub located?

In any case, I think anyway that update-grub could not work fromWindows, since it's a Linux program, right? I was wondering about that myself. I thought it best to at least try it, though. Not much success since I can't even find it, though You should be able to do anything you nee

Re: Where is the script update-grub located?

can run it > > from windows. > > $ dpkg -L grub > > > I'm afraid that that doesn't work from Windows > > > > $ locate update-grub > > This says it doesn't exist > > Now what? Next time I&#x

Re: Where is the script update-grub located?

On 12/12/05, Ron Johnson <[EMAIL PROTECTED]> wrote: On Mon, 2005-12-12 at 16:05 -0500, David R. Litwin wrote:> I should like to know where the actual script is so that I can run it> from windows.$ dpkg -L grub I'm afraid that that doesn't work from Windows  $ locate update-grubThis says it doe

Re: Where is the script update-grub located?

On Mon, 2005-12-12 at 16:05 -0500, David R. Litwin wrote: > I should like to know where the actual script is so that I can run it > from windows. $ dpkg -L grub $ locate update-grub -- - Ron Johnson, Jr. Jefferson, LA USA

Where is the script update-grub located?

the effect that /sys/boot/hda5/dev can not be found (I'll give you the exact wording if I need to). I beleive that this can be solved with update-grub, but I do not know where it is so that I can run it from Windows. I thank you kindly in advance.-- —A watched bread-crumb never boils.—My hover-

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 debia

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 fil

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

Hi, 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? Thx, -- Javier-Elias Vasquez-Vivas

update-grub in 3.1r0a assigns wrong root device, cannot boot with 2.4

Two boot problems I ran into with the 3.1 r0a release: 1. My only drive is /dev/hde, /dev/hda is a cdrom, /dev/hde6 is the Linux root partition: /dev/hde6 78626 15878540400608+ 83 Linux update-grub wrote (hd0,0) as the root device into the AUTOMAGIC KERNELS LIST in /boot

Sarge and update-grub

I have been trying to compile a 2.6.9 kernel under woody. I used backports, but the kernels kept crashing - kernel panics, etc. So then I upgraded to sarge, using apt-get dist-upgrade and after changing my sources.list. I now have a problem with update-grub. It just seems to stop after

update-grub and kopt_x_y_z.

According to /boot/grub/menu.lst, ## If you want special options for specifiv kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. What am I doing wrong with # kopt_2_6_3=/dev/sdb1 ro console=tty0 console=ttyS1,9600n8 ? It seems to be ignored a

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

update-grub hangs

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. I added the new one by hand, copying the portion of menu.lst that specifies a kernel, changing the name, and copying the e