hatari.tuxfamily.org

A Mac is a desktop or laptop computer made by Apple that runs the macOS operating system. You use it for everyday computing (email, web, documents, video calls), creative work such as photo editing, and professional tasks like software development or media production. It sits alongside Apple's other devices — iPhone, iPad, and Apple Watch — but it is the only one in that group designed as a full general-purpose computer with a keyboard, pointer, and file system.

How a Mac fits into Apple's lineup

Apple's products overlap in apps and services, but they are built for different jobs:

The practical difference: a Mac is where you go when a task needs a real keyboard, large screen, multiple windows, and the ability to install desktop software. An iPhone or iPad can do many of the same things, but the Mac is the one built for sustained, heavy work.

What people actually use a Mac for

• Everyday computing — email, web browsing, word processing, spreadsheets, video calls, messaging.
• Creative work — photo editing and cataloging (for example, in Lightroom), graphic design, video editing, music production.
• Professional and technical tasks — software development, data work, running business applications.
• Media and entertainment — streaming, music libraries, and syncing with an iPhone, iPad, or Apple TV.
• Organization and storage — managing files, backups, and photos across Apple devices.

If your work is mostly reading, messaging, and light apps, an iPhone or iPad may be enough. If you need desktop software, large-screen multitasking, or heavy file management, a Mac is the appropriate tool.

Laptop vs. desktop: which kind of Mac

Macs come in two broad shapes, and the choice usually comes down to portability versus screen size and expandability.

Laptops

• MacBook Air — thin and light, aimed at everyday use and travel.
• MacBook Pro — more performance for demanding creative or professional work.

Desktops

• iMac — an all-in-one with the computer built into the display.
• Mac mini — a small desktop you pair with your own monitor, keyboard, and mouse.
• Mac Studio — a compact desktop positioned for higher-end professional workloads.

The general rule: choose a laptop if you need to work in different places; choose a desktop if you want a larger screen, a fixed workspace, or more room to configure the machine.

Where Macs overlap with iPhone, iPad, and Apple Watch

Apple designs these devices to work together. Photos, messages, notes, and calendars can stay in sync across them, and a Mac can serve as the hub where you manage files and backups for the others. That integration is a major reason people choose a Mac rather than a Windows PC — but it also means setup, accounts, and syncing are common points where new users need help.

If you need help getting started or fixing something

A Mac is straightforward once it's set up, but the first steps — initial setup, networking, moving files from an old computer, syncing with an iPhone or iPad, or learning a specific app like Lightroom — are where people most often get stuck.

Metro MacSupport, run by Apple Certified Support Professional Ronald Gehrmann, provides training, tutoring, coaching, troubleshooting, and support for Mac, iPad, iPhone, iPod, Apple TV, and Apple Watch users in Portland, with remote support available anywhere. If you're deciding whether a Mac fits your needs, or you already have one and want help with setup, networking, or a particular application, that's the kind of support to look for: an Apple-certified professional who can work on-site in the Portland area or remotely.

Arx Libertatis is an improved, cross-platform, open-source engine for Arx Fatalis, the 2002 first-person RPG/dungeon crawler/immersive sim from Arkane Studios. To play on Linux, you install Arx Libertatis (official Linux builds are provided), then point it at a copy of the original Arx Fatalis game data — the engine itself does not include the game. You need to own or otherwise obtain Arx Fatalis or its demo before you can play.

What Arx Libertatis actually is

Arx Libertatis is a port and modernization of the Arx Fatalis engine, based on the publicly released Arx Fatalis source code and available under the GPL 3+ license. Version 1.2.1 supports modern systems, brings the game to new platforms, and removes bugs and limitations of the original release.

Two things follow from that:

• The engine is free and open source. You can download, inspect, and redistribute the code under the GPL.
• The game data is not included. The license covers the engine only. The art, audio, levels, and other assets remain part of the commercial game, so you must supply them yourself.

The game itself features crafting, melee and ranged combat, and a distinctive spellcasting system where you draw runes in real time to cast the spell you want.

What you need before installing

The original game is sold through storefronts such as GOG.com, the Microsoft Store, and the Bethesda Store, and it also has a demo. Any of these gives you the data files the engine needs.

Installing Arx Libertatis on Linux

Arx Libertatis provides official builds for Windows and Linux. Beyond those, it has been packaged for macOS (Homebrew), FreeBSD, DragonFly BSD, NetBSD, OpenBSD, Haiku, and Pandora, and will likely compile and work on other operating systems.

On Linux, you have two practical routes:

Option 1: Use a distribution package

Check whether your distribution ships Arx Libertatis in its repositories. If it does, install it through your normal package manager. This is the least manual path and keeps updates tied to your system.

Option 2: Use the official Linux build

