|
|
Sponsored Content
Operating Systems
OS X (Apple)
shell script location w/ Panther
Post 47994 by ropers on Tuesday 24th of February 2004 10:39:24 AM
02-24-2004
shell script location w/ Panther
I'm sure there things have only been asked a thousand times (I just couldn't find the answers):
I am running Panther (Mac OS X ver. 10.3.2.[at present]).
I am using the (default) bash shell.
I am *starting* to write shell scripts.
I would like to "install" some shell scripts, so that they are always available for execution (for me only), and preferably so that they can be called by simply typing their filename (plus optional parameters).
I don't want to type ./filename or something.
I *suspect* I'd need to do the following:
- Write the script(s) and store it/them in a location where it's good practice to put them.
- Write/edit a ~/.bashrc file and add an alias/aliases for every command I want included.
Am I right with the above?
Would there be additional things I'd need to do?
Also, what location would be good practice to put these things in?
Alternatively, there wouldn't be a way to just include the files in the path and it would work, would it? (I remember this from goody ole DOS.)
Also, I'd be interested to learn how I can make these scripts available to everyone (but otherwise as above). This would obviously mean storing them in a commonly accessible location -- again, I'd like to know where it's good practice to put them. Plus, I'd need something else than ~/.bashrc.
Again, if I'm entirely on the wrong track, please do not hesitate correcting me. I am not looking for a quick fix, I am looking for a solution that's truly best practice with my OS.
Many thanks in advance!!!
rop
I am running Panther (Mac OS X ver. 10.3.2.[at present]).
I am using the (default) bash shell.
I am *starting* to write shell scripts.
I would like to "install" some shell scripts, so that they are always available for execution (for me only), and preferably so that they can be called by simply typing their filename (plus optional parameters).
I don't want to type ./filename or something.
I *suspect* I'd need to do the following:
- Write the script(s) and store it/them in a location where it's good practice to put them.
- Write/edit a ~/.bashrc file and add an alias/aliases for every command I want included.
Am I right with the above?
Would there be additional things I'd need to do?
Also, what location would be good practice to put these things in?
Alternatively, there wouldn't be a way to just include the files in the path and it would work, would it? (I remember this from goody ole DOS.)
Also, I'd be interested to learn how I can make these scripts available to everyone (but otherwise as above). This would obviously mean storing them in a commonly accessible location -- again, I'd like to know where it's good practice to put them. Plus, I'd need something else than ~/.bashrc.
Again, if I'm entirely on the wrong track, please do not hesitate correcting me. I am not looking for a quick fix, I am looking for a solution that's truly best practice with my OS.
Many thanks in advance!!!
rop
|
|
10 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
I wanna know what Panther (The Next Major Release Of OS X)
Due Date: around August
I predict that X11 will be released in a new Full stable version in the new OS X (No new revelation)
And Safari (Apple's FAST Internet Browser) will be implemented in Full...
I'm Guessing that the new G5... (0 Replies)
Discussion started by: DonJawz
0 Replies
2. Shell Programming and Scripting
Hi,
I need a shell script that when run should be able to find the geographical location of the system.
can anyone help me with this?
Thanks,
Sundeep (1 Reply)
Discussion started by: eamani_sun
1 Replies
3. Shell Programming and Scripting
Create a script that copies files from one specified directory to another specified directory, in the order they were created in the original directory between specified times. Copy the files at a specified interval. (2 Replies)
Discussion started by: allways4u21
2 Replies
4. Shell Programming and Scripting
Hi,
On the server, we have app log files in this location /app/logs/error.log
On the same server, in a real time, we would like to replicate that into /var/ directory.
if someone has already done this, please share the script.
Thanks in advance. (4 Replies)
Discussion started by: lookinginfo
4 Replies
5. Shell Programming and Scripting
Hi,
I am using Solaris 10 OS and trying to create shell script that can add input at certain location into a file.
The input that I am trying to put is new domain name
e.g
@newdomain.com
the file contains,
more test01.out
user/zzzz786@st.com/INBOX
user/zzzz@po.com/INBOX... (8 Replies)
Discussion started by: Mr_47
8 Replies
6. Shell Programming and Scripting
Hi
This is my third past and very impressed with previous post replies
Hoping the same for below query
How to find a existing file location and directory location in solaris box (1 Reply)
Discussion started by: buzzme
1 Replies
7. Shell Programming and Scripting
Hello.
I want to to backup some "default:" values from a file do some other job and after restore that "default:" values back.
The problem is that the source and destination file has a lot of default: strings in it but with different values...
So..
Here is an example:
A part of my source... (6 Replies)
Discussion started by: ausdim
6 Replies
8. Shell Programming and Scripting
Hi All,
i'm trying to copy the 1.txt files (sample files) in to different path location using the below command.
But it is not copying the files , when i tried for single location able to copy the file.
can any one please assist here.
Please find the below path :-
/ckr_mkr1/licencekey... (2 Replies)
Discussion started by: venkat918
2 Replies
9. Shell Programming and Scripting
Is there any possible way transfering the file from unix to shared location using shell script.
i had created the batch script to fetch the files from unix to shared location and it works fine. Due to some problem in windows unable to transfer the file to shared location automatically. can anyone... (2 Replies)
Discussion started by: venkat918
2 Replies
10. UNIX for Beginners Questions & Answers
Hi ALL,
I am trying to find the installed tomcat version and location of the server.xml file to get the tomcat port number.
Using below script to do that.
#!/usr/bin/env bash
var1=$(find / -name "version.sh" ! -size 0 2>&1 |egrep -v "tmp|docker")
for loc1 in $var1
do
... (1 Reply)
Discussion started by: sravani25
1 Replies
LEARN ABOUT MOJAVE
platform::shell
platform::shell(n) Tcl Bundled Packages platform::shell(n) __________________________________________________________________________________________________________________________________________________ NAME
platform::shell - System identification support code and utilities SYNOPSIS
package require platform::shell ?1.1.4? platform::shell::generic shell platform::shell::identify shell platform::shell::platform shell _________________________________________________________________ DESCRIPTION
The platform::shell package provides several utility commands useful for the identification of the architecture of a specific Tcl shell. This package allows the identification of the architecture of a specific Tcl shell different from the shell running the package. The only requirement is that the other shell (identified by its path), is actually executable on the current machine. While for most platform this means that the architecture of the interrogated shell is identical to the architecture of the running shell this is not generally true. A counter example are all platforms which have 32 and 64 bit variants and where a 64bit system is able to run 32bit code. For these running and interrogated shell may have different 32/64 bit settings and thus different identifiers. For applications like a code repository it is important to identify the architecture of the shell which will actually run the installed packages, versus the architecture of the shell running the repository software. COMMANDS
platform::shell::identify shell This command does the same identification as platform::identify, for the specified Tcl shell, in contrast to the running shell. platform::shell::generic shell This command does the same identification as platform::generic, for the specified Tcl shell, in contrast to the running shell. platform::shell::platform shell This command returns the contents of tcl_platform(platform) for the specified Tcl shell. KEYWORDS
operating system, cpu architecture, platform, architecture platform::shell 1.1.4 platform::shell(n)