Comments for /dev/rant

Comment on Mount LVM-based volumes from loopback full disk images by Ross Golder

Ross Golder — Thu, 11 Mar 2010 05:55:14 +0000

Handy tip to avoid the need to unload/reload ‘loop’ module (i.e. it’s compiled in!)…

Find the offset of the LVM partition in the file image using the ‘file’ command…

root@zeus:/data/kvm# file hermes.img
hermes.img: x86 boot sector; GRand Unified Bootloader, stage1 version 0×3, boot drive 0×80, 1st sector stage2 0×11c41; partition 1: ID=0×83, active, starthead 1, startsector 63, 208782 sectors; partition 2: ID=0×8e, starthead 0, startsector 208845, 104647410 sectors, code offset 0×48

Then, setup the loop device with an appropriate offset into the file, based on the start sector of the partition multiplied by the block size…

root@zeus:/data/kvm# losetup -v -o $[512*208845] /dev/loop0 hermes.img
Loop device is /dev/loop0

Now, go get LVM to recognise it…

root@zeus:/data/kvm# lvm pvscan
PV /dev/loop0 VG VolGroup00 lvm2 [49.88 GB / 0 free]
Total: 1 [49.88 GB] / in use: 1 [49.88 GB] / in no VG: 0 [0 ]

Comment on In Silicon Valley for the summer by Storage and scale | /dev/rant

Storage and scale | /dev/rant — Sun, 07 Mar 2010 22:37:50 +0000

[...] 2008, I worked at IBM Research Almaden on a project called Panache. I was recently pleased to find that an [...]

Comment on Chrome extension: edit Gmail textarea in an external editor by davidhi

davidhi — Mon, 08 Feb 2010 01:03:25 +0000

Thanks for your comments, Christian.

Regarding your first question, I’m just starting my Python web server manually. Since this was just a little project for my own uses, and I only restart my web browser or system once every few months at most, starting up the Python part isn’t a big deal for me.

Thanks for pointing out that I have no easily-accessible contact info. I updated my About page to point to my college webpage (which has contact info) and added an email address. As far as working more on the concept, I’d like to but I just graduated and I’m currently in the process of interviewing for jobs, so realistically I don’t think I’ll have any time for it in the near future. I’ve been also meaning to write a few new posts for my blog, but there’s no time for that either.

Comment on CentOS / RHEL repo madness by davidhi

davidhi — Mon, 08 Feb 2010 00:48:37 +0000

No problem — these are just the kind of comments I want. I’m glad it helped.

Comment on CentOS / RHEL repo madness by Kryten42

Kryten42 — Sun, 07 Feb 2010 05:03:50 +0000

Oops! I perhaps should have added that for me the conflict was mainly due to version conflicts between the rpmfusion-free and the rpmforge repo’s. MPLayer in rpmforge was 1.0.0.41, and in rpmfusion it was 1.0.0.101 and it was confusing because of the date stamps, ie: 1.0.0.41.svn20090711.el5.rf & 1.0.0.101.20080903svn.el5.1

One would intuitively think that the higher version # would have the more recent date, and the formats are different also. I love standards! There are sooo many of them! LOL

Sorry to SPAM your comments!
K42.

Comment on CentOS / RHEL repo madness by Kryten42

Kryten42 — Sun, 07 Feb 2010 04:48:41 +0000

*sigh* why didn’t I find this earlier? Could have saved myself a couple days insanity! LOL

Once you pointed out the yum repo conflict issue (what should have been obvious to me), problems solved. Installed both VLC & MPlayer.

BTW, using Yum Extender (the yum GUI that comes with CentOS) makes it a lot easier to temporarily disable the repo’s and erase the previous install attempts if any. Basically, just disable all repo’s except the CentOS standard and RPMforge & RPMforge-testing repo’s.

I also had to erase the packages Richard mentioned above, and also : faac, faad2, ffmpeg, ffmpeg-libpostproc.

Using Yum Extender also made it easy to install the additional MPlayer bits if you want them, such as:

mencoder-1.0-0.41.svn20090711.el5.rf.x86_64
mplayer-1.0-0.41.svn20090711.el5.rf.x86_64
mplayer-docs-1.0-0.41.svn20090711.el5.rf.x86_64
mplayer-fonts-1.1-3.0.rf.noarch
mplayer-skins-1.8-1.nodist.rf.noarch
mplayerplug-in-3.55-1.el5.rf.x86_64
ogmrip-0.11.2-1.el5.rf.x86_64
smplayer-0.6.8-1.el5.rf.x86_64

All from the RPMforge repo.

Thanks again, and I hope this helps someone.

Comment on Chrome extension: edit Gmail textarea in an external editor by Christian Höltje

Christian Höltje — Fri, 05 Feb 2010 15:26:08 +0000

PS: I don’t see how to contact you directly. If there is a link, I don’t see it. You can reach me at http://docwhat.org/mail if you are interested working more on generalizing this concept.

Comment on Chrome extension: edit Gmail textarea in an external editor by Christian Höltje

Christian Höltje — Fri, 05 Feb 2010 15:13:13 +0000

Interesting. I hadn’t considered this approach. There are some real advantages to this approach.

The downside is that python (or perl in the case of TextAid) is required, which isn’t a great requirement for Windows. :-/

I’m going to take another look at this and see if I can make this work in a more cross platform way and possibly port the idea back to IAT for FF.

How are you starting the python web server? Is that done externally or from within the extension?

Ciao!

Comment on Chrome extension: edit Gmail textarea in an external editor by Mark Stosberg

Mark Stosberg — Sat, 09 Jan 2010 14:22:19 +0000

A formal Google Chrome extension has been released which works basically the same way, although the web server is written in Perl. It’s called TextAid…and it defaults to opening Vim rather than Emacs.

https://chrome.google.com/extensions/detail/ppoadiihggafnhokfkpphojggcdigllp

Mark

Comment on Chrome extension: edit Gmail textarea in an external editor by Alex

Alex — Wed, 30 Dec 2009 12:37:42 +0000

OK I’ve done some fixups and restored the behaviour of the toolbar button. I’ve tagged 1.1 and published the extension. It should be showing up on the Google extension gallery once it has been through the approval process.