reseting home folder permissions in ubuntu linux

If you are like me and my coworkers, you often end up running stuff as root in your home folder and end up not able to access your own files.

For the record, here's the commands to reset the permissions (leaving all execute flags off, which may not be what you want).

Warning, this could have undesired side effects. If you have executable files in your home folder that you actually want to be executable, you will have to manually mark them as executable again.

# Become root (as you don't currently have permissions to modify your own files)
sudo -i

# Reset ownership & group to yourself
chown -R tim:tim /home/tim

# give yourself the default read-write permissions, set group and other to read only
chmod -R 644 /home/tim

# re-apply excecute permissions on all the directories
find /home/tim -type d -print0 | xargs -0 -II chmod 755 'I'

# Don't leave your private keys showing:
chmod -R 700 /home/tim/.ssh

My latest use for this was after extracting files from my p910i with p3nfs, which as with so many desktop/device tasks needed root to work.

You could do this slightly more neatly if you know what permissions you have ended up with by using chmod u+w etc so you don't have to re-apply directory permissions, but I wanted to easily guarantee permissions are right regardless of what state they have ended up in.

It occurs to me it might be sensible to set the sticky bit on the home folders so that anything added by root stays owned by the user. (chmod u+s g+s /home/tim)

Don't trust audible.com, it's drm infected and they don't tell you

If there's one thing I hate (there isn't, there's lots, but this is today's) it's companies being economical with the truth to get you to part with your money, only to have you disappointed when you find out the whole truth.

I just bought an audio book on audible.co.uk. And now I can't even listen to it. I thought I was buying an mp3, or maybe even an ogg file. It is only on actually attempting to download the thing I have just paid for that I discover to my utter disgust that all the download links are for some kind of evil drm type program (I presume here, but there sure as hell was no mp3 in sight).



As you can see from the screenshot above, they clearly imply an mp3 download. I haven't seen such a clear use of weasel sales words for some time.

Next time I'll read the god damn small print, but I still think this is totally out of order not warning that they are providing crippled versions of what you think you are buying.

Thank fsm for people like the FSF. Their logo really sums up how I feel about being treated in this way.

Protect your freedom!

---

Update: credit where due. 24th July 2008.
My complaint about the website still stands, and my aversion to drm has not diminished, however the responses I have received from their customer service (by email), have been prompt, courteous and have totally resolved my outstanding problem. I have been given a full refund. I've been especially impressed given the hot blooded content of my initial contact. A lot of companies could learn lessons in good customer relations from these people.

work at emapsite

The company I work for, emapsite is hiring a developer.
Interviews are starting so you'll have to be quick.

More details available on their news item.

New wiki, mostly for car pc

I've created a wiki at wikispaces.com, to document things that are less transient than a blog entry.

Take a look at http://timwise.wikispaces.com/

I've started adding information about the car pc, and won't make any promises about what else I'll be adding (personal motto: under promise, over deliver).

I've made it open to all editors, and licensed under the GNU Free documentation licence to ensure the maximum value, reach and participation.

Nightly Shutdown, a new product from Proven Works

Congratulations to Joel Mansford, a good friend of mine, and his company Proven Works on getting the first release of Nightly Shutdown out of the door.

This looks to be a great product and hopefully will make system administrators' lives easier and greener. It's a utility for ensuring that the computers are off when you want them to be, and can be deployed through active directory making the sys admin's life easier. There's a 10 PC free trial available, so check it out at the download page.

Without even looking I know this will be a good product and fantastically well supported. Best of luck to all at Proven Works, and to all the potential users and buyers out there, don't forget to check it out and provide any feedback you can.

A vision of open in-car computing systems

I have a vision. A vision that puts you in control of your in car computing experience.

There are many superb appliances and embedded devices available for your in-car enjoyment, such as the sat navs, the dvd players, the built in games consoles. But they all share one thing in common, they are closed to you. You don't have the freedoms defined by Stallman because they are designed, intentionally or otherwise, to be hard for you to modify as you wish.

I feel deep in my heart that there is enormous potential for in-car computing. There are more possibilities than any individual or company can imagine or provide on their own. I'm sure my imagination is not big enough to list them here, so I leave the ideas for you to contemplate.

Add to this, the evidence and my experience that open source when done right produces the better engineered solution at a lower cost, and you have a compelling argument for such a system.

I have seen the freedom that open source and the GPL provide on the desktop computer, and I believe that this culture of openness and freedom for the users can be applied to the in-car computing market to the benefit of all.

My mission is to provide a basis for this innovation, and cultivate a thriving ecosystem in the way that only open systems can. And so, my vision is a range of affordable flexible and most importantly open computing devices for your car.

And so, I introduce to you in the above photo, the mark one of my in-car pc. It has no name, and the software and hardware needs some work to say the least, but in the tradition of openness on the internet, I will present here my ups and downs, successes and failures, genius and downright stupidity for your entertainment.

I have minimal spare time and numerous other projects, but there is no rush, as I think this plan will stand the test of time, and all the while hardware gets cheaper, smaller, faster and less power hungry. As I progress in fits and starts I will post photos to flickr under the tag carpc (first set) and progress updates to this blog under tag carpc.

All feedback welcome. I will announce new articles on my twitter feed, twitter.com/tim_abell, and can be contacted using the links at the bottom of my blog.

sharing work between computers with a usb flash drive and git

I couldn't find anything exactly matching this on the net when I was figuring it out, so here's what I did.

This is working against a remote svn (subversion) server, but applies even without one.

On the first computer, grab your git working copy from svn with git-svn clone (or clone a git repo, or just start a new one).

mkdir ~/project.git
cd ~/project.git
git-svn clone svn://project-server/trunk
git repack #for good measure

Plugin your usb flash drive/stick/external harddrive, I'll presume it's a vfat/fat32/fat16 formated device mounted at /media/flash.
Create an empty repository on the drive, I'll use a bare one as there's no need to keep the working copy as well.

mkdir /media/flash/project.git
git --bare init /media/flash/project.git

Then add the flash drive git repo as a remote source in your local git repo. "flash" is the name I've given to the remote branch reference, you can call it whatever you like.

git remote add flash /media/flash/project.git

If you push immediately it will fail (as I discovered) because fat doesn't support the execute flag on files, so all the hooks are automatically active. I deleted all the hooks as I wasn't planning on using them, this may be wrong so no promises, but it seems ok so far for me. So remove the hooks with:

rm /media/flash/project.git/hooks/*

Then push your current local copy to the flash drive with:

git push flash

This will copy all your committed work onto the flash drive, even if you haven't pushed it upstream to the svn server with "git-svn dcommit" yet. Bonus! It won't copy any of your branches across though, so you if you want them you can add those independently with:

git push flash mybranch

Now move over to the second computer and plug the flash drive in. I'm making the same assumptions on paths and devices. Do another completely independent svn checkout as above:

mkdir ~/project.git
cd ~/project.git
git-svn clone svn://project-server/trunk
git repack #for good measure

Then add the flash drive's repo to the git repo on the second pc and pull all changes from the flash drive, optionally including any branches:

git remote add flash /media/flash/project.git
git pull flash master
git pull flash mybranch #if you like

When you've committed changes to git or pulled the latest changes from svn on either pc, you can then update the flash drive with the simple command:

git push flash

Which pushes all your changes on your master branch on to the flash drive. You are now ready to run the pull command on the other computer to get back in sync:

git pull flash master

If you don't push changes to the flash drive before committing to svn then things will be very simple. If you push changes to the flash drive, and then commit them to the svn server you will need to do a little more work. This is because when you run "git svn dcommit" it pushes your latest git commits to the svn server, deletes your locally committed changes, and then fetches them back from the svn server. This means that git won't recognise your local changes as being the same as the ones on the flash drive because they have different commit message and SHA1 hash. Attempting to push to the flash drive fails with the message "! [rejected] master -> master (non-fast forward)" as the old copy of the commits are still there.

To resolve this you need to throw away the matching set of changes on the flash drive. To do this you can use git reset as follows, where HEAD~1 should be the number of commits you need to throw away (eg HEAD~3 to throw away the last 3 commits that were pushed to the flash drive):

cd /media/flash/project.git
git --bare log #to see how many changes don't have svn information
git --bare reset HEAD~1

You can then push your changes as above.

cd ~/project.git
git push flash

I've glossed over subtleties with fetch vs pull, but hopefully you will find this useful.

This howto makes use of git's ability to pull from multiple sources, and I've found that git quite happily copes with changes that were checked in to svn coming via the flash drive, even when later running "git-svn rebase".

Please do comment or contact me with any problems, errors, extra info and feedback, and let me know if it was useful.