Mac OS and FreeBSD (or Linux or whatever) complement each other quite nicely. Mac OS for usability,.nix for raw power.-Re:Use NetBSD code? (Score: 3) by seebs on Monday May 22, 2000 @08:12AM Homepage. The main obstacles are technical and political; the NetBSD people have insisted on a few substantial differences in kernel structures.
- FreeBSD is a free and open-source Unix-like operating system descended from the Berkeley Software Distribution (BSD), which was based on Research Unix.The first version of FreeBSD was released in 1993. In 2005, FreeBSD was the most popular open-source BSD operating system, accounting for more than three-quarters of all installed simply, permissively licensed BSD systems.
- FreeBSD 10: # bless -device /dev/disk0s1 -setBoot -legacy; Reboot to FreeBSD. If you want the Mac Mini to power on automatically after a power failure, you can install the sysutils/pciutils port which will give you setpci. Put the following command in a startup script like /etc/rc.local to make the Mac Mini boot when power is restored.
21.2. FreeBSD as a Guest on Parallels for Mac OS® X
Parallels Desktop for Mac® is a commercial software product available for Intel® based Apple® Mac® computers running Mac OS® 10.4.6 or higher. FreeBSD is a fully supported guest operating system. Once Parallels has been installed on Mac OS® X, the user must configure a virtual machine and then install the desired guest operating system.
![Mac Mac](/uploads/1/1/9/6/119611765/857475293.png)
The first step in installing FreeBSD on Parallels is to create a new virtual machine for installing FreeBSD. Select FreeBSD as the Guest OS Type when prompted:
Choose a reasonable amount of disk and memory depending on the plans for this virtual FreeBSD instance. 4GB of disk space and 512MB of RAM work well for most uses of FreeBSD under Parallels:
Freebsd Mac_ntpd
Select the type of networking and a network interface:
Save and finish the configuration:
After the FreeBSD virtual machine has been created, FreeBSD can be installed on it. This is best done with an official FreeBSD CD/DVD or with an ISO image downloaded from an official FTP site. Copy the appropriate ISO image to the local Mac® filesystem or insert a CD/DVD in the Mac®'s CD-ROM drive. Click on the disc icon in the bottom right corner of the FreeBSD Parallels window. This will bring up a window that can be used to associate the CD-ROM drive in the virtual machine with the ISO file on disk or with the real CD-ROM drive.
Once this association with the CD-ROM source has been made, reboot the FreeBSD virtual machine by clicking the reboot icon. Parallels will reboot with a special BIOS that first checks if there is a CD-ROM.
In this case it will find the FreeBSD installation media and begin a normal FreeBSD installation. Perform the installation, but do not attempt to configure Xorg at this time.
When the installation is finished, reboot into the newly installed FreeBSD virtual machine.
After FreeBSD has been successfully installed on Mac OS® X with Parallels, there are a number of configuration steps that can be taken to optimize the system for virtualized operation.
![Freebsd For Mac Freebsd For Mac](/uploads/1/1/9/6/119611765/749904200.png)
- Set Boot Loader VariablesThe most important step is to reduce the
kern.hz
tunable to reduce the CPU utilization of FreeBSD under the Parallels environment. This is accomplished by adding the following line to/boot/loader.conf
:Without this setting, an idle FreeBSD Parallels guest will use roughly 15% of the CPU of a single processor iMac®. After this change the usage will be closer to 5%. - Create a New Kernel Configuration FileAll of the SCSI, FireWire, and USB device drivers can be removed from a custom kernel configuration file. Parallels provides a virtual network adapter used by the ed(4) driver, so all network devices except for ed(4) and miibus(4) can be removed from the kernel.
- Configure NetworkingThe most basic networking setup uses DHCP to connect the virtual machine to the same local area network as the host Mac®. This can be accomplished by adding
ifconfig_ed0='DHCP'
to/etc/rc.conf
. More advanced networking setups are described in Chapter 31, Advanced Networking.
FreeBSD supports security extensions based on the POSIX®.1e draft. These security mechanisms include file system Access Control Lists (Section 13.9, “Access Control Lists”) and Mandatory Access Control (MAC). MAC allows access control modules to be loaded in order to implement security policies. Some modules provide protections for a narrow subset of the system, hardening a particular service. Others provide comprehensive labeled security across all subjects and objects. The mandatory part of the definition indicates that enforcement of controls is performed by administrators and the operating system. This is in contrast to the default security mechanism of Discretionary Access Control (DAC) where enforcement is left to the discretion of users.
This chapter focuses on the MAC framework and the set of pluggable security policy modules FreeBSD provides for enabling various security mechanisms.
Freebsd Format Disk
After reading this chapter, you will know:
- The terminology associated with the MAC framework.
- The capabilities of MAC security policy modules as well as the difference between a labeled and non-labeled policy.
- The considerations to take into account before configuring a system to use the MAC framework.
- Which MAC security policy modules are included in FreeBSD and how to configure them.
- How to implement a more secure environment using the MAC framework.
- How to test the MAC configuration to ensure the framework has been properly implemented.
Before reading this chapter, you should:
- Understand UNIX® and FreeBSD basics (Chapter 3, FreeBSD Basics).
- Have some familiarity with security and how it pertains to FreeBSD (Chapter 13, Security).
Warning:
Freebsd Mac Framework
Improper MAC configuration may cause loss of system access, aggravation of users, or inability to access the features provided by Xorg. More importantly, MAC should not be relied upon to completely secure a system. The MAC framework only augments an existing security policy. Without sound security practices and regular security checks, the system will never be completely secure.
The examples contained within this chapter are for demonstration purposes and the example settings should not be implemented on a production system. Implementing any security policy takes a good deal of understanding, proper design, and thorough testing.
Freebsd Mac Mini
While this chapter covers a broad range of security issues relating to the MAC framework, the development of new MAC security policy modules will not be covered. A number of security policy modules included with the MAC framework have specific characteristics which are provided for both testing and new module development. Refer to mac_test(4), mac_stub(4) and mac_none(4) for more information on these security policy modules and the various mechanisms they provide.