search for: bootnet

...uilds but want to take the voodo out of the process so I can control and understand the whole system. I am new to PXE technology and so consider me ignorant. The current server is a MS RIS server and I am attempting to migrate our facility to use Linux / PXE instead. First stage: take existing DOS bootnet floppy and convert to boot from network via PXE. This will retain the current DOS menu structure for the users to choose the ghost image. What I have done is read the user group mail list archives for the last year. Learning a much but as usual, lots of information in little tidbits. Here is what I...

Real quick background on what I'm doing now, and what I'm trying to do: We are using PXELinux with VA's SystemImager software to image new servers over our network. It's been working beautifully since the fall of 2000 using a 2.2 kernel. (Long and short: we bootstrap with PXE, use the initrd as the root file system, partition, mount and rsync the new drive, reconfigure, lilo

We are attempting to setup an automated system to build some Linux systems. We have utilised the PXELINUX bootloader after encountering the PXE 512Kb limit with bootp. We now have another issue which you may have already run into. In the DHCP configuration we specify pxelinux.0 as the bootfile, this works reasonable well, we call the Redhat vmlinuz and initrd.img files within the

I use 3Com's PXE server to deploy the RedHat Linux network boot disk for an ftp install. I have done this for RedHat 7.2 and 7.3. I followed the same procedure I used for the other RedHat boot disks using the RedHat 8.0 boot disk and syslinux didn't work. Syslinux boots the system, gets the boot: prompt and dies. The error message is can not find ramdisk image and then cannot find