From: Daniel Cordero <gentoo.catalyst@xxoo.ws>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH 1/5] embedded: remove actions that are broken by default
Date: Fri, 22 May 2020 04:19:23 +0000 [thread overview]
Message-ID: <20200522041923.GB3784957@dysnomia.localdomain> (raw)
In-Reply-To: <CAEdQ38Hrh3cgic8XF9z3O5LhEadVAUJQL-NEw2DfetfrvobQLA@mail.gmail.com>
On Thu, May 21, 2020 at 01:41:18PM -0700, Matt Turner wrote:
> So, you must use the embedded target. Could you tell me how you use
> it, for what device, etc?
I produce mini-systemd tarballs to run under systemd-nspawn (or other
container systems). Sometimes, those tarballs can be used as
installation tarballs on bare metal systems, but in those cases
I need to bring my own kernel and bootloader.
systemd does require dynamic library dependencies so I modified (patches
probably will not sent upstream for inclusion) the embedded target to
pull in dependencies. The embedded target usually leaves dependency
resolution to the user (with embedded/packages).
> It's not obvious to me what specific tools this requires to be
> installed in the seed stage. Presumably you're referring to this?
>
> cmd([self.settings['controller_file'], 'bootloader',
> self.settings['target_path'].rstrip('/')]
>
> which eventually runs bootloader-setup.sh.
So the "controller.sh bootloader" is executed, but it kills the build in
the create_bootloader() function:
22 May 2020 03:58:27 UTC: NOTICE : --- Running action sequence: bootloader
NOTICE:catalyst:--- Running action sequence: bootloader
touch: cannot touch '/substrate/next/builds/amd64/minimal/20200521/embedded-amd64-minimal-20200521/livecd': No such file or directory
Unable to find grub-mkstandalone
22 May 2020 03:58:27 UTC: ERROR : CatalystError: cmd(['/substrate/next/catalyst/targets/embedded/controller.sh', 'bootloader', '/substrate/next/builds/amd64/minimal/20200521/embedded-amd64-minimal-20200521']) exited 1
ERROR:catalyst:CatalystError: cmd(['/substrate/next/catalyst/targets/embedded/controller.sh', 'bootloader', '/substrate/next/builds/amd64/minimal/20200521/embedded-amd64-minimal-20200521']) exited 1
I don't have grub in the seed stage (it _is_ optional), and don't make livecd images (I
don't know why it's trying to touch the builds/ path; maybe it wants tmp/...)
> I'd assume it's generally sensible to install a bootloader in the
> embedded target, and I don't think we have mechanism for customizing
> the action_sequence, so if we remove bootloader from the list then I
> think the python bootloader() function is just dead code, isn't it? I
> doubt that's the end result we want.
Personally, I just need the tarball of the mergeroot, so I don't need the
bootloader action. In lieu of this particular change, maybe some if
statements to see if bootloader-setup.sh can run successfully may be
needed.
prev parent reply other threads:[~2020-05-22 4:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 17:32 [gentoo-catalyst] [PATCH 1/5] embedded: remove actions that are broken by default Daniel Cordero
2020-05-21 17:32 ` [gentoo-catalyst] [PATCH 2/5] stagebase: allow specfiles to define install_mask Daniel Cordero
2020-05-21 20:45 ` Matt Turner
2020-05-21 17:32 ` [gentoo-catalyst] [PATCH 3/5] embedded/rm: use destpath to clean mergeroot Daniel Cordero
2020-05-21 20:46 ` Matt Turner
2020-05-21 17:32 ` [gentoo-catalyst] [PATCH 4/5] embedded/root_overlay: copy root overlay into destpath Daniel Cordero
2020-05-21 20:48 ` Matt Turner
2020-05-21 17:32 ` [gentoo-catalyst] [PATCH 5/5] Allow embedded target to unpack a root_overlay Daniel Cordero
2020-05-21 20:52 ` Matt Turner
2020-05-22 3:48 ` Daniel Cordero
2020-05-21 20:41 ` [gentoo-catalyst] [PATCH 1/5] embedded: remove actions that are broken by default Matt Turner
2020-05-21 22:08 ` Brian Dolbec
2020-05-22 0:22 ` Matt Turner
2020-05-22 4:19 ` Daniel Cordero [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200522041923.GB3784957@dysnomia.localdomain \
--to=gentoo.catalyst@xxoo.ws \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox