comp.unix.programmer

• Date Index

---

• 2'complement for 8bit variables, Ron Eggler
  • Re: 2'complement for 8bit variables, Jens Thoms Toerring
    • Re: 2'complement for 8bit variables, Ron Eggler
      • Re: 2'complement for 8bit variables, Jens Thoms Toerring
      • Re: 2'complement for 8bit variables, jgharston
      • Re: 2'complement for 8bit variables, Wayne C. Morris
  • Re: 2'complement for 8bit variables, Ike Naar
• Video tutorials on VIM and UNIX, Yue Jiang
• Compilation under HPUX or any other commercial Unix, thomas . mertes
  • Re: Compilation under HPUX or any other commercial Unix, Volker Birk
    • Re: Compilation under HPUX or any other commercial Unix, Fritz Wuehler
      • Re: Compilation under HPUX or any other commercial Unix, Noob
      • Re: Compilation under HPUX or any other commercial Unix, Fritz Wuehler
      • Re: Compilation under HPUX or any other commercial Unix, thomas . mertes
  • Re: Compilation under HPUX or any other commercial Unix, Casper H . S . Dik
    • Re: Compilation under HPUX or any other commercial Unix, Noob
    • Re: Compilation under HPUX or any other commercial Unix, thomas . mertes
      • Re: Compilation under HPUX or any other commercial Unix, Rainer Weikusat
      • Re: Compilation under HPUX or any other commercial Unix, thomas . mertes
      • Re: Compilation under HPUX or any other commercial Unix, Geoff Clare
      • Re: Compilation under HPUX or any other commercial Unix, Rainer Weikusat
  • Re: Compilation under HPUX or any other commercial Unix, Richard Kettlewell
    • Re: Compilation under HPUX or any other commercial Unix, Mark
    • Re: Compilation under HPUX or any other commercial Unix, thomas . mertes
      • Re: Compilation under HPUX or any other commercial Unix, Rainer Weikusat
      • Re: Compilation under HPUX or any other commercial Unix, thomas . mertes
      • Re: Compilation under HPUX or any other commercial Unix, Rainer Weikusat
      • Re: Compilation under HPUX or any other commercial Unix, thomas . mertes
      • Re: Compilation under HPUX or any other commercial Unix, Rainer Weikusat
      • Re: Compilation under HPUX or any other commercial Unix, thomas . mertes
      • Re: Compilation under HPUX or any other commercial Unix, Rainer Weikusat
      • Re: Compilation under HPUX or any other commercial Unix, Rainer Weikusat
      • Re: Compilation under HPUX or any other commercial Unix / spelling, James Waldby
  • Re: Compilation under HPUX or any other commercial Unix, Rich Gray
• Linux serial port communications, cerr
  • Re: Linux serial port communications, Scott Lurndal
    • Re: Linux serial port communications, cerr
      • Re: Linux serial port communications, Johann Klammer
      • Re: Linux serial port communications, Ron Eggler
      • Re: Linux serial port communications, Ralf Fassel
      • Re: Linux serial port communications, Ron Eggler
      • Re: Linux serial port communications, Scott Lurndal
      • Re: Linux serial port communications, Ron Eggler
      • Re: Linux serial port communications, Scott Lurndal
      • Re: Linux serial port communications, Ike Naar
• fork + exec and SIGSTOP/SIGCONT, dmarkh
  • Re: fork + exec and SIGSTOP/SIGCONT, Joshua Maurice
    • Re: fork + exec and SIGSTOP/SIGCONT, Scott Lurndal
      • Re: fork + exec and SIGSTOP/SIGCONT, Joshua Maurice
      • Re: fork + exec and SIGSTOP/SIGCONT, Scott Lurndal
      • Return type of main() (was: fork + exec and SIGSTOP/SIGCONT), Geoff Clare
  • Re: fork + exec and SIGSTOP/SIGCONT, Huibert Bol
    • Re: fork + exec and SIGSTOP/SIGCONT, dmarkh
      • Re: fork + exec and SIGSTOP/SIGCONT, Barry Margolin
      • Re: fork + exec and SIGSTOP/SIGCONT, dmarkh
      • Re: fork + exec and SIGSTOP/SIGCONT, Huibert Bol
      • Re: fork + exec and SIGSTOP/SIGCONT, dmarkh
      • Re: fork + exec and SIGSTOP/SIGCONT, dmarkh
      • Re: fork + exec and SIGSTOP/SIGCONT, dmarkh
      • Re: fork + exec and SIGSTOP/SIGCONT, Scott Lurndal
      • Re: fork + exec and SIGSTOP/SIGCONT, Scott Lurndal
      • Re: fork + exec and SIGSTOP/SIGCONT, Barry Margolin
      • Re: fork + exec and SIGSTOP/SIGCONT, dmarkh
    • Re: fork + exec and SIGSTOP/SIGCONT, Barry Margolin
      • Re: fork + exec and SIGSTOP/SIGCONT, dmarkh
      • Re: fork + exec and SIGSTOP/SIGCONT, Scott Lurndal
  • Re: fork + exec and SIGSTOP/SIGCONT, Huibert Bol
