Archive for the ‘Redirected’ Category


Fedora 12 Constantine on MacBook Aluminum 5,1 [Guide]

UPDATED: 11/22/2009

This is my guide to getting Fedora 12 Constantine running on a MacBook Aluminium 5,1 (I believe this should work on more recent generations as well because the only difference was the addition of the SD card slot and Firewire port). As a general note, this release of Fedora was much better than the previous for the MacBook Aluminium because more things worked out of the box.
[


How To: Install VirtualBox 3 on Fedora 12 [Tutorial]

Updated: 11/22/2009

This is a step by step tutorial on how to get VirtualBox 3 up and running on Fedora 12. Specifically, this guide was written using the VirtualBox 3.0.8 version and an i386 CPU (32-bit). It can be adapted to upcoming versions and different CPUs (64-bit). The folks at VirtualBox have made it easy to install for Fedora users and I’m going to show you how in a few easy steps. Right, open a terminal window and let’s get to it…
[


LaTeX Laboratory Report Template with Many Examples

I have prepared a complete laboratory report template which gives examples of nearly everything a student could need or want in a lab write-up. Most of the document is self-documenting, but for the sections or items that are not, I have commented. You can download it here (the resultant PDF file is included in this zip file and can be seen below):
LaTeX Laboratory Write-Up Template. Edit: Like mentioned in the comments below, if you’re on a Linux box, you’ll need to install texlive-publishers using the command sudo apt-get install texlive-publishers. I’m pretty sure MikTeX and others have package managers that should recognize the need for this package and then fetch it automagically.

This template is geared towards students who are new to LaTeX and would like to utilize the powerful features it has to offer. The main benefit to using LaTeX to write a lab write-up is that you’ll spend far less time formatting your paper, typing equations, and referring back to specific outline requirements for different professors/teachers. The other benefit is that you’ll have a very professional, consistent lab report to hand in and you’ll be able to archive and organize your reports easier. This was something I wish I had done in college.

The reason I put this template together was because I received lots of positive feedback from my professors and peers about the quality of my work; they all wanted to know how I accomplished such a nice looking report. I told them I used LaTeX and they had no idea what it was. I was able to point to a general location where they were able to create a “hello world” document and then they were asking for examples. I wanted them to have the same great experience I had after I got everything figured out (not the bad experience I had while trying to figure it out). In order to do this, I had to make it comprehensive with examples of headers, sections, subsection, figures, sub-figures, equations, equation arrays, references, bookmarks, hyper-links, k-maps, tables, lists, and much, much more. The only thing that this LaTeX file is really missing is a bibliography section with footnotes and references (and that’s another area where LaTeX shines).

If you’re a student looking at this (or even a professional needing better documentation), I hope you’ll write at least one of your lab reports given this template. It might take a little bit longer to get used to writing in LaTeX than in a word processor, but once you see the final result I believe you’ll be hooked like I was. LaTeX has some quirks, but for the most part, it’s an incredible tool for writing technical documentation and lab reports in. It’s a shame most schools only hint at the existence of LaTeX when asking their master students to write a dissertation. I say, there needs to be an optional class or group which can teach anybody LaTeX earlier for college or, dare I say, high school.


Search Quickly Using Boolean Logic [Craigslist Tip]

So, I stumbled upon this by tinkering around on when trying to find myself a car. I thought it was very convenient and made searching much quicker when trying to narrow things down.

If you want to search for more than one specific thing at a time, you can use the OR operand by placing a pipe ‘|’ between the words.

If you’d like to search for very specific things, you can use the AND operand by placing ‘++’ between the words. For example, this is what I entered into the keyword field to search for a car:


I’ve yet to figure out how to exclude certain keywords from the search. If you find out how, please let me know in the comments below.

Update: I’ve used before (previously craigshelper) to help me search for craigslist items beyond my local city. The owner, Nathan, contacted me letting me know he found this blog post and wanted to share his keywords help page here. I thought it was pretty useful, so here it is!


Fedora 11 Leonidas on MacBook Aluminum 5,1 [Guide]

Updated: Jun 25, 2009

This is a continuation of my Fedora 11 Beta on MacBook Aluminum 5,1 notes. I am going to gear this one more specifically on how to get Fedora 11 behaving on a MacBook Aluminum. Here we go…
[


How To: Install VirtualBox on Fedora 11 [Tutorial]

Note: I have been unable to verify these steps. They should work just fine, but I’m a little concerned about the USB support fix. You may or may not want to try it at this point. I have it here just as a reference for now.

This is a tutorial on how to get VirtualBox up and running on Fedora 11. Also, this tutorial is for the 32-Bit version of VirtualBox, so you’ll have to customize a little more to get the 64-bit version running. Everything in the “code” sections should be copy/pasted/typed into the terminal. Right, let’s get to it:

PreStep.) Open the terminal and get into super user mode:
su -

1.) Get the latest VirtualBox package (as of now, 2.2.4) from the VirtualBox website for Fedora 11 and install it.  The following command should download and install the application:
wget && rpm -ivh VirtualBox-2.2.4_47978_fedora11-1.i586.rpm

2.) Get the kernel-devel and other needed packages:
yum install make automake autoconf gcc kernel-devel dkms

3.) Run the setup file for VirtualBox:
/etc/init.d/vboxdrv setup

4.) Add yourself to the “vboxusers” group and fix the SELinux Permissions:
usermod -G vboxusers -a username
chcon -t textrel_shlib_t /usr/lib/virtualbox/

5.) Run, and enjoy!

6.) To Get USB Support:

1 – create a new group called “usb”;
2 – locate file usbfs: in my case is /sys/bus/usb/drivers (I suggest to find the file with a usb device inserted;
3 – modify file /etc/fstab inserting a line containing the right path and the number corresponding the “usb” group :
none /sys/bus/usb/drivers usbfs devgid=503,devmode=664 0 0
4 – command mount -a;
5 – start VB and try…;

Source: Fedora Forums

7.) To Properly Backup the VirtualBox Machine (.vdi):

Please refer to my other page here:

How To: Properly Backup a VirtualBox Machine (.VDI)

8.) To Get Sound Working:

Highlight your virtual machine and click on the “Settings” button. Click on the “Sound” category, and then check the “Enable Sound” option. In the drop-down box, select “PulseAudio”. You should now have sound.

That’s it! If you find yourself with problems, feel free to comment below or ask for assistance on the fedora forum thread that I have created located here.


Including a Program Source File in LaTeX [Tip]

This is a command within LaTeX that I forget constantly and I always lose the resource from where I learned about it. So, I’m documenting it here so that I can find it later on when I need it. I also figured it might help somebody else out there looking for the same thing.


Basically, what this little code snippit does is import a source code file and inserts it into the final document. It’s a lot easier than copy/paste and it has a lot of formatting options associated with it. Just check out the lstset command manual or this guide here or this guide here (LaTeX wikibook). Be sure to include the listings package with this declaration before the main document: usepackage{listings}.


Fedora 11 Beta on MacBook Aluminum 5,1

UPDATE 05/09 (2) – I just installed Fedora 11 on my MacBook. I’ve also created another post which will deal with taming this beast. Please refer to it here:

UPDATE 05/09 – It’s the big day today. Fedora 11 was just released to the public. I’m in the process of downloading it and soon I’ll be able to update the steps that I’ve taken to get it working on my MacBook. I hope this will be of help to somebody.

UPDATE 05/07 – So, I’ve updated a few things and I was able to use RPMFusion’s repo to install the wireless and video card drivers. Unfortunately, the one last system update I ran totally destroyed my Fedora installation. I’ll just be waiting for the big release day.

UPDATE 04/22 – Nothing new to see here. I’ve tried to install the wireless and video card drivers using RPMFusion’s repo, and I keep getting these dependency errors. I’ll try again when the Release Candidate comes out.

The purpose of this post is to 1.) provide an update from the last time I posted on the progress made with Fedora on a MacBook Aluminum and 2.) serve as documentation while I fiddle with this and that trying to get everything to work. Things will change around here, so check back as you get the chance!

As of now, I’m tying this from my Fedora 11 Beta installation on my MacBook via Ethernet. Here’s what seems to work right from the box:

  1. Ethernet Port
  2. Graphics (Thanks to nouveau.)
  3. Volume keys bring up the volume notification, but no sound.
  4. USB Ports (Why wouldn’t they?)
  5. CD-ROM Drive (Eject button works too!)
  6. Web Cam (Needs color calibration badly)

Things that aren’t working:

  1. Trackpad (Worked on the LiveCD)
  2. Function keys (backlight, etc)
  3. Sound from Speakers
  4. Sound from Headphone Jack
  5. Wireless
  6. Desktop Graphics
  7. System Restart (you’ll just get a black screen if you try, but hey, no beeping this time!)
  8. Battery Status (GNOME Power Management thinks it’s a dead battery)


  1. Keyboard keymap is strange.
  2. Full screen flash is still unusable with Nouveau drivers. (Haven’t tried Nvidia drivers yet)
  3. Seems to me that the MacBook is running hot.
  4. Fonts seemed stretched vertically.
  5. Battery life isn’t as good as in Mac OSX.

So, for right now, I’m going to use my old guide as far as I can and then report back here with what works. Check back if you’d like, because this post is going to be updated as I get things working.


From F-Spot to iPhoto (or Picasa): Transfering Keywords [Tips & Tricks]

This was taken and adapted from a gentleman in Michigan.

This is a trick to get your keywords to show up in iPhoto (or even Google Picasa, as it turns out) after using F-Spot as your photo manager. Basically, you take a tool that will allow you to manipulate the metadata (EXIF) information of your digital photos. In this case, it will be used to copy the keywords location of F-Spot into the keywords location of iPhoto. Both applications will then have access to the keywords that you’ve added.

I did change the original post a little bit by making a correction to the keywords location. It seems that F-Spot keeps it’s Keywords in XMP:Subject which needs to be copied to the spot where iPhoto will recognize the keywords in IPTC:Keywords. Moving on…
[


Fedora 10 and the MacBook Aluminium (5,1) [Guide]

Without boring you too much with the details, I recently purchased a new 13.3″ MacBook Aluminum (Intel C2Duo 2.4Ghz) with the uni-body design.  It’s one heckofa laptop and I would recommend it to anybody.  However, I’m having a very difficult time getting used to the Mac OSX environment and the programs that it uses and I dearly miss Fedora 10.

So, I’ve gone through the process of tripple booting my MacBook with several different partitions for Mac OSX, Windows, and Linux each having access to what I call a shared partition formatted in the HFS filesystem so that all OS’s have access to the files on that “home” drive.  I plan on making Fedora my main OS on this machine.  After installing and fixing some of the issues that I will outline below, there are still some issues that are unacceptable at this time, namely 1.) the backlight control, 2.) the sound, 3.) the touchpad, 4.) the keyboard keymap, and 5.) three (3) error beeps when rebooting.  A program called pommed, which controls backlight and hotkeys, just may take care of some of these issues, but the version packaged with Fedora is outdated and needs to be replaced with pommed version 1.23 (at least, newest version is 1.25) which also requires the Linux 2.6.28 kernel to run.  This means that either you’ll have to compile the kernel yourself, or wait for the update to come through Fedora on it’s own (be it through the package manager or waiting until Fedora 11).

In order to help other Fedora MacBook users, here are the steps I have taken to get 1.) the video card, 2.) wireless, 3.) headphone jack sound, 4.) minor touchpad functionality, 5.) a little better keyboard mapping to work, and 6.) the iSight webcam.

Video, Wireless, and FirstBoot

Upon startup of a freshly installed Fedora 10, users will notice that they had to go through a non-graphical installation and then once Fedora was installed, they were met with despair when they only had access to a command line interface (CLI).  This is because the video card drivers have yet to be installed.  The good news is that the Ethernet Port still works, so find a hardwired connection and type the following into the command line after you’ve logged in using “root” as the username:

rpm -ivh
&& yum install -y kmod-nvidia kmod-wl

You will now have video and wireless support, but stay connected via hardwire while you’re there and type the following into the terminal:


If this doesn’t give you a nice GUI (sorry, I can’t remember), then type “startx” which will get you into the GUI and then from there, open the terminal and type in “firstboot”. This will walk you through and help you setup your username and password as well as a few other things.

Next, if you’ve installed Fedora in text mode, you will always be defaulted to text mode upon boot. To fix this type the following into the terminal:

gedit /etc/inittab

Then make the following change to the last line in that file:


Speaker Sound

I don’t think there has been anybody to figure this one out quite yet for Fedora. It seems that a few people over in the Ubuntu world have been able to get it to work. I’ll refer you to a couple good resources to follow:

Apparently, some distros have recommended using a sound mixer application (any) to switch from 2ch to 6ch, save the settings, reboot and enjoy.  At this point, it’s either the speaker sound or the headphone jack… not both.

Headphone Jack Sound

Please view this thread over at the Fedora Forums:
How to: Fix PulseAudio and primary audio issues with Fedora 10 (F10)


It seems that the guide posted over here works well for the touchpad. I’ve yet to personally test it.

Keyboard Keymap

Within the “System->Hardware->Keyboard” menu, there is a place to select what kind of keyboard you are using. Simply select, “MacBook” and that will help out a little bit. I’ll try and get a little more specific on this soon.

iSight WebCam

You will need a copy of the firmware from Apple. You can either download this here or simply type the following into the terminal:

su -c 'wget'

Then you’ll need the isight-firmware-tools package, so type this into the terminal:

su -c 'yum install isight-firmware-tools'

Then, from the same directory that you downloaed the AppleUSBVideoSupport file into, type the following into the terminal:

su -c ift-extract --apple-driver AppleUSBVideoSupport

Honestly, this could probably all be done swiftly with one command, but I haven’t tested it yet:

su -c 'wget && yum install isight-firmware-tools && su -c ift-extract --apple-driver AppleUSBVideoSupport'

You’ll need to reboot to take advantage of it.

Other Issues:


If I were to make a conclusion (and so I have), I would have to say that, at this time, Linux is not ready for the MacBook Aluminum.  If you’re a beginner installing Linux for the first time, then I would seriously recommend waiting for another 6 months or so when the software has been able to adapt.  Knowing the aggressiveness of Linux, it won’t be too long before this generation of MacBooks will be fully supported.


Next Page »