ZenFone 2 Review: Cheap, Fast, Big, Flawed

http://www.xda-developers.com/zenfone-2-review-cheap-fast-big-flawed    

Contents

o Design, Build Quality

o Performance

  1 CPU & System

  2 GPU & Gaming

o On Storage and Memory

o Display

o Audio

o Camera

o Battery Life and Charging

o A Note on System Stability

o Software UI/UX

o Rootability, Future Proofing and Other Thoughts

o Final Thoughts

Android’s ART replaced Dalvik for many reasons, some of them being that AOT trumped JIT compilation and that Dalvik’s garbage collector was inefficient. Ultimately, it aims to improve app performance and the results have been widely discussed ever since ART’s original optional implementation on KitKat. With better performance and less of a need for native and platform-dependent code, the x86 architecture can benefit as apps become more efficient and do not have as many ARM hooks that need to be translated by libhoudini or whatever method of binary translator that gets put in place. Moreover, developers can port their ARM-based NDK applications to x86 and avoid binary translation altogether for more efficient results (some documentation by Intel can be found here). We hope that ASUS does bring further ART optimizations from more recent and upcoming Android builds to strengthen the process.

Unlock bootloader

Unlock bootloader

5. Unlocking Bootloader (UNOFFICIAL METHOD)

BootLoader Unlock (both ZE551ML and ZE550ML)
http://forum.xda-developers.com/showpost.php?p=61426871&postcount=26
http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547

 
Official bootloader unlock for ZenFone 2 is now available

Unlocking your bootloader allows you to put custom software onto your device. Many developers have created custom ROMs and have had to hack their way into the ZenFone 2 to make this available to powerusers in the community.
Now, unlocking the bootloader is as easy as downloading the utility, installing it, and running it.

Proceed with caution and read below notice before attempting

From the ASUS Support site: Unlock Device App: Unlock bootloader

Utilities (1)
 Version V1.0
 Description

Unlock Device App: Unlock boot loader

Notice:

1. Update your software image to V2.20.40.139 or latest version

2. Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions; the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.

You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.

Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.

It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.

Resources (for Asus ZE551ML / ZE550ML)

Resources (for Asus ZE551ML / ZE550ML)

Asus Zenfone 2 | Resources all in one thread

1. Drivers | ADB installer
2. Recovery Related Stuff (Entering Recovery|Stock Recovery | Custom Recovery)
3. Rooting | Flashing | Applying OTA
4. Changing from CN to WW version
5. Unlocking Bootloader (UNOFFICIAL METHOD)
6. Xposed Framework Installer
7. Viper4Android Related Stuff
8. Adjusting DPI without root
9. NTFS support for OTG devices

[INDEX] Asus Zenfone 2

Click on a Link below for More Info

• Manufacturer's Device Home Page
• Basic Device Information
• Official Stock Firmware
• Device Tools, Root/Un-root/Un-brick methods
• Custom ROMs
• Kernels & Radios
• MODS, GUIDES, and Misc

Slitaz -- adb / fastboot

sh: /usr/bin/adb: No such file or directory


1.
tux@slitaz:~ $ adb --help
sh: /usr/bin/adb: No such file or directory

tux@slitaz:~ $ which adb

tux@slitaz:~ $ ls -l /usr/bin/adb
ls: /usr/bin/adb: No such file or directory


2.
tux@slitaz:~ $ tazpkg info android-platform-tools

TazPKG information
===========================================
 Package : android-platform-tools
Version : r19.0.1
Category : development
Short desc : Platform-Tools for Google Android SDK (adb and fastboot).
Maintainer : pankso@slitaz.org
License : custom
Depends : android-sdk
Web site : http://developer.android.com
Size : 820k/4.8M
===========================================



3.
tux@slitaz:~ $ tazpkg -lf android-platform-tools
Installed files by: android-platform-tools
===========================================
/opt/android-sdk/platform-tools/adb
/opt/android-sdk/platform-tools/api/api-versions.xml
/opt/android-sdk/platform-tools/fastboot
/opt/android-sdk/platform-tools/NOTICE.txt
/opt/android-sdk/platform-tools/source.properties
/opt/android-sdk/platform-tools/systrace/AUTHORS
/opt/android-sdk/platform-tools/systrace/LICENSE
/opt/android-sdk/platform-tools/systrace/NOTICE
/opt/android-sdk/platform-tools/systrace/prefix.html
/opt/android-sdk/platform-tools/systrace/script.js
/opt/android-sdk/platform-tools/systrace/style.css
/opt/android-sdk/platform-tools/systrace/suffix.html
/opt/android-sdk/platform-tools/systrace/systrace-legacy.py
/opt/android-sdk/platform-tools/systrace/systrace.py
/opt/android-sdk/platform-tools/systrace/UPSTREAM_REVISION
==========================================
 15 files installed with android-platform-tools


4.
tux@slitaz:~ $ /opt/android-sdk/platform-tools/adb version
Android Debug Bridge version 1.0.31
tux@slitaz:~ $

ASUS Zenfone2 Basic Device Information

Basic Device Information
http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748

There are many variants of the Asus Zenfone 2, and it is important to use the files for the corresponding device or you may damage your device permanently. They are:

Device -- Model -- RAM/CPU

• Z00AD -- ZE551ML -- 4GB/2.3GHz or 4GB/1.8GHz or 2GB/1.8GHz (5.5 in 1080p FHD Screen)
• Z008D -- ZE550ML -- 2GB/1.8GHz (5.5 in 720p HD Screen)
• Z00D -- ZE500CL -- 2GB/1.6GHz
• ZE500KL -- 2GB/1.2 GHz (5.0 in 720p HD Screen)*
• ZE500KG -- 2GB/1.2 GHz (5.0 in 720p HD Screen)*
• ZD551KL -- 2GB/1.7GHz (5.5 in 1080p FHD Screen)

*The Zenfone 2 Laser has it's own forum available here: http://forum.xda-developers.com/zenfone-2-laser

All of these devices share this subforum, but most of the development is targeted towards the Z00A and the Z008.

Resources (for Asus ZE500KL)

Resources (for Asus ZE500KL)
 
> Asus Official Firmware and Kernel Source
> Original boot.img
> Decompressed original boot.img (with unpackbootimg)
> Official recovery (linked by @miau9202, credits to @shakalaca )
> Original dt.img (extracted from official recovery)
> Device Tree
> Rooted boot.img


Asus Official Firmware and Kernel Source

Firmware (7)

Version WW_12.8.5.156
  Description    ASUS ZenFone 2 Laser(Z00E/Z00ED/Z00EDA/Z00EDB)software Image:
                 V12.8.5.156 for WW SKU only*

Version WW_12.8.5.118
  Description    ASUS ZenFone 2 Laser(Z00E/Z00ED/Z00EDA/Z00EDB)software Image:
                 V12.8.5.118 for WW SKU only*

