InfoTechPedia - User contributions [en]

MediaWiki:Pivot.css

2021-04-14T20:57:05Z

TomHutchison:

/* Column-output Home Page */
.column-output {
-webkit-columns: 16em 2;
-moz-columns: 16em 2;
columns: 16em 2;
margin:0 1.5em
}
/* Icons */
#n-Contact-us a:before {
content: "\f003";
}
/* Custom colors - top bar*/
.tab-bar {
background: #2f3f4f
}
/* style the labels */
ul.side-nav label {
background: #2f3f4f;
color: #fff;
padding: .25em .5em;
}
/* sidebar background color and font-family */
body {
background-color: #bad6d6;
font-family: -apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";
}
.side-nav {
font-family: -apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";
}
/* Pre tags */
pre {
background: darkslategrey;
color: #D1F8D1;
padding: 10px 10px;
line-height: 1.5em;
margin: 1em 3em 1em 4em;
font-family: Consolas,"Liberation Mono",Courier,monospace;
}
/* Pre tags in MediaWiki Namespace */
.ns-8 pre {
background: #efefee;
margin: 0;
color: #483d8b;
}
/* Pre tags plain */
pre.code {
color: #555;
background: #f8f8f8;
border: 1px solid #dfdfdf;
margin: 1em 0;
}
/* Image classes */
.center {
text-align: center;
}
img {
margin-bottom: 1em;
}
/* Nested UL and OL */
.mw-content-ltr ul>li>ul {
margin: .25em 0 .25em 1.25em;
}
.mw-content-ltr ol>li>ol {
margin: .25em 0 .25em 1.25em;
}
.mw-content-ltr ol>li>ol {
list-style-type: upper-alpha;
}
.mw-content-ltr ol>li>ol>li>ol {
list-style-type: lower-alpha;
}
.mw-content-ltr ol>li>ol>li>ol>li>ol {
list-style-type: lower-roman;
}
.mw-content-ltr ol>li>ol>li>ol>li>ol>li>ol {
list-style-type: decimal;
}
dl, dd, dl dd {
margin-bottom: 0;
}
/* Override MW legacy.module for all skins styling of ul and ol */
.mw-content-ltr ul,
.mw-content-rtl .mw-content-ltr ul {
/* @noflip */
margin: 0em 0 0.5em 3.2em;
padding: 0;
}

.mw-content-rtl ul,
.mw-content-ltr .mw-content-rtl ul {
/* @noflip */
margin: 0em 3.2em 0 0.5em;
padding: 0;
}

.mw-content-ltr ol,
.mw-content-rtl .mw-content-ltr ol {
/* @noflip */
margin: 0em 0 0.5em 3.2em;
padding: 0;
}

.mw-content-rtl ol,
.mw-content-ltr .mw-content-rtl ol {
/* @noflip */
margin: 0em 3.2em 0 0.5em;
padding: 0;
}

/* @noflip */
.mw-content-ltr dd,
.mw-content-rtl .mw-content-ltr dd {
margin-left: 1.6em;
margin-right: 0;
}

/* @noflip */
.mw-content-rtl dd,
.mw-content-ltr .mw-content-rtl dd {
margin-right: 1.6em;
margin-left: 0;
}
/* Notice Boxes */
.dablink {
font-style: italic;
padding-bottom: 0.5em;
padding-left: 0;
margin-bottom: 0.5em;
color: #555;
border-bottom: 1px solid #ccc;
}

div[class*="panel radius notice-"] {
-webkit-box-shadow: 3px 3px 5px 0px rgba(0,0,0,0.75);
-moz-box-shadow: 3px 3px 5px 0px rgba(0,0,0,0.75);
box-shadow: 3px 3px 5px 0px rgba(0,0,0,0.75);
}

.panel.radius.notice-note {
background: lightgray;
padding: 5px 10px 0px 10px;
}

.panel.radius.notice-warning {
background: rgba(255, 0, 0, 0.85);
padding: 5px 10px 0px 10px;
color: white;
}

.panel.radius.notice-hint {
background: mediumseagreen;
padding: 5px 10px 0px 10px;
color: #f9f9f9;
}

.panel.radius.notice-see-also {
background: lightgoldenrodyellow;
padding: 5px 10px 0px 10px;
color: #191970;
}

.panel.radius.notice-info {
background: aliceblue;
padding: 5px 10px 0px 10px;
color: #191970;
}

.notice {
margin: .5em 0;
}

.notice-title {
font-weight: bold;
border-bottom:1px solid;
width: 100%;
font-size: 18px;
}

p.notice {
width: 100%;
font-size: 16px;
}

/* Category links */
#mw-normal-catlinks li {
background: #2f3f4f;
margin: 5px;
padding: 4px;
}

#catlinks ul li a {
color: #f9f9f9;
}

/* Screen width styles 60em and under */

@media screen and (max-width: 60em) {
.notice-icon {
font-size: .65em;
}
}

@media screen and (max-width: 60em) {
pre {
margin-left:0px;
margin-right:0px;
}
}

Main Page

2021-04-14T20:38:32Z

TomHutchison: /* Contents */

