On Wed, 2024-06-05 at 13:37 +0200, Patrick Dupre via users wrote:
> Sorry for all this mail exchanges for a simple thing.
Multi-boot isn't a simple thing, there's a lot of hurdles. If you
needed to ask, you needed to ask. That's what the list is for.
--
NB: All unexpected mail to my mailbo
Thank for all these comments
>
> Patrick Dupre composed on 2024-06-04 23:57 (UTC+0200):
>
> > Disklabel type: gpt
> > Disk identifier: 5975BF99-78B4-4807-9CE4-C2BB0B8FE075
> >
> > Device Start End Sectors Size Type
> > /dev/sda1 2048 6143 4096 2M BIOS boot
> >
Patrick Dupre composed on 2024-06-04 23:57 (UTC+0200):
> Disklabel type: gpt
> Disk identifier: 5975BF99-78B4-4807-9CE4-C2BB0B8FE075
>
> Device Start End Sectors Size Type
> /dev/sda1 2048 6143 4096 2M BIOS boot
> /dev/sda2 6144 33560575 335544321
> On 6/5/24 1:04 AM, Patrick Dupre via users wrote:
> > Samuel S said
> >
> >> Number Start End Size Type File system Flags
> >> 2 1049kB 470MB 469MB primary ext4 boot
> >> 3 470MB 25.4GB 24.9GB primary ext4
> >> 4 25.4GB 82.0GB 56.6GB extended
> >> 5 25.4GB 82.0GB 56.6GB logical ext4
> >
> > You
On 6/5/24 1:04 AM, Patrick Dupre via users wrote:
Samuel S said
Number Start End Size Type File system Flags
2 1049kB 470MB 469MB primary ext4 boot
3 470MB 25.4GB 24.9GB primary ext4
4 25.4GB 82.0GB 56.6GB extended
5 25.4GB 82.0GB 56.6GB logical ext4
You don't have an EFI partition on this di
>
> On Tue, 4 Jun 2024 22:15:33 +0200, Patrick Dupre via users wrote:
>
> > I guess that when I run grub2-mkconfig there was a UBS key what connected
> > on the usb poer.
> >
> > I made some progresses, but not enough
> > I mounted the Fedora 40 / and
> > cp -a /mnt/fedrao40/boot/loader/entries/*
On Tue, 4 Jun 2024 22:15:33 +0200, Patrick Dupre via users wrote:
> I guess that when I run grub2-mkconfig there was a UBS key what connected on
> the usb poer.
>
> I made some progresses, but not enough
> I mounted the Fedora 40 / and
> cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/ent
Samuel Sieb composed on 2024-06-04 15:03 (UTC-0700):
> You don't have an EFI partition on this disk. It's not even a GPT
> partition table. So both installations will be fighting over the EFI
> partition on sda. And there's no easy way to add a boot entry for this
> installation.
A multiboo
Samuel Sieb composed on 2024-06-04 15:03 (UTC-0700):
> You don't have an EFI partition on this disk. It's not even a GPT >
> partition table. So both installations will be fighting over the EFI >
> partition on sda. And there's no easy way to add a boot entry for this >
> installation.
A mul
On 6/4/24 2:57 PM, Patrick Dupre via users wrote:
Model: ATA Maxtor 6Y080M0 (scsi)
Disk /dev/sdc: 82.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End SizeType File system Flags
2 1049kB 470MB 469MB primary ext4
Disklabel type: gpt
Disk identifier: 5975BF99-78B4-4807-9CE4-C2BB0B8FE075
Device Start End Sectors Size Type
/dev/sda1 2048 6143 4096 2M BIOS boot
/dev/sda2 6144 33560575 3355443216G Linux swap
/dev/sda3 33560576 34584575 1024000 500M EFI Sy
Samuel Sieb composed on 2024-06-04 13:49 (UTC-0700):
> Patrick Dupre via users wrote:
>> I am maintaining this machine for numerous years, it always passed the
>> updates,
>> but from 38 to 40, the same approach fails!
> You haven't given a full explanation of your disk layout,
If you provide
> On 6/4/24 1:39 PM, Patrick Dupre via users wrote:
> >>
> >> On 6/4/24 1:15 PM, Patrick Dupre via users wrote:
> >>> I made some progresses, but not enough
> >>> I mounted the Fedora 40 / and
> >>> cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
> >>>
> >>> cat
> >>> /boot/loader/
> Patrick Dupre via users composed on 2024-06-04 22:15 (UTC+0200):
>
> > I do not understand, because every thing seems OK
> > The file is at the right place as well as
> > System.map-6.8.11-300.fc40.x86_64
> > initramfs-6.8.11-300.fc40.x86_64.img
> > config-6.8.11-300.fc40.x86_64
> > symvers-6.8.1
Patrick Dupre via users composed on 2024-06-04 22:15 (UTC+0200):
> I do not understand, because every thing seems OK
> The file is at the right place as well as
> System.map-6.8.11-300.fc40.x86_64
> initramfs-6.8.11-300.fc40.x86_64.img
> config-6.8.11-300.fc40.x86_64
> symvers-6.8.11-300.fc40.x86_
On 6/4/24 1:39 PM, Patrick Dupre via users wrote:
On 6/4/24 1:15 PM, Patrick Dupre via users wrote:
I made some progresses, but not enough
I mounted the Fedora 40 / and
cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
cat
/boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8
>
> On 6/4/24 1:15 PM, Patrick Dupre via users wrote:
> > I made some progresses, but not enough
> > I mounted the Fedora 40 / and
> > cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
> >
> > cat
> > /boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8.9-100.fc38.x86_64.conf
> >
On 6/4/24 1:15 PM, Patrick Dupre via users wrote:
I made some progresses, but not enough
I mounted the Fedora 40 / and
cp -a /mnt/fedrao40/boot/loader/entries/* /boot/loader/entries
cat
/boot/loader/entries/dcdc9ed7e87243ec91d6d876cf7c3384-6.8.9-100.fc38.x86_64.conf
title Fedora Linux (6.8.11-
>
> On Tue, 4 Jun 2024 14:11:22 +0200, Patrick Dupre via users wrote:
>
> > > On Tue, 4 Jun 2024 13:11:03 +0200, Patrick Dupre via users wrote:
> > >
> > > > search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4
> > > > --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4
> > > > 0ab8c5a6-a
On Tue, 4 Jun 2024 14:11:22 +0200, Patrick Dupre via users wrote:
> > On Tue, 4 Jun 2024 13:11:03 +0200, Patrick Dupre via users wrote:
> >
> > > search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4
> > > --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4
> > > 0ab8c5a6-a344-48f8-afca-
> On 4 Jun 2024, at 13:39, Patrick Dupre wrote:
>
>
>
>
> On 4 Jun 2024, at 13:11, Patrick Dupre via users
> wrote:
>
> Fedora 38 when I will be sure that I can have control on the full
> installation.
> The risk is that I lost more control, typically on the installation of sda4
>
On 4 Jun 2024, at 13:11, Patrick Dupre via users wrote:
Fedora 38 when I will be sure that I can have control on the full installation.
The risk is that I lost more control, typically on the installation of sda4
The way I test out new Fedora releases is to see if the live image w
> On 4 Jun 2024, at 13:11, Patrick Dupre via users
> wrote:
>
> Fedora 38 when I will be sure that I can have control on the full
> installation.
> The risk is that I lost more control, typically on the installation of sda4
The way I test out new Fedora releases is to see if the live image
>
> On Tue, 4 Jun 2024 13:11:03 +0200, Patrick Dupre via users wrote:
>
> > search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4
> > --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4
> > 0ab8c5a6-a344-48f8-afca-e6187c589cde
> > else
> > search --no-floppy --fs-uuid --set=root
> > 0ab8
On Tue, 4 Jun 2024 13:11:03 +0200, Patrick Dupre via users wrote:
> search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4
> --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4
> 0ab8c5a6-a344-48f8-afca-e6187c589cde
> else
> search --no-floppy --fs-uuid --set=root 0ab8c5a6-a344-48f8-afca-
In my case
-rw-r--r--. 1 root root 160 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-0-memtest86+.conf
-rwxr-xr-x. 1 root root 417 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-0-rescue.conf
-rw-r--r--. 1 root root 362 Jun 4 12:26 11b839ed895a4a55a8ef89bc2dcec102-6.8.7-100.fc38.x86_64.conf
-rw
> On Tue, 4 Jun 2024 12:35:37 +0200, Patrick Dupre via users wrote:
>
> > but in the generated file (grub.cfg) there is no reference to Fedora 40
> > or sdc3
>
> What do you see in the grub2.cfg file section with the "10_linux" header?
### BEGIN /etc/grub.d/10_linux ###
insmod part_gpt
insmod ext
On Tue, 4 Jun 2024 12:35:37 +0200, Patrick Dupre via users wrote:
> but in the generated file (grub.cfg) there is no reference to Fedora 40
> or sdc3
What do you see in the grub2.cfg file section with the "10_linux" header?
--
___
users mailing list --
> On 4 Jun 2024, at 11:35, Patrick Dupre via users
> wrote:
>
> but in the generated file (grub.cfg) there is no reference to Fedora 40
> or sdc3
Fedora use BLS (boot loader specifcations) that are in /boot/loader/entries.
grub, by default, scans that folder and adds all the entries to the me
On Thu, Jun 15, 2023 at 8:03 PM Stephen Morris
wrote:
>
>
> On 12/6/23 05:24, George N. White III wrote:
>
> On Fri, Jun 9, 2023 at 9:54 PM Stephen Morris
> wrote:
>
>> Hi,
>> I have just used dnf to put on the currently available maintenance in
>> F38, having not put any on for a week or so
On 12/6/23 05:24, George N. White III wrote:
On Fri, Jun 9, 2023 at 9:54 PM Stephen Morris
wrote:
Hi,
I have just used dnf to put on the currently available
maintenance in F38, having not put any on for a week or so, after
upgrading from F37 via dnf system-upgrade a coupl
On 10/6/23 11:11, Tom Horsley wrote:
On Sat, 10 Jun 2023 10:53:58 +1000
Stephen Morris wrote:
fgrep: warning: fgrep is obsolescent; using grep -F
It means OCD linux geeks have decided they ought to remove an option used
for decades in uncounted thousands of shell scripts because they don't
lik
On 11 Jun 2023 at 16:24, George N. White III wrote:
From: "George N. White III"
Date sent: Sun, 11 Jun 2023 16:24:45 -0300
Subject: Re: grub2-mkconfig Strange Message
To: Community support for Fedora users
Send reply to: Community support for Fedora users
>
&g
On Fri, Jun 9, 2023 at 9:54 PM Stephen Morris
wrote:
> Hi,
> I have just used dnf to put on the currently available maintenance in
> F38, having not put any on for a week or so, after upgrading from F37 via
> dnf system-upgrade a couple of weeks ago.
> After putting on the maintenance I u
On Sat, 10 Jun 2023 19:41:34 +0200
Ralf Corsépius wrote:
> You mean, after a 15 years period of deprecation
Yes, I always examine ever single shell script I have and google
for any potential deprecations for every command I use every time
there is an update.
_
Am 10.06.23 um 03:11 schrieb Tom Horsley:
On Sat, 10 Jun 2023 10:53:58 +1000
Stephen Morris wrote:
fgrep: warning: fgrep is obsolescent; using grep -F
It means OCD linux geeks have decided they ought to remove an option used
for decades in uncounted thousands of shell scripts because they d
On Sat, 10 Jun 2023 10:53:58 +1000
Stephen Morris wrote:
> fgrep: warning: fgrep is obsolescent; using grep -F
It means OCD linux geeks have decided they ought to remove an option used
for decades in uncounted thousands of shell scripts because they don't
like it. They've done the same with egrep
"
To: "Community support for Fedora users"
Cc: "stan"
Subject: Re: grub2-mkconfig
try typing vgs/lvs/pvs and see if that also gets the warning.
Some prior centos version did also have this error for a while, I
never noticed any real issue with the programs reporting
> Sent: Saturday, June 03, 2023 at 8:11 PM
> From: "Roger Heflin"
> To: "Community support for Fedora users"
> Cc: "stan"
> Subject: Re: grub2-mkconfig
>
> try typing vgs/lvs/pvs and see if that also gets the warning.
> Some prior centos
try typing vgs/lvs/pvs and see if that also gets the warning.
Some prior centos version did also have this error for a while, I
never noticed any real issue with the programs reporting this.
For the most part this is just some attempt at reporting a "leaked"
file descriptor.I am not sure how o
On Fri, 2 Jun 2023 13:18:47 +0200
Patrick Dupre wrote:
> Hello,
>
> On a machine with a triple boot (an 3 HD, all fedora), I get a
> bunches of
>
> File descriptor 3 (pipe:[240388]) leaked on vgs invocation. Parent
> PID 75317: grub2-probe
>
> when I run grub2-mkconfig
> I have /boot/efi (UEFI
On 07/27/2018 11:44 AM, Patrick Dupre wrote:
On 07/27/2018 11:19 AM, Patrick Dupre wrote:
On 07/27/2018 04:14 AM, Patrick Dupre wrote:
If I run a system on VolSys1-root, and if I run grub2-mkconfig
with
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
in /etc/default/grub
I get in
> On 07/27/2018 11:19 AM, Patrick Dupre wrote:
> >>
> >> On 07/27/2018 04:14 AM, Patrick Dupre wrote:
> >>> If I run a system on VolSys1-root, and if I run grub2-mkconfig
> >>> with
> >>> GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
> >>> in /etc/default/grub
> >>> I get in grub.
On 07/27/2018 11:19 AM, Patrick Dupre wrote:
On 07/27/2018 04:14 AM, Patrick Dupre wrote:
If I run a system on VolSys1-root, and if I run grub2-mkconfig
with
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
in /etc/default/grub
I get in grub.cfg
linux16 /vmlinuz-4.16.11-100.fc26.x
>
> On 07/27/2018 04:14 AM, Patrick Dupre wrote:
> > If I run a system on VolSys1-root, and if I run grub2-mkconfig
> > with
> > GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
> > in /etc/default/grub
> > I get in grub.cfg
> >
> > linux16 /vmlinuz-4.16.11-100.fc26.x86_64 root=/dev/m
On 07/27/2018 04:14 AM, Patrick Dupre wrote:
If I run a system on VolSys1-root, and if I run grub2-mkconfig
with
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
in /etc/default/grub
I get in grub.cfg
linux16 /vmlinuz-4.16.11-100.fc26.x86_64 root=/dev/mapper/VolSys1-root ro
rd.lvm.
On 02/26/18 07:48, Celso Viana wrote:
> Is there no more "grub2-mkconfig" in Fedora 27?
dnf is your friend
egreshko@meimei system]$ dnf whatprovides *bin/grub2-mkconfig
Last metadata expiration check: 0:56:28 ago on Mon 26 Feb 2018 06:54:20 AM CST.
grub2-tools-1:2.02-22.fc27.x86_64 : Support
And even *better* would be to disable 30_os-prober, and instead of
copy pasting corrected grub2-mkconfig output into
/etc/grub.d/40_custom, would be to create menuentries using the
configfile command that point to the real grub.cfg for each distro on
your system. That way you use that distro's grub
Actually, nevermind. The easiest way out of this is to not
troubleshoot it. All the problems come from the
/etc/grub.d/30_os-prober section, so what I suggest doing is disable
it. Copy and paste the output from that section into
/etc/grub.d/40_custom, and then change the wrong parts, save it, then
ue, France
===
> Sent: Sunday, February 08, 2015 at 5:41 PM
> From: "Chris Murphy"
> To: "Community support for Fedora users"
> Subject: Re: grub2-mkconfig
>
> On S
On Sun, Feb 8, 2015 at 4:19 AM, Patrick Dupre wrote:
> ++ GRUB_CMDLINE_LINUX='rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True
> KEYTABLE=fr-latin9 rd.luks=0 LANG=en_US.UTF-8'
OK so the system GRUB is running in doesn't use LVM at all, apparently.
> + echo '### BEGIN /etc/grub.d/30_os-prober ###'
star
ot; in
+ grub_file_is_not_garbage /etc/grub.d/40_custom
+ test -f /etc/grub.d/40_custom
+ case "$1" in
+ return 0
+ test -x /etc/grub.d/40_custom
+ echo
+ echo '### BEGIN /etc/grub.d/40_custom ###'
### BEGIN /etc/grub.d/40_custom ###
+ /etc/grub.d/40_custom
# This file pro
What's the output from
rpm -q grub2
bash -x grub2-mkconfig
Try to post the entire thing to the forum. If it bounces back, then
stick the text file up somewhere and provide the URL.
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
htt
| | 59140 Dunkerque, France
===========
> Sent: Sunday, February 08, 2015 at 1:28 AM
> From: "Chris Murphy"
> To: "Community support for Fedora users"
> Subject: Re: grub2-mkconfig
>
> On Sat, Feb 7
On Sat, Feb 7, 2015 at 4:26 PM, Patrick Dupre wrote:
> Hello,
>
> grub2-mkconfig find systems which do not exist
> For example it find a partition root=/dev/mapper/VolGrpSys0-root
> which does not exist
> Where is kept VolGrpSys0?
What output do you get from os-prober?
--
Chris Murphy
--
users
On Mon, 24 Jun 2013 20:10:32 +0200
poma wrote:
> On 06/24/2013 06:25 PM, Frank Murphy wrote:
>
> > He forgot the version:
> > https://bugzilla.redhat.com/show_bug.cgi?id=908528
> > Fixed In Version: grub2-2.00-16
>
> Who's forgotten and what's forgotten!? :)
Figured you may have forgot to ment
Am 24.06.2013 18:25, schrieb Frank Murphy:
> On Mon, 24 Jun 2013 00:03:19 +0200
> Reindl Harald wrote:
>
>> Am 23.06.2013 20:43, schrieb poma:
>>> On 23.06.2013 20:16, Frank McCormick wrote:
>>>
Further to thisI checked the grub.cfg and the other
kernels are in the list. But G
On 06/23/2013 06:03 PM, Reindl Harald wrote:
Am 23.06.2013 20:43, schrieb poma:
On 23.06.2013 20:16, Frank McCormick wrote:
Further to thisI checked the grub.cfg and the other kernels are
in the list. But Grub is not displaying them when advanced options
is picked. It only displays th
On 06/24/2013 06:25 PM, Frank Murphy wrote:
> He forgot the version:
> https://bugzilla.redhat.com/show_bug.cgi?id=908528
> Fixed In Version: grub2-2.00-16
Who's forgotten and what's forgotten!? :)
Although your namesake mentions F17/18/19, he actually
alludes to the F19 - grub2-2.00-22.fc19 that
On 06/24/2013 12:25 PM, Frank Murphy wrote:
On Mon, 24 Jun 2013 00:03:19 +0200
Reindl Harald wrote:
Am 23.06.2013 20:43, schrieb poma:
On 23.06.2013 20:16, Frank McCormick wrote:
Further to thisI checked the grub.cfg and the other
kernels are in the list. But Grub is not displaying
On 06/24/2013 01:10 AM, Michael Schwendt wrote:
On Sun, 23 Jun 2013 14:16:22 -0400, Frank McCormick wrote:
On 06/23/2013 01:47 PM, Frank McCormick wrote:
Reposting on Fedora list because it's not only 19 affected
I noticed this morning that when I run grub2-mkconfig from my fedora
19 partiti
On Mon, 24 Jun 2013 00:03:19 +0200
Reindl Harald wrote:
> Am 23.06.2013 20:43, schrieb poma:
> > On 23.06.2013 20:16, Frank McCormick wrote:
> >
> >> Further to thisI checked the grub.cfg and the other
> >> kernels are in the list. But Grub is not displaying them when
> >> advanced optio
Am 24.06.2013 01:24, schrieb poma:
> …
>
> Oh yeah,
> this is the only problem I've found so far, which doesn't affect
> the functioning of the grub,
> $ rpm -ql grub2-tools-2.00-22.fc19 | grep default/grub
> /etc/default/grub
> $ file /etc/sysconfig/grub
> /etc/sysconfig/grub: broken symbolic l
Am 23.06.2013 20:43, schrieb poma:
> On 23.06.2013 20:16, Frank McCormick wrote:
>
>> Further to thisI checked the grub.cfg and the other kernels are
>> in the list. But Grub is not displaying them when advanced options
>> is picked. It only displays the one kernel.
>
> Simplify,
> /etc/d
Am 23.06.2013 20:16, schrieb Frank McCormick:
> On 06/23/2013 01:47 PM, Frank McCormick wrote:
>>
>> Reposting on Fedora list because it's not only 19 affected
>>
>>
>> I noticed this morning that when I run grub2-mkconfig from my fedora 19
>> partition, or from my 18 partition
>> it does not f
On Sun, 23 Jun 2013 14:16:22 -0400, Frank McCormick wrote:
> On 06/23/2013 01:47 PM, Frank McCormick wrote:
> >
> > Reposting on Fedora list because it's not only 19 affected
> >
> >
> > I noticed this morning that when I run grub2-mkconfig from my fedora
> > 19 partition, or from my 18 partition
On 06/23/2013 07:24 PM, poma wrote:
…
Oh yeah,
this is the only problem I've found so far, which doesn't affect
the functioning of the grub,
$ rpm -ql grub2-tools-2.00-22.fc19 | grep default/grub
/etc/default/grub
$ file /etc/sysconfig/grub
/etc/sysconfig/grub: broken symbolic link to `/etc/defa
…
Oh yeah,
this is the only problem I've found so far, which doesn't affect
the functioning of the grub,
$ rpm -ql grub2-tools-2.00-22.fc19 | grep default/grub
/etc/default/grub
$ file /etc/sysconfig/grub
/etc/sysconfig/grub: broken symbolic link to `/etc/default/grub'
You can do it yourself, righ
On 23.06.2013 21:27, Frank McCormick wrote:
…
> The only difference is GRUB_TERMINAL_OUTPUT
> ^
> and should true have double quotes around it ?
It's all the same for the single values.
I just tested,
- grub2-2.00-15.fc18.x86_64
- grub2-2.00-22.fc19.i686
and no problemos at all as you des
On 06/23/2013 02:43 PM, poma wrote:
On 23.06.2013 20:16, Frank McCormick wrote:
Further to thisI checked the grub.cfg and the other kernels are
in the list. But Grub is not displaying them when advanced options
is picked. It only displays the one kernel.
Simplify,
/etc/default/grub
GR
On 23.06.2013 20:16, Frank McCormick wrote:
> Further to thisI checked the grub.cfg and the other kernels are
> in the list. But Grub is not displaying them when advanced options
> is picked. It only displays the one kernel.
Simplify,
/etc/default/grub
GRUB_DISABLE_SUBMENU="true"
GRUB_TER
On 06/23/2013 01:47 PM, Frank McCormick wrote:
Reposting on Fedora list because it's not only 19 affected
I noticed this morning that when I run grub2-mkconfig from my fedora
19 partition, or from my 18 partition
it does not find all the kernels on a fedora 17 partition. There are
3 in Fedo
On Sun, 23 Dec 2012 10:00:22 +1000
"Michael D. Setzer II" wrote:
> Then it sorts correctly again. Seems to have been fixed in other
> later releases, but not in Fedora 16.
F16 EOL in a month or so.
There may not be many updates forthcoming.
--
Regards,
Frank
"The sheep lie"
--
users mailin
2012 13:30:10 -0700
Subject: Re: grub2-mkconfig with 3.2.10 kernels?
On Sun, Mar 18, 2012 at 2:50 PM, Michael D. Setzer II
wrote:
> Just did an update and it included a new kernel, but then on
> reboot after running grub2-mkconfig noticed that the newest one was
> not first. Seems to b
On 19 March 2012 19:53, Michael D. Setzer II wrote:
> I have had some messages on the grub list, and they confirmed
> the bug, and a fix seems to be to modify the
> /usr/lib/grub/grub_mkconfig_lib by changing one line from sort -n
> to sort -V. Note: That is an unofficial patch in this case does
On 19 Mar 2012 at 17:39, Piscium wrote:
Date sent: Mon, 19 Mar 2012 17:39:43 +
Subject:Re: grub2-mkconfig with 3.2.10 kernels?
From: Piscium
To: Community support for Fedora users
Send reply to: Community support
On 18 March 2012 15:00, Michael D. Setzer II wrote:
> Just did an update and it included a new kernel, but then on
> reboot after running grub2-mkconfig noticed that the newest one
> was not first. Seems to be sorting the 9 before the 10?
>
> Is this a bug?
I have been using Grub2 built from upst
On Sun, Mar 18, 2012 at 5:00 PM, Michael D. Setzer II
wrote:
> Just did an update and it included a new kernel, but then on
> reboot after running grub2-mkconfig noticed that the newest one
> was not first. Seems to be sorting the 9 before the 10?
>
> Is this a bug?
> I use the default="0", so thi
On 03/19/2012 09:22 AM, Michael D. Setzer II wrote:
>
> Did you run grub2-mkconfig -o /boot/grub2/grub.cfg?
>
> From what I have seen, when a new kernel is installed, it runs
> grubby, which doesn't make the recover option, so I generally run
> the grub2-mkconfig to get it have the listing, but i
On 19 Mar 2012 at 8:39, Ed Greshko wrote:
Date sent: Mon, 19 Mar 2012 08:39:00 +0800
From: Ed Greshko
To: Community support for Fedora users
Subject:Re: grub2-mkconfig with 3.2.10 kernels?
>
> On 03/19/2012 08:09 AM, Mic
On 03/19/2012 08:49 AM, Reindl Harald wrote:
> because "/etc/default/grub" in Fedora contains GRUB_DISABLE_RECOVERY="true"?
No, it isn't even listed there But it is listed in grub.rpmnew.
Learning about grub2 is on my list of things to learn more about. May have to
bump
the priority a bit.
Am 19.03.2012 01:39, schrieb Ed Greshko:
> On 03/19/2012 08:09 AM, Michael D. Setzer II wrote:
>> The issue is that the order is coming up wrong.
>> On my sytem, it adds the new kernel, but it is the in this order
>> from the grub.cfg file.
>>
>> menuentry 'Fedora Linux, with Linux 3.2.9-2.fc16
On 03/19/2012 08:09 AM, Michael D. Setzer II wrote:
> The issue is that the order is coming up wrong.
> On my sytem, it adds the new kernel, but it is the in this order
> from the grub.cfg file.
>
> menuentry 'Fedora Linux, with Linux 3.2.9-2.fc16.x86_64'
> menuentry 'Fedora Linux, with Linux 3.
On Monday 19 Mar 2012 10:09:50 Michael D. Setzer II wrote:
> On 19 Mar 2012 at 7:47, Ed Greshko wrote:
>
> > On 03/18/2012 11:00 PM, Michael D. Setzer II wrote:
> > > Just did an update and it included a new kernel, but then on
> > > reboot after running grub2-mkconfig noticed that the newest one
On 19 Mar 2012 at 7:47, Ed Greshko wrote:
Date sent: Mon, 19 Mar 2012 07:47:47 +0800
From: Ed Greshko
To: Community support for Fedora users
Subject:Re: grub2-mkconfig with 3.2.10 kernels?
Send reply to: Community
On 03/18/2012 11:00 PM, Michael D. Setzer II wrote:
> Just did an update and it included a new kernel, but then on
> reboot after running grub2-mkconfig noticed that the newest one
> was not first. Seems to be sorting the 9 before the 10?
>
> Is this a bug?
> I use the default="0", so this makes
86 matches
Mail list logo
