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. The 'classic' Mac OS is the original Macintosh operating system that was introduced in 1984 alongside the first Macintosh and remained in primary use on Macs until the introduction of Mac OS X in 2001. Apple released the original Macintosh on January 24, 1984; its early system software was partially based on the Lisa OS and the Xerox PARC Alto computer, which former Apple CEO Steve Jobs. Inside Macintosh covers only the classic Mac OS; a new set of documentation was introduced for Mac OS X. Initially this documentation included only the Carbon Specification identifying the APIs that were supported in Carbon and the Cocoa documentation inherited from OpenStep. To access your Brent desktop remotely use Using Desktop.gov.uk. You will need a computer that runs Microsoft Windows XP or later, or Mac OS 10.5 or later, access to the internet and a way to provide a remote access security number (see below).
Tom Sweeney, Brent Baude, Jhon Honce, Dan Walsh, Chris Evich, Lokesh Mandvekar, Urvashi Mohnani, Nalin Dahyabhai, Eduardo Santiago, Matt Heon, Ashley Cui, Sumantro Mukherjee, Scott McCarty, Shion Tanaka, Juanje Ojeda, Edward Shen, Reinhard Tartler
If you’re fixing a bug or an issue, please include a link to the commit message or at least in a comment.
Matt pulled up the release notes (https://github.com/containers/podman/blob/master/RELEASE_NOTES.md). Matt likes to get rleases out every 6 to 8 weeks
Added secrets, although not with crypto, manifest commands and prune have been added. The Podman copy command has been reworked heavily by Valentin Rothberg. Now you can copy to directories too now. You should now be able to copy anywhere in a container.
Also added U option for mounting volumes.
Matt then went over a number of bugs/issues about 50, with many fixes from the community and a small CVE.
More significant work in the next release coming up in
New Volume option.
podman run -it -v /tmp/data01:/data:Z –user 998:998 fedora sh
This showed that the wrong user (root) owned directories in the container.
Now with ‘U’ added to the volume specification.
podman run -it -v /tmp/data01:/data:Z,U –user 998:998 fedora sh
The directory and files are now owned by 998.
This can also be run with tmpfs volumes
podman run -it –rm –tmpfs /data:Z,U –user 998:998 fedora ls -la data
This also shows the directory has the right permissions. Ditto overlayfs.
Dan talked about some other use cases.
Brent Baude led off. Creating a Podman on Mac using a subcommand in pocman called “machine” building upon other efforts. The code is very modular. The initial implementation is Fedora CoreOS in the vm which is configurable.
Testing on X86 linux on Mac OS X8664 and aarch64.
Current implementation relies on qemu which currently has some platform dependencies.
Hurdle to resolve the networking on the VM and exposing services running in the container on the host.
Podman machine is upstream now and works, but no ability to expose services at this point. But you can build images and experiment with how it works.
Ashley did a demo running on her Mac.
Used the podman-remote machine –help commandpodman-remote machine init # pulled fedora coreos image
podman-remote machine init anothername # creates with the specified name.
podman-remote machine ls # shows the machines create
When you init the vm, it creates connections automatically.
podman-remote machine start # starts the VM
podman-remote machine ssh podman-machine-default # sshinto the machine
podman-remote pull alpine #failed with socket issue being chased.
Ashely tried a number of pulls and it finally worked after a number of attempts and tweaking.
The container runs on the VM, but you type on the Mac. It does work, but socket activation issues are being chased.
This is running on the Mac M1 now, and work in progress on Mac Intel based.
Questions on the systemd socket. The socket issue is likely due to Podman talking to systemd. Dan thinks it’s fixed upstream in systemd.
The demo showed “podman-remote”, but the final release will just be “podman”.
The user experience should be you would just install “podman” and everything needed will come along with that.
Dan asked about install: goal user experience is brew install podman
, podman machine init
, podman machine start
, and then you’re running as if you’re on a linux box.
Inside Macintosh is the title of the developer documentation manuals published by Apple Computer, documenting the APIs and machine architecture of the Macintosh computer.
The first Inside Macintosh documentation, for the Mac 128K, was distributed in two large binders with photocopied 3-hole-punched pages. Every few months, updated sections were distributed for insertion into the binders. Some of the original sections were written by very early members of the Macintosh group, including Chris Espinosa and Joanna Hoffman.
In July 1982, Caroline Rose was hired to take over the software documentation, while Bradley Hacker focused on documenting the hardware. In addition to being the lead writer, Rose edited Volumes I–III and was the project supervisor. In 1984, additional writers joined the effort, including Robert Anders, Mark Metzler, Kate Withey, Steve Chernicoff, Andy Averill, and Brent Davis.
Due to numerous last-minute software changes, the official version to be published by Addison-Wesley was delayed. In the meantime, a $25 Promotional Edition (known as the 'phone book edition' because it was published by phone book publisher Lakeside Press) became available in April 1985.[1]
Addison-Wesley published Volumes I–III in July 1985 in two formats: as three separate paperback books and as one hardcover book combining all three volumes. It was the official technical documentation for the original Mac 128K, the Mac 512K ('Fat Mac'), and Mac XL models.
Reactions to Volumes I–III were mixed. While many praised the documentation for its clarity, thoroughness, and consistency, others disagreed, particularly complaining about the lack of sample code.
Among the positive feedback were the following:
On the negative side:
These versions of Inside Macintosh were subsequently published by Addison-Wesley (with authorship attributed only to Apple Computer in general):
All of these volumes were designed to be read together; no information was repeated.[1]
Shortly after Volume VI was published, Apple revamped the entire Inside Macintosh series, breaking it into volumes according to the functional area discussed, rather than specific machine models or capabilities. In this form, the series was far more coherent and a much better reference for programmers. As new functionality was added to the classic Mac OS, new volumes (below) could be written without invalidating those published earlier—in contrast to the first series, which became increasingly out of date over time.
These related documents were also published:
In the late 1990s, Apple stopped publishing Inside Macintosh as a printed book, instead making it available as a CD-ROM at least since 1994,[5] as well as online. Since then, the CD variant has been phased out, though Apple developers can still receive online documentation as part of the developer CDs. In its online form, the information is much easier to maintain, but some developers still prefer a printed format.
Inside Macintosh covers only the classic Mac OS; a new set of documentation was introduced for Mac OS X. Initially this documentation included only the Carbon Specification identifying the APIs that were supported in Carbon and the Cocoa documentation inherited from OpenStep. Later, the Carbon Specification was refactored into the Carbon Reference, which actually documented the APIs (taking much content from Inside Macintosh). Today, the Carbon Reference and Cocoa Reference are bundled together in the ADC Reference Library.