<div class="row">
<div class="large-12 columns>
[[File:SiteHeader.png]]
</div>
</div>
== Contents ==
<div class="column-output">
<dpl>
namespace=
ordermethod=category,title
headingmode=h4
mode=unordered
</dpl>
</div>
{{keywords|Info Tech,Information,Techonology,System Admin,Developer,Support,Linux,Git,CLI}}
{{description|A scratchpad of everything to do with being a System's Admin, Developer or an IT Support Specialist.}}

Category:Virtualmin

2020-11-03T17:02:43Z

TomHutchison:

[[File:Virtualmin-logo.svg|right|100px]]

Pages in the <code>{{PAGENAME}}</code> category.
{{-}}
[[Category:All Categories]]{{ogmeta}}

Template:Ogmeta

2020-11-03T17:01:38Z

TomHutchison:

<includeonly>{{#set:
|Meta element og-image={{filepath:{{#sub:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}|5}}}}
|Meta element og-image-type={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}} |?MIME type }}
|Meta element og-image-width={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}#_EXIFDATA |?Width }}
|Meta element og-image-height={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}#_EXIFDATA |?Height }}
}}</includeonly><noinclude>
This template automatically adds the og meta tags, og:image, og:image-type, og:image-height, and og:image-width.
<pre>
{{#set:
|Meta element og-image={{filepath:{{#sub:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}|5}}}}
|Meta element og-image-type={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}} |?MIME type }}
|Meta element og-image-width={{#show:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}#_EXIFDATA|?Width }}
|Meta element og-image-height={{#show:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}#_EXIFDATA|?Height }}
}}
</pre>
</noinclude>

Category:PHP

2020-11-03T17:00:08Z

TomHutchison:

[[File:PHP-logo.svg|right|100px]]

Pages in the <code>{{PAGENAME}}</code> category.
{{-}}
[[Category:All Categories]]{{ogmeta}}

Property:Meta element og-image-height

2020-11-03T16:30:23Z

TomHutchison:

[[Has type::Text]]

Property:Meta element og-image-width

2020-11-03T16:29:56Z

TomHutchison:

[[Has type::Text]]

Property:Has meta description

2020-11-03T16:26:08Z

TomHutchison: Created page with "Has type::Text"

[[Has type::Text]]

Template:Ogmeta

2020-11-03T16:19:01Z

TomHutchison:

<includeonly>{{#set:
|Meta element og-image=https:{{filepath:{{#sub:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}|5}}}}
|Meta element og-image-type={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}} |?MIME type }}
|Meta element og-image-width={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}#_EXIFDATA |?Width }}
|Meta element og-image-height={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}#_EXIFDATA |?Height }}
}}</includeonly><noinclude>
This template automatically adds the og meta tags, og:image, og:image-type, og:image-height, and og:image-width.
<pre>
{{#set:
|Meta element og-image=https:{{filepath:{{#sub:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}|5}}}}
|Meta element og-image-type={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}} |?MIME type }}
|Meta element og-image-width={{#show:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}#_EXIFDATA|?Width }}
|Meta element og-image-height={{#show:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}#_EXIFDATA|?Height }}
}}
</pre>
</noinclude>

Template:Ogmeta

2020-11-03T16:10:42Z

TomHutchison:

<includeonly>{{#set:
|Meta element og-image=https:{{filepath:{{#sub:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}|5}}}}
|Meta element og-image-type={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}} |?MIME type }}
|Meta element og-image-width={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}#_EXIFDATA |?Width }}
|Meta element og-image-height={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}#_EXIFDATA |?Height }}
}}</includeonly><noinclude>
This template automatically adds the og meta tags, og:image, og:image-type, og:image-height, and og:image-width.
<pre>
{{#set:
|Meta element og-image=https:{{filepath:{{#sub:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}|5}}}}
|Meta element og-image-type={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}} |?MIME type }}
|Meta element og-image-width={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}#_EXIFDATA |?Width }}
|Meta element og-image-height={{#show: {{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}#_EXIFDATA |?Height }}
}}
</pre>
</noinclude>

Pure Linux iMac Boot

2020-11-03T16:07:13Z

TomHutchison: /* Zeroing the Hard Drive */

I recently bought a Mac Mini 6,1 (late 2012 model) to replace the giant tower PC
I was using as a household server. Oddly enough for an Apple product, out of all
the small-form-factor PCs around with a decent amount of power, it was by far
the cheapest.
When I installed Ubuntu Saucy (13.10), I was initially faced with an unbootable
system, which I eventually got to work. When Ubunty Trusty (14.04) came out I
was hoping things would go better. Sure enough, there was a <code>+mac</code> variant
installer available (buried behind several download pages), but ths used legacy
BIOS booting. The non <code>+mac</code> variant simply gave me an unbootable system again.
This wasn’t good enough for me! I used [http://glandium.org/blog/?p=2830 Mike Hommey’s Debian EFI boot instructions],
and adapted them for recent Ubuntu systems. The result was a Mac Mini that would
boot Ubuntu Trusty in pure EFI mode, with no rEFInd and no OS X, and with an
Ubuntu entry in the Mac’s bootloader menu.
Thank you Mike. They were excellent instructions.
Note that I’ve only applied this process to my situation: single-booting Ubuntu
Trusty (14.04.1) on a Mac Mini 6,1. If you’re knowledgeable enough, you should
be able to use this to dual/multi-boot, or boot other Linux distros, or use
other Mac devices. But I haven’t tried any of that myself, so be prepared for
some surprises.

==Why EFI? Why Not rEFInd?==
Because I can. Because of aesthetics. Because I’m an engineer, and if there’s a
simpler way to make something work, I’ll try to find it.
If the legacy BIOS boot mode works for you, and you don’t want any fuss, use it!
If rEFInd works for you, use it! These instructions are for people who just want
to try it out, or perhaps for installer developers who want a starting point for
a more general process.
Are there any benefits at all then? Sure:
<ul>
<li>I couldn’t actually figure out how to install rEFInd without keeping OS X
installed, which meant giving over about 100GB of my 500GB drive to it. No
thanks.</li>
<li>The Mac bootloader firmware seems to boot about 30s faster.</li>
<li>You have access to various EFI-related utilities.</li><li>You can make yourself a pretty Ubuntu entry in the bootloader menu!</li>
</ul>

==Equipment==

* A Mac that uses EFI to boot. It is helpful, but not essential, to have OS X still installed.
* Two USB sticks, with at least 2GB capacity. One is for the OS X recovery disk, the other is for the Ubuntu installer.
* The Ubuntu 14.04 installer ISO image (both desktop and server installers should work, but I only tried the server installer). Do not use the <code>+mac</code> variant.
* Another machine, preferably also Ubuntu, from which you can
** make the installer USB drive,
** SSH into the new system, and
** ask for help if things go wrong.
* A monitor, keyboard and mouse (ie. don’t try for a headless install).</li><li>An internet connection for the new machine (preferably ethernet, not WiFi).

==Disclaimer. Warning. Caution. Caveat.==

{{warning|This process will wipe OS X and any other data you have on the machine. All of it! That’s the whole point. Make backups.}}

I’m pretty sure this won’t brick a machine (ie. break it irrepairably). But only pretty sure. If all else fails, you should always be able to reinstall OS X from a recovery disk. But there might be subtle differences between machines that make it harder for you to back out if something goes wrong. Therefore, I really don’t recommend trying this unless you’re reasonably proficient with this sort of thing in general. So as a parallel to the equipment list above, here’s a checklist of concepts that shouldn’t phase you:
<ul>
<li>You should absolutely be comfortable working from a command line.</li><li>You should not be afraid to work from a GRUB command line.</li><li>You should understand how to identify disks on a live/installer system (ie.
be able to answer the question “is the internal hard drive <code>/dev/sda</code> or <code>/dev/sdb</code>?”)</li>
<li>You should understand disk partitioning (not the low level details, just that the general idea is).</li><li>You should understand that when I use device names or numbers, such as <code>/dev/sda1</code> or <code>UUID=whatever</code>, these may be different for your system.</li>
</ul>

Finally, even though this process only takes a couple of hours, it took me
weeks to figure it out. This means that if your system is different, you might
require a lot more time too. So you should be doing this on a machine that you
can afford to have out of action for a couple of days.

==Preliminary Work in OS X==

{{hint|If you still have OS X installed, this is a good time to create a [http://support.apple.com/kb/HT4848 recovery disk]. And also make those backups
I told you to make.}}

===That Stupid Startup Noise===

There is only one part of this process that requires starting from scratch if you forget it, and it’s this: turning off that stupid noise that the Mac makes
upon booting. Despite what you may read, on some systems it is impossible to adjust without OS X installed. Impossible. No, <code>nvram</code> utilities won’t work. No, <code>efibootmgr</code> won’t work. No, the OS X recovery disk won’t help. There is some extra, magical, inaccessible bit of state somewhere that keeps the stupid thing alive that you can only control via a full install of OS X. So if you still have OS X installed, or you don’t mind reinstalling it just for this, do this:
<ul><li>Open the System Settings.</li><li>Click on Sound.</li><li>Click on Output.</li><li>Select Internal Speakers (“Type: Built-in”).</li><li>Drag the slider all the way to the left.</li></ul><figure><a href="/trinkets/MacOSXVolume.png"><img alt="OS X Internal Speaker Volume" src="/trinkets/MacOSXVolume.png" width="670" height="489"></a></figure>
If you’re a real optimist, you could open a terminal, run <code>nvram -p</code> and note
the value for <code>SystemAudioVolume</code>. Mine was this:
<pre>
SystemAudioVolume %80
</pre>

==How To Boot From USB==

This isn’t really a step, but it’s complicated enough to warrant its own section. You may need to refer to this a few times. The trick to booting from USB on Macs is to hold down the <code>option</code> key while you press the power button to turn it on. Don’t have an <code>option</code> key? Use <code>alt</code>
instead. Note: I found that on some keyboards (eg. my non-bluetooth wireless keyboard), I needed to repeatedly tap the key until I saw the boot menu. Sometimes it was hit-and-miss, but it never took more than three power cycles to get it.

Doing this should bring up the boot menu. Note that when I say “boot menu,” I don’t mean the GRUB/syslinux boot menu. I mean the Mac’s internal bootloader: it has a grey background, a drop-down menu at the bottom for configuring your internet connection, and a horizontal list of OS logos and descriptions.

[[File:MacBootloader.jpg|center|800|I forgot to take a picture, so this is actually from a completely different machine than mine (hence the blurring of the hard drive label). But your Mac bootloader should look pretty much the same.]]

If your USB drive is bootable, you’ll see one or two orange icons with the USB logo on them. For the Ubuntu installer they will probably be labelled “Windows” (just because) and “EFI boot”. You can use <code>→</code>/<code>←</code> and <code>enter</code> to select the thing to boot, or just click with the mouse.

==Starting the Installer==
Create the installer USB drive using Startup Disk Creator. You shouldn’t need extra (persistent) space on it. I used the server edition installer because I use my machine as a server. You might want to use the desktop installer. These instructions should work for either. Please leave a comment below if there are any discrepancies.

Insert the installer USB drive, and power on the machine while holding <code>option</code>/<code>alt</code>, as per the <a href="#boot-from-usb">boot from USB instructions</a>. The grey screen of the bootloader might stay there for a while (perhaps 30s to a
minute) before it loads the available boot options. You should see the following options:

* Macintosh HD (unless you’ve already wiped OS X)
* Windows
*EFI boot

Use the arrow keys to select EFI boot and press <code>enter</code>.

==Installing Ubuntu==
For the server installer, you will be presented with a GRUB bootloader menu:

[[File:Server-grub.png|center]]

The desktop installer might not show you this; you might instead see a prettier menu with the option to '''Try Ubuntu''' or '''Install Ubuntu'''. In either case, select the '''Install''' option.

You can breeze through the first few steps of the installer, the ones that just configure the installer environment and basic setup. However, you should '''stop when you get to partitioning.'''

Specifically, the steps you can treat as normal are:
*Language/region/keyboard layout.
*Hardware detection, disk detection, loading installer components.
*Network detection and configuration.
*Hostname and user account setup.
*Home directory encryption (in case it wasn’t clear, you can enable this if you like, it won’t affect anything here).</li><li>Time, date and time zone.

Around this point, you should be expecting to see the partitioning menu. This is
where it can get a bit tricky.

==Partitioning==

As far as I can tell, you should actually be able to let this step go as per the defaults too. But I’ll tell you exactly what I did, just in case the defaults don’t allow you to follow the remaining steps.

I got to a screen titled '''Partition disks''', which presented me with these
options:
*Guided - use entire disk
*Guided - use entire disk and set up LVM
*Guided - use entire disk and set up encrypted LVM
*Manual

I selected '''Guided - use entire disk'''. When asked which disk I wanted to partition, I selected the only one available:
<pre>
SCSI (0,0,0) (sda) - 500.1 GB ATA APPLE HDD HTS545
</pre>

Yours might be different, but it should be obvious which it is. Incidentally, this might be a good point to note down whether the installer sees your disk as <code>sda</code> or some other <code>sdX</code>. When you proceed, you’ll be shown the changes that will be made:
<pre>
The partition tables of the following devices are changed:
SCSI (0,0,0) (sda)

The following partitions are going to be formatted:
partition #1 of SCSI (0,0,0) (sda) as EFIboot
partition #2 of SCSI (0,0,0) (sda) as ext4
partition #3 of SCSI (0,0,0) (sda) as swap
</pre>

'''This is the important thing:''' at the end of this step, there must be a partition that is listed as <code>EFIboot</code>. As long as that exists, you should be fine to continue. The others probably don’t matter. If you see any partition labelled anything like '''BIOS legacy boot''' or '''bios-grub''', you might have missed a vital part of these instructions and are using the <code>+mac</code> variant of the installer.

Because I was doing this over and over again, I occasionally encountered a problem where the installer would be unable to format the EFIboot partition. If
this happens, try <a href="#zero-the-drive">zeroing the drive</a> and start over. You may now proceed with the rest of the installation as usual. If you’re
installing a server, I strongly recommend installing the '''OpenSSH server''' task so that you can do the next few steps remotely.
Congratulations! You now have an unbootable Ubuntu system! Hooray!

==The Manual Boot==

Your new system is unbootable, but don’t despair! We’ll repair it and make it better than it would have been!
Firstly, when you reboot/power on your Mac, here’s what will probably happen: you will see the grey screen of the Mac bootloader for about 30s, and then a
gently flashing folder with a <code>?</code> inside. If you insert the installer USB now, it should boot. If not, try holding the power button to force the power off, and then follow the <a href="#boot-from-usb">USB booting instructions</a> to bring it up. If you’re using the desktop installer, hold the shift key to bring up the GRUB bootloader menu. For the server installer, it should just come up automatically.

To be absolutely clear, for both the server and the desktop installer, you want to bring up a menu that looks like this:

[[File:Server-grub.png"|center]]

The entries may be different, but that’s what the GRUB menu looks like. Don’t select any of the entries; instead, press <code>C</code> to bring up the GRUB console. Now you should be looking at a GRUB console:
<pre>
grub>
</pre>

===Finding Your Installation’s Drive===

At the GRUB console, do:
<pre>
grub> ls
(memdisk) (hd0) (hd0,msdos) (hd1) (hd2) (hd2,gpt3) (hd2,gpt2) (hd2,gpt1)
</pre>

You may not get exactly the same results as this, but you’ll have some similar options. You want to look for your new installation, not the installer/live system. I suggest finding a partition with your new user’s home directory on it:
<pre>
grub> ls (hd2,gpt2)/home
jason/
</pre>

Keep trying this pattern until you find it.

===Finding Your Installation’s Boot Partition===

The result from the last step has two parts: <code>(hdX,gptY)</code>. You need to keep the
<code>hdX</code> part, but go through all the <code>gptY</code> options looking for a <code>/boot/grub</code>
directory:
<pre>
grub> ls (hd2,gpt1)/boot/grub
error: file `/boot/grub' not found.</code>
</pre>

Nope, not that one.
<pre>
grub> ls (hd2,gpt2)/boot/grub
unicode.pf2 [...] grub.cfg
</pre>

Found it!
Now you want to set this as your root for further commands:
<pre>
grub> set root=(hd2,gpt2)
</pre>

===Figuring Out the Boot Command===

I found that the only way to boot properly was to use the UUID of the drive (ie. no shortcuts with <code>/dev/sdaX</code>!) - so let’s get that:
<pre>
grub> ls -l (hd2,gpt2)
Partition hd2,gpt2: Filesystem type ext* 〈...snip...〉 UUID e86c20b9-83e1-447d-a3be-d1ddaad6c4c6 - Partition start at [...]
</pre>

Note the UUID string! Yours will be different. Now tell GRUB where Linux is:
<pre>
grub> linux /boot/vmlinuz〈...tab here!...〉.efi.signed root=UUID=〈the UUID from above〉
</pre>

The GRUB console can do <code>tab</code> completion, so if you just type out the <code>vmlinuz</code> part and hit <code>tab</code>, then hit <code>.</code> and <code>tab</code> again… you won’t have to type out the whole filename. But do make sure the <code>.efi.signed</code> bit is there! And yes, you will have to type out that whole UUID.

Now set the <code>initrd</code> (initial RAM disk):
<pre>
grub> initrd /boot/initrd〈...tab here!...〉
</pre>

===Booting===
Type:
<pre>
grub> boot
</pre>

You should find yourself booted into your installation!

==Fixing the EFI Partition==
So why is the system unbootable? The problem is that the Mac bootloader expects
the EFI partition to be formatted as HFS+, the typical Mac filesystem. It also
expects certain files to be present. The Ubuntu installer actually formats it as
VFAT and doesn’t create the files that are necessary for booting on a Mac.

===Install Extra Packages===

The first thing you’ll need to do is add my PPA and install some extra utilities. Fire up a command line and enter:

<pre>
$ sudo add-apt-repository ppa:detly/mactel-utils
[...]
Utilities for Intel based Macs (eg. recent MacBooks, Mac Minis). Includes a
fan control (macfanctld) and the HFS "bless" utility.
More info:
https://launchpad.net/~detly/+archive/ubuntu/mactel-utils
Press [ENTER] to continue or ctrl-c to cancel adding it
</pre><ref>[https://launchpad.net/~detly/+archive/ubuntu/mactel-utils Reference]</ref>

Press <code>enter</code> to add the PPA. Then update your package list and install the
necessary utilities:

<pre>
$ sudo apt-get update
$ sudo apt-get install mactel-boot hfsprogs gdisk grub-efi-amd64
</pre>

===Reformatting the EFI Partition===
Firstly, make sure you’ve actually got an EFI partition. Run <code>mount</code> to get a list of mounted filesystems, and look for anything mounted at <code>/boot/efi</code>:
<pre>
$ mount
[...]
/dev/sda1 on /boot/efi type vfat (rw)
[...]
</pre>

For me, it’s <code>/dev/sda1</code>. If there is no entry for <code>/boot/efi</code> (<code>/boot</code> by
itself doesn’t count), you are probably running in legacy BIOS mode. So, let’s unmount it:

<pre>
$ sudo umount /dev/sda1
</pre>

We now use <code>gdisk</code> to delete the VFAT partition and create an HFS+ one. <code>gdisk</code>
is interactive, and doesn’t write changes to the disk until you tell it to, so
don’t panic if you make a mistake.

<pre>
$ sudo gdisk /dev/sda
GPT fdisk (gdisk) version 0.8.8

Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: present

Found valid GPT with hybrid MBR; using GPT.

Command (? for help):
</pre>

You must see the <code>GPT: present</code> line. The <code>MBR: hybrid</code> line is optional. If you’re not using a <code>GPT</code> (GUID partition table)… well, I don’t know what kind of machine you’re using there. Print the partition table and confirm that the first partition has type <code>EF00</code>:

<pre>
Command (? for help): p
Disk /dev/sda: 976773168 sectors, 465.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 717BD65E-A514-4FD9-A4A7-1BE01C2F31E0
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4077 sectors (2.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 2048 194559 94.0 MiB EF00
2 194560 968574975 461.8 GiB 8300
3 968574976 976771071 3.9 GiB 8200
</pre>

The other details aren’t really important, but we definitely expect the device
associated with <code>/boot/efi</code> (from the output of <code>mount</code>) to match the numbering
here (ie. if <code>/boot/efi</code> was <code>/dev/sda1</code>, the <code>EF00</code> partition should be #1).
Now we delete that <code>EF00</code> partition:
<pre>
Command (? for help): d
Partition number (1-3): 1
</pre>

…and create a new HFS+ one in its place:

<pre>
Command (? for help): n
Partition number (1-128, default 1): 1
</pre>

Just press <code>enter</code> for the first and last sector options:

<pre>
First sector (34-976773134, default = 2048) or {+-}size{KMGTP}:
Last sector (2048-194559, default = 194559) or {+-}size{KMGTP}:
</pre>

…but enter <code>AF00</code> for the filesystem code:

<pre>
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): AF00
Changed type of partition to 'Apple HFS/HFS+'
</pre>

Now we’re ready to write the changes. Use the <code>p</code> command to double-check your
changes, and then <code>w</code> to write:

<pre>
Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/sda.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
</pre>

Now we have an unformatted HFS+ partition. We can format it with:
<pre>
$ sudo mkfs.hfsplus /dev/sda1 -v Ubuntu
Initialized /dev/sda1 as a 94 MB HFS Plus volume
</pre>

===Updating the Filesystem Table===

For system partitions (eg. <code>/</code>, <code>/boot</code>, <code>/boot/efi</code>) Ubuntu uses the UUID
(universally unique identifier) of a disk partition to mount it (rather than
the device node, eg. <code>/dev/sda1</code>). This means we need to update <code>/etc/fstab</code>:<pre>$ sudoedit /etc/fstab
</pre>
This will launch the <code>nano</code> text editor. Look the two lines that
refers to <code>/boot/efi</code>:<pre># /boot/efi was on /dev/sda1 during installation
UUID=C59D-1B30 /boot/efi vfat defaults 0 1
</pre>
Use <code>↓</code>/<code>↑</code> to position the cursor at the start of these lines and hit
<code>ctrl</code>+<code>K</code> to delete them. Run this to add the necessary entries:<pre>$ sudo bash -c 'echo $(blkid -o export -s UUID /dev/sda1) /boot/efi auto defaults 0 0 >> /etc/fstab'
</pre>
Test it out by remounting <code>/boot/efi</code>:<pre>$ sudo mount /boot/efi
</pre>
Note that you shouldn’t use extra options here. If it doesn’t work from that
command alone, it means your <code>/etc/fstab</code> entry is wrong.

===Installing GRUB===

Now we’ll reinstall GRUB so it can use the newly formatted HFS+ partition for
its EFI data. Since Mike Hommey wrote his instructions, GRUB has actually been
updated to work with HFS+ partitions, so there’s no need to hack the installer
any more (good thing too, since it’s now a C program, not a shell script).
First, create the necessary directory on the EFI partition:

<pre>
$ sudo mkdir -p "/boot/efi/EFI/$(lsb_release -ds)/"
</pre>

The <code>$(lsb_release -ds)</code> part automatically produces a label for the
distribution like <code>Ubuntu 14.04.1 LTS</code>.
Now, there’s a <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716927#20">bug in GRUB</a>
that means that on HFS+ it requires a file named <code>mach_kernel</code> to exist in a
particular place before it runs. In fact, it’s really the Mac bootloader that
requires this file, but GRUB seems to look for it in the wrong place and refuses
to run if it’s not there, so we need to create it twice:

<pre>
$ sudo bash -c 'echo "This file is required for booting" > "/boot/efi/EFI/$(lsb_release -ds)/mach_kernel"'
$ sudo bash -c 'echo "This file is required for booting" > /boot/efi/mach_kernel'
</pre>

Now we need to install GRUB, and we need to be a bit explicit about where it
should put its files:

<pre>
$ sudo grub-install --target x86_64-efi --boot-directory=/boot --efi-directory=/boot/efi --bootloader-id="$(lsb_release -ds)"
</pre>

The final step is to “bless” the bootloader code, so that the Mac bootloader
will boot it:

<pre>
$ sudo hfs-bless "/boot/efi/EFI/$(lsb_release -ds)/System/Library/CoreServices/boot.efi"
</pre>

The system should now be bootable!

You should reboot your system (<code>sudo reboot</code>) to see if it boots straight into your new Ubuntu installation. '''Note''' that there will still be that delay at the Mac boot screen (the light grey one). But the system will still boot, and we can get rid of that delay later. You might also like to <a href="#boot-from-usb">bring up the boot menu</a> to see what the Ubuntu entry looks like. At this point it should have the correct label (“Ubuntu
14.04.1 LTS…”), but the icon will be a plain grey hard drive.

===Replacing the Bootloader Icon===

Simply do:

<pre>
$ sudo apt-get install mactel-boot-logo
$ sudo cp /usr/share/mactel-boot-logo/ubuntu.icns /boot/efi/.VolumeIcon.icns
</pre>

Now when you reboot, if you bring up the Mac boot menu, you should see the familiar Ubuntu logo!<figure><a href="/trinkets/MacBootloaderUbuntu.jpg"><img src="/trinkets/MacBootloaderUbuntu.jpg" width="400" height="438"></a></figure>

==Removing the Boot Delay==

The boot delay is caused by a couple of things:

* The bootloader firmware might still have old entries in it, with the default set to something that doesn’t exist.</li><li>The bootloader itself has a timeout that can be changed, and it defaults to 5s.

This can be managed with the <code>efibootmgr</code> utility. If you run it without arguments, you’ll see all the settings I mentioned:

<pre>
$ sudo efibootmgr
BootCurrent: 0000
Timeout: 5 seconds
BootOrder: 0080
Boot0000* ubuntu
Boot0001* Ubuntu 14.04.1 LTS
Boot0080* Mac OS X
BootFFFF*
</pre>

In my case, the timeout was set to 5s, the default boot was set to an entry that no longer exists, and there was still an old OS X entry. This will get rid of the built-in timeout:

<pre>
$ sudo efibootmgr -t 0
</pre>

This gets rid of the extra entries (note that your numbers might be different!):

<pre>
$ sudo efibootmgr -b 0000 -B
$ sudo efibootmgr -b 0080 -B
</pre>

This sets the default entry (again, the number here might be different for you):

<pre>
$ sudo efibootmgr -o 0001
</pre>

…and now, when you reboot, it should be significantly faster.

{{note|When I initially searched for a fix for this, I read a lot of posts claiming that using the OS X recovery disk to bless the partition would do the trick. But as far as I can tell, this has no effect, so don’t panic if you don’t have a recovery disk.|subject=Note #1}}

{{note|I am not talking about the usual GRUB delay here. In theory, this can be changed by editing <code>/etc/default/grub</code> and setting all the timeout values to <code>0</code>. However, [https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1273764 bug #1273764] stops this from working, so use [https://gist.github.com/LeahCim/9332432 LeahCim’s extra GRUB scripts] to fix it.|subject=Note #2}}

==You’re Done!==

That should be it. You should now have a system that boots straight into Ubuntu,
no delay, giving you access to all the EFI goodness.

==Zeroing the Hard Drive==

This is not a step! It’s just here in case things go so wrong you don’t know what to do. Hopefully you won’t need this bit, but you may find that the installer partitioner isn’t working as expected, or maybe you’ve tried a load of different things and you want a clean slate. You could reinstall OS X, but that takes time and data. In most cases, I found that zeroing out the start of the drive was enough to get rid of any bad state
that was interfering with the process.

Boot off the Ubuntu installer USB drive, but don’t select Install Ubuntu. Instead, use the Rescue a broken system option.
Go through the keyboard detection, but don’t bother with anything else — as soon as you see a <code><go back></code> option, use that to get to the rescue menu. Select Execute a shell in the installer environment, and you’ll be presented with a prompt that’s just a <code>#</code> (ie. root access). Assuming your hard drive is <code>/dev/sda</code>, this command will zero out the first GB of the hard drive. That should cover the master boot record (MBR), the GUID partition table (GPT), and any other magic that interferes with partition/OS detection:

<pre>
# dd if=/dev/zero of=/dev/sda bs=16M count=64
</pre>

It will not touch the Mac’s internal bootloader firmware, nor will it reset any nvram variables such as the internal speaker volume.

[[Category:Linux]][[Category:iMac]][[Category:EFI Boot]]{{keywords|linux,iMac,boot,partitioning,EFI boot}}{{description}}{{ogmeta}}

Property:Meta element og-image-width

2020-11-03T16:06:46Z

TomHutchison: Created page with "Has type::Number"

[[Has type::Number]]

Property:Meta element og-image-height

2020-11-03T16:06:15Z

TomHutchison: Created page with "Has type::Number"

[[Has type::Number]]

Pure Linux iMac Boot

2020-11-03T16:02:49Z

TomHutchison: /* Zeroing the Hard Drive */

Category:Linux

2020-11-03T16:01:59Z

TomHutchison:

[[File:Tux.png|right|100px]]

{{cat}}{{ogmeta}}
{{-}}
[[Category:All Categories]]

Template:Ogmeta

2020-11-03T16:01:37Z

TomHutchison: Created page with "<includeonly>{{#set: |Meta element og-image=https:{{filepath:{{#sub:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}|5}}}} |Meta el..."

<includeonly>{{#set:
|Meta element og-image=https:{{filepath:{{#sub:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}|5}}}}
|Meta element og-image-type={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?MIME type }}
|Meta element og-image-width={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}#_EXIFDATA |?Width }}
|Meta element og-image-height={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}#_EXIFDATA |?Height }}
}}</includeonly><noinclude>
This template automatically adds the og meta tags, og:image, og:image-type, og:image-height, and og:image-width.
<pre>
{{#set:
|Meta element og-image=https:{{filepath:{{#sub:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}|5}}}}
|Meta element og-image-type={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?MIME type }}
|Meta element og-image-width={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}#_EXIFDATA |?Width }}
|Meta element og-image-height={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}#_EXIFDATA |?Height }}
}}
</pre>
</noinclude>

Category:Linux

2020-11-03T15:58:33Z

TomHutchison:

[[File:Tux.png|right|100px]]

{{cat}}{{#set:
|Meta element og-image=https:{{filepath:{{#sub:{{#explode:<MANY>{{#show: {{FULLPAGENAME}} |?Attachment_link|format=array}}|<MANY>|1}}|5}}}}
|Meta element og-image-type={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?MIME type }}
|Meta element og-image-width={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}#_EXIFDATA |?Width }}
|Meta element og-image-height={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}#_EXIFDATA |?Height }}
}}
{{-}}
[[Category:All Categories]]

Category:Linux

2020-11-03T15:02:50Z

TomHutchison:

[[File:Tux.png|right|100px]]

{{cat}}{{#set:
|Meta element og-image=https:{{filepath:{{#sub:{{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}|5}}}}
|Meta element og-image-type={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?MIME type }}
|Meta element og-image-width={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}#_EXIFDATA |?Width }}
|Meta element og-image-height={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}#_EXIFDATA |?Height }}
}}
{{-}}

[[Category:All Categories]]

Category:Linux

2020-11-03T15:02:28Z

TomHutchison:

[[File:Tux.png|right|100px]]
{{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?MIME type|link=none}}{{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}
{{#show: File:Tux.png#_EXIFDATA |?Width }}{{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}#_EXIFDATA |?Height }}
{{cat}}{{#set:
|Meta element og-image=https:{{filepath:{{#sub:{{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}|5}}}}
|Meta element og-image-type={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?MIME type }}
|Meta element og-image-width={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}#_EXIFDATA |?Width }}
|Meta element og-image-height={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}#_EXIFDATA |?Height }}
}}
{{-}}

[[Category:All Categories]]

Property:Meta element og-image

2020-11-03T14:24:08Z

TomHutchison: Created page with "Has type::Text"

[[Has type::Text]]

Property:Meta element og-image-type

2020-11-03T14:22:39Z

TomHutchison: Created page with "Has type::Text"

[[Has type::Text]]

Category:Linux

2020-11-03T14:21:40Z

TomHutchison: Undo revision 182 by TomHutchison (talk)

[[File:Tux.png|right|100px]]

{{cat}}{{#set:
|Meta element og-image=https:{{filepath:{{#sub:{{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}|5}}}}
|Meta element og-image-type={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?MIME type }}
|Meta element og-image-width={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?Width }}
|Meta element og-image-height={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?Height }}
}}
{{-}}

[[Category:All Categories]]

Category:Linux

2020-11-03T14:19:52Z

TomHutchison:

[[File:Tux.png|right|100px]]

{{cat}}{{#set:
|Has meta tag image=https:{{filepath:{{#sub:{{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}|5}}}}
|Meta element og-image-type={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?MIME type }}
|Meta element og-image-width={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?Width }}
|Meta element og-image-height={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?Height }}
}}
{{-}}

[[Category:All Categories]]

Category:Linux

2020-11-03T14:15:31Z

TomHutchison:

[[File:Tux.png|right|100px]]

{{cat}}{{#set:
|Meta element og-image=https:{{filepath:{{#sub:{{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }}|5}}}}
|Meta element og-image-type={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?MIME type }}
|Meta element og-image-width={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?Width }}
|Meta element og-image-height={{#show: {{#show: {{FULLPAGENAME}} |?Attachment_link|link=none }} |?Height }}
}}
{{-}}

[[Category:All Categories]]

Category:Linux

2020-11-03T13:40:55Z

TomHutchison:

[[File:Tux.png|right|100px]]

{{cat}}
{{-}}
[[Category:All Categories]]

File:Tux.png

2020-11-03T13:37:26Z

TomHutchison:

== Summary ==
Identity image for Linux logo.

File:Tux.png

2020-11-03T13:37:05Z

TomHutchison: Identity image for Linux logo

== Summary ==
Identity image for Linux logo

File:Virtualmin-logo.svg

2020-11-03T13:14:33Z

TomHutchison:

== Summary ==
Minimal Logo use for identity of organization.

Patch Command

2020-08-15T12:56:13Z

TomHutchison:

This page shows how to use the patch command in CLI

Example using MediaWiki patch files to update minor versions of MediaWiki.

A small patch file is usually made available for a minor version upgrade. Manually download and extract the patch file from the dumps site or follow the directions with wget below. Patches are incremental, you can not skip a version.

:cd to your main MediaWiki directory (the one with LocalSettings.php)
:Download the patch file and gunzip it. <code>gunzip mediawiki-x.xx.x.patch.gz</code>
:Use patch <code>-p1 --dry-run</code> to check what will be changed (e.g., <code>patch -p1 --dry-run -i mediawiki-x.xx.x.patch</code>)
:If all is well, run patch again without --dry-run.
:Check your Special:Version and you should see the new version number in place.

[[Category:Linux]][[Category:Command Line]]

Category:All Categories

2020-08-15T03:22:25Z

TomHutchison:

This is the top level of all categories.

{{note|This category should only contain sub categories.}}

Categories in the <code>{{PAGENAME}}</code> category. To add categories to this category, please add <code><nowiki>[[Category:</nowiki>{{PAGENAME}}<nowiki>]]</nowiki></code> to the bottom of a category page.
{{-}}

File:CLI.png

2020-08-15T03:21:45Z

TomHutchison:

Category:Command Line

2020-08-15T03:21:30Z

TomHutchison: Created page with "100px {{cat}} Category:All Categories"

[[File:CLI.png|right|100px]]

{{cat}}

[[Category:All Categories]]

Category:Linux

2020-08-15T03:19:01Z

TomHutchison:

[[File:Tux.svg|right|100px]]

{{cat}}
{{-}}
[[Category:All Categories]]

File:Virtualmin-logo.svg

2020-08-15T03:15:36Z

TomHutchison: Minimal Logo use for identity of organization

== Summary ==
Minimal Logo use for identity of organization

Category:Virtualmin

2020-08-15T03:12:04Z

TomHutchison: Created page with "100px Pages in the <code>{{PAGENAME}}</code> category. {{-}} Category:All Categories"

[[File:Virtualmin-logo.svg|right|100px]]

Pages in the <code>{{PAGENAME}}</code> category.
{{-}}
[[Category:All Categories]]

Category:PHP

2020-08-15T03:07:53Z

TomHutchison: Created page with "100px Pages in the <code>{{PAGENAME}}</code> category. {{-}} Category:All Categories"

[[File:PHP-logo.svg|right|100px]]

Pages in the <code>{{PAGENAME}}</code> category.
{{-}}
[[Category:All Categories]]

Install Different Version of PHP on Ubuntu

2020-08-15T03:04:36Z

TomHutchison:

You can install different versions of PHP on Ubuntu. This will also show how to install the versions and use them on Virtualmin for different virtual servers on a Virtualmin/Webmin install.

== Add the Repository ==
=== Ubuntu 16.06 ===
Use the following on the command line.
<pre>
sudo add-apt-repository ppa:ondrej/php
sudo apt-get update
</pre>

=== Ubuntu 18.04 ===
Use the following on the command line.
<pre>
sudo add-apt-repository ppa:ondrej/php
sudo apt update
</pre>

=== Additional Info ===

After the updates you can use <code>sudo apt-get upgrade</code> for Ubuntu 16.04 or <code>sudo apt upgrade</code> for Ubuntu 18.04. This should pull down the very latest version of PHP from the <code>ondrej/php</code> repository. Currently, as of this writing is PHP 7.4.

== Install Specific Versions & Modules ==
Right now I am using the following. You can substitute <code>7.3</code> or <code>7.2</code> for <code>7.4</code>. Just check the modules available per PHP version noted below.

Time to install.
=== Ubuntu 16.04 ===
<pre>
sudo apt-get install php7.4 php7.4-cli php7.4-common php7.4-cgi
</pre>

Then the following modules (these are the ones I generally install):
<pre>
sudo apt-get install php7.4-bcmath php7.4-bz2 php7.4-curl php7.4-dba php7.4-enchant php7.4-gd
php7.4-gmp php7.4-imap php7.4-interbase php7.4-intl php7.4-ldap php7.4-mbstring php7.4-mysql
php7.4-odbc php7.4-pgsql php7.4-pspell php7.4-snmp php7.4-soap php7.4-tidy php7.4-xml php7.4-xmlrpc
php7.4-xsl php7.4-zip
</pre>

=== Ubuntu 18.04 ===
<pre>
sudo apt install php7.4 php7.4-cli php7.4-common php7.4-cgi
</pre>

Then I add the following modules as a start:
<pre>
sudo apt install php7.4-bcmath php7.4-bz2 php7.4-curl php7.4-dba php7.4-enchant php7.4-gd
php7.4-gmp php7.4-imap php7.4-interbase php7.4-intl php7.4-ldap php7.4-mbstring php7.4-mysql
php7.4-odbc php7.4-pgsql php7.4-pspell php7.4-snmp php7.4-soap php7.4-tidy php7.4-xml php7.4-xmlrpc
php7.4-xsl php7.4-zip
</pre>

=== Version Check ===
Check your version. Usually, the highest version is available with:
<pre>
user@YourServer:~$ php -v
PHP 7.4.9 (cli) (built: Aug 7 2020 14:29:10) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.9, Copyright (c), by Zend Technologies
user@YourServer:~$ php7.3 -v
PHP 7.3.21-1+ubuntu16.04.1+deb.sury.org+1 (cli) (built: Aug 7 2020 14:43:42) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.21, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.21-1+ubuntu16.04.1+deb.sury.org+1, Copyright (c) 1999-2018, by Zend Technologies
user@YourServer:~$
</pre>

=== Adding Modules ===

Check what modules are installed.
<pre>
user@YourServer:~$ php7.4 -m
[PHP Modules]
apc
apcu
bcmath
bz2
calendar
Core
...truncated...
exif
fileinfo
filter
ftp
gd
gettext
gmp
hash
iconv
imagick
imap
interbase
intl
json
ldap
libxml
mbstring
mcrypt
mysqli
mysqlnd
...truncated...
xml
xmlreader
xmlrpc
xmlwriter
xsl
Zend OPcache
zip
zlib

[Zend Modules]
Zend OPcache

user@YourServer:~$
</pre>
Now check what modules are available in your apt-cache for the specific PHP version, 7.4 or 7.3 or 7.2, etc.
<pre>
user@YourServer:~$ sudo apt-cache search php7.4
php-amqp - AMQP extension for PHP
php-apcu - APC User Cache for PHP
php-geoip - GeoIP module for PHP
php-igbinary - igbinary PHP serializer
php-imagick - Provides a wrapper to the ImageMagick library
php-mongodb - MongoDB driver for PHP
php-msgpack - PHP extension for interfacing with MessagePack
php-oauth - OAuth 1.0 consumer and provider extension
php-redis - PHP extension for interfacing with Redis
...truncated...
php7.4-soap - SOAP module for PHP
php7.4-sqlite3 - SQLite3 module for PHP
php7.4-sybase - Sybase module for PHP
php7.4-tidy - tidy module for PHP
php7.4-xml - DOM, SimpleXML, XML, and XSL module for PHP
php7.4-xmlrpc - XMLRPC-EPI module for PHP
php7.4-xsl - XSL module for PHP (dummy)
php7.4-zip - Zip module for PHP
</pre>

Need a module? From the list what is available in your apt-cache:
<pre>
user@YourServer:~$ sudo apt-get install php7.4-tidy
</pre>

For Ubuntu 18.04
<pre>
user@YourServer:~$ sudo apt install php7.4-tidy
</pre>

Now you have multiple versions of PHP installed on your server.

== Virtualmin ==

If you are running Webmin w/Virtualmin it is pretty easy to make the versions available for specific virtual hosts (websites) on your Virtualmin Install. This pertains to the latest Webmin 1.954 w/Virtualmin 6.11.

*Log on to the Webmin admin <code><nowiki>https://yourserver.com:10000</nowiki></code>
*'''System Settings''' -> '''Re-check configuration'''
*All installed versions of PHP should be found.
*Manage each Virtual Server -> select the proper Virtual Server from Dropdown list at top of Navigation Menu, example, yourdomain.org, you want to manage.
*Then select '''Server Configuration''' -> '''PHP Versions'''
*Select the version of PHP for the Virtual Server. Then "Save Versions" button.

All the correct php.ini files and directories should be created in your <code>/home/{username}/</code> directory.

[[Category:Linux]][[Category:PHP]][[Category:Virtualmin]]

Install Different Version of PHP on Ubuntu

2020-08-15T03:03:42Z

TomHutchison: /* Virtualmin */

Install Different Version of PHP on Ubuntu

2020-08-15T03:02:48Z

TomHutchison: /* Virtualmin */

You can install different versions of PHP on Ubuntu. This will also show how to install the versions and use them on Virtualmin for different virtual servers on a Virtualmin/Webmin install.

== Add the Repository ==
=== Ubuntu 16.06 ===
Use the following on the command line.
<pre>
sudo add-apt-repository ppa:ondrej/php
sudo apt-get update
</pre>

=== Ubuntu 18.04 ===
Use the following on the command line.
<pre>
sudo add-apt-repository ppa:ondrej/php
sudo apt update
</pre>

=== Additional Info ===

After the updates you can use <code>sudo apt-get upgrade</code> for Ubuntu 16.04 or <code>sudo apt upgrade</code> for Ubuntu 18.04. This should pull down the very latest version of PHP from the <code>ondrej/php</code> repository. Currently, as of this writing is PHP 7.4.

== Install Specific Versions & Modules ==
Right now I am using the following. You can substitute <code>7.3</code> or <code>7.2</code> for <code>7.4</code>. Just check the modules available per PHP version noted below.

Time to install.
=== Ubuntu 16.04 ===
<pre>
sudo apt-get install php7.4 php7.4-cli php7.4-common php7.4-cgi
</pre>

Then the following modules (these are the ones I generally install):
<pre>
sudo apt-get install php7.4-bcmath php7.4-bz2 php7.4-curl php7.4-dba php7.4-enchant php7.4-gd
php7.4-gmp php7.4-imap php7.4-interbase php7.4-intl php7.4-ldap php7.4-mbstring php7.4-mysql
php7.4-odbc php7.4-pgsql php7.4-pspell php7.4-snmp php7.4-soap php7.4-tidy php7.4-xml php7.4-xmlrpc
php7.4-xsl php7.4-zip
</pre>

=== Ubuntu 18.04 ===
<pre>
sudo apt install php7.4 php7.4-cli php7.4-common php7.4-cgi
</pre>

Then I add the following modules as a start:
<pre>
sudo apt install php7.4-bcmath php7.4-bz2 php7.4-curl php7.4-dba php7.4-enchant php7.4-gd
php7.4-gmp php7.4-imap php7.4-interbase php7.4-intl php7.4-ldap php7.4-mbstring php7.4-mysql
php7.4-odbc php7.4-pgsql php7.4-pspell php7.4-snmp php7.4-soap php7.4-tidy php7.4-xml php7.4-xmlrpc
php7.4-xsl php7.4-zip
</pre>

=== Version Check ===
Check your version. Usually, the highest version is available with:
<pre>
user@YourServer:~$ php -v
PHP 7.4.9 (cli) (built: Aug 7 2020 14:29:10) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.9, Copyright (c), by Zend Technologies
user@YourServer:~$ php7.3 -v
PHP 7.3.21-1+ubuntu16.04.1+deb.sury.org+1 (cli) (built: Aug 7 2020 14:43:42) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.21, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.21-1+ubuntu16.04.1+deb.sury.org+1, Copyright (c) 1999-2018, by Zend Technologies
user@YourServer:~$
</pre>

=== Adding Modules ===

Check what modules are installed.
<pre>
user@YourServer:~$ php7.4 -m
[PHP Modules]
apc
apcu
bcmath
bz2
calendar
Core
...truncated...
exif
fileinfo
filter
ftp
gd
gettext
gmp
hash
iconv
imagick
imap
interbase
intl
json
ldap
libxml
mbstring
mcrypt
mysqli
mysqlnd
...truncated...
xml
xmlreader
xmlrpc
xmlwriter
xsl
Zend OPcache
zip
zlib

[Zend Modules]
Zend OPcache

user@YourServer:~$
</pre>
Now check what modules are available in your apt-cache for the specific PHP version, 7.4 or 7.3 or 7.2, etc.
<pre>
user@YourServer:~$ sudo apt-cache search php7.4
php-amqp - AMQP extension for PHP
php-apcu - APC User Cache for PHP
php-geoip - GeoIP module for PHP
php-igbinary - igbinary PHP serializer
php-imagick - Provides a wrapper to the ImageMagick library
php-mongodb - MongoDB driver for PHP
php-msgpack - PHP extension for interfacing with MessagePack
php-oauth - OAuth 1.0 consumer and provider extension
php-redis - PHP extension for interfacing with Redis
...truncated...
php7.4-soap - SOAP module for PHP
php7.4-sqlite3 - SQLite3 module for PHP
php7.4-sybase - Sybase module for PHP
php7.4-tidy - tidy module for PHP
php7.4-xml - DOM, SimpleXML, XML, and XSL module for PHP
php7.4-xmlrpc - XMLRPC-EPI module for PHP
php7.4-xsl - XSL module for PHP (dummy)
php7.4-zip - Zip module for PHP
</pre>

Need a module? From the list what is available in your apt-cache:
<pre>
user@YourServer:~$ sudo apt-get install php7.4-tidy
</pre>

For Ubuntu 18.04
<pre>
user@YourServer:~$ sudo apt install php7.4-tidy
</pre>

Now you have multiple versions of PHP installed on your server.

== Virtualmin ==

If you are running Webmin w/Virtualmin it is pretty easy to make the versions available for specific virtual hosts (websites) on your Virtualmin Install. This pertains to the latest Webmin 1.954 w/Virtualmin 6.11.

*Log on to the Webmin admin <code><nowiki>https://yourserver.com:10000</nowiki></code>
*'''System Settings''' -> '''Re-check configuration'''
*All installed versions of PHP should be found.
*Manage each Virtual Server -> select Virtual Server from Dropdown list at top of Navigation Menu, example, yourdomain.org
*Then select '''Server Configuration''' -> '''PHP Versions'''
*Select the version of PHP for the Virtual Server. Then "Save Versions" button.

All the correct php.ini files and directories should be created in your <code>/home/{username}/</code> directory.

Install Different Version of PHP on Ubuntu

2020-08-15T03:02:04Z

TomHutchison: /* Install Specific Versions & Modules */

You can install different versions of PHP on Ubuntu. This will also show how to install the versions and use them on Virtualmin for different virtual servers on a Virtualmin/Webmin install.

== Add the Repository ==
=== Ubuntu 16.06 ===
Use the following on the command line.
<pre>
sudo add-apt-repository ppa:ondrej/php
sudo apt-get update
</pre>

=== Ubuntu 18.04 ===
Use the following on the command line.
<pre>
sudo add-apt-repository ppa:ondrej/php
sudo apt update
</pre>

=== Additional Info ===

After the updates you can use <code>sudo apt-get upgrade</code> for Ubuntu 16.04 or <code>sudo apt upgrade</code> for Ubuntu 18.04. This should pull down the very latest version of PHP from the <code>ondrej/php</code> repository. Currently, as of this writing is PHP 7.4.

== Install Specific Versions & Modules ==
Right now I am using the following. You can substitute <code>7.3</code> or <code>7.2</code> for <code>7.4</code>. Just check the modules available per PHP version noted below.

Time to install.
=== Ubuntu 16.04 ===
<pre>
sudo apt-get install php7.4 php7.4-cli php7.4-common php7.4-cgi
</pre>

Then the following modules (these are the ones I generally install):
<pre>
sudo apt-get install php7.4-bcmath php7.4-bz2 php7.4-curl php7.4-dba php7.4-enchant php7.4-gd
php7.4-gmp php7.4-imap php7.4-interbase php7.4-intl php7.4-ldap php7.4-mbstring php7.4-mysql
php7.4-odbc php7.4-pgsql php7.4-pspell php7.4-snmp php7.4-soap php7.4-tidy php7.4-xml php7.4-xmlrpc
php7.4-xsl php7.4-zip
</pre>

=== Ubuntu 18.04 ===
<pre>
sudo apt install php7.4 php7.4-cli php7.4-common php7.4-cgi
</pre>

Then I add the following modules as a start:
<pre>
sudo apt install php7.4-bcmath php7.4-bz2 php7.4-curl php7.4-dba php7.4-enchant php7.4-gd
php7.4-gmp php7.4-imap php7.4-interbase php7.4-intl php7.4-ldap php7.4-mbstring php7.4-mysql
php7.4-odbc php7.4-pgsql php7.4-pspell php7.4-snmp php7.4-soap php7.4-tidy php7.4-xml php7.4-xmlrpc
php7.4-xsl php7.4-zip
</pre>

=== Version Check ===
Check your version. Usually, the highest version is available with:
<pre>
user@YourServer:~$ php -v
PHP 7.4.9 (cli) (built: Aug 7 2020 14:29:10) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.9, Copyright (c), by Zend Technologies
user@YourServer:~$ php7.3 -v
PHP 7.3.21-1+ubuntu16.04.1+deb.sury.org+1 (cli) (built: Aug 7 2020 14:43:42) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.21, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.21-1+ubuntu16.04.1+deb.sury.org+1, Copyright (c) 1999-2018, by Zend Technologies
user@YourServer:~$
</pre>

=== Adding Modules ===

Check what modules are installed.
<pre>
user@YourServer:~$ php7.4 -m
[PHP Modules]
apc
apcu
bcmath
bz2
calendar
Core
...truncated...
exif
fileinfo
filter
ftp
gd
gettext
gmp
hash
iconv
imagick
imap
interbase
intl
json
ldap
libxml
mbstring
mcrypt
mysqli
mysqlnd
...truncated...
xml
xmlreader
xmlrpc
xmlwriter
xsl
Zend OPcache
zip
zlib

[Zend Modules]
Zend OPcache

user@YourServer:~$
</pre>
Now check what modules are available in your apt-cache for the specific PHP version, 7.4 or 7.3 or 7.2, etc.
<pre>
user@YourServer:~$ sudo apt-cache search php7.4
php-amqp - AMQP extension for PHP
php-apcu - APC User Cache for PHP
php-geoip - GeoIP module for PHP
php-igbinary - igbinary PHP serializer
php-imagick - Provides a wrapper to the ImageMagick library
php-mongodb - MongoDB driver for PHP
php-msgpack - PHP extension for interfacing with MessagePack
php-oauth - OAuth 1.0 consumer and provider extension
php-redis - PHP extension for interfacing with Redis
...truncated...
php7.4-soap - SOAP module for PHP
php7.4-sqlite3 - SQLite3 module for PHP
php7.4-sybase - Sybase module for PHP
php7.4-tidy - tidy module for PHP
php7.4-xml - DOM, SimpleXML, XML, and XSL module for PHP
php7.4-xmlrpc - XMLRPC-EPI module for PHP
php7.4-xsl - XSL module for PHP (dummy)
php7.4-zip - Zip module for PHP
</pre>

Need a module? From the list what is available in your apt-cache:
<pre>
user@YourServer:~$ sudo apt-get install php7.4-tidy
</pre>

For Ubuntu 18.04
<pre>
user@YourServer:~$ sudo apt install php7.4-tidy
</pre>

Now you have multiple versions of PHP installed on your server.

== Virtualmin ==

If you are running Webmin w/Virtualmin it is pretty easy to make the versions available for specific virtual hosts (websites) on your Virtualmin Install. This pertains to the latest Webmin 1.954 w/Virtualmin 6.11.

*Log on to the Webmin admin <code>https://yourserver.com:10000</code>
*'''System Settings''' -> '''Re-check configuration'''
*All installed versions of PHP should be found.
*Manage each Virtual Server -> select Virtual Server from Dropdown list at top of Navigation Menu, example, yourdomain.org
*Then select '''Server Configuration''' -> '''PHP Versions'''
*Select the version of PHP for the Virtual Server. Then "Save Versions" button.

All the correct php.ini files and directories should be created in your <code>/home/{username}/</code> directory.

Install Different Version of PHP on Ubuntu

2020-08-15T02:33:17Z

TomHutchison: Created page with "You can install different versions of PHP on Ubuntu. This will also show how to install the versions and use them on Virtualmin for different virtual servers on a Virtualmin/W..."

You can install different versions of PHP on Ubuntu. This will also show how to install the versions and use them on Virtualmin for different virtual servers on a Virtualmin/Webmin install.

== Add the Repository ==
=== Ubuntu 16.06 ===
Use the following on the command line.
<pre>
sudo add-apt-repository ppa:ondrej/php
sudo apt-get update
</pre>

=== Ubuntu 18.04 ===
Use the following on the command line.
<pre>
sudo add-apt-repository ppa:ondrej/php
sudo apt update
</pre>

=== Additional Info ===

After the updates you can use <code>sudo apt-get upgrade</code> for Ubuntu 16.04 or <code>sudo apt upgrade</code> for Ubuntu 18.04. This should pull down the very latest version of PHP from the <code>ondrej/php</code> repository. Currently, as of this writing is PHP 7.4.

== Install Specific Versions & Modules ==
Right now I am using the following. You can substitute <code>7.3</code> or <code>7.2</code> for <code>7.4</code>. Just check the modules available per PHP version noted below.

Time to install.
=== Ubuntu 16.04 ===
<pre>
sudo apt-get install php7.4 php7.4-cli php7.4-common php7.4-cgi
</pre>

Then the following modules (these are the ones I generally install):
<pre>
sudo apt-get install php7.4-bcmath php7.4-bz2 php7.4-curl php7.4-dba php7.4-enchant php7.4-gd
php7.4-gmp php7.4-imap php7.4-interbase php7.4-intl php7.4-ldap php7.4-mbstring php7.4-mysql
php7.4-odbc php7.4-pgsql php7.4-pspell php7.4-snmp php7.4-soap php7.4-tidy php7.4-xml php7.4-xmlrpc
php7.4-xsl php7.4-zip
</pre>

Check your version. Usually, the highest version is available with:
<pre>
user@YourServer:~$ php -v
PHP 7.4.9 (cli) (built: Aug 7 2020 14:29:10) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.9, Copyright (c), by Zend Technologies
user@YourServer:~$ php7.3 -v
PHP 7.3.21-1+ubuntu16.04.1+deb.sury.org+1 (cli) (built: Aug 7 2020 14:43:42) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.21, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.21-1+ubuntu16.04.1+deb.sury.org+1, Copyright (c) 1999-2018, by Zend Technologies
user@YourServer:~$

Check what modules are installed.
<pre>
user@YourServer:~$ php7.2 -m
[PHP Modules]
apc
apcu
bcmath
bz2
calendar
Core
ctype
curl
date
dba
dom
enchant
exif
fileinfo
filter
ftp
gd
gettext
gmp
hash
iconv
imagick
imap
interbase
intl
json
ldap
libxml
mbstring
mcrypt
mysqli
mysqlnd
odbc
openssl
pcntl
pcre
PDO
pdo_dblib
PDO_Firebird
pdo_mysql
PDO_ODBC
pdo_pgsql
pdo_sqlite
pgsql
Phar
posix
pspell
readline
recode
Reflection
session
shmop
SimpleXML
snmp
soap
sockets
sodium
SPL
sqlite3
standard
sysvmsg
sysvsem
sysvshm
tidy
tokenizer
wddx
xml
xmlreader
xmlrpc
xmlwriter
xsl
Zend OPcache
zip
zlib

[Zend Modules]
Zend OPcache

user@YourServer:~$
</pre>
Now check what modules are available.
<pre>
user@YourServer:~$ sudo apt-cache search php7.4
php-amqp - AMQP extension for PHP
php-apcu - APC User Cache for PHP
php-geoip - GeoIP module for PHP
php-igbinary - igbinary PHP serializer
php-imagick - Provides a wrapper to the ImageMagick library
php-mongodb - MongoDB driver for PHP
php-msgpack - PHP extension for interfacing with MessagePack
php-oauth - OAuth 1.0 consumer and provider extension
php-redis - PHP extension for interfacing with Redis
...truncated...
php7.4-soap - SOAP module for PHP
php7.4-sqlite3 - SQLite3 module for PHP
php7.4-sybase - Sybase module for PHP
php7.4-tidy - tidy module for PHP
php7.4-xml - DOM, SimpleXML, XML, and XSL module for PHP
php7.4-xmlrpc - XMLRPC-EPI module for PHP
php7.4-xsl - XSL module for PHP (dummy)
php7.4-zip - Zip module for PHP
</pre>
=== Ubuntu 18.04 ===
<pre>
sudo apt install php7.4 php7.4-cli php7.4-common php7.4-cgi
</pre>

Then I add the following modules as a start:
<pre>
sudo apt-get install php7.4-bcmath php7.4-bz2 php7.4-curl php7.4-dba php7.4-enchant php7.4-gd
php7.4-gmp php7.4-imap php7.4-interbase php7.4-intl php7.4-ldap php7.4-mbstring php7.4-mysql
php7.4-odbc php7.4-pgsql php7.4-pspell php7.4-snmp php7.4-soap php7.4-tidy php7.4-xml php7.4-xmlrpc
php7.4-xsl php7.4-zip
</pre>

Property:Has meta keywords

2020-02-28T13:44:55Z

TomHutchison: Created page with "Has type::Keyword"

[[Has type::Keyword]]

MediaWiki:Pivot.css

2019-10-20T03:34:32Z

TomHutchison:

/* Icons */
#n-Contact-us a:before {
content: "\f003";
}
/* Custom colors - top bar*/
.tab-bar {
background: #2f3f4f
}
/* style the labels */
ul.side-nav label {
background: #2f3f4f;
color: #fff;
padding: .25em .5em;
}
/* sidebar background color and font-family */
body {
background-color: #bad6d6;
font-family: -apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";
}
.side-nav {
font-family: -apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";
}
/* Pre tags */
pre {
background: darkslategrey;
color: #D1F8D1;
padding: 10px 10px;
line-height: 1.5em;
margin: 1em 3em 1em 4em;
font-family: Consolas,"Liberation Mono",Courier,monospace;
}
/* Pre tags in MediaWiki Namespace */
.ns-8 pre {
background: #efefee;
margin: 0;
color: #483d8b;
}
/* Pre tags plain */
pre.code {
color: #555;
background: #f8f8f8;
border: 1px solid #dfdfdf;
margin: 1em 0;
}
/* Image classes */
.center {
text-align: center;
}
img {
margin-bottom: 1em;
}
/* Nested UL and OL */
.mw-content-ltr ul>li>ul {
margin: .25em 0 .25em 1.25em;
}
.mw-content-ltr ol>li>ol {
margin: .25em 0 .25em 1.25em;
}
.mw-content-ltr ol>li>ol {
list-style-type: upper-alpha;
}
.mw-content-ltr ol>li>ol>li>ol {
list-style-type: lower-alpha;
}
.mw-content-ltr ol>li>ol>li>ol>li>ol {
list-style-type: lower-roman;
}
.mw-content-ltr ol>li>ol>li>ol>li>ol>li>ol {
list-style-type: decimal;
}
dl, dd, dl dd {
margin-bottom: 0;
}
/* Override MW legacy.module for all skins styling of ul and ol */
.mw-content-ltr ul,
.mw-content-rtl .mw-content-ltr ul {
/* @noflip */
margin: 0em 0 0.5em 3.2em;
padding: 0;
}

.mw-content-rtl ul,
.mw-content-ltr .mw-content-rtl ul {
/* @noflip */
margin: 0em 3.2em 0 0.5em;
padding: 0;
}

.mw-content-ltr ol,
.mw-content-rtl .mw-content-ltr ol {
/* @noflip */
margin: 0em 0 0.5em 3.2em;
padding: 0;
}

.mw-content-rtl ol,
.mw-content-ltr .mw-content-rtl ol {
/* @noflip */
margin: 0em 3.2em 0 0.5em;
padding: 0;
}

/* @noflip */
.mw-content-ltr dd,
.mw-content-rtl .mw-content-ltr dd {
margin-left: 1.6em;
margin-right: 0;
}

/* @noflip */
.mw-content-rtl dd,
.mw-content-ltr .mw-content-rtl dd {
margin-right: 1.6em;
margin-left: 0;
}
/* Notice Boxes */
.dablink {
font-style: italic;
padding-bottom: 0.5em;
padding-left: 0;
margin-bottom: 0.5em;
color: #555;
border-bottom: 1px solid #ccc;
}

div[class*="panel radius notice-"] {
-webkit-box-shadow: 3px 3px 5px 0px rgba(0,0,0,0.75);
-moz-box-shadow: 3px 3px 5px 0px rgba(0,0,0,0.75);
box-shadow: 3px 3px 5px 0px rgba(0,0,0,0.75);
}

.panel.radius.notice-note {
background: lightgray;
padding: 5px 10px 0px 10px;
}

.panel.radius.notice-warning {
background: rgba(255, 0, 0, 0.85);
padding: 5px 10px 0px 10px;
color: white;
}

.panel.radius.notice-hint {
background: mediumseagreen;
padding: 5px 10px 0px 10px;
color: #f9f9f9;
}

.panel.radius.notice-see-also {
background: lightgoldenrodyellow;
padding: 5px 10px 0px 10px;
color: #191970;
}

.panel.radius.notice-info {
background: aliceblue;
padding: 5px 10px 0px 10px;
color: #191970;
}

.notice {
margin: .5em 0;
}

.notice-title {
font-weight: bold;
border-bottom:1px solid;
width: 100%;
font-size: 18px;
}

p.notice {
width: 100%;
font-size: 16px;
}

/* Category links */
#mw-normal-catlinks li {
background: #2f3f4f;
margin: 5px;
padding: 4px;
}

#catlinks ul li a {
color: #f9f9f9;
}

/* Screen width styles 60em and under */

@media screen and (max-width: 60em) {
.notice-icon {
font-size: .65em;
}
}

@media screen and (max-width: 60em) {
pre {
margin-left:0px;
margin-right:0px;
}
}

MediaWiki:Pivot.css

2019-10-20T03:31:25Z

TomHutchison:

/* Icons */
#n-Contact-us a:before {
content: "\f003";
}
/* Custom colors - top bar*/
.tab-bar {
background: #2f3f4f
}
/* style the labels */
ul.side-nav label {
background: #2f3f4f;
color: #fff;
padding: .25em .5em;
}
/* sidebar background color and font-family */
body {
background-color: #bad6d6;
font-family: -apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";
}
.side-nav {
font-family: -apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";
}
/* Pre tags */
pre {
background: darkslategrey;
color: #D1F8D1;
padding: 10px 10px;
line-height: 1.5em;
margin: 1em 3em 1em 4em;
font-family: Consolas,"Liberation Mono",Courier,monospace;
}
/* Pre tags in MediaWiki Namespace */
.ns-8 pre {
background: #efefee;
margin: 0;
}
/* Pre tags plain */
pre.code {
color: #555;
background: #f8f8f8;
border: 1px solid #dfdfdf;
margin: 1em 0;
}
/* Image classes */
.center {
text-align: center;
}
img {
margin-bottom: 1em;
}
/* Nested UL and OL */
.mw-content-ltr ul>li>ul {
margin: .25em 0 .25em 1.25em;
}
.mw-content-ltr ol>li>ol {
margin: .25em 0 .25em 1.25em;
}
.mw-content-ltr ol>li>ol {
list-style-type: upper-alpha;
}
.mw-content-ltr ol>li>ol>li>ol {
list-style-type: lower-alpha;
}
.mw-content-ltr ol>li>ol>li>ol>li>ol {
list-style-type: lower-roman;
}
.mw-content-ltr ol>li>ol>li>ol>li>ol>li>ol {
list-style-type: decimal;
}
dl, dd, dl dd {
margin-bottom: 0;
}
/* Override MW legacy.module for all skins styling of ul and ol */
.mw-content-ltr ul,
.mw-content-rtl .mw-content-ltr ul {
/* @noflip */
margin: 0em 0 0.5em 3.2em;
padding: 0;
}

.mw-content-rtl ul,
.mw-content-ltr .mw-content-rtl ul {
/* @noflip */
margin: 0em 3.2em 0 0.5em;
padding: 0;
}

.mw-content-ltr ol,
.mw-content-rtl .mw-content-ltr ol {
/* @noflip */
margin: 0em 0 0.5em 3.2em;
padding: 0;
}

.mw-content-rtl ol,
.mw-content-ltr .mw-content-rtl ol {
/* @noflip */
margin: 0em 3.2em 0 0.5em;
padding: 0;
}

/* @noflip */
.mw-content-ltr dd,
.mw-content-rtl .mw-content-ltr dd {
margin-left: 1.6em;
margin-right: 0;
}

/* @noflip */
.mw-content-rtl dd,
.mw-content-ltr .mw-content-rtl dd {
margin-right: 1.6em;
margin-left: 0;
}
/* Notice Boxes */
.dablink {
font-style: italic;
padding-bottom: 0.5em;
padding-left: 0;
margin-bottom: 0.5em;
color: #555;
border-bottom: 1px solid #ccc;
}

div[class*="panel radius notice-"] {
-webkit-box-shadow: 3px 3px 5px 0px rgba(0,0,0,0.75);
-moz-box-shadow: 3px 3px 5px 0px rgba(0,0,0,0.75);
box-shadow: 3px 3px 5px 0px rgba(0,0,0,0.75);
}

.panel.radius.notice-note {
background: lightgray;
padding: 5px 10px 0px 10px;
}

.panel.radius.notice-warning {
background: rgba(255, 0, 0, 0.85);
padding: 5px 10px 0px 10px;
color: white;
}

.panel.radius.notice-hint {
background: mediumseagreen;
padding: 5px 10px 0px 10px;
color: #f9f9f9;
}

.panel.radius.notice-see-also {
background: lightgoldenrodyellow;
padding: 5px 10px 0px 10px;
color: #191970;
}

.panel.radius.notice-info {
background: aliceblue;
padding: 5px 10px 0px 10px;
color: #191970;
}

.notice {
margin: .5em 0;
}

.notice-title {
font-weight: bold;
border-bottom:1px solid;
width: 100%;
font-size: 18px;
}

p.notice {
width: 100%;
font-size: 16px;
}

/* Category links */
#mw-normal-catlinks li {
background: #2f3f4f;
margin: 5px;
padding: 4px;
}

#catlinks ul li a {
color: #f9f9f9;
}

/* Screen width styles 60em and under */

@media screen and (max-width: 60em) {
.notice-icon {
font-size: .65em;
}
}

@media screen and (max-width: 60em) {
pre {
margin-left:0px;
margin-right:0px;
}
}

MediaWiki:Sidebar

2019-10-20T03:28:45Z

TomHutchison:

MediaWiki:Sidebar

2019-10-20T03:28:15Z

TomHutchison:

MediaWiki:Sidebar

2019-10-20T03:27:46Z

MediaWiki:Contactpage-defsubject

2019-10-20T03:23:17Z

TomHutchison: Created page with "[InfoTechPedia] Contact Message"

[InfoTechPedia] Contact Message

Patch Command

2019-10-16T12:27:46Z

TomHutchison:

This page shows how to use the patch command in CLI

Example using MediaWiki patch files to update minor versions of MediaWiki.

A small patch file is usually made available for a minor version upgrade. Manually download and extract the patch file from the dumps site or follow the directions with wget below. Patches are incremental, you can not skip a version.

:cd to your main MediaWiki directory (the one with LocalSettings.php)
:Download the patch file and gunzip it.
:Use patch <code>-p1 --dry-run</code> to check what will be changed (e.g., <code>patch -p1 --dry-run -i mediawiki-x.xx.x.patch</code>)
:If all is well, run patch again without --dry-run.
:Check your Special:Version and you should see the new version number in place.

[[Category:Linux]][[Category:Command Line]]

Patch Command

2019-10-16T12:26:07Z

TomHutchison: new page on patch

Using patch cli command

Example using MediaWiki patch files to update minor versions of MediaWiki.

A small patch file is usually made available for a minor version upgrade. Manually download and extract the patch file from the dumps site or follow the directions with wget below. Patches are incremental, you can not skip a version.

:cd to your main MediaWiki directory (the one with LocalSettings.php)
:Download the patch file and gunzip it.
:Use patch <code>-p1 --dry-run</code> to check what will be changed (e.g., <code>patch -p1 --dry-run -i mediawiki-x.xx.x.patch</code>)
:If all is well, run patch again without --dry-run.
:Check your Special:Version and you should see the new version number in place.