Saturday, February 28, 2015

cubietruck setup, though my card reader is flaky

Finally setup my cubietruck that I purchased late last year. Here it is under my desk running Fedora 21:






Riveting, I know.

I mostly just followed bits from Rich's and Kashyap's blog posts, and the Fedora ARM install instructions. I used this serial adapter, though note you need to make sure to make sure the TX pin on the board is wired to the RX pin USB end, and vice versa. Probably obvious to some people but I would have been stumped if I hadn't seen it mentioned in an Amazon review.

Everything is working now but my hardware has a bit of a malfunction that I mentioned in this fedora-arm thread. Basically the device can boot off the SD card, but linux doesn't detect it. If I wiggle the card around a lot while inserting it I can get linux to detect it about 1/5 of the time, but after rebooting the device is back to not being detected. In the thread, Hans guessed that the card-detect pin is flaky or not connecting well, but it doesn't affect the cubieboard firmware which just ignores that pin and assumes the device is present.

Since I was planning on using a SATA drive anyways, this isn't that big of a deal, just delete everything on the SD card except u-boot, and the SATA drive will be used /boot and /. But if I ever want to update u-boot on the SD card, I'll have to go through the whole wiggle process again and manually 'dd' it into place using the steps on the Fedora install page.

Monday, February 16, 2015

Fedora 22 Virt Test Day scheduled for Thu Apr 16

Just a quick note that the Fedora 22 Virt Test Day is scheduled for Thursday April 16th. The inprogress landing page is at:

https://fedoraproject.org/wiki/Test_Day:2015-04-16_Virtualization

If you're interested in helping out please mark your calendars.

Friday, February 13, 2015

git up: The better git pull

A while ago I stumbled across a nice git extension 'git up'. The README synopsis lays out the motivation:
git pull has two problems:
  • It merges upstream changes by default, when it's really more polite to rebase over them, unless your collaborators enjoy a commit graph that looks like bedhead.
  • It only updates the branch you're currently on, which means git push will shout at you for being behind on branches you don't particularly care about right now.
Solve them once and for all.
As implied above, git-up will update all your branches that are tracking a remote branch. This often comes in handy in fedora git repos:

 [crobinso@colepc openbios (master)]$ fedpkg pull  
 Already up-to-date.  
 [crobinso@colepc openbios (master)]$ git up  
 Fetching origin  
 f20  fast-forwarding...  
 master up to date  
 returning to master  

Another useful bit is that it will stash and unstash uncommitted changes. Often times I find myself doing this:

 [crobinso@colepc ~]$ cd src/virt-manager/  
 # Hack some minor bug fix  
 [crobinso@colepc virt-manager (master *)]$   
 # Oops, I should pull first, maybe the issue is fixed  
 [crobinso@colepc virt-manager (master *)]$ git pull  
 Cannot pull with rebase: You have unstaged changes.  
 Please commit or stash them.  
 [crobinso@colepc virt-manager (master *)]$ git up  
 Fetching origin  
 stashing 1 changes  
 master up to date  
 unstashing  
 [crobinso@colepc virt-manager (master *)]$   

Nowadays I don't even attempt the pull, git up is my reflex. (And yes I should just make it a reflex that I switch to a branch before doing any hacking...)

Nice to see that nowadays git-up is packaged in fedora, so grab it with sudo yum install rubygem-git-up