10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello I am attempting to generate a bash scrip that prompts me at loggin to change my PS1 -
However, I am running into an issue w/ the code.
#!/bin/bash
#the point of this script is to that it automates and changes my prompts every day
msg1="What do you feel like adding today :"
echo... (11 Replies)
Discussion started by: D'go
11 Replies
2. Shell Programming and Scripting
I have coded PS1 as shown, producing the following result when writing on the command line
┌─ cdl
└──╼ make tracepdf2d
If I make an error in the command an ✗ is printed
┌─ ✗ cdl
└──╼ ls-a
ls-a: command not found
My problem is that if I just press enter, I do not want to have the... (3 Replies)
Discussion started by: kristinu
3 Replies
3. Shell Programming and Scripting
I am trying to create my custom prompt and I have almost succeeded. Right now I have PS1='\n\\$\ '
What I have not figured out is how to make the directories bold when I'm using commands ls or ls -la.
Any idea how to do it???
Many thanx. (2 Replies)
Discussion started by: emailkia
2 Replies
4. UNIX for Dummies Questions & Answers
I have set PSI for my prompt using the following command:
PS1="${debian_chroot:+($debian_chroot)}\\u@\h:\\\w\a]\ "which produces
chrisd@pguk:~]I want to include [ in the beginning but cannot understand the way to do this.
Also I want to show only the current directory, not the whole... (4 Replies)
Discussion started by: kristinu
4 Replies
5. Shell Programming and Scripting
Ok then i Have a challenge for you :
Give me PS1 so that it always display the least 2 levels of directory
(except if i am above of course)
I want it this way :
so if i go to
/
/home/
/home/user
/home/user/whatever
/home/user/whatever1/whatever2
my PS1 should respectively... (12 Replies)
Discussion started by: ctsgnb
12 Replies
6. Shell Programming and Scripting
I am 100% new to Unix and trying to learn.
This is my first time even touching a script in Unix.
We have the following variable script that I am trying to run....
##################################
###### variable test###
##################################
Hostname=`hostname`... (3 Replies)
Discussion started by: LRoberts
3 Replies
7. UNIX for Dummies Questions & Answers
please advise what's wrong with this command ?
PS1="`hostname`:`who am i | cut -d " " -f1`:>>"
trying to make the PS1 prompt look like :
machine_name:username:>>
thank you (4 Replies)
Discussion started by: venhart
4 Replies
8. UNIX for Dummies Questions & Answers
I know this question has come up before but I couldn't find any documentation on ksh here.
I'm trying
PS1="`whoami`@`hostname`:`pwd`> "
export PS1
in ksh but the working directory sticks at the home directory. How do I fix that? Also, how do I make the prompt bold in korn? (3 Replies)
Discussion started by: rein
3 Replies
9. UNIX for Advanced & Expert Users
I want to set my prompt to something more descriptive than a plain old $, so I set the PS1 variable as such:
PS1=""
Which changes the prompt correctly, but when I change directories, it does not update the prompt. So I tried this:
PS1="`pwd`>"
I get the same results when changing... (2 Replies)
Discussion started by: dangral
2 Replies
10. UNIX for Dummies Questions & Answers
Hello
I am using Debain Potato and I changed the PS1. When I log in locally everythink is fine, except that when I enter a long row without hitting enter, then it word wraps automatically. And it does it not at the end of the row, it does it in the middle of the row!
It also does not writes... (7 Replies)
Discussion started by: Fwurm
7 Replies
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