Monthly Archive for April, 2007

Respinning Fedora Core 6

My favorite distro updates its packages frequently. If I wanted to install a new FC6 system, I would have to do updates all over again. So I decided to try the respins, which are distributions that contain the latest updates from the official repositories.

However, Fedora Unity, which packages the respins, currently only offer torrents. It’s not that I don’t like torrents, it’s just that I can’t use them. There was mention of Jigdo for the respins, but I can’t find the .jigdo nor .template files. Update: Jigdo files are available now.

I was left with no option but do my own respin. Enter pungi:

The pungi project is two things. First and foremost it is a free opensource tool to spin Fedora installation trees / isos. It will be used to produce Fedora releases from Fedora 7 on until it is replaced by something better. Secondly pungi is a set of python libraries to build various compose like tools on top of. Pungi provides a library with various funtions to find, depsolve, and gather packages into a given location. It provides a second library with various functions to run various Anaconda tools on the gathered packages and create isos from the results.

So here’s what I did:

  1. Install pungi. Since it’s in Fedora Extras, it was a simple yum install pungi.
  2. Create my own configuration file:
    # Pungi config file
    [default]
    product_name = Fedora Core
    product_path = Fedora
    iso_basename = FC
    comps = /home/d3m/pungi/comps-fc6.xml
    yumconf = /etc/yum.conf
    destdir = /home/d3m/pungi/i386
    cachedir = /home/d3m/pungi/cache
    arch = i386
    version = 6
    discs = 5
    getsource = No

    Note that I used my Fedora box’s yum.conf to get packages from the repos I set there.

  3. Create a working directory for the pungi files, and in it, two subdirectories for the destination and cache:
    $ mkdir -p ~/pungi/i386; mkdir -p ~/pungi/cache
  4. In the working directory, I placed the comps.xml and config file.
  5. Run pungi as root:
    $ sudo pungi -c pungi.fc6.i386
  6. If all goes well, there would be ISOs under ~/pungi/i386/6/isos.

I hit a few snags. Sometimes, because of connectivity issues, pungi failed to download some RPMs. When I reran pungi, it would fail because there are already existing RPMs in the cache and destination directories. That meant I had to start all over again: delete all previously downloaded packages and run pungi again. Pungi also failed when there were no associated source RPMs for certain packages — weird, that one. I had to turn off downloading of the sources in the config file (getsource = No).

Through all that, I was finally able to get DVD as well as CD ISOs.

Nokia makes an offer you can’t refuse

Har, har.

Presenting the Nokia N73 Godfather edition. Comes with a 256MB SD loaded with The Godfather for your mobile viewing pleasure.

N73 Godfather

Via Gizmodo.

Kurt Vonnegut, 84

Credit: Fred R. Conrad/The New York Times
Credit: Fred R. Conrad/The New York Times

Remote desktop through SSH

I sometimes telecommute. And when I badly need some files on my office desktop, I can connect remotely through the company’s SSH gateway and tunnel RDP to my desktop. Here’s how:

  1. Using PuTTY, create a new session for the SSH gateway.
    PuTTY session
  2. In Connection > SSH > Tunnels, add a new forwarded port: the source can be an arbitrary port number (e.g. 4444) and the destination should be the address of the remote desktop with the port set to tcp/3389 (the RDP port). Make sure the “Local” is selected because we will be forwarding the local port (4444) to the remote desktop’s port (remote.desktop:3389).

    Set tunnel

  3. Connect and log in in the SSH session. (We use one-time RSA SecurID passkeys, so I always keep that nob handy.)
  4. In Windows XP (yes, my notebook is still not free), open up Remote Desktop Connection, add connect to localhost:4444. This should then be forwarded through the SSH session to the remote desktop port 3389.

    Remote desktop connection

  5. You would have to authenticate again, and if all goes well, you’ll be presented with your remote desktop.
    Remote desktop

Steps 1 and 2 above can also be achieved from the command line, using Plink:

C:\> plink -N -L 4444:remote.desktop:3389 user@ssh.server.org

Take note that the SSH gateway must be able to forward tcp/3389. (Setting that up is beyond the scope of this post. ;)) It would have been great if the VNC port (tcp/5900) was set up as well, but unfortunately, only RDP is allowed. So to connect to my Linux box at work, I either use SSH or, in the remote desktop, open up TightVNC. It looks a bit surreal: having a remote desktop within a remote desktop.

Julian

Julian
Originally uploaded by iandexter.