NFSv4 on Solaris and Netapp

Hit a peculiar problem today with a new Solaris 10 T2000 and our NetApp FAS3020.  While the right users had the right access to the volumes mounted from the NetApp, directory listings showed the directories and files owned by “nobody” with the group “nobody”.

With older version of NFS, this usually meant that the filesystem was not exported with read/write access to the host, but, since this had already been done quite some time ago, it looked like the problem was related to NFSv4.   Some quick investigation showed this to be the case.

The resolution was two fold:

  1.  On the Netapp, I make sure that “nfs.v4.id.domain” was set to the domain name.  It defaults to nothing “”.
  2. Again, on the Netapp, since we are not using a centralized location for accounts (we have < 12 accounts across all of the systems), I had to populate /etc/passwd with all of the accounts on the rest of the systems and /etc/group with all of the groups defined on the rest of the systems.

That brought the behavior back to what was expected.

Fedora Core 5 to Fedora Core 6 Upgrade via YUM on x86_64 (64bit)

Having had past success with yum upgrades for Fedora under the i386 install, I thought I would give it a whirl with my x86_64 installations. The YumUpgradeFaq points out that the yum upgrade process is very straight forward, and this was, indeed, what I followed before.

I ran in to the problem where the elfutils package came up as a conflict, as outlined in the comments here, here (post #5), and here. The last link had a “hackish” way of making it work, but, after some fighting and a little bit of panic, I can say that it doesn’t really work and it just isn’t worth the hassle.

It seems that the only sure-fire way to perform an upgrade would be to use the DVD or CD set to upgrade. Yum still hasn’t caught up to the x86_64 world just yet.

Be aware, though, that an upgrade will take a very long time.  Seriously consider the idea of backing up your important configuration files and just performing a clean install.

MythTV Woes: mythtv-users mailing list

One of the main beauties of MythTV is the fact that you are getting a wonderful implementation and an ever expanding user base who are all willing to ‘give back’ in some way.

At least, that is what it first appears to be like.

MythTV’s installation can be daunting, but the end result is very impressive. The provided support via the mythtv-users mailing list is enough to put some companies support structure to shame. Technical questions get quickly answered and, when they cannot be answered, a poster was quickly pointed in the right direction. Of course, there are always a couple of nasty responders, but that comes with the territory.

Or so one might think. After being on the list for 6 months, one realizes that there are two classifications of people on the mythtv users list: knowledgable (let’s call them “old-timers” since they have been on the list for a long time) and newbie (people who inistalled recently and are trying to get off the ground, or ones that have recent successful implementation and are trying to help the product grow). The dynamics of the two groups cause a fair amount of friction and noise in an otherwise prosperous mailing list.

As with any complex installation, you see a lot of the same questions show up on the mailing list. This is just natural. While efforts at a FAQ have been on-going, human nature is to simply ask the question rather than hunt for the right question/answer. Rather frequently, you see the more vocal of the ‘old-timers’ slap around an inexperienced poster for not checking the FAQ or misphrasing items. This is generally tolerated on a mailing list when you are trying to keep things moving and teach at the same time. Unfortunately, that also teaches the other posters that it is ok to be nasty in a response.

Over the course of the 6 months snippet in time, it was quite surprising to see a fair number of the responses to postings (not the majority, but a growing minority) were general ‘turn off’ messages that degraded in to flames, apologies, and more flames for posting apologies. It is silly and sad at the same time.

The mysterious class-like structure of the ‘old-timers’ is such that they expect that everyone else should know as much about MythTV and its history as they do. The impression is that if a poster has not read every past posting and article, then that poster has not properly researched their problem. You actually see a lot of references to the main author/project lead and “the mythtv-devs” in regards to history and rules of mythtv that ‘everyone should have known about’, in an effort to create some form of authority in the posting without actually mentioning the contents of the reference. In other words, the use of the main author’s name is done to create a sense of authority, and it seems unlikely that the main author nor the mythtv-devs even know about this. Additionally, several of the developers who frequent the mythtv-users list will lash out at a poster, clearly throwing weight around, all while the majority of the newbie (see definition above) portion of the community have no idea who that person is until they identify themselves as “one of the devs”.

In summary, as someone who wishes to help out others with their MythTV installs and share some of our experience so as to make their road a little easier to travel on, try to keep a level head and don’t get bitter.  Spread that wealth of knowledge you have gained.