Messages

One of the problems with "hard" mounts is they can lead to hung processes if the device stops responding (manually mount an nfs share then disconnect that box from the net, then try to access the share).  Automounter is the more robust solution.

For more info, http://en.wikipedia.org/wiki/Automounter

HTH,
Roy

Well, the choppy playback finally got on my nerves a couple of months ago, so I solved the issue by switching to svn XBMC running on gentoo ~x86.  Just created mirrored media directories with hard links from .dvd to .iso files, then mounted each of my NFS volumes on the new box and added them as sources.

I still have my LMCE box in place but am just using it for a firewall/DHCP server until I take the time to migrate those functions.

Have fun,
Roy

Re-reading the thread, I'm a little confused about when you talk about the automounter unmounting the share.  If you are noticing that /mnt/device/124 is disappearing this is normal behaviour.  The data in the share should still be accessible under /home/public/data/videos/NFS Share [124].  Basically the automounter tries to keep shares unmounted except when they are being accessed.  If the data is not there, then we need to troubleshoot.

One NFS gotcha that I've recently ran across when trying to use a macbook as a nfs client to my gentoo server (which also serves media to my linuxmce system) has to do with secure ports.  My solution was to add an "insecure" option to share in the /etc/exports on the server.  I know this is opposite what you are trying but bring it up that some systems restrict the allowable ports differently.  It's been years since I used solaris and just don't know how it handles ports.

And to answer your question, yes, nfs shares must be manually configured.  Follow the "Manual Creation of Network Shares" section on the "Howto: Using Network Shares" wiki page.

HTH,
Roy

When used for flickr.pl replacement on LinuxMCE, you have to specify the plugin in your config:

  :plugins => [:LinuxMCE_Plugin]

This tells flickrfetchr to hook into the LinuxMCE database.

In your example, I would use this config:

Code Select Expand


LINUXMCE_1024_X_768_CRITERIA = {
                    :limit => 100,
                    :daycount => 5,
                    :destination_path => '/home/flickr',
                    :destination_naming => :short,
                    :plugins => [:LinuxMCE_Plugin],
                    :image_acceptable_types => ['jpg'],
                    :image_resize_to => {:width => 1024, :height => 768}
                  }

MUFFIN_CRITERIA = LINUXMCE_1024_X_768_CRITERIA.merge({
                    :username => 'hlt1611',
                    :destination_path => '/home/flickr/muffin'
                  })

config[:USERS] += [MUFFIN_CRITERIA]



Witzman, I have a long answer just about ready, but flickr.com isn't responding for me to verify it at the moment.

HTH,
Roy

You tickled a bug, thank you. 

For now, you can work around it by specifying a :destination_path.  For example:

Code Select Expand


config[:USERS] += [{:username => 'hlt1611', :destination_path => '.'}]


I'll patch the bug tomorrow when I'm more alert (it's bed time).

Thank you,
Roy

LinuxMCE expects the photos to be stored under /home/flickr.  Note, it is ok to have sub-directories there.

This is configured in the flickrfetchr.conf file.

Here's part of my /etc/flickrfetchr.conf file.  You might want to cut and paste to give you a starting point:

# this pretty much matches the criteria that the default flickr.pl uses
LINUXMCE_1024_X_768_CRITERIA = {
                    :limit => 100,
                    :daycount => 5,
                    :destination_path => '/home/flickr',
                    :destination_naming => :short,
                    :plugins => [:LinuxMCE_Plugin],
                    :image_acceptable_types => ['jpg'],
                    :image_width_range => 600..1920,
                    :image_height_range => 600..1080,
                    :image_resize_to => {:width => 1024, :height => 768}
                  }

# some flickr group IDs
TOP20AVIATION_ID = '60512572@N00'
TOP20FISHEYE_ID = '46819026@N00'
TOP20LONGEXPOSURE_ID = '54941127@N00'

# lets put the top20 groups into a top20 LinuxMCE subdirectory
TOP20_CRITERIA = LINUXMCE_1024_X_768_CRITERIA.merge({
                    :destination_path => '/home/flickr/top20',
                    :limit => 20
                  })

# now let's create the group criteria for the top20 groups
TOP20AVIATION_GROUP_CRITERIA = TOP20_CRITERIA.merge({
                    :nsid => TOP20AVIATION_ID,
                  })

TOP20FISHEYE_GROUP_CRITERIA = TOP20_CRITERIA.merge({
                    :nsid => TOP20FISHEYE_ID,
                  })

TOP20LONGEXPOSURE_GROUP_CRITERIA = TOP20_CRITERIA.merge({
                    :nsid => TOP20LONGEXPOSURE_ID,
                  })

# finally lets specify which groups we want.
config[:GROUPS] = [
        TOP20AVIATION_GROUP_CRITERIA,
        TOP20FISHEYE_GROUP_CRITERIA,
        TOP20LONGEXPOSURE_GROUP_CRITERIA
]

Note, you can "force" an update to test the config file by simply running flickrfetchr.rb as root:

Code Select Expand


sudo flickrfetchr.rb --verbose


You should see something like:

Code Select Expand


linuxmce@dcerouter:/home/flickr$ sudo flickrfetchr.rb --verbose
[sudo] password for linuxmce:
INFO flickrfetchr: Loading /etc/flickrfetchr.conf
INFO flickrfetchr: Loading /home/linuxmce/.flickrfetchr.conf
INFO flickrfetchr: Loading LinuxMCE_Plugin (require "flickrfetchr-linuxmce.rb")
INFO flickrfetchr: Downloading photos from GROUPS ({:destination_naming=>:short, :image_width_range=>600..1920, :image_acceptable_types=>["jpg"], :limit=>20, :destination_path=>"/home/flickr/aircraft", :nsid=>"79204191@N00", :image_height_range=>600..1080, :image_resize_to=>{:width=>1920, :height=>1080}, :plugins=>[:LinuxMCE_Plugin], :image_fill_to=>{:width=>1920, :height=>1080}, :daycount=>5})
INFO flickrfetchr: downloading http://farm4.static.flickr.com/3220/3144058266_2e6c2f4cc8_o.jpg to /home/flickr/aircraft/3144058266.jpg
INFO flickrfetchr: downloading http://farm4.static.flickr.com/3127/3145331668_6c0860f186_o.jpg to /home/flickr/aircraft/3145331668.jpg
INFO flickrfetchr: Skipping 2642314900 => [/home/flickr/top20/2642314900.jpg.tnj]
...
INFO flickrfetchr: Cleanup LinuxMCE flickr images
INFO flickrfetchr: Limiting to 200 flickr images
INFO flickrfetchr: Cleanup completed


HTH,
Roy

you should be good to go.  Just run

Code Select Expand


flickrfetchr.rb


It's during the first time that the script is ran that you are prompted to authenticate with flickr.  BTW that is what creates the .cache files that are then used for future authentication.

After running it the first time, locate the .flickrfetchr.conf files, there should be three:

Code Select Expand


/root/.flickrfetchr.conf
/home/linuxmce/.flickrfetchr.conf
/etc/flickrfetchr.conf


Here's the logic for the multiple conf files. 

The /home/linuxmce/.flickrfetchr.conf is the one used when you run the script as the linuxmce user.  I use it to pull my photos from flickr to the linuxmce system (actually on my NAS so whole house has access).

The /root/.flickrfetchr.conf is the one used by the root user, for example if you want to set it up as a cron job.

The /etc/flickrfetchr.conf is the one used when you integrate flickrfetchr into the linuxmce (i.e., replace flickr.pl).

It's actually a little more complex than that.  The actual flow is to load the /etc/flickrfetchr.conf then merge ~/.flickrfetchr.conf.

There was a practical rational for this loading weirdness when I wrote it, but don't recall exactly what it was.  Maybe it should be simplified.

HTH,
Roy

OK, here are the steps to manually upgrade rubygems to 1.3.1:

Code Select Expand


sudo apt-get install rubygems
wget http://rubyforge.org/frs/download.php/45905/rubygems-1.3.1.tgz
tar xvzf rubygems-1.3.1.tgz
cd rubygems-1.3.1
sudo ruby setup.rb
sudo rm /usr/bin/gem
sudo ln /usr/bin/gem1.8 /usr/bin/gem


The first command is there just to pull in the dependencies.  If you already have gem installed you may skip it.

Now verify:

Code Select Expand


linuxmce@dcerouter:~$ gem --version
1.3.1


Now try to install flickrfetchr using the setup-linuxmce script.  I uninstalled the gems then ran the setup on my linuxmce box and it installed fine.

Please give me a confirmation that this solved your installation problem, then I'll patch the setup scripts.

Just a FYI, apparently debian team does not like gems as the dependencies are internal to the source (as they should be in a scripting language) and not externally controlled (as brain dead apt expects).  That's probably why kubuntu's version of rubygems is so dated.  I installed rubygems on my kubuntu (0804 upgraded to 0810) system and apt installed rubygems-0.9.4 (the release from 05/2007).

The ruby community strongly recommends the 1.3 version.

I don't have a clean installed 0810 at the moment.  If you want to see what version kubuntu 0810 has:

Code Select Expand


sudo apt-get install rubygems
gem --version


HTH,
Roy

It's been awhile, but IIRC only a few groups are available unauthenticated.  I'll see what can be done.

Currently fighting the stupid kubuntu package manager (I really, really prefer gentoo's portage).  gem is up to v1.3.1, but apparently all kubuntu knows about is v1.1.1.  Or at least I haven't found the obscure magical combination for it to find the latest and greatest.

BTW, flickrfetchr is now available on github if you want to fork it.

http://github.com/royw/flickrfetchr

inuxmce@dcerouter:~/flickrfetchr$ ./setup-linuxmce
/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- commandline/optionparser (LoadError)
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
        from ./setup-linuxmce:31

This error message is saying that the "commandline" gem is not installed.  Try this:

Code Select Expand


sudo gem install commandline


HTH,
Roy

Sorry.  I working on a non-LinuxMCE project at the moment.  It'll be a couple of weeks before I get back to this.

• Battery Life - Not realy a feature but, want to know if it makes sense to use this a primary remote in each room i have an MD

N800 OS2007 about 12 hours battery life.  We usually leave it plugged in when not in use so it's always ready.

Only have two wishes on using it as an orbiter:

• The double screen saver takes about 10s to wake up before you can press the pause.  It would be really neat to map pause/play to the nokia's physical keys.
• The On-Screen UI2 during DVD playback has a "Zoom & Aspect" feature that I haven't found on the Nokia's UI1.  Movies that I played using my old video setup (NTSC) usually have to be zoomed out to 135% when first played on my new 1080p TV.

HTH,
Roy

Please clarify, is it the screen saver that is locking up or the retrieval of photos from flickr?