![]() (well…that and actually compiling & installing dwm).Most users use Disk Utility to erase a disk or hard drive. If this is any indication, my dotfiles are in a git repository, and a quick clone makes me feel like I'm at home when I use linux. But as far as the shell goes……it's the same shell. ![]() How close you can get to what you're used to really depends on how you used Linux. I'm using xnomad, iTerm2, Shadowkiller, bartender, Shades, Flux, Nocturne, iStat Menus, Alfred (+PowerPack)……mostly to do things that I do on linux with dwm + scripts, though I do like iStat's monitoring better than anything I used in Linux. But it kind of depends on what you're developing.īut it does take a lot of little 3rd party apps to get it there. I also use vim & git and develop on os x and linux…and the experiences are basically identical except that dwm on linux works better than xnomad on OS X (not xmonad)………but xnomad is good enough for now. Other than that, the experience is similar. Homebrew and MacPorts both try, but they both fall short. There is no package manager for OS X that's as good as pacman or portage. (Personally, I recommend homebrew.)Īlthough the bulk of it is the same, some things are done differently to Linux, but are usually no less scriptable (with the exception of the MAS noted above).įor instance, to have a program run periodically, rather than invoking crontab -e and adding a line, you drop a file in your ~/Library/LaunchAgents folder and register it with launchctl. ![]() (If someone were to prove me wrong here I would be delighted.) That said, it's rare to find an app that is only available on the MAS.Īs others have mentioned, there are multiple package managers for CLI apps. #Terminal os x mac#The exception to this is the Mac App Store, which AFAIK can only be used via the GUI. (Disk images can also be opened from the CLI, but I don't remember how.) This is normally done with the GUI, but since a bundle is just a folder and wget, unzip and mv are all present, this is scriptable. #Terminal os x zip file#GUI applications are typically installed by downloading an application bundle (usually inside a zip file disk image), and then moving that bundle to the Applications folder. Others have answered most of your questions, but I'll add this: I sense if you're familiar with Arch, you'll be able to learn OS X's quirks pretty quickly. I use both OS X and Linux (Ubuntu, Fedora and Crunchbang.) I can do most of what I'd do in a terminal on Linux on OS X too, but the major difference is the package management. It also has the Mac App Store, which will deal with downloading apps, but doesn't really handle dependencies (all MAS applications are sandboxed Cocoa and don't require external frameworks.) It does have a package system, but it isn't exposed to the user. ![]() It's also worth noting that OS X doesn't ship with a "package manager" as such. conf files.) OS X is closely related to FreeBSD so I'd recommend looking into that-install it in a virtual machine if you want to get a feel for it. (for instance configuration files tend to be XML. Architecturally OS X is just about different enough from Linux to be annoying: chances are you'll still be able to do what you want to do, it's just done in a different way. The places where I imagine you might run into issues are if you wanted to do configuration at the command line. ![]() The default shell is BASH (I believe it used to be tcsh, but that's changed) so the experience should be mostly similar. Day-to-day operation is broadly identical to most Linux systems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |