Greetings. Make sure you read the "NOTES" section at the end of this file. It has important information that you will almost certainly need! These files are binary packages of the components needed to run an experimental build of the mozilla brower, for the BSD/OS v4.0.1 or BSD/OS v4.1 operating system. You MUST have a modern GTK/GDK library installation to run this experimental version of the browser. You can get a binary copy of these required libraries at the site mentioned later in this file. (Due to changes in the system supplied C++ compiler between BSD/OS 4.0.1 and 4.1, you WILL NOT be able to run a BSD/OS 4.0.1 compiled version of the browser under BSD/OS 4.1. I have switched to building the milestone snapshots on a BSD/OS 4.1 based system. Currently, I am able to build the milestone releases on both BSD/OS v4.1 and v4.0.1. At some point in the not too distant future, I will probably stop building them on BSD/OS v4.0.1. A note of this change will be made at that time, in this file. I have changed the names for some of the files to reflect this versioning information.) To unpack and use these binaries, you will need to retrieve several of the tar files from the a FTP server. One such FTP server is: ftp://ftp.eng.us.uu.net/lidl/mozilla/ Files that have a "i386-pc-bsdi4.0.1" in their names are binaries for BSD/OS v4.0.1 (intel based) machines. This will be the "MACHINE+OS" field in the filenames. Files that have a "i386-pc-bsdi4.1" in their names are binaries for BSD/OS v4.1 (intel based) machines. This will be the "MACHINE+OS" field in the filenames. The files you will need to get: gtk-MACHINE+OS.tar.gz -- GTK/GDK/glib libraries that are needed XXX-MACHINE+OS.tar.gz -- tarball of the mozilla distribution For the XXX in the above filenames: - M13 is the Milestone 13 build. - M14 is the Milestone 14 build. - M15 is the Milestone 15 build. You will need MORE THAN 30MB of free disk space (plus whatever storage is required for the .tar.gz files) to fully unpack the files. To use these packages, you will need to unpack them all, probably as root. Here's an example of how to do this for a 4.0.1 machine: First, unpack the gtk libraries: cd /usr/local gzcat < gtk-i386-pc-bsdi4.0.1.tar.gz | tar xvf - ldconfig The 'ldconfig' will force the system to recognize new libraries that have been installed into /usr/local/lib. (If you have removed the entry for /usr/local/lib from /etc/ld.so.conf for some reason, you'll want to put it back before running 'ldconfig'.) gzcat < XXX-i386-pc-bsdi4.0.1.tar.gz | tar xvf - To run the binary, you will need to do the following things: 1) cd into the bin directory that was unpacked: cd bin 2) run the "./mozilla" program I will hopefully have the chance to update these binaries occasionally, as time permits. If you find a bug, please visit http://bugzilla.mozilla.org and read their guidelines for submitting good bug reports. I am not able to provide much, if any, support for these snapshots. However, I would like to know if you have success (or not) running these binaries. Remember, this is not even BETA software, with no warranty implied or offered. If if crashes your machine, deletes your files or makes you owe back taxes, that's your problem, not mine. Best of luck. -Kurt (lidl@pix.net preferred for mail about Mozilla) NOTE 1: Some people have reported problems trying out this software on a not completely patched 4.0.1 machine. It works OK for me, but I have all the patches applied to the systems where I am using the pthreads support in my libc.so. I have copied over a current libc.so from my machine, which you should be able to stick into the lib directory that gets unpacked, and I think the browser will pick up that copy of libc.so in preference to the normal libc.so on the machine. This file is called libc.so-i386-pc-bsdi4.0.1.gz. Note 2: If you want the sources to the glib/gtk/gdk libraries that were used to build those libraries, look in the gtk.src.tar.gz file located on the FTP server. You should be able to rebuild the libraries from those sources, should you desire to do so. Note 3: Several people have reported problems due to their system having too low a default value for the system's vm.maxmapentries sysctl value. By changing their system's value for vm.maxmapentires to 512, they were able to get this software to work. The vm.maxmapentries value is related to the number of pages that you can mmap() at once, and as the system malloc() as of BSD/OS 4.X uses mmap(), there is a correspondence between the number of things you can malloc() on the system and the number of things you can mmap()! At any rate, if you want to change a machine's vm.maxmapentries value, run the following command as root on your machine: # sysctl -w vm.maxmapentries=512 Note 4: This software seems to work OK on BSD/OS v4.1, patch with the first 8 patches (M410-001 through M410-008). It's always a good idea to keep your system fully patched. In general, a fully patched BSD/OS system is the primary developement environment that I use to build Mozilla on and would expect the fewest problems on that platform.