From: Alexander Stein <alexander.stein@systec-electronic.com>
To: ptxdist@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: Re: [ptxdist] Creating hardlinks withing ptxdist?
Date: Thu, 19 Apr 2012 15:16:03 +0200 [thread overview]
Message-ID: <1493316.pihEpPUWPN@ws-stein> (raw)
In-Reply-To: <20120418144406.GF17656@pengutronix.de>
Am Mittwoch, 18. April 2012, 16:44:06 schrieb Michael Olbrich:
> Hi,
>
> On Wed, Apr 18, 2012 at 02:08:10PM +0200, Alexander Stein wrote:
> > is it possible to create hardlinks within ptxdist? Our current problem is
> > that the kernel image is located in /boot/bzImage, as usually. But we
> > need the also the file under /efi/boot/bootia32.efi to be bootable from
> > EFI. A symlink doesn't work from EFI side and I don't want to maintain 2
> > binaries in parallel, despite the space wasting. So I got the idea of
> > using a hardlink. Seems to work, manually created.
>
> You could try a postinst script. But I'm not sure if the tools that create
> the images can handle hardlinks.
> Or only install /efi/boot/bootia32.efi and not /boot/bzImage, or do you
> need that as well?
Well, I don't need /boot/bzImage necessarily, I think. But the kernel image
would be in the default place and so I could still boot from this image with a
non-EFI bootloader.
Best regards
Alexander
--
Dipl.-Inf. Alexander Stein
SYS TEC electronic GmbH
August-Bebel-Str. 29
D-07973 Greiz
Tel: +49-3661-6279-0, Fax: +49-3661-6279-99
eMail: Alexander.Stein@systec-electronic.com
Internet: http://www.systec-electronic.com
Managing Director: Dipl.-Phys. Siegmar Schmidt
Commercial registry: Amtsgericht Jena, HRB 205563
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-04-19 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 12:08 Alexander Stein
2012-04-18 14:44 ` Michael Olbrich
2012-04-19 13:16 ` Alexander Stein [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=1493316.pihEpPUWPN@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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