Skip to main content

Experiences with new Mac Mini

Earlier this month I bought a Core i5 Mac Mini. It was quite an impulsive decision, partly influenced by the fact that it was a bit annoying frequently rebooting my office Dell desktop to switch back and forth between Windows and Linux. I have been using Linux for everything (like browsing, programming, creating Tex documents as well as for music and movies) since the last 4+ years. However, when I joined as a Grad student in CQT, earlier this year, my requirements changed a bit, which made be quite a bit dependent on Windows. I got involved in some device driver development in Windows, creating/maintaining several VIs in Labview and working in AutoDesk occasionally to coordinate with workshop technicians. Moreover the lab-notebooks were traditionally being maintained in MS OneNote. Since I am heavily reluctant to completely move away from *nix for my computing needs, I tried dual-booting my Core i7 desktop with Windows 7 and Ubuntu 11.10. Primarily I was using Ubuntu, but had to frequently reboot into Windows for either Labview/Autodesk/Onenote. At this point wanted to give OS X a try and ordered the base version of the new Core i5 Mac Mini online. It came with a 500GB HDD and 2GB DDR3 RAM. It was pointless giving $$$ to Apple for memory upgrade, when 4GB Kingston DDR3 modules are available in the market at a fraction of Apple's price. Even before my Mac Mini arrived, I headed off to Sim Lim Square to get a pair of 4GB, 1333MHz DDR3 Kingston modules for 78 SGD.
When the Mini arrived in my office, before switching it on, I took off the back cover and replaced the 2GB modules with the 8GB ones. I had a Dell 23" display and Microsoft wireless keyboard/mouse, so without wasting anymore time, hooked them and booted the Mini. First time startup configuration was highly "Idiot Friendly". All I had  to do, was enter my Apple ID, everything else was done automagically.
Ofcourse, having used a Hackintosh for sometime, the OS X experience was nothing new. But I was pissed off a bit by the fact that the new computer didn't come with any inbuilt system recovery option. Even though I didn't have any urgent need to do a system recovery, I tried the much famed "Lion Internet Recovery", where the Mac downloads a recovery image of Lion directly off Apple's server. But  I was heavily disappointed to find that it doesn't work reliably. A little bit of Googling revealed that, I am not the only one, it fails to work reliably for most Earthlings.
Anyway, I used SuperDuper to create a full disk image and stored it away in a external USB drive safely, in case I manage to bork the system in the future.


Popular posts from this blog

Force an application to use VPN, using iptables in Linux

Enforcing an application, for example a torrent client like Transmission, to always use the VPN interface or any particular network interface for that matter, is trivially simple using iptables on Debian, Ubuntu or any other GNU/Linux distro.
Personally, I am running Debian Sid on the Raspberry Pi. Occasionally I use it for downloading files ( legal stuff, seriously, believe me :D  ) using Transmission Bittorrent client over a VPN connection. Sometimes it happens that the VPN connection fails and doesn't reconnect for whatever reason and Transmission continues pulling stuff directly over my internet connection, which I would like to avoid. Fortunately it is very straightforward to enforce rules based on application owner UID. Transmission runs under the owner debian-transmission in Debian (use htop to check this) and the following two lines of iptables ensures that any process with owner having UID, debian-transmission, will not use any other network interface apart from the Open…

Some more fun with SSH port forwarding and socks proxy

Few days ago I made the following post:

Prologue: Our Institute has several nice Dual Core Machines deployed for the students. Unfortunately the machines are behind a NAT with no port forwarded for external SSH access. Student's hostel is a bit far off from the computational centre. As such if someone felt the need of accessing the machines during non-office hours, it was a wee bit difficult. The sysadmin would not have agreed to forward any ports. Something had to be done....

SSH has a very useful feature - Remote and Local Port Forwarding. We have an old rickety PIII running Ubuntu 8.04.1 in the Hostel, it is connected to the net and is accessible via SSH from the internet. Using a tiny little shell script running on one of the machines in the Institute, I managed to make the old PIII an intermediate gateway for gaining SSH access to the Institute's machines from anywhere in the internet. The script is of few lines, but nevertheless powerful enough to serve our purpose.


Raspberry Pi -- Installing Samba (Windows Share) File server

Having successfully run Debian Wheezy on my Raspberry Pi, I went forward with my initial idea of setting up a low cost power efficient file server for accessing my external hard disks from my Windows7 desktop, HP-Mini running Ubuntu and Mac Mini running OS X Lion (yeah I do like bragging about my machines :D ).

This turned out to be pretty straight forward.

As expected, the external Seagate USB disk immediately got recognized and appeared as /dev/sda
[ 579.948350] usb 1-1.2: New USB device found, idVendor=0bc2, idProduct=3001 [ 579.948384] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 579.948405] usb 1-1.2: Product: FreeAgent [ 579.948421] usb 1-1.2: Manufacturer: Seagate [ 579.948447] usb 1-1.2: SerialNumber: 2GEX323R [ 579.967638] scsi0 : usb-storage 1-1.2:1.0 [ 580.970520] scsi 0:0:0:0: Direct-Access Seagate FreeAgent 102D PQ: 0 ANSI: 4 [ 589.142942] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 589.144669] sd…