We also need a user for the netboot clients to connect as. Sudo chmod +s /netboot/Images /netboot/Clients Sudo chmod g+w /netboot/Images /netboot/Clients Sudo chgrp adm /netboot/Images /netboot/Clients Sudo mkdir /netboot /netboot/Images /netboot/Clients The commands below create the needed paths and set appropriate permissions so they are group-owned by the admin group, group writable and ownership/permissions are sticky(inherited) when new files are created. Anyway we are going to put everything under the /netboot folder. I recommend you use a dedicated hard drive/partition for this and set it up to mount at boot at the appropriate location, but this is up to you and an exercise for you to perform yourself. Next we need to create a place to store all the netboot files. Sudo apt-get install tftpd-hpa apache2 apache2-utils netatalk git nfs-kernel-server python-configparser Now lets add in some packaged requirements: During the install process we installed the OpenSSH server and nothing else. No GUI to take up space or CPU cycles and a really small footprint to my VM system. Okay, so we start with an Ubuntu 14.04 Server install. Samba for SMB connections (my directory server does not currently have the Samba schema, so I have not installed it yet).Network volume access (AFP and SMB) for loading NetBoot images.Ubuntu 14.04 (what is with Ubuntu and their minor version numbers?).
So let’s just see if Linux comes to the rescue.įor those that just want to check out the BSDP project, head over to github and you can check out the code there. I have heard rumor that Deploy Studio can act as a BSDP server (Apple’s netboot protocol), but it is also a bit overkill for what I need. We have a number of NetInstall images and a single “thin-client” image for System Diagnostics (has a few helpful utilities).
How to netboot on mac for mac#
So in my continuing deletion of all things Apple Server, I am tasking myself with also getting rid of our BSDP NetBoot server for Mac clients.
0 kommentar(er)
