For more help with UNIX, try this guide from the University of Edinburgh UNIX Frequently Asked Questions (FAQs) These seven articles contain the answers to some Frequently Asked Questions often seen in comp.unix.questions and comp.unix.shell. Adapted for Mac OS X by Shane Burns from a tutorial by M.Stonebank@surrey.ac.uk. The current Mac operating system is macOS, originally named 'Mac OS X' until 2012 and then 'OS X' until 2016. Developed between 1997 and 2001 after Apple's purchase of NeXT, Mac OS X brought an entirely new architecture based on NeXTSTEP, a Unix system, that eliminated many of the technical challenges that the classic Mac OS faced. MacOS is a UNIX 03-compliant operating system certified by The Open Group. It has been since 2007, starting with MAC OS X 10.5. The only exception was Mac OS X 10.7 Lion, but compliance was regained with OS X 10.8 Mountain Lion. Amusingly, just as GNU stands for 'GNU's Not Unix,' XNU stands for 'X is Not Unix.'.
Everyone already knows that Mac OS X is a Unix variant and that it can run Unix software. Many just leave it at that, assuming that Unix software means things that run in the Terminal – but there's also a whole wide world of graphical apps in the Unix world that run in what's known as the X11 environment.
Mac Os X Unix Background
https://chicagosoft.mystrikingly.com/blog/auto-clicker-left-and-right. The problem is that not many in the Mac community – beyond the übergeeks – seem to know or understand what X11 is.
Fortunately, Apple has made it easy to install and use X11 in a near seamless fashion on your Mac. With a little guidance, it's pretty easy to be up and running with a bunch of free apps that are well-known to those in the Linux and Unix world.
X11 is the flagship product of X.Org Foundation and simply provides a method for Unix systems to draw windows, mouse pointers, and other standard elements of a graphical user interface (GUI).
Without X11, using a Unix or Linux system is totally a command-line affair.
What Is X11?
X, as it was originally known, was first developed at MIT in 1984. (Probably not coincidentally, this is the same year the first Mac debuted, starting the GUI revolution.) By 1987, it had developed into X11, and it hasn't changed a whole lot since, beyond being updated for newer video cards and the like.
X11 operates on a client-server methodology. Basically, the X server serves up graphical content and an X client draws the windows and accepts mouse and keyboard input. For nearly all its uses these days, the server and the client are running on the machine, providing Linux distributions everywhere with a fully graphical environment.
After the Mac OS transitioned to a Unix base when OS X debuted in 2001, it was only a matter of time before X11 was up and running on the Mac. But X11 had actually been there long before. X11 clients for the Mac have existed since the late 1980s. Tenon's MachTen provided a full Unix environment for 680×0 and early PowerPC Macs, including a bundled X client and server. (Tenon later morphed this product into iTools, which provides a nice graphical front end for the Unix/server parts of OS X.)
Apple's mid-1990s Unix, A/UX, also shipped with an X11 client and server.
X11 on OS X
Getting X11 up and running with Mac OS X 10.0 meant compiling it from source code. Although this was a snap for veteran Unix admins, it would take a while before the idea took off on the Mac. Flash-forward 18 months, and the process got a lot easier in the era of Mac OS X 10.2. A package installer for X11 surfaced from X.Org, and a new third-party app named XDarwin made it easy to run X11 apps alongside OS X's Aqua ones (or run X11 in its full-screen 'rootless' mode).
Not long after, Apple started shipping a beta of its own package simply named X11, combining both the X11 framework and a client very similar to XDarwin.
Since OS X 10.3, X11 has been quick and easy to get up and running, and thus there's been a lot more interest in the Mac community.
Is it worth downloading X11 for 10.3 (or installing from your Tiger install disc for 10.4 users)?
There a few good reasons, and since we're in the realm of free software, it won't cost you anything but some time.
Reason #1: Free software
There's a ton of free, open source software that runs under X11 on Unix/Linux systems, and with a little bit of recompiling they can easily run on OS X, too. If compiling software is a deal-killer for you, don't worry, because somebody else has already done the work for you.
Fink and DarwinPorts are two incredible projects with the common goal of porting Unix software to Mac OS X. Installing either one of these makes it a breeze to get a ton of free software on your system.
For newcomers, I'd recommend Fink, if only because of it's wonderful bundled GUI companion, FinkCommander. With FinkCommander in hand, it's a point-and-click affair to find the type of software you're looking for and get it installed on your Mac.
Best format for external hard drive mac. Although Fink has a package installer and is really easy to get up and running, follow the instructions closely. In particular, make sure you download the Fink that's right for your OS and install the X11 SDK from your X11 installer (either downloaded or on the Tiger DVD).
Once you have your software installed, type the program's full path in X11's terminal window. For example, to open the Bluefish editor I installed with Fink, I type:
(The '&' backgrounds the bluefish process, so that I don't have to leave the terminal window open to keep Bluefish up and running.)
The downside to this is having to know the full path of an application's command. Fortunately, fink installs almost everything in /sw/bin/. You can use X11's built-in menu editor to add shortcuts to the the Application menu and not have to type the commands every time.
It's also possible to download packages that utilize X11 but require no typing of commands to launch. One such fantastic package is Gimp.app, which makes installing and running the popular open-source image editor a snap. Just double-click its icon, X11 opens, and then Gimp opens up.
Reason #2: Run Apps on Other Systems
Going back to its client-server methodology, X11 can serve apps over the network using a standard SSH connection.
In a typical SSH connection, you would type something like the following to get a remote terminal connection:
To forward X11 from that SSH connection, use the following for OS X 10.3:
Or, for OS X 10.4:
Now you will have a session opened on the remote machine. Just type in an X11 application's command, and it will open in your Mac's X11 environment.
In my day job, I work with an assortment of Linux systems, and running these apps quickly and securely over the network on my PowerBook is a real joy. It beats using a VNC (virtual network computing) client or standing at the console in the server room any day.
This also opens up possibilities for the home user who'd like to try Linux. Linux can run on an old box in your closet while you try out the apps on the laptop from your couch.
Reason #3: Run a Different Desktop Environment
A little bored with OS X and Aqua? With X11, it's possible to run an entirely different desktop environment on your Mac. This includes the ever-popular K Desktop Environment (KDE), which along with Gnome is one of the leaders in Linux graphical environments.
Fink can get you a working KDE installation, and there are quite a few other methods to get to the same place. Googling for 'KDE Mac OS X install' will bring up quite a few pages for research, but those actually inclined to run KDE on their Mac will probably enjoy the challenge (and master it quite easily).
Further Reading
- Preparing for Scribus: Working with X11 and FinkCommander, Jason Walsh, Low End Designer
Keyword: #x11
Short link: http://goo.gl/q7XMSO
searchword: x11
Related
1998: If you cut your teeth on the Mac or even a Windows machine, count yourself fortunate. A graphical operating system lets you play around and figure out how things work. It's user-friendly, which is why the Macintosh caught on and influenced the shape of the dominant PC operating systems.
The same concepts are playing a larger role in the Unix world, with X Windows, NeXTstep, and BeOS offering graphical interfaces for the underlying operating system.
Until next year, the Macintosh OS is highly integrated from the kernel through the interface. But next year Mac OS X will integrate our familiar interface with a kernel designed around very different principles.
In the Beginning
The first computers didn't use keyboards, punch cards, or any kind of tape. They were hard wired. Then came programmable computers and ways to save programs and run them again. Eventually, we got to things like keyboards, video displays, and disk drives.
Early computer operating systems would greet you with a blank screen. Well, nearly blank. There might be a cursor awaiting your input – a blinking cursor on some systems. But you couldn't just sit down and use these computers. You had to know their language. You had to work to get them to work for you.
Unix was born at AT&T in 1969. In an age when most computers had proprietary operating systems, Unix was designed for portability. Written in the C programming language, all you needed to do to put C on another computer was write a C compiler and compile Unix for the new computer.
In that era, computers did many jobs for many users and cost many, many dollars. They also generated many dollars by leasing computer time, so a top concern was a robust operating system – you wanted that machine earning its keep every minute that it was running. Chrome 60 mac.
Unix became a leading operating system because it was designed from the ground up to track users, track system resources, track time used, and keep the computer up and running. Today you hear stories of Unix computers that never crash, only going down for preventive maintenance, system updates, or natural disasters. Ch340s usb parallel driver.
Enter Personal Computers
The first personal computers didn't have enough resources to run Unix. With only a few kilobytes (KB) of memory, there was no reason to even consider multi-user support. Early PC operating systems such as TRS-DOS, Apple DOS, and CP/M assumed one CPU, one user, and one program running at a time. If the system crashed, only one person lost data. The key was making as much functionality as possible fit into a limited amount of memory. Stability was nice but not always foremost.
But they all had the same kind of blank screen waiting for input as the earlier mainframe and minicomputers had.
That didn't change with the introduction of the IBM PC. Sure, it could handle an unimaginable 640 KB of memory, but MP/M-86 (an early multi-user OS for the PC) was never a hit. Users had become used to one CPU, one user, and one program running at a time.
Over time the paradigm shifted, thanks to utilities that let DOS machines keep two or more programs in memory and switch on the fly. Then came operating systems for personal computers (including Windows, OS/2, and the Mac OS) that let you run more than one program at a time, even allowing the background programs to keep working (although usually with reduced performance).
One CPU, one user, many programs has given way, over the past few years, to one or more CPUs, one user, many programs. Both the Mac OS and Windows support two or more CPUs, which can be very helpful for Photoshop filters and a handful of other intensive tasks.
Full Circle
Windows and the Mac OS grew out of the single user, single task, single CPU paradigm to allow multiple tasks and multiple users. But they lost stability along the way.
It's tiresome restarting a computer and waiting while it reloads. And it's frustrating losing your work. Stability has become a top concern among PC users, whether we use Macintosh, Windows 98, or Windows NT.
From that perspective, Unix looks like the holy grail. Stable. Multitasking. Support for multiple CPUs. Even if we don't need the multi-user capabilities, it looks like a much better platform to build upon than a hacked at OS with roots going back to DOS 1.0 (1981, rooted in CP/M from the 1970s) or Macintosh System 1 (1984).
Really Full Circle
I've done a little experimenting with MacBSD, an implementation of Unix that runs on older Macs. I find it as opaque as MS-DOS was when I first set out to learn it. There's a blank screen with a cursor.
What do you do?
For all its power, Unix is an operating system for gurus and wizards. For most users, it will be enough to run a graphical shell that isolates us from Unix, just as Windows 98 isolates users from DOS.
From what I've seen of BeOS, it's not difficult to implement a version system that hides the underlying OS behind an easy-to-use shell. For most of us, Mac OS X will look and act a lot like Mac OS 8.x – but it will keep running if our applications crash.
I'm glad Steve Jobs is willing to lead Apple forward by finding roots even deeper in the past than the Apple II. Unix will give Mac OS X the stable, extensible foundation it needs to enter the 21st century.
And Jobs should know. He went down this road with NeXT, perhaps the first consumer computer designed to run Unix with a graphical shell.
Mac Os Unix Based
Further Reading
- Operating Systems: Past, Present, and Future, Mac Musings
Is Mac Unix Based
keywords: #unix #macosx #macbsd
