mcdudeabides wrote:
> Hello Steen. I've been able to exercise 1.14d for a bit. All of the
> wifi cards I have work out of the box with this release. Certainly a
> good step forward. I have two things to share for your consideration.
>
> 1) Using the picoreplayer.sh script approach to setup: If your intent
> is to abandon the script setup option, then my suggestion may have no
> merit. However for those occasions where one cannot launch the web
> interface, the old standby of the ssh to perform script setup is a
> lifesaver. To that extent, if one uses only the script to setup options
> (like wifi), then the parameters set in wifi.db do not survive a reboot.
> The bootlocal.sh will exec
> "mnt/mmcblk0p2/tce/OliWeb-master/ivySox/myweb/do_rebootstuff.sh" and
> this will reset wifi.db with the initial values contained in
> /usr/local/sbin/config.cfg
> (/mnt/mmcblk0p2/tce/Oliweb-master/ivySox/myweb/config.cfg). Somehow the
> values captured with the setup script must be reflected in the
> config.cfg to have both work properly. If this is something you agree,
> I would be willing to take a first pass at amending the script logic for
> option 10 to save values to the config.cfg file.
Thanks, you are absolutely right.
The SSH piCoreplayer script has been neglected for some time, as I have
been focused on the web-GUI stuff. Therefore, I have not added the
functionality of saving changes made by the SSH script to the config.cfg
file - so as you describe changes will not survive a reboot. I will be
happy if you have the time to look into this and I would be happy to
incorporate these changes into the new piCorePlayer. At some time I was
thinking that we didn't need the piCorePlayer script anymore, but
actually I think we need both a web-GUI and a SSH script?
mcdudeabides wrote:
> 2) Server assignment of squeezelite player name: Given the portable
> nature of these devices, I have seen many occasions where my friends
> will relocate them. The initial names given the players are no longer
> relevant and I get the call for help in changing the name (at least I
> can get a beer out of it:-)). Most of the web controllers and remote
> control applications (iPeng in particular) can allow the name of the
> player to be set from the controller. The following changes to a few
> items would allow this to happen and still preserve the ability to enter
> a hardwired name in the web interface.
> -in /usr/local/etc/init.d/squeezelite_initd change line 13.
> >
Code:
--------------------
> > if [[ X"" = X"$NAME" ]]; then NAME="-N
/mnt/mmcblk0p2/tce/playername.cfg"; else NAME="-n $NAME"; fi
>
--------------------
> >
> If the NAME field on the web form is set to null (cleared), then the
> logic will allow the -N option to express.
>
> -to enable this logic on first boot, the config.cfg file you ship with
> the image should have the NAME variable set to "".
>
> -the playername.cfg is stored on /mnt/mmcblk0p2/tce so that any writes
> by squeezelite (via server call) will be preserved over reboots. If
> you place "piCorePlayer" as the default text in this file for the
> image you ship, then if no action is taken the player will
> automatically show up as "piCorePlayer".
I'm not sure I quite understand what you are suggesting here.
What is the problem with the current way it works?
However if a change is needed I would prefer to keep all variables in
one config file.
So if you need to use an alternative name variable if NAME is set to
null, could we not use a new static variable in config.cfg like:
GENERIC_NAME=piCorePlayer and then make the logic something like:
Code:
--------------------
if [[ X"" = X"$NAME" ]]; then NAME="-n $GENERIC_NAME"; else NAME="-n
$NAME"; fi
--------------------
mcdudeabides wrote:
> Hopefully I haven't been too intrusive with these suggestions. You have
> my email should you want to get any further specifics covered.
>
> Thanks again for the great project.
Not at all.
I like to learn and if no one is commenting on the piCorePlayer I think
I would lose interest So please continue asking questions and suggest
improvements.
/Steen
piCorePlayer a small player for the Raspberry Pi (25MB in RAM).
Homepage: https://sites.google.com/site/picoreplayer/home and
discussion:
http://forums.slimdevices.com/showthread.php?97803-piCoPlayer-Squeezelite-on-Microcore-linux-An-embedded-OS-in-RAM-with-Squeezelite
Squeezeboxserver on Voyage Linux 500 MB CF-card (read-only)
http://forums.slimdevices.com/showthread.php?90581-HOW-TO-install-squeezeboxserver-on-very-small-Linux-(Voyage-linux)
Please 'donate'
(https://www.paypal.com/uk/cgi-bin/webscr?cmd=_flow&SESSION=_Wc9nDqkHvtg-sUXCIrz1nB1Ct8pwHDrBSxETDiHfpX5H6F4Wflav3VBIAK&dispatch=5885d80a13c0db1f8e263663d3faee8d7ff5e1e81f2ed97dd1e90bd72966c40c)
if you like the piCorePlayer
------------------------------------------------------------------------
sbp's Profile: http://forums.slimdevices.com/member.php?userid=37237
View this thread: http://forums.slimdevices.com/showthread.php?t=97803
_______________________________________________
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
