EON ZFS Storage 0.59.4 based on snv_124 released!

Embedded Operating system/Networking (EON), RAM based live ZFS NAS appliance is released on Genunix! Many thanks to Genunix.org for download hosting and serving the opensolaris community.

EON ZFS storage is available in 32 and 64-bit, CIFS and Samba versions:
EON 64-bit x86 CIFS ISO image version 0.59.4 based on snv_124

• eon-0.594-124-64-cifs.iso
• MD5: 4bda930d1abc08666bf2f576b5dd006c
• Size: ~89Mb
• Released: Monday 19-October-2009

EON 64-bit x86 Samba ISO image version 0.59.4 based on snv_124

• eon-0.594-124-64-smb.iso
• MD5: 80af8b288194377f13706572f7b174b3
• Size: ~102Mb
• Released: Monday 19-October-2009

EON 32-bit x86 CIFS ISO image version 0.59.4 based on snv_124

• eon-0.594-124-32-cifs.iso
• MD5: dcc6f8cb35719950a6d4320aa5925d22
• Size: ~56Mb
• Released: Monday 19-October-2009

EON 32-bit x86 Samba ISO image version 0.59.4 based on snv_124

• eon-0.594-124-32-smb.iso
• MD5: 3d6debd4595c1beb7ebbb68ca30b7391
• Size: ~69Mb
• Released: Monday 19-October-2009

New/Changes/Fixes:
- initialization of ntpd, nscd at boot time, moved to /mnt/eon0/.exec
- added /mnt/eon0/.disable for K99local stop for a cleaner shutdown
- added /mnt/eon0/.purge to allow removing drivers and binaries not needed by your image
- new version of install.sh. Fixes a bug for virtual disks, multiple runs and improved error checking of stages
- new transporter.sh CLI to automate upgrades, backups or downgrades to backed-up versions
- eon rebooting at grub(since snv_122) in ESXi, Fusion and various versions of VMware workstation. This is related to bug 6820576. Workaround, at grub press e and add on the end of the kernel line "-B disable-pcieb=true"

A new and simpler way to upgrade EON ZFS storage

There is a new and simple way to upgrade your current EON ZFS storage to the newest version. I've added a tool, transporter.sh which allows you to backup, upgrade or restore(NOTE: restore only works if you have a backed-up version) your EON ZFS storage version. Here is a usage output:

transporter.sh 
usage: transporter.sh -i /path/eon.iso -b /path/backup -d /mnt/eon0
transporter.sh -i /tmp/eon-0.593-122-64-smb.iso -d /mnt/eon0
transporter.sh -i /tmp/eon-0.593-122-64-smb.iso -b /pool/backup -d /mnt/eon0
transporter.sh -r /pool/backup/0.59.3 -d /mnt/eon0

-i path to the source ISO
-b path to the backup destination [optional]
-d path to the upgrade destination
-r path to the restore source [optional]

Here's an example run without backup options. It is always wise to have a backup. I cannot stress this enough. There is no backup in this example because I have a previous backup in /abyss/eonback/0.593.

transporter.sh -i /tmp/eon.iso -d /mnt/eon0
OK: lofiadm -a /tmp/eon.iso /dev/lofi/1
OK: mount -F hsfs /dev/lofi/1 /tmp/upgrade
removing /mnt/eon0/boot
copying /tmp/upgrade -> /mnt/eon0
x ., 0 bytes, 0 tape blocks
x ./boot, 0 bytes, 0 tape blocks
x ./boot/amd64, 0 bytes, 0 tape blocks
x ./boot/grub, 0 bytes, 0 tape blocks
x ./boot/grub/bin, 0 bytes, 0 tape blocks
x ./boot/grub/bin/grub, 180380 bytes, 353 tape blocks
[...]   excerpt clipped
./boot/platform/i86xpv/kernel/amd64, 0 bytes, 0 tape blocks
x ./boot/platform/i86xpv/kernel/amd64/unix, 2084984 bytes, 4073 tape blocks
x ./boot/platform/i86xpv/kernel/unix, 1544152 bytes, 3016 tape blocks
x ./boot/x86.eon, 49523134 bytes, 96725 tape blocks
x ./.backup, 1454 bytes, 3 tape blocks
x ./.catalog, 2048 bytes, 4 tape blocks
x ./.disable, 137 bytes, 1 tape blocks
x ./.exec, 1383 bytes, 3 tape blocks
x ./.remove, 3264 bytes, 7 tape blocks
unmounting /dev/lofi/1
OK: umount /dev/lofi/1
releasing /dev/lofi/1
OK: lofiadm -d /dev/lofi/1

Please report any inconsistent findings.