Version WW_12.8.5.106
 Description     ASUS ZenFone 2 Laser(Z00E/Z00ED/Z00EDA/Z00EDB)software Image:
                 V12.8.5.106 for WW SKU only*

Source Code (5)

Version V12.8.5.156
Description   ASUS ZenFone 2 Laser (ZE500KL) Kernel Source Code for Android OS

Version V12.8.5.118
Description   ASUS ZenFone 2 Laser (ZE500KL) Kernel Source Code for Android OS

Version V12.8.5.106
Description   ASUS ZenFone 2 Laser (ZE500KL) Kernel Source Code for Android OS

 

Root for ZE500KL / Z00E

Root for ZE500KL / Z00E

Rooting (Android OS)

Rooting is the process of allowing users of smartphones, tablets and other devices running the Android mobile operating system to attain privileged control (known as root access) over various Android subsystems. As Android uses the Linux kernel, rooting an Android device gives similar access to administrative (superuser) permissions as on Linux or any other Unix-like operating system such as FreeBSD or OS X.

Root for ZE500KL and ZE500KG 

http://forum.xda-developers.com/zenfone-2-laser/general/wip-finding-to-root-ze500kl-t3223797

Compatible models:
Original posts by @miau9202: (Go and leave a thanks to him!)
>ZE500KL
>ZE500KG

Compatible System Version:
>WW_12.8.5.118 (tested)

How To:
1 - Install adb and fastboot driver (follow THIS guide)
2 - Reboot in fastboot mode with one of the following method:

a -Volume Up while booting up

b -With adb, after enabling USB debugging in developer settings, using:

Code:

 adb reboot bootloader

3 - When you are in the bootloader, run this command:

Code:

fastboot boot mod_boot.img

IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!

>Now your phone should automatically reboot with root installed and working!

Bug:
>While not everyone had it, there was a case where com.asus.services started crashing every boot after rooting, the only way to fix it was to reflash the OTA and wipe the data partition

Note:
NO ONE IN THIS FORUM, NOR THE FORUME ITSELF, IT'S RESPONSABLE OF YOUR ACTION!
THIS GUIDE COULD BRICK YOUR PHONE, FOLLOW IT AT YOUR OWN RISK!

Download:
ZE500KL: Original Post - Mirror
ZE500KG: Original Post - Mirror

Resources (for Asus ZE500KL)
> Asus Official Firmware and Kernel Source
> Original boot.img
> Decompressed original boot.img (with unpackbootimg)
> Official recovery (linked by @miau9202, credits to @shakalaca )
> Original dt.img (extracted from official recovery)
> Device Tree
> Rooted boot.img 

Zenfone 2 ZE500KL / Z00E

ZE500KL / Z00E

Platform   OS      Android OS, v5.0 (Lollipop), planned upgrade to v6.0 (Marshmallow)
           Chipset Qualcomm MSM8916 Snapdragon 410
           CPU     Quad-core 1.2 GHz Cortex-A53
           GPU     Adreno 306

Linux localhost 3.10.49-perf-gd1c5ee8 #1 SMP PREEMPT Mon Oct 26 16:13:26 CST 2015 aarch64 GNU/Linux

Processor : AArch64 Processor rev 0 (aarch64)
CPU architecture: 8
Hardware : Qualcomm Technologies, Inc MSM8916

1.
tux@slitaz:~ $ adb devices
List of devices attached
F9AXXXXXX714 device

2.
tux@slitaz:~ $ adb shell
shell@ASUS_Z00E_2:/ $ su

3.
root@ASUS_Z00E_2:/ # grep -Ei '500kl|z00e|abi|8916' /system/build.prop
ro.product.model=ASUS_Z00ED
ro.product.device=ASUS_Z00E_2
ro.product.board=msm8916
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.board.platform=msm8916
ro.build.product=ZE500KL
ro.build.fingerprint=asus/WW_Phone/ASUS_Z00E_2:5.0.2/LRX22G/12.8.5.156-20151026:user/release-keys
ro.build.csc.version=WW_ZE500KL-12.8.5.156-20151026
# from device/qcom/msm8916_64/system.prop
# system.prop for msm8916
# [ASUS BSP] Jacob Kung - ZE500KL support golve mode property
# [ASUS BSP] Jacob Kung - ZE500KL support double tap mode property
# [ASUS BSP] Jacob Kung - ZE500KL support gesture mode property
# [ASUS BSP] Jacob Kung - ZE500KL support flipcover mode property
# [ASUS BSP] Jacob Kung - ZE500KL default enable touch check proximity before gesture wake up
#Set for msm8916
ro.asus.browser.uap=ASUS-ZE500KL
root@ASUS_Z00E_2:/ #

adb - aarch64

Android Debug Bridge (adb)
AArch64 Processor (aarch64)


1.
tux@slitaz:~ $ uname -a
Linux slitaz 3.2.71-slitaz64 #2 SMP Sat Oct 10 15:35:50 CEST 2015 x86_64 GNU/Linux


2.
tux@slitaz:~ $ adb version
Android Debug Bridge version 1.0.31


3.
tux@slitaz:~ $ lsusb | grep ASUS
Bus 001 Device 003: ID 0b05:5f03 ASUSTek Computer, Inc.

tux@slitaz:~ $ lsusb -v | grep -A 15 0b05:5f03
Bus 001 Device 003: ID 0b05:5f03 ASUSTek Computer, Inc.

Device Descriptor:
bLength                 18
bDescriptorType         1
bcdUSB                  2.00
bDeviceClass            0 (Defined at Interface level)
bDeviceSubClass         0
bDeviceProtocol         0
bMaxPacketSize0        64
idVendor           0x0b05 ASUSTek Computer, Inc.
idProduct          0x5f03
bcdDevice           ff.ff
iManufacturer           1 Android
iProduct                2 Android
iSerial                 3 F9AXXXXXX714
bNumConfigurations      1 

4.
tux@slitaz:~ $ adb shell
shell@ASUS_Z00E_2:/ $ uname -a
Linux localhost 3.10.49-perf-gd1c5ee8 #1 SMP PREEMPT Mon Oct 26 16:13:26 CST 2015 aarch64 GNU/Linux


5.
shell@ASUS_Z00E_2:/ $ cat /proc/cpuinfo
Processor : AArch64 Processor rev 0 (aarch64)
processor : 0
processor : 1
processor : 2
processor : 3
Features : fp asimd crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 0

Hardware : Qualcomm Technologies, Inc MSM8916
shell@ASUS_Z00E_2:/ $

Slitaz -- Loop Install summary

/dev/sdb1: LABEL="slitaz-318" UUID="b9f5cf75-b3a0-4c86-bd48-3933094a7551" TYPE="ext4" PARTUUID="02190218-01"

1. slitaz-rolling-preinit.iso 2015-Aug-16
root@slitaz:~# grep slitaz-boot /var/lib/tazpkg/installed.md5
b43d9dd85ec1a41643a47d4856096a4c slitaz-boot-scripts-409.tazpkg


