What are other users seeing for total space required per MD for their core?

I am looking over things from a few previous installations while I gather hardware for a reinstall and have found some areas I want to look into further.  Specifically I am looking at logrotate and some run-away folder sizes.  The issues causing these coredumps and crash logs of course will need to be located and addressed individually.

Healthy Core (OS partition)
Total disk space used?
Total number of MD?

With enough input I will add a portion to the wiki pertaining to hardware selection covering suggested drive size based on max number of potential future device, or room count + outdoor areas if that reads easier.  Thanks.

Tireless developers and administrators:

I am using Facebook business pages to promote my home-business.  The large majority of electronics in my home are operated by and use LinuxMCE menus, displays, logos, etc.  I am requesting proper procedures for displaying images and videos of these devices, while giving all credit to LinuxMCE for its operation.

I do computer repair, non-glamorous "fix this PII so I can get on facebook", hardware upgrades and similar the majority of the time.  On occasion I do,  and my company goal is, to move into more and more customization, product development, installations and yes... home automation.  I will type it here nice and clear so it is communicated and can be quoted:

I will not offer for sale LinuxMCE or any software that is not entirely my creation.  I will not sell equipment that I am not able to make operational for my customers without the use of LinuxMCE, as this would burden LinuxMCE's developers with supporting customers I profited from."

There may be a situation where a customer is inspired after visiting my home office or seeing images/videos of LinuxMCE operating and despite my declaration of the quoted above, wishes to install LinuxMCE.  Should this occur I will refer to any instruction I am given here or contact an admin directly.  So far no customers of mine (that I am aware of) are using LinuxMCE.  The few used pieces of compatible equipment I have sold were configured to operate stand-alone or with that customers existing OS/control devices.

I realize that the mention of profit makes for immediate uneasiness.  I apologize though as I prefer a direct post and request such as this to any doubt about my intentions.  Links to GPL documentation, feedback from developers and responses from administrators is 100% welcome.

"Cheap" is my favorite word!  Well maybe second favorite...

There are always exceptions, clearance, thrift shop finds etc, but for the most part you truly do get what you pay for.  Forgive me if I leave any out as there is a ton of work making this operational.  The wiki sums this up better, but your options for orbiter 'types' is:

web-orbiter 2.0 :  laptop, pretty much everything with a browser.  I have used this on a Nintendo DSI XL.  No streaming cams to this, unless you tab switch away from the orbiter and open the cam url directly.

embedded orbiter (such as webdt-366, cisco 7970 and similar):  I believe this is what you are referring to when you say Linux OS running.  Supports streaming cams on devices I have tested. 

JavaMo:  have not tested

iOS apps :  (Dianemo S, Roaming Orb) :  Andrew will have to correct me here if I am mistaken but I believe cams are not supported for linuxmce on dianemo S due to their integration of kmotion??

qOrbiter:  This is exciting!  I do not currently have a capable device to test but the work being done is game changing.  Again you are going to get what you pay for in performance.  A tablet that was mentioned to me as pretty standard hardware capable of taking advantage of qOrbiter would be the Nexus 7.  Something very important to consider here btw is that investments here are not "home-bound,"  a tablet away from home functions like a tablet, when home it also becomes an orbiter.

One more point of clarity, I am used to having to make this distinction when introducing the system to family members.  Security Cameras being the exception, an orbiter does not play media.  Orbiters control Media Directors which play media.  If you can remember Media Directors as moon## devices the orbiter reference becomes easier to swallow as orbiters can control (orbit) a moon.  To cement this open an on-screen orbiter and change its room.  This one is the hardest for people to grasp i feel because a TV screen/monitor is viewed as a single image.  What you are seeing though is:

you       on-screen orbiter (living room)     media director (living room) display

change the onscreen orbiter in the living room though to  bedroom and you get:

you       on-screen orbiter (bedroom)         media director (living room) display

Play a movie using the onscreen orbiter now and the bedroom tv wakes up and starts playing.

I had an odd similar issue with one Z-wave module that supported load detection.  My guess would be that like the Z-wave module, the security light needs constant power to keep its detection circuitry alive.  This draw could be telling the module that local power (via Amp draw) is requested.

I am fairly familiar with some of your other projects so will recommend getting a meter and experimenting/testing to see how much draw the light needs.  Perhaps there is a way in the zwave-api to turn off certain features like local load switching? 

To get around it another way you could use the zwave module to turn off a relay placed between the devices.  Wired normally open this would allow you to kill attached devices regardless of any 'leaked-power' they try and pull.  Good Luck.

Result:

lmce-usb-gamep 2.0.0.45.13020

For the sake of completeness I checked version on my hybrid and three media directors where I have gameplayer running.  I also performed:

apt-get update
apt-get install lmce-usb-gamepad

This returned that I had the most current version.

My work around as I said basically kills all orbiter remote functionality by disabling and removing its keymapping.  Here are some environmental variables that may be helpful.

Install method for gameplayer:  Select gameplayer from web-admin>media directors>edit modules?>checkbox>save>close>reload router.  Gameplayer-plugin is unassigned to a room so I put it in the room with the hybrid since it is category 'controlled by dcerouter'

Install method for usb-gamepad:  Plug it in, gamepad detection picks it up within a few seconds, use as an orbiter remote is automagic, open gameplayer and individually map buttons for each system the way I like them (ie, 1 button consoles using the bottom button, 2 buttons using top and right, genesis using left, top, right, etc)

Connections:  Gamepads are disconnected when not in use,  typically connected after a game is initiated via orbiter.

Equipment variables: 
LivingRoom MD - MSI P45-Neo3 w/ usb-uirt 0056, gyration 'fiire clone' dongle, cm15a & occasionally a generic USB keyboard making up lsusb. 
Den MD - Revo R1600 (mem upgraded, hdd ignored) w/ occasional USB mouse or USB keyboard on lsusb.
Desk MD (hybrid/core) - Asus M4A785TD-M EVO w/ USB keyboard, USB mouse full time

lsusb -v from Revo when connected: Sidewinder & GameFoundry (unused hub info removed)

root@moon64:~# lsusb -v

Bus 002 Device 005: ID 045e:0027 Microsoft Corp. SideWinder PnP GamePad
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x045e Microsoft Corp.
  idProduct          0x0027 SideWinder PnP GamePad
  bcdDevice            1.05
  iManufacturer           1 Microsoft�
  iProduct                2 Microsoft� SideWinder� Plug & Play Game Pad
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           34
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.00
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      57
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0003  1x 3 bytes
        bInterval              10
Device Status:     0x0000
  (Bus Powered)

Bus 002 Device 004: ID 0e8f:0003 GreenAsia Inc.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x0e8f GreenAsia Inc.
  idProduct          0x0003
  bcdDevice            1.07
  iManufacturer           1 GreenAsia Inc.   
  iProduct                2 USB Joystick     
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           34
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode           33 US
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     101
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              17
Device Status:     0x0001
  Self Powered

I saw the notice.  I consider what I am proposing would be personal use, I am just having dcerouter/mythtv pull this information off my personal browser for me on my behalf, for my use.

I have no problem contacting SiliconDust for written permission but wont waste their time if I am not able to actually do what I am asking to do.  Maybe it is the exception to the rule but I have found that requests such as this are granted most times, even more so when you are not asking them for any new information. 

So again, I think the information is there and could be fairly easy to access but I am not capable of writing this and getting it into the initial mythtv build that lmce does.  If someone is interested in assisting me I will take care of the permissions and do as instructed with the coding.

I held the Picture-In-Picture analogy for a long time before I accepted that the images you see on-screen are not bound like typical AV equipment,  overlays are possible because what you see is generated for you at that moment. 

Using UI2 w/ alpha blending the screen for single cam view is actually not that bad and because the audio track to what I am watching continues, I don't miss dialog.  If you forced your media into a cam view of quad-cam audio could be an issue.

I am very familiar with "I think I heard something" or "is someone here?"  In our house we handle this with touchscreen orbiters.  The media continues on-screen (unless of course it is telecom, security event etc) and these quick-checks of the cameras are done with orbiter/web orbiter/qtorbiter.  Now to get streaming video you will want true orbiters for this, as web-orbiter 2.0 just gives you a snapshot unless refreshed.

