Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Inside Security (insert)
2017-11-07, 19:57 (This post was last modified: 2017-11-08 00:42 by draugadrottinn.)
Post: #3
RE: Inside Security (insert)
Ha! I "kinda" figured it out...

So, I'm using iPXE to chainload PXE to boot knoppix. Here's what I have:

imbedded.ipxe above - as it's part of ipxelinux.0 when I create it; but does not effect the way Knoppix is being loaded so it's not necessary.

menu.ipxe is as follows:
***************************************************************
echo Booting Knoppix 7.2
set use-cached 1
dhcp
set 209:string http://###.###.###.4/knoppix-tftpboot/px...noppixboot
set 210:string tftp://###.###.###.4/knoppix-tftpboot/
chain ${210:string}knoppix.0
goto start
***************************************************************
http://###.###.###.4/knoppix-tftpboot/px...noppixboot (again, APPEND is one line):
***************************************************************
TIMEOUT 1
DEFAULT http://###.###.###.4/knoppix-tftpboot/linux
APPEND nfsdir=###.###.###.4:/var/lib/tftpboot/knoppix-tftpboot/cdrom nodhcp lang= ramdisk_size=100000 init=/etc/init apm=power-off nomce loglevel=1 2 initrd=http://###.###.###.4/knoppix-tftpboot/miniroot.gz libata.force=noncq tz=localtime lang=en apm=power-off nomce libata.force=noncq hpsa.hpsa_allow_any=1 loglevel=1 noswap nofstab nopcmcia nofirewire BOOT_IMAGE=knoppix
***************************************************************

Hopefully this will help with anyone else having this issue. I still could not figure out how to do it with only iPXE, but this is a close second that will work.

Good luck everyone.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Inside Security (insert) - draugadrottinn - 2017-11-07 19:57
RE: Inside Security (insert) - NiKiZe - 2017-11-08, 00:15



User(s) browsing this thread: 2 Guest(s)