Brown Paper Packages Mac OS
- Mac Os Package Manager
- Mac Os List
- Brown Paper Packages Mac Os Catalina
- Mac Os Package Installer
- Brown Paper Packages Mac Os 11
This section covers the installation of the PaperCutUser ClientThe User Client tool is an add-on that resides on a user's desktop. It allows users to view their current account balance via a popup window, provides users with the opportunity to confirm what they are about to print, allows users to select shared accounts via a popup, if administrators have granted access to this feature, and displays system messages, such as the 'low credit' warning message or print policy popups. on Apple Mac systems. Before installing the client software, review Mac printing in detail and first ensure printing is working as expected.
The PaperCut Mac User Client software is a supplied as a native Mac .app package. The User Client is delivered in two flavors:
The current client, which supports Mac OS X 10.7 (Mountain Lion) and above.
The legacy client, which supports Mac OS X versions from 10.4 to 10.6. It is a universal application that runs on both PowerPC and Intel hardware. The legacy client will not receive future feature enhancements.
On Mac OS X packages can be installed in three ways: Using Package Manager in the R.APP GUI (recommended for most Mac users) Using install.packages command in R; Using R CMD INSTALL command in the shell (aka Terminal) The latter two methods are common to all Unix systems and as such described in the general R documentation. Mac has long been referred to as the “Creative’s workshop.” The idea that most graphic designers, interior designers, video animators, and architects are more drawn to Mac may hold water to an extent. Mac attracts creatives for either of two reasons – as the traditional tool they’ve always used or its perceived high performance standards. Explore the world of Mac. Check out MacBook Pro, MacBook Air, iMac, Mac mini and more. Visit the Apple site to learn, buy and get support. These packages contain Moodle plus all the other software needed to make it run on a Mac: Apache, MySQL and PHP. They are built using MAMP.
Apple has switched to a yearly release cycle for Mac OS X, which means it is difficult to keep this documentation up to date. For the most recent and up-to-date information on current best practices, see the Knowledge Base.
For Mac OS X 10.7 and later
Utilizing LaunchAgent:
For Macs running 10.7, 10.8, 10.9, 10.10, 10.11, and later, the best way to establish set launch behavior patterns for the PCClient.app is to use LaunchAgents managed by LaunchD. For more information, see http://www.papercut.com/kb/Main/MacClientStartupWithLaunchd.
For legacy Mac OS X (10.6 and earlier) solutions:
For Macintosh computers running versions of Mac OS older than 10.7, the following three common installation methods cover most situations. The instructions for the 'single user install' follow the standard Mac application installation process and can be conducted by any Mac end user. The other installation methods are more technically focused and aimed at Mac network administrators.
Special Notes for Mac OS X 10.6 and earlier
NOTE'>NOTEThe current version of the PaperCut client does not work on Mac OS X 10.6 and earlier. For these systems the legacy client must be used. If the client fails to start, ensure you are using the correct client for your system.
The legacy client is found in [app-path]/client/legacy. Use this path to locate the client when referenced in the following sections.
The legacy client software works best if Java 5 (or higher) is installed. Java 5 is available for OS X 10.4 or above. If Java is not already installed, the installer is available from the Apple website. This simplest way to install Java is to run /Applications/Utilities/Java Preferences from OS X Finder, and you are prompted to complete the installation.
Single user install
This method is suitable for a Mac computer used by a single user. For example, a personal Mac desktop or laptop. The installation process involves clicking the client-local-install program. This copies the PCClient application into the over to the system's Applications folder and starts the client in the 'confirm network identity' mode. The simplest way to run the install process is to connect to a Windows server's pcclient share over the network, however, alternate methods such as copying the folder contents via a USB key or drive are also possible.
To install the Mac User Client from a server's share:
Start and Log in to the Mac computer. Ensure it's connected to the network.
Open the Finder.
In the Go menu, select Connect to Server.
Enter the pcclient share's connection details, such as: smb://server_name/pcclient.
Enter password information if requested.
Double-click the client-local-install file. This executes a small AppleScript program that starts the install/copy process. (If installing on a legacy system (OS X 10.6 or earlier), you must install the legacy client located in the legacy folder.)
Test the application by double-clicking the PCClient application icon in the system's local Applications folder.
If the user needs the User Client for printing (for example, to use the shared accountA shared account is an account that is shared by multiple users. For example, in business, shared accounts can be used to track printing costs by business unit, project, or client. Organizations like legal firms, engineering firms, or accounting offices often have long lists of accounts, projects, clients, or matters. In a school or university, shared accounts can be used to track printing by departments, classes, or subjects. popup), configure the application to automatically open upon start up:
Open System Preference from the Apple menu.
Select Accounts.
Select your login account.
Click the Login Items tab.
Click + then browse and select the PCClient application.
Test by restarting the computer. The client should start automatically after the reboot and log in procedure is complete.
Multi-user install
On a multi-user Mac system, setting up a Login Item for each user would be a tedious task. To streamline this process, you can configure the PCClient application to start on login via the login hook. A login hook is an advanced Mac feature that works by running a script when a user logs in. The PCClient package includes a command script resource that installs the login hook.
To install the User Client on a multi-user system:
Start and log in to the Mac computer.
Ensure the Mac computer is connected to the network.
Open the Finder.
From the Go menu, select Connect to Server
Enter the pcclient share's connection details, for example, smb://server_name/pcclient
Enter password information if requested.
Drag the PCClient (or legacy/PCClient on OS X 10.6 or lower) package to the local hard disk's Applications folder. The copy process begins.
In the Applications directory, Control+click the newly copied PCClient application.
Select Open Package Contents.
Navigate to Contents/Resources/.
Double-click the install-login-hook.command script.
Restart the system and verify the client starts on login.
If you're already using a login hook for other script tasks, the setup process is different. Instead in step 10, double-click the set-permissions.command file. Then insert the following line at the end of your current login script (all on one line):
/Applications/PCClient.app/Contents/Resources/login-hook-start '$1'
The set-permissions.command script ensures the software is set up with the correct permissions, making it accessible to all users.
You can remove the login hook, once installed, with the terminal command:
sudo defaults delete com.apple.loginwindow LoginHook
Zero-install deployment
Mac Os Package Manager
This deployment method is for advanced Mac network administrators and is suitable for medium to large Mac networks. Knowledge of the Mac's Unix underpinning and scripting is required.
A more flexible option over locally installing the PCClient package on each Mac system, is to directly launch the client from the pcclient share. The advantage of this deployment method is that any updates applied on the server (and updates to the client directory) are automatically propagated to all workstations.
The process of setting up zero-install deployment varies from network to network depending on the directory environment in use and administrator preferences. The process can, however, be summarized as:
Configure the Macs to mount the pcclient share as a volume on login or start-up.
Configure a login hook to start the client off the share. The install-login-hook.command resource script explained in the multi-user install above might help.
The typical way to mount the share is to use mount_smbfs in a boot script. See the Apple documentation on mount_smbfs at: http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/mount_smbfs.8.html
Further information on Mac printing is available at Mac printing in detail.
All HEASOFT tasks may now be run remotely using the Hera data analysis serviceat the HEASARC without having to install the software locally. This providesa quick way to try out the software and is ideal for users who have limited orinfrequent need to run the HEASOFT tasks. More intensive users of HEASOFT arestill encouraged to install the software locally for best performance. Learn more about using Hera.
A download containing all of the package selections can be around 5 Gbin size when unpacked; the actual size will vary depending on the packagesyou select and - if you choose a binary distribution - the architectureselected. If large file sizes present problems for your connection, itis possible to download the packages you want separately and unpack thetar files on top of each other afterwards, though you may need to eitherrename each tar file with a temporary name during the process or unpackeach file immediately upon downloading so that one tar file isn'toverwritten by the next.
Please use the interface below to download pre-compiled binaries, orif you wish to select only certain parts of the HEASoft suite for yoursource code download. For users who want all of the HEASoft sourcecode, here are direct links to two tar file options, one of the completesource code, and one which addsolder Xspec model data files:
Mac Os List
Please click SUBMIT only once, and be patient while a tar file containing your selections is assembled and retrieved.
* Xspec Notes:
- HEASOFT 6.28 includes Xspec v12.11.1. Please see the Xspec issues web page to apply the latest patches after building Xspec (source code distribution required).
- Older Xspec model data (file list here) is available in a separate tar file:
Older Xspec model data (1Gb / 4.5Gb unpacked)
After installing and initializing HEASoft, unpack this tar file in the directory above $HEADAS: - Users who wish to link Xspec models into their own program are advised todownload the Xspec source code distribution and configure heasoft using the option '--enable-xs-models-only'.
- Visit the known issues page for notifications about any problems (and relevant patches) identified after HEAsoft 6.28 was released.
- Un-gzip and un-tar the file created for you (either heasoft-6.28src.tar.gz or heasoft-6.28<platform>.tar.gz depending on which type of distribution you selected) in a clean directory and follow the instructions in our installation guides for the following platforms:
A lengthier and more complete HEASoft installation guide is also available if you need more information. - See our recommendations for batch processing and good scripting practices when writing your own scripts to run HEASoft tasks.
- Optional: download and run the hwrap script to create an alternate runtime environment for HEASOFT to help avoid conflicts with other software packages (e.g. XMM-SAS or CIAO).
FTOOLS HELP DESK
If FTOOLS has been useful in your research, please reference thissite (http://heasarc.gsfc.nasa.gov/ftools) and use the ASCL reference for HEASoft[ascl:1408.004] or theASCL reference for the original FTOOLs paper[ascl:9912.002]:
Brown Paper Packages Mac Os Catalina
Blackburn, J. K. 1995, in ASP Conf. Ser., Vol. 77, AstronomicalData Analysis Software and Systems IV, ed. R. A. Shaw, H. E. Payne,and J. J. E. Hayes (San Francisco: ASP), 367.
Mac Os Package Installer
Web page maintained by:Bryan K. Irby