Search results

I am wading through all that myself ,.. been using linux for many years but i need to be less laze a delve deeper even if much doesnt apply to just a home linux box -- it is good to learn when family and friends begin to drop .. lets say "other OS" for linux , then it will be good to be...

I totally agree - permissions are to limit / grant access according to need and for security. for the most part since it is only myself on a laptop the permissions are generally not an issue other than certain things for the system which might be created while in a sudo mode and permissions...

i will read the man again .. sometimes they are so hard to follow .. thank you onward to more experiments

But shouldnt it default to appear in the command window where it was created ? i have to searching tty's or dump to a file --i cant just use it like a timer / reminder? though yes i would do more useful things with it but i wanted to do proof of concept type basic stuff first

thank you

"at" didnt come installed i had to sudo apt install at I then did :~$ at now+5min warning: commands will be executed using /bin/sh at> echo "Hello" at> at> <EOT> job 5 at Mon Sep 2 12:38:00 2024 :~$ it shows job 5 queued (i tried a few times) even with atq 5 Mon Sep 2 12:38:00 2024...

it took me a while to figure this out. I had to compare your post (scratching my head over the -d. where i expected-d . This works as you said : ls | cut -d. -f1 Perhaps i need to get book on grep / sed / awk - the gnu.org page mentions sed to do this. ls | awk -F . '{print $1}' --and...

i see i have them all mixed up in my brain. The first version the way you have it make perfect sense and i follow that but the usage says : basename NAME [SUFFIX] doesnt the [ ] mean optional ? what if you dont know or dont care about the suffix ? I re-read then man page and then followed...

On the basename man page it has two syntax uses. Only the second version works for me basename NAME [SUFFIX] basename OPTION... NAME... version one: basename -s datafile.pdf doesnt work but basename datafile.pdf .pdf -does work as does the necessity of using the back ticks in the...

i can see this is going to take lots of practice. and not being afraid to make mistakes and do research for the solutions

at least i seem to be on the same page -- keeping aliases (relatively) simple and using scripts for more complicated tasks. I like the scripts that run and end, not ones that keep a shell instance running unless they are something real time i suppose , like "top" but that's more of an app...

I am not that complex either (not yet) but i followed the reasoning and flow as to what was going on I have steered away from making scripts / aliases the exact same as standard commands --but i do like knowing that i can escape them if i make them .. thats kool

Vektor: -- my distro (ubuntu) doesnt have that file /usr/local/share/applications I put them in /usr/local/bin/ or .local/bin/ I am not sure which is best... it is only home so i dont think it really matters new_vintage: i-- agree -- i think if it is more than making an often used...

Here is a question that i would like to pose for thought and discussion I have made aliases ( wih simple commands and at least one called a function) -- and i have made scripts with bash and python . both of the latter scripts i have succeeded in making executable and placed in my $PATH so...

this is perfectly said .. many combinations are possible but in practice , we use very few in basic file permissions 744 -- i tend to use this at home rather than 777 , i dont really know why , feels right 777 766

Excellent !! going to save that in my bash notes thank you

I am fiddling around with permissions and chmod - and just on my own linux box I tend to make the scripts chmod 744 (rwxr--r--) so only i can run but any can read ( and not write or execute ) PS -- the chmod +x sets the "x" or the "1" bit note they would all become "odd" to get 755 in...