@dustinb3403 ok got it, weird one

The deployment guide can be found here.

@fateknollogee Super Jeally

Go figure...CentOS-7 UEFI vm on Windows Server 2019 "Preview" w Hyper-V installs no problem!!!

@stacksofplates said in Newb question - Running a script from the root directory: @dustinb3403 said in Newb question - Running a script from the root directory: @stacksofplates said in Newb question - Running a script from the root directory: @dustinb3403 said in Newb question - Running a script from the root directory: @stacksofplates said in Newb question - Running a script from the root directory: @dustinb3403 said in Newb question - Running a script from the root directory: @stacksofplates said in Newb question - Running a script from the root directory: @dustinb3403 said in Newb question - Running a script from the root directory: @scottalanmiller said in Newb question - Running a script from the root directory: @dustinb3403 said in Newb question - Running a script from the root directory: @stacksofplates said in Newb question - Running a script from the root directory: @dustinb3403 said in Newb question - Running a script from the root directory: @danp said in Newb question - Running a script from the root directory: Is the directory in your path? What do you get from echo $PATH? echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/root/opt/scripts/:/root/opt/scripts I've added it (twice). Well first off you had /root/opt/scripts not /opt/scripts. Second you either have to log out and back in or tell your user to use the new path with something like source ~/.bash_profile I used ````~/opt/scripts``` initially, as I wasn't aware of just adding my scripts into one of the existing locations. (everything said just add a new directory). By simply moving the script into an already existing path, I am able to update with just "script.sh". When you are root and your home is /root and you put ~/opt/scripts that is /root/opt/scripts. Remember that ~ is a shortcut to your home directory, which is /root So by adding ```/opt/scripts/```` this would've worked, but would've added complexity for no reason. No that still isn’t a default location. In the OP you said you put the script in /opt/scripts. Where did you actually put it? Originally I created the directory /opt/scripts and put the script in there so the Directory looks like /opt/scripts/script.sh I went back and change the script location to be in /usr/local/bin So in /usr/local/bin I now have script.sh This now works without issue, and /opt/scripts no longer exists. Ok ya that’s where the problem was. /opt/scripts is different than /root/opt/scripts. If you would have had that in your .bashrc or .bash_profile (or whichever shellconfigure you’re using) it would have worked. But you still have to let the user know of the PATH change. I'm the user in this case, but I never really create / save my own scripts. I just got tired of running a set of commands, every other day. Thus the need to figure out how I could run the script, without having to jump into the exact directory from which the script was saved. I mean you have to let the user you are logged in as Know if the change. Either by logging out and back in or by temporarily sourcing the config. I've logged out, what do you mean "sourcing the config" ? If you change your PATH while you’re logged on the user account doesn’t know of that change. You have to either log out and log in again or temporarily do something like source ~/.bashrc Or the non-aliased version... . ~/.bashrc

@bnrstnr said in Centos 7 Minimal Install: Is there ever a reason to go with one of the other security policies for centOS? Depends where you work, usually this is set for government standards for example: https://en.wikipedia.org/wiki/Federal_Information_Processing_Standards So theoretically if you work for the Government agency they will require you to choose certain protocols, and those profiles will make your life easier.

Start with old Desktop with Virtualization extension, something that you can install OS and dont have to remove cause of free space or you need it for something else. Cause learning Linux or Centos or anything else needs environment, and virtualbox can work but it wont allow you play with KVM, and thats for me the big part of the fun. Also you need to keep learning that means its is process some day you will leave it 4-5 days dormat cause your stuck in an issue the other day bulb lights up mainly due to reading this site and you get back on it.

Added "Where to start?" here https://mangolassi.it/topic/13584/where-to-start

@DustinB3403 said in CentOS rsync between servers using keyfile to pass credentials: Nevermind, seems to work when I don't bother telling the system to use the authorized key. That IS kinda the idea. ssh just handles that for you, even when called from another program like rsync.

@Romo said in Lookin for best method to create a network bridge CentOS 7: @stacksofplates Another quick question, it is better to create the bridge from the os network utils instead of relying in virtmanager to create it right? That all depends. Macvtap is quick and dirty. Also has the benefits of not allowing network access between the host and VMs (can be a benefit or a hindrance depending on your scenario). If you want Full access across the bridge, then you'll have to manually create it.

Nice deal!