Easiest way of upgrading or updating Mediawiki version on Debian/Ubuntu/etc.

So far this is the easiest way I have found to update Mediawiki. This presumes SSH access.   Back up your database and files first!  
wget https://releases.wikimedia.org/mediawiki/1.31/mediawiki-1.31.1.tar.gz
(if going for another version, replace with the appropriate link)
tar -xvzf mediawiki-1.31.1.tar.gz
cp -rf mediawiki-1.31.1/* /var/www/YOURSITE
If your sites are stored elsewhere, replaces /var/www/YOURSITE with whatever the path name is. Copy with the rf flags forces over-write and copies recursively.
Visit https://yoursitename/mw-config/ in your browser
Follow the instructions from there – you will need the upgrade key from your existing LocalSettings.php file, which should be found in your existing Wiki directory via:

cat LocalSettings.php | grep -A 2 key


liberal christian dating site

Forgotten what it was you last updated, or want to check what someone else has been updating? There’s a log file for that, and it’s located at:  
  To view it, run:  
less /var/log/apt/history.log
  Looking for an older logfile? They’re kept, too. To see the other log files available, view the directory using ls:  
ls /var/log/apt/
  It should look something like:  
history.log  history.log.1.gz  history.log.2.gz  history.log.3.gz  history.log.4.gz  term.log  term.log.1.gz  term.log.2.gz  term.log.3.gz  term.log.4.gz
  One further note – This will show the most recent things done with apt, not just upgrades.

date night pictures

catholic singles omaha
  Fedora, unlike Ubuntu with apt-get, uses yum to update it’s software. Run the following as root (either by logging in as root or using su in front of the command):  
yum update
  You will see a list of the updated packages and a confirmation at the end. On our test system it looks like this:  
Transaction Summary ============================================ Install   3 Packages (+  6 Dependent packages) Upgrade  97 Packages (+157 Dependent packages) Total size: 332 M Total download size: 275 M Is this ok [y/d/N]:
  If you are happy with the listed upgrades and/or new installations hit ‘y’ to update!

How to update the firmware of a HP tape drive – StorageWorks Ultrium 448

  The quickest and easiest way of updating the firmware is through HP’s Library and Tape Tools – at the time of writing it is available here:  
  Click on the “Link to free download” link to acquire the software. Assuming you have the correct drivers for your setup (SCSI/SAS/etc card), the tape drive is connected and powered on you will be able to detect it using LTT. Click on “Firmware” at the top:   hp-firmware-01 Now click “Get Files From Web”, then select your tape drive/firmware and click Download:   hp-firmware-02   Once it has download, exit that screen and click on Firmware again:   hp-firmware-03 You should be looking at the Update Firmware tab by default, if not select it and you should see the above screen. To update the firmware now (once checking that all of the numbers look as they should!) click Start Update. You will see the following warning message:   hp-firmware-04   After that, you should see:   hp-firmware-05 We find that the Time Remaining is usually reasonably pessimistic and that it generally finishes early. Once the update is complete you will get the following popup:   hp-firmware-06   Once LTT comes back to life, your update should be completed and you can check it through the Health tab, which should pop up the Report Viewer:   hp-firmware-07 There’s plenty of info in there so it’s well worth checking to see how much life is remaining on the drive.   Done!

Changing or Updating the time zone in Ubuntu Server

  There are quite a few reasons you may find that you need to change your time zone – for example, if you’re using a pre-made image for a virtual machine you may find that the default timezone is not set to your country. You can change the time manually, though there is a quick and easy way:  
sudo dpkg-reconfigure tzdata  
This reconfigures the tzdata (timezone data) package and runs you through a series of prompts asking which country/city you live in, and updates the time accordingly.   You can check the current system time with:  
  to verify that it worked!

Ubuntu: How to update PHP’s timezone

  We came across this one recently when setting up a Zabbix server, where the installation would not proceed until the PHP timezone was set. This is quite straightforward – using your favourite editor edit:  
  Look for the Module Settings section or search for:  
  (in vi /date.timezone should get you there). Uncomment the line by removing the leading ; and then add in your desired timezone. For Sydney it would look like:  
[Date] ; Defines the default timezone used by the date functions ; http://php.net/date.timezone date.timezone = UTC+10
  Change UTC+10 to your desired timezone, save the file and restart Apache:  
sudo service apache2 restart

Asus motherboard BIOS update error: CAP file not recognised EFI bios!

  If you see the above error – and you’re selecting what you’re sure is the proper CAP file – chances are you’re trying to use a USB disk formatted to NTFS rather than FAT32. Frustratingly, the error message for a corrupt/non-CAP file is the same as the error message you get when you’re trying to use an NTFS-formatted drive, which Asus Ez Flash 2 is not compatible with.   The solution is simply to use a FAT32-formatted drive. If that doesn’t work double check that your file hasn’t corrupted during the download and is complete, and the right BIOS for the board.

esxcli: Update/patch produces “Could not download from depot” error

In ESXi 5.1 you can patch using the following command:  
esxcli software vib install -d /path/to/patch.zip
  If you’re getting the following result (using ESXi510-20121001.zip as an example):  
 [MetadataDownloadError] Could not download from depot at zip:/var/log/vmware/ESXi510-201210001.zip?index.xml, skipping ((‘zip:/var/log/vmware/ESXi510-201210001.zip?index.xml’, ”, “Error extracting index.xml from /var/log/vmware/ESXi510-201210001.zip: [Errno 2] No such file or directory: ‘/var/log/vmware/ESXi510-201210001.zip'”)) url = zip:/var/log/vmware/ESXi510-201210001.zip?index.xml Please refer to the log file for more details.
  This results from not putting in the absolute path to the .zip – e.g. using:  
esxcli software vib install -d ESXi510-20121001.zip  
rather than:  
esxcli software vib install -d /vmfs/volumes/datastore/ESXi510-20121001.zip
  Putting in the full path to the .zip file should resolve that error.

Asus P8Z77-V Deluxe not recognising IBM M1015

  We had a customer who installed a M1015 into their workstation and it wouldn’t recognise the card at all during the boot process; the board was still on the shipping BIOS 0906, and the issue was resolved by updating to the most current BIOS (1401 at the time of writing). After updating the BIOS the card was recognised during the boot process as normal.