I think I've gone about as far as I can with this project now. For my needs it's fully functional. There are some features of the original Squeezeplay image that aren't working on my build, but I'm getting nowhere fast trying to implement them - I don't think my software skills are up to the challenge.
1) Audio feedback: I found what I thought was the correct place to issue an 'aplay' command, but it had no effect. I have a feeling that some other part of the build tells Jivelite that it doesn't have playback capabilities. @Ralphy - when you said that this feature was disabled in Jivelite, was that achieved by removing all the necessary code, or is it a simple flag somewhere that I could revert? 2) Screen Off: The best I've been able to achieve is 'zero brightness'. I found that 'setterm --blank force' will blank the screen from the command line, but when I call this from within Jivelite it doesn't seem to work. Maybe SDL has control of the screen? I wonder if there's an SDL command that can achieve this instead. 3) Boot messages/splash screen: Grub is already configured to suppress most boot messages, so those that remain seem to be errors/warnings etc. I looked into using Plymouth to show a splash screen instead, but couldn't get it to work. 4) There's a feature in the Joggler Squeezeplay image that I'd like to get working - there's a home menu item that says 'Turn Off <player>'. It toggles to 'Turn On <player>' when it's already off, and <player> is replaced with the selected player's name. I can already achieve this with the soft power button in the top left, but there's no feedback of any sort, so I like that home menu option. I've looked through the Squeezeplay code but can't find any trace of that option, so I may just implement a little applet. I'm not quite sure how to implement a change to the menu item's text though, i.e. so that it toggles between On and Off. I've been running my 'alpha03' image on several Jogglers over the weekend - two from internal memory and one from a tiny external USB stick - and they've all been working fine, so my original objective has been met Regarding being able to kill the power without corrupting the OS, Andy replied with the following: > In a roundabout way. It doesn't set the root to read-only, but it does > shove as much temporary file generation as possible into RAM; anything > volatile is redirected to RAM through tmpfs... > ... I am pretty sure that you could set the root to read-only at this > point and still have the thing boot and work perfectly well. The > 'zombie' 3.18 kernel has overlayfs support compiled-in too, so you could > look to using that. So my interpretation is that it's not totally safe to kill the power, but most 'disk' activity is happening in RAM, to reduce wear on the internal flash storage. If I was to make root completely read-only I think I'd miss the ability to make changes to the various applet settings files while Jivelite is running. I'm not sure what 'overlayfs' is/does - I might investigate, but that seems like it might need in-depth Linux knowledge that I don't have. ------------------------------------------------------------------------ chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110040 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