• Rejecting connection attempts on socket, Kenneth Brody
  • Re: Rejecting connection attempts on socket, Richard Kettlewell
    • Re: Rejecting connection attempts on socket, Kenneth Brody
      • Re: Rejecting connection attempts on socket, Richard Kettlewell
      • Re: Rejecting connection attempts on socket, Kenneth Brody
      • Re: Rejecting connection attempts on socket, Eric Sosman
      • Re: Rejecting connection attempts on socket, Richard Kettlewell
      • Re: Rejecting connection attempts on socket, Ulrich Eckhardt
  • Re: Rejecting connection attempts on socket, Ersek, Laszlo
    • Re: Rejecting connection attempts on socket, Mark
  • Re: Rejecting connection attempts on socket, Nobody
  • Re: Rejecting connection attempts on socket, Xavier Roche
    • Re: Rejecting connection attempts on socket, Scott Lurndal
      • Re: Rejecting connection attempts on socket, Xavier Roche
      • Re: Rejecting connection attempts on socket, William Ahern
      • Re: Rejecting connection attempts on socket, Nobody
• read system call hangs, Jaydeep Chovatia
  • Re: read system call hangs, Volker Birk
    • Re: read system call hangs, Barry Margolin
• Import into bibtex, google scholar, rudra
• BITS 4002 "Deep Collisions" Demostration., Herman Samso J.
• Equivalence of sem_trywait and sem_timedwait, Noob
  • Re: Equivalence of sem_trywait and sem_timedwait, Rainer Weikusat
• Search for API function to activate a task and return it's PID to the caller, dmarkh@xxxxxxxxxx
  • Re: Search for API function to activate a task and return it's PID to the caller, Måns Rullgård
    • Re: Search for API function to activate a task and return it's PID to the caller, dmarkh@xxxxxxxxxx
      • Re: Search for API function to activate a task and return it's PID to the caller, Måns Rullgård
      • Re: Search for API function to activate a task and return it's PID to the caller, dmarkh@xxxxxxxxxx
      • Re: Search for API function to activate a task and return it's PID to the caller, Lew Pitcher
      • Re: Search for API function to activate a task and return it's PID to the caller, Barry Margolin
      • Re: Search for API function to activate a task and return it's PID to the caller, Jeff Flinn
      • Re: Search for API function to activate a task and return it's PID to the caller, Barry Margolin
      • Re: Search for API function to activate a task and return it's PID to the caller, Casper H . S . Dik
      • Re: Search for API function to activate a task and return it's PID to the caller, Rainer Weikusat
      • Re: Search for API function to activate a task and return it's PID to the caller, Måns Rullgård
      • Re: Search for API function to activate a task and return it's PID to the caller, Gordon Burditt
      • Re: Search for API function to activate a task and return it's PID to the caller, Casper H . S . Dik
      • Re: Search for API function to activate a task and return it's PID to the caller, dmarkh@xxxxxxxxxx
      • Re: Search for API function to activate a task and return it's PID to the caller, dmarkh@xxxxxxxxxx
      • Re: Search for API function to activate a task and return it's PID to the caller, Rainer Weikusat
      • Re: Search for API function to activate a task and return it's PID to the caller, Barry Margolin
      • Re: Search for API function to activate a task and return it's PID to the caller, Xavier Roche
      • Re: Search for API function to activate a task and return it's PID to the caller, Rainer Weikusat
      • Re: Search for API function to activate a task and return it's PID to the caller, Eric Sosman
      • Re: Search for API function to activate a task and return it's PID to the caller, Rainer Weikusat
      • Re: Search for API function to activate a task and return it's PID to the caller, Xavier Roche
      • Re: Search for API function to activate a task and return it's PID to the caller, William Ahern
      • Re: Search for API function to activate a task and return it's PID to the caller, Xavier Roche
      • Re: Search for API function to activate a task and return it's PID to the caller, William Ahern
      • Re: Search for API function to activate a task and return it's PID to the caller, Rainer Weikusat
      • Re: Search for API function to activate a task and return it's PID to the caller, Barry Margolin
      • Re: Search for API function to activate a task and return it's PID to the caller, Casper H . S . Dik
      • Re: Search for API function to activate a task and return it's PID to the caller, Rainer Weikusat
      • Re: Search for API function to activate a task and return it's PID to the caller, Casper H . S . Dik
      • Re: Search for API function to activate a task and return it's PID to the caller, Casper H . S . Dik
• Re: Exact meaning of the "hello world", Michael Press
  • Re: Exact meaning of the "hello world", Barry Margolin
    • Re: Exact meaning of the "hello world", Michael Press
  • Re: Exact meaning of the "hello world", Nomen Nescio
  • Re: Exact meaning of the "hello world", Rainer Weikusat
  • <Possible follow-ups>
  • Re: Exact meaning of the "hello world", J0ax88
• mmap questions, de
  • Re: mmap questions, Scott Lurndal
• Re: Why is gcc stage 1 needed?, Jianjun Mao
• Best practices for avoiding leak zombie processes while retaining child exit code?, Joshua Maurice
  • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Geoff Clare
    • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Joshua Maurice
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Geoff Clare
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Richard Kettlewell
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Barry Margolin
    • Message not available
      • Message not available
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Geoff Clare
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Joshua Maurice
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Ian Collins
  • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Barry Margolin
    • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Joshua Maurice
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Ian Collins
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Joshua Maurice
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Joshua Maurice
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Ian Collins
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Joshua Maurice
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Ersek, Laszlo
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Scott Lurndal
      • MIME [was: Best practices for avoiding leak zombie processes while retaining child exit code?], Ersek, Laszlo
      • Re: MIME [was: Best practices for avoiding leak zombie processes while retaining child exit code?], Richard Kettlewell
      • Re: MIME [was: Best practices for avoiding leak zombie processes while retaining child exit code?], Marc
      • Re: MIME [was: Best practices for avoiding leak zombie processes while retaining child exit code?], Ersek, Laszlo
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Joshua Maurice
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Ersek, Laszlo
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Nobody
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Rainer Weikusat
      • Re: Best practices for avoiding leak zombie processes while retaining child exit code?, Rainer Weikusat
• function question, Bill Cunningham
  • Re: function question, Paul
  • Re: function question, Volker Birk
    • Re: function question, Nicolas George
      • Re: function question, Volker Birk
      • Re: function question, Bill Cunningham
      • Re: function question, Volker Birk
      • Re: function question, Richard Kettlewell
      • Re: function question, Volker Birk
      • Re: function question, Rainer Weikusat
    • Re: function question, Bill Cunningham
      • Re: function question, Casper H . S . Dik
      • Re: function question, Geoff Clare
      • Re: function question, Bill Cunningham
      • Re: function question, Geoff Clare
      • Re: function question, Alan Curry
    • Re: function question, Rainer Weikusat
      • Re: function question, Volker Birk
      • Re: function question, Måns Rullgård
      • Re: function question, Rainer Weikusat
      • Re: function question, Casper H . S . Dik
      • Re: function question, Måns Rullgård
    • Re: function question, Scott Lurndal
• Re: Ordering of sem_wait waiters, Noob
  • Re: Ordering of sem_wait waiters, Rainer Weikusat
    • Re: Ordering of sem_wait waiters, Noob
• Re: sh: time: command not found, Ersek, Laszlo
  • Re: sh: time: command not found, Geoff Clare

• Security
• UNIX
• Linux
• Coding
• Usenet

• Mailing-Lists
• Newsgroups
• About
• Privacy
• Search
• Imprint

unix.derkeiler.com  > Newsgroups  > comp.unix.programmer  > 2012-05