That's not Unix nor part of the SUS. It's not a Unix problem, it's an OS X problem.
None of those are Unix either. They're very much OS X problems.
Nope, they don't. Do you know what Unix is and what the SUS is ? If you said something like the open() syscall not returning EEXIST when passed O_CREAT and O_EXCL, then yes, that would be a Unix problem.
LOL. Maybe you should start by defining WTF you mean by OSX. Because OSX is a general abstract term for the entire operating system. Is "LS" an OSX command too? You're getting into programming calls now and playing games with semantics left and right. WTF does that have to do with a Mac consumer trying to deal with an OS problem? The "Mac" is supposed to be 100% GUI to the consumer. If I have to go to the Unix shell to fix a problem, particularly with programs that typically only come with a Unix-type OS under normal circumstances, I don't call that an OSX specific problem. It's an app problem, but an app associated nearly exclusively with Unix-type operating systems. Beyond the GUI panes in preferences, all those programs I mentioned are standard Unix programs and contain command interfaces at their heart. They are certainly not Cocoa problems or any sort of GUI problem. Using the CLI in OSX requires some knowledge of the Unix shell structure usage.
In other words, you apparently want to label those sorts of problems an Apple when to me if it looks like a duck, quacks like a duck and craps on my car like a duck, I call it a flipping duck. If the solution to a given problem is identical in OSX as to say Linux and involves the CLI, I'd call it a Unix-type problem, not an "OSX" one since there's nothing specific to the Mac or OSX about the core Samba services or even the file permissions, for that matter. They are common to Unix operating systems and their solutions are typically common as well. You can find the answer on any Unix or Linux type message forum since they all use many of the same basic applications and services underneath.
Sounds like you haven't spent quite enough time to be qualified to discuss it though. You don't seem to quite grasp what is and isn't a Unix implementation problem.
I'm not a Unix admin. I never claimed to be. But if you think you're having a hard time relating what you're saying to someone that's played with desktop Linux a lot over the past decade, imagine a typical Mac user trying to grasp WTF you're talking about because this all STILL comes back to you telling Mac users to fix their problems (whatever they may be; it's completely abstract at this point) instead of going to a backup or a reinstall. Do you even know what a 'typical' Mac user's knowledge level of computers is? I can't say that I do, but I'd wager it's less than a typical Windows user based on the Mac's reputation for being friendly to non-computer types.
Oh, I relate to normal users.
Nothing you've said in this thread or any recent thread I've seen you in demonstrates that
one iota. You talk down to everyone and have an arrogant attitude that ranks up there in the top 10 on the entire forums.
I understand them perfectly. I've dealt with them since the 90s. A little searching around the Internet could do them some good but they prefer to lay cash down to get their stuff repaired for them.
You understand
everything perfectly. You are god, right? I've got some existential type questions for you later....
But why are you comparing the Macrumors crowd to normal users ? Normal users don't reinstall their OS.
And what is and who is a "normal" user? You're throwing extremely abstract terms around left and right in this thread without defining them. I've never "reinstalled" OSX. I have restored from backup that one time Apple's own software update screwed the pooch, though. If I hadn't had a backup, I may very well have reinstalled barring locating another solution within a reasonable length of time. Like I said before, choosing a solution should factor the time it takes YOU personally to fix the problem. If that fix takes longer than a reboot from backup or even a reinstall, why would one want to take the longer amount of time? What you can do in 10 minutes and what an typical Mac user can do probably aren't the same thing.
You claim to understand typical users perfectly, but I see no evidence of it based on your one-shoe-fits-all matter-of-fact replies and that goes for every thread and every topic. Your answer is always right and everyone else that disagrees is a moron.
🙄
People who do a notch above normal users. These guys pretend they have "technical" know-how about this stuff, yet their solution to about every obscure error message popping up in the syslog is to do a clean install. Frankly that's just absurd. These are the guys I was pointing out. The "OS reinstallation fixes problems!" crowd that want to do "Clean installs of Lion!". Not. Your. Average. User.
While I've never re-installed OSX to fix a problem (other than buying a new computer and 're-installing' the same software I have on an existing one), it is incredibly easy to install most OSX Apps by simply copying them straight over to the Applications folder (barring the few that have installers) so I can see why someone with no other knowledge might not mind 'fixing' their install by starting over. To them, it's simpler than having to take the time to learn more about the problem or the OS. I certainly cannot speak for others on this matter. It's certainly simpler than reinstalling all one's software with Windows.
You, however, have some pre-defined definition of "normal" and "average user". Short of a poll, I couldn't say what is normal or average for the Mac. I can only gauge a certain amount based on typical replies on these forums and yet these forums represent people that are interested in Mac news. What about those using the Mac just to run a specific App like say perhaps Logic Pro? Users that just use the Mac to do the Internet and e-mail? They're not really represented on here either. Thus this notion of a typical or average Mac user is pretty elusive short of an actual study (or at least a reasonable scale poll) to conclude what level of knowledge they actually have. I certainly wouldn't prescribe to a one-shoe fits all outlook when addressing people on these forums. One shoe does
not fit all. A primary difference between you and I is that I recognize that and you clearly do not.
If you're reinstalling Lion, you had the package at any point, or how would you have installed it in the first place ? You don't read much of the posts now do you ? The sub-thread was about reinstalling lion on a failed drive.
That's odd. The thread title is "Lion Clean Install Requires Snow Leopard Disk?" not "REinstalling Lion. How do I do it?" Are you sure you're in the right thread?
🙄
A clean install does not imply one already has Lion at all. In fact, no one has the final release of Lion yet. The original article that started this post talks about how to upgrade to Lion for a clean install. NOWHERE does it say how do a clean install AFTER you downloaded Lion already.
🙄
Your native language isn't English right ? Because you have a serious lack as far as reading comprehension goes.
How odd, I was just about the say the same thing to you because you don't even know WTF the thread is about.
😛