First.surname (and so on) When I connect to the file server using my non-administrator credentials, I can see the 'Shared' and 'Staff Shared' folders, however Users$ isn't there (Because obviously the $ makes it hidden). My credentials only give me permission to my Home Drive: /Fileserver/Users$/Staff/first.surname. I don't have permission for the parent directories Users$ and Staff! With Windows, I can put the path to my HomeDirectory into Run and then authenticate with my credentials and it works!
But I can't do this with my Mac. My original intention was to actually set these up to mount via AppleScript, so that I could have Staff Shared, Shared, and my Home drive (inside Users$/Staff) mounted with one click. Shared and Staff Shared mount without issue this way, but I can't for love nor money mount my home drive. Even If i set the full path of my home drive up, It tries to Mount, and instead mounts the Users$ directory, but it has the little No Entry sign and I can't open it. Does anybody have any suggestions? (also code for AppleScript would be appreciated, I'm a bit new to AppleScript) PS.
IT Support won't be able to help because they have no clue about Macs! Click to expand.Are you in IT or management? Does senior management out rank IT in your organization? Why is IT so afraid of Macs? You would think they would be open to better things and new challenges.
Application's data folder in Mac. Ask Question. Users userName AppData Roaming appName? I need a directory that won't cause permission problems to store the updateable part of my application so I can automatically download and override my content. How to install Java 8 on Mac. How, When, and Why to Repair Disk Permissions on Your Mac Chris Hoffman @chrisbhoffman September 8, 2014, 4:04am EDT “Try repairing your disk permissions” is a standard Mac troubleshooting tip that’s been going around forever.
Bottom line is you're not going to make this work without help from IT, permissions on the share need changed. No other way around it. You likely only have traverse permission on the Users$ folder (which works great with Windows for security purposes), that should be bumped up to 'Read - This folder only'. That.or create a new share point like I advised earlier. Click to expand.I'm guessing the OP is a teacher or other faculty member.
The reality is that they probably don't want to bother setting up something special for a couple users which is actually reasonable however annoying it might be. They could also be less flexible because of internal politics and/or they don't like Macs or at least don't want to manage two/three different platforms.
At work our IT department hates the fact we have computers on XP 32bit, XP 64bit, Server 2003 64bit, Vista 64bit, and Win 7 64bit. Really the problems fall into Win XP/Win Vista/Win Vista & Win 7 problems, but having to keep track of three different sets of fixes for things is kinda annoying.
I'm not sure how important the issue is, but you could try Dave and see if it works: They have a free trial I believe. Are you in IT or management? Does senior management out rank IT in your organization?
Why is IT so afraid of Macs? You would think they would be open to better things and new challenges. Bottom line is you're not going to make this work without help from IT, permissions on the share need changed. No other way around it. You likely only have traverse permission on the Users$ folder (which works great with Windows for security purposes), that should be bumped up to 'Read - This folder only'. That.or create a new share point like I advised earlier. Click to expand.And therein lies the problem with IT in so many organisations.
It's viewed as a problem to control/quash instead of as a partner in meeting the 'ends' of the organisation. I'm sick and tired of dinosaur execs that can't manage a simple home network but think they've got what it takes to make good unilateral decisions regarding corporate networks/systems and expect IT to simply fall in line. It is imperative that organisations have checks and balances in place to establish mutual accountability between IT and senior management, to encourage innovation and discourage either from running amok.
Unix for Mac OS X Users unlocks the powerful capabilities of Unix that underlie Mac OS X, teaching how to use command-line syntax to perform common tasks such as file management, data entry, and text manipulation. The course teaches Unix from the ground up, starting with the basics of the command line and graduating to powerful, advanced tools like grep, sed, and xargs.
The course shows how to enter commands in Terminal to create, move, copy, and delete files and folders; change file ownership and permissions; view and stop command and application processes; find and edit data within files; and use command-line shortcuts to speed up workflow. Exercise files accompany the course. Instructor. Kevin Skoglund builds custom web solutions at Nova Fabrica, and teaches web development to others at Lynda.com. Kevin Skoglund is the founder of, a web development agency specialized in delivering custom, scalable solutions using Ruby on Rails, PHP, SQL, and related technologies. Nova Fabrica clients include An Event Apart, Atlas Carpet Mills, Consulate Film, Gregorius Pineo, Maharam, Oakley, and The Bold Italic. Kevin is a lynda.com author with over 15 years of teaching and web development experience.
By: Sean Colins course. 6h 50m 28s. 2,080 viewers.
Course Transcript Now that we understand file and directory ownership, we are ready to look at file and directory permissions. The way that we see permissions is using the ls -la, just like we did for owner, to show us the full listing. Notice that I am already inside my user directory inside the unixfiles folder. In this listing, we just got through talking about the owner column, the column where it says kevin over and over and then the one where it says staff that's the group column. What I want to talk about now is that very first block there, all the rws and dashes that are there.
The very first character that you see we already said was an indicator of whether or not it's a directory, a file, or a link. D for directory, dash for file, l for symbolic link. The next nine characters after that is a notation that indicates the permissions for each of these files and directories. So before we can go about changing the permissions, we need to understand what these symbols are trying to tell us about the current permissions. So we need to know how to decode them. We refer to this system as being alpha notation because we are using the alphabet to describe the different permissions. Imagine that we have three categories.
We have our user. Which is our owner category. We are going to call it user. That's the first category. The second one is group, everyone who belongs to the group, and then the third category is other. That's everyone else who might have access to this file.
So user, group, and other are our three categories. And for each of them we can set three kinds of permissions. We can set read permissions, whether or not you can read the contents of a file or a directory.
Write, whether or not we can actually make changes to a file or make changes to a directory. And then execute, which for a file would mean that we could run it like a program or a script. For a directory, it means that we can search inside of it.
That's what it means to be able to execute on a directory. Notice in this table that I've got yes's and no's, indicating which permissions I'd like to give each of these three categories. So I want the owner of the file to be able to read, write, and execute a file.
The group, I'd like to just be able to read and write it. They can't execute it.
For everyone else, they can only read it. I don't want them to make changes.
So the only people should be able to make changes are the user and the group. So what we do for each of those, read, write, and execute, is we use the letter r, w, or x to indicate it and then we essentially add them up, so that what we end up with for the user is r, w, and x and they can do all three things. The group is r and w, but not an x and we put a placeholder dash in place of it.
For everyone else, they can only read. So they get r and two dashes. Notice now we have nine characters. You take all of those, you smash them together, and that is the nine-character permission string that we are seeing in our directory listing. So for example, if we take this file loremipsum.txt, you can see that its permissions allow me, the owner, to read and write to the file but not execute it and that's fine. Frequently we don't have execute turned on for files because it's not a script. It's a text file.
We don't need to run this. We are just going to be reading and writing to it.
For the group, which would be everyone in the group staff, which you'll remember included the other user I created, lynda, has the ability to read the file, but not to write to it or execute it, and then everyone else, everyone else who might ever come in contact with this file, is able to read it, but not to write and execute to it. Now you can see that, for example, that there is different permissions down here for the test directory. By default, directories are given the x so that they are searchable. It's essentially the same thing as being able to read, so we're able to search inside of it if we can read what's in it. So, by default, when you create a directory, it will include that as well.
But you can see that the group staff and everyone else can't write to this directory. They can just read it and search it. So let's see how this prevents people from having access. Let's take a look as a contrast.
Windows Directory Permissions
I have the other user on here, which is lynda, and now we can see the contents of her directory. Here is the directory. Remember this dot represents the current directory. So this is the directory we are looking at. We as part of her group have read and execute permissions on this directory. That's why we are able to see this listing.
Let's try now to do the same thing, but let's add pictures to begin. We are going to try and look at her vacation photos. Notice what the permissions are down here. She has read, write, and execute privileges, but that's it.
No one else has any privileges. So if we hit Return, it says 'Oops, permission denied.'
If we do cd into that folder, you will see it says 'Nope sorry, you can't get in there, permission denied.' So you see how it works.
You see how these keep us from getting into other people's stuff. So we can see her user directory, but we're not able to go any deeper into her documents or her movies or her pictures or anything like that. Practice while you learn with exercise files. Watch this course anytime, anywhere.
Directory Permission 563 For Mac Mac
Course Contents. Introduction Introduction. 1. Introduction to Unix 1.
Introduction to Unix. 2. Filesystem Basics 2.
Filesystem Basics. 3. Working with Files and Directories 3. Working with Files and Directories. 4. Ownership and Permissions 4.
Ownership and Permissions. 5. Commands and Programs 5. Commands and Programs.
6. Directing Input and Output 6. Directing Input and Output. 7. Configuring Your Working Environment 7.
Configuring Your Working Environment. 8. Unix Power Tools 8. Unix Power Tools. 9.
Useful Mac-Only Commands and Techniques 9. Useful Mac-Only Commands and Techniques. Conclusion Conclusion.