uname -a output:
Linux scallion 4.9.0-kali4-amd64 #1 SMP Debian 4.9.30-2kali1 (2017-06-22) x86_64 GNU/Linux

Bash version output:
GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)

Greetings, I've been trying to add a ppa repository so that I can install WoeUSB. I keep running into this error:

This is the command:
sudo add-apt-repository ppa:nilarimogard/webupd8

This is the error message:
/usr/sbin/add-apt-repository: 1: /usr/sbin/add-apt-repository: Syntax error: redirection unexpected

This has been occurring for any and all ppa repos that I've tried to add. I believe I have all the dependencies installed. Can't figure out what is wrong with the syntax of the command. Any help appreciated. Thanks.

PPAs are for the Ubuntu family. Kali is based directly on Debian so doesn't support them. There *are* workarounds available which allow some PPAs to be installed - you should search on the web for these and for the exact error message you received. If this doesn't work for WoeUSB, then just download and install a deb package version of WoeUSB. Searching the web for Kali WoeUSB will give you lots of pointers.

Did you see this thread at the Kali forums?

Yes, thanks, but I've scraped all the searches and forums and tried many different possible solutions to no avail. Now my kali install won't boot into gui and mariadb-server and ruby-CMS-scanner are broken and system won't boot into gui

I broke the system after I created a win10 bootable disk using Rufus from within a VMware virtual Win10 environment and subsequently tried to use the disk to boot into a windows environment. Ultimately I'm trying to fix my windows 10 install which is primary to a dual boot w/ kali

I should point out that Kali is a specialised distro aimed at pen testing experts. Given the experience that you're having, I would recommend that you choose another friendlier distro to cut your Linux teeth on unless there is some abiding reason that you need to use Kali.

see https://www.linuxquestions.org/quest...ad-4175614092/

So, is the current situation that your Windows 10 install is broken on a dual-boot system? If so, I would recommend also that you hit the Windows forums to solve the issue and forget Linux for the moment. Once you've got the Windows side of things working again, come back and we'll give you some advice on how to proceed.

Yes I'm well aware of the use of Kali Linux for penetration testing. I've been using it for a couple of years now learning the tools and testing penetration techniques for ethical hacking. Now I understand the issue about dual booting from a primarily Windows machine. My issue is this, I broke my windows install and I'm using my Linux install in order to fix my windows OS. In doing so I inadvertently broke my Linux install by using USB drive that I created from within my Linux install and attempting to boot from said disc. I've had this issue before during the time when I was going through the hell of setting up my dual boot system. I've merely forgotten what I did to fix the problem. Appreciate any help.
I believe the problem is associated with the grub in that I think the grub was destroyed buy whatever boot process that didn't take when when I tempted to use the faulty boot disk.
The the symptoms of the problem include not being able to perform an update from the terminal, yet I'm still able to Ping various IP addresses such as Google 8. 8. 8. 8
Maria DB server and Ruby CMS scanner are showing that they are not installed producing dpkg dependency problem errors.

SystemRescueCD can repair a lot of bootup/Grub issues.

However, if your Grub is faulty, how are you able to boot up into Kali to use the terminal? Also, Grub shouldn't affect in any way your ability to update from the terminal etc.

Just trying to understand...

Good news guys I was able to fix my Linux install, the issue was something with the DNS processing. I purged all services that refers to DNS information + reset the network manager service, now full connectivity restored to my Linux install. Great. Now the issue is back to the original problem which was that my Windows 10 install is not bootable. This problem, I believe is due to issues with the Windows boot sector, or window side grub. I could be wrong, but as usual, the Enigma that is Windows is full of Black Box Mysteries that I'll now have to refer to the windows Geeks for help. I'm well aware that this is a Linux forum. I appreciate the input I receive from you guys and I hope to be able to also contribute to resolving Linux issues for less fortunate users in the future. I won't refuse any knowledgeable help in resolving this Windows issue as well. The damn thing just stays stuck after going to that automatic repair thingy.

Getting there. Do note that repairing the Windows install may well entail you having to throw SystemRescueCD at it afterwards in order to able to boot into the Linux side of things, so it would be useful to create a boot media with that ISO on it at some point.

Sorry guys I have just given up. I no longer using the Linux system to try to fix a Windows system while cohabiting the same machine. I've since found a Windows 8 PC with a very large monitor and it's a desktop and I'm rocking and rolling now. Got the Windows media creation tool doing its thing right now.