sasahalf.blogg.se

1. #Zelotes t 80 big mac beeping mac os x
2. #Zelotes t 80 big mac beeping install
3. #Zelotes t 80 big mac beeping full

I have done full and partial restores from backups using Retrospect with no unexpected effects on aliases, sounds like you were using a crappy backup tool.Īpple's aliases have slightly different semantics than unix aliases. There were no ill effects on any aliases. When I managed Mac labs, users used to rename various HDs in labs fairly often, which I would name back. *NIX tools do not like aliases, so I always use symlinks instead, no big deal.Īliases point to a file in an intuitive way to a non-technical person - if you move or rename the file it keeps pointing to the file - if you replace it, then it points to the replacement, simple for grandma to get.Īs for breaking aliases, you are in error saying that renaming your HD will do this. Having used OS X since Public Beta, I have yet to have had a real problem with the alias/symlink thing. By default there are not many in the system, so provided you make symlinks rather than aliases all is well. Or use 'ditto -rsrc' which handles forks as well.Īs far as the alias thing goes, 1) it is not too hard to avoid aliases and 2) they are designed to be convenient to your average user.

#Zelotes t 80 big mac beeping install

Then again, it's nice to learn a new thing once in a while, isn't it?Īs far as cp goes, most files will copy fine, but if you work with files that have resource forks (fewer and fewer as time goes by) then install the Dev Tools and use CpMac and MvMac, which handle resource forks properly. You could install X11 on it, but X apps will never feel like native apps, and most apps that are written for OSX that you might want to modify won't be using X. OSX is way different from other Unix-like systems. Once you get to GUI's then it's a whole different thing (unless you remember when Suns came with Sun Tools, DEC had X11, AT&T had the BLiT, and everyone else had their own thing too). Straight down to programs sometimes forgetting a htonl or the like. I remember when SunOS was king, and it was a slight pain to port stuff to Ultrix (DEC's Unix).

One of the less common ones, so you may not find as many things compiling out of the box, but that isn't because OSX is more different from whatever Unixish system the author used (most likely Linux these days) then, say NetBSD or SunOS is, but just that whatever 3 random things that always seem to trip people up when going to a new platform weren't already spotted and fixed.

#Zelotes t 80 big mac beeping mac os x

If you are talking about command line tools, Mac OS X is "just another Unix", period. Yes, Apple has a ton of GUI admin tools that whizz all over /etc, but what is IBM's SMIT? Or HP's.er.what does HP call their admin tools again?

Sure Apple uses NetInfo, but it really isn't any different from Sun's YP or NIS. If you ignore the fact that pretty much every Unix system that has a GUI except Apple's uses X11 the differences from "Apple's Unix" to anyone else's isn't really any bigger then the differences between any two other Unix-like systems. dangerous directories) and can easily be over ridden. Many of the differences the article outlines are simply "hiding" the Unix from newbies (i.e. I think you'll find that the variations aren't so much variations from Unix, but from Linux.