Announcing PING Updates / Stable releases

[DabbelJu]

That's strange enough. Can you get the /tmp/x.log file ?

Hi
her is the part of the x.log where the hda2.zip is unpacked
I think the mkntfs command creates a new disk

2110 rc.ping 13:10:09> * Restore [/dev/?? from hda2.zip] with [/mnt/smbfs/MyComputer/hda2.zip]
2110 rc.ping 13:10:09> * [umount /mnt/dos]
2110 rc.ping 13:10:09> * [mkntfs -Q -F /dev/hda2]
2110 rc.ping 13:10:11> * [ntfsfix /dev/hda2]
2110 rc.ping 13:10:11> * [; mount /dev/hda2 /mnt/dos >/dev/null 2>&1; umount /mnt/dos >/dev/null 2>&1; mount /dev/hda2 /mnt/dos]
2110 rc.ping 13:10:11> * [cd /mnt/dos; unzip /mnt/smbfs/MyComputer/hda2.zip; sleep 2]
2110 rc.ping 13:10:13> * [cd /; umount /mnt/dos; sleep 2]
2110 rc.ping 13:10:15> * Restore [/dev/?? from hda3.000] with [/mnt/smbfs/MyComputer/hda3.000]
2110 rc.ping 13:10:15> Cmd: [umount /dev/hda3 >/dev/null 2>&1]
2110 rc.ping 13:10:15> Cmd: [sleep 2; partimage -f3 -b -c -d -o restore /dev/hda3 "/mnt/smbfs/MyComputer/hda3.000"; sleep 2; reset]

[Natan]

I don't understand what happened, because I've really commented out that part of the script (which was supposed to format the partition in case it could not be mounted, so to permit deploying only a zip).

Anyway, there's a new kernel, with some bug fixes related to SATA handling, so I'm going to release 2.01.18.

[DabbelJu]

I don't understand what happened, because I've really commented out that part of the script (which was supposed to format the partition in case it could not be mounted, so to permit deploying only a zip).

Anyway, there's a new kernel, with some bug fixes related to SATA handling, so I'm going to release 2.01.18.

As Turnaround for me I created a script for CMD_2

#! /bin/sh
mount.cifs //MyShare/Partimages /mnt/smbfs -o username="MyDomain\\MyUser",password=MyPasswd
# Remove old x.log and Copyingnew x.log to MyShare
rm /mnt/smbfs/x.log
cp /tmp/x.log /mnt/smbfs/x.log
umount /mnt/dos
# Remount Device and unzip
ntfsmount /dev/hda2 /mnt/dos -o force
cd /mnt/dos
unzip -X /mnt/smbfs/MyDirectory/addon.zip

and the best it runs. What do this other than yours ?

[Natan]

It's good, but not mudulable... you know, if you've got 2 images, it will always unzip the same file, for example.

But the Cmd_2 param was designed for this kind of workarounds, really.

Natan

[DabbelJu]

Is there a reason why you use not ntfsmount in you script?

As sugestion: Place the x.log to the SHARE-folder then the users can read the x.log from Windows and we have a little documentation how the image was created.

[Natan]

ntfsmount has only one advantage over mount -t ntfs-3g, and this is the force option. Now, it's used.

I've also added a ntfsfix in case ntfsmount fails (which is not rare after a restoration).

Copying the log to the image folder is a good idea, it has been evoked a few times, but never done, in part because it obviously can't be complete, being copied before the end of the script. Would be better than nothing, though.

[Natan]

Hi there !
I'm glad to announce a small update, after some people sent me some useful feedback.

Code: Select all

* 2.01.18
  - Linux kernel upgraded from 2.6.26.3 to 2.6.26.5.
  - Little bug fixes in rc.ping (zip archives handling).

* 2.01.17 2008-09-09
  - Added S-Tar 1.5a89. Usual tar is now replaced by a symlink
    from star to tar. S-Tar has plenty of interesting features.
  - Added 7-Zip 4.58.
  - Oops, the kernel needed static Intel e1000 drivers. Back.
  - Moreover zipped archives (ex.: sda1.000.zip), several other
    formats are now accepted: .tar, .tar.gz, .tar.bz2, .tar.7z, .7z.

As always, it can be downloaded here.

Thanks to all those who have taken some time to give first shots a try!

Regards
Natan

[DabbelJu]

Hi there !
I'm glad to announce a small update, after some people sent me some useful feedback.

Hi Natan
Maybe it ist possible that you have forgotten to implement rc.ping and ping.conf in the new ISO.

This Versions are the rights
http://ping.windowsdream.com/dl/PING_2.01/rc.ping
http://ping.windowsdream.com/dl/PING_2.01/ping.conf
but they differ from the ISO

[Natan]

That's very possible ; uploading another one. Sigh.

[DabbelJu]

That's very possible ; uploading another one. Sigh.

Hi Natan
I' very confused about the Version of rc.ping. In the downloaded ISO V2.01.18 it seems to be Version 2.01.15. The download version of rc.ping told's me Version 2.01.18. Which is the actal rc.ping.

[Natan]

You made me doubt and I've downloaded it to make sure
No way, there's really rc.ping 2.01.18 inside. Maybe something to do with the cache of your proxy server if you've got one. Try to copy the link to the iso, to copy it to your URL bar, then add a ? at the end of the URL. This should force the re-download. You might also check against the MD5 checksum, wich can be downloaded too.

Regards
Natan

[Natan]

Hi there !
I'm glad to announce a small update, after some people sent me some more useful feedback.

Code: Select all

* 2.01.19 2008-09-17
  - Added dmraid to the OS. So we'll finally handle fakeraid.
  - Added fuse-zip 0.2.5 to the OS so to be able to mount
    zip archives.
  - Added hdparm 8.9 to get info on HDD devices and possibly
    adjust them so to get better speed.
  - Little bug fix: an image with a .part file but no file named
    after the device (for ex.: sda) would be ignored. A workaround
    was to create a zero-byte file called after the device -- this
    is not needed any more.
  - Little bug fix: in the case of LVM, the name of the logical
    volumes could not contain a _ character (thx, Mark G.).
  - Little bug fix: a Cmd_2 would be launched in batch mode,
    preventing interactivity.
  - Little bug fix: if you had zsplitted files in an image directory,
    PING would ask for the choice of a target device (no consequence).
  - Kernel: unset the CONFIG_IDE_GENERIC option. Might finally solve
    the performance issue reported on several SATA devices.

As always, it can be downloaded here.

Thanks to all those who have taken some time to give first shots a try!

Regards
Natan

[nickf]

Hi,

I've just downloaded 2.0.19 and as far as I can see Samba is still version 3.0.30. Can anybody confirm this?

Also mount.cifs -V (to get the version) doesn't seem work.

Really want to try and get DFS working

[Natan]

Hi !
I'm pretty sure it's a recent one. The new mount.cifs does not send back its version, but it's a sign it has changed !

Natan

[nickf]

When I run smbmount, it says v3.0.30 at the top. According to the release notes (of ping 2.01.16) it should be 3.2.3.

The ping.rc script when runs says its 2.01.19, so I am pretty sure I am using the correct initrd file.