Ok, No More Major Issues In Cacko 1.22?

[Miami_Bob]

Man, you're probably starting to hate seeing my posts (G). But this one is easy.

At first I wasn't sure the screen capture (shift)+(Fn)+C was working. No "shutter" sound. Noticed that several wave files were AWOL from the sounds subdir.

I can understand dropping chime.wav & wave.wav since they are 110kB & 207kB. But shtr.wav is only 17kB. And it lets you know for sure that you've got the "shot".

Since I have pleanty of room still, I added all 5 back.

chime.wav          110k
shtr.wav               17k
surprise.wav         74k
wave.wav            207k
xylophone.wav     65k

Just for what its worth (G).


BTW - the cache routines are doing a much better job of returning free memory when required than the Sharp 1.31 or 1.40 versions. Sometime with the Sharp ones, I have to reboot in order to stop the yellow warning from showing even when only a few apps are running. After reboot, the cache is back to more reasonable size. I have not gotten a yellow warning yet with v1.22 despite sometimes having (IMHO) very little free memory. GOOD WORK, gang!!

[maslovsky]

Man, you're probably starting to hate seeing my posts (G). But this one is easy.

At first I wasn't sure the screen capture (shift)+(Fn)+C was working. No "shutter" sound. Noticed that several wave files were AWOL from the sounds subdir.[div align=\"right\"][a href=\"index.php?act=findpost&pid=64443\"][{POST_SNAPBACK}][/a][/div]

Yes, I noticed that "shutter" sound was missing from the ROM. This will be fixed in Hotfix A

[Stubear]

Any chance of getting bunzip2 linked to bzip2?

It's not a major annoyance, but annoyance when I forget and type "bunzip" before I remember and have to go back and  type "bzip2 -d".

Also there is a more up to date version of busybox (1.0) kicking around - although for some reason they haven't included mount support. Having a tar that recognised -j flag would be great.

Stu

[maslovsky]

Any chance of getting bunzip2 linked to bzip2?

It's not a major annoyance, but annoyance when I forget and type "bunzip" before I remember and have to go back and type "bzip2 -d".

I have bunzip2 linked to bzip2 linked on my Z, but I have heavily customized ROM version, so I'll check default ROM

Also there is a more up to date version of busybox (1.0) kicking around - although for some reason they haven't included mount support. Having a tar that recognised -j flag would be great.

No, that's a huuuuge pain in the butt. I've spent about two weeks trying to get busybox 1.0 into 1.22 ROM. It's totaly incompatible with many Sharp applications, including Package Manager. And once againm since we have no source code for them, there is no way to fix the problems. We're stuck with current bisybox.

[Stubear]

No, that's a huuuuge pain in the butt. I've spent about two weeks trying to get busybox 1.0 into 1.22 ROM. It's totaly incompatible with many Sharp applications, including Package Manager. And once againm since we have no source code for them, there is no way to fix the problems. We're stuck with current bisybox.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=64896\"][{POST_SNAPBACK}][/a][/div]

Hmm, the version of busybox I've got on my Z now installs into Qtopia/bin and hasn't given me any problems with any of the sharp apps. Maybe it's because the original busybox is still present in /bin/ and the package manager is hard coded to call /bin/tar.

I'll try replacing the version I have with the one in /bin and get back to you with the results.

I'll also try contacting the author and see if mount can be put in to the 1.0 version

Stu

[maslovsky]

Hmm, the version of busybox I've got on my Z now installs into Qtopia/bin and hasn't given me any problems with any of the sharp apps. Maybe it's because the original busybox is still present in /bin/ and the package manager is hard coded to call /bin/tar.

I'll try replacing the version I have with the one in /bin and get back to you with the results.

I'll also try contacting the author and see if mount can be put in to the 1.0 version

