Logitech Media Server (LMS) on TC.7

[Greg Erskine]

I noticed that Michael just made a small dedicated ARM version (about 30MB in size) can it simply be untarred on top?

http://forums.slimdevices.com/showthread.php?105085-New-Debian-packages-for-7-9-ARM-x86_64

Oh, and the ARM build should now be compatible with Debian Jessie on
 first generation Raspberry Pi.

I think this means newer CPAN modules with later perl versions.

regards
Greg

[Paul_123]

How do you think we should handle the update process? Most likely people would like to update the LMS more often than you would like to update the tcz package.
I noticed that Michael just made a small dedicated ARM version (about 30MB in size) can it simply be untarred on top?

Who is most people lol.   My server at home is still running LMS7.8 and perl 5.14.4.     But I see he just pushed another change on git..........   Damn,  he could have saved us a ton of work if he had pushed that patch on Friday.   lol

So right now, the "guts of the files in slimserver are in an extension.   So updates for the average user is not going to be easy to do.  Plus, I don't think the average user could decipher an update that has a potential of being armv7 only.   (The binaries for arm on the slimserver repo are armv7 only)   

I have no problem being the extension maintainer on piCore.    So what I plan to do.
1) I have the full git tree downloaded on my server,  I made local changes to remove everything we didn't need and the right armv6 binaries, and then committed the changes on my local system
2) When there is a large enough update, I can merge the updated files into my local repo.  Repack the tcz, and send to bmarkus for uploading to the repo.

How do you release updates for piCoreplayer?     

[jgrulich]

How do you think we should handle the update process?

If you like new update, simply use this simple manual setup:

1) Backup the folder

Code: (bash) [Select]

/usr/local/slimserver/CPAN/arch/5.20

2) Download

Code: (bash) [Select]

http://downloads.slimdevices.com/nightly/7.9/sc/e96ce46/logitechmediaserver-7.9.0-1453713980-noCPAN.tgz

for sure the actual night build.

3) Replace all the files in the slimserver directory and, if it's overwritten, copy back the CPAN/arch/5.20.

4) Than change the first line in scaner.pl and slimserver.pl like this:

Code: (bash) [Select]

#!/usr/local/perl5/bin/perl

That's all. You may build some simple script to do so if you like and share with us.

[jgrulich]

Be aware that if you use the RPi2, the regular last version of LMS from nightly may be used.
If you run it no the B, or B+ board (armv6), than you need to use the older CPAN modules from the link, I've sent some days ago and which is used in the slimserver.tcz provided by Paul.

[jgrulich]

The Raspberry perl incompatibility was solved and doesn't need the CPAN patch in CPAN/arch/5.20.
The nightly, or git version is working on B and B+ board now directly.

[Paul_123]

Thanks for testing.

/usr/local/slimserver is symlinks to the squashfs of the extension.  If you overwrite it, then all of the files will be in RAM, and not persistent any longer. 

Bela recommended the way it is currently setup, as it more fits the Core way of doing things.    I'm not sure what is practical to update the extension.   I know that steen has custom upgrade scripts that points to their own repository to download updated for picoreplayer.  Perhaps we can go that route......but I think keeping an extension is the best way to go.

[sbp]

Thanks for testing.

Working very good - no problems.
 

I'm not sure what is practical to update the extension.   I know that steen has custom upgrade scripts that points to their own repository to download updated for picoreplayer.  Perhaps we can go that route......but I think keeping an extension is the best way to go.

I also think that the optimal way would be to have LMS as a tcz package. It will make it easy to install and maintain.

The only problem/issue is the update which the will be on your shoulders then. As you know Michael is regularly updating the LMS (nightly) debian packages, and I think there will be a pressure from users to also update their LMS.tcz package. I don't know if it is possible to automate the process so that a script could pull the Nightly-LMS-ARM.deb from the Logitech server to convert it to LMS.tcz and upload it to piCore repro every night or once a week or ??

Thanks for your work on getting LMS in piCore. It is really working good.

[Paul_123]

The only problem/issue is the update which the will be on your shoulders then. As you know Michael is regularly updating the LMS (nightly) debian packages, and I think there will be a pressure from users to also update their LMS.tcz package. I don't know if it is possible to automate the process so that a script could pull the Nightly-LMS-ARM.deb from the Logitech server to convert it to LMS.tcz and upload it to piCore repro every night or once a week or ??

I think this might work.......  Create slimserver-nocpan.tcz, slimserver-armv6cpan.tcz, slimserver-scripts.tcz   Then build a script to pull the nightly .deb file with no CPAN, and rebuild only the slimserver-nocpan.tcz

Major updates would need to come from the tc-repo.

The only piece that worries me is folks having a big enough partition to do the rebuilding (plus the need for more packages like squashfs-tools.tcz     

[jgrulich]

Sorry to wrong explanation. For sure that I'm not using symlink access to the /usr/local/ ..., but copy of the /tmp/tcloop/slimserver to something like /home/tc/build/slimserver/usr/local ... and make the tcz at the end.
The question is how to get the update files without other garbage. The git source is 180MB, which is not practical. The nightly nocpan seems to be more usefull, but file name is generated dynamically and just don't know how to wget it.

[Paul_123]

I'll look into it.

[jgrulich]

Paul,
hit the "trivial" issue with the IP address. Until now I used dhcp for eth0, but it's not comfortable to search the server on the network. I've used the ip=192.168.1.100 in the cmdline.txt, but it doesn't work. It set the IP, but not the gateway. Than I tried ifconfig ... but nothing.
Was looking for something like /etc/networking/interfaces but nothing like that. I know that I need to disable the dhcp at boot first and that set the config somehow, but where?
Please help.

[sbp]

The only piece that worries me is folks having a big enough partition to do the rebuilding (plus the need for more packages like squashfs-tools.tcz     

I was more thinking like having this process automated at one computer and uploading the nightly_LMS.tcz to piCore repro. So that this process is done by a single computer (person) and not on the users individual RPi's.
I don't know if Bela would allow the daily upload of the nightly builds.
Then we would have a structure like the LMS, with stable releases and nightly builds.

[Paul_123]

Paul,
hit the "trivial" issue with the IP address. Until now I used dhcp for eth0, but it's not comfortable to search the server on the network. I've used the ip=192.168.1.100 in the cmdline.txt, but it doesn't work. It set the IP, but not the gateway. Than I tried ifconfig ... but nothing.
Was looking for something like /etc/networking/interfaces but nothing like that. I know that I need to disable the dhcp at boot first and that set the config somehow, but where?
Please help.

Put "NODHCP" in command line

Then in bootlocal.sh put

Code: [Select]

ifconfig eth0 down
ifconfig eth0 add 192.168.1.100
ifconfig eth0 up


[jgrulich]

Strange, the NODHCP is not running and doesn't display something like "disabling DHCP as requested..." and dhcp get the address as before.

[Greg Erskine]

Paul,
hit the "trivial" issue with the IP address. Until now I used dhcp for eth0, but it's not comfortable to search the server on the network. I've used the ip=192.168.1.100 in the cmdline.txt, but it doesn't work. It set the IP, but not the gateway. Than I tried ifconfig ... but nothing.
Was looking for something like /etc/networking/interfaces but nothing like that. I know that I need to disable the dhcp at boot first and that set the config somehow, but where?
Please help.

Put "NODHCP" in command line

Then in bootlocal.sh put

Code: [Select]

ifconfig eth0 down
ifconfig eth0 add 192.168.1.100
ifconfig eth0 up


Another method, which I prefer, is to assign a IP address to a MAC address on your DHCP server (router).