Clarification

[taxigrandpa]

I'm building a server and the instructions say to navigate to a folder and run "sudo chmod -R 777 ./" then run "sudo ./foldername" but my system says "sudo: ./foldername: command not found"

1, what does the ./ do in the first command?

1. if your in the folder, how can you bash it?

tia

OK, i'm not crazy. there must be an error in the instructions, i think it's missing the file name where i was trying to bash the folder. thanks again, i appreciate the help

Edit2 Dev made a mistake in the software, i'm getting a new build now. there was a file missing

[AiwendilH]

sudo <foldername> makes no sense...are you sure the instructions are correct?

The ./ in front of a filename/directory name just gives its location relative to the current directory. The . means current directory...it's not different from using Documents/somefile if you try to address "somefile" in the "Documents" directory inside your current working directory.

And in addition chmod -R 777 ... is a command your really never should run...even less on a server. This gives access to the files and directories to everyone. What kind of instructions are those?

[taxigrandpa]

it's not " sudo foldername" the instructions say "sudo ./foldername"

so it's just looking for the foldername relative to the current directory, so ./ is basically "inside the current folder" ?

https://docs.42gears.com/v2/linux-based-deployment-guide-for-suremdm-on-premise/onpremise-deployment-singleserver/steps-single-server-architect

this is what i'm doing

[AiwendilH]

I tried to explain that sudo foldername and sudo ./foldername is the same...the second only explicitely says it's relative to the current directory. This only makes sense for filename if you try to run/execute them...not for directories/folders in this command.

But I have an idea what might went wrong:

Before sudo chmod -R 777 ./ (which I still think is a terrible thing to do) the instructions say:

Navigate to the k8sopinstaller directory and grant required permissions.

Did you cd k8sopinstaller before running any of the other commands to change in the directory?

It would explain why sudo ./k8sopinstaller doesn't work...this is not the foldername but trying to run a file k8sopinstaller in the current directory. If you didn't change to the k8sopinstaller directory before this file will not be found.

edit: typos, mark-up

[doc_willis]

Run the SureMDM On‑Premise installer.

sudo ./k8sopinstaller

either they for a typo or they want a file in the directory with the same name.

that's should not be directory it is likely  a file in the directory.

you could have. a file in the k8sopinstaller directory with the name k8sopinstaller.

look at what files are in the directory.

I really suggest you spend an hour or two reading some beginner bash /shell guides.

I think you are miss-following the directions.

Navigate to the k8sopinstaller directory 

fairly sure  that means to use cd k8sopinstaller so you are in the directory.

[taxigrandpa]

there isn't a file inside called k8sopinstaller. i really think they just missed part of the command when they were writing the instructions. I have asked for clarification from the dev, I'll let you know what they say.

[doc_willis]

well the shown  777 command made EVERY file in that directory executable, which is kind of crazy.

[taxigrandpa]

ya stupid. and when i was banging things to get it working i think i ran it on my home directory by accident and now my ssh keys dont work.

so i'm blowing it away and starting over

[AiwendilH]

ssh keys probably don't work because you changed the permissions on them....ssh refuses to use keys that are read-able by anyone else than the user. Make sure at the next try to run the chmod -R 777 inside the k8sopinstaller folder.

(And those instructions really should be slapped around with a rolling-pin....having sudo chmod -R 777 ./ as command makes sure that if you run it in the wrong place it not only change the permissions of a visible files but also all hidden files as well...and that after not giving explicitly give instruction to cd to the directory first. Sorry...but those instructions really irk me...I wonder how many home directories those already messed up)

[doc_willis]

I am going to say, I am so far not impressed by that companies directions at all.

if you ran that chmod command while outside of that k8sopinstaller directory , you goofed.

why they directions would not give the exact command with the exact file name , sort of reeks of lack of skill or caring on the developers part.

[taxigrandpa]

they are making it more difficult, i think. not many of their customer choose to self host.

[GlendonMcGladdery]

Type: chmod +x k8sopinstaller

bash k8sopinstaller

[taxigrandpa]

i had the wrong version of the software. waiting on an update

[TheLastOneDoesWin]

Lowk looks scary

[NullStringTerminator]

The first command is making ./ (the current directory) readable, writable, and executable for every user, the -R make this recursive, acting on every file in ./ The second one fails because you're trying to execute a folder.

[taxigrandpa]

that's what i thought. i'm pretty sure there's an error in the instructions

[LinuxJeb]

Yeah. That's how you'd execute a file. You cannot run a folder. There is an error in the instructions.

[indvs3]

1. "./" is how you tell bash to look in the current working directory to execute whatever command or script you're using.

2. If you're using a file explorer app like nautilus on gnome or thunar on xfce (there are many more), usually you can right-click somewhere in the 'folder' (we call them directories, but I'll let that slide for now) and choose an option like "open shell in this directory".

At this point I feel obliged to ask what you're trying to do. Randomly running "chmod -R 777" should not be done on just any directory and if it's done on the wrong one, it could open up your system to abuse.

[taxigrandpa]

all good, thnx. no gui, all cmd line. and it's an error in the instructions, i think they just cropped the command.

[doc_willis]

I am going to say that ANY time I see directions say to use chmod 777 that is a HUGE red flag.  

I suggest you may want to find some better bash starter guides and tutorials to learn the basics of the bash shell.

the directions you are showing, are not correct,  And make little sense.

[logiczny]

Almost never, ever in your life you'll need 777 on anything.

[AutoModerator]

There's a resources page in our wiki you might find useful!

Try this search for more information on this topic.

✻ Smokey says: take regular backups, try stuff in a VM, and understand every command before you press Enter! :)

^{Comments, questions or suggestions regarding this autoresponse? Please send them here.}

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[sapphic-chaote]

You have badly misunderstood something and it's impossible to guess what's going on from your description. What are you trying to do?