The translation is temporarily closed for contributions due to maintenance, please come back later.
Context English Portuguese (Brazil) State
<personname> <firstname>Sergey</firstname> <surname>Lyubka</surname> </personname> <contrib>Contributed by </contrib> <personname><firstname>Sergey</firstname><surname> Lyubka</surname></personname><contrib> Contribuíram por </contrib>
<primary>BIOS</primary> <primary>BIOS</primary>
<primary>firmware</primary> <primary>firmware</primary>
<primary>IA-32</primary> <primary>IA-32</primary>
<primary>booting</primary> <primary>inicialização</primary>
<primary>system initialization</primary> <primary>inicialização do sistema</primary>
<literal>boot0</literal> <literal>boot0</literal>
<filename>loader</filename> <filename>carregador</filename>
<primary>MBR</primary> <primary>MBR</primary>
<filename>sys/boot/i386/boot0/Makefile</filename> <filename>sys/boot/i386/boot0/Makefile</filename>
<filename>sys/boot/i386/boot0/boot0.S</filename> <filename>sys/boot/i386/boot0/boot0.S</filename>
<filename>sys/boot/i386/boot2/Makefile</filename> <filename>sys/boot/i386/boot2/Makefile</filename>
<filename>boot0</filename> relocates itself to <literal>0x600</literal>, the address it was linked to execute, and jumps over there. It then reads the first sector of the FreeBSD slice (which consists of <filename>boot1</filename>) into address <literal>0x7c00</literal> and jumps over there. <filename> boot0 </filename> se muda para <literal> 0x600 </literal> , o endere�o que estava ligado para executar e salta para l�. Ele ent�o l� o primeiro setor da fatia do FreeBSD (que consiste em <filename> boot1 </filename> ) no endere�o <literal> 0x7c00 </literal> e pula ali
<filename>boot1</filename> loads the first 16 sectors of the FreeBSD slice into address <literal>0x8c00</literal>. This 16 sectors, or 8192 bytes, is the whole file <filename>boot</filename>. The file is a concatenation of <filename>boot1</filename> and <filename>boot2</filename>. <filename>boot2</filename>, in turn, contains the <acronym>BTX</acronym> server and the <filename>boot2</filename> client. Finally, a jump is made to address <literal>0x9010</literal>, the entry point of the <acronym>BTX</acronym> server. <filename> boot1 </filename> carrega os primeiros 16 setores da fatia do FreeBSD no endere�o <literal> 0x8c00 </literal> . Este 16 setores, ou 8192 bytes, � o arquivo inteiro <filename> bota </filename> . O arquivo � uma concatena��o de <filename> boot1 </filename> e <filename> boot2 </filename> . <filename> boot2 </filename> , por sua vez, cont�m o servidor <acronym>BTX</acronym> eo <filename> boot2 </filename> cliente. Finalmente, um salto � feito para abordar <literal> 0x9010 </literal> , o ponto de entrada do servidor <acronym>BTX</acronym> .
<filename>sys/boot/i386/boot2/boot2.h</filename> <filename> sys / boot / i386 / boot2 / boot2.h </filename>
<primary>virtual v86 mode</primary> <primary> modo virtual v86 </primary>
<literal>boot2</literal> defines an important structure, <literal>struct bootinfo</literal>. This structure is initialized by <literal>boot2</literal> and passed to the loader, and then further to the kernel. Some nodes of this structures are set by <literal>boot2</literal>, the rest by the loader. This structure, among other information, contains the kernel filename, <acronym>BIOS</acronym> harddisk geometry, <acronym>BIOS</acronym> drive number for boot device, physical memory available, <literal>envp</literal> pointer etc. The definition for it is: <literal> boot2 </literal> define uma estrutura importante, <literal> struct bootinfo </literal> . Essa estrutura � inicializada por <literal> boot2 </literal> e passou para o carregador e depois para o kernel. Alguns n�s desta estrutura s�o definidos por <literal> boot2 </literal> , o resto pelo carregador. Esta estrutura, entre outras informa��es, cont�m o nome do arquivo do kernel, <acronym>BIOS</acronym> geometria disco r�gido, n�mero da unidade <acronym>BIOS</acronym> para dispositivo de inicializa��o, mem�ria f�sica dispon�vel, <literal> envp </literal> ponteiro etc. A defini��o para isso �:
<literal>boot2</literal> enters into an infinite loop waiting for user input, then calls <function>load()</function>. If the user does not press anything, the loop breaks by a timeout, so <function>load()</function> will load the default file (<filename>/boot/loader</filename>). Functions <function>ino_t lookup(char *filename)</function> and <function>int xfsread(ino_t inode, void *buf, size_t nbyte)</function> are used to read the content of a file into memory. <filename>/boot/loader</filename> is an <acronym>ELF</acronym> binary, but where the <acronym>ELF</acronym> header is prepended with <filename>a.out</filename>'s <literal>struct exec</literal> structure. <function>load()</function> scans the loader's ELF header, loading the content of <filename>/boot/loader</filename> into memory, and passing the execution to the loader's entry: <literal> boot2 </literal> entra em um loop infinito esperando por entrada do usu�rio, ent�o chama <function> carga() </function> . Se o usu�rio n�o pressionar nada, o loop ser� interrompido por um tempo limite, <function> carga() </function> ir� carregar o arquivo padr�o ( <filename> / boot / loader </filename> ). Fun��es <function> pesquisa ino_t (char * filename) </function> e <function> int xfsread (inodo_t inode, void * buf, tamanho_t nbyte) </function> s�o usados ​​para ler o conte�do de um arquivo na mem�ria. <filename> / boot / loader </filename> � um bin�rio <acronym>ELF</acronym> , mas onde o cabe�alho <acronym>ELF</acronym> � prefixado com <filename> a.out </filename> ';s <literal> struct exec </literal> estrutura. <function> carga() </function> varre o cabe�alho ELF do carregador, carregando o conte�do do <filename> / boot / loader </filename> na mem�ria e passando a execu��o para a entrada do carregador:
<application>loader</application> is a <acronym>BTX</acronym> client as well. I will not describe it here in detail, there is a comprehensive man page written by Mike Smith, <citerefentry><refentrytitle>loader</refentrytitle><manvolnum>8</manvolnum></citerefentry>. The underlying mechanisms and <acronym>BTX</acronym> were discussed above. <application> carregador </application> � um cliente <acronym>BTX</acronym> tamb�m. Eu n�o vou descrev�-lo aqui em detalhes, h� uma manpage abrangente escrito por Mike Smith, <citerefentry><refentrytitle> carregador </refentrytitle><manvolnum> 8 </manvolnum></citerefentry> . Os mecanismos subjacentes e <acronym>BTX</acronym> foram discutidos acima "
<function>init386()</function> <function> init386 () </function>