gfjardim

It depends of what services/steps you need your plugin to precede/supervene. LT just postponed VMs and Docker init from disks_mounted to started.

It's an additional container on my repository. Wow, I'm not sure how I missed this! I want to try it out, but I've been reviewing the code: https://github.com/gfjardim/docker-containers/tree/master/crashplan-desktop and it seems like it stores everything inside the Docker container? Would you considering setting it up a little more like the standard crashplan: https://github.com/gfjardim/docker-containers/blob/master/crashplan/config.sh so we don't have to adopt the account and re-synchronize every time the docker changes? That's just the GUI. There's no backup service running into it.

It's an additional container on my repository.

jonp, I was thinking, this method of yours, the two step passthrough, is much safer than the simple passthrough without the pci-stub step. This could make passthrough of USB/SATA/Ethernet pretty much doable via the VM Manager plugin. Is Eric working on something like this on the present moment? PS: little code to find in which pci bus is unRAID's usb drive: udevadm info -q path -n /dev/disk/by-label/UNRAID |grep -Po '0000:\K\w{2}:\w{2}\.\w{1}'

I know that. This code only shows you which NIC is eth(n) and the PCI id. It's designed to gather info for your method, not to replace it. If, for an example, I wish to passthrough the unconnected NIC of my board, I can easily do so. It makes easier to pin a NIC to the physical port.

A easier method of discovering the right card to passthrough is running: #!/bin/bash for ETH in $(find /sys/devices/ -type d -iname "eth[0-9]"); do port=$(basename $ETH); export $(cat $ETH/device/uevent); link_status=$(cat $ETH/operstate); desc=$(lspci -d $PCI_ID| cut -d ':' -f3) pci_bus=$(echo $PCI_SLOT_NAME|sed -e 's#0000:##') echo -e "Found NIC: $port\n Name: $desc\n PCI id: $PCI_ID\n PCI bus: $pci_bus\n Status: $link_status\n" done

Digital Devices Cine v6.5: 03:00.0 Multimedia controller: Digital Devices GmbH Octopus DVB Adapter

Added a container for CrashPlan Desktop GUI. It's based on SparklyBalls desktops and can be reached by RDP at port 3389.

Updated DropBox and ownCloud, both with invaluable contribution of HurricaneHernandez!

Added port maps (still default to host network since it's an UPnP server) and rename it to Emby. Container got updated too.

Hi, Bungy. Could you add support for this? http://lime-technology.com/forum/index.php?topic=39106.msg365627#msg365627 Thanks in advance!

Hi, Spants. Could you add support for this? http://lime-technology.com/forum/index.php?topic=39106.msg365627#msg365627 Thanks in advance!

Here it is, guys, a centralized topic for support to my containers. For specific container support, please go to the appropriate topic: CrashPlan: http://lime-technology.com/forum/index.php?topic=33864.0 ownCloud: http://lime-technology.com/forum/index.php?topic=33891.0 If you need needo's support, please go here: http://lime-technology.com/forum/index.php?topic=33822.msg312539.0 Update requests can be made here or by PM.

That's mean! We have so many projects that somethings just got lost in the way.

So I'm having the same problem. I looked to make sure that the ip/port settings are correct. I even redeployed the docker several times, and on redeploy I'm able to connect to CrashPlan for a while. Then I'm not able to reconnect, the launcher on Windows just stays open, but does not say unable to connect to server. And it will actually stay open for a while and close when I shutdown the docker. So I know there is some sort of connection being formed. The only thing that I've come across is: http://support.code42.com/CrashPlan/Latest/Troubleshooting/Unable_To_Connect_To_The_Backup_Engine#Linux_Solution And I noticed in the docker file that one language is not en_US like the rest. I don't know if this is related or not as I haven't figured out yet how to manually edit the docker file. Ok, found the potential flaw, now I'll try to solve it.

Thanks. I've patched this a while ago, just waiting bonienl to release the update.

Can you post the output for these?

Your sysfs structure is very different from mine. Let's try some other commands: ls -la `dirname $(find /sys/devices -iname "fan*_input")` ls -la `dirname $(find /sys/devices -iname "pwm[0-9]")`

Please post the result of this command: find -L /sys/class/hwmon/ -maxdepth 5 -iname "pwm[0-9]" 2>/dev/null Here you go: /sys/class/hwmon/hwmon1/device/pwm1 /sys/class/hwmon/hwmon1/device/pwm2 /sys/class/hwmon/hwmon1/device/pwm3 Those are the three possible pwm controls from my it87 board. Ok, I need one last command output: find /sys/devices -iname "hwmon[0-9]" -exec echo {} \; -exec ls -la {} \;

Please post the result of this command: find -L /sys/class/hwmon/ -maxdepth 5 -iname "pwm[0-9]" 2>/dev/null

Yes, I modified that script to import variables from a file. It's working fine right now. Will keep you posted about any news.

I followed these steps also, and got these drivers... coretemp nct6775 I already had coretemp working, but wanted to see if nct6775 would give me fan speed info, so I put that in the available drivers box, hit detect, then hit load drivers, and now I have more stuff available in my dropdown boxes; see attached. I don't really know which one goes with which, but it feels like progress. I use coretemp - Physical id 0 to CPU and SYSTIN to Motherboard.

This one? : Have I missed something here? What plug-in is that? I'm working on it, it's almost done.

Your drivers are k10temp and fam15h_power.

This one? :