From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] syslinux: add support for host-install
Date: Thu, 1 Sep 2011 18:26:46 +0200 [thread overview]
Message-ID: <201109011826.47154.arnout@mind.be> (raw)
In-Reply-To: <20110831101935.03bda653@skate>
On Wednesday 31 August 2011 10:19:35, Thomas Petazzoni wrote:
> You don't have the $(eval $(call GENTARGETS,boot,syslinux,host)) line
> anymore, so the HOST_* variables are quite useless no ? This line was
> present in your previous posting.
Oops! Messed up rebase, and I didn't think it was necessary to test...
Patch v3 coming up.
> Also can you comment how this host package is used ? It isn't part of
> the dependencies of any target package, so it doesn't seem to be used
> anywhere (except by manually running "make host-syslinux").
Indeed, manually running "make host-syslinux" in the script that creates a
USB image. I guess the host-grub support that was submitted a couple of days
ago had the same purpose.
> Not related to your patches directly, but could you elaborate a bit on
> how syslinux is used in practice by giving an example usage. This would
> explain a bit why a host version is needed, how to set up syslinux on
> the target, etc.
To build a rescue disk that rewrites the disk of the target device. The idea
is that the whole thing can be sent as a zip file and the customer just has to
unzip it to a USB stick and run syslinux (from Windows) and voila, he has a
rescue USB stick. The compiled syslinux.exe is taken from the tar file for
that. However, I also want to be able to create a rescue disk directly from
buildroot, hence I want a working host-syslinux.
FYI the make_rescue script is attached.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
-------------- next part --------------
A non-text attachment was scrubbed...
Name: make_rescue.sh
Type: application/x-shellscript
Size: 4508 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110901/69f22f82/attachment.bin>
next prev parent reply other threads:[~2011-09-01 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 6:06 [Buildroot] [PATCH v2 1/2] syslinux: bump version to 4.04 and fix build error in 4.04 Arnout Vandecappelle
2011-08-31 6:06 ` [Buildroot] [PATCH v2 2/2] syslinux: add support for host-install Arnout Vandecappelle
2011-08-31 8:19 ` Thomas Petazzoni
2011-09-01 16:26 ` Arnout Vandecappelle [this message]
2011-09-02 8:21 ` [Buildroot] [PATCH v2 2/2] syslinux: add support forhost-install Will Moore
2011-09-02 8:14 ` [Buildroot] [PATCH v3] syslinux: add support for host-install Arnout Vandecappelle
2011-09-14 8:45 ` [Buildroot] [PATCH v2 1/2] syslinux: bump version to 4.04 and fix build error in 4.04 Arnout Vandecappelle
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=201109011826.47154.arnout@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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