4 ms·
I can think of one way to write "cd" out-of-process from the shell: exec /bin/cd /some/path, which does chdir("/some/path") and execs your shell. You'd lose yo
by JoshTriplett 11y ago
I can think of one way to write "cd" out-of-process from the shell: exec /bin/cd /some/path, which does chdir("/some/path") and execs your shell. You'd lose your history and similar state, but if you had a shell that didn't even put cd in-process, it probably doesn't have history either.
Sample:
/tmp$ exec /tmp/cd /bin
/bin$ exec /tmp/cd /home
/home$ exec /tmp/cd /usr
/usr$
Sample code:
#include <err.h>
#include <stdlib.h>
#include <unistd.h>
int main(int argc, char *argv[])
{
char *shell;
if (argc != 2)
errx(1, "Usage: exec cd /some/path");
if (chdir(argv[1]) == -1)
err(1, "chdir");
shell = getenv("SHELL");
if (!shell || !*shell)
shell = "/bin/sh";
execl(shell, shell, NULL);
err(1, "exec");
}
- duaneb 11y agoHah, hadn't thought of that. Kind of CPS for processes. I'm not sure what that would gain you, though, as you'd have to either a) write both the cd and the user of the cd, and there are less awkward ways to do that than exec'ing, or b) you'd have to pass something ELSE to exec to return control after cd finishes. This seems a little awkward and I'm not sure what is being proven. :P
- aardvark179 11y agoIt's how very early version of Unix effectively did stuff, they exceed a program, and when it exited they exceed the shel again. When they introduced something like the fork/exec model we now have they discovered cd didn't work any more and had to write it as a built in. Now, for bonus points, work out how goto worked when it wasn't a built in.
- JoshTriplett 11y ago> It's how very early version of Unix effectively did stuff, they exceed a program, and when it exited they exceed the shel again. Makes sense, since those systems might not have enough memory to run the shell and another program at the same time.
- acveilleux 11y agoThis would cause an eventual exhaustion of process table entry / pid and/or addressable memory as the previous shell is left in the background.
- cperciva 11y agoThere's nothing being left in the background. It's one process which is calling exec repeatedly; no forking going on.