Sponsored Content
Top Forums UNIX for Advanced & Expert Users What's your most useful shell? Post 302492324 by tetsujin on Monday 31st of January 2011 03:09:32 AM
Old 01-31-2011
Quote:
Originally Posted by Corona688
The shell is a more direct interface to the environment and the kernel than a lot of people realize. File numbers in shell are the file descriptor numbers the kernel has actually assigned to this process, nothing more, nothing less.
The same is true of file descriptors in C - but when you call open() to open a file there's no chance of accidentally closing a file you had open - the newly-opened file is assigned to a previously unallocated file descriptor.

So there's that basic problem of syntax when using redirection syntax to open files... That much could be solved pretty easily. (Actually, I guess Bash already has it pretty much licked: "exec {newfd}<filename"... $newfd takes on the newly allocated file descriptor number...)

But why stop there? There's no reason the shell couldn't tie the idea of an "open file" (within the shell) to a specialized, non-exportable variable, which offers the possibility of scoping and reference-counting the file descriptor, closing it when it's unused within the shell process. This would also give us a natural way to express whether the file descriptor should be "exported" to child processes (i.e. whether it's kept open through a fork()/exec()) - if the variable is exported, the child process gets an environment variable with a file descriptor number in it, and that file is open. If it's not, the file descriptor is closed on (or before) exec().

There's no reason numeric redirections couldn't still be made available for those cases where you need to control exactly where an open file ends up for a specific child process. I think that's just not the common case. The common case is that people want to read from or write to files. The bash/zsh syntax that allows opening a file and assigning its descriptor to a variable is a step in the right direction, but I think there's no reason things couldn't be improved further.

Quote:
Environment variables (though not non-exported variables)
I want to point out that exception because it's an important one. Variables implemented in shells are already removed from the reality of the underlying mechanism of environment variables. You've got integer variables, array variables, hash table variables... Shells provide these special cases despite the fact that they don't fit the underlying environment variable mechanism (and, therefore, can't be exported) because they're useful.

Quote:
Moving away from the model the kernel presents you would make it a more capable language, and a less capable shell.
Well, granted, though with caveats.

