Technology How To’s

Article that I’ve written over the years to resolve specific technology issues that I’ve run across in my day to day life.

How To: Change Default Mail Client on OSX

Posted by Rick on in Apple, Leopard, OSX, Technology How To's 0 Comment

How To: Change Default Mail Client on OSX 

When I moved away from Entourage to Thunderbird I had a huge issue with mailto: html links still attempting to open Entourage to send emails. OS X itself simply does not provide a simple way to change this default behavior.

So, the trick is to open OS X’s Mail Client and use that. Simply create a dummy account, it doesn’t matter what info you put in as you won’t be using it. Once Mail is opened, go to Preferences then click on the General Tab. There will be a “Default Mail Reader” drop down menu. Choose your default client (even Firefox or Safari if you have something like Zimbra or another web mail) and exit the client.

The other, and possibly better trick if you’re going to make this change across multiple computers such as an entire Enterprise setup is to edit one of the plist files.

In ~/Library/Preferences/ look for com.apple.LaunchServices.plist

Add

    LSHandlerRoleAll
    com.mail.client
    LSHandlerURLScheme
    mailto

Just under
LSHandlers


Options for mail client would be com.mozilla.firefox or com.microsoft.entourage or the preferences name of any other mail client. These can easily be found in the same folder. Once this is done, mailto: links will then open in your preferential mail client!

How To: Use Dump to back up a full filesystem

Posted by Rick on in FreeBSD, GPL, Linux, Technology How To's, Unix 0 Comment

How To: Use Dump to back up a full filesystem

Way back in the day when tape drives first started being heavily used to do backups of Unix machines, the dump command was created. In typical Unix simplicity the dump command “dumps” files from one device to another device. This can be a tape drive, a hard drive, even a network share. rsync does a similar process but is meant for immediate use of those files.

First step is to be sure dump is installed. If not use, rpm, yum, port, apt-get, or your local repository method to install dump on your system.

The quickest command to get started is: dump -0 -j9 -f /pathtosavebackup /pathtobackup

This would give us a down and dirty dump of the requested path, or if / is used in the second part of the command, the full file system starting at the root.

-j9 tells the command to compress (using tar) the file as much as possible.

-f defines the device (or filesystem path) to dump too. Keep in mind that this command could not be used to dump files from the local filesystem back to the local filesystem.

The bad news is that this will take quite a while depending on how much data needs to be dumped, how fast the hard drives (or tape drive) is, and if backing up to a network share, how fast the ethernet connection is. In my tests 100gb filesystem got compressed down to 23gb, and took about fives hours across a 10/100 connection.

After the dump is done, tar can be used to unarchive the file to a new file system.

Home Network Setup

Posted by Rick on in Hardware, Technology How To's, Unix, Windows 0 Comment

Home Network Setup

Originally Posted 11/20/2000. Ironically a lot of this is still useful.

 

Home Networking

 

 

            In the day and age of Multi-computer families, a frequent argument is, who gets to be online? The answer is simple, Modem Sharing or networking. Modem Sharing can be done one of several ways, using a regular Analog Modem (300 baud to 56.6K,) DSL or ADSL, ISDN and Cable modems. You could also be on a T-1 (or greater!) network connection, but then why are you reading this? J

           

 

Which one is right for me?

 

            Analog Modems

 

            Pros: Can be used anywhere a telephone is located.

            Cons: Limited to an upper bandwidth of 53K due to telephone regulations in the US. May be slightly higher in other countries. Modems also suffer greatly from phone line quality, crosstalk (where two or more wires touch each other in the wrong place therefore mixing the signal,) and any line noise at all. More then two low-bandwidth applications can easily make this almost worse then nothing. Ties up the phone line if you only have one.

 

            ISDN:

            Pros: Very fast, two 64K channels giving 128K total. Even one channel at 64K is cleaner and noticeably faster then 56k.

            Cons: Still only 128K, costs the same as DSL. In addition, totally against ISDN specs, some companies charge you for the 2nd line to automatically drop when an incoming or outgoing phone call is detected, so your phone is still tied up.

 

            ADSL/DSL:

 

            Pros: Very fast… minimum 265K maximum 7 megabits, makes this very, very fast. Phone lines do not get tied up at all. Can easily support multiple high-bandwidth applications (web browsers, games, large downloads, etc.) Can get a Static IP, which is very useful if you wish to run servers at home.

            Cons: Suffers slightly at the phone companies end due to misconfiguration. Such things as dropped carriers, being able to see other people’s computers (in Network Neighborhood.) and depending on the carrier, a slight slow down in bandwidth due to the phone company over selling it. Remember, at this point the phone company does not have to guarantee a certain amount of bandwidth… you simply have speeds up what ever your limit is.

 

            Cable:

 

            Pros: As above, very, very fast

            Cons: Suffers greatly from overselling of bandwidth. If other cable subscribers are all using it at the same time as you, they effect your speed. If you’re the only one in the area then it’s not a big deal. But frequently this slows down to speeds that are little better then a regular modem. Can’t get a Static IP number,  you’ll never be able to run a server, at least not very effectively.

 

