The lsbom command is used to see a list of objects installed by the package. You can also see the options such as the permissions assigned to files by the package as they’re installed. For example, that Twitter app from the app store; to see what it installs:

lsbom /private/var/db/receipts/com.twitter.twitter-mac.bom

This package is installed by the Mac App Store. When run, packages installed by the Mac App Store should only contain objects within that applications .app bundle. That’s a pretty good bit of information, so you can also use the -s option to constrain the output to only see the paths of files (relative paths, of course). I’m usually a fan of getting more information than less, so I usually run it adding the -m option, which shows me those permissions.

lsbom /private/var/db/receipts/com.twitter.twitter-mac.bom

Note: You can also use the mkbom command to create new .bom files. As the man page for bom indicates, this goes back to NeXTSTEP and was extended for 10.0 and again in 10.3.Similar Articles:

• Deploy Final Cut Pro Fast
• Mass Deploy Parallels
• Mac OS X: Using the Command Line to Install a pkg
• Mac OS X Server: Installing the OS
• What's a Metapackage?

Luckily for my poor MacBook Airs, Apple thought of people like me when they wrote the Finder and invented something called Simple Finder which makes OS X even simpler than it is by default to use. To enable Simple Finder, just go to Parental controls, enable controls for a user and then check the box for Simple Finder. Or, if you have an entire population of users like me, who simply can’t be trusted with a full operating environment, you can send the InterfaceLevel key with the contents of simple (easy to remember for those of us who resemble said key) to com.apple.finder and restart our friendly neighborhood Finder:

defaults write com.apple.finder InterfaceLevel simple; killall Finder

Come to think of it, maybe I’m not so awful. Let’s say I want to turn that whole Simple Finder thing right back off. Well, all we have to do is delete that key we created and then restart the Finder:

defaults delete com.apple.finder InterfaceLevel; killall Finder

Actually, I am terrible with these things. So much so that it’s not appropriate for me to use a computer. Therefore, just take it away. I’ll be better off using that Samsung with Windows 8 for awhile. At least there, I won’t be able to get any of my apps open or find any of the administrative tools that could damage the computer!Similar Articles:

• Disable the Go To Folder Menu Item
• Mac OS X: Showing Invisible Files
• Finder: I Just Can’t Quit You
• iTunes High Contrast Mode
• Selecting Text in QuickLook

The one I think I was most interested in seeing is available right here, and I can embed it into my own site and watch it from here.

I will try and make the next one to do the presentation I’d planned on giving. This is a community I am very supportive of and love contributing to (although the next time someone uses “serial entrepreneur” as their job title I might not be able to suppress the eye roll + flutter combination – sry).Similar Articles:

• Apple Finally Finds YouTube
• iMovie: Publishing Projects to YouTube
• Fun with YouTube: Thru-you
• One Last MinneDemo For The Year In Minneapolis
• Robcop vs. Terminator

• Blue: The access point is booting
• Green: The access point has a valid IP address over the Ethernet interface and has a valid connection to HiveManager
• Yellow: The access point has an IP address over the Ethernet interface but is not yet connected to HiveManager
• White: The access point is connected to HiveManager and is in normal operating mode. All configurations, updates are applied. This should be the normal state of the device.
• Purple: The access point’s HiveOS has a software image that is in the process of being update.

Similar Articles:

None Found

That lifestyle worked for me for a long time. It kept me focused on work and learning. I bought into the notion that your brain gets imprinted a certain way when you learn things all hopped up on caffeine and nicotine. So I believed that I had to maintain.

I was wrong (don’t worry, I still believe in Jarmusch, despite how Ghost Dog turned out). Which is nothing new mind you. But this is a deeper, more long-term wrong. One that was decades in the making. How do I know I was wrong? Let me count the ways:

• One one-thousand: The soda doesn’t affect me. First of all, that’s in direct opposition to why you do it. And I still do, although I’ve managed to cut back and continue to do so. Second of all, the second I stopped drinking any soda after 5pm my sleep problems disappeared immediately. Oddly, Dr. Pepper stock has dropped…
• Two one-thousand: I’m a night owl. No, I’m actually not. After I dropped caffeine after 5pm I am in bed earlier and up earlier. I enjoy being up earlier in the morning. I am less grumpy when I wake up naturally and I have more time so I can go work out, have a more relaxed exit from the house with my daughter (she’s much less ornery in the morning when she isn’t rushed – OR AM I?!?!).
• Three one-thousand: Smoking makes me more social. No. Smoking makes me less social. I put a barrier around myself by smoking, seemingly unaware of the impact on propinquity with others. Or not consciously aware. Smoking also causes me to want to vacate my chair and to be honest, I do my best work in my chair, not outside smoking. And while I do occasionally meet people outside smoking, I meet far more when not smoking.
• Four one-thousand: I do my best work at night. Again, I have hit a new stride of sorts. You see, no one knows when I write my posts. They all go up at 6am or whatever time I want and they usually get released daily rather than in a burst of 10 one day and none for a week like I write them. Sure, I’ll go weeks without, especially while I’m working on me and not computers. But the beauty of a CMS is that I get to future post. I don’t write after midnight any more. In fact, I’m writing this post on an exercise bike.
• Five one-thousand: I don’t need to work out. Yes, I said exercise bike. You can re-read this section 10 times, but it will still say the same thing. Yes, getting up earlier and going to the gym or yoga every day of the week actually makes me happy. Clearly pacing while smoking is stoking the Fitbit Flex, but it’s not really doing me any good.
• Six one-thousand:  Trust the tech. Sure, the Fitbit and Nike+ can see that I’m taking steps which is probably why I don’t weigh 4 times what I do. But Fitbit tells me my sleep sucks when I have caffeine after 5 and that I feel much better when I burn more calories.
• Seven one-thousand: I don’t need food if I drink soda or coffee for breakfast. After 30 minutes on the elliptical the other day I had only burned half the calories in a can of Dr. Pepper. When I eat earlier in the day I feel better at bed time. Who cares what I can reason to myself, I actually feel better…
• Eight one-thousand: I need to stop reasoning crap to myself. When your alarm goes off in the morning and you hit snooze, you’re reasoning to yourself that you have a little more time. When you decide to eat that last slice of pizza knowing that even if you have Lactaid that you’ll have heartburn tonight you’re reasoning yourself into some good old fashioned acid reflux. When you work an extra 10 minutes rather than go buy flowers for your significant other, you’re reasoning yourself into divorce.
• Nine one-thousand: Focus. If I’m not staying up as much or getting into that laser focus at night then I can’t do my job or write books or write articles. Poppycock. When I drop the multi-threading that is induced by what I’ve come to look at as practically a caffeine driven mania then I have focus. And I’ll pit one hour of focus against 10 hours of delusional multi-tasking any day. I now want to do one task. It gets knocked out in a fraction of the time it used to. Then I want to do another. I want each task done well. See, I don’t have a context switch or hardware interrupts like a CPU does… Without that focus I haven’t grown in a long time. I’m glad to have it back. Now to set some boundaries on others to try and keep it…
• Ten one-thousand: But your concurrent computing techniques may be way better than mine. Your mind may be able to time share while still having plenty of memory protection. More power to your multithreaded self. I’m not saying anyone should mimic me or do as I say. I’m not even saying I won’t smoke tomorrow or that I won’t end up drinking 3 Dr. Peppers. I’m cutting back, being better, being happier and feeling better. That certainly doesn’t mean anyone else needs to. Yes, I live in the midwest now; no, I haven’t picked up a mean dose of the judgmentals. In fact, just because I wrote this, I think I’ll grab a Juicy Lucy tomorrow, for lunch, along with a milkshake!
  

  Yes, that is a burger with super fatty Wisconsin cheddar cooked in the meat and sometimes then with cheese and onions that have been sautéed in grease on top! In fact, the bun of one of these all by itself has enough butter to probably cost you a thousand calories!!! I like to focus on the lettuce. Iceberg is really good for you, right!?!?! If I can find a partner in crime I might even get a big order of friend onion rings or pickles! Nom nom nommer flippin’ nommers!

Thanks for reading my site. I suspect I’ll be writing it for a little longer than I’d previously thought. Unless the Juicy Lucy gives me a heart attack on the spot. In which case know I died a very happy man who was ironically a little more healthy than I was 2 months ago!

Note: This is one of those posts that is for me, not you. I am happy you stuck with it until the end. But I also fear that in having done so I may have actually reduced your IQ. Sorry about that. I’ll make it up to ya’ in Jägermeister.

‘Cause Jäger makes ya’ smarter!

• RFC2324
• Interviewing 99 for SysAdmins
• Upgrading to Mountain Lion Server
• A Well Caffeinated Command Line

When running /usr/sbin/sysdiagnose from the command line there are a couple of options. My favorite is -f (which I think must be short for favorite) which allows me to write to my file to a directory I specify rather than some random object in a tmp directory. You can also get even more output using -t. Verbose logging is obtained using -h and passing a pid will also provide information about the pid. So let’s say that process 10883 is giving me some problems. I could run the following to get some good output on my desktop:

sysdiagnose -h -t -f ~/Desktop

Anyway, hope you enjoy!Similar Articles:

• vnode
• Core Dumps in Mac OS X
• Opening a Terminal Window From, Well, Terminal
• Kickstarting ARD
• The iTunes Alarm Clock

Then, along came a script. That script allowed us to create loads of IDs on the fly. Now, we have a very nice GUI tool called the Apple ID Automation Builder that can be used to batch create a number of Apple IDs on the fly. Brought to us by Greg Moore and hosted by enterpriseios.com, this is one of those rare finds that is a serious time saver and very valuable when you need it in your bat belt. Great little tool, well worth the money and I look forward to providing Greg with plenty of accolades should we ever meet!Similar Articles:

• New 3rd Party Apple Certification Exams Now Available
• Talking A Look Under Apple Configurator’s Hood
• Apple Configurator 1.0.1 Released
• Using Apple Configurator To Automate Casper MDM Enrollment
• Apple’s Customer Facing SystemStatus

I also like the fact that the layout allowed me to read only the parts that mattered to me. For example, I have used the iBooks app for awhile, so I really just wanted to jump straight into writing. While some of the book is very specific to shopping on the iBookstore much of it is also dedicated to writing. I like it when I can pick something up and have no dependencies looking at earlier elements of the book.

Overall, it’s a nice quick read and very practical. Even if you’ve been using iBooks, check it out; you may learn something new (I did).Similar Articles:

None Found

I’ve also taken a lot of certification exams. And along the way I’ve definitely developed a feeling for what I think are good and what I think are bad questions. I feel for anyone that actually reads the feedback left on most certification exams, although I sincerely doubt anyone actually does. So what are those tips:

