similar to: Booting initrd with PXELinux

Hi, I am trying to load kernel 2.6.6 on a Soekris net4521 from the network using PXE. I built my initrd with mkinitrd. RedHat nash (while running linuxrc) hangs after mounting /proc and says "Creating block devices". I am using the pxelinux.0 from the syslinux-2.10 distribution and the kernel and initrd were built on redhat 9.0. I built my kernel with BLK_DEV_RAM, RAMFS, TMPFS,

Hello, I have been trying to use the "configfile" option in the DHCP response to specify a specific config file when booting. When I specify this in my /etc/dhcpd.conf file the kernel and initrd are transferred, but the kernel does not boot. I am using v2.04 of pxelinux. I would appreciate any help anyone might be able to give. If I remove the "configfile" dhcp option and

I've got a Fedora 13 box that I am using as a pxe server to pxe load client machines. Using dhcp, tftp, and http I have been able to succesfully pxe load clients. However I am now trying to serve up multiple images via a menu, and not having any luck in configuring my pxelinux.cfg/default file to direct clients to the appropriate source repositories. I do have the pxelinux.cfg/default file

folks, Im finding that using a config like this: SERIAL 0 19200 #IPAPPEND 2 PROMPT 1 TIMEOUT 100 IMPLICIT 0 APPEND console=ttyS0,19200n81 root=/dev/nfs nfsaddrs=10.10.10.100:10.10.10.2:10.10.10.2:255.255.255.0:soekris:eth0 nfsroot=10.10.10.2:/nfshost/truck panic=15 LABEL deb268 KERNEL vmlinuz-2.6.8-1-386 initrd=initrd.img-2.6.8-1-386 panic=10 LABEL deb268-ram KERNEL vmlinuz-2.6.8-1-386

Hello all Now I may be way of whack here, so please forgive me. I''m trying to merge xen with redhat''s config-netboot. The idea being a kinda stateless domU. For those that haven''t seen you share a rootfs and then bind mount all the individual files over then top, and the redhat gui builds all the pxeboot config and stuff for you if you want a diskless client. I

Howdy, Running a round of updates from 6.3 to 6.4 and I'm seeing the following on all the servers. Want to make sure I'm not going to end up with a kernel panic if I reboot into the new kernel or have any other issues. Apr 22 11:10:21 www kdump: kexec: unloaded kdump kernel Apr 22 11:10:21 www kdump: stopped Apr 22 11:10:21 www kdump: mkdumprd: failed to make kdump initrd Apr 22

Hi This is a PXELinux problem that I'm facing. The problem, in brief, is that I have a set of diskless nodes (AMD Athlon XP 1800+ with 256MB RAM) connected via an internal 172.20.0.0/24 network to a dual AMD Opteron running SuSE Linux 8.3 for AMD64. I want the remote machines to diskless boot off the main server and run independently. The diskless machines have a PXE-compliant BIOS for

On Tue, Aug 02, 2016 at 03:29:07PM +0000, Olivier BONHOMME wrote: > On Tue, Aug 02, 2016 at 02:56:26PM +0000, Olivier BONHOMME wrote: > So the question is: Is that behaviour can be considered as an lftp bug or not ? Hello again, Just answering to myself and the list for a conclusion. lftp in CentOS uses the default priority provided by gnutls and it's not possible to override it in

Looking at the FAQ for SysLinux there is an option for an initrd file (initrd=filename), this does not seem to work with pxelinux (or it is just that I am doing something wrong...). here is my config file: prompt 1 #serial 0 115200 label linux kernel vmlinuz-2.4.18-ssi #read-write #root=/dev/ram0 append init=/linuxrc console=tty0 console=ttyS0,115200 initrd initrd-2.4.18-ssi.img label local

I have an interesting situation where I am loading gpxelinux.0 v3.72 from pxelinux.0 ( older ). I have a stanza that I use after loading gpxelinux such as : --- label pxelinux.new kernel pxelinux.new.0 label recovery.http kernel http://kickstart/pxelinux.new/vmlinuz-ramdisk append initrd=http://kickstart/pxelinux.new/ramdisk.img.gz ramdisk_size=358400 ramdisk_blocksize=1024

On 08/02/2016 06:11 AM, Olivier BONHOMME wrote: > Hello everybody, > > I am writing on that mailing list because I have an issue using lftp and I would > love to have more infos about features available on the LFTP version provided by > CentOS 6. > > I try to connect to a ftp server in secured mode using FTPS explicit and I would > love to use TLSv1.2. > > After

The following patch sets the default root device to be the null device. This is the behavior Linux is launched with no root device specified in the command line and without a device provided by the boot loader. Previously, the default root device was set to be /dev/ram0. This broke initrd support. This change was made in 2.6 to because of a bug reported on September 14th with dynamic ipconfig.

Hello again! I have this piece od code: ##################### #lftp will make the backup lftp -u user,password -e "mirror --reverse --delete --only-newer --verbose /var/bkp /test_bkp" somehost.com >> $LOGFILE # end log file date >> $LOGFILE echo "Backup Completo!" >> $LOGFILE ##################### Everything is fine, but the bash scrip dosn't complete

As you might know, LFTP is a popular FTP/SFTP command-line client for most systems. One feature that is lacking from this tool is the ability to do a globbed ls via sftp. I have a patch ready for LFTP that incorporates some of the knowledge [like oddball systems glob() handling] and some of the code from sftp-glob.c for this tool to add this capability. I do, however, have some questions about

CentOS Errata and Bugfix Advisory 2014:0156 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0156.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0fa29e430e78f3df7739ae7534a61e7534da5f0f1f1435909fe9c3fed39c02c2 lftp-4.0.9-1.el6_5.1.i686.rpm 14afd576b489a45446911c0672f733b0ba03435a22d4362849915d173e5226bb

CentOS Errata and Bugfix Advisory 2015:0793 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0793.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b0bd2688031fc57327e6f421c9fbd6c8cd5a8bc0f9b323cb3aae8852f209e4e5 lftp-4.0.9-6.el6.i686.rpm f3b6f43c1938941dd274558d5f329837530929933aac7fd412b24a7c12b7ce01

CentOS Errata and Bugfix Advisory 2016:1405 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1405.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d8041c3a9f61587a42ff479156751198a57d1fdc970f5a019b43a39a7b61902e lftp-4.0.9-6.el6_8.2.i686.rpm f668cb9d616b16b3dd352664110d4df2792075db082f602ce556cfae9ebed7fc

CentOS Errata and Bugfix Advisory 2016:2003 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-2003.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f4f7155f12afa2cdcb6e0b260f4295fded485aadd1771ff650efaf9992613f11 lftp-4.0.9-6.el6_8.3.i686.rpm bcb5757539fd2b5f39a191ef9121e9fdc8d13bc5145f30bb1c53cb55b1160fa6

CentOS Errata and Bugfix Advisory 2017:0040 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-0040.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: bf0451919bffe8f45288ff806cda98dc5a0ecb96ce3509518751a3e71d28299e lftp-4.0.9-6.el6_8.4.i686.rpm db635751773fbe039b1d77d1e7b0b23ab10cceb51882bda64b941bc33bedb757

hi: i try to make some images for pxelinux+memdisk. the version i try is 2.0.6 and 2.0.7pre5 for 2.88M floppy image, first i make a 1.44M boot floopy, then use "winimage" to load the disk and transfer it to 2.88M format, then save the image. it seems a easy way to make a 2.88M boot image. for harddisk image, i use vmware to build a virtual machine with 20M harddisk, make it boot