Initial Setup

 

            First you need to get the network equipment. Your best bet for ease of configuration and portability is to get a couple of  mid-priced range network cards, (Kingston is a good bet) and a decent 100Base hub. (NetGear, Bay Networks, Intel.) You can buy cheaper cards such as SMC but they will effect your speed. If you can afford it, a switch is even better, giving you more bandwidth and speed. You’ll also want several lengths of networking cables too. J

            Second, your modem or router should be hooked up to one of the computers. In the case of some DSL routers, these can be directly hooked up to your hub. Other products have a DSL router and hub built in to the same unit. In my opinion this is unncessecary and could cause problems down the road. Remember to install the 2nd network card if it’s an external unit. (Cable and DSL only.)

            The third step is to setup the modem/router itself to connect to the network. This changes from different brands of Cable modems and routers. If you’re using a regular 56k modem, connect as you usually would.

            The last step is to make sure you know what your IP Address, DHCP Server (if needed,) DNS Server, Gateway and Netmask numbers are. You may or many not have all of these options. These have four numbers or “octets” like 255.255.255.0 or 192.168.1.0 Each of these numbers or octets can be anything between 0 to 255, with some exceptions.

            Your network should look something like this when you’re done:

            ISP -> Modem/Routers -> Computer -> Hub <-> Other computers

            One thing to point out, the computer plugged into the modem/router needs to be running an Operating system capable of doing routing. Windows 95 is not capable of doing this.  Windows 98 sorta does it, while Windows NT, ME, 2000, FreeBSD and Linux are all capable of doing so. Mac OS X being based off of FreeBSD can also do this. Windows 95 is capable of doing so with the help of a third party commercial piece of software. I personally run FreeBSD on  a 486 SX-25, recently upgraded to a Intel P-166 to do this. (BTW, it runs quicker and more efficiently then Windows NT or 2000 on a AMD –450 with 128 megs of RAM!)

 

Network Setup

 

            The Network hardware is pretty straightforward. One cable from each computer plugs into the hub or the switch. Each port should have a LED saying the port is active. Usually there is a 2nd LED that shows network traffic on that port of the hub.

            Start with the computer connected to the modem/router. The protocol that you wish to run is TCP/IP, make sure IPX/SPX and Netbui are both disabled unless you need them. Most games these days don’t care what protocol you’re running, but some of the older ones need IPX/SPX (Duke Nukem 3D, Warcraft, early Diablo releases, etc.) Having Netbui disabled helps keep people from hacking into your computer, there are hundreds of security holes in Windows with this protocol.

            After adding TCP/IP in the Network option under Control Panel Add in your network settings as provided by your ISP. Usually your ISP gives you instructions on how to do this, you’ll want to follow them. Test your dial-up and networking. The computer should run perfect.

            Now comes the tricky part, configuring the other computers. The easiest configuration is the dual network card and external modem/router option. The first NIC connected to the modem/router is configured exactly as it should be. The 2nd NIC’s TCP/IP Address should be one that is assigned by you. For ease you should pick something like 192.168.1.1 You can pick any number, but make sure the first three octets are all the same. Do not pick the same first three octets as the IP assigned to your 1st NIC… it will cause problems.

            Your Netmask is always 255.255.255.0 do not ever change this unless you know what you’re doing, your network will become unreachable. The Gateway address is the same as the IP address of the 1st network card. Keep in mind this is only for this card. Certain operating system will not accept this option either, but most Windows systems should.

            In addition some operating systems will need a flag set to make it a gateway or router machine. For instance, in FreeBSD and Mac OS X /etc/rc.conf needs the line “gateway=enable” This also invokes the NAT or “Name Address Translation” program. NT and 2000 should both give you a similar option.

            The 2nd (and all subsequent computers) will have an IP address of 192.168.1.x (where x is any number between 2 and 254, do not use 1 as it’s already used, 0 and 255 should also be reserved, Just in case.) Their Gateway address will be the IP of the 2nd network card in the first computer! DNS or Name Server address will be the same across all computers, unless you setup a nameserver, which for a small network I recommend against doing.

            For computer with a single network card, and a modem, the theory is the same. Use the gateway to be the IP number of the modem/router. Remember that IP numbers are assigned to Network interfaces, not to the computer. A computer can theoretically have an infinite amount of IP addresses, in reality it’s whatever number the operating system is capable of handling, at least 254 though, and more then most people will ever need.

            If you have a large amount of computers, say more then 5 or 6, you may want to look into assigning these IP numbers via DHCP, it’s initial setup is harder, but more robust with large networks, it also makes the client machines virtually Plug and Play.

 

            Security

           

            Now that your network is running, it’s time to turn your eye towards security. The best way is a firewall. Windows NT, 2000, FreeBSD and Linux can all do this. Linux has more security holes fixed then Windows NT or 2000, and FreeBSD even more. If you’re really serious about security and wish to really learn, OpenBSD is the best of all. FreeBSD offers the best choice of security and ease of setup.

            A Firewall is simply that, it keeps the bad stuff from coming in, and if you wish, keeps stuff from going out. It works by stopping or dropping traffic if it does not adhere to the rules that you define.

            The first step in building effective firewalls is to block everything. Then step by step you want to unblock stuff you want. Port 80 (http requests,) 21 and 22 (FTP) are good starts. Some programs will want other ports open, PCAnywhere needs 186 & 187 open. Remember, it’s easier to block stuff before it’s broken, then to block if after somebody has hacked into your computer.

 

            Conclusion

 

            These are really some very basic instructions. Unluckily due to the sheer amount of different configurations out there, I can’t give step by step instructions like I’d like too. If you have specific questions though, post to the Hardware and Software forums and somebody can help! J Even then you should have a working network configuration in no time at all!

Troubleshooting: Facebook constantly logs out in Safari

Posted by Rick on in Apple, Technology How To's, troubleshooting 2 Comments

**Update** Facebook made updates that fixes this problem.

Troubleshooting: Facebook constantly logs out in Safari

A recent problem has cropped up with the latest version of Safari, 3.2.1 and Leopard 10.5.6. When using Facebook (and possibly other websites such as Last.fm, Gmail, and Twitter, that require authentication to login,) users are finding that they constantly have to re-login again. Of course this gets annoying, and makes accessing those sites nearly impossible. This problem is bad enough that it could even be affecting Firefox users too.

The culprit maybe partially on Facebook’s side as they attempt to combat the recent virus threats and the Leopard/Safari upgrade may be coincidence. Another guess is that Apple changed how multiple programs handle cookies and this is causing issues.

In addition users of iPhones and Adium in conjunction with Facebook seem to have a high chance of having an issue. Using Facebook Chat in Adium and on the iPhone is one of the culprits.

While not a guarantee, here are some possible fixes.

iPhone Users: (may have to be jailbroken to work, I do not have an iPhone to confirm)
1.) Download a terminal program for the iPhone
2.) chown -R mobile /var/mobile/
3.) Power Cycle the iPhone

It seems that the /var/mobile directory is owned by the root user instead of mobile and is causing some of these problems problems.

Adium Users:

  • Disconnect from Facebook or Google Chat before logging in to Facebook or GMail

    • Safari: One or all of these options may be needed to fix

  • Disable Private Browsing (Under Safari Menu, the Private Browsing)
  • Empty Safari Cache (Safari Menu, Empty Cache)
  • Clear Cookies (Safari Menu, Preferences, Security, Show Cookies, Remove All)
  • Reset Safari (Safari Menu, Reset Safari)
  • Reinstall Safari (Download from here)
  • Remove Autofill (Safari Menu, Preferences, Autofill, User Names and Passwords, Edit, remove the site that is having issues)
  • Remove Keychain Entry (Applications/Utilities/Keychain Access. Remove affected site, then go to Menu, Keychain First-Aid, then Repair.)
  • Delete cookie.plist file (/User Home Directory/Library/Cookies/Cookie.plist)

    • Advanced Safari Tip: Enable Developer menu using the command line: defaults write com.apple.Safari IncludeDebugMenu 1 or download Safari Enhancer and clear cookies from this menu.

    Dashboard:

  • Disable any Web Clippings

    • If any of these do work, or you have another solution (or a question about the above,) let me know in the comments and I’ll see what I can do.

    How To: Disable ._ Files and .DS_Store on Network Shares

    Posted by Rick on in Apple, Technology How To's 3 Comments

    How To: Disable ._ Files and .DS_Store on Network Shares

    In heterogeneous networks of Macs and Window users, few things tick off Windows users then the “droppings” Macs leave behind in the form of files with . or ._ in front of them. These files are known as resource forks on the Mac side and store all kinds of really nifty information that makes OS X interact with files quicker and more efficiently. Among their uses they store metadata about files such as keywords, file size, and preview information.

    None the less for various reason Windows (and to a lesser extent, Linux) is not able to always ignore these files and automatically sorts them to the top of the file view list. These files tend to be confusing if one is not aware of what they are. Or worse yet cause problems in directories with thousands of files present.

    If on a small network with only a few Macs there is a program that takes care of this automatically. For $13 BlueHarvest works just perfectly.

    Of course there is a simple trick to disable .DS_Store files. In Terminal run the command:

    defaults write com.apple.desktopservices DSDontWriteNetworkStores true

    If the network is Leopard only, then editing nsmb.conf is a good trick too. In /etc/nsmb.conf look for the following line: streams=no and change to streams=yes .

    If the file does not exist, then it can be created via TextEdit or VI.

    These files are only viewable under very certain circumstances but they can cause a lot of coworker friction, and worse yet even cause management to question the usability of OS X in the work place. These simple tricks will go a long ways to resolving those issues and making work much more friendly.