Contributions Thread

[Natan]

Sure. My feeling is that some vars should be usable within the APPEND line, asking PING to use what IP/GW/Netmask PXE has retrieved.

[mrralan]

Here is a basic structure for a new menu system in PING. It will be less confusing if the menus only offer 1 option and don't show items relating to other options. It's not easy to show menus in text but I will try.



PING MAIN MENU

Imaging

1) Create An Image
2) Restore An Image


Tools

3) Partition & Format
4) Blank Local Admin Password

------------------------------------



If user selects 1 goto... What partition do you want to image? (User is presented with available partitions)
User makes selection then goto... Where do you want to save the image? (User is presented with the local and/or network locations)
User makes selection and process continues.

If user selects 2 goto... What image do you want to restore? (User is presented with available images)
User makes selection then goto... What partition do want to restore to? (User is presented with available partitions to restore)
user makes selection and process continues.

If user selects 3 goto... Partition & Format menu

If user selects 4 goto... Blank Local Admin Password menu


I haven't used Partitioning or Blanking passwords so I am not sure the options but following along the guidelines of selection 1 and 2 would suffice.

[mrralan]

Any input? Anyone?

[Curtis8]

I like it. Simple and straight forward.

[jhurd8025]

I would like to say that NFS works flawless with PING

I've had much less trouble than using smb/cifs.

I think it should be an option to use nfs within the network config section.

[mrralan]

I like it. Simple and straight forward.

It doesn't appear as if anyone else sees any problems with it either.

[jhurd8025]

[Natan]

Thanks, Jon. Seems quite good... I'm going to implement it (look for a third beta 2.01.16).

Natan

[jhurd8025]

Hey Natan....


let me know if you decide to include this...


If its too much hassel or interupts other users, then no need. I can put it in myself.

[Natan]

Hi Jon,
No hassle ; but I didn't understand the purpose.

Natan

[Curtis8]

From what I understand, IPAPPEND will take the PXE IP info and give it to PING so it does not need to do dhcp to get a new address.

[Natan]

That's the point I don't get ! If a DHCP server worked to give the PXE client an address, why wouldn't it work for the shell too ?

Well, unless you have 2 NICs and you want to be absolutely sure the PING script will connect the even NIC that got a PXE launching, and not the second one.

Natan

[jhurd8025]

Again this probably isnt needed for anyone else, so you can leave it out...

Our envrioment is 99% static ip's. For SOX reasons we only allows DHCP requests to clients identifing themselves with Host Identifier 'PXECLIENT'. So only upon the pxe request will it get a DHCP ip, anything else would not get a dhcp ip. That includes any windows, linux, or unknown server requesting an ip. With the append, I can pass the IP information automaticaly to the kernel if the kernel can accept the parameters.

[Natan]

Understood.

I suggest you add the IPAPPEND parameter to your pxelinux file, and use the Cmd_1 parameter to connect to the network using the collected IP.

This should have 2 advantages :
- solving your problem
- without forcing you to modify the PING script at each new release.

Regards
Natan

[jhurd8025]

good idea!