4:25 p.m.
Hi,
I am trying to roll my own Fedora 37 openbox spin (for personal use).
However, i came across the group @x86-baremetal-tools in
/usr/share/spin-kickstarts/fedora-live-base.ks
but I get:
# sudo dnf groupinstall @x86-baremetal-tools
Last metadata expiration check: 2:15:02 ago on Sat 21 Jan 2023 02:01:56 PM CST.
Module or Group 'x86-baremetal-tools' is not available.
Error: Nothing to do.
Where do i get this group?
Many thanks and best wishes,
Ranjan
10 a.m.
On Sat, 21 Jan 2023 16:25:51 -0600
Ranjan Maitra <mlmaitra(a)gmx.com> wrote:
Hi,
I am trying to roll my own Fedora 37 openbox spin (for personal use).
However, i came across the group @x86-baremetal-tools in
/usr/share/spin-kickstarts/fedora-live-base.ks
but I get:
# sudo dnf groupinstall @x86-baremetal-tools
Last metadata expiration check: 2:15:02 ago on Sat 21 Jan 2023
02:01:56 PM CST. Module or Group 'x86-baremetal-tools' is not
available. Error: Nothing to do.
Where do i get this group?
I was intrigued, so did some investigation. It is gone, no longer
needed.
https://pagure.io/fedora-kickstarts/pull-request/895
I also found this script that you might find useful, at least as a
reference.
https://gist.github.com/cyborganizer1/b34fa50afa2d79d3e002187497a133da
It has baremetal-tools in it, but you could just comment or remove that
line.
10:58 a.m.
On 22 Jan 2023 at 9:00, stan via users wrote:
Date sent: Sun, 22 Jan 2023 09:00:50 -0700
To: users(a)lists.fedoraproject.org
Subject: Re: @x86-baremetal-tools on F37
Organization: zohofree
Send reply to: Community support for Fedora
users <users(a)lists.fedoraproject.org>
From: stan via users
<users(a)lists.fedoraproject.org>
Copies to: stan <upaitag(a)zoho.com>
On Sat, 21 Jan 2023 16:25:51 -0600
Ranjan Maitra <mlmaitra(a)gmx.com> wrote:
> Hi,
>
> I am trying to roll my own Fedora 37 openbox spin (for personal use).
>
> However, i came across the group @x86-baremetal-tools in
> /usr/share/spin-kickstarts/fedora-live-base.ks
>
> but I get:
>
> # sudo dnf groupinstall @x86-baremetal-tools
> Last metadata expiration check: 2:15:02 ago on Sat 21 Jan 2023
> 02:01:56 PM CST. Module or Group 'x86-baremetal-tools' is not
> available. Error: Nothing to do.
>
> Where do i get this group?
I was intrigued, so did some investigation. It is gone, no longer
needed.
https://pagure.io/fedora-kickstarts/pull-request/895
I also found this script that you might find useful, at least as a
reference.
https://gist.github.com/cyborganizer1/b34fa50afa2d79d3e002187497a133da
It has baremetal-tools in it, but you could just comment or remove that
line.
Not sure what this group was for, but looked at the page,
and it talks about memtest86+ as well.
The latest grub iso of memtest86+ has two memtest
programs (One that works fine with legacy boot, and one
that works with UEFI boot).
I've used isomaster to pull the two programs, but change
names to memtest.leg and memtest.uefi and put them in
/boot. Then modifiy the /etc/grub.d/20_memtet86+ to
# !/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply
type the
# menu entries you want to add after this comment. Be careful not to
change
# the 'exec tail' line above.
menuentry 'Memtest Legacy' {
echo 'Loading memtest 6.01 for BIOS BOOT SYSTEM'
linux /memtest.leg
}
menuentry 'Memtest UEFI' {
echo 'Loading memtest 6.01 for UEFI BOOT SYSTEM'
linux /memtest.uefi
}
That then adds the two lines to the grub boot menu, and
picking the correct one for boot seems to work fine in
both cases.
As for baremetal backup, I've been maintainer of g4l
since 2004, and it is basically a disk imaging program,
and have had option to add it to grub menu as well.
Latest version does work with both legacy and uefi boot
in my test machine (not secure boot thou).
Use 40_custom with
# !/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply
type the
# menu entries you want to add after this comment. Be careful not to
change
# the 'exec tail' line above.
menuentry G4L_Version_0.63_video_800x600 {
set gfxpayload=800x600x16,800x600
linux /bz6x1.7 root=/dev/ram0 telnetd=yes
initrd /ramdisk.lzma
}
kernels built from kernel.org, and ramdisk.lzma built
using Fedora 36 as base at moment.
Just put files in /boot
10856224 Jan 19 00:28 bz6x1.7
26252475 Jan 22 18:03 ramdisk.lzma
also have an usb that uses grub4dos to boot with both
legacy and uefi options.
So, not exactly sure what they were doing with group.
Used it a lot with my computer labs before I retired, but
still use it to create back images and clone my home
machines.
Really like have working memtest86+ 6.01.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
11:07 a.m.
On Sun Jan22'23 09:00:50AM, Community Support for Fedora Users wrote:
From: stan via users <users(a)lists.fedoraproject.org>
Date: Sun, 22 Jan 2023 09:00:50 -0700
To: users(a)lists.fedoraproject.org
Cc: stan <upaitag(a)zoho.com>
Reply-To: Community support for Fedora users <users(a)lists.fedoraproject.org>
Subject: Re: @x86-baremetal-tools on F37
On Sat, 21 Jan 2023 16:25:51 -0600
Ranjan Maitra <mlmaitra(a)gmx.com> wrote:
> Hi,
>
> I am trying to roll my own Fedora 37 openbox spin (for personal use).
>
> However, i came across the group @x86-baremetal-tools in
> /usr/share/spin-kickstarts/fedora-live-base.ks
>
> but I get:
>
> # sudo dnf groupinstall @x86-baremetal-tools
> Last metadata expiration check: 2:15:02 ago on Sat 21 Jan 2023
> 02:01:56 PM CST. Module or Group 'x86-baremetal-tools' is not
> available. Error: Nothing to do.
>
> Where do i get this group?
I was intrigued, so did some investigation. It is gone, no longer
needed.
https://pagure.io/fedora-kickstarts/pull-request/895
I also found this script that you might find useful, at least as a
reference.
https://gist.github.com/cyborganizer1/b34fa50afa2d79d3e002187497a133da
It has baremetal-tools in it, but you could just comment or remove that
line.
Thanks, yes, that is what I did (uncommented the memtest and commented that line.) But is
this not a bug in the fedora-kickstarts package, since that line is part of a system-wide
file at: /usr/share/spin-kickstarts/fedora-live-base.ks
Btw, there is a bug in livecd-tools: see
https://github.com/livecd-tools/livecd-tools/issues/258 and I do not know how to get
around it. (There was a response to my bug report, but I do not understand it.)
So, my rolling of my own remix has come to a stop.
Many thanks and best wishes,
Ranjan
1 p.m.
On Sun, 22 Jan 2023 11:07:47 -0600
Ranjan Maitra <mlmaitra(a)gmx.com> wrote:
Thanks, yes, that is what I did (uncommented the memtest and
commented that line.) But is this not a bug in the fedora-kickstarts
package, since that line is part of a system-wide file at:
/usr/share/spin-kickstarts/fedora-live-base.ks
Yes, I surmise that the removal was not complete. You could open a
bugzilla on the package of that file to get it fixed.
fedora-kickstarts-0.36.0-0.3.fc37.noarch
Btw, there is a bug in livecd-tools: see
https://github.com/livecd-tools/livecd-tools/issues/258 and I do not
know how to get around it. (There was a response to my bug report,
but I do not understand it.)
So, it looks like it is the terminal login, and gdm, which is somehow
connected to login, but is not owned by any package. Isn't gdm the
gnome desktop manager? Maybe this is a relic that hasn't been cleaned
up after the move to Wayland?
/etc/X11/gdm
/etc/X11/gdm/Sessions
/etc/X11/gdm/Sessions/Blackbox
/etc/dconf/db/gdm
$ rpm -qf /etc/X11/gdm
file /etc/X11/gdm is not owned by any package
The only imgcreate I can find is
python3-imgcreate-31.0-2.fc37.x86_64
As far is I can tell, there is no library connected with that package.
Perhaps it is one of its dependencies that is causing the problem.
What happens if you try doing the creation in a virtual console? They
can be found at Ctrl-Alt-F[3-6]. Some are used by different processes,
so you will have to try until you get a login screen.
6:15 p.m.
My apologies, I did not see this email earlier.
On Sun Jan22'23 12:00:53PM, Community Support for Fedora Users wrote:
From: stan via users <users(a)lists.fedoraproject.org>
Date: Sun, 22 Jan 2023 12:00:53 -0700
To: users(a)lists.fedoraproject.org
Cc: stan <upaitag(a)zoho.com>
Reply-To: Community support for Fedora users <users(a)lists.fedoraproject.org>
Subject: Re: @x86-baremetal-tools on F37
On Sun, 22 Jan 2023 11:07:47 -0600
Ranjan Maitra <mlmaitra(a)gmx.com> wrote:
> Thanks, yes, that is what I did (uncommented the memtest and
> commented that line.) But is this not a bug in the fedora-kickstarts
> package, since that line is part of a system-wide file at:
> /usr/share/spin-kickstarts/fedora-live-base.ks
Yes, I surmise that the removal was not complete. You could open a
bugzilla on the package of that file to get it fixed.
fedora-kickstarts-0.36.0-0.3.fc37.noarch
Yes, I was thinking of doing this, and will do so now.
> Btw, there is a bug in livecd-tools: see
> https://github.com/livecd-tools/livecd-tools/issues/258 and I do not
> know how to get around it. (There was a response to my bug report,
> but I do not understand it.)
So, it looks like it is the terminal login, and gdm, which is somehow
connected to login, but is not owned by any package. Isn't gdm the
gnome desktop manager? Maybe this is a relic that hasn't been cleaned
up after the move to Wayland?
/etc/X11/gdm
/etc/X11/gdm/Sessions
/etc/X11/gdm/Sessions/Blackbox
/etc/dconf/db/gdm
$ rpm -qf /etc/X11/gdm
file /etc/X11/gdm is not owned by any package
The only imgcreate I can find is
python3-imgcreate-31.0-2.fc37.x86_64
As far is I can tell, there is no library connected with that package.
Perhaps it is one of its dependencies that is causing the problem.
What happens if you try doing the creation in a virtual console? They
can be found at Ctrl-Alt-F[3-6]. Some are used by different processes,
so you will have to try until you get a login screen.
_______________________________________________
Because I did not see your email earlier, I went ahead and tried the kickstart files that
are presumably the ones that are used to build the official Fedora spins. I tried the
kickstarts for the Workstation, the LXDE and the XFCE Live CDs. In all cases, the error is
the same.
Does this mean that the Fedora LiveCDs are created by some other process? I always assumed
that it was in the same manner as how I rolled my own personal spins, but with the
official kickstart files.
Why should it matter that I do the creations in a virtual screen? I setenforce to 0 and
then use livecd-creator on the .ks file to create my spin. Would a virtual console do
something else?
Many thanks and best wishes,
Ranjan
12:01 p.m.
On Mon, 23 Jan 2023 18:15:31 -0600
Ranjan Maitra <mlmaitra(a)gmx.com> wrote:
Because I did not see your email earlier, I went ahead and tried the
kickstart files that are presumably the ones that are used to build
the official Fedora spins. I tried the kickstarts for the
Workstation, the LXDE and the XFCE Live CDs. In all cases, the error
is the same.
Are those spins available for F37?
Does this mean that the Fedora LiveCDs are created by some other
process? I always assumed that it was in the same manner as how I
rolled my own personal spins, but with the official kickstart files.
If those are the scripts that they used, perhaps koji is part of the
removal of baremetal-tools that did not get cleaned up. So, it has the
package, and works fine.
Why should it matter that I do the creations in a virtual screen? I
setenforce to 0 and then use livecd-creator on the .ks file to create
my spin. Would a virtual console do something else?
Well, the issue seems to be something to do with gnome, so I was
thinking that maybe if you didn't have a gui running, it might work.
But, you ask a good question. Why should it matter? If the script
looks for that, it looks for that. My thoughts were that it somehow
used your environment when building the image. Doesn't seem plausible
in hindsight, so I think you are right.
12:52 p.m.
On Tue Jan24'23 11:01:11AM, Community Support for Fedora Users wrote:
From: stan via users <users(a)lists.fedoraproject.org>
Date: Tue, 24 Jan 2023 11:01:11 -0700
To: users(a)lists.fedoraproject.org
Cc: stan <upaitag(a)zoho.com>
Reply-To: Community support for Fedora users <users(a)lists.fedoraproject.org>
Subject: Re: @x86-baremetal-tools on F37
On Mon, 23 Jan 2023 18:15:31 -0600
Ranjan Maitra <mlmaitra(a)gmx.com> wrote:
> Because I did not see your email earlier, I went ahead and tried the
> kickstart files that are presumably the ones that are used to build
> the official Fedora spins. I tried the kickstarts for the
> Workstation, the LXDE and the XFCE Live CDs. In all cases, the error
> is the same.
Are those spins available for F37?
The kickstart files are, and I assumed that they created the F37 ISOs available. But
someone on the github who has a workaround says that those ISOs may be created in a
headless environment.
> Does this mean that the Fedora LiveCDs are created by some
other
> process? I always assumed that it was in the same manner as how I
> rolled my own personal spins, but with the official kickstart files.
If those are the scripts that they used, perhaps koji is part of the
removal of baremetal-tools that did not get cleaned up. So, it has the
package, and works fine.
I see.
> Why should it matter that I do the creations in a virtual
screen? I
> setenforce to 0 and then use livecd-creator on the .ks file to create
> my spin. Would a virtual console do something else?
Well, the issue seems to be something to do with gnome, so I was
thinking that maybe if you didn't have a gui running, it might work.
But, you ask a good question. Why should it matter? If the script
looks for that, it looks for that. My thoughts were that it somehow
used your environment when building the image. Doesn't seem plausible
in hindsight, so I think you are right.
No problem: btw, the workaround is here, I have not tried it yet, but will soon.
https://github.com/livecd-tools/livecd-tools/issues/258#issuecomment-1402...
Thanks again!
Best wishes,
Ranjan
8:54 p.m.
No problem: btw, the workaround is here, I have not tried it yet, but will soon.
https://github.com/livecd-tools/livecd-tools/issues/258#issuecomment-1402...
IN case anyone is interested, the error or whatever appears to have been introduced with
the update to 30.0 in python3-imgcreate. Copying the 27.9 version of fs.py to the current
fs.py from 31.0 makes the issue go away and a LiveCD is created.
Best wishes,
Ranjan
459
days inactive
465
days old
8 comments
3 participants
participants (3)
-
Michael D. Setzer II -
Ranjan Maitra -
stan