system calls
in [Unix Programming]
|
From: Phred Phungus on 8 Mar 2010 13:51 Michael Vilain wrote: > In article <7vjnk5FpmqU6(a)mid.individual.net>, > Ian Collins <ian-news(a)hotmail.com> wrote: > >> Phred Phungus wrote: >>> I don't post to be told that I'm putting forth no effort. Why don't you >>> tell me what I didn't read today, >> One of W. Richard Stevens Unix programming books? They will give you >> the background to make better sense of man pages and other documentation. > > "Don't try to teach a pig to sing. It just frustrates you and annoys > the pig"--Lazarus Long > > [e.g. programming newbies should do their homework before posting "My > program doesn't work. Why?"] > Don't call me a pig, fuckstick. plonk
From: Janis Papanagnou on 8 Mar 2010 14:10 Phred Phungus wrote: > Michael Vilain wrote: >> In article <7vjnk5FpmqU6(a)mid.individual.net>, >> Ian Collins <ian-news(a)hotmail.com> wrote: >> >>> Phred Phungus wrote: >>>> I don't post to be told that I'm putting forth no effort. Why don't >>>> you tell me what I didn't read today, >>> One of W. Richard Stevens Unix programming books? They will give you >>> the background to make better sense of man pages and other >>> documentation. >> >> "Don't try to teach a pig to sing. It just frustrates you and annoys >> the pig"--Lazarus Long >> >> [e.g. programming newbies should do their homework before posting "My >> program doesn't work. Why?"] >> > > Don't call me a pig, fuckstick. Incapable of doing your homework, incapable of understanding the suggestions to your question, incapable of understanding the meta answers WRT your posting, incapable of understanding the meaning of a metaphor in a quote, and now offending people. "The answer, my friend, is blowin' in the wind" [Bob Dylan] > > plonk
From: Phred Phungus on 8 Mar 2010 14:43 Ian Collins wrote: > Phred Phungus wrote: >> >> I don't post to be told that I'm putting forth no effort. Why don't >> you tell me what I didn't read today, > > One of W. Richard Stevens Unix programming books? They will give you > the background to make better sense of man pages and other documentation. > Thx, Ian, I just ordered it. I only have one unix reference right now, and it's more from a user's standpoint. http://i46.tinypic.com/33db7nq.png This shows a couple of the frustrations I have with man pages. When they are slightly out of the ordinary, I don't have them. Furthermore, they take over the terminal, and though they be 1500 lines long, I can't use the scroll bar. I've been using this place for reference: http://www.opengroup.org/onlinepubs/000095399/functions/fork.html , and have gone the next step to download the current unix specification, but it comes in a form that I don't see how to use: http://i50.tinypic.com/2njyrup.png After extraction, it looks like this: http://i46.tinypic.com/33db7nq.jpg , so I know the content is there; it's just in dozens of different folders and html pages. -- fred
From: Phred Phungus on 8 Mar 2010 15:03 Janis Papanagnou wrote: > Incapable of doing your homework, > incapable of understanding the suggestions to your question, > incapable of understanding the meta answers WRT your posting, > incapable of understanding the meaning of a metaphor in a quote, > and now offending people. > > "The answer, my friend, is blowin' in the wind" [Bob Dylan] How is it you people have this crystal ball that looks into my house and my study habits? The people I rent to see me studying this stuff with every free moment. You are factually incorrect on the other points, as I got popen to open a process by creating a pipe, forking, invoking the shell, and doing something useful for me: #include <stdio.h> #include <stdlib.h> #define PATH_MAX 4096 int main () { FILE *fp; int status; char path[PATH_MAX]; //printf ("%d\n", system ("ls | grep .")); fp = popen ("mv *.c backups1/.", "r"); if (fp == NULL) {/* Handle error */} ; while (fgets (path, PATH_MAX, fp) != NULL) printf ("%s", path); status = pclose (fp); if (status == -1) { /* Error reported by pclose() */ } else { /* Use macros described under wait() to inspect `status' in order to determine success/failure of command executed by popen() */ } printf("fp is %p\n", fp); fp = popen ("ls | grep zax", "r"); printf("fp is %p\n", fp); return 0; } // gcc -D_GNU_SOURCE -Wall -Wextra rr4.c -o out This is a differing form of a syscall than system, which returns a file pointer rather than the status. I worked up the other forms that Lew mentioned out of thoroughness, not because I had to. As far as metaphors go, how would you like it to be told you're a grub in a pile of eurotrash? -- fred
From: Ian Collins on 8 Mar 2010 15:27
Phred Phungus wrote: > Ian Collins wrote: >> Phred Phungus wrote: >>> >>> I don't post to be told that I'm putting forth no effort. Why don't >>> you tell me what I didn't read today, >> >> One of W. Richard Stevens Unix programming books? They will give you >> the background to make better sense of man pages and other documentation. >> > > Thx, Ian, I just ordered it. I only have one unix reference right now, > and it's more from a user's standpoint. > > http://i46.tinypic.com/33db7nq.png > > This shows a couple of the frustrations I have with man pages. When > they are slightly out of the ordinary, I don't have them. Furthermore, > they take over the terminal, and though they be 1500 lines long, I can't > use the scroll bar. I don't think you have mentioned which system you are using, but even if you aren't using it, the Solaris documentation at docs.sun.com is very well written. You can read online, or download as PDF. http://docs.sun.com/app/docs/prod/solaris.10 Is a good place to start. -- Ian Collins |