Download the Linux build from the project's download page and unpack it. This works regardless of whether your distribution packages the engine, and it lets you run a specific version such as 1.2.1.

If neither fits, the source is available on GitHub, so you can build it yourself — the project notes it will likely compile on other systems too.

Pointing the engine at your game data

The engine needs to find the Arx Fatalis data files. The general flow is:

1. Install or unpack Arx Libertatis using one of the routes above.
2. Locate your Arx Fatalis data. If you bought the game from a storefront, the installer places the data files somewhere on disk; if you have the demo, it comes as its own set of files.
3. Tell Arx Libertatis where that data is when you first launch it, or place the data where the engine expects it.
4. Launch the game and confirm it reaches the main menu.

The expected result at each step is simple: the engine starts, finds the data, and loads the game rather than exiting with a "data not found" style error.

If the game does not run

Check these in order:

• Data path is wrong. The most common failure is the engine not finding the Arx Fatalis data. Re-check the path you gave it.
• You installed the engine but not the game. Arx Libertatis alone cannot run — it has no assets of its own.
• Graphics/driver problems. Since the engine targets modern systems, most rendering issues trace back to drivers or to running an old build. Try the current release (1.2.1).
• Wrong build for your system. Make sure you grabbed the Linux build, not the Windows one, if you installed manually.

Where to go next

The project plans to keep improving and modernizing the engine and to enable community customizations and mods. If you want to follow development or get help, the project links to its GitHub repository, Mod DB page, and community forums such as the TTLG Forum and the GOG.com forum. There are also community projects built around the game, including the Arx Insanity Mod and other Arx mods.

BSD is a family of Unix-like operating systems—most notably FreeBSD, OpenBSD, and NetBSD—that share a common heritage and a development model in which the kernel and core userland tools are designed and released together. It differs from Linux mainly in that structure, in its permissive licensing, and in how hardware support is organized. BSD is a reasonable choice if you want a coherent, conservatively engineered system for a server, a network appliance, or a security-focused machine; it is a less obvious choice if you depend on very new consumer hardware or on software that assumes Linux-specific interfaces.

What "BSD" actually refers to

BSD is not one operating system. The name covers several independent projects, each with its own release cycle, installer, and priorities:

All of them descend from the Berkeley Software Distribution of Unix, and all ship a complete base system: kernel, C library, shell utilities, and often a compiler and server daemons, maintained as one unit.

How BSD differs from Linux

Kernel and userland are developed together

On a Linux system, the kernel comes from one project and the userland tools usually come from GNU, BusyBox, or another provider, assembled by a distribution. BSD projects develop the kernel and the base userland in a single source tree and release them together. The practical effect is that a base install is internally consistent, and upgrading the system means upgrading the whole base rather than tracking kernel and userland versions separately.

Licensing

BSD operating systems use permissive licenses (the BSD family of licenses, plus others depending on component). Linux uses the GPL for the kernel. The difference matters mostly if you plan to redistribute modified code: permissive licensing places fewer conditions on derivative works. For an end user running the system, licensing rarely changes day-to-day behavior.

Hardware support model

Linux hardware support often arrives through vendor-contributed drivers in the kernel tree. BSD projects maintain their own driver trees, so support for a given chipset or laptop model can lag, and some devices are supported on one BSD and not another. This is the single most important practical check before committing to BSD on a specific machine: verify that your storage controller, network adapter, graphics chip, and Wi-Fi card are supported by the version you intend to run.

Package management and third-party software

Each BSD has its own approach. FreeBSD offers the pkg package manager with prebuilt binary packages, plus the Ports Collection for building from source with local options. OpenBSD uses its own package tools and releases packages in step with the OS version. Software that is written for Linux—especially anything relying on Linux-specific kernel interfaces—may need a compatibility layer or may not run at all. Check the project's package repository for the applications you actually need before deciding.

Where BSD is commonly used

• Servers and hosting: FreeBSD is a long-standing choice for web and file servers, partly because of its networking stack and the integrated base system.
• Networking appliances: OpenBSD's default security posture and its firewall and routing tools make it a frequent pick for firewalls, VPN endpoints, and routers.
• Security-sensitive systems: OpenBSD's audit practices and default hardening are the reason many people choose it.
• Older or unusual hardware: NetBSD's portability means it can run on architectures that other systems have dropped.
• Desktops: possible and used by experienced users, but this is where the hardware-support gap is felt most, particularly with recent laptops, Wi-Fi, and graphics.

Practical considerations for newcomers

