AFP548 Changing the world one server at a time.

Firstboot

Home › Forums › Software › InstaDMG › Firstboot

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #380074
    bw38
    Participant

    I gave up on this a while back because I wanted to make more progress on the rest of the image. So I’m at a point now where I’m getting very close to creating an image that’s about complete. However I still cannot get Firstboot.pkg to work.

    I followed the instructions to the letter. I don’t understand what I could be doing wrong. Should the firstboot.pkg go last in the workflow or should it be very early in the workflow? Currently I have it set to be the last item in my workflow.

    Does it matter that I don’t have ARD?

    There are only three things I’d like to change that the firstboot script seems to contain:
    -ability to set sleep time
    -change log in screen
    -set time zone via network location

    I have just a few weeks left and need wish to get this right.

    For the record I followed this guide: http://www.osxdeployment.info/wiki/Firstboot_Package_Guide

    #380075
    tristan_mason
    Participant

    I had a similar experience until I realized I needed to tick the check box to make it executable in package maker. Then everything worked. It’s the same as the 644 bit in the terminal but the easy way.

    Hope this helps.

    Tristan

    #380076
    bw38
    Participant

    tristan_mason wrote:

    I had a similar experience until I realized I needed to tick the check box to make it executable in package maker. Then everything worked. It’s the same as the 644 bit in the terminal but the easy way.

    Hope this helps.

    Tristan

    Tick what box? Could you show me a screenshot?

    #380079
    tristan_mason
    Participant

    I’ll try and describe it first. Am not sure if the server will handle a screen shot.

    Open the “firstboot.pmdoc” in PackageMaker. Click on the disclosure triangle in the left hand “Contents” pane to reveal the two files. Select the first file (now named to your co/institution and select “Contents” in the right pane. Select the file below then click the “Execute” check box for “Owner” and “Group”. Repeat for the second file in the contents pane. Save, build, include and test.

    Let me know how that goes. If not I can email you screens from my setup.

    Some knowledge with PackageMaker is really helpful for this whole process as is Composer. Composer saved me a great deal of pain and all for under a hundy.

    Regards

    Tristan

    #380104
    bw38
    Participant

    Just wanted to confirm that this worked. The guide is incorrectly saying it needs to be set to permissions 644 when in fact it needs to be 775. At least that’s what seems to have finally worked for me.

    #380106
    dead2sin
    Participant

    I’ll fix it 🙂 I changed it to 644 after someone said what I had was wrong. If 775 works, then we’ll go with that.

    Nate

    #380122
    bw38
    Participant

    Sorry I need to rectify my last statement. It wasn’t 775 that worked. It was 754 permissions that worked in the end. Not that I doubt 775 would work too, but no need for extra permissions if not necessary right?

    #380123
    dead2sin
    Participant

    Fixed. Thanks 🙂

Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.