My Updated Beta3, for whoever wants it
My Updated Beta3, for whoever wants it
May 11 2008, 10:08 AM
Joined: 3-December 06
Member No.: 13,063
Last updated: 13 may 2008
fixes by default (located in the default "backup" file that the system is restored from):
These changes you can see / replace in backups/backup*.tar.gz (can't remember the name right now, but it's only one file)
note: for the .tar file, check section 'The upgrade/fix all-in-one'
* image files open with gpicview
* mc is now able to open .ipk files on enter key
* /usr/bin/mbsession - can't remember what i've fixed there ...
* startx - added '-kb -screen 480x640@270'
* /etc/X11/kb - added usb.xmodmap (most of the things do work ...)
* /etc/X11/kb - userdefined.xmodmap - F1-F10 support, Insert key support, some other fixes - see it closer
* /etc/apm/scripts.d/hwclock fixes suspend/resume problems with clock setup
* /etc/mplayer - best setup (my opinion) for playing with mplayer in console
* /etc/pcmcia/ide.opts - this is a strictly setup like mine - /dev/hda3 points to /storage here
* /etc/rc.d/rc.sysinit ... can't remember what I've fixed here
* /etc/sysconfig/clamshell/* - adds support to switch wallpaper in ROX with /home/root/rox_wallpaper_landscape and /home/root/rox_wallpaper_portrait ( simple text files which contains path to images )
* /etc/fstab - strictly set up for my hdd setup - do not use if your's is not like mine ( or change to your preference )
scripts in /usr/local/bin ( also installed with the backup file mentioned above ):
* backup.sh - allows you to make full backups of all directories that you might need, in a specific location - PLEASE EDIT BEFORE USE!!!
* build_prepare and build_prepare_compat - development scripts
* change_wallpaper - this is for ROX desktop
* cleanup_some_space - removes some doc files
* cpu1, cpu2, cpu3, cpu4, cpu5, cpu6 - underclocks/overclocks the cpu (SL-C3200 tested ONLY. might work on SL-C3X00, but not for others - please check the values inside)
* distcc_use_home - development script
* dt - the right way to synchronize your date and preserve it correctly. Check sync server inside, if you don't like Bulgarian one
* duh - the same as 'du -hacs'
* lt_set and lt_unset - sets and unsets timezone - this is needed for correct operation of 'dt' script. CHECK CONTENTS and change to your timezone.
* make2 and make3 - development scripts
* mp - script that will switch to 624mhz, play the file you want and then go back to 416mhz. Use under console for best results! It will play greatly encoded files in 640x480. Check my script for making such files.
* reb - okay, this is cleaner way to reboot your system. If you don't clean /etc/mtab , you might end up with some non-working X terminal screens. But if you reboot with 'reb' - everything is perfect
* s - suspend the machine (if used in console/x console) - actually equivalent to 'sync ; date ; apm ; apm --suspend' - sync, show some info and suspend, but it's faster for me to type 's'
* search_remote - useful script to search for packages
* socklist - borrowed from slackware - better way to show what's listening on your machine
* zstore.sh - okay, this one is actually VERY powerfull, if you use it correctly. I suggest that you clean it up from my stuff, and then add your stuff. The idea is to backup ONLY WHAT YOU WANT from your Z machine, not everything. The resulting backup file is stored (right now) in /mnt/card/backups/backup_stored_files.tar.gz and later used in the install procedure. So, the idea is after you setup zaurus the final way you want - run 'zstore.sh' (of course, edit it first!) and it will backup ONLY the settings/files that you want. If you do this, the first time it might take you some more time, but the next time you add something, it will be really fast. Using this script, it's really quite fast for me to restore in clean system from plain beta3 to _exactly_ what I've setup before the reinstallation. It's worth checking it.
Here's how I do it (more info to follow):
My HDD setup is this:
/dev/hda1 points to /mnt/ide - place for additionally installed application. This is by DEFAULT.
/dev/hda2 is swap file or some experimental partition
/dev/hda3 points to /storage - a place where I store everything that's mp3s or videos or devel files
beware that some system files might not work correctly if this is not the way your system is set up.
To have more space in /tmp, create directory in /storage ( /dev/hda3 ) named 'tmp' ( /storage/tmp ), it will be used in install procedure to link it to /tmp
I will explain, according to my setup. Whenever appropriate - please check and edit the target /dev/hda* or /dev/whatever and target locations.
The upgrade/fix all-in-one
1. Download this archive:
and unpack it in /mnt/card or wherever you want. If you use different location, don't forget to edit install/functions and replace the paths with the appropriate ones.
2. Edit files according to your settings ( if needed ) AND check the installed files:
a ) GENERIC settings: /mnt/card/install/functions - these are for target locations. Note that by default ipkg will not install in / - because it can easily go short on space, but on the secondary location ( /mnt/ide by default ). This can easily be changed by editing /etc/ipkg.conf later.
b ) PLEASE, examine /mnt/card/install/fixes/* files and if needed - replace or remove parts of them, to suit your installation and/or preference. Specially fix_other scripts needs a lot of changes or things to be removed. I've left some of mine for reference.
c ) edit /mnt/card/install/install_packages_upgrade and check the removed packages section. Normally there's a good reason for them to be removed, so you can leave them as-is.
d ) Check the files that are processed. they are named packages_upgrade, packages_required, packages_development, packages_custom_root, packages_custom_additional. While you can edit freely *custom* directory contents, beware that _upgrade, _required might be essential for correct system installation/upgrade. Files from packages_custom_additional will go to the specified secondary location. packages_custom_root will go to / .
e ) I suggest, after editing the files, store them somewhere safe.
3. cd to /mnt/card/install/
./install script basically runs these 4 scripts:
so, if you don't want any of them - just comment it out.
In order to install the updates/required upgrades and additional packages, run
It will remove some files, install the required ones, upgrade the newer, and then add packages from *custom* directories. You should check to see if there are things that you don't need, inside. I copied my setup, so you can just remove files, not add Of course, you're free to add whatever packages you need additionally.
for development ( -devel ) packages installation, run
I use this script to convert movies on my slackware box for playing under console in pdaX b3
usage is like this:
zencoder /path/to/movie.avi /path/to/output.avi [/path/to/subtitle.sub|srt]
You need working mplayer with codecs that can handle opening the file you want.
Best playback expirience you will get if you use my mplayer.conf setup and the script 'mp' located in /usr/local/bin/ . Beware that it overclocks the machine to 624mhz (tested on SL-C3200 - might be different on others). Althought everyone says it's dangerous to do this, I've played more than 150 whole movies like this, without _any_ problem so far, and my Z is working still
This should cover what I wanted to say in general, I will add more info if needed, or when I have it, or when I fix bug. Hope you enjoy painless updated beta3 setup, as I do.
Cross compilation setup
It should be noticed that I use Slackware -current, but the setup is compatible with any distro ( It should be ). You may need to install distcc server, don't know - with Slackware it comes preinstalled.
Download this archive:
Unpack it somewhere ( it contains subdir cross/ ) and symlink this cross to /opt/cross, like this
ln -s /storage/devel/cross /opt/cross
Okay. When I need distcc running, I execute (normal user, not root) this shell script:
It basically contains only the following:
PATH=/opt/cross/arm/3.4.6-xscale-softvfp/bin:$PATH nice -19 distccd -j 2 --daemon -a 192.168.3.10
What it does is to setup path to cross compiler before the normal path to compiler and execute nice ( no need to get all the cpu for your desktop ) which executes distccd with 2 threads in daemon mode and will accept requests for IP 192.168.3.10 ( That's my Zaurus ). Refer to distccd documentation for more parameters, those are mine.
When you execute it, distccd listens and basically, your box is ready to accept connections. Note: the cross compiler might be outdated in terms of header files and whatsoever. But I've compiled SO much programs without _any_ problem, so I don't consider it a major thing. However, if something fails in crosscompilation, it will be built natively automatically.
download and extract somewhere where you have space, this archive:
I personally extract it in /storage/devel/ and do
ln -s /storage/devel/native /opt/native
I have this in /etc/profile: (note that my custom built setup updates /etc/profile with this code already, it's here for anyone who wants to use onboard (and cross) compilation of programs:
###### devel env
export DISTCC_HOSTS="192.168.129.1 localhost"
My /usr/local/bin/distcc_use_home contains (change the IP address to whatever you like):
export DISTCC_HOSTS="192.168.3.1 localhost"
echo "Use 'exit' to exit"
Ok, so - my zaurus have 192.168.3.10 as IP and my box's IP is 192.168.3.1 - it's easy to understand, that those are my values - you need to change them if your setup differs.
If you want to compile something, you need to execute this shell script _before_ starting compilation.
Compiling ... autotools based programs
That's the easiest thing to compile. I personally use the following script for this:
or the more compatible one:
the one have FLAGS="-mcpu=xscale -mtune=iwmmxt -O3 -fomit-frame-pointer -fno-common"
the other have FLAGS="-O2"
it's up to you to choose which one to use. I personally prefer more optimized one. In _some_ cases, the compilation may fail with very strange problems. Try make distclean and use the second one. May not fix it, but you can try.
If the compilation is okay, you will have your package pseudo-installed in $PWD/package directory.
Making package out of a directory
First, cd to $PWD/package/ or whatever your directory is. Then create directory named CONTROL and put a file inside, named control. In my case the full path to the file would be /storage/devel/build/program-1.0.1/package/CONTROL/control
It should contain something like this (those are the minimal required fields):
Description: some text here
You can also add scripts inside CONTROL directory, named postinst, postrm, preinst, prerm - via them you can control whether to start/stop a service before/after install or removal.
Ok, so it's up to you to strip the binaries ( build_prepare tries to make install-strip, but this may fail sometimes ). It's up to you also to remove all doc, man pages, as your zaurus have limited space.
I normally also copy package dir to package-dev and separate the files - /usr/bin/include and /usr/lib/pkgconfig and /usr/lib/*.a and such files go into -devel package, all others are in the normal one.
Then, go to the directory that contains package/ directory, in my example - /storage/devel/build/program-1.0.1/ and type:
If you don't have errors in your CONTROL/control file, you will get the ipk in the same directory with a small notice about it.
1. If you encounter PATH_MAX undefined, edit config.h and add
#define PATH_MAX 65535
I fixed this while ago in the native compilation setup, but I lost it , and had to restore from backup, so I never fixed it again
more will follow soon ...
May 15 2008, 07:15 PM
Joined: 5-January 07
Member No.: 13,705
Very google resouce, a lot of api need to be compiled again since gtk code has been upgrade.
|Lo-Fi Version||Time is now: 13th December 2013 - 11:59 AM|