Jump to content
InsanelyMac Forum
  • Announcements

    • Allan

      Solution to create a topic or post.   04/24/2018

      Hello guys. The majority of you are having issues to create a topic or post here. This are a problem with our current theme InsanelyMac.  Now the theme will be the Default IPS. Sorry for any inconvenience.
Sign in to follow this  
eddie11c

Script question

Recommended Posts

I am trying to add a script into an installer to make an alias. Can I not use the ln command in bash? if so is the usage different somehow? ln -s <target> <alias> is what i have tried, I get no error during the script, but also don't see any alias output. I can do the command just fine in terminal and I do require root authorization. Any ideas? I want to create an alias as opposed to installing a premade one..

Share this post


Link to post
Share on other sites
Advertisement

ln -s ${1} ${2} works in #!/bin/bash or #!/bin/sh on my machine.

 

In what context are you trying to use it?

Share this post


Link to post
Share on other sites

During my custom install DVD I want to create some alias'. I tried ln -s "$3/target" "$3/alias", and even tried pointing to the ln command /bin/ln, it doesn't spit out any errors about not finding the file or that it already exists, but yet there is no output that I can see. Maybe my syntax is incorrect. If you could post an example of what is working?

 

Lets make up a file called test that is located in /System/Library/Filesystems/Example of the target Volume $3 and want an alias created in the same volume in /usr/bin. ln -s "$3/System/Library/Filesystems/Example/test" "$3/usr/bin/test" but this is not working. Any help would be appreciated.

Share this post


Link to post
Share on other sites

Where in the installer will this command being called from?

 

InstallationCheck

VolumeCheck

preflight

postflight...Etc

 

Is volume referenced by $3 definitely mounted at the point in time in question?

 

When I said it was working in bash and sh, that was just a quick test from a shell script on my desktop, not from a running Installer. I will try again from my live/install memory stick.

Share this post


Link to post
Share on other sites

Okay, I'll build a pkg and try it. Back in a mo..... Yes, it works fine.

Share this post


Link to post
Share on other sites
Okay, I'll build a pkg and try it. Back in a mo..... Yes, it works fine.

 

And the syntax I had was correct? If so I will have to double check it again for a typo or something.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.



  • Posts

    • Monitor EDID often contains OEM string in Details Timing section. For example Extracted contents: header: 00 ff ff ff ff ff ff 00 serial number: 06 10 df 9c 00 00 00 00 1a 15 version: 01 04 basic params: 95 1d 12 78 02 chroma info: ef 05 97 57 54 92 27 22 50 54 established: 00 00 00 standard: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 descriptor 1: c2 23 a0 d4 50 84 1a 30 40 2a 36 00 1e b3 10 00 00 18 descriptor 2: 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 descriptor 3: 00 00 00 fe 00 4c 50 31 33 33 57 50 31 2d 54 4a 41 37 descriptor 4: 00 00 00 fc 00 43 6f 6c 6f 72 20 4c 43 44 0a 20 20 20 extensions: 00 checksum: 7a Manufacturer: APP Model 9cdf Serial Number 0 Made week 26 of 2011 EDID version: 1.4 Digital display 6 bits per primary color channel DisplayPort interface Maximum image size: 29 cm x 18 cm Gamma: 2.20 Supported color formats: RGB 4:4:4 First detailed timing is preferred timing Established timings supported: Standard timings supported: Detailed mode: Clock 91.540 MHz, 286 mm x 179 mm 1440 1504 1546 1652 hborder 0 900 903 909 926 vborder 0 -hsync -vsync Dummy block ASCII string: LP133WP1 Monitor name: Color Checksum: 0x7a (valid)  
    • "copy to clip board" - "скопировать" "log copied to clip board!" - "журнал скопированного"   First one is better.   Good! I think to reduce EDID as talking above. 
    • And my config.plist I will also try iMacPro1.1 SMBIOS on my build. This may help clarify something
×