Here’s my first take on a Xen network that I’m putting together for work.

This all takes place in one physical box with 2 physical network interfaces. I’m still not sure this is path we’ll take, but it’s a start. Also, it might have been less complex if I did routing and NATing in Dom0, but for security reasons, I’ve opted to keep Dom0 very minimal. I’ve even considered leaving it off of the network (console only). Any thoughts/suggestions?
Update: As pointed by a confused (but observant) reader… There is no such thing as fif3.0. It should have been labeled vif3.0. Good eye. Guess I was a little sleepy when working on it :)
I’ve installed what I’m pretty sure will be the final version of FC6 (I checked the SHA1SUMs from a listing at an official mirror). Here are my first impressions:
Mono seems to be totally jacked:
[gabe@office ~]$ tomboy
Segmentation fault[gabe@office ~]$ mono -V
Segmentation fault[gabe@office ~]$ mcs
Segmentation fault[gabe@office ~]$ sqlsharp
Segmentation fault[gabe@office ~]$ gmcs
Segmentation fault[gabe@office ~]$ echo “Segmentation fault”
Segmentation fault
O.K. that last one isn’t that disturbing, but the others look pretty messed. I’m guessing they didn’t build it with a “–with-xen_opt=yes” flag. I’m running this box on Xen, but if you don’t, I’m guessing Mono would work just fine. That brings me to my next point…
When installing, it has an option for Xen related tools. I selected them to be installed. I assumed it would install a few userland tools for monitoring and creating Xen instances. I further assumed it would install an additional Xen kernel and add that option to GRUB. To my surprise, it only installed a Xen kernel. This would be the first time that any distro, that I’ve run, has done this out of the box. I’ve stated before that I thought this would eventually be the norm. Please note that this is not the default behavior.
One major plus is that the bubbles are gone. If you used FC5 and have good taste or a sense of style, you know what I’m talking about. The DNA strands are much, much better, but still, they are not great.
The new font (DejaVu) looks pretty good. Hinting is still a little off on some uppercase letters.
I was hoping Firefox 2 RC 3 would have been dropped in. I know, at some point you have to say “no” to new packages.
Evolution seems a little bit snappier. I don’t follow it’s development, so I have no idea what to attribute that to.
There are still 101 services that startup when you boot. Shutting half of them down is still the first thing I do after I install.
Clearlooks has nice controls but the icons and the window borders look average. I see icons from old GNOME, RH9, old Blue Curve, Tango, etc…
That’s the short list. Overall, I like it better then FC5 so far. I still think Ubuntu has done a better job pulling it all together, however I’m using FC because of it’s solid Xen support.
I’ll add to this list if anything interesting shows up in the next few days.
If this needs explained, you won’t think it’s cool anyway ;)
vi /etc/asterisk/extensions.conf
;; Call hacks.
[hacks]
exten => 411,1,Dial(${TRUNK}/18003733411)
It makes it so that when you dial 411 (directory service) your call actually goes to a free 411 service. Myself, I have a hard time remembering long toll-free numbers. This makes it easy and free!
Today’s screenshot is brought to you by the Django Admin interface:

For those of you who don’t recognize this, it’s the GNOME System Monitor applet. The dark blue basically represents CPU usage for Django (more accurately - caused by Django). The model validates [1] and the tables/Models are shown in the front page of the Admins interface. Most of the Models are represented well and work as one would expect. However, there is one table/Model that doesn’t work as expected. It works OK when you go to add an additional record [2], but when going to view items before changing them [3], it causes the CPU to spike and three minutes later I have my results. Before I edited the table/Model to remove one of the ForeignKeys, I would get a PostgreSQL error because Django passed it a SELECT statement with *over* 1664 entries [4]! Well, it seems that by editing the table I was able to keep the entries under the 1664 limit and PostgreSQL would process the SELECT, but it takes forever to finish it.
I guess that technically, the CPU is being eaten up by PostgreSQL, but that’s not really the point. The point is that Django really doesn’t have any business sending it a SELECT statement with some 2000+ entries in it (especially for such a simple, simple request.) OK, so maybe it has a bug, limitation or whatever, I’m cool with that - it happens. The frustrating part is that I can’t confirm that this is a known problem or find the answer. The answer I’m looking for should be simple, but I have not been able to find it. IRC and #django was a bust and the mailing list yields nothing yet.
I was pretty enthusiastic about Django, but maybe it’s to soon. It’s a cool project and I wish them luck. I’m just wondering if all the time spent so far porting one of my apps to the Django framework was time wasted or not.
1) -
./manage.py runserver
Validating models…
0 errors found.
2) http://localhost:8000/admin/App/Model/add/
3) http://localhost:8000/admin/App/Model/
4) -
Request URL: http://localhost:8000/admin/core/stagedorder/
Exception Type: ProgrammingError
Exception Value: ERROR: target lists can have at most 1664 entries SELECT
I don’t have a ton to say right now (really, I don’t have a lot of *time* to say it), but first impressions of Python and Django are very positive. The admin interface is a great little tool to get things going FAST. I’m really, really impressed. The CREATE TABLES are clean, the SQL is clean and the DB API is clean (different, but I can learn to like it); I’m really enjoying it. How often can you say that?


Extra points for:
- PostgreSQL as preferred database.
- Template system that strikes a good balance.
- Powerful and clean URL handling.
- Modular design.
Needs work:
- Namespace support for PostgreSQL (app_table vs. app.table).
- Keeping data model and DB schema synced (this might be in a better state then I know; I need to read up on it).
This blog details a new service that allows you to make FREE phone calls… there are strings attached.
The deal is that you get a free 6 minute phone call, but you give up your privacy. The calls get published on the Internet for the world to hear. It’s better then tapping the pay phone at the state liquor store at 2:00 A.M. And so, we now get to sit and listen as people “air their dirty laundry” to the world for the price of a 25 cent phone call. Jerry Springer has nothing on these guys.
From the source blog:
He (James Bowman of for60secs.com) explained that they envision a few different kinds of user for the phone service, such as people who are very price-conscious or shameless self-promoters who view it like reality TV - you give up privacy in exchange for fame.
And now you will never have to wonder “So she is 100% alive?” Warning: many of the calls contain strong language.
How did this information cross my path? It’s powered by the very cool Open Source Asterisk PBX.
Reading this made me feel better about my goals that can seem a little ambitious at times:
My objective is to Re-master Fedora Core 5 into a single CD…. am pretty much new to Linux… I have about a weeks time to accomplish this…
Good luck my newbie brother. The command line is your friend. Let Google be your companion. Use the source. May your weeks be long.

How come I can’t settle on a Jabber server? I’ve tried them all and none sticks out as my clear favorite. They all have things I love and hate about them. Oh well, I’ll pick one and get it running soon. I think I’m going to base my decision on which one has the best LDAP support.
Any ideas?
P.S. If you need me before I get my jabber server re-installed, I can be reached by email at the same address [gabe (a) gundy.org].
My brother Jordan (A.K.A. jordy) and I have salvaged a motherboard or two with bad caps on it. It can be a sweet way to get a cheap desktop system (do *not* try this with your server). It doesn’t seem like MBs are plagued by bad CAPS like they were 4-5 years ago, but you still see them from time to time. Anyway, here is a sweet write-up on the whole process. It’s a good way to go if you like to tinker, feel good about saving $ and are good with a soldering iron.

Recent Comments