I was recently building some preflight scripts and was looking to record some information about a machine live, before proceeding with a script. I found the cheapest way to determine information about architectures and chipsets when scripting preflight scripts for OS X to be the arch and machine commands respectively. For example, to verify the architecture is i386, use the arch command with no options: /usr/bin/arch Which simply outputs “i386”: i386 To check the machine type, simply use the machine command: /usr/bin/machine Which outputs as follows: x86_64h
-
-
Allow Diskless NetBoot From the Command Line
Client systems don’t have to have drives. Nor should they, in certain circumstances. Therefore, diskless NetBoot has been a part of OS X since the early beginnings. And it’s great provided you have the Server Admin application handy. But if you want to enable/control diskless NetBoot without Server Admin then you’re going to need to use the command line. Each of your NetBoot images will be stored in an array, which can be seen by running the serveradmin command, along with the settings option and then the net boot service, as follows: serveradmin settings netboot Locate the netBootImagesRecordsArray, which shows the images that are served up on the server. Find…
-
Xsan: Designing an Xsan
Planning an Xsan is perhaps the most complicated part of any deployment. First, start with one of two objectives, speed or size (or both). How big does the SAN need to be and what speeds does the SAN (aggregate speed of all clients) need to be able sustain? That becomes the primary design consideration. Beyond that, you’ll also want to plan how it will get backed up and when, the makeup of the clients (Mac, PC, Linux), how permissions will get handled for new files written to the SAN, etc.