I understand the button mapping 'should' change when in gameplay.  When I say BACK I mean the gamepad beings up the onscreen UI just as it would if I was at flicker art and wanted to see the menu or wanted to exit a media file grid.  Because each remote labels these buttons differently I have a hard time explaining...

On the simple 4 button remote.  The topmost button works as a left mouse button would, rightmost button works like a right mouse click.

Enter gameplay. Super Mario Bros NES for example.
Topmost button = A (menus, fireballs)
Rightmost button = B (jump)

Pressing the rightmost button jumps but it also brings up the UI overlay.  This is bad because until you press "B" again, all directional key presses navigate the UI and "A" works like "enter". 

I wanted to list a few of the usb-gamepads I have used and their detection issues, performance and what I have done to get them working as game remotes. 

Common Problems:
USB-Gamepad is detected and two devices are created, usb-gamepad & usb-gamepad remote.
Use as controller for onscreen orbiter works very well however the device is not "grabbed" by the game player.  When a game is being played pressing back still brings up the onscreen UI.
I overcome this problem by using the remotes exclusively for gameplay by disabling "usb-gamepad remote" and deleting its key settings.


MicroSoft Plug & Play Game Pad (part no. X04-97602)
Comfortable, very much like a madcatz 'stretched' PS2 remote feel.  4 buttons with L & R triggers.  D-pad is not analog but works well for older titles using very clean UP, DOWN, etc etc without rolled diagonal inputs being common.  Good little gamepad for people who prefer very deliberate key presses, also the most simple of my game pads as in it doesn't require toggling between modes or having too many unused buttons.  Short usb cable requires an extension to play comfortably

Game Foundry USB GAME PAD (G60310A)
Used as my main living room gamepad, dual analog (doubling as buttons 9 & 10), d-pad, esc & enter located centrally where start select would be, 4 front buttons, 2 L & 2 R shoulder buttons, "mode" button.  The mode button toggles use of the analog controls which for most of the games playable currently are just a tad over sensitive.  Pressing down on the analogs for buttons 9 & 10 is disabled when "mode" is not illuminated.  Some titles for reasons I have not resolved also require "mode" while others do not, regardless of if d-pad or analog stick is used...   Good cord length does not need an extension in small to medium rooms.

GameStop branded Mad Catz Xbox 360 wired controller
Horrible, sorry I have nothing good to say about this controller under lmce as a gamepad remote.  As a orbiter remote I have nothing short of 4 letter words about it.  The sensitivity is just so high that trying to select Lights on UI2 could easily end up bringing up KDE desktop!  Maybe for some of the later MegaDrive games this could be useful but I haven't come across a use for it yet.

This could well be a mythtv development issue but it could be helpful to add to the HDhomeRun setup scripts lmce already employs.  This particular TV tuner does appear to be one of the more popular in use by lmce users.

http://www.silicondust.com/support/channels/

I am a supporter of datadirect's service, but the difference between cheap and free at times is pretty noteworthy.  I can probably do 90% of the work on making this an easily selectable option in mythtv setup if someone is able to oversee and provide the assistance with the other 10%. 

There are other free guide data sources I have used such as iTV for iOS that with more work could be brought in as well but as the protocols add up in number I would need more assistance.  So if there are other aspiring developers out there looking for a project and like this idea, respond.   

I was successful in making a few LMCE breakers.  My inexperience with making scripts into executible .sh prevented me from further integrating it as a computing application etc.  I am basically just toggling between two sources.list files with rename commands. 

