Preboot Execution Environment: differenze tra le versioni

Contenuto cancellato Contenuto aggiunto
Hce (discussione | contributi)
inserisco testo da tradurre commentato, si prega di respirare prima di ricancellare da capo. anzi, se gentilmente vuoi ripristinare la prima sezione che avevo già tradotto quando è stata cancellata...
Hce (discussione | contributi)
+ trad
Riga 11:
 
Inoltre, utilizza concetti come GUID/UUID e Universal Network Device Interface ed estende il firmware del client PXE (il computer che viene avviato via PXE con un ulteriori API.
 
== Funzionamento ==
Il firmware cerca un PXE redirection service, ovvero un server DHCP che fornisca i parametri necessari per conoscere i server PXE disponibili e il nome del [[#Network_Bootstrap_Program|network bootstrap program]] (NBP) da scaricare. Se ne trova uno, il firmware lo scaricherà via TFTP da uno dei boot server, memorizzandolo nella propria [[Random Access Memory|RAM]], ne verificherà la correttezza e lo eseguirà.
 
<!--
The '''Preboot Execution Environment''' ('''PXE''', aka Pre-Execution Environment, or 'pixie') is an environment to [[booting|boot]] [[computer]]s using a [[network interface card]] independently of available [[data storage device]]s (like [[hard disk]]s) or installed [[operating system]]s.
 
{{for|a high-level overview of network booting|Network booting}}
 
PXE was introduced as part of the [[Wired for Management]] framework by [[Intel]] and is described in the [http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf specification (v2.1)] published by Intel and [http://www.systemsoft.com/ Systemsoft] on [[September 20]],[[1999]]. It makes use of several [[network protocol]]s like [[Internet Protocol|IP]], [[User Datagram Protocol|UDP]], [[Dynamic Host Configuration Protocol|DHCP]] and [[Trivial File Transfer Protocol|TFTP]] and of concepts like [[Globally Unique Identifier|GUID]]/[[Universally Unique Identifier|UUID]] and [[Universal Network Device Interface]] and extends the [[firmware]] of the PXE [[Client (Computing)|client]] (the computer to be bootstrapped via PXE) with a set of predefined [[Application Programming Interface|APIs]].
 
== Chain ==
The firmware tries to locate a PXE redirection service (Proxy DHCP) in order to receive information about available PXE boot servers. After parsing the answer, the firmware will ask an appropriate boot server for the [[Path (computing)|file path]] of a [[#Network_Bootstrap_Program|network bootstrap program]] (NBP), download it into the computer's [[Random Access Memory|RAM]] using TFTP, possibly verify, and finally execute it. If only one NBP is used among all PXE Clients, it could be downloaded using [[BOOTP]] without any need of a proxy DHCP or boot server.
 
== Availability ==
Riga 98 ⟶ 93:
[[ru:PXE]]
[[sv:Preboot Execution Environment]]
 
The '''Preboot Execution Environment''' ('''PXE''', aka Pre-Execution Environment, or 'pixie') is an environment to [[booting|boot]] [[computer]]s using a [[network interface card]] independently of available [[data storage device]]s (like [[hard disk]]s) or installed [[operating system]]s.
 
{{for|a high-level overview of network booting|Network booting}}
 
PXE was introduced as part of the [[Wired for Management]] framework by [[Intel]] and is described in the [http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf specification (v2.1)] published by Intel and [http://www.systemsoft.com/ Systemsoft] on [[September 20]],[[1999]]. It makes use of several [[network protocol]]s like [[Internet Protocol|IP]], [[User Datagram Protocol|UDP]], [[Dynamic Host Configuration Protocol|DHCP]] and [[Trivial File Transfer Protocol|TFTP]] and of concepts like [[Globally Unique Identifier|GUID]]/[[Universally Unique Identifier|UUID]] and [[Universal Network Device Interface]] and extends the [[firmware]] of the PXE [[Client (Computing)|client]] (the computer to be bootstrapped via PXE) with a set of predefined [[Application Programming Interface|APIs]].
 
-->