1. Check hardware compatibility first. Look up your exact machine or components in the hardware notes for the specific BSD release you plan to install. Community-maintained hardware databases and the project's own supported-hardware lists are the places to start.
2. Confirm your applications exist. Search the package repository for each tool you rely on. Browsers, office suites, and development toolchains are generally available; niche or Linux-only software may not be.
3. Expect to read documentation. The handbooks published by FreeBSD and OpenBSD are thorough and are the primary reference for installation and configuration. Community forums are smaller than Linux's, so self-sufficiency helps.
4. Plan the install around the base system. Because the base is managed as a unit, learn the project's upgrade procedure before you need it, rather than treating it like a Linux distribution's package upgrade.

Deciding between BSD and Linux

Choose BSD when a consistent, conservatively maintained base system, permissive licensing, or a specific project's strengths (OpenBSD's security defaults, FreeBSD's server tooling, NetBSD's portability) match your goal, and when your hardware and software are known to be supported.

Choose Linux when you need the widest hardware coverage, the largest software ecosystem, or vendor support for a particular device or application. For a first desktop install on a recent laptop, Linux is usually the lower-friction path; BSD becomes attractive once you have verified that your specific components are supported and you value the integrated design.

Unix is a family of multitasking, multi-user operating systems, not a single product you download. When an open-source game like Heroes lists "Unix" support, it usually means the source code can be compiled and run on Unix-like systems such as Linux, FreeBSD, Solaris, SunOS, or IRIX. Whether you can actually play depends on whether a binary exists for your system or whether you can build the game from source with a compiler and the required libraries.

Unix as a family, not a download

Unix began as an operating system developed at Bell Labs and later branched into many commercial and academic variants. Over time, the term came to describe both:

• Systems derived from the original Unix code, such as Solaris or IRIX.
• Unix-like systems that follow similar design conventions and APIs but were written independently, such as Linux and FreeBSD.

The Heroes project page reflects this breadth. Its keyword list includes unix, linux, windows, mingw32, solaris, sunos, freebsd, and irix — a mix of operating system families and specific platforms. That list is a signal of where the code has been ported or is expected to build, not a promise that every listed system has a ready-to-run package.

A useful way to think about it: Unix is closer to a specification and a design tradition than to a single installer. Each implementation — Linux, FreeBSD, Solaris — has its own kernel, tools, and package management, even though they share concepts like a hierarchical file system, processes, and a command-line shell.

Why projects list Unix-like platforms separately from Windows

Open-source projects often separate Unix-like targets from Windows because the build and runtime environments differ substantially:

For Heroes, the presence of mingw32 alongside unix, linux, and freebsd suggests the project maintained separate build paths for Windows and for Unix-like systems. Listing them separately helps users find the right download or build instructions instead of assuming one package works everywhere.

Unix is not one downloadable thing

Because Unix is implemented by many systems, there is no single "Unix download" that covers all of them. A game that supports Unix-like systems may provide:

• Prebuilt binaries for specific systems or distributions.
• Source code that you compile yourself.
• Both, with binaries covering the most common platforms and source covering the rest.

The Heroes page describes the project as concentrating on "cleaning the code and porting the game to the various operating systems available," with the goal of a version 1.0 as a "clean and portable base." That language indicates portability work was ongoing rather than finished, so availability of ready binaries for any given Unix-like system should be checked on the download page rather than assumed.

How portable source code gets built on Unix-like systems

When a project distributes source code rather than binaries, running it on a Unix-like system generally follows this pattern:

1. Confirm prerequisites. You need a C or C++ compiler, a build tool such as make, and any libraries the game depends on. The exact list comes from the project's build documentation.
2. Obtain the source. Download the source archive from the project's download page.
3. Configure the build. Many Unix-oriented projects include a configure script that checks your system for compilers and libraries and generates build files. The expected result is a report of what was found and what is missing.
4. Compile. Running make builds the executable. Errors at this stage usually point to missing headers or libraries.
5. Run and verify. Launch the resulting binary. If it starts and reaches the main menu, the build succeeded; missing data files or sound libraries typically show up as startup errors.

For Heroes specifically, the page mentions 12 original sound tracks, 94 levels across 10 tile sets, and a level editor, so a working build also needs the game's data files in place. The page does not document the exact build commands, so those should come from the manual or the source archive's own instructions.

What Unix support means in practice for Heroes

The practical takeaway for a player is conditional:

• If a binary exists for your system, download and run it, checking that required libraries are installed.
• If only source is available, you need a compiler and build tools, and you should expect to resolve dependency issues yourself.
• If your system is listed only as a keyword, treat that as a hint that the code has been considered for that platform, not as a guarantee of a working package.

The Heroes page also notes that the original MS-DOS version is unmaintained and "should be considered obsolete," and that the current code is distributed under the GNU General Public License version 2. That license means the source is available for building and modification, which is exactly what makes porting to multiple Unix-like systems feasible in the first place.

In short, "Unix support" for a game like Heroes describes a family of target systems and a source-based path to running the game, not a single download that works everywhere. Check the download page for your specific system, and be prepared to build from source if no binary is provided.