example.   
/etc/apt/sources_off.list = ##original list
/etc/apt/sources_on.list = the toggled state (useful to know if which file is active, with a simple search if the file sources_off exists then the ## is in use, if sources_on exists then the original is in place)
/etc/apt/sources.list = original list

disable_updates.sh
rename sources.list to sources_off.list
rename sources_on.list to sources.list

enable_updates.sh
rename sources.list to sources_on.list
rename sources_off to sources.list

As Posde mentioned, I only had this on my core.  It was the only machine that I could not resolve automagic updates on.  Use of the past tense here is important because having onboard video continue to work after installation on a hybrid was not worth the frustration of having to remember to toggle every time I did just about anything on the network.  I instead placed a $5 ATI X300 card into the hybrid and use its VGA output.  The simplicity of the toggled state .list way of applying or removing settings may be helpful and simple for other issues people are looking for a temporary solution on.

I have issues with my cm15a every few months that I have to resolve outside of LMCE on a windows machine.  If your cli capable you may be able to push this directly.?

I don't have tech specs but it appears that the cm15a retains firmware/settings in volatile memory.  After I change the AAAs and run ActiveHome Pro's command to "save to interface" I am able to use it under LMCE until it runs the batteries down AND is bumped or unplugged from the wall.

May want to try it out.  One final note is on the AHP start up page is a key-code enter prompt for the software.  This can be skipped with "esc" if you just want to reload the interface.

Thanks Posde.

I will look into confirm dependencies a little more.  Manipulations I may make at that level could certainly do a lot of harm so perhaps I should rethink my approach.  A backup prior to setting changes happening automagically with a boot-time option to rollback perhaps.

A small number of reboot test so far have held up with a manually un commented sources.list and manually inserted Pluto.conf and xorg.conf.  Asound & myth are my next hurdles as I can't get sound on them yet.

I havent made much progress on this yet as I have been setting up a replacement core.  Once that is running I will be doing an intentionally aggressive reboot/add/remove over the next three days for any signs of driver issues or stability problems with the hardware itself.  During that time I will be preparing notes for the "real" installation and locked settings.

My new thought on this actually makes it simple and could already exist.  "Offline Mode," I selected this in the web admin site and was still able to use web-bookmarks from a MD.  Is anyone familiar with the desired use of Offline Mode is/was?

If Offline Mode is not allready in place to handle this route I am looking to open up, I believe all I need to do is comment sources.list.  Much like the Stop-MediaUpdater, I can write a toggle script that would rename (swap name) two files:  sources.list and [anything].list.  Prior to adding a device or changing something the user would have to toggle sources.list to pull packages automatically but for working equipment I am and others may be willing to.

Sources of sources?

etc/apt/sources.  obviously is the main location and where the actual url exists, however there may be other avenues I am not familiar with such as buried away in databases. 
In web-admin packages there are the needed packages and build instructions for any device that may be added.  When something is added that needs a special download could/would pluto-main or pluto-dcerouter modify the sources.list to add repos it keeps record of?

I have had a lot of issues with standard installation devices working and then breaking after a reboot because of driver/kernel changes that I am not initiating.  Instead of hacking my install to bits and ending up with something other than LinuxMCE I wish to develop a feature.  My plan will be to write a small shell script and perhaps a few supporting files.  If they work without changing much else than I would like a dev to try it out and then figure out how to submit it.

Devices currently breaking themselves as examples:

Hybrid install w/ onboard ATI 4200 HD.  Can be installed from snapshots or 10.04 Final and works amazing with onboard HDMI w/ audio etc, as long as the hybrid is off-line.  If the machine has Internet during install or any reboot after it loads back ports and flgrx driver which breaks it.

Acer Revo 1600R as MD.  First install as new MD works flawless and uses the nvidia driver.  The MD continues to work unless it has to reboot, be reset.  On any reboot after initial it removes the nvidia driver automatically and will not run again until the moon# is deleted and re-detected as a new device.

My executable:
/usr/Pluto/bin/freeze_settings.sh & unfreeze_settings.sh. (This would also need to be present in /usr/Pluto/diskless/##/usr/Pluto/bin/

Replace sources.list with a blank or commented out version?

My problem, and where I need some assistance please:

LMCEs entire structure is built around detection, self testing and configuring new devices.  I had tried everything I can to prevent a problem driver (and will need to try for the Revo) from making two working devices into non-working devices.  Utils.sh rewrites itself, killing sources.list alone would not stop other detections from going off such as storage radar etc...

I am going to write it and test it but,

If you wanted to cement a configuration of your own, which files/scripts/initd/modprobe/blacklists would you change?