Stu
[div align=\"right\"][a href=\"index.php?act=findpost&pid=65030\"][{POST_SNAPBACK}][/a][/div]

Be carefull, you can easily get your Zaurus into unbootable state by replacing busybox...

[stupkid]

Stubear,

Once you get your the 1.00 version busybox booting make sure that you test all the Sharp apps thoroughly.  We always thought that we had succeeded only to find a few problems with the Sharp apps.  There are also a few applets that are in the 0.65 verison of busybox that are not available in the new version.

Good Luck!

[maslovsky]

To my opinion it's not really worth the efforts. If you need tar with -j option, I can simply create a ipk with standalone version of tar, which will install somewhere to /usr/local/bin and will not interfere with busybox's tar.

[Stubear]

Well I'm using the ipk from here and everything seems fine at the moment. I can install and remove packages using ipkg and qinstall. Mount has been moved to sbusybox so I had to make a new symlink, but it rebooted fine (although there were some errors about /etc/mtab being readonly).

The main reason I want the later version of busybox is to get rid of tar, bzip, zip etc and use busybox for them all - saving space on the filesystem so I can put other things there.

The current version has the following modules available

    [, ar, arping, awk, basename, bunzip2, busybox, bzcat, cal, cat,
    chgrp, chmod, chown, chroot, chvt, clear, cmp, cp, cpio, crond,
    cut, date, dc, dd, deallocvt, df, dirname, dmesg, dos2unix, dpkg,
    dpkg-deb, du, dumpkmap, echo, egrep, env, expr, false, fbset,
    fdflush, fdisk, fgrep, find, fold, free, freeramdisk, fsck.minix,
    ftpget, ftpput, getopt, grep, gunzip, gzip, head, hexdump, hostid,
    hostname, hwclock, id, ifconfig, insmod, install, ip, ipaddr,
    ipcalc, iplink, iproute, iptunnel, kill, killall, last, length,
    ln, loadfont, loadkmap, logger, logname, losetup, ls, lsmod, makedevs,
    md5sum, mkdir, mkfifo, mkfs.minix, mknod, mkswap, mktemp, modprobe,
    more, mt, mv, nameif, nc, netstat, nslookup, od, openvt, patch,
    pidof, pipe_progress, pivot_root, printf, ps, pwd, rdate, readlink,
    realpath, renice, reset, rm, rmdir, rmmod, route, rpm, rpm2cpio,
    run-parts, rx, sed, seq, setkeycodes, sha1sum, sleep, sort, start-stop-daemon,
    strings, stty, swapoff, swapon, sync, sysctl, tail, tar, tee,
    telnet, test, tftp, time, top, touch, tr, true, tty, uname, uncompress,
    uniq, unix2dos, unzip, uptime, usleep, uudecode, uuencode, watch,
    watchdog, wc, wget, which, who, whoami, xargs, yes, zcat

and sbusybox has

busybox, crontab, mount, ping, ping6, traceroute, umount

Which means I don't have to install seperate ipks for strings, traceroute, tar, zip, gzip, top, bzip, fdisk - yeah I know that many of these are already installed on Cacko but they are seperate programs that are taking space I could use for storing other things like dictionary files and games.

I'll get back to you after I've given the new busybox a workout nad tested all the Sharp apps.

By the way could you include dawg (in /home/QtPalmtop/etc/dict/ so that the handwriting app has word completion/lookup - it makes using it so much faster. If you don't have the file I can upload it - it's available in the opie-i18n-eng ipk from memory. I assume that other language version would work too but have only tried English.

Stu

[stupkid]

Most of the busybox versions of the apps you have are missing many features.  The features for tar, sed, awk, grep, and find to name a few are missing most of the functionality of the regular GNU versions of those apps.  You will end up using more space once you have the same amount of functionality + some of the new busybox features.  So, if saving space is your motivation I don't see the pay off.

[maslovsky]

Well I'm using the ipk from here and everything seems fine at the moment. I can install and remove packages using ipkg and qinstall. Mount has been moved to sbusybox so I had to make a new symlink, but it rebooted fine (although there were some errors about /etc/mtab being readonly).

Are you sure you indeed replaced original busybox? How did you install new one? The only way you can actualy replace busybox in ROM is to remount root partition as writable and replace busybox binary in /bin. The try to reboot and install some packages via Package Manager.

Unless you have replaced busybox in /bin, your system doesn't use it. And you don't save any space...

Finally you can calculate how much space you save by replacing some of the full featured apps with creapy busybox versions and I'm sure you won't even get to a 1 Mb...

[Stubear]

Most of the busybox versions of the apps you have are missing many features.  The features for tar, sed, awk, grep, and find to name a few are missing most of the functionality of the regular GNU versions of those apps.  You will end up using more space once you have the same amount of functionality + some of the new busybox features.  So, if saving space is your motivation I don't see the pay off.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=65178\"][{POST_SNAPBACK}][/a][/div]

That's part of the testing procedure - finding out what the busybox version is missing. If it's missing something that I think is important then I agree that it's not worth it. I.e although tar has the -j flag to allow inline bzip2 usage, it seems to be lacking the -p flag to keep permissions.

There may not be much space saving in the ned, but a lot of it is just the fun of playing with my Z and seeing what it is I can/can't change

Stu

[Stubear]

Are you sure you indeed replaced original busybox? How did you install new one? The only way you can actualy replace busybox in ROM is to remount root partition as writable and replace busybox binary in /bin. The try to reboot and install some packages via Package Manager.

Unless you have replaced busybox in /bin, your system doesn't use it. And you don't save any space...

Finally you can calculate how much space you save by replacing some of the full featured apps with creapy busybox versions and I'm sure you won't even get to a 1 Mb...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=65212\"][{POST_SNAPBACK}][/a][/div]

Yep, sure I've replaced the original busybox.

Installed the ipk, which installs busybox to /home/QtPalmtop/bin and creates a few symlinks.
Remount / rw - mount -o remount,rw /
Cd to /bin and mv busybox busybox.orig and mv sbusybox sbusybox.orig
cp /home/QtPamltop/bin/busybox /bin/busybox
cp /home/QtPalmtop/bin/sbusybox /bin/sbusybox
rm mount umount
ln -s sbusybox mount and ln -s sbusybox umount
Remount / ro - mount -o remount,ro /

Test a few things in konsole and then get brave enough to reboot

Warning - Do not try this without having a backup. You can make you Z unbootable I know I did it with the last version before I noticed mount was in sbusybox instead of busybox

Yeah, I probably won't save a lot of space, but then if I didn't try I wouldn't be having fun. And I might just learn something useful too. Although I do see you point about stability and compatability in the Cacko rom - if it wasn't this stable then I wouldn't be brave enough to play.

Stu

[ev1l]

It's the second time now that Cacko fucks itself: it suddenly stops responding, and rebooting it litteraly takes *hours* (I had to let it sit overnight).
I don't know what causes it, which is what's turning me crazy.
How can I provide you guys with feedback next time it happens? I don't really have much of anything else installed: KDEPIM/PI suite, qpe-filemanager, qpe-alarmclock, that's about it (that runs permanaently, anyway).

[juanr]

It's the second time now that Cacko fucks itself: it suddenly stops responding, and rebooting it litteraly takes *hours* (I had to let it sit overnight).
I don't know what causes it, which is what's turning me crazy.
How can I provide you guys with feedback next time it happens? I don't really have much of anything else installed: KDEPIM/PI suite, qpe-filemanager, qpe-alarmclock, that's about it (that runs permanaently, anyway).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=65347\"][{POST_SNAPBACK}][/a][/div]

I had a similar issue and discovered that my SD card information was corrupted.
After re-format the SD card every returned to normal.