Let's suppose, for instance, I actually were proposing a shell design that wouldn't allow for numeric redirection, and that I were running one of the few programs for which that feature is actually useful. (I only know of a few - xterm, screen - can't think of any others...) Then, yes, something of value was lost.

But this doesn't mean that working with raw resources must be the default means of interacting with the shell - only that it must be available, and that the shell's normal mode of operation shouldn't be too far removed from this. The raw control should be there when you need it, and out of the way the rest of the time.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to run unix commands in a new shell inside a shell script?

Hi , I am having one situation in which I need to run some simple unix commands after doing "chroot" command in a shell script. Which in turn creates a new shell. So scenario is that - I need to have one shell script which is ran as a part of crontab - in this shell script I need to do a... (2 Replies)
Discussion started by: hkapil
2 Replies

2. AIX

Difference between writing Unix Shell script and AIX Shell Scripts

Hi, Please give me the detailed Differences between writing Unix Shell script and AIX Shell Scripts. Thanks in advance..... (0 Replies)
Discussion started by: haroonec
0 Replies

3. Linux

How to Start a Shell as Login shell instead of ordinary shell

Hi I tried with bash --login option. but the output is siva:~$ bash --login siva:~$ is there any way to make the shell ask for user id and password ( and login as different user instead of using sudo / su ) Thx in advance Siva (3 Replies)
Discussion started by: Sivaswami
3 Replies

4. Shell Programming and Scripting

Help need to make a shell script run for ffmpeg vhook watermaking in shell

i have a small problem getting a batxh shell script to run in shell this is the code the problem seems to be centered around the ffmpeg command, something maybe to do with the ' ' wrapping around the vhook part command this is a strange problem , if i take the ffmpeg command and... (1 Reply)
Discussion started by: wingchun22
1 Replies

5. Shell Programming and Scripting

How to run cmds after changing to a new env (shell) in a shell script

Hi, I am using HP-UNIX. I have a requirement as below I have to change env twice like: cadenv <env> cadenv <env> ccm start -d /dbpath ccm tar -xvf *.tar ccm rcv .... mv *.tar BACKUP but after I do the first cadenv <env> , I am unable to execute any of the later commands . ... (6 Replies)
Discussion started by: charlei
6 Replies

6. Shell Programming and Scripting

simple shell - how to get a parameter typed in a shell script

Hi, I am new to unix and using linux 7.2. I would like to create a script that would make it easyer for me to run my java programms. At the moment I have to type java myJavaprogram I am trying to write a script that will allow me to type something like this "myscript myJavaprogram" or maybe... (4 Replies)
Discussion started by: cmitulescu
4 Replies

7. Shell Programming and Scripting

calling 'n' number of shell scripts based on dependency in one shell script.

Hello gurus, I have three korn shell script 3.1, 3.2, 3.3. I would like to call three shell script in one shell script. i m looking for something like this call 3.1; If 3.1 = "complete" then call 3.2; if 3.2 = ''COMPlete" then call 3.3; else exit The... (1 Reply)
Discussion started by: shashi369
1 Replies

8. Shell Programming and Scripting

Any shell or hack that makes the shell command line take vi commands?

basically i'm tired of hitting the left arrow a few dozen times when correcting a mistake or modifying a history command i'd like to use vim style key shortcuts while on the command line so that a 55 moves the cursor 55 places to the left... and i want all the other vi goodies, search of... (3 Replies)
Discussion started by: marqul
3 Replies

9. UNIX for Dummies Questions & Answers

Shell script to read lines in a text file and filter user data Shell Programming and Scripting

sxsaaas (3 Replies)
Discussion started by: VikrantD
3 Replies

10. Shell Programming and Scripting

Pass C shell array to another C shell script(csh) and shell(sh)

Dear Friends, Please help me on this my script name is send.csh In this i have written the statement like this set args = ( city state country price ) I want to pass this array to another c shell called receiver.csh. and i want to use it in this c shell or how to pass to... (2 Replies)
Discussion started by: SA_Palani
2 Replies
DUP(2)							     Linux Programmer's Manual							    DUP(2)

NAME
dup, dup2, dup3 - duplicate a file descriptor SYNOPSIS
#include <unistd.h> int dup(int oldfd); int dup2(int oldfd, int newfd); #define _GNU_SOURCE #include <unistd.h> int dup3(int oldfd, int newfd, int flags); DESCRIPTION
These system calls create a copy of the file descriptor oldfd. dup() uses the lowest-numbered unused descriptor for the new descriptor. dup2() makes newfd be the copy of oldfd, closing newfd first if necessary, but note the following: * If oldfd is not a valid file descriptor, then the call fails, and newfd is not closed. * If oldfd is a valid file descriptor, and newfd has the same value as oldfd, then dup2() does nothing, and returns newfd. After a successful return from one of these system calls, the old and new file descriptors may be used interchangeably. They refer to the same open file description (see open(2)) and thus share file offset and file status flags; for example, if the file offset is modified by using lseek(2) on one of the descriptors, the offset is also changed for the other. The two descriptors do not share file descriptor flags (the close-on-exec flag). The close-on-exec flag (FD_CLOEXEC; see fcntl(2)) for the duplicate descriptor is off. dup3() is the same as dup2(), except that: * The caller can force the close-on-exec flag to be set for the new file descriptor by specifying O_CLOEXEC in flags. See the description of the same flag in open(2) for reasons why this may be useful. * If oldfd equals newfd, then dup3() fails with the error EINVAL. RETURN VALUE
On success, these system calls return the new descriptor. On error, -1 is returned, and errno is set appropriately. ERRORS
EBADF oldfd isn't an open file descriptor, or newfd is out of the allowed range for file descriptors. EBUSY (Linux only) This may be returned by dup2() or dup3() during a race condition with open(2) and dup(). EINTR The dup2() or dup3() call was interrupted by a signal; see signal(7). EINVAL (dup3()) flags contain an invalid value. Or, oldfd was equal to newfd. EMFILE The process already has the maximum number of file descriptors open and tried to open a new one. VERSIONS
dup3() was added to Linux in version 2.6.27; glibc support is available starting with version 2.9. CONFORMING TO
dup(), dup2(): SVr4, 4.3BSD, POSIX.1-2001. dup3() is Linux-specific. NOTES
The error returned by dup2() is different from that returned by fcntl(..., F_DUPFD, ...) when newfd is out of range. On some systems dup2() also sometimes returns EINVAL like F_DUPFD. If newfd was open, any errors that would have been reported at close(2) time are lost. A careful programmer will not use dup2() or dup3() without closing newfd first. SEE ALSO
close(2), fcntl(2), open(2) COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2008-10-09 DUP(2)
All times are GMT -4. The time now is 07:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy