Announcing PING Updates / Stable releases

[mrralan]

Just before the first prompt appears. Also, the kernal is the same date and size as the .14 kernal.

[Alberto Maria]

Oh yes, I see...

[mwall]

Natan,

Do you no longer send out the email for new PING releases? I found it much easier that way

Or maybe my spam filter is blocking it...

Mike

[Natan]

Hi Mike,
I still do, but that time, time has lacked, and there was no big evolution... you see...

Regards
Natan

[jhurd8025]

Hey Natan, thanks for the updates.

I've tested the new
- 20080901.initrd.gz
- 20080901.kernel

I did this manualy and not through kernel paramaters or ping.conf, but all tests passed perfectly.

NFS: Success
Dirty Mount: Success

I've only tested this using a Virtual Machine thus far. I will test both doing automatic through kernel parameters and on other hardware types in a bit. Ill post back with results.

[jhurd8025]

Exciting.. Will try this in a little bit!

[kazgor]

i like the sound of the sda1.zip idea.

i use ping for training laptops.. so after the courses are finished i can restore the laptop to a predefined image.. but obviously i would have to recreate the image if i added any extra files or notes.. so this would such a useful time saver

[Natan]

Isn't the forum the perfect place where to get good ideas ?

[jhurd8025]

Just tested this doing the prompts... Will test using the kernel switch you suggested soon.

Does this work for cciss/c0d0 devices as well?

Also does it require the image files to be named with hda?

or can I just name it image.001 image.002 and it will still work?

[Natan]

Ola !

Just tested this doing the prompts... Will test using the kernel switch you suggested soon.

Does this work for cciss/c0d0 devices as well?

Hopefully.

Also does it require the image files to be named with hda?

or can I just name it image.001 image.002 and it will still work?

Good point, the image files have got to be called hda* or sda* or whatever they have been called at image creation time. The idea is, PING will try to restore hda* files to /dev/hda, and if it doesn't find such a dev, will propose all the devices that have been detected. If you decide once that hda will target sda, then hda1* files will be restored to sda1 and hda2* to sda2 etc. with no more question. cciss/rd/ida/mapper devices should work the same way.

Natan

[kazgor]

i can't get build 16 to work compared to build 12.

basically.. booting into 12 i see

sdb1 - 500gb USB drive

sda1 - 7gb Linux (for lilo)
sda2 - 120gb windows c:\

boot using Build 16, i just see the USB drive as SDA1 and thats it.
even using FDISK -l just shows the usb drive.

looking at the x.log file its just ends at LOOKING FOR ANY ADDON IN THE CD/DVD...


Laptop is a Dell Latitute D830 - I couldn't use build 13 when that came out either

[Natan]

I think I've finally found the cause.

Can you give a try to this kernel ?

[JEdmondson]

I checked this version against my unique issues with my Dell Vostro 200's. If the IDE Controller is left in IDE mode, no errors, no hard drives detected, PING won't start. If I switch the IDE controller to RAID mode, I recieve several errors, but then PING is able to start, it appears to find the hard drive, but not the partition as the list is empty (except for restore). Would it be helpful if I post log details in my other thread of this so you can see what it's doing?

[Natan]

Yes, sure. And dmesg log as well.

[kazgor]

thanks Nathan, it will be Monday now when i get to try out the new version. will let you know how i get on.