[haiku-development] Re: Nightly ARM builds now automated
- From: Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sat, 11 Feb 2017 09:47:41 +0100
On Sat, Feb 11, 2017 at 04:18:43AM +0000, Thomas Mueller wrote:
Is the reason for using TFTP rather than NFS related to (extended) attributes?
As I said, TFTP is used to load the bootloader, then the kernel. The OS
is (of course) not yet running at this point so you need a very simple
protocol. TFTP is just that and is always used in that case. This is how
you would net boot a Linux or BSD system as well.
What about an NAS server that supports NFS and FTP but not TFTP? Is there a
backward compatibility between ftp and tftp?
Network booting is a rather "invasive" setup: usually you need to change
settings in your DHCP server and have a TFTP server running next to it.
This means you need a second machine acting as a server for all these
things (usually a Linux or BSD). That same machine can run the custom
network filesystem server as well.
I am not really familiar with u-boot, though I remember references to u-boot
on Haiku web pages.
What can be used on i386 and amd64 in place of u-boot?
The BIOS is used, and the PXE ROM of your network card if there is one.
If there isn't, you may try iPXE or gPXE.
I still have never PXE-booted but would like to set up and try.
I would recommend first doing it with a known to work system (boot a
Linux or *BSD from the network) to see what it involves. Once you have
that running, you can start experimenting with the Haiku support, with
some understanding of what is happening.
--
Adrien.
Other related posts:
