Find out how to rename a number of folders in Linux

(Updated) [Staking] Reddcoin Core client GUI wallet on a Raspberry Pi Model 3B


This thread is an update to my first Reddcoin staking tutorial that was written 7 months ago.
The reason for the update
My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:
The updates
If you would like to tip me
Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.





This video shows how long it takes to start Reddcoin Core.   TL;DR:


Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
Boot with only 1 USB drive plugged in:
Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly.   If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
Start Reddcoin Core easier
Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
Minimization options
Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
Updates / Upgrades
If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.  


Credits in previous tutorial:
submitted by Yavuz_Selim to reddCoin [link] [comments]

Threadripper KVM GPU Passthru: Testers needed

TL;DR: Check update 8 at the bottom of this post for a fix if you don't care about the history of this issue.
For a while now it has been apparent that PCI GPU passthrough using VFIO-PCI and KVM on Threadripper is a bit broken.
This manifests itself in a number of ways: When starting a VM with a passthru GPU it will either crash or run extremely slowly without the GPU ever actually working inside the VM. Also, once a VM has been booted the output of lspci on the host changes from one kind of output to another. Finally the output of dmesg suggests an issue bringing the GPU up from D0 to D3 power state.
An example of this lspci before and after VM start, as well as dmesg kernel buffer output is included here for the 7800GTX:
08:00.0 VGA compatible controller: NVIDIA Corporation G70 [GeForce 7800 GTX] (rev a1) (prog-if 00 [VGA controller]) [ 121.409329] virbr0: port 1(vnet0) entered blocking state [ 121.409331] virbr0: port 1(vnet0) entered disabled state [ 121.409506] device vnet0 entered promiscuous mode [ 121.409872] virbr0: port 1(vnet0) entered blocking state [ 121.409874] virbr0: port 1(vnet0) entered listening state [ 122.522782] vfio-pci 0000:08:00.0: enabling device (0000 -> 0003) [ 123.613290] virbr0: port 1(vnet0) entered learning state [ 123.795760] vfio_bar_restore: 0000:08:00.0 reset recovery - restoring bars ... [ 129.534332] vfio-pci 0000:08:00.0: Refused to change power state, currently in D3 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation G70 [GeForce 7800 GTX] [10de:0091] (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: vfio-pci 
Notice that lspci reports revision FF and can no longer read the header type correctly. Testing revealed that pretty much all graphics cards except Vega would exhibit this behavior, and indeed the output is very similar to the above.
Reddit user wendelltron and others suggested that the D0->D3 transition was to blame. After having gone through a brute-force exhaustive search of the BIOS, kernel and vfio-pci settings for power state transitions it is safe to assume that this is probably not the case since none of it helped.
AMD representative AMD_Robert suggested that only GPUs with EFI-compatible BIOS should be able to be used for passthru in an EFI environment, however, testing with a modern 1080GTX with EFI bios support failed in a similar way:
42:00.0 VGA compatible controller: NVIDIA Corporation Device 1b80 (rev a1) and then 42:00.0 VGA compatible controller: NVIDIA Corporation Device 1b80 (rev ff) (prog-if ff) !!! Unknown header type 7f 
Common to all the cards was that they would be unavailable in any way until the host system had been restarted. Any attempt at reading any register or configuration from the card would result in all-1 bits (or FF bytes). The bitmask used for the headers may in fact be what is causing the 7f header type (and not an actual header being read from the card). Not even physically unplugging and re-plugging the card, rescanning the PCIe bus (with /sys/bus/pci/rescan) would trigger any hotplug events or update the card info. Similarly, starting the system without the card and plugging it in would not be reflected in the PCIe bus enumeration. Some cards, once crashed, would show spurious PCIe ACS/AER errors, suggesting an issue with the PCIe controller and/or the card itself. Furthermore, the host OS would be unable to properly shut down or reboot as the kernel would hang when everything else was shut down.
A complete dissection of the vfio-pci kernel module allowed further insight into the issue. Stepping through VM initialization one line at a time (yes this took a while) it became clear that the D3 power issue may be a product of the FF register issue and that the actual instruction that kills the card may have happened earlier in the process. Specifically, the function drivers/vfio/pci/vfio_pci.c:vfio_pci_ioctl, which handles requests from userspace, has entries for VFIO_DEVICE_GET_PCI_HOT_RESET_INFO and VFIO_DEVICE_PCI_HOT_RESET and the following line of code is exactly where the cards go from active to "disconnected" states:
if (!ret) /* User has access, do the reset */ ret = slot ? pci_try_reset_slot(vdev->pdev->slot) : pci_try_reset_bus(vdev->pdev->bus); 
Commenting out this line allows the VM to boot and the GPU driver to install. Unfortunately for the nVidia cards my testing stopped here as the driver would report the well known error 43/48 for which they should be ashamed and shunned by the community. For AMD cards a R9 270 was acquired for further testing.
The reason this line is in vfio-pci is because VMs do not like getting an already initialized GPU during boot. This is a well-known problem with a number of other solutions available. By disabling the line it is neccessary to use one of the other solutions when restarting a VM. For Windows you can disable the device in Device Manager before reboot/shutdown and re-enable it again after the restart - or use login/logoff scripts to have the OS do it automatically.
Unfortunately another issue surfaced which made it clear that the VMs could only be stopped once even though they could now be rebooted many times. Once they were shut down the cards would again go into the all FF "disconnect" state. Further dissection of vfio-pci revealed another instance where an attempt to reset the slot that the GPU is in was made: in drivers/vfio/pci/vfio_pci.c:vfio_pci_try_bus_reset
if (needs_reset) ret = slot ? pci_try_reset_slot(vdev->pdev->slot) : pci_try_reset_bus(vdev->pdev->bus); 
When this line is instead skipped, a VM that has had its GPU properly disabled via Device Manager and has been properly shutdown is able to be re-launched or have another VM using the same GPU launched and works as expected.
I do not understand the underlying cause of the actual issue but the workaround seems to work with no issues except the annoyance of having to disable/re-enable the GPU from within the guest (like in ye olde days). Only speculation can be given to the real reason of this fault; the hot-reset info gathered by the ioctl may be wrong, but the ACS/AER errors suggest that the issue may be deeper in the system - perhaps the PCIe controller does not properly re-initialize the link after hot-reset just as it (or the kernel?) doesn't seem to detect hot-plug events properly even though acpihp supposedly should do that in this setup.
Here is a "screenshot" of Windows 10 running the Unigine Valley benchmark inside a VM with a Linux Mint host using KVM on Threadripper 1950x and an R9 270 passed through on an Asrock X399 Taichi with 1080GTX as host GPU:
This is the culmination of many weeks of debugging. It is interesting to hear if anyone else is able to reproduce the workaround and can confirm the results. If more people can confirm this then we are one step closer to fixing the actual issue.
If you are interested in buying me a pizza, you can do so by throwing some Bitcoin in this direction: 1KToxJns2ohhX7AMTRrNtvzZJsRtwvsppx
Also, English is not my native language so feel free to ask if something was unclear or did not make any sense.
Update 1 - 2017-12-05:
Expanded search to non-gpu cards and deeper into the system. Taking memory snapshots of pcie bus for each step and comparing to expected values. Seem to have found something that may be the root cause of the issue. Working on getting documentation and creating a test to see if this is indeed the main problem and to figure out if it is a "feature" or a bug. Not allowing myself to be optimistic yet but it looks interesting, it looks fixable at multiple levels.
Update 2 - 2017-12-07:
Getting a bit closer to the real issue. The issue seems to be that KVM performs a bus reset on the secondary side of the pcie bridge above the GPU being passed through. When this happens there is an unintended side effect that the bridge changes its state somehow. It does not return in a useful configuration as you would expect and any attempt to access the GPU below it results in errors.
Manually storing the bridge 4k configuration space before the bus reset and restoring it immediately after the bus reset seems to magically bring the bridge into the expected configuration and passthru works.
The issue could probably be fixed in firmware but I'm trying to find out what part of the configuration space is fixing the issue and causing the bridge to start working again. With that information it will be possible to write a targeted patch for this quirk.
Update 3 - 2017-12-10:
Begun further isolation of what particular registers in the config space are affected unintentionally by the secondary bus reset on the bridge. This is difficult work because the changes are seemingly invisible to the kernel, they happen only in the hardware.
So far at least registers 0x19 (secondary bus number) and 0x1a (subordinate bus number) are out of sync with the values in the config space. When a bridge is in faulty mode, writing their already existing value back to them brings the bridge back into working mode.
Update 4 - 2017-12-11 ("the ugly patch"):
After looking at the config space and trying to figure out what bytes to restore from before the reset and what bytes to set to something new it became clear that this would be very difficult without knowing more about the bridge.
Instead a different strategy was followed: Ask the bridge about its current config after reset and then set its current config to what it already is; byte by byte. This brings the config space and the bridge back in sync and everything, including reset/reboot/shutdown/relaunch without scripts inside the VM, now seems to work with the cards acquired for testing. Here is the ugly patch for the brave souls who want to help test it.
Please, if you already tested the workaround: revert your changes and confirm that the bug still exists before testing this new ugly patch:
In /drivers/pci/pci.c, replace the function pci_reset_secondary_bus with this alternate version that adds the ugly patch and two variables required for it to work:
void pci_reset_secondary_bus(struct pci_dev *dev) { u16 ctrl; int i; u8 mem; pci_read_config_word(dev, PCI_BRIDGE_CONTROL, &ctrl); ctrl |= PCI_BRIDGE_CTL_BUS_RESET; pci_write_config_word(dev, PCI_BRIDGE_CONTROL, ctrl); /* * PCI spec v3.0 requires minimum Trst of 1ms. Double * this to 2ms to ensure that we meet the minimum requirement. */ msleep(2); ctrl &= ~PCI_BRIDGE_CTL_BUS_RESET; pci_write_config_word(dev, PCI_BRIDGE_CONTROL, ctrl); // The ugly patch for (i = 0; i < 4096; i++){ pci_read_config_byte(dev, i, &mem); pci_write_config_byte(dev, i, mem); } /* * Trhfa for conventional PCI is 2^25 clock cycles. * Assuming a minimum 33MHz clock this results in a 1s * delay before we can consider subordinate devices to * be re-initialized. PCIe has some ways to shorten this, * but we don't make use of them yet. */ ssleep(1); } 
The idea is to confirm that this ugly patch works and then beautify it, have it accepted into the kernel and to also deliver technical details to AMD to have it fixed in BIOS firmware.
Update 5 - 2017-12-20:
Not dead yet!
Primarily working on communicating the issue to AMD. This is slowed by the holiday season setting in. Their feedback could potentially help make the patch a lot more acceptable and a lot less ugly.
Update 6 - 2018-01-03 ("the java hack"):
AMD has gone into some kind of ninja mode and has not provided any feedback on the issue yet.
Due to popular demand a userland fix that does not require recompiling the kernel was made. It is a small program that runs as any user with read/write access to sysfs (this small guide assumes "root"). The program monitors any PCIe device that is connected to VFIO-PCI when the program starts, if the device disconnects due to the issues described in this post then the program tries to re-connect the device by rewriting the bridge configuration.
This program pokes bytes into the PCIe bus. Run this at your own risk!
Guide on how to get the program:
If you have any PCI devices using VFIO-PCI the program will output something along the lines of this:
------------------------------------------- Zen PCIe-Bridge BAConfig Recovery Tool, rev 1, 2018, HyenaCheeseHeads ------------------------------------------- Wed Jan 03 21:40:30 CET 2018: Detecting VFIO-PCI devices Wed Jan 03 21:40:30 CET 2018: Device: /sys/devices/pci0000:40/0000:40:01.3/0000:42:00.0 Wed Jan 03 21:40:30 CET 2018: Bridge: /sys/devices/pci0000:40/0000:40:01.3 Wed Jan 03 21:40:30 CET 2018: Device: /sys/devices/pci0000:00/0000:00:01.3/0000:08:00.1 Wed Jan 03 21:40:30 CET 2018: Bridge: /sys/devices/pci0000:00/0000:00:01.3 Wed Jan 03 21:40:30 CET 2018: Device: /sys/devices/pci0000:40/0000:40:01.3/0000:42:00.1 Wed Jan 03 21:40:30 CET 2018: Bridge: /sys/devices/pci0000:40/0000:40:01.3 Wed Jan 03 21:40:30 CET 2018: Device: /sys/devices/pci0000:00/0000:00:01.3/0000:08:00.0 Wed Jan 03 21:40:30 CET 2018: Bridge: /sys/devices/pci0000:00/0000:00:01.3 Wed Jan 03 21:40:30 CET 2018: Monitoring 4 device(s)... 
And upon detecting a bridge failure it will look like this:
Wed Jan 03 21:40:40 CET 2018: Lost contact with /sys/devices/pci0000:00/0000:00:01.3/0000:08:00.1 Wed Jan 03 21:40:40 CET 2018: Recovering 512 bytes Wed Jan 03 21:40:40 CET 2018: Bridge config write complete Wed Jan 03 21:40:40 CET 2018: Recovered bridge secondary bus Wed Jan 03 21:40:40 CET 2018: Re-acquired contact with /sys/devices/pci0000:00/0000:00:01.3/0000:08:00.1 
This is not a perfect solution but it is a stopgap measure that should allow people who do not like compiling kernels to experiment with passthru on Threadripper until AMD reacts in some way. Please report back your experience, I'll try to update the program if there are any issues with it.
Update 7 - 2018-07-10 ("the real BIOS fix"):
Along with the upcoming A.G.E.S.A. update aptly named "ThreadRipperPI-SP3r2" comes a very welcome change to the on-die PCIe controller firmware. Some board vendors have already released BETA BIOS updates with it and it will be generally available fairly soon it seems.
Initial tests on a Linux 4.15.0-22 kernel now show PCIe passthru working phenomenally!
With this change it should no longer be necessary to use any of the ugly hacks from previous updates of this thread, although they will be left here for archival reasons.
Update 8 - 2018-07-25 ("Solved for everyone?"):
Most board vendors are now pushing out official (non-BETA) BIOS updates with AGESA "ThreadRipperPI-SP3r2" including the proper fix for this issue. After updating you no longer need to use any of the temporary fixes from this thread. The BIOS updates comes as part of the preparations for supporting the Threadripper 2 CPUs which are due to be released in a few weeks from now.
Many boards support updating over the internet directly from BIOS, but in case you are a bit old-fashioned here are the links (please double-check that I linked you the right place before flashing):
Vendor Board Update Link
Asrock X399 Taichi Update to 2.3, then 3.1
Asrock X399M Taichi Update to 1.10 then 3.1
Asrock X399 Fatality Profesional Gaming Update to 2.1 then 3.1
Gigabyte X399 AURUS Gaming 7 r1 Update to F10
Gigabyte X399 DESIGNARE EX r1 Update to F10
Asus PRIME X399-A Possibly fixed in 0601 (TR2 support and sure fix inbound soon)
Asus X399 RoG Zenith Extreme Possibly fixed in 0601 (TR2 support and sure fix inbound soon)
Asus RoG Strix X399-E Gaming Possibly fixed in 0601 (TR2 support and sure fix inbound soon)
MSI X399 Gaming Pro Carbon AC Update to Beta BIOS 7B09v186 (TR2 update inbound soon)
MSI X399 SLI plus Update to Beta BIOS 7B09vA35 (TR2 update inbound soon)
submitted by HyenaCheeseHeads to Amd [link] [comments]

Homelab collective ressources post!

Hey guys!
I'm fairly new to this sub and to having a home lab in general and I found this community to be so kind and helping, I wanted to give back what I've learned. I'm seeing a lot of questions asked around on improvements and on what to do with x extra hardware so I thought it would be nice to have a thread to regroup that.
I'll put here some stuff I gathered and the most common questions I've seen, feel free to contribute and i'll update the post along.
Latest Additions
Homelab Dashboard
Posts about dashboards have been growing lately and here are some of the best that were kind enough to provide us with their sources.
User Screenshot Source
yours truly
NiknakSi TBA
yourofl10 TBA
mescon & SyNiK4L
Or build yours from scratch: PRTG API, ELK, Grafana, freeboard, JumpSquares
Some other resources: Custom Monitoring Scripts by 0110010001100010
Credits to apt64 for his original post
= Pi specific =
= Download Automation =
= Virtualization =
= Monitoring =
= Media Center =
= Remote access =
= VOIP =
= Networking =
= File Servers/Storage/RAID =
= Cameras =
= Documentation =
= Dynamic DNS =
= Backup =
= Creating network diagrams =
= Guides =
= Misc =
That's all I could come up with on top of my head + some research, passing over to you guys so we can get a nice complete list!
Let's try and stick with free(or mostly) softwares, let me know if you guys feel otherwise.
submitted by Gabisonfire to homelab [link] [comments]

Creating a Headless Staking Node on Ubuntu 18.04

Creating a Headless Staking Node on Ubuntu 18.04
##UPDATE## Step 8 - Option 2, has some bugs in the final build process. i haven't had time to work them out yet!

This guide will take you through building and running a headless x42 Full Node! The OS I am using here is Ubuntu 18.04, this guide picks up from a complete/fresh ubuntu install.
This is meant to setup a staking node and so this guide will run you through building, configuring and setting up staking. It will not cover sending transactions or anything else.
The things we are going to do:
  • Step 1 - Install .net core
  • Step 2 - Download The x42 Node Source & Compile It
  • Step 3 - Setting The x42 Node Up To Run On Boot
  • Step 4 - Setup A New Wallet
  • Step 5 - Configure The x42 Daemon
  • Step 6 - Get Address
  • Step 7 - Check Balance
  • Step 8 - Connect The UI Wallet To A Headless Node
  • Step 8 - [Option 1 - Use Installer] Connect The UI Wallet To A Headless Node
  • Step 8 - [Option 2 - Build/Compile UI Only] Connect The UI Wallet To A Headless Node # BROKEN#

Step 1 - Install .net Core

Here is the reference link:
Register Microsoft Key’s & Install Their repos:
cd /tmp wget -q sudo dpkg -i packages-microsoft-prod.deb sudo add-apt-repository universe sudo apt -y install apt-transport-https sudo apt update sudo apt -y install dotnet-sdk-2.2 
Microsoft collect telemetry data by default, if you are part of the “tin foil hat brigade” you can set the following environment variable to turn it off:
echo "DOTNET_CLI_TELEMETRY_OPTOUT=1" >> /etc/environment 
now you should be at a point where .net core is installed on your system… that wasn’t so hard was it! You can check by running the following command:
The output should look like this:
$ dotnet --list-sdks 2.2.103 [/usshare/dotnet/sdk] 

Step 2 - Download & Compile The x42 Node

This part assumes you have GIT installed, if not:
apt -y install git 
Now to pull down the source and compile it!
cd ~/ git clone # “cd” into the source folder cd X42-FullNode/src/ 
Now .net core uses NuGet for package management, before we compile, we need to pull down all of the required packages.. its as simple as running (this will take a couple of minutes) inside of “X42-FullNode/src/”:
dotnet restore 
now we are ready to compile the source, execute (inside of “X42-FullNode/src/”):
dotnet build --configuration Release 
ignore the yellow warnings, this is just the rosyln compiler having a grumble.. if you get red ones then something went wrong! The “--configuration Release” will strip out all debug symbols and slim things down.. only a little, this optional parameter is not mandatory.
Once this is done everything is built/compiled, you can run the daemon directly from the repository, this can be done by going to:
cd ~/X42-FullNode/src/x42.x42D/bin/Release/netcoreapp2.1 dotnet x42.x42D.dll 
this will kick off the node, however if you exit SSH at this time it will kill the process! however I always recommend copying out the binaries to a separate folder. This can be done with the following:
mkdir ~/x42node mv ~/X42-FullNode/src/x42.x42D/bin/Release/netcoreapp2.1/*.* ~/x42node/ 
now we have everything we need to run the node outside the git repository! What we need to do now is run the node and have it create the default x42.conf file.. so
cd ~/x42node dotnet x42.x42D.dll 
feel free to hit “CTRL + C” to exit the application after a couple of seconds, by then the folders/files would have been created at the following path:

Step 3 - Setting The x42 Node Up To Run on Boot

Now we are going to create a service file so our x42 node automatically starts when the system is rebooted.
THINGS TO NOTE ABOUT BELOW.. CHANGE THE ##USER## to the username your currently using as these files are within your home directory!
We need to drop to root for this..
sudo -i cat < /etc/systemd/system/x42node.service [Unit] Description=x42 Node [Service] WorkingDirectory=/home/##USER##/x42node ExecStart=/usbin/dotnet /home/##USER##/x42node/x42.x42D.dll Restart=always # Restart service after 10 seconds if the dotnet service crashes: RestartSec=10 SyslogIdentifier=x42node User=##USER## Environment=ASPNETCORE_ENVIRONMENT=Development [Install] EOF 
To enable the service, run the following (as the root user):
systemctl enable x42node.service 
BOOM.. the node isn’t running yet.. but next time the system restarts it will automatically run!
now lets exit out of root!
We can now start the node up and begin downloading blocks, by running the following command:
sudo systemctl start x42node.service 
if you want to check its loaded and see some of the output, you can run:
sudo systemctl status x42node.service 
an example of the output:
$ sudo systemctl status x42node.service ● x42node.service - x42 Node Loaded: loaded (/etc/systemd/system/x42node.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-01-24 15:47:55 UTC; 14s ago Main PID: 5456 (dotnet) Tasks: 23 (limit: 1112) CGroup: /system.slice/x42node.service └─5456 /usbin/dotnet /home/darthnoodle/x42node/x42.x42D.dll Jan 24 15:48:09 x42staking x42node[5456]: Batch Size: 0 Mb (0 headers) Jan 24 15:48:09 x42staking x42node[5456]: Cache Size: 0/50 MB Jan 24 15:48:09 x42staking x42node[5456]: Jan 24 15:48:09 x42staking x42node[5456]: =======Mempool======= Jan 24 15:48:09 x42staking x42node[5456]: MempoolSize: 0 DynamicSize: 0 kb OrphanSize: 0 Jan 24 15:48:09 x42staking x42node[5456]: Jan 24 15:48:09 x42staking x42node[5456]: info: Stratis.Bitcoin.Connection.ConnectionManagerBehavior[0] Jan 24 15:48:09 x42staking x42node[5456]: Peer '[::ffff:]:52342' connected (outbound), agent 'x42:1.2.13 (70012)', height 213920 Jan 24 15:48:09 x42staking x42node[5456]: info: Stratis.Bitcoin.Connection.ConnectionManagerBehavior[0] Jan 24 15:48:09 x42staking x42node[5456]: Peer '[::ffff:]:52342' offline, reason: 'Receiving cancelled.'. All node screen output can be found in the /valog/syslog file. 

Step 4 - Setup a New Wallet

With the Node running, we now need to setup and/or restore a wallet!
Everything will be performed through the API’s, however by default these API’s are listening on localhost (, if you are connecting in remotely then this would be a problem since you cant hit that IP. The solution, SSH TUNNEL!
Execute the following command on your local system:
ssh -L 42220:localhost:42220 @ 
This binds the local port (on your system) with on the remote system, once you have executed the command you can type the following address in your laptop/desktop’s web browser and be able to access the API’s: 
It should look something like this:
To Create a new wallet, first we have to generate some mnemonic works (e.g. the seed), you can do that by going to the following API:
Hit the “Try it out” button which then prompts you for 2 fields:
Enter “English” and I would recommend 24 words as this greatly increases the seed strength! Once that is done you hit execute and then scroll down to see the “Response Body”, this should contain the mnemonic which you are going to use to create the wallet! This looks something like below:
So now we have our mnemonic, its time to generate the wallet, for this we need to use the API:
There are a number of parameters which are required in order to create a wallet:
WalletCreationRequest{ mnemonic string password* string passphrase* string name* string } 
It should be noted that the password and mnemonic are is the most important parts of this request where the “password” will encrypt the wallet and Is required to unlock it.
  • Hit the “Try it out” button
  • input the necessary data
  • Insert the mnemonic
  • Put a password & passphrase
  • “Name” is what your wallet will be called
It should look something like the following:
Hit “Execute”, the “Loading” sign may spin for a few minutes while the wallet is created… once the wallet has been created the “Response Body” will return the mnemonic you have just used.. we now have a wallet!!
This is where we will now jump back out and to configure the node to automatically load the wallet and automatically start staking when it first loads.

Step 5 - Configure The x42 Daemon

Now we are going to modify the x42.conf file in order to automatically load our wallet and start staking 😊
First things first, lets stop our node by running the following command:
sudo systemctl stop x42node.service 
CD to the following folder and view its contents:
~/.x42node/x42/x42Main ls -lah 
within that folder there should be 2 files you are interested in:
-rw-r--r-- 1 darthnoodle darthnoodle 18K Jan 28 16:01 TestWallet.wallet.json -rw-rw-r-- 1 darthnoodle darthnoodle 3.1K Jan 24 15:25 x42.conf 
So TestWallet.wallet.json is our physical wallet that will be loaded, but for right now we want to modify the x42.conf file.. fire up your favourite text editor (if you use VI you’re a masochist)..
nano x42.conf 
The area we are interested in is the following:
####Miner Settings#### #Enable POW mining. #mine=0 #Enable POS. #stake=0 #The address to use for mining (empty string to select an address from the wallet). #mineaddress= #The wallet name to use when staking. #walletname= #Password to unlock the wallet. #walletpassword= #Maximum block size (in bytes) for the miner to generate. #blockmaxsize=1000000 #Maximum block weight (in weight units) for the miner to generate. #blockmaxweight=1000000 #Enable splitting coins when staking. #enablecoinstakesplitting=1 #Minimum size of the coins considered for staking, in satoshis. #minimumstakingcoinvalue=10000000 #Targeted minimum value of staking coins after splitting, in satoshis. #minimumsplitcoinvalue=10000000000 
Uncomment (remove the #) of the following lines and change their value:
stake=1 (changed to 1) walletname=TestWallet (changed to our Wallet Name) walletpassword=password123 (changed to the wallet password) 
save the file and exit back to the command prompt, now we shall restart the node with the following command:
sudo systemctl status x42node.service 
now the wallet is automatically loaded and ready for action!
You can check its loaded by going back to the API and executing the following command:
Or execute the following command on the NODE:
curl -X GET "" -H "accept: application/json" 
both will produce the same output, if you scroll to the bottom you should see something like this:
======Wallets====== TestWallet/account 0, Confirmed balance: 0.00000000 Unconfirmed balance: 0.00000000 
This means the wallet is loaded and ready for action!!

Step 6 - Get Addresses

Next thing you are probably going to want is a receive address and to check the balance and TX history.. so lets start with getting an address!
Go to the following API:
Fill in the Wallet name which is “TestWallet” (in this example) and “account 0” (which is the first/default account):
Hit execute and you should have an x42 address within the “Response Body”:
BOOM… ok now we can receive funds! 😊

Step 7 - Check TX History

Go to the API and the following call:
The 2 fields we are most concerned about are:
Input the name of the wallet and account you want to view the history of, then hit execute. The other fields can be black. This will return a list of TX’s that the wallet has received:
This should look like the following:
There is an easier way of doing this, that doesn’t require you to be connected to your node.. especially if your only interested in viewing your staking rewards… THE EXPLORER!
Access the following URL: 
this will allow you to easily see all TX’s associated with this address, it should look something like below:
… and your done! By this point your node should be running, staking and you have an easy way to view transactions/rewards 😊

Step 8 - Connect The UI Wallet To A Headless Node

The UI utilises a combination of technologies, however the important part is the code attempts to access the x42 Node API on
So you have 2 options here:
  1. Download the Wallet Installers
  2. Compile The UI Yourselves
Pick the option that best suits you given the pros/cons below:
Option 1 - Pro's/Cons
  • If you use the installer, its quick and easy.
  • This also installs an x42 node on your system which runs when the UI loads.
  • If you dont setup an SSH tunnel before running the wallet the local node will bind to the port and the tunnel wont work.. you will be connecting to the local wallet!!
Option 2 - Pro's/Cons
  • You only run the UI, the x42 node is not installed
  • you dont have a superfluous node running, downloading blocks on your local system
  • Time Consuming
  • Have to download dependencies and manually compile the code

Pre-Requirement - Needed For Both Options!!
As previously mentioned, the UI attempts to access the API's on, however our node isnt running on our local system. IN ORDER TO GET IT WORKING YOU NEED TO HAVE AN SSH TUNNEL, THIS TUNNEL NEEDS TO REMAIN ACTIVE WHENEVER YOU WANT TO ACCESS THE WALLET.
this can be done by executing the following command:
ssh -L 42220:localhost:42220 @ 

Step 8 - [Option 1 - Use Installer] Connect The UI Wallet To A Headless Node

Download and install the UI/Wallet & Node from:

Those of us who dont want to run a local node and just want the UI, execute the following commands (as an administrator):
cd C:\Program Files\x42 Core\resources\daemon\ ren x42.x42D.exe x42.x42D.exe.bak 
The above is with Windows, if your are in *NIX then locate the daemon and rename it (i will update how to do that/where to find it shortly)
Setup the SSH tunnel as outlined above, Execute the wallet and it will load, however you will see an exception:
dont worry, this is just the wallet trying to execute/start the x42 node which we dont want, if all works according to plan.. after you click "OK" you should now be presented with the wallet UI and have the option to select what wallet you would like to load:
... DONE!

Step 8 - [Option 2 - Build/Compile UI Only] Connect The UI Wallet To A Headless Node ###BROKEN


Ok, this is the fun bit! .. we need to install the following dependencies. these instructions are written for a Windows system but it should be easy enough to perform the same on a *NIX system.
Install Dependencies
In order to build the wallet UI, you need to install the following components:
  • git
  • NodeJS
  • Electron Builder
First thing you need to do is install git, so download and install the package:
Next you need to install NodeJS, download and install the package:
Next we need to install the node package manager:
npm install npx –verbose 
next we need to make sure we have Visual Studio build tools and Python (2.7) installed, this can be done by executing the following (AS AN ADMINISTRATOR!):
npm install -g --production windows-build-tools 
this will install the necessary tools to build C#/C++ code and python 2.7, this could take some time! When its done you should have something like the following;

Build & Install - Windows
Create a temp folder to navigate to a folder where you want to download the GIT repository, execute the following command:
git clone 
This will clone the repository into the folder, it will only clone the wallet and not the Node source! now lets CD into the folder and build the UI:
cd X42-FullNode-UI\FullNode.UI npm install 
This will download and install all dependencies (can take a while), at the end you should see something like..
Now the stock UI has a number of third-party libraries which contain some vulnerabilities, being a security conscious person, ive also run:
npm audit fix 
when this is done, we have fixed most of the package vulnerabilities 😊 We also get a complaint about the typescript library being too new for the version of angular in use, so run the following command to install the additional dependency:
npm install [email protected]">=2.4.2 <2.7.0" 
now its time to build the UI, execute the following:
npm run build:prod 
once complete you should see something like the following..
Next its time to compile the electron binary, it should be noted that the build/package process utilises AppVoyer which is not installed and if you attempt to build right now you will get the following error:
cannot expand pattern "${productName}-v${version}-setup-${os}-${env.arch}.${ext}": env arch is not defined. 
To fix this we need to modify the build file, this is a quick one liner that can do it:
powershell -Command "(gc electron-builder.json) -replace 'env.arch', 'arch' | Out-File electron-builder.json" 
Essentially the offending line for Windows is..
"artifactName": "${productName}-v${version}-setup-${os}-${env.arch}.${ext}" 
The build cannot resolve “env.arch”, so the above one liner replaces “env.arch” with “arch” which works 😊
execute the following command:
npx electron-builder build --windows --x64 
At present i get the following error, no matter what i do.. and ive ran out of time to go hunting about.. if anyone has any ideas on how to fix then please post in here or message me on discord:

Happy staking!

If you found this post helpful, then buy me a beer and send a donation to XQXeqrNFad2Uu7k3E9Dx5t4524fBsnEeSw
submitted by D4rthNoodle to x42 [link] [comments]

Seedbox for Usenet & Sonarr/Radarr

I've filled out more than one of these over the past few weeks, and I hope that's ok. The more I research and learn, the more my wants/needs evolve. I figured it's easier to fill out a new form that try and explain changes in one I already posted.
• What is your budget per month? Around $10-$25 USD
• How much disk space do you need? Flexible
• Are you looking for shared or dedicated seedbox? I think shared is fine.
• Particular uses, streaming? VPN? One-click ease? Racing? NZBGet, radarr, sonarr, transferring downloads to Google Drive, and transferring files to local machine • What is the primary reason for getting a seedbox? Currently I use sonarradarnzbget to download my movie/tv library to my local machine. My media library folders are then synced to my G Suite Google Drive as a backup using my relatively slow upload at home (upstream only 10mbps). I'd like to use a seedbox to offload NZBGet, Sonarr, and Radarr to the cloud. My ideal end result would be RadarSonarr tells NZBGet what to download. After downloading, files are synced to my local machine somehow where they can be added to my Plex library. I do not have a strong preference whether the files are renamed and organized before or after being synced to my local machine. The only other thing I'd love to see happen would be for the files to somehow be automatically transferred to my GDrive straight from my seedbox as a way to bypass my slow home upload speed.
Though I'm slowly learning, my capabilities with linux and the command line is beginner at best. I'd be willing to pay a little more each month to have the setup process for all of this be as easy as possible.
• Location (yours and/or the vendors)? I'm in the US. • Particular speed (100M, 1G, 10G, Ludicrous Speed, etc)? I'd say a minimum of 1G, but the faster the better.
• Do you use public trackers extensively? Not really. I will honestly be doing very little torrenting (mainly Usenet).
• How much experience do you have with seedboxes, linux, and alike? Need a lot of handholding? Very minimal experience with seedboxes. I've spent the last couple days playing around with some, but that's it. Some experience with Linux (have set up a few Raspberry Pis, and have played with Docker some), but am really only capable of following very explicit step-by-step directions when working with the command line.
• Is your location problematic? e.g. I'm at university. I'm one of three people on the island of Yap. No
• Particular payment methods the vendor needs to accept: bitcoin, paypal, paysafecard, Turkish Lire? No
• Particular content: Games, TV shows, Anime; Movies; Remuxes; the oeuvre of Fatty Arbuckle? Ebooks, audiobooks, blu-Ray (1080p) remuxes, 1080p tv shows.
• Using problemsome trackers like public ones or challenging trackers like RED and CHD? No
• Any idea on how much bandwidth you need a month? 1TB; 3TB; 30TB? 1TB minimum, but the more the better.
• Are you a paranoiac, need special safety assurances? Not really.
• Other more unique requirements? You want to run a website too; Azureus is your favorite client, can't live without it; Or god forbid you really, really need Windows. No.
submitted by seannymurrs to seedboxes [link] [comments]

Dogecoin on Linux - The Complete Beginner's Guide

I'm writing this because I couldn't find a single condensed guide on compiling the wallet and running mining software on linux, specficially Ubuntu/Linux Mint. I combed Bitcoin and Litecoin forums for similar problems I was running into and eventually got everything nailed down, so here it is in one place, for new Shibes.
If you want to make a Dogecoin directory in your downloads folder to keep things organized, you will need to modify these commands to refelct the change. So instead of going to ~/Downloads/ you will need to go to ~/Downloads/Dogecoin and be sure to put the zipped files there when you download them, but the commands will be the same otherwise.
cwayne18 put in the work to make a PPA for the QT client here.
Ubunutu/Mint/Debian users should be able to install the client with the following commands:
sudo add-apt-repository ppa:cwayne18/doge sudo apt-get update && sudo apt-get install dogecoin-qt 
To update using this method, run
sudo apt-get update && sudo apt-get upgrade dogecoin-qt 
Compiling the Wallet Manually
I suggest using the PPA above, but if you want to compile manually, here you go.
1)Download the newest source from here. If you want to check out the Github page, click here
2)Unzip the package with the native client OR, navigate to your downloads and unzip
cd ~/Downloads unzip 
3)Now it's time to compile. You will need to install the dependencies, just copy and paste the following code. It will be a fairly large download and could take some time. It is always important to update before installing any new software, so we'll do that first and then install the dependencies.
sudo apt-get update sudo apt-get upgrade sudo apt-get install libssl-dev libdb-dev libdb++-dev libqrencode-dev qt4-qmake libqtgui4 libqt4-dev sudo apt-get install libminiupnpc-dev libminiupnpc8 libboost-all-dev build-essential git libboost1.53-all-dev 
4)Once that is done, go to the doge-coin master directory and compile:
cd ~/Downloads/dogecoin-maste sed -i 's/-mgw46-mt-sd-1_53//g' qmake USE_UPNP=- USE_QRCODE=0 USE_IPV6=0 make -j3 
After running the qmake command you will likely see some text similar to
Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target language has less forms. If this sounds wrong, possibly the target language is not set or recognized. 
It's perfectly normal, so don't worry about that.
Your Dogewallet is ready to go! The executable is in ~/Downloads/dogecoin-maste and called dogecoin-qt. Your wallet information is in ~/.dogecoin. You can run the wallet at any time by opening terminal and typing
cd ~/Downloads/dogecoin-maste ./dogecoin-qt 
Future upgrades to dogewallet are easy. Back up your wallet.dat, and simply follow the same directions above, but you'll be unzipping and building the newer version. You will likely need to rename the old dogecoin-master directory in ~/Downloads before unzipping the newest version and building. Also, it is likely that you will not need to install the dependencies again.
Alternate Method For Installing Dogecoin Wallet from Nicebreakfast
After installing the dependencies listed in step 3, open terminal, then navigate to where you want Dogecoin Wallet stored and run:
git clone ./ ./configure make 
then when the wallet is updated just run
git pull 
from the dogecoin directory.
GPU Mining
GPU mining requires CGminer. My suggestion is to get the executable already built. The creator of cgminer has removed the built file from his website, but I've uploaded it here
sudo apt-get install pkg-config opencl-dev libcurl4-openssl-dev autoconf libtool automake m4 ncurses-dev cd ~/Downloads tar -xvf cgminer-3.7.2-x86_64-built.tar.bz2 
Don't use anything newer than 3.7.2. The newer versions of CGMiner don't support GPU mining.
That's it! You have cgminer ready to go! You will run cgminer with the following syntax
cd ~/Downloads/cgminer-3.7.2-x86_64-built/ ./cgminer --scrypt -o stratum+tcp://SERVERNAME:PORT -u WORKER.ID -p PASS 
A good guide for fine tuning cgminer can be found here; follow the litecoin example.
I had trouble getting cgminer running with a single line command, but running it via an executable .sh file works. This is covered in the cgminer setup guide I posted above but I'll put it here too. In the same directory that has the cgminer executable, you need to make a file called and make it executable. It should contain the follwing:
export GPU_USE_SYNC_OBJECTS=1 export GPU_MAX_ALLOC_PERCENT=100 export DISPLAY=:0 find *.bin -delete sleep 5 ./cgminer 
Then you can call cgminer in terminal by doing ./ You will need a cgminer.conf file containing all your options. All of this is covered in the guide that is linked above.
A quick note about AMD drivers: They used to be a huge PITA to install and get working, but the newest Catalyst drivers are great. There's a GUI installer, everything works out of the box, and there is a lot of documentation. You can download them here: AMD Catalyst 14.6 Beta Linux
CPU Mining
For CPU mining I use minerd because it doesn't require any work to get running, simply download it and get to work. Download the built file for your machine 32-bit or 64-bit, and then unzip it and you're ready to go!
cd ~/Downloads tar -xvf pooler-cpuminer-2.3.2-linux-x86.tar.gz 
The executable is called minerd and it will be in ~/Downloads but you can move it to wherever you like. To run it, pull up terminal and do
cd ~/Downloads minerd --url=stratum+tcp://SERVER:PORT --userpass=USERNAME.WORKERNAME:WORKERPASSWORD 
You're done! Happy mining!
Common Issues
I ran into this and I've seen others with this problem as well. Everything installs fine but there is a shared library file that isn't where it should be. In fact, it isn't there at all. cannot open shared object file: No such file or directory 
In terminal, do
sudo updatedb locate 
And it will probably return a path /lib/x86_64-linux-gnu. Inside that directory there's a library file called You'll need to make a symlink (aka shortcut) that links to So, assuming you're working with do this
cd /lib/x86_64-linux-gnu sudo ln -s 
Now if you do
ln -l 
You should see -> ./ 
Meaning you've made the symlink. Also, the text for will be blue.
submitted by Boozybrain to dogecoin [link] [comments]

Subreddit Stats: PowerShell top posts from 2016-09-13 to 2017-09-12 15:08 PDT

Period: 363.81 days
Submissions Comments
Total 1000 13381
Rate (per day) 2.75 36.66
Unique Redditors 594 2754
Combined Score 34214 35206

Top Submitters' Top Submissions

  1. 1085 points, 28 submissions: Prateeksingh1590
    1. Powershell Cheat Sheet Compilation (177 points, 15 comments)
    2. Get-Weather report using Powershell (78 points, 20 comments)
    3. Plot Graph in Powershell console (68 points, 9 comments)
    4. Powershell : Find-UnsecureWifiConnection’s Nearby (57 points, 7 comments)
    5. Powershell Auto Mute, when headphones are accidently unplugged. (54 points, 5 comments)
    6. PowerShell : Get MP3/MP4 File’s MetaData and How to use it to make your Life easy (53 points, 2 comments)
    7. Scrolling Internet Explorer with Powershell (52 points, 2 comments)
    8. Get-Nutrient composition of Food Items using Powershell (47 points, 7 comments)
    9. Get-Summary of a Text document using PowerShell (43 points, 4 comments)
    10. PowerShell ranks 18 in RedMonk Programming Language Rankings (34 points, 11 comments)
  2. 777 points, 8 submissions: daviwil
    1. Just released v0.10.0 of the PowerShell extension for Visual Studio Code with an integrated console experience like the ISE! (166 points, 47 comments)
    2. Announcing PowerShell for Visual Studio Code 1.0! (124 points, 25 comments)
    3. Just released #PowerShell for VS @Code v0.12.0 with a bunch of fixes and improvements! (115 points, 48 comments)
    4. Just released PowerShell for VS Code v1.3.0 with CodeLens support for Pester tests and function references! (88 points, 8 comments)
    5. Just released v1.2.0 of PowerShell for VS Code with improvements for PSScriptAnalyzer and dynamic help snippets! (86 points, 29 comments)
    6. Just released PowerShell for Visual Studio Code 1.1.0 with a cool new feature: dynamic snippets for comment-based help! (77 points, 22 comments)
    7. Just released PowerShell for VS Code 1.4.0 with new code formatting presets and custom HTML content view APIs! (73 points, 17 comments)
    8. Check out new improvements to the integrated console and debugging experience in 0.11.0 of PowerShell for VS Code (48 points, 21 comments)
  3. 713 points, 18 submissions: markekraus
    1. Flat Is Justice! Flatter Code for PowerShell (77 points, 51 comments)
    2. Bye Bye Backtick: Natural Line Continuations in PowerShell (Get-PowerShellBlog markekraus) (73 points, 45 comments)
    3. PowerShell Fun for the Holidays! (73 points, 15 comments)
    4. PSRAW (PowerShell Reddit API Wrapper) 2.0 Released (51 points, 4 comments)
    5. Let’s Kill Write-Output (Get-PowerShellBlog markekraus) (49 points, 53 comments)
    6. TIFU By Breaking the PowerShell Core Nightly Build For the 2nd Time this Month (49 points, 14 comments)
    7. PowerShell GUI for Viewing/Exporting Dynamic Distribution List Members on Office 365 (41 points, 2 comments)
    8. If PowerShell Were School, I would Ditch Classes Regularly (39 points, 25 comments)
    9. Write The FAQ 'N Manual: Automated Documentation in a CI/CD Pipeline for PowerShell Modules with PlatyPS, psake, AppVeyor, GitHub and ReadTheDocs (markekraus Get-PowerShellBlog) (39 points, 13 comments)
    10. PSRAW: PowerShell Reddit API Wrapper Module - Core Functionality Release - v1.1.0.5 (36 points, 9 comments)
  4. 685 points, 13 submissions: rschiefer
    1. Learn Powershell in 5 Painless Steps - Storage (152 points, 13 comments)
    2. Slow Code: Top 5 Ways to Make Your PowerShell Scripts Run Faster (128 points, 25 comments)
    3. A Practical Guide for Using Regex in PowerShell (90 points, 10 comments)
    4. High Performance PowerShell with LINQ (56 points, 18 comments)
    5. Release v6.0.0-alpha.11 release of PowerShell (54 points, 11 comments)
    6. Hitchhikers Guide to the PowerShell Module Pipeline (41 points, 2 comments)
    7. How to create a Nano Server Image using PowerShell (34 points, 0 comments)
    8. Introducing Reverse DSC – Nik Charlebois (25 points, 4 comments)
    9. Nano Server with, Hyper-V AND Pester (24 points, 1 comment)
    10. PowerShell Magazine » ForEach and Where magic methods (22 points, 4 comments)
  5. 613 points, 3 submissions: nepronen
    1. Free Online PowerShell GUI Designer (503 points, 121 comments)
    2. Free Online PowerShell GUI Designer REPOST /PowerShell (81 points, 14 comments)
    3. Would you use a free simple WPF designer for PowerShell? (29 points, 11 comments)
  6. 600 points, 17 submissions: KevMar
    1. Everything you wanted to know about hashtables (73 points, 27 comments)
    2. Powershell: Everything you wanted to know about PSCustomObject (58 points, 25 comments)
    3. Kevmar: All .Net 4.6 Exceptions List for use with Powershell (57 points, 12 comments)
    4. KevMar on Powershell: The many ways to use regex (52 points, 19 comments)
    5. PowerShell + DevOps Global Summit 2017 - YouTube (41 points, 12 comments)
    6. KevMar: The many ways to read and write to files (39 points, 23 comments)
    7. KevMar: Let's build the CI/CD pipeline for a new module (37 points, 11 comments)
    8. KevMar: Building a Module, one microstep at a time (33 points, 18 comments)
    9. Kevmar: Remote install software (33 points, 11 comments)
    10. @ATXPowershell user group on Thur: General admin problems and how to solve them (29 points, 8 comments)
  7. 518 points, 11 submissions: l33t_d0nut
    1. Introducing PowerShell Pro Tools Universal Dashboard - Cross-platform, web-based dashboards (114 points, 29 comments)
    2. ConvertTo-PowerShell and ConvertTo-CSharp cmdlets now available in PowerShell Pro Tools module (85 points, 7 comments)
    3. PSPack.exe - Package PowerShell Script in an Executable (78 points, 22 comments)
    4. View as PowerShell - Chrome extension to convert C# to PowerShell (61 points, 3 comments)
    5. Converting C# to PowerShell using Roslyn (46 points, 13 comments)
    6. PowerShell Pro Tools for Visual Studio 2017 - Psst Form Designer (40 points, 3 comments)
    7. Converting PowerShell to C# through intent instead of an abstract syntax tree alone (26 points, 1 comment)
    8. Building WPF Windows with PowerShell in Visual Studio (19 points, 2 comments)
    9. Building Windows Forms with PowerShell in Visual Studio 2017 (18 points, 0 comments)
    10. PowerShell Tools for VS - May Release Notes (16 points, 3 comments)
  8. 483 points, 15 submissions: Net-Runner
    1. How To Create Progress Bars in PowerShell (118 points, 12 comments)
    2. Microsoft Transitioning Windows PowerShell 6.0 into PowerShell Core (47 points, 10 comments)
    3. How to Version and Publish a PowerShell Module to GitHub and PSGallery with AppVeyor (42 points, 0 comments)
    4. Managing Owners of Files and Folders with PowerShell (33 points, 4 comments)
    5. How to upload Custom Images to Microsoft Azure using PowerShell (29 points, 0 comments)
    6. Working with Arrays in PowerShell (28 points, 12 comments)
    7. Get Windows 10 digital license with Powershell (26 points, 7 comments)
    8. PowerShell Script to Load Balance DNS Server Search Order (25 points, 3 comments)
    9. PowerShell – where, .where or Where? (24 points, 6 comments)
    10. How To Grep in PowerShell (23 points, 43 comments)
  9. 473 points, 16 submissions: fourierswager
    1. In light of PowerShell Core, what's your plan for refactoring old stuff and writing new stuff? (57 points, 44 comments)
    2. WinRM-Environment Module - Make your remote PSSession environment the same as your local session. Plus the ability to edit files within the PowerShell console. (50 points, 7 comments)
    3. Start-SudoSession - Sudo for PowerShell written in 100% PowerShell! (42 points, 14 comments)
    4. Register-FileIOWatcher - function to montior one or more files and/or subdirectories for changes. (38 points, 5 comments)
    5. Get-UserSessionEx - Get all user session info in one place...for real though. (36 points, 5 comments)
    6. ManageLocalUsersAndGroups Module Significant Update: Now capable of managing local users and groups on Remote Hosts on different domains (or not on a domain at all) (36 points, 2 comments)
    7. Vi/Nano for PowerShell? (35 points, 30 comments)
    8. Start-PSLogging - Capture logs for ALL PowerShell activity on a system. (32 points, 7 comments)
    9. Replace-Text powerful, easy-to-use function. (24 points, 3 comments)
    10. EncryptDecrypt Module - Hybrid RSA/AES Encryption solution with PowerShell. Please use responsibly. (22 points, 1 comment)
  10. 439 points, 11 submissions: PowerShellChallenge
    1. Installing latest PowerShell Core 6.0 Release on Linux just got easier! (69 points, 14 comments)
    2. Windows Management Framework (WMF) 5.1 now in Microsoft Update Catalog (60 points, 3 comments)
    3. PSSwagger – Automatically generate PowerShell cmdlets from OpenAPI (f.k.a Swagger) specification (56 points, 2 comments)
    4. PowerShell 6.0 Roadmap: CoreCLR, Backwards Compatibility, and More! (53 points, 9 comments)
    5. Join the PowerShell 10th Anniversary Celebration! (48 points, 2 comments)
    6. OpenSSH Security Testing Kick Off (47 points, 1 comment)
    7. PowerShell Open Source Community Dashboard (24 points, 1 comment)
    8. Managing Security Settings on Nano Server with DSC (23 points, 3 comments)
    9. Windows PowerShell 2.0 Deprecation (21 points, 4 comments)
    10. Code Coverage – Part 2 (19 points, 0 comments)
  11. 417 points, 6 submissions: thebeersgoodnbelgium
    1. dbatools - an open source project, now with over 100 PowerShell commands for DBAs. Here's our most recent release! • /SQLServer (123 points, 1 comment)
    2. I'm presenting tomorrow! PowerShell ❤ SQL Server: Modern Database Administration with dbatools & dbareports (83 points, 12 comments)
    3. Official SqlServer module now in the PowerShell Gallery! (83 points, 16 comments)
    4. If all goes well, the SQL Server module will be in the PowerShell Gallery in the next month! (80 points, 25 comments)
    5. we just added 63 commands to a beta dbatools release - help us test, please? :D (27 points, 8 comments)
    6. Rejoice! dbatools now helps with SPN management: Get-DbaSpn, Set-DbaSpn, Test-DbaSpn & Remove-DbaSpn • /SQLServer (21 points, 0 comments)
  12. 414 points, 13 submissions: ramblingcookiemonste
    1. What have you done with PowerShell this month? July 2017 (53 points, 83 comments)
    2. What have you done with PowerShell this month? March 2017 (51 points, 69 comments)
    3. What have you done with PowerShell this month? June 2017 (41 points, 84 comments)
    4. What have you done with PowerShell this month? April 2017 (40 points, 46 comments)
    5. What have you done with PowerShell this month? January 2017 (33 points, 54 comments)
    6. What have you done with PowerShell this month? November 2016 (33 points, 51 comments)
    7. 2016 Retrospection: What have you done with PowerShell this year? (31 points, 25 comments)
    8. What have you done with PowerShell this month? October 2016 (27 points, 68 comments)
    9. What have you done with PowerShell this month? August 2017 (25 points, 45 comments)
    10. What have you done with PowerShell this month? September 2016 (24 points, 40 comments)
  13. 408 points, 8 submissions: oze4
    1. Install a Powershell Script .ps1 as a Windows Service! GUI that allows you to install and run a Powershell script as a Windows Service! (With example .ps1 you can run as a service) (129 points, 50 comments)
    2. Run PowerShell Script (.ps1) as a Windows Service! (88 points, 49 comments)
    3. GUI Tool For Enabling/Disabling AD Accounts & Reset PWs! (59 points, 40 comments)
    4. Custom "Windows Explorer" for Powershell GUI scripts (51 points, 3 comments)
    5. Is there a way to tell when windows is at the login screen after boot via power shell? (23 points, 11 comments)
    6. How to install a PowerShell script as a Windows Service. GUI Edition! ~PaaWS: PowerShell as a Windows Service~ with bonus uninstaller (20 points, 6 comments)
    7. Get permissions for specific Active Directory user - even if they are in a Group! (19 points, 0 comments)
    8. Log your pings! (19 points, 18 comments)
  14. 402 points, 9 submissions: happysysadm
    1. A PowerShell function to rapidly gather system events for sysadmin eyes only with some tips (92 points, 24 comments)
    2. Is WinRM Secure or do I need HTTPs? (63 points, 7 comments)
    3. Getting weather data with PowerShell and other funny things you can do in just a line of code (59 points, 0 comments)
    4. Ramp up your PowerShell knowledge in 2017 with these books (52 points, 8 comments)
    5. Announcing the winner of the PowerShell Oneliner Contest 2016 (43 points, 10 comments)
    6. The new way to check computer information with PowerShell and WMF 5.1 (30 points, 15 comments)
    7. Do you think you know PowerShell? Code Golf - Find Next Palindrome Number (26 points, 6 comments)
    8. Using the PoshRSJob module with a PowerShell function to perform a WinRM check up (20 points, 0 comments)
    9. All the 7 principles of the LEAN methodology in a single line of PowerShell code (17 points, 21 comments)
  15. 367 points, 4 submissions: mikefrobbins
    1. How to install Visual Studio Code and configure it as a replacement for the PowerShell ISE (144 points, 44 comments)
    2. Announcing a new book: PowerShell 101 – The No-Nonsense Beginner’s Guide to PowerShell (106 points, 3 comments)
    3. Use PowerShell to Determine if Specific Windows Updates are Installed on Remote Servers (78 points, 18 comments)
    4. PowerShell One-Liner to Disable Active Directory Accounts and Log the Results to a SQL Server Database (39 points, 6 comments)
  16. 331 points, 7 submissions: signalwarrant
    1. PowerShell Desired State Configuration (DSC) How-To for Beginners (Pull Mode) (87 points, 7 comments)
    2. Hey PowerShell... Text me when the Domain Admins Group changes. (75 points, 13 comments)
    3. Fellow PowerShell wizards... You need version control in your life. (43 points, 11 comments)
    4. Create an HTML report of Active Directory Forest Information with PowerShell (42 points, 4 comments)
    5. PowerShell Desired State Configuration (DSC) How-To for Beginners (Push Model) (39 points, 3 comments)
    6. Automate Creating Lab Virtual Machines in Azure with PowerShell (26 points, 3 comments)
    7. Convert text files to PDF then merge PDFs in bulk with PowerShell and iTextSharp (19 points, 6 comments)
  17. 324 points, 6 submissions: ColeMcDonald
    1. Learn Powershell in 5 Painless Steps: 4 - Loops (87 points, 11 comments)
    2. Learn Powershell in 5 Painless Steps - Part 3: Input (63 points, 2 comments)
    3. Learn Powershell in 5 Painless Steps: Data - Classes and Storage (63 points, 4 comments)
    4. Here's the second step on our journey to world domination through scripting. (40 points, 12 comments)
    5. Learn Powershell in 5 Painless Steps - 5 - Decisions (40 points, 6 comments)
    6. Learn Powershell in 5 Painless Steps: Data - 3.Movement... This week, classes and methods move around in another dimension... or something like that. (31 points, 0 comments)
  18. 265 points, 6 submissions: jerdub1993
    1. PowerShell for beginners video training course as taught by its inventor, Jeffery Snover. (145 points, 8 comments)
    2. Change all AD usernames to firstname.lastname and rename home directory. (34 points, 13 comments)
    3. Query IMDB for movies and information. (32 points, 10 comments)
    4. Is it possible to use PowerShell to get information from an online account if you provide the credentials? (ie: Facebook, email, Reddit inbox?) (24 points, 12 comments)
    5. Help piping multiple values by property name? (15 points, 14 comments)
    6. Is it possible to test a command without running it? (15 points, 11 comments)
  19. 259 points, 3 submissions: nickrod518
    1. Never too busy to have fun... send cat facts to coworker's PC's using PowerShell (183 points, 20 comments)
    2. Migrate Windows user profile(s) from one computer to another or to an archive (57 points, 20 comments)
    3. Create a price chart of Bitcoin from the last 30 days (19 points, 7 comments)
  20. 242 points, 2 submissions: blownart
    1. 10 Free PowerShell e-books (187 points, 16 comments)
    2. PowerShell 10 Year Anniversary (55 points, 9 comments)
  21. 230 points, 1 submission: bigbirdtoejam
    1. Using powershell for office pranks (230 points, 86 comments)
  22. 215 points, 5 submissions: kabanossi
    1. Learn basics of PowerShell & PowerCLI under 1.5 hours (76 points, 2 comments)
    2. The Top 3 Features in Visual Studio Code for PowerShell Folks (74 points, 20 comments)
    3. Powershell Script to Get ESXi Datastore Path Information (27 points, 4 comments)
    4. vCenter Cluster Performance Tool (21 points, 0 comments)
    5. Making sure your Citrix Desktops are utilized in 35 lines of PoSH (17 points, 0 comments)
  23. 214 points, 1 submission: pmd006
    1. Not what I expected (214 points, 33 comments)
  24. 213 points, 6 submissions: 1RedOne
    1. Extracting and monitoring web content with PowerShell (45 points, 19 comments)
    2. POWERSHELL DECONSTRUCTED - A deep dive into how binary modules work (44 points, 20 comments)
    3. SOLVED: What happens to WINRM when certs die (37 points, 19 comments)
    4. Adding tab-completion to your PowerShell Functions (36 points, 15 comments)
    5. Advanced Autocompletion - Part II (30 points, 16 comments)
    6. Building a DSC Design application with PowerShell (21 points, 8 comments)
  25. 183 points, 4 submissions: AdminArsenal
    1. Happy Star Wars Day, /PowerShell (77 points, 2 comments)
    2. Creating a Hipster Playlist Using PowerShell (42 points, 4 comments)
    3. Anyone looking for a full-time PowerShell position? (39 points, 55 comments)
    4. Determining Disk Type with Get-PhysicalDisk (25 points, 3 comments)

Top Commenters

  1. markekraus (1517 points, 465 comments)
  2. Lee_Dailey (1044 points, 590 comments)
  3. KevMar (899 points, 297 comments)
  4. ihaxr (404 points, 84 comments)
  5. daviwil (287 points, 75 comments)
  6. spyingwind (285 points, 94 comments)
  7. Sheppard_Ra (277 points, 103 comments)
  8. ka-splam (265 points, 85 comments)
  9. JBear_Alpha (255 points, 102 comments)
  10. jheinikel (254 points, 62 comments)
  11. SeeminglyScience (230 points, 74 comments)
  12. SaladProblems (222 points, 92 comments)
  13. Swarfega (207 points, 64 comments)
  14. OathOfFeanor (198 points, 71 comments)
  15. Snak3d0c (191 points, 110 comments)
  16. root-node (188 points, 66 comments)
  17. evetsleep (188 points, 59 comments)
  18. gangstanthony (188 points, 55 comments)
  19. ramblingcookiemonste (165 points, 29 comments)
  20. fourierswager (161 points, 75 comments)
  21. creamersrealm (158 points, 70 comments)
  22. itmonkey78 (154 points, 38 comments)
  23. artvandelay440 (151 points, 62 comments)
  24. 1RedOne (150 points, 60 comments)
  25. nepronen (148 points, 39 comments)
  26. the_spad (148 points, 33 comments)
  27. Ominusx (139 points, 38 comments)
  28. omers (139 points, 38 comments)
  29. oze4 (135 points, 74 comments)
  30. Old-Lost (132 points, 41 comments)
  31. halbaradkenafin (127 points, 38 comments)
  32. alinroc (127 points, 19 comments)
  33. cml0401 (126 points, 41 comments)
  34. icklicksick (125 points, 45 comments)
  35. KnifeyGavin (124 points, 42 comments)
  36. michaeltlombardi (120 points, 63 comments)
  37. aXenoWhat (119 points, 48 comments)
  38. toregroneng (117 points, 36 comments)
  39. pertymoose (112 points, 35 comments)
  40. _Unas_ (109 points, 39 comments)
  41. suddenarborealstop (107 points, 40 comments)
  42. allywilson (103 points, 41 comments)
  43. Flyboy (98 points, 13 comments)
  44. cofonseca (97 points, 39 comments)
  45. lordv0ldemort (94 points, 35 comments)
  46. NathanielArnoldR2 (87 points, 31 comments)
  47. chreestopher2 (85 points, 38 comments)
  48. steviecoaster (85 points, 34 comments)
  49. yeah_i_got_skills (85 points, 19 comments)
  50. Emiroda (84 points, 30 comments)

Top Submissions

  1. Free Online PowerShell GUI Designer by nepronen (503 points, 121 comments)
  2. Using powershell for office pranks by bigbirdtoejam (230 points, 86 comments)
  3. Not what I expected by pmd006 (214 points, 33 comments)
  4. 10 Free PowerShell e-books by blownart (187 points, 16 comments)
  5. Announcing the PowerShell Module Browser by tr4p (183 points, 30 comments)
  6. Never too busy to have fun... send cat facts to coworker's PC's using PowerShell by nickrod518 (183 points, 20 comments)
  7. Powershell Cheat Sheet Compilation by Prateeksingh1590 (177 points, 15 comments)
  8. Just released v0.10.0 of the PowerShell extension for Visual Studio Code with an integrated console experience like the ISE! by daviwil (166 points, 47 comments)
  9. Learn Powershell in 5 Painless Steps - Storage by rschiefer (152 points, 13 comments)
  10. Would anyone here like to see content related to Active Directory? by deleted (150 points, 28 comments)

Top Comments

  1. 78 points: screamingpackets's comment in Are there any free alternatives to using Powershell ISE?
  2. 53 points: GenghisChaim's comment in Windows 10 Hardening Via Powershell
  3. 49 points: Alliwantispcb's comment in Using powershell for office pranks
  4. 47 points: scabby_al's comment in Vote to petition native PowerShell support in Microsoft Excel - PowerShell Macros!
  5. 46 points: dbussanich's comment in Does anyone have a job where they only write powershell scripts?
  6. 42 points: nepronen's comment in Free Online PowerShell GUI Designer
  7. 40 points: deleted's comment in PowerShell for private purposes?
  8. 38 points: bukem's comment in $MyInvocation annoys me. What is a foolproof, reliable way to get path of currently run script?
  9. 36 points: Quicknoob's comment in Top 10 powershell scripts you use
  10. 36 points: gdhhorn's comment in Is it possible to test a command without running it?
Generated with BBoe's Subreddit Stats (Donate)
submitted by subreddit_stats to subreddit_stats [link] [comments]


The first ever PIVX rebranded v. wallet has been released. Compiled wallet binaries for various OS should be put up in the repo link below.
If you have an existing wallet, you MUST rename the following 2 items 'BEFORE' you start the new wallet as the foldefile naming has changed.
  1. Shut down the wallet gracefully either via CLI or via wallet GUI.
  2. For linux users, hidden directory ".darknet" needs to be renamed to ".pivx".
  3. For Windows users, similar will need to be done to your wallet.dat directory. (usually located in %APPDATA%)
  4. For everyone, "darknet.conf" needs to be renamed to "pivx.conf".
  5. Replace the wallet binaries with the updated v2.1.4.0 binaries.
  6. Start the wallet!
For Windows users: I personally recommend Windows wallet users to specify the wallet.dat directory via a shortcut method. Basically create a shortcut the qt executable and append the -datadir= and specify a folder you created.
e.g. C:\Coins\PIVX\pivx-qt.exe -datadir=C:\Coins\PIVX\blockchain
Then the wallet and chain/dat/conf files will all be within a single folder instead of it going to %APPDATA%. This trick works for pretty much every coin under the sun btw. (bitcoin, litecoin, whatever coin etc etc) P.S. If you have an existing wallet.dat & conf files, you'll need to move them to the new -datadir folder.
this post was originally made by JAKIMAN on Bitcointalk forums here :
submitted by cryptosi to pivx [link] [comments]

Rename root folder name Class 5Rename,Delete,Restore and Copying A File And FolderBy:- Himanshu Sir How to Copy, Move and Rename Files in UNIX or Linux ? Copy, Move, Rename Files and Folders - Linux CLI Linux - Make, Rename, Move, Delete Folders (mkdir, mv, cp, rm)

A note about rename command. Many Linux distros have rename command that will rename the specified files by replacing the first occurrence of an expression in their name by replacement. For example, the following command would fix extension of your pl files. In other words, rename all *.perl to *.pl file: Begin by renaming the Bitcoin Core data directory. Use the name bitcoin-backup. Don’t move the renamed folder. This allows recovery of the original data directory in case something goes wrong. To recover the original, reinstate the original name of the bitcoin-backup folder (either Bitcoin or .bitcoin). I am a new Linux system user. How do I rename a folder on Linux operating system using the command line? How can I rename a directory via the bash command line option? You need to use the mv command to rename and move files and directories/folders. Everything is a file under Linux or Unix-like […] How to rename multiple folders in Linux. To rename multiple folders, one can use rename command from MariaDB/MySQL or Linux utilities package. Another option is to use the bash for loop. Linux rename multiple folders using rename command. The syntax is: rename expression replacement file. rename command examples. Let us see some examples. Please contemplate donating cash to the nixCraft by way of PayPal/Bitcoin, or develop into a supporter utilizing Patreon. Find out how to rename a number of folders in Linux. To rename a number of folders, one can use rename command from MariaDB/MySQL or Linux utilities package deal.Another choice is to make use of the bash for loop.

[index] [1871] [6573] [4949] [471] [549] [10010] [27] [4881] [1514] [1667]

Rename root folder name

Rename root folder name Linux Copy,Move & Rename Files Tutorials Point (India) Ltd. Loading... Unsubscribe from Tutorials Point (India) Ltd.? Cancel Unsubscribe. Working... Subscribe Subscribed Unsubscribe 1.63M. ... Find code and diagrams at: Managing folders is much like managing files in Linux. Just remember to use the -r option (recursive) for copying and deleting. How to Copy, Move and Rename Files in UNIX or Linux ? Part 1 of 3 Copy files - the 'cp' command cp source target ( File to File ) cp file1 file11 cp source destination ( File to Directory ) cp ... Linux/Mac Terminal Tutorial: Create, Copy, Move, Rename and Delete Files and Directories - Duration: 11:41. Corey Schafer 98,727 views