Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fetching bootloader from network location



 > On Mon, Apr 7, 2008 at 11:46 AM, <[hidden email]> wrote: 
> > Then using DHCP you create a record that points to a boot server and 
> > directory running TFTP (Trivial File Transfer Protocol) 
> > 
> > The boot loader uses DHCP to configure the network cared (You can assign 
> > specific IP addresses in the DHCP server by MAC address) 
> > 

I have no access to the DHCP server. I cannot create a record that 
points to a boot server. Effectively, the only thing that the DHCP 
server does is hand out IPs. 

It seems that using gPXE here to fetch an image from the tftp server 
makes the most sense, because it seems that I can more easily point it 
directly to the tftp server. Also, the image that is fetched from the 
server is going to be a menu-driven bootloader through which the user 
can select the desired kernel, boot options, etc. So the final goal is 
to have a disc from which the user can boot and then see a menu of 
options which allow the user to boot using images from the remote 
server. 

-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and is 
believed to be clean. 

_______________________________________________ 
Discuss mailing list 
[hidden email] 
http://lists.blu.org/mailman/listinfo/discuss
 


BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org