Firefox 8.0
<h2>Windows</h2>
<h6>Operating Systems</h6>
Mac OS X 10.5.8 Now Available Can open a gazillion tabs without it crashing Cons Nothing really Summary Updated on Oct 13, Cool firefox for mac 10. If you want to see just how many security threats have to be fixed on a regular basis by Mozilla, check out the. According to the posted Firefox 16.0 System Requirements, Mac OSX 10.5 is still supported on Intel platforms, so that's a bit surprising.Since Firefox and SeaMonkey share the same Mozilla Core code (a.k.a. 'Gecko'), which usually dictates the system requirements, I wouldn't expect differences between the supported platforms of either application. Firefox on Mac OS X 10.5.8? I was wondering, and this may be a dumb question, if I can run Firefox on my Mac? I used to have it on my PC but always thought it was a PC application and not compatible with a Mac. If I can download it, what version should I download? Does it run well on a Mac? I do remember having issues.
- Windows 2000
- Windows XP
- Windows Server 2003
- Windows Vista
- Windows 7
Please note that while the 32-bit and 64-bit versions of Windows Vistaand Windows 7 can be used to run Firefox 8, only 32-bit builds of Firefox 8 aresupported at this time.
<h6>Recommended Hardware</h6>
- Pentium 4 or newer processor that supports SSE2
- 512MB of RAM
- 200MB of hard drive space
<h2>Mac</h2>
<h6>Operating Systems</h6>
- Mac OS X 10.5
- Mac OS X 10.6
- Mac OS X 10.7
<h6>Recommended Hardware</h6>
- Macintosh computer with an Intel x86 processor
- 512 MB of RAM
- 200 MB hard drive space
<h2>Linux</h2>
<h6>Software Requirements</h6>
Please note that Linux distributors may provide packagesfor your distribution which have different requirements.
- Firefox will not run at all without the following libraries or packages:
- GTK+ 2.10 or higher
- GLib 2.12 or higher
- Pango 1.14 or higher
- X.Org 1.0 or higher (1.7 or higher is recommended)
- libstdc++ 4.3 or higher
- For optimal functionality, we recommend the following libraries or packages:
- NetworkManager 0.7 or higher
- DBus 1.0 or higher
- HAL 0.5.8 or higher
- GNOME 2.16 or higher
< ReferencePlatforms
![Download Download](/uploads/1/2/6/4/126425554/465221014.png)
- 1Reference Image Info
- 1.1Updating the images
- 2Things done for you
- 2.16Buildbot
- 3Manual setup after cloning
- 4Puppet packages
We now have one image for xserve and one for minis:
You must do everything in the 'Manual steps after cloning' section after a machine is freshly imaged, still.
Now that the reference image for minis and xserves has Puppet on it new images do not need to taken every time something is added, new machines that receive the current image will automatically update themselves when deployed.
Updating the images
As mentioned above, these images do not need to be updated every time a change happens. However, it is good to update them from time to time, to speed up new slave deployment, and make it cleanlier in general. Here's how to do it:
Updating the mini image
bm-mini-build-ref.build.mozilla.org
We've got a mac mini which is permanently dedicated to being a ref image. It will be kept up to date by Puppet. Therefore, the only thing to do to update it is file an IT bug requesting a new image be taken. Make sure you ask them to use the new image for all future deployments.
We've got a mac mini which is permanently dedicated to being a ref image. It will be kept up to date by Puppet. Therefore, the only thing to do to update it is file an IT bug requesting a new image be taken. Make sure you ask them to use the new image for all future deployments.
Updating the xserve image
Unlike the mini, we do not have a machine dedicated to being a ref image, which makes this process a little more involved.
First, choose an xserve and shut down the Buildbot process on it. Next, some prep work:
Once all of the above is done, it's time to file a bug and wait.
Once the new image has been taken the xserve needs to be returned to its original place:
Now, reboot and Puppet will sync up the ssh keys and start Buildbot for you.
Darwin Version
These are the kernel versions we're starting with:
Intel: Darwin bm-xserve16.build.mozilla.org 9.2.0 Darwin Kernel Version 9.2.0: Tue Feb 5 16:13:22 PST 2008; root:xnu-1228.3.13~1/RELEASE_I386 i386
This is 10.5.2, up to date on 28/Feb/2008.
Initial Setup and Account Creation
- Change the resolution to 1024 x 768, 60 Hz, Millions of Colours, under System Preferences->Displays (this is changed later)
- Change the password for the administrator user to the standard build system root password.
- Create a new admin-equiv account for the cltbld user using the standard build password.
- Under System Preferences->Sharing->Screen Sharing->Computer Settings change the VNC screen control password to the standard build password. NOTE: your VNC session will drop when you do this. You'll need to reconnect with the new password.
- If the hostname is wrong, e.g. unused-*, use
sudo scutil --set HostName new.hostname.mozilla.org
to fix it. NOTE: you'll need to restart the machine for this to fully take effect. - Under System Preferences->Software Update, turn off automatic update checking.
- Using the Workgroup Manager, open the Preferences pane for the cltbld user. Under Software Update, set Manage: to Always, and set the Software Update server to use: as http://bm-xserve01.build.mozilla.org:8088/ - NEED TO FIGURE THIS OUT
Ref platform packages
Helpfully, OS X doesn't have CVS out of the box, so retrieve the Mac reference platform packages on another machine:
This should yield 4 files with md5sums:
Then transfer them to the machine you are setting up. (We switch to xcode 3.1 later)
Installing Xcode
- Mount the Xcode disk image, and begin installing the XcodeTools.mpkg.
- A standard install is fine (we don't need 10.3.9 support or WebObjects).
Now we have cvs.
Installing CHUD
- Mount the CHUD disk image, install the CHUD.mpkg
Installing MacPorts
- Install the MacPorts package from ref platform version 1.6-10.5; ignore the error about the postflight script
- Unpack the macports-10.5 tarball of source packages and move them into place:
- Next, you need to install a series of ports, all of which should already be contained (and the right version) in the macports tarball you just unpacked. If you see the port command hitting the network at all (-->Fetching...) while installing the needed ports, something has gone wrong.
There's a bug with sqlite3 where it fails to compile, depending on what was built before it, so we build it and it's deps first. The second command builds everything else. Afterwards, running
port installed
should show only the 21 ports listed below:ssh
scp the cltbld and appropriate role keys over directly from a machine that already has them installed. In .ssh, make sure the cltbld keys are called cltbld* and not id_dsa*, then symlink
This is temporary to get hold of the standard .profile (we should move that file to public cvs).
ENV setup
...at which point you'll probably want to restart your shell to use the new .profile.
switch to role key
In ~/.ssh,
or substitute ffxbld for whatever key is appropriate for what you will be building.
chown scripts
NOTE: This section is now taken care of by puppet (bug 528189).
After you've created your initial /builds/tinderbox directory structure, checkout and build the following tools that are also required for changing permissions while packaging on Macs:
Establish initial ssh connections and accept keys
Execute the following simple ssh calls to connect to the ftp server (stage), symbol server (if different from ftp), and update server so that the various pieces of the build can be uploaded automatically by the build scripts when needed:
Mail config
NB: Postfix config is tinderbox client specific, all the buildbot information goes over a socket to the master and is posted to the tinderbox server from there.
You'll need to update the postfix config to make sure that
myhostname
is set correctly and that large messages can be sent. The tail of /etc/postfix/main.cf
should look similar to:You'll then want to restart postfix to pick up the changes.
Also make sure that Mail.app is installed.
ntp config
Tp2 config
NB: This is deprecated by talos.
Set up the server by doing to Application->Server->Server Preferences. Disable File Sharing, iCal, and iChat. Then go to Web, and uncheck 'Enable group Wikis', 'Webmail', and 'User blogs'; set 'Home Page' to 'Server Home Page'.
To setup Tp2:
nagios
- Copy over the appropriate package from bm-admin01, either nrpe-darwin-i386.tar.gz or nrpe-darwin-powerpc.tar.gz depending on your platform.
- Create a nagios user and group
- Unpack the package in /usr/local. Eg,
- Edit/checkout nrpe.cfg. The one in mozilla/tools/nagios/nrpe-mac.cfg may be useful.
- Run enablenrpe to turn it on
Ask IT to setup the suite of checks.
Buildbot
Make directories
Install Python 2.5.2
Python 2.5 doesn't compile on 10.5, and we'll take the latest version rather than the 2.5.1 that ships with the OS.
Installing Zope Interface
Installing Twisted
Final Configuration
Add the appropriate paths to the Buildbot user's .bash_profile
Misc loose ends
We used to do the following manually, but this change is now done on the ref image, to reduce manual setup.
- Change screen resolution to 1280 x 1024, Millions of colours
- Set the background to a Solid Colour (better for slower network connections)
- Remove crud from doc, leaving Finder, System Preferences, Terminal, Activity Monitor (not essential, just tidier)
- have /usr/local/bin/autoconf-2.13 symlink to /opt/local/bin/autoconf-2.13
Update to Xcode 3.1
- Check out the XCode disk image from cvs (will need to adjust ~/.ssh/id_dsa)
- Check sha1 sum is right
- Mount the Xcode disk image, and begin installing the XcodeTools.mpkg.
- A standard install is fine (we don't need 10.3.9 support or WebObjects).
Installing Mercurial 1.2.1
Copy fonts from another Mac
Set dock size
(until a fix is in for bug 470420)
Symlink for autoconf
Due to calling in RepackFactory to command=['bash', '-c', 'autoconf-2.13'] to fix this we have to add a symlink to autoconf213
'Install' 7z
We need 7zip for the l10n verification step of releases
Setup for verification on staging
Move ~/.ssh to ~/ssh_prod, and scp staging keys in from a staging box. Patch master config to allow new clone to connect and get jobs.
Setup buildbot start on boot
- Ensure the the correct user and slave directory are set in the script (cltbld and /builds/slave by default)
From VNC:
- Make sure the resolution is set to 1280x1024. (this is not in the xserve ref image)
- System Prefs -> Accounts -> Login Options
- Set 'Automatic Login' to 'cltbld', enter the password when prompted.
Reboot (after setting up the slave, see following step in this doc). NB: The LaunchAgent will try to start buildbot every 10 minutes, be wary of leaving a working buildbot.tac in place during setup
(See bug 428124 for details.)
Puppet client installation
After the next reboot Puppet will be starting on boot.
Post-puppet packages
Download Mozilla For Windows 10
If you used the new ref images then you should only need to do all the bullet points and sections below
- Set the hostname if required (IT probably did this, but see above if not)
- Double check that the display resolution is 1280 x 1024
- Double check that Bluetooth Setup Assistant is turned off (System Preferences -> Bluetooth -> Advanced -> uncheck 'Open Setup Assistant...')
- Verify that screen saver is off - check bug 562629
- Verify that spotlight is disabled
- * For a try builder, be sure to wipe all ssh keys and copy over trybld keys from another try builder
Add slave(s) to configuration files
The following files need to be updated with new slaves (note that the production Buildbot config is explicitly not updated here, it will be done later):
- puppet-manifests/site-production.pp (or site-staging.pp for slaves that will be in staging permanently).
- For a permanent staging slave - edit /Library/LaunchDaemons/com.reductivelabs.puppet.plist to staging-puppet
Once your patches have landed, you need to update the following checkouts:
- On staging-master:
- On production-puppet (or staging-puppet if you updated site-staging.pp):
- If a machine has been recloned/replaced then you also do this as root@production-puppet
Setup buildbot slave
The buildbot.tac file will automatically be generated to send the slave to the correct staging master (staging-master or sm-staging-try-master).
Run the slave through staging
see ReleaseEngineering:BuildSlaveSetup
Disable bluetooth
TODO: Document this.
See bug 570843.
Mozilla Firefox 5.0 Download
Retrieved from 'https://wiki.mozilla.org/index.php?title=ReferencePlatforms/Mac-10.5&oldid=343643'