Note: This document assumes you are using MacOS 7.1 or later and version 7 or later of the LaserWriterdriver. If you are using Mac OS X, see ARCHIVED: In Mac OS X, how do I convert a document to PostScript?
This article is a guide for how to tweak BIOS setting, installing macOS and post-installation setup with Clover Bootloader for installing Mac OS (X) on PC (Hackintosh) using the vanilla method. This tutorial is mainly for PC with legacy BIOS, but just be creative if you’re UEFI BIOS user. The Macintosh project began in 1979 when Jef Raskin, an Apple employee, envisioned an easy-to-use, low-cost computer for the average consumer.He wanted to name the computer after his favorite type of apple, the McIntosh, but the spelling was changed to 'Macintosh' for legal reasons as the original was the same spelling as that used by McIntosh Laboratory, Inc., an audio equipment. While I wouldn’t recommend them to every Mac user, if you’re comfortable with the potential issues of immediately shutting down your Mac, you’ll want to learn these post-haste. The Mac now has the highly desirable “Cut and Paste” file feature throughout the Mac OS X desktop and Finder, allowing users to truly cut and paste to move the selected documents or folders to a new location, rather than just making a copy of them. Define post-haste. Post-haste synonyms, post-haste pronunciation, post-haste translation, English dictionary definition of post-haste. Post-haste - as fast as possible; with all possible haste; 'send it to me post-haste' Based on WordNet 3.0, Farlex clipart collection.
You can create a PostScript file out of any document usingthe LaserWriter printer driver. Whether you actually have aLaserWriter printer or not, you can still use this driver to print tothe disk, creating a PostScript document. To do so:
From the Apple menu, select Chooser. In the window thatappears, look for a LaserWriter or LaserWriter 8icon. If you can't find one, you can download the LaserWriter driverinstaller from the LaserWriter directory on Apple's Software Updates site.
From thedirectory, select the four links titledLW_8.2.3f_Installer-XofX.img.bin. Numbers will replaceX, indicating the sequence number out of the four-image setof files. You must download and install all four files.
Chooser
window, click the LaserWriter8 icon.Note: This post may be a little out of date as it was originally written in 2015. But I’m posting it here as the fundamentals have not really changed much.
Credits: Thanks to Gary Larizza for his post on AFP548.com where most of this documents content was sourced ( https://www.afp548.com/2010/06/03/the-commandments-of-packaging-in-os-x )
When managing Mac OS X devices, you will enviably have to deploy files or applications to many devices. There are many ways to achieve this, however the most effective and best practice method is to use Packages.
While packaging is quite simple, it can very quickly become quite complex. This document serves to provide some guidelines to help you avoid some simple mistakes and prevent confusion when creating packages.
There are many tools out there used to create Packages, Apple offer their own built in command line tools like pkgbuild. This guide will not go into detail about how to use any of these tools, it is up to the system admin’s own personal preference on which tools they wish to use in order to create their packages.
However version control is very important, as is the ability to quickly and accurately create and recreate packages. The ability for packages to be peer reviewed and package versions to easily be diff’d is also important and the admin’s choice of tools should take this into account. It is also highly recommend that a version control system such as git is used in combination with package creation.
Below is a list of tools that are recommended for creating packages:
A great GUI driven tool to create flat and distribution packages and provides an easy to learn GUI. It is still quite powerful and allows a great deal of control over how your packages are created. A build file is created which saves information on how the package should be created such as the payload, pre/post flight scripts, additional resources etc etc.
Cost: $0 – FREE
A completely text driven package building system perfect for use with version control systems such as Git. Files can easily be reviewed to see what will be in the package without any extra work.
The big benefit to using The Luggage is that because the packages are created with make files, these make files can easily be diff’d to see changes as well as talking other users through the creation process. No GUI panes to navigate.
Cost: $0 – FREE
Munki PKG is a simple tool very similar to The Luggage which builds packages in a consistent, repeatable manner from source files and scripts in a project directory.
Files, scripts and metadata are stored in a way that is easy to track and manage using a version control system like git.
Cost: $0 – FREE
Your installer should not require any input from the end user.
DO:
DO NOT:
DO:
DO NOT:
DO:
Licensing should be managed by Systems Administrators. Wherever possible licensing files should be packaged separately to the application being deployed. This allows for a single application package to be deployed to multiple sites with different licensing files applied later depending upon the licence that is appropriate for that site.
Licensing information might be supplied via a global plist/config profile/KMS or other.
This also prevents unauthorised installation of software should your application package be obtained by a unauthorised third party.
DO NOT:
DO:
Use pre and post install scripts only when necessary, and follow all other rules with your scripts.
For example, it would be silly to use a package to install some files on disk and then use a post install script to set the permissions of those files. Instead correctly set the permissions of the files in the payload.
This also allows for reviewing of package contents via lsbom
DO NOT:
DO:
Naming conventions are necessary and helpful. For example VPN.pkg is NOT helpful.
Give your packages meaningful names and version numbers. Providing vendor and product name, along with important version numbers and vendor identification codes.
DO:
If you are going to supporting running your application or payload on operating systems back to say version 10.8, then it should go without saying that you need to TEST your package on every version from 10.8 to the most current.
DO NOT:
DO:
Even if you are not planning on having your package installed via the GUI you should still make it GUI-friendly.
DO:
Try to avoid using Snapshot methods to create packages – a common tool used to create snapshot packages is JAMF’s composer.
Snapshotting is generally considered bad juju and the result of a lazy (not in a good way) sysadmin
Packages created from snapshots lack the nuances and intent of the original package. They can often miss critical files or modifications to the file system.
If you are unable to use a vendor package, consider the following:
DO:
Gatekeeper was introduced in 10.8 as a way to alert users to unsigned packages. For this reason, it is best practice to sign your installer packages with a developer ID certificate that lets your users know your packages can be trusted. It also allows packages to be installed in the GUI when Gatekeeper is configured to allow apps downloaded from the App Store and identified developers
Unsigned packages are not an issue when not using the GUI installer however.
DO: