So my Linux install going messed up somehow and I was left with no wireless driver installed. I know that you can use Android phones to USB tether mobile data (e.g. 3G/4G/LTE) but I didn’t know that you can do the same over WiFi!
Now while in OSX I’m pretty sure it worked out of the box previously, it seems that you need now need to download the HoRNDIS driver. With Linux (Ubuntu) it worked out of the box and in my previous usage of USB tethering, Windows should work automatically as well.
The first version of Ubuntu for this year has been released. It is dubbed Natty Narwhal or for easier date reference 11.04. Check out the release naming scheme on the Wiki that includes the history of this naming convention. But in all seriousness the main new change is that they have changed to the Unity as the desktop environment instead of Gnome. This brings a refreshed look to this Linux distribution as well as providing added functionality. Check out OMG! Ubuntu’s guide to Natty Narwhal and Ubuntu’s own “What’s New” page.
Summary for UI changes as well as naming convention:
Unity: a new desktop environment which could be described as the desktop / user interface that the user sees when they log in. It is comprised of the Launcher, the Dash and the Panel
The Launcher: This seems more like OS X’s dock than WIndows task bar. You can launch applications from from it and open windows should shown in the launcher
The Dash: similar to the Window’s Start button (or now the Windows button), this will allow you to look through and launch any application installed
The Panel: situated at the top of the screen, this acts as a global menu bar just like OS X, but also integrates with other applications through the indicator area (similar to Windows’ notification area)
Go try it out and download it now. You don’t even have to install it, just burn it to a CD or install it to a USB drive and boot straight from it to see how your hardware handles it. For the computer enthusiast there is no reason not to give Ubuntu a try and delve into the world of Linux.
If you have played around with any 2 of the 3 major operating systems (Windows, OS X and Linux) and start transferring files to and from external hard disk you will probably run into an issue with the type of filesystem you choose for your hard disk. Windows likes NTFS, OS X likes HFS and Linux likes ext. As you can see none of them are the same. Being different is not so much an issue, but being compatible and accessible to all is.
Based on default system settings:
NTFS is readable on all operating systems, but not writable on OS X. Most modern Linux distributions can write to NTFS drives
HFS is readable on OS X and modern Linux distributions, and not writable on Windows or Linux
ext is only readable on Linux and not writable on Windows or OS X.
or to put it based on operating system
Windows can only read and write to NTFS, nothing else
OS X can read and write to HFS and read NTFS
Linux can read and write to ext and NTFS and read HFS
Take note that there is also the older FAT32 filesystem that is fully supported for reading and writing by all operating systems but due to limitations of FAT32, I rather not consider this. Basically the main issues with FAT32 is that the maximum file size is 4GB and the maximum partition size is 32GB (actually Windows can’t format a FAT32 partition greater than 32GB but can read FAT32 partitions of more than 32GB. Use GParted or just filter this Google search to be able to create and format a partition of 32GB). If these are limitations you can deal with, for the sake for interoperability stick with FAT32.
Now to solve the problem of support for each filesystem in each operating system:
I’ve been using NTFS-3G in Linux for many years and haven’t had any problems with it and so far it’s working well with OS X too
On another note if the NTFS drive is not unmounted properly or there are some issues with the file system integrity, it is necessary to use Windows scan disk to rectify the problem. Thus this requires a copy of Windows to fix the filesystem.
I’ve had issues of only being able to mount an ext2 partition in Linux and it gave a mount error in Windows and OS X and was due to an inode issue as new Linux distributions create the file system with inodes of 256 bytes but Ext2 fs only supports the older version with 128 bytes. And the only solution is to back up the files, and reformat partition with inodes of 128 bytes (-I 128) and restore the files.
Filesystem integrity issues should be able to be fixed with “fsck” from a Linux distribution / live CD. The great thing about this is that you can get a Linux distribution for free and this recovery can be done with out any strings attached.
Note: I have not personally tested these so I cannot give first hand experience of how well it works or what issues can be had with this.
I believe that HFS+ journal
I would believe any filesystem repairs would have to be done in OS X (similar to NTFS and Windows) and if so this enforces that you have OS X at hand, and in order to have OS X you must have Apple hardware or a Hackintosh either way this is very restrictive.
So it is pretty easy to get full read and write support of all 3 default file systems on the 3 major OS’s but there are issues. So far I’m inclined to stick with ext2/ext3 just due to the fact that it has no restrictions in terms of filesystem repair. I’ve had many NTFS issues related to damaged filesystems that required Windows and the inconvenience of taking the drive out of my box to find a Windows box was too much.
Install packages for Ubutun/Debian systems sudo apt-get install wvdial bluez bluetooth
Steps to get your Bluetooth modem working
Turn phone’s Bluetooth connection and set to discoverable mode
Scan for your device: sudo hcitool scan Result: Scanning ...
Search device to see if supports Dial-Up Networking (DUN) for use as a modem. Look out for RFCOMM channel sdptool search --bdaddr 00:11:22:33:44:55 DUN Result: Searching for DUN on 00:11:22:33:44:55 ...
Service Name: Dial-Up Networking
Service RecHandle: 0x1000f
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"RFCOMM" (0x0003) Channel: 4
Language Base Attr List:
Profile Descriptor List:
"Dialup Networking" (0x1103)
Bind the modem on the RFCOMM Channel to a device sudo rfcomm bind /dev/rfcomm0 00:11:22:33:44:55 4
Dial and connect (ensure your wvdial configuration is correct, for sample see below) sudo wvdial dstbt Result: --> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
--> Sending: AT+CGDCONT=,,"dst.internet"
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
~[7f]}#@!}!} } }2}#}$@#}!}$}%\}"}&} }*} } g}%~
--> Carrier detected. Waiting for prompt.
~[7f]}#@!}!} } }2}#}$@#}!}$}%\}"}&} }*} } g}%~
--> PPP negotiation detected.
--> Starting pppd at Wed Aug 19 23:45:04 2009
--> Pid of pppd: 17558
--> Using interface ppp0
--> local IP address 10.84.2.128
--> remote IP address 10.6.6.6
--> primary DNS address 220.127.116.11
--> secondary DNS address 18.104.22.168
Init = ATZ # far card with no PIN
# Init = ATZ+CPIN=”0000″ # for card with PIN, replace 0000 with your PIN
# If you know your ISP’s APN, specify it instead of YOUR_ISP_APN below.
# There’s also an APN table at https://wiki.ubuntu.com/NetworkManager/Hardware/3G .
# use one of the following 3 options. change to your providers APN
Init2 = AT+CGDCONT=,,”dst.internet”
#Init2 = AT+CGDCONT=1,”IP”,”YOUR_ISP_APN”
#Init2 = AT+CGDCONT=1,”IP”
# Most services/devices dial with *99# . A few seem to require *99***1#
Phone = *99#
# These often suffice, but your ISP might require different details. They’re
# often dummy details used for all users on the ISP, frequently the ISP’s
# name, but some ISP’s do require you to use a real username and password.
# any details possible
Username = internet
Password = internet
If you have a problem connecting please note this bug that causes the connection to timeout if there is a shell running as root. So close all terminals open. It took me 2 hours to figure this out so I hope you won’t have to suffer the same.