* [Buildroot] syslinux on target
@ 2014-10-08 11:32 Zoltan Gyarmati
2014-10-08 17:09 ` Yann E. MORIN
0 siblings, 1 reply; 3+ messages in thread
From: Zoltan Gyarmati @ 2014-10-08 11:32 UTC (permalink / raw
To: buildroot
Dear All,
is there any supported way to install syslinux (the utility which
installs syslinux on a partition) on the target? If not (i couldn't find
it), is there any specific reason to not support this in Buildroot?
Thanks in advance,
regards
zgyarmati
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] syslinux on target
2014-10-08 11:32 [Buildroot] syslinux on target Zoltan Gyarmati
@ 2014-10-08 17:09 ` Yann E. MORIN
2014-10-08 19:44 ` Zoltan Gyarmati
0 siblings, 1 reply; 3+ messages in thread
From: Yann E. MORIN @ 2014-10-08 17:09 UTC (permalink / raw
To: buildroot
Zoltan, All,
On 2014-10-08 13:32 +0200, Zoltan Gyarmati spake thusly:
> is there any supported way to install syslinux (the utility which installs
> syslinux on a partition) on the target? If not (i couldn't find it), is
> there any specific reason to not support this in Buildroot?
Currently, we do not install 'syslinux' (the command) on the target.
Neither do we install 'extlinux' or 'isolinux' (the commands).
syslinux (the package) is very special. It does not cross-compile nicely
in my experience. So, we build it as a native package, using the native
host toolchain.
Also, we fully install syslinux in the host/ directory, even though it
contains blobs (e.g. the .c32 modules) for the target. That's the
traditional way syslinux exxpects to fins it files.
Finally, even if we were to install the 'syslinux' (or 'extlinux' or
'isolinux') programs in the target, we'd also need to install a few
other files, such as:
- the mbr blobs: for BIOS- or GPT- or CD-based boots, 'alt' versions,
the '_c' and '_f' versions (wtf are those?),
- all of the .c32 modules (even though only a sbuset is really used to
actually boot the target,
- and a lot of other stuff.
Also, the reason is that Buildroot mostly targets simple devices, and we
did not so far see a valid reason for having the syslinux tools on the
target.
So, what is the use-case to have those tools on the target?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] syslinux on target
2014-10-08 17:09 ` Yann E. MORIN
@ 2014-10-08 19:44 ` Zoltan Gyarmati
0 siblings, 0 replies; 3+ messages in thread
From: Zoltan Gyarmati @ 2014-10-08 19:44 UTC (permalink / raw
To: buildroot
On 10/08/2014 07:09 PM, Yann E. MORIN wrote:
> Zoltan, All,
>
> On 2014-10-08 13:32 +0200, Zoltan Gyarmati spake thusly:
>> is there any supported way to install syslinux (the utility which installs
>> syslinux on a partition) on the target? If not (i couldn't find it), is
>> there any specific reason to not support this in Buildroot?
> Currently, we do not install 'syslinux' (the command) on the target.
> Neither do we install 'extlinux' or 'isolinux' (the commands).
>
> syslinux (the package) is very special. It does not cross-compile nicely
> in my experience. So, we build it as a native package, using the native
> host toolchain.
>
> Also, we fully install syslinux in the host/ directory, even though it
> contains blobs (e.g. the .c32 modules) for the target. That's the
> traditional way syslinux exxpects to fins it files.
>
> Finally, even if we were to install the 'syslinux' (or 'extlinux' or
> 'isolinux') programs in the target, we'd also need to install a few
> other files, such as:
>
> - the mbr blobs: for BIOS- or GPT- or CD-based boots, 'alt' versions,
> the '_c' and '_f' versions (wtf are those?),
>
> - all of the .c32 modules (even though only a sbuset is really used to
> actually boot the target,
>
> - and a lot of other stuff.
>
> Also, the reason is that Buildroot mostly targets simple devices, and we
> did not so far see a valid reason for having the syslinux tools on the
> target.
>
> So, what is the use-case to have those tools on the target?
>
> Regards,
> Yann E. MORIN.
>
Dear Yann,
yes, by looking into it i also came to the conclusion that it probably
doesn't worth the effort.
My use case is that i have to distribute my Buildroot built appliance to
the targets on the field (target is an x86 box), and instead of getting
out the disks from each of them and dump the needed content from a
laptop, i decided to make a "live" Buildroot system running from usb
stick which contains the rootfs.tar.gz, the kernel image, the config
data and a script which creates the needed partitions and copies the
content to the target disk. For this script it would have been handy to
have syslinux (utility) available on the system, but of course there are
several other ways to get the bootloader installed on the target disk,
so i just chose an other one, just wondered when saw that it's not
available.
Thanks, regards
zgyarmati
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-10-08 19:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-08 11:32 [Buildroot] syslinux on target Zoltan Gyarmati
2014-10-08 17:09 ` Yann E. MORIN
2014-10-08 19:44 ` Zoltan Gyarmati
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.