01-07-2005
Just edit your PS1 Variable like
PS1=' `pwd` `uname -n` # '
Note the different characters ..
I´ve tried it on Solaris 9 SPARC and bash 2.05
To set this permanently :
Just edit the line at the end of your profile
($HOME/.profile)
after the Line you have to add "export PS1" like
...
PS1=' `pwd` `uname -n` # '
export PS1
...
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am having a hard time figuring out how to change the command prompt in my UNIX shell.
I am using the bash shell, and I would like to set the prompt to show me the full path of the current working directory along with my username, I suppose... The main thing I want is the full path of the... (2 Replies)
Discussion started by: WERUreo
2 Replies
2. UNIX for Dummies Questions & Answers
Phew simple question,
I want to display the my directory path in prompt.
Did the following in .profile
PS1=`pwd`
export PS!
Worked, but it always points to HOME directory.
When i do a cd, it doesn't change.
What am i missing.
Thanks (7 Replies)
Discussion started by: vibhor_agarwali
7 Replies
3. UNIX for Dummies Questions & Answers
I know no one has ever asked this before {not :D } but I am trying to set the prompt in the .profile under sh. I have tried everything I have seen on the web in regards to this, with no success. The OS is SCO Unixware 7.1.1, {not by my choice}. All the examples I see seem to be for ksh, which is... (1 Reply)
Discussion started by: jcc5169
1 Replies
4. Solaris
I currently have this as my prompt when I log in (shell is sh):
PS1="`hostname ` # "
My question is how do I add the current directory to that prompt? Is there a way?
Thanks. (5 Replies)
Discussion started by: kjbaumann
5 Replies
5. Shell Programming and Scripting
hi all, please tell me why this 2 liner script is not working!!
#!/bin/bash
oldps1="$PS1"
PS1="myprompt>"
but when type this in terminal it works!! (7 Replies)
Discussion started by: tprayush
7 Replies
6. UNIX for Advanced & Expert Users
Is there any way I can change the prompt which asks for the password on a UNIX system? e.g. When I login using Telnet instead of "Password" I should get "Correct Password".
Thanks,
Vineet (3 Replies)
Discussion started by: vineetd
3 Replies
7. Shell Programming and Scripting
Hi,
I want to change the shell prompt, using the cd command.
I have a shell prompt like this -
p78-mfx(dgaw1078/9781)$
Now i do this -
p78-mfx(dgaw1078/9781)$ cd log4j
here the shell prompt should change like this -
p78-mfx(dgaw1078/9781)log4j$ (6 Replies)
Discussion started by: arunkumarmc
6 Replies
8. UNIX for Dummies Questions & Answers
Currently, when I cd to a directory I get the directory path in the command prompt, making it very long. I would like to change it so the path is not displayed.
If I am in directory ~/tatsh/hstmy/test, I just want my prompt to be the last directory name as shown just below
---------- Post... (1 Reply)
Discussion started by: kristinu
1 Replies
9. Shell Programming and Scripting
Hi, i was wondering if it is possible to change the default prompt for the shells that are availble on your system?
For example, i want to change the prompt for the C shell from % to something like ( or ).
Thanks,
Nav. (7 Replies)
Discussion started by: Navs_
7 Replies
10. Shell Programming and Scripting
Need assistance in changing prompt .
Trying to change prompt in csh,tcsh shell . Below are the commands i tried in .cshrc and sourcing this files.
set prompt = "$user@`uname -n` : ${cwd}> "
#above commands works for username and hostname but cwd doesnt change
directories
set... (16 Replies)
Discussion started by: ajayram_arya
16 Replies
LEARN ABOUT OPENDARWIN
unix
UNIX(4) BSD Kernel Interfaces Manual UNIX(4)
NAME
unix -- UNIX-domain protocol family
SYNOPSIS
#include <sys/types.h>
#include <sys/un.h>
DESCRIPTION
The UNIX-domain protocol family is a collection of protocols that provides local (on-machine) interprocess communication through the normal
socket(2) mechanisms. The UNIX-domain family supports the SOCK_STREAM and SOCK_DGRAM socket types and uses filesystem pathnames for address-
ing.
ADDRESSING
UNIX-domain addresses are variable-length filesystem pathnames of at most 104 characters. The include file <sys/un.h> defines this address:
struct sockaddr_un {
u_char sun_len;
u_char sun_family;
char sun_path[104];
};
Binding a name to a UNIX-domain socket with bind(2) causes a socket file to be created in the filesystem. This file is not removed when the
socket is closed--unlink(2) must be used to remove the file.
The UNIX-domain protocol family does not support broadcast addressing or any form of ``wildcard'' matching on incoming messages. All
addresses are absolute- or relative-pathnames of other UNIX-domain sockets. Normal filesystem access-control mechanisms are also applied
when referencing pathnames; e.g., the destination of a connect(2) or sendto(2) must be writable.
PROTOCOLS
The UNIX-domain protocol family is comprised of simple transport protocols that support the SOCK_STREAM and SOCK_DGRAM abstractions.
SOCK_STREAM sockets also support the communication of UNIX file descriptors through the use of the msg_control field in the msg argument to
sendmsg(2) and recvmsg(2).
Any valid descriptor may be sent in a message. The file descriptor(s) to be passed are described using a struct cmsghdr that is defined in
the include file <sys/socket.h>. The type of the message is SCM_RIGHTS, and the data portion of the messages is an array of integers repre-
senting the file descriptors to be passed. The number of descriptors being passed is defined by the length field of the message; the length
field is the sum of the size of the header plus the size of the array of file descriptors.
The received descriptor is a duplicate of the sender's descriptor, as if it were created with a call to dup(2). Per-process descriptor
flags, set with fcntl(2), are not passed to a receiver. Descriptors that are awaiting delivery, or that are purposely not received, are
automatically closed by the system when the destination socket is closed.
SEE ALSO
socket(2), intro(4)
"An Introductory 4.3 BSD Interprocess Communication Tutorial", PS1, 7.
"An Advanced 4.3 BSD Interprocess Communication Tutorial", PS1, 8.
BSD
June 9, 1993 BSD