Home Forums Mac Software Mac Operating Systems Permissions Horror, Apple inserting Read only into

Log onto the desktop with the DESKTOP username and password, not with the LAPTOP username and password. That should solve the problem.

Tacit, thanks!

What am I logging onto to? Lost me from the get go.

(sorry for being so lame -- you guys are genius compared to me....)

You have used the words "network" and "sharing" in some of your previous posts. So... does not the act of 'logging in' also occur within this troublesome scenario at some point? [i.e., when mounting the share.]

Shouldn't it be you who explains to us what (exactly) you're doing in the first place? [i.e., add a little more description so folks can get a better visual of the setup.]

Sorry guys my fault. Being that it's my intern who is logging on, I did not get my head around that. Ok, so the intern logs on. She sees my network name in the dropdown list.
I then give her the password (no user name), just the password to get online at my house/ home business. that's it. JUst like when you go to Starbucks or Coffebean. you are logged on now to the internet. From there most interns can then get into my designated shared folder. She gets in, but for some reason 3 or the 6 files in a particular folder are not showing on here little windows netbook. The permissions have been double checked, those files are ok, all say read/write like the other three that are showing up.

The normal practice would be to give the intern an account and password to log onto. The account would be the same account the files are stored under unless the files are on an external drive that is set to ignore permissions and then it could be any account. That way she appears as a normal user on the host system and would have all the privileges of that particular user account.

Just a thought, I know you do not want to invest much, or any, more money into this system, but given what you are trying to do you might consider a Mac Mini Server that comes with Snow Leopard Server installed. It would take a bit more to setup initially, but it would neatly solve all of these permission issues you are having with co-workers, interns, etc. The server software is specifically designed for the task you have in mind, and in the long run could make your life much easier.

Kevs, does your post #15026 belong here in "Permissions Horror, Apple inserting Read only into" or should it be in Issue with someone on Windows getting with my netw?

Cyn, the issues cross pollinate. I'm not sure they are the same.

I do get my Mac automatically making files read only after I've made them read write on the everyone. Still don't know why.

This issue is about my intern can get to a folder with file sharing, but several of the excel in that folder are not showing. it's bizarre.

Joe/ Tacit: The intern does not log into my computer. That's not how this work. I have a router -- again it's like going into a coffee shop, you get a single 7 digit password and they are on your network for internet. Then via file sharing I've designated a folder for the intern to access.

Why can she get into the folder and access 3 files but the other 3 don't show?
Thanks all for your great help!

(this may not be solvable, but it's good to ask)

What folder, where? Name its path (and tell us which "machine" it's on).

Better yet, list that folder via:

ls -alOe /path/to/the/folder

[you can get the proper pathname using copy/paste (or drag-n-drop) from Finder to Terminal.]



The listing i requested might just answer that question... if you're willing.

I don't know if this helps Hal, it's just, ya know:

Volumes/main hardrive/ documents/List/Projects

Couldn't he turn the trick at less cost by upgrading to Lion and its included Server component?

Oh it helps... as it shows to what extent you're sincere about solving this issue. (again, most of my requested info was ignored... so perhaps i should do the same to this thread).

Hal, remember, I'm not that intelligent!

A lot of this stuff goes over my head. Honestly, it may be a Gremlin, think about, she see's 3 files in the folder but not the other three.

What are the odds you guys, brilliant as you are, are going to know why that is? But I gotta ask, you never know.

Yeah but... you won't even run a simple (and totally safe) terminal command to allow us to see anything. You just want folks to guess, based on as little information as possible. Seems most of your "efforts" go into attention seeking, rather than learning and/or problem solving.

i say again:

ls -alOe /path/to/the/problem/folder

...where "/path/to/the/problem/folder" is a simple matter of copy/paste (or drag-n-drop).

Too much for you?
Too bad.

For the benefit of kevs, an admitted 'out of this league'r, how about being a tad more specific yourself? For instance, by giving the exact text to copy/paste into the Terminal window (/path), followed by drag & drop after that text in the Terminal window of the target folder via the Finder?

Keep in mind that for someone who's never done it or has little if any experience with Terminal, this can be quite confusing/scary, particularly when it's not clear exactly what to expect, or when you've made an error, and what (not) to do then.

Since you didn't...

kevs:

1. Launch /Applications/Utilities/Terminal.
2. Copy this text and paste it at the prompt, i.e. the little grey bar that comes after kevs$.
   Code:

   ls -alOe

3. Type a single space after the pasted text.
4. Drag the folder in which your files are into the Terminal window (and its path will automatically be entered).
5. Hit "Return."
6. Copy Terminal's results.
7. Paste them into a reply post.

Now, let's see.

I know you two are really into the Terminal. For me something has to be life and death to take terminal commands on faith with no context or explanations -- as it's so draining.

...it's less draining if you just think of it as following a recipe to bake a cake.

You've gotten some very thoughtful and detailed suggestions that will provide an insight into your long-standing issue with permissions....what have you got to lose?

If you haven't heard of it before, you might take a look at Bwana, which brings the man (Unix manual) pages to your browser and will enable you to understand Terminal commands that have been posted so you don't have to take them on faith.

what is man page.

also, there is the idea -- do you really know this will work?

The "man pages" are the UNIX manual that is stored on your HD as part of OS X; in it you can look up the functionality of commands and their options.

For instance, Hal posted


in which "ls" is the command and "alOe" are the options; this is how man describes "ls" (We'll ignore the options for now.):


> also, there is the idea -- do you really know this will work?

Terminal is pretty straightforward; you enter a command and it either runs and generates results or tells you "No such...."

So to answer your question, yeah; it works by default as long as you enter a correct command. (But you always want to copy and paste your commands!!!)

The 'man' page stands for the (Unix) 'manual', which is built into Mac OS X, but only accessible via this route (that is, without a 3rd party GUI).

At this point we need information about the problem, so that its nature becomes clear(er). That information will then either suggest a solution, or another question to pinpoint things further. This approach is time proven and will work.

What do you mean by "work"?

All it's supposed to do is produce a list of the items in that folder. The intent is simply to provide us with detailed information about the ownership & permissions on those items (that goes way beyond Finder's measly Get Info window), with which to answer the question you asked. [or at least supply some food for thought]