2. blkid: sda and sdb
root@slitaz:~# blkid
/dev/loop0: UUID="3bff2dfa-99d7-4e18-850e-3701b2ec017e" TYPE="ext3" PTTYPE="dos"
/dev/sda1: LABEL="win" UUID="000534FA0002617A" TYPE="ntfs" PARTUUID="329e43ff-01"
/dev/sda2: LABEL="rolling" UUID="e9594d18-8d01-4cf3-9e9c-bdcf9ca64060" TYPE="ext3" PARTUUID="329e43ff-02"
/dev/sda3: LABEL="slitaz-ff" UUID="724023ae-b6a9-4b54-9cd8-2b76a510a463" TYPE="ext4" PARTUUID="329e43ff-03"
[..]
/dev/sdb1: LABEL="slitaz-318" UUID="b9f5cf75-b3a0-4c86-bd48-3933094a7551" TYPE="ext4" PARTUUID="02190218-01"

root@slitaz:~# dmesg | grep -A 7 SanDisk
scsi 8:0:0:0: Direct-Access SanDisk Cruzer Switch 1.26 PQ: 0 ANSI: 5
sd 8:0:0:0: Attached scsi generic sg1 type 0
sd 8:0:0:0: [sdb] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB)
sd 8:0:0:0: [sdb] Write Protect is off
sd 8:0:0:0: [sdb] Mode Sense: 43 00 00 00
sd 8:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 8:0:0:0: [sdb] Attached SCSI removable disk


3. mount=/dev/sda3...
root@slitaz:~# cat /proc/cmdline
mount=/dev/sda3 loopfs=slitaz.fs

root@slitaz:~# head -7 /var/log/boot.log
Mount /dev/sda3...
Into file slitaz.fs...
[ Done ]
Processing: /etc/init.d/rcS...
Mounting proc filesystem on /proc [ Done ]
Mounting devtmpfs filesystem on: /dev [ Done ]
Starting udev daemon...

root@slitaz:~# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 3.6G 232.0K 3.6G 0% /run
/dev/sda3 484.2M 112.9M 346.4M 25% /mnt
/dev/loop0 484.2M 112.9M 346.4M 25% /
devtmpfs 3.6G 0 3.6G 0% /dev
tmpfs 3.6G 0 3.6G 0% /dev/shm
tmpfs 3.6G 0 3.6G 0% /var/lock

root@slitaz:~# mount
tmpfs on /run type tmpfs (rw,relatime)
/dev/loop0 on / type ext3 (rw,relatime,user_xattr,barrier=1,nodelalloc,data=ordered)
proc on /proc type proc (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=3798508k,nr_inodes=949627,mode=755)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime)
tmpfs on /var/lock type tmpfs (rw,relatime)
usbfs on /proc/bus/usb type usbfs (rw,relatime)
root@slitaz:~#


4. Mount /dev/sda3 (slitaz-ff)...
root@slitaz:~# cat /proc/cmdline
mount=slitaz-ff loopfs=slitaz.fs

root@slitaz:~# head -7 /var/log/boot.log
Mount /dev/sda3 (slitaz-ff)...
Into file slitaz.fs...
[ Done ]
Processing: /etc/init.d/rcS...
Mounting proc filesystem on /proc [ Done ]
Mounting devtmpfs filesystem on: /dev [ Done ]
Starting udev daemon...

root@slitaz:~# df -h | head -4
Filesystem Size Used Available Use% Mounted on
tmpfs 3.6G 228.0K 3.6G 0% /run
/dev/sda3 484.2M 112.8M 346.4M 25% /mnt
/dev/loop0 484.2M 112.8M 346.4M 25% /

root@slitaz:~# mount | head -2
tmpfs on /run type tmpfs (rw,relatime)
/dev/loop0 on / type ext3 (rw,relatime,user_xattr,barrier=1,nodelalloc,data=ordered)


5. Mount /dev/sda3 (724023ae-b6a9-4b54-9cd8-2b76a510a463)...
root@slitaz:~# cat /proc/cmdline
mount=724023ae-b6a9-4b54-9cd8-2b76a510a463 loopfs=slitaz.fs

root@slitaz:~# head -7 /var/log/boot.log
Mount /dev/sda3 (724023ae-b6a9-4b54-9cd8-2b76a510a463)...
Into file slitaz.fs...
[ Done ]
Processing: /etc/init.d/rcS...
Mounting proc filesystem on /proc [ Done ]
Mounting devtmpfs filesystem on: /dev [ Done ]
Starting udev daemon...

root@slitaz:~# df -h | head -4
Filesystem Size Used Available Use% Mounted on
tmpfs 3.6G 228.0K 3.6G 0% /run
/dev/sda3 484.2M 112.8M 346.4M 25% /mnt
/dev/loop0 484.2M 112.8M 346.4M 25% /

root@slitaz:~# mount | head -2
tmpfs on /run type tmpfs (rw,relatime)
/dev/loop0 on / type ext3 (rw,relatime,user_xattr,barrier=1,nodelalloc,data=ordered)
root@slitaz:~#


6. Mount /dev/sdb1...
root@slitaz:~# cat /proc/cmdline
mount=/dev/sdb1 loopfs=slitaz.fs

root@slitaz:~# head -8 /var/log/boot.log
Mount /dev/sdb1...
mount: mounting /dev/sdb1 on /mnt failed: No such device or address
Sleep 2 seconds...Into file slitaz.fs...
[ Done ]
Processing: /etc/init.d/rcS...
Mounting proc filesystem on /proc [ Done ]
Mounting devtmpfs filesystem on: /dev [ Done ]
Starting udev daemon...

root@slitaz:~# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 3.6G 240.0K 3.6G 0% /run
/dev/sdb1 484.2M 112.9M 346.4M 25% /mnt
/dev/loop0 484.2M 112.9M 346.4M 25% /
devtmpfs 3.6G 0 3.6G 0% /dev
tmpfs 3.6G 0 3.6G 0% /dev/shm
tmpfs 3.6G 0 3.6G 0% /var/lock

root@slitaz:~# mount
tmpfs on /run type tmpfs (rw,relatime)
/dev/loop0 on / type ext3 (rw,relatime,user_xattr,barrier=1,nodelalloc,data=ordered)
proc on /proc type proc (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=3798504k,nr_inodes=949626,mode=755)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime)
tmpfs on /var/lock type tmpfs (rw,relatime)
usbfs on /proc/bus/usb type usbfs (rw,relatime)


7. Mount slitaz-318...
root@slitaz:~$ cat /proc/cmdline
mount=slitaz-318 loopfs=slitaz.fs

root@slitaz:~$ head -11 /var/log/boot.log
Mount slitaz-318...
mount: mounting /dev/slitaz-318 on /mnt failed: No such file or directory
Sleep 2 seconds...mount: mounting /dev/slitaz-318 on /mnt failed: No such file or directory
Into file slitaz.fs...
losetup: /mnt/slitaz.fs: No such file or directory
Switching / to tmpfs...
[ Done ]
Processing: /etc/init.d/rcS...
Mounting proc filesystem on /proc [ Done ]
Mounting devtmpfs filesystem on: /dev [ Done ]
Starting udev daemon...


8. Mount b9f5cf75-b3a0-4c86-bd48-3933094a7551...
root@slitaz:~$ cat /proc/cmdline
mount=b9f5cf75-b3a0-4c86-bd48-3933094a7551 loopfs=slitaz.fs

root@slitaz:~$ head -11 /var/log/boot.log
Mount b9f5cf75-b3a0-4c86-bd48-3933094a7551...
mount: mounting /dev/b9f5cf75-b3a0-4c86-bd48-3933094a7551 on /mnt failed: No such file or directory
Sleep 2 seconds...mount: mounting /dev/b9f5cf75-b3a0-4c86-bd48-3933094a7551 on /mnt failed: No such file or directory
Into file slitaz.fs...
losetup: /mnt/slitaz.fs: No such file or directory
Switching / to tmpfs...
[ Done ]
Processing: /etc/init.d/rcS...
Mounting proc filesystem on /proc [ Done ]
Mounting devtmpfs filesystem on: /dev [ Done ]
Starting udev daemon...
root@slitaz:~$

http://forum.slitaz.org/topic/init-patch-fix-tazusb-writefs-tazlito-writeiso-issues#post-38925

Slitaz -- PS1

root@slitaz:~$

root@slitaz:~$ grep Red -A 2 /etc/profile
# Red and blue for root
PS1="\[\e[1;31m\]\u@\h\[\e[0m\]:\[\e[1;34m\]\w\[\e[0m\]\\$ "
#PS1='\u@\h:\w\$ '

root@slitaz:~$ . /etc/profile
root@slitaz:~#

Slitaz -- Loop install / UUID-2

slitaz-rolling-preinit.iso 2015-Aug-09

mount: mounting /dev/b9f5cf75-b3a0-4c86-bd48-3933094a7551 on /mnt failed: No such file or directory

/bin/sh: tazpkg: not found


1.
root@slitaz:~$ cat /proc/cmdline
mount=b9f5cf75-b3a0-4c86-bd48-3933094a7551 loopfs=slitaz.fs


2.
root@slitaz:~$ grep slitaz /var/lib/tazpkg/installed.md5
370f8b89f84bdea6d148dcde164794af slitaz-base-files-282.tazpkg
d217df7d7f46042afd4d54879170c53d slitaz-boot-scripts-408.tazpkg


3.
root@slitaz:~$ head -28 /var/log/boot.log
$root:

Mount b9f5cf75-b3a0-4c86-bd48-3933094a7551...

r=$(blkid|sed):

${r:-$root}: b9f5cf75-b3a0-4c86-bd48-3933094a7551

${r#/dev/}: b9f5cf75-b3a0-4c86-bd48-3933094a7551

{/dev/$(r%%/*)}: /dev/b9f5cf75-b3a0-4c86-bd48-3933094a7551

${root#*$r}: b9f5cf75-b3a0-4c86-bd48-3933094a7551

mount: mounting /dev/b9f5cf75-b3a0-4c86-bd48-3933094a7551 on /mnt failed: No such file or directory
Sleep 2 seconds...

$r : /dev/b9f5cf75-b3a0-4c86-bd48-3933094a7551

mount: mounting /dev/b9f5cf75-b3a0-4c86-bd48-3933094a7551 on /mnt failed: No such file or directory
Into file slitaz.fs...
losetup: /mnt/slitaz.fs: No such file or directory
Switching / to tmpfs...
[ Done ]
Processing: /etc/init.d/rcS...
Mounting proc filesystem on /proc [ Done ]
Mounting devtmpfs filesystem on: /dev [ Done ]
Starting udev daemon...


4.
root@slitaz:~$ diff /init-orig /init
--- /init-orig
+++ /init
@@ -89,18 +89,26 @@
got $1 && msg "$1 $root"
}
+echo -e "\$root: $root\n"
+
mnt()
{
r=$(blkid 2> /dev/null | sed "s|\"||g;/$(echo $root | tr / .)/!d;s|:.*||;q")
+echo -e "\nr=\$(blkid|sed): $r\n"
r=${r:-$root}
+echo -e "\${r:-\$root}: $r\n"
r=${r#/dev/}
+echo -e "\${r#/dev/}: $r\n"
r=/dev/${r%%/*}
+echo -e "{/dev/\$(r%%/*)}: $r\n"
d=${root#*$r}
+echo -e "\${root#*\$r}: $d\n"
busybox mount $r $1 && return
w=$(cat /sys/module/usb_storage/parameters/delay_use)
w=$((1+${w:-2}))
echo -n "Sleep $w seconds..."
sleep $w
+echo -e "\n\$r : $r\n"
busybox mount $r $1
}


5.
root@slitaz:~$ tazpkg
/bin/sh: tazpkg: not found

root@slitaz:~$ ls -l /usr/bin/taz*
ls: /usr/bin/taz*: No such file or directory

Slitaz -- Loop install

Loop install

http://doc.slitaz.org/en:guides:uncommoninst#loop-install

 

If you want to install SliTaz on a disk (not a frugal install), and you don't want to create a partition for SliTaz, but you have enough room in a feature-poor filesystem (FAT32 or NTFS)…
… create a loop file and install SliTaz into it!
The problem is: what size? 200MB should be the minimum. Imagine, you could like it and install many more packages!

Loopfile creation

You can create the loop file with mountbox (click loop, enter the file name, then click create, enter the size, the units, click create) or with the command line:

# dd if=/dev/zero bs=1M count=200 of=slitaz.fs

You now need to create a filesystem in this loopfile:

# yes | mke2fs -j slitaz.fs

Later, if the loopfile is too small you can extend it (assuming you don't boot from the loopfile, but a Slitaz Live CD for example):

# dd if=/dev/zero bs=1M count=100 >> slitaz.fs
# resize2fs slitaz.fs

Root filesystem files installation

Copy files from the rootfs.gz archive of a cdrom into the loopfile:

# mount /dev/cdrom /media/cdrom
# mount -o loop,rw slitaz.fs /mnt
# unlzma -c /media/cdrom/boot/rootfs.gz | ( cd /mnt; cpio -idmu )
# umount -d /mnt
# umount /media/cdrom

Boot setup

Get a preinit iso file with same version (the kernel version must match the modules version in the root filesystem). The partition storing the loopfile (say /dev/hda1) and its path into the partition (say /data/slitaz.fs) is defined by the mount and loopfs arguments:

title SliTaz cooking
  map (hd0,0)/boot/slitaz-preinit.iso (hd1)
  map --hook
  kernel (hd1)/boot/bzImage mount=/dev/hda1 loopfs=data/slitaz.fs
  initrd (hd1)/boot/rootfs.gz

 

The loop install does not use exotic packages from preinit. You can use any SliTaz flavor (except lorams).

 

You can built an up-to-date preinit iso anytime with

# tazlito get-flavor preinit
# tazlito gen-distro

title SliTaz cooking in loop file
  map (hd0,0)/boot/slitaz-cooking.iso (hd1)
  map --hook
  kernel (hd1)/boot/bzImage mount=/dev/hda1 loopfs=data/slitaz.fs
  initrd (hd1)/boot/rootfs.gz
  
title SliTaz cooking in RAM (like the Live CD)
  map (hd0,0)/boot/slitaz-cooking.iso (hd1)
  map --hook
  kernel (hd1)/boot/bzImage rw root=/dev/null autologin
  initrd (hd1)/boot/rootfs.gz

Or, you can replace the device name of the mount variable by the UUID or LABEL returned by blkid:

title SliTaz cooking
  map (hd0,0)/boot/slitaz-preinit.iso (hd1)
  map --hook
  kernel (hd1)/boot/bzImage mount=a4b346ee-4c7b-46aa-9fd4-6bc39ab4fa96 loopfs=data/slitaz.fs
  initrd (hd1)/boot/rootfs.gz

 

You can extract the bzImage and rootfs.gz from the iso image to avoid map commands and defragmentation.

Slitaz -- Loop install / LABEL

Or, you can replace the device name of the mount variable by the UUID or LABEL returned by blkid:

mount: mounting /dev/slitaz-318 on /mnt failed: No such file or directory

tmpfs: Bad value '90%' for mount option 'nr_inodes'
 

1.
root@slitaz:~# cat /proc/cmdline
mount=slitaz-318 loopfs=slitaz.fs

2.
root@slitaz:~# head -12 /var/log/boot.log
Mount slitaz-318...
mount: mounting /dev/slitaz-318 on /mnt failed: No such file or directory
Sleep 2 seconds...mount: mounting /dev/slitaz-318 on /mnt failed: No such file or directory
Into file slitaz.fs...
losetup: /mnt/slitaz.fs: No such file or directory
Switching / to tmpfs...
mount: mounting tmpfs on /mnt failed: Invalid argument
[ Skipped ]
Loading module: squashfs
Processing: /etc/init.d/rcS...
Mounting proc filesystem on /proc [ Done ]
Mounting devtmpfs filesystem on: /dev [ Done ]

3.
root@slitaz:~# grep tmpfs /var/log/dmesg.log
tmpfs: Bad value '90%' for mount option 'nr_inodes'
root@slitaz:~# blkid | grep sdb
/dev/sdb1: LABEL="slitaz-318" UUID="b9f5cf75-b3a0-4c86-bd48-3933094a7551" TYPE="ext4" PARTUUID="02190218-01"

4.
root@slitaz:~# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 3.6G 212.0K 3.6G 0% /run
devtmpfs 3.6G 0 3.6G 0% /dev
tmpfs 3.6G 0 3.6G 0% /dev/shm
tmpfs 3.6G 0 3.6G 0% /var/lock

5.
root@slitaz:~# mount
rootfs on / type rootfs (rw,relatime)
tmpfs on /run type tmpfs (rw,relatime)
proc on /proc type proc (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=3798496k,nr_inodes=949624,mode=755)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime)
tmpfs on /var/lock type tmpfs (rw,relatime)
usbfs on /proc/bus/usb type usbfs (rw,relatime)

6.
root@slitaz:~# grep -A 13 'mnt()' /init
mnt()
{
r=$(blkid 2> /dev/null | sed "s|\"||g;/$(echo $root | tr / .)/!d;s|:.*||;q")
r=${r:-$root}
r=${r#/dev/}
r=/dev/${r%%/*}
d=${root#*$r}
busybox mount $r $1 && return
w=$(cat /sys/module/usb_storage/parameters/delay_use)
w=$((1+${w:-2}))
echo -n "Sleep $w seconds..."
sleep $w
busybox mount $r $1
}

7.
root@slitaz:~# grep -A 4 rootfsinodes /init
got rootfsinodes && inodes=$root
root=90%
got rootfssize
[ $(busybox free|busybox awk '/Mem:/{print int(($4*100)/$3)}') -ge $r ] &&
busybox mount -t tmpfs -o size=$root,nr_inodes=$inodes tmpfs /mnt &&
root@slitaz:~#

Slitaz -- Loop install / UUID

Loop install
http://doc.slitaz.org/en:guides:uncommoninst#loop-install

Boot setup
[..]
title SliTaz cooking in loop file
map (hd0,0)/boot/slitaz-cooking.iso (hd1)
map --hook
kernel (hd1)/boot/bzImage mount=/dev/hda1 loopfs=data/slitaz.fs
initrd (hd1)/boot/rootfs.gz

title SliTaz cooking in RAM (like the Live CD)
map (hd0,0)/boot/slitaz-cooking.iso (hd1)
map --hook
kernel (hd1)/boot/bzImage rw root=/dev/null autologin
initrd (hd1)/boot/rootfs.gz

Or, you can replace the device name of the mount variable by the UUID or LABEL returned by blkid:

title SliTaz cooking
map (hd0,0)/boot/slitaz-preinit.iso (hd1)
map --hook
kernel (hd1)/boot/bzImage mount=a4b346ee-4c7b-46aa-9fd4-6bc39ab4fa96 loopfs=data/slitaz.fs
initrd (hd1)/boot/rootfs.gz

mount: mounting /dev/b9f5cf75-b3a0-4c86-bd48-3933094a7551 on /mnt failed: No such file or directory
tmpfs: Bad value '90%' for mount option 'nr_inodes'


1.
root@slitaz:~# cat /proc/cmdline
mount=b9f5cf75-b3a0-4c86-bd48-3933094a7551 loopfs=slitaz.fs

2.
root@slitaz:~# head -11 /var/log/boot.log
Mount b9f5cf75-b3a0-4c86-bd48-3933094a7551...
mount: mounting /dev/b9f5cf75-b3a0-4c86-bd48-3933094a7551 on /mnt failed: No such file or directory
Sleep 2 seconds...mount: mounting /dev/b9f5cf75-b3a0-4c86-bd48-3933094a7551 on /mnt failed: No such file or directory
Into file slitaz.fs...
losetup: /mnt/slitaz.fs: No such file or directory
Switching / to tmpfs...
mount: mounting tmpfs on /mnt failed: Invalid argument
[ Skipped ]
Loading module: squashfs
Processing: /etc/init.d/rcS...
Mounting proc filesystem on /proc [ Done ]

3.
root@slitaz:~# grep tmpfs /var/log/dmesg.log
tmpfs: Bad value '90%' for mount option 'nr_inodes'

4.
root@slitaz:~# blkid | grep sdb
/dev/sdb1: LABEL="slitaz-318" UUID="b9f5cf75-b3a0-4c86-bd48-3933094a7551" TYPE="ext4" PARTUUID="02190218-01"

5.
root@slitaz:~# grep -A 7 'mnt()' /init
mnt()
{
r=$(blkid 2> /dev/null | sed "s|\"||g;/$(echo $root | tr / .)/!d;s|:.*||;q")
r=${r:-$root}
r=${r#/dev/}
r=/dev/${r%%/*}
d=${root#*$r}

6.
root@slitaz:~# grep -A 4 rootfsinodes /init
got rootfsinodes && inodes=$root
root=90%
got rootfssize
[ $(busybox free|busybox awk '/Mem:/{print int(($4*100)/$3)}') -ge $r ] &&
busybox mount -t tmpfs -o size=$root,nr_inodes=$inodes tmpfs /mnt &&
root@slitaz:~#

http://hg.slitaz.org/slitaz-boot-scripts/rev/d6c818f35639

Slitaz -- sed: unsupported command |

sed: unsupported command |

root@slitaz:~# cat /proc/cmdline
mount=/dev/sda3 loopfs=slitaz.fs

root@slitaz:~# head -4 /var/log/boot.log
Mount /dev/sda3...
sed: unsupported command |
Into file slitaz.fs...
[ Done ]

root@slitaz:~# grep -A 13 'mnt()' /init
mnt()
{
r=$(blkid 2> /dev/null | sed "s|\"||g;|$root|!d;s|:.*||;q")
r=${r:-$root}
r=${r#/dev/}
r=/dev/${r%%/*}
d=${root#*$r}
busybox mount $r $1 && return
w=$(cat /sys/module/usb_storage/parameters/delay_use)
w=$((1+${w:-2}))
echo -n "Sleep $w seconds..."
sleep $w
busybox mount $r $1
}

Slitaz -- cookutils / bundle.tar.lzma / IDs

Getting "bundle.tar.lzma"...

1.
root@slitaz:/home/tux# tazpkg recharge

Recharging repository "Main"
================================================================================
Database timestamp: 05/24/2015 00:01
Creating backup of the last packages list...                           [ Failed ]
Getting "bundle.tar.lzma"...                                                     [ Done ]
Getting "files-list.lzma"...                                                         [ Done ]
================================================================================
Last database is ready to use.


2.
root@slitaz:/home/tux# ls -l /var/lib/tazpkg/ID*
-rw-r--r--    1 root     root            33 May 25  2015 /var/lib/tazpkg/ID
-rw-r--r--    1 root     root            44 May 25  2015 /var/lib/tazpkg/IDs

root@slitaz:/home/tux# cat /var/lib/tazpkg/ID*
28b4d51b105dfca6be5201742bc78de5
28b4d51b105dfca6be5201742bc78de5 1432425688

root@slitaz:/home/tux# date -d @1432425688
Sun May 24 00:01:28 UTC 2015
root@slitaz:/home/tux#


3.
cookutils changeset 725:2cf877e5b167

http://hg.slitaz.org/cookutils/raw-rev/2cf877e5b167
# HG changeset patch
# User Aleksej Bobylev <al.bobylev@gmail.com>
# Date 1430654849 -10800
# Node ID 2cf877e5b1677e2c7d6a3870bf4cc1985dab3ee2
# Parent  851a2b8075dc6c67c36ddec39e2e7b60470f2bd6
cook pkgdb: provide new mechanism of recharging: IDs contains "old" ID plus timestamp, bundle.tar.lzma contains all "old" recharge files plus files.list.md5 to determine whether to download massive files.list.lzma or not.

diff -r 851a2b8075dc -r 2cf877e5b167 cook
--- a/cook    Fri Apr 17 14:10:59 2015 +0200
+++ b/cook    Sun May 03 15:07:29 2015 +0300
@@ -1348,20 +1348,26 @@
         echo "cook:pkgdb" > $command
         _ "Cook pkgdb: Creating all packages lists" | log
         newline; _ "Creating lists for: \$PKGS"; separator
+
         datenow=$(date "$(_ '+%Y-%m-%d %H:%M')")
         _ "Cook pkgdb started: \$datenow"
+
         cd $PKGS
         rm -f packages.* extra.list
         ln -s ../get.list extra.list
+
         _ "Creating: packages.list"
         ls -1 *.tazpkg | sed s'/.tazpkg//' > $PKGS/packages.list
+
         _ "Creating: packages.md5"
         md5sum *.tazpkg > $PKGS/packages.md5
+
         md5sum packages.md5 | cut -f1 -d' ' > ID
+        ( cat ./ID | tr $'\n' ' '; date -ur ./ID +%s ) > IDs    # md5 and timestamp
+
         _ "Creating lists from: \$WOK"
         cd $WOK
-        for pkg in *
-        do
+        for pkg in *; do
             unset_receipt
             . $pkg/receipt
             # PACKED_SIZE and UNPACKED_SIZE are only in built receipt
@@ -1420,15 +1426,25 @@
         # files.list.lzma
         _ "Creating: files.list.lzma"
         touch $PKGS/files.list
-        cd $PKGS; lzma e files.list files.list.lzma
-        rm -f files.list
+        # Pre-sorting filenames causes 10% smaller resulting lzma file
+        cat $PKGS/files.list | sort -k2 -o $PKGS/files.list.sorted
+        cd $PKGS; lzma e files.list.sorted files.list.lzma
+        rm -f files.list files.list.sorted
+
+        md5sum files.list.lzma | cut -d' ' -f1 | tr -d $'\n' > files.list.md5

         # packages.info.lzma
         PI=packages.info
         _ 'Creating: packages.info.lzma'
         touch $PKGS/$PI
         cd $PKGS; lzma e $PI $PI.lzma
-        rm -f $PI
+
+        # Make bundle to fast recharge
+        _ 'Creating: bundle.tar.lzma'
+        [ -f bundle.tar.lzma ] && rm bundle.tar.lzma
+        busybox tar -caf bundle.tar.lzma \
+            extra.list mirrors files.list.md5 packages.info \
+            packages.desc packages.md5 packages.txt packages.list packages.equiv

         # Display some info.
         separator

Slitaz -- date / rdate

Unix time (also known as POSIX time or erroneously as Epoch time)

1.
tux@slitaz:~$ dmesg | grep cmos
rtc_cmos 00:07: RTC can wake from S4
rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
rtc_cmos 00:07: setting system clock to 2015-05-14 10:38:31 UTC (1431599911)


2.
tux@slitaz:~$ date -d @1431599911
Thu May 14 18:38:31 CST 2015


3.
tux@slitaz:~$ date
Thu May 14 18:46:37 CST 2015

tux@slitaz:~$ date -u
Thu May 14 10:46:55 UTC 2015

tux@slitaz:~$ date -R
Thu, 14 May 2015 18:47:19 +0800

tux@slitaz:~$ date +%s
1431600482

tux@slitaz:~$ date -ud @1431600482
Thu May 14 10:48:02 UTC 2015


4.
tux@slitaz:~$ rdate -p time.nist.gov
Thu May 14 10:50:17 2015

tux@slitaz:~$ sudo rdate -s time.nist.gov
tux@slitaz:~$ date
Thu May 14 18:52:06 CST 2015

Ref:

Unix time

http://en.wikipedia.org/wiki/Unix_time 

Unix time (also known as POSIX time or erroneously as Epoch time) is a system for describing instants in time, defined as the number of secondsthat have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970,^{[1][note 1]} not counting leap seconds.^{[1][2][note 2]}It is used widely in Unix-like and many other operating systems and file formats. Due to its handling of leap seconds, it is neither a linear representation of time nor a true representation of UTC.^{[note 3]} Unix time may be checked on most Unix systems by typing date +%s on the command line.

Example: 1431460917 (ISO 8601:2015-05-12T20:01:57Z) the Unix time when this page was last generated

UTC time is also known as 'Zulu' time, since 'Zulu' is the NATO phonetic alphabet word for 'Z'.

http://en.wikipedia.org/wiki/ISO_8601 

Combined date and time representations

<date>T<time>

A single point in time can be represented by concatenating a complete date expression, the letter T as a delimiter, and a valid time expression. For example "2007-04-05T14:30".

grus4dos : map --mem option

map --mem option
https://github.com/chenall/grub4dos/blob/master/README_GRUB4DOS.txt#L3136 

***                  The CDROM emulation (virtualization)               ***
*****************************************************************

The CDROM emulation is sometimes called ISO emulation. Here is an example:

map  (hd0,0)/myiso.iso  (hd32)
map  --hook
chainloader  (hd32)
boot

if myiso.iso is not contiguous and you have enough memory, add a --mem option:

map  --mem  (hd0,0)/myiso.iso  (hd32)
map  --hook
chainloader  (hd32)
boot

Note: (hd32) is a grub drive number equivalent to (0xA0). If a virtual drive is
specified with a drive number greater than or equal to 0xA0, then it will be
treated as a cdrom (i.e., with 2048-byte big sectors).

Like normal disk emulations, the CDROM emulation also (mainly) works with
real-mode OSes. After a protected-mode OS kernel (such as
WinNT/2K/XP/VISTA/LINUX) gains control, the OS would have no ability to access
the virtual CDROM through BIOS int13.

DOS/Win9x users may google for ELTORITO.SYS and use it in CONFIG.SYS as a
device driver for the virtual cdrom.

Example usage of eltorito.sys in CONFIG.SYS:

device=eltorito.sys /D:oemcd001

Corresponding MSCDEX command which can be placed in AUTOEXEC.BAT:

MSCDEX /D:oemcd001 /L:D


Due to some bugs found in eltorito.sys, the driver could fail to load. If you
encounter such problems, then you may replace (hd32) with (0xFF) for the
virtual cdrom drive number and try again.

Slitaz -- Java Control Panel

1.
tux@slitaz:~$ java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) Server VM (build 25.45-b02, mixed mode)


2.
tux@slitaz:~$ tazpkg info javajre

TazPKG information
=================================================================
Package    : javajre
Version    : 1.8.0_45
Category   : non-free
Short desc : Java Platform Standard Edition Runtime Environment
Maintainer : nobody@slitaz.org
Depends    : bash
Web site   : http://java.com/en/download/linux_manual.jsp?locale=en
Size       : 44.5M/163.7M
=================================================================


3.
tux@slitaz:~$ ldd /usr/lib/java/jre1.8.0_45/bin/java

/usr/lib/java/jre1.8.0_45/bin/java:
linux-gate.so.1 =>  (0xffffe000)
libpthread.so.0 => /lib/libpthread.so.0 (0xf778d000)
libjli.so => /usr/lib/java/jre1.8.0_45/bin/../lib/i386/jli/libjli.so (0xf7778000)
libdl.so.2 => /lib/libdl.so.2 (0xf7773000)
libc.so.6 => /lib/libc.so.6 (0xf75fd000)
/lib/ld-linux.so.2 => /lib/ld-2.14.1.so (0xf77aa000)

4.
tux@slitaz:~$ jcontrol &

tux@slitaz:~$ ps | grep -A 1 jcontrol
 2417 tux        0:00 {jcontrol} /bin/bash /usr/bin/jcontrol
 2434 tux        0:01 /usr/lib/java/jre1.8.0_45/bin/java -Djavaplugin.user.profile= -Xbootclasspath/a:/usr/lib/java/jre1.8.0_45/bin/../lib/deploy.jar com.sun.deploy.panel.ControlPanel
--
 2458 tux        0:00 grep -A 1 jcontrol
tux@slitaz:~$


5.
tux@slitaz:~$ head -6 /usr/lib/java/jre1.8.0_45/bin/jcontrol
#!/bin/bash
#
# Copyright (c) 2006, 2011, Oracle and/or its affiliates. All rights reserved.
# ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
#
# Shell Script to run the Java Plug-in control panel.

Slitaz -- get-scripts / tazpkg / qcad

Depends : qcad ??

Please check get-scripts and tazpkg.

1.
# TazPanel Install "FoxitReader"
[..]
TazPkg: Install
Installing: FoxitReader
Tracking dependencies for package "FoxitReader"
Missing package "qcad"


2.
# tazpkg -gi flash-plugin
[..]
Package "flash-plugin-11.2.202.457" compressed successfully.
Size: 4.9M
Tracking dependencies for package "flash-plugin"
==============================================================================
Missing package "seamonkey"
Missing package "qcad"
==============================================================================
2 missing packages to install.


3.
# tazpkg -gi javajre
[..]
Package "javajre-1.8.0_45" compressed successfully.
Size: 32.2M
WARNING! Dependency loop between "javajre" and "qcad".
Tracking dependencies for package "javajre"
======================================================================
Missing package "nvidia-173xx"
Missing package "glib-dev"
Missing package "ffmpeg-compat"
Missing package "cairo-gl"
======================================================================
4 missing packages to install.

Slitaz -- get-scripts / tazpkg

Also, the current get script pulls a lot of dependencies: qcad,
which itself pulls many libQt*, nvidia-173xx, mesa-wayland
(which pulls wayland). Do we really need all this stuff?

1.
tux@slitaz:~$ tazpkg info qcad
TazPKG information
=========================================================
Package : qcad
Version : 3.7.5
Category : network
Short desc : The Open Source CAD System For Everyone.
Maintainer : pankso@slitaz.org
License : GPL3
Depends : libQtWebkit libQtGui libQtDesigner libQtXml libQtDeclarative libQtCore libQtScript libQtNetwork libQtClucene libQtOpenGL libQtDBus libQtScriptTools libQtHelp libQtSvg libQtSql libQtTest libQtMultimedia
Web site : http://www.qcad.org
Size : 23M/134.7M
=========================================================



2.
TazPkg: Install
Installing: FoxitReader

Tracking dependencies for package "FoxitReader"

Missing package "qcad"


3.

tux@slitaz:~$ ldd /usr/bin/FoxitReader | grep libqcad*

tux@slitaz:~$ ldd /usr/bin/FoxitReader

/usr/bin/FoxitReader:
 linux-gate.so.1 =>  (0xffffe000)
 libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xf7357000)
 libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xf72b8000)
 libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xf7297000)
 libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xf7285000)
 libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xf7266000)
 libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xf725a000)
 libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0xf70ed000)
 libcairo.so.2 => /usr/lib/libcairo.so.2 (0xf6ff0000)
 libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xf6fac000)
 libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xf6f33000)
 libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xf6f01000)
 libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xf6ebf000)
 libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xf6ebc000)
 libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xf6dc9000)
 libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xf6dc6000)
 libcups.so.2 => /usr/lib/libcups.so.2 (0xf6d67000)
 libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xf6ca1000)
 libm.so.6 => /lib/libm.so.6 (0xf6c74000)
 libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xf6c5c000)
 libc.so.6 => /lib/libc.so.6 (0xf6ae6000)
 libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xf6ae0000)
 libX11.so.6 => /usr/lib/libX11.so.6 (0xf69c4000)
 libpthread.so.0 => /lib/libpthread.so.0 (0xf69a9000)
 libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xf69a6000)
 libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xf699d000)
 libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xf6993000)
 libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0xf6990000)
 libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0xf698d000)
 libXrender.so.1 => /usr/lib/libXrender.so.1 (0xf6985000)
 libXext.so.6 => /usr/lib/libXext.so.6 (0xf6975000)
 libffi.so.6 => /usr/lib/libffi.so.6 (0xf696e000)
 libpcre.so.1 => /usr/lib/libpcre.so.1 (0xf6934000)
 librt.so.1 => /lib/librt.so.1 (0xf692b000)
 libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0xf68e6000)
 libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0xf68d5000)
 libxml2.so.2 => /usr/lib/libxml2.so.2 (0xf67b9000)
 libdl.so.2 => /lib/libdl.so.2 (0xf67b4000)
 libz.so.1 => /usr/lib/libz.so.1 (0xf67a1000)
 libresolv.so.2 => /lib/libresolv.so.2 (0xf6788000)
 libpng12.so.0 => /usr/lib/libpng12.so.0 (0xf6766000)
 libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0xf66dd000)
 libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0xf66da000)
 libX11-xcb.so.1 => /usr/lib/libX11-xcb.so.1 (0xf66d8000)
 libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0xf66cf000)
 libxcb.so.1 => /usr/lib/libxcb.so.1 (0xf66af000)
 libXau.so.6 => /usr/lib/libXau.so.6 (0xf66ab000)
 libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xf66a6000)
 libEGL.so.1 => /usr/lib/libEGL.so.1 (0xf6689000)
 libGL.so.1 => /usr/lib/libGL.so.1 (0xf6630000)
 libcrypt.so.1 => /lib/libcrypt.so.1 (0xf65fd000)
 /lib/ld-linux.so.2 => /lib/ld-2.14.1.so (0xf775d000)
 libxcb-dri2.so.0 => /usr/lib/libxcb-dri2.so.0 (0xf65f8000)
 libxcb-xfixes.so.0 => /usr/lib/libxcb-xfixes.so.0 (0xf65f1000)
 libxcb-shape.so.0 => /usr/lib/libxcb-shape.so.0 (0xf65ed000)
 libwayland-client.so.0 => /usr/lib/libwayland-client.so.0 (0xf65e4000)
 libwayland-server.so.0 => /usr/lib/libwayland-server.so.0 (0xf65d7000)
 libgbm.so.1 => /usr/lib/libgbm.so.1 (0xf65d2000)
 libglapi.so.0 => /usr/lib/libglapi.so.0 (0xf65b4000)
 libudev.so.0 => /lib/libudev.so.0 (0xf65a6000)
 libdrm.so.2 => /usr/lib/libdrm.so.2 (0xf659b000)
 libxcb-glx.so.0 => /usr/lib/libxcb-glx.so.0 (0xf6584000)
 libXxf86vm.so.1 => /usr/lib/libXxf86vm.so.1 (0xf657f000)

tux@slitaz:~$ 

Slitaz -- javajre

Short answer : try 'tazpkg get-install javajre'

get-scripts are lighter: common parts are in tazpkg.
They are safer: tazpkg automagicaly detects the depends.

root@slitaz:/home/tux# java -version
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object


root@slitaz:/home/tux# tazpkg info javajre
TazPKG information
==============================================================================
Package : javajre
Version : 1.8.0_40
Category : non-free
Short desc : Java Platform Standard Edition Runtime Environment
Maintainer : nobody@slitaz.org
Depends : zlib xorg-libXxf86vm xorg-libXtst xorg-libXrender xorg-libXrandr xorg-libXinerama xorg-libXi xorg-libXfixes xorg-libXext xorg-libXdmcp xorg-libXdamage xorg-libXcursor xorg-libXcomposite xorg-libXau xorg-libX11 qcad pixman pcre pango nvidia-173xx libxslt libxml2 libxcb libpng libgio libffi harfbuzz gtk+ glib-dev glib gdk-pixbuf fontconfig ffmpeg-compat cairo-gl bzlib atk alsa-lib
Web site : http://java.com/en/download/linux_manual.jsp?locale=en
==============================================================================


root@slitaz:/home/tux# uname -a
Linux slitaz 3.2.53-slitaz #4 SMP Wed Mar 25 11:33:01 CET 2015 i686 GNU/Linux


Ref:

http://forum.slitaz.org/topic/patches-to-get-java6-jre-get-libreoffice-get-teamviewer#post-37175

Get-scripts are pushed to the get repo on mirror which is mirror/slitaz/packages/get folder.

http://download.tuxfamily.org/slitaz/packages/get/

Tazpkg uses download_get_script function to download get-script from packages/get folder on mirror.

http://hg.slitaz.org/tazpkg/rev/67303cb00c9f

The get-scripts are listed for download in tazpanel/packages -> extra categorie

http://hg.slitaz.org/tazpkg/rev/c82b727d2012

tazpkg recharge pulls the extra.list with contents of get repo.

I see no way to list or search the extra list from tazpkg.

It appears the user would have to know the exact name of the script to fetch it unless there is a tazpkg of the exact name.

Thanks Pascal!

tazpkg searchs extra.list

http://hg.slitaz.org/tazpkg/rev/37df6365cf41