Skip to main content

Apple: MacBook Manual Surprises

This is a list of things that surprised me while reading the manual for my MacBook:
  • Use two fingers on the touchpad to scroll.

  • It doesn't come with a modem.

  • The lowest model MacBook can burn CDs but not DVDs.

  • Hit F3 (without fn) or F10 (with fn) to use expose.

  • Turn it off if you're not going to use it for a day or two.

  • Putting it to sleep decreases the chances of damaging the hard drive while moving it.

  • Use "fn delete" to delete characters to the right of the cursor.

  • The manual use to say that if you added memory yourself you would void your warranty. It now says that you'll only void your memory if you mess up ;-)

  • Hold down D while booting to use Apple Hardware Test.

  • The printed manual is only in English.


Anonymous said…
One thing that surprised me on my iBook was: Hold down T on bootup for Target Disk Mode. Once you see the yellow firewire symbol on your screen, now your laptop has been transformed into an external firewire disk.

Fastest way to move data between two Macs.
Eddy Mulyono said…
Does this mean you bought a MacBook, JJ?
jjinux said…
Embarrassingly enough, yes. I'm trying to mix things up to recover from burnout. Hence, I'm switching from Linux to Mac, and I'm switching from Vim to Emacs. I feel very strange.
Anonymous said…
I thought you were going to say you bought this for the family and not yourself :-) How much open source crap have you installed already :-P
Alec said…
FWIW, I leave both my work and home macbooks (Original MacbookPro and 12-month old Macbook) in sleep mode all the time. I typically go 2+ weeks between actual reboots.
jjinux said…
> How much open source crap have you installed already :-P

Ah, you know me well ;)

> I leave both my work and home macbooks (Original MacbookPro and 12-month old Macbook) in sleep mode all the time. I typically go 2+ weeks between actual reboots.

Yeah, that's my favorite feature so far. Going from 2 hours of battery life to 5 makes all the difference in the world. I no longer bother with bringing my power adapter with me when I go to the coffee shop or to meet with people.
dm said…
I whimsically clicked on your "Apple" tag and found this post. Interesting contrast with your previous Apple post. What happened to loving the freedom, man?
jjinux said…
I was desperately burnt out, so I started trying a bunch of things to get me over the burnout. I switched from Linux to Mac, Vim to Emacs, and Python to Ruby.

I ended up really disliking Emacs per my post here: I seem to go through an Emacs phase every couple years, and I always en up back with Vim.

I decided I still liked Python more than Ruby, but I was sick of Web development. Hence, my current job is mostly not Web related.

The Mac is nice. It's really the hardware I like best. 5 hours of battery life rules, and suspend works really well. I haven't really started using anything proprietary yet. I'm still all about Vim, zsh, Flock, Python, etc.
jjinux said…
> What happened to loving the freedom, man?

I thought about it a lot, and I explained it here:
bsergean said…
Suspend to RAM works fine on Linux too. This article explain it all.
I just had to add two lines in my xorg.conf to get my lenovo with nvidia hardware to suspend / resume.

But I type this on a MacBook Pro ... I have to say it's a really nice hardware. One thing I really like is the screen, that is probably back-lighted so you can see it's content everywhere even when there is some sun coming in.
jjinux said…
I know; I'm normally a Linux guy. The thing about MacBooks is that suspend works *reliably right out of the box*.

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p