1. Start with an outline. Just like when you’re writing text, know what you want to accomplish ahead of time. Use each question to accomplish a goal from the outline.
2. Know your audience. Certification testing should have no humor. It’s too bad, but when people fail the test the last thing you want is them punching you in the face and then repeating your humor back to you. It can happen…
3. Given your audience the test should be passable. If you’re writing a test for desktop administration you likely shouldn’t be asking questions about the structure of a bdb file in an Open Directory database or for specific methods for managing the schema within Active Directory. You may know all that and be awesome, but you’re not taking the test, you’re writing it.
4. Build questions based on fact rather than opinion. Also keep in mind that different people consider certain things opinion. For example, evolution, things Rush Limbaugh spews and whether or not an Apple computer is better than Windows. To many these are facts and to others they are opinions. Doesn’t matter here, as they don’t belong on a test. Think of Jeremy Piven in PCU. That’s NOT you.
5. Don’t ask negative questions. Yes, I moved this one below #3 because of the word NOT. Don’t do that. Asking which port is not used on a mail server is better done by either using a matching question that matches each port with the port number or by asking which protocol does a specific function. Maybe a bad example, but this article is about writing tests, not articles… Either way, keep in mind “accentuate the positive, eliminate the negative.”
6. Be technically correct. Nothing worse than either not having any correct answers or knowing that the author has no idea what they’re talking about.
7. With multiple choice questions, it’s best to have one answer. If you have multiple answers you might be jumping around on the outline or simply withholding points from users where not needed. Note that all of the above or none of the above are answers that are multiple answers on their own. I don’t like using those.
8. Be relevant. If you are writing a test about OS X Server then a question about how Active Directory builds service records for Exchange is definitely misplaced. If you’re writing a question about Solaris and ask how to install an msi en masse via SCCM then that too is pretty darn misplaced. These are egregious examples, but every question should have a point and that point should go into your outline.
9. Scenario based questions are awesome for technical exams. Yes, if you put someone in a situation with all the relevant facts and you ask them a simple question that gets to the root of whether they know a product then that is probably amongst the best ways to test a skill.
10. Don’t try and compound multiple questions into one question. If you’re following an outline then each question should match up with an objective. You will only confuse many a test taker with compound questions.
11. True/False questions are stupid. Yup, I said it, even though I’ve written them in the past. But I won’t write them again in the future. 
12. Edge cases are irrelevant. Yes, I’m irrelevant. But more to the point if you ask someone a question that came up once in your twenty year career and when it came up no one else in your field had any clue what you were talking about then it’s probably a crappy question that maybe a few people get right by accident.
13. Trick questions suck. This goes into the edge cases comment. The fact that someone can or cannot see through some weird way to phrase a question isn’t telling you whether they know the product you’re testing on.
14. Always pose questions in an active voice.
15. Don’t include a bunch of random facts. For example, if you’re asking a test taker how to use awk, don’t include 10 facts that have nothing to do with what awk is supposed to accomplish. Don’t try to hide what you’re trying to figure out. Put it out there right at the beginning.
16. But don’t answer the question within the question. It’s easy to give an answer away, but you don’t have to.
17. If every answer (incorrect and correct) start with the same few words, move those into the question. Looks better, uses less energy because less bits have to be in databases and therefore saves the world from disaster (if you believe in global warming – reread #2 at this point).
18. Do not use past tense.
19. Spell out your acronyms. Yes, plenty if not most in many exams should be common knowledge. That doesn’t mean you shouldn’t do it anyway.
20. All of your answers (incorrect and correct) should be consistent with regards to structure and grammar on a per-question basis. If one has a period they all should. If one has a subject and an adverb then they all should, if one lacks a pronoun at the beginning then they all should, etc.
21. Don’t ask the same question twice. Sure, you might phrase it differently but if you stick with an outline you won’t end up hitting the same area twice. Unless you’re planning an adaptive testing experience. Then you can hammer in on areas of weakness. But that’s kinda’ rare.
22. Don’t use really big words that have nothing to do with the subject you’re testing on. Keep in mind that you’re not writing an English test (unless you are), so the objective for the test is to determine if someone has a given skill or understands a concept. By using overly complex grammar and vocabulary you will be testing a skill that maybe you’re not supposed to be testing for.
23. Don’t have your incorrect choices be too different. They should be within the realm of reason, use real industry terminology and be possible for a different question maybe, but wrong for the question you’re asking. The correct choice should not be absurdly longer or shorter than the incorrect choices either, so structure and appearance actually play into this. I’ve found some test writers will actually have their correct choices always be three or four words or a line longer than incorrect choices. These incorrect choices should also not be extremely different from one another.
24. Leave your ego out of it. Many of the above items are perhaps derived from this one. Sure, we get it, you have seen some really weird things. And you have great grammar. And you can pick out things that have nothing to do with the topic to find the right answer. And your critical thinking skills are awesome. But don’t put things that have nothing to do with your subject matter on the test because in 99.9% of testing scenarios no one knows who you are…
25. I’m going to #1. Start with an outline. I know I said don’t repeat yourself, but I’m doing so here. The outline will be your guide. You can be open to alterations to the outline as you write questions. Figure out what you want to ask about before you write your first question. You will be glad you did!

I hope that just reading through these helps you pass your next tests, write tests, etc. Good luck in whatever your endeavors are!Similar Articles:

None Found

allmemory

This is going to result in a few errors if only because allmemory is getting a little long in the tooth. But you can also scan on a per-process basis. To do so, run allmemory with a -proc option and then the pid for the process:

allmemory -proc 13727

You can also use the following options:

• -noframework: doesn’t show data that comes from frameworks (otherwise it does), so this option would only show the spcific process and not dependencies
• -noprocess: doesn’t show the process, so more looking at framework utilization
• -32bit: only show 32-bit processes
• -64bit: only show 64-bit processes
• -v: show address space utilization on a per process basis
• -f: show segment utilization on a per framework basis
• -i: show data from a previous run of the tool, which uses a path after the -i to load that data from
• -o: outputs the data to a specific directory (otherwise it defaults to /tmp/allmemoryDataFiles). Note, when called from other Apple tools, the output is normally set within a dmg or zip in /var/tmp
• -d: loads data from /tmp/allmemoryDataFiles if it exists
• -P: shows information about VM regions used

There are a few other options, but those are the only ones I can remember using. Overall, allmemory is a pretty cool tool and I think that if nothing else it’s helped me to prove to vendors when I have issues with their software. I’m maybe not always happy with their responses but it’s good to prove that there’s a problem… Finally, output can look something like the following:

Similar Articles:

None Found