That's good info, thanks. I'm running 0710 now, but am building a test server now to try 0810 on.

Would you happen to know if there an upgrade path anticipated from the current 0810 Beta to the final release? If so, I may just take the plunge and start using 0810 full time. My whole family runs on LMCE and, for everybody's sanity, I want to minimize the number of clean reinstalls we go through.

In general, I find it more convenient to playback videos recorded using MythTV from the standard LMCE Video catalog. However, as the MythTV files do not have cover art, only the title of the program appears on the main catalog screen and, as many episodes of the same show may be listed, this can become confusing as there is no way to identify which episode is which. I use UI1 and was wondering how one would go about showing the episode title or file creation date along with the program title on the main Video catalog page. Displaying this additional information would be a great benefit.

I have an old Sony camcorder with a firewire interface that I would like to use as a security camera. Provided it's possible to stream DV across the camera's firewire port, should LMCE be able to accept and display this video stream?

The solution that I've settled on for now is simply to install Windows on one of my MDs and, when I want to watch a Netflix on-demand movie, just restart the box and preempt the netboot to load XP from the local hard drive instead.

I have a partial solution, which may ultimately work or prove to be a dead end. I need some advice:

I have an XP box which I can view Netflix on-demand movies on. With a gigabit connection to my core, I can use VNC to remote into it and also watch Netflix on-demand movies. Trouble is, the video is choppy and there's no audio.

As, of course, my MDs play movies all the time streamed across my LAN, I'm not sure why the Netflix video is choppy. I'm hoping there's a VNC setting to improve throughput. Not sure about the audio yet.

I'd like to minimize network traffic in my home and have a general question about how media are served-up to MDs. Does all media get routed through the Core when played back? I'm wondering because all of my MDs have large internal hard drives which are used by LMCE for storage. If files that reside on an MD's own hard drive(s) stay off the network when played back by that MD, that would be very cool and would prompt me to locate media primarily used by a particular MD on that MD, rather than on the Core.

That was the problem. The MD was running an AMD64 image; once it was changed back to i386, xfsprogs installed without issues and I was able to run mkfs.xfs /dev/sda1 to format the partition. LMCE has now recognized and is managing the drive. Thanks for the help!

However, upon running "sudo apt-get install xfsprogs" I was greeted with a boatload (pages, literally) of unmet dependencies and offered the option of running "apt-get -f install" to correct. I then ran "sudo apt-get -f install xfsprogs" just to see what would happen and I again was presented with pages of packages that were going to be updated upon pressing Enter.

I didn't. I know it's "just" a diskless MD, but the wholesale upgrade of just about every package on the MD to install a package that loaded without incident on the core seems suspicious.

However, now that I think of it, there *is* a difference between the LMCE systems on the core and the MD. While I don't know much about this stuff, the core is a P4 running a standard 386 package set and the MD is an Intel Dual Core which I believe is running an AMD (kernel?) which came up as part of the MD's diskless autoconfiguration. Perhaps this explains the different behavior vis-a-vis the xfsprogs package on the core and the MD?

I'm making progress. I checked dmesg and found out the drive is identified as sda. I ran fdisk /dev/sda and now have a partition sda1.

However, attempting to run either "apt-get install xfsprogs" or "sudo apt-get install xfsprogs" at the MD produced the error "E: Couldn't find package xfsprogs".

I ran "sudo apt-get install xfsprogs" at the core and it installed fine and mkfs.xfs is now in the core's /sbin, but this is not visible on the MD.

I checked the apt sources.list on the MD and it appears identical to the core's, so I'm guessing there's something blocking installs on MDs. I tried rebuilding the MD image, thinking this would replicate the current core package set on the MD, but it didn't.

mke2fs -b 4096 -m 1 -j /dev/whateverwhere "whatever" is the hard disk in question (hda1, sda1, etc.) and this is what I could use some help with in creating. The 1TB SATA disk on this Media Director is recognized in the Media Directors Systems Settings: Disk & Filesystems. I'm not sure whether this disk device should be (hd, sd, hd1, sd1, hda1, sda1, etc.) or how to actually create the device.

Well, the problem is now resolved, though I'm still not sure of the problem in the first place; though I'm guessing some of the UI1 screens didn't get built properly during the media director's initial setup.

The problem was fixed by running AVWizard and switching to UI2. After a session of running UI2, I ran AVWizard again and switched back to UI1. This time everything is working fine.