comp.unix.programmer

• Thread Index

---

• Re: pthread_join(): any way to limit how long it waits for?
  • From: Simon Elliott
• Re: Evil filename
  • From: Michael Wojcik
• Re: GDB Break the program execution
  • From: Salvatore Di Fazio
• Re: how to write a library ( .a or .so file ) in Unix using C? Urgent!!!
  • From: Thomas Dickey
• Re: GDB Break the program execution
  • From: Salvatore Di Fazio
• Re: pthread_join(): any way to limit how long it waits for?
  • From: David Schwartz
• Re: loading process environment variables
  • From: Roger Leigh
• Re: loading process environment variables
  • From: RickE
• Re: Unix scripting
  • From: Stephan Brönnimann
• makefile recursion
  • From: billy
• Unix scripting
  • From: tejal.acharya@xxxxxxxxx
• Re: how to use ioctl to check out memory usage
  • From: lanchen . ubuntu
• Re: libXt version
  • From: Chuck Dillon
• Re: how to use ioctl to check out memory usage
  • From: Rainer Temme
• how to use ioctl to check out memory usage
  • From: lanchen . ubuntu
• Re: Threaded/forked timer that terminates a function after n minutes passed
  • From: Stephan Brönnimann
• Re: pthread_join(): any way to limit how long it waits for?
  • From: Andrei Voropaev
• Re: GDB Break the program execution
  • From: Andrei Voropaev
• Re: pthread_join(): any way to limit how long it waits for?
  • From: Simon Elliott
• Re: pthread_join(): any way to limit how long it waits for?
  • From: David Schwartz
• Re: pthread_join(): any way to limit how long it waits for?
  • From: Simon Elliott
• LDPC platform: Looking forward
  • From: saad
• Re: GDB Break the program execution
  • From: Salvatore Di Fazio
• Re: GDB Break the program execution
  • From: Salvatore Di Fazio
• Re: pthread_join(): any way to limit how long it waits for?
  • From: David Schwartz
• Re: Threaded/forked timer that terminates a function after n minutes passed
  • From: Stephan Brönnimann
• Re: Threaded/forked timer that terminates a function after n minutes passed
  • From: Jakub Moskal
• Re: how to write a library ( .a or .so file ) in Unix using C? Urgent!!!
  • From: Rich Teer
• Re: Threaded/forked timer that terminates a function after n minutes passed
  • From: Stephan Brönnimann
• Re: Compiling a Visual Studio project in Unix using gcc/icc
  • From: saad
• how to write a library ( .a or .so file ) in Unix using C? Urgent!!!
  • From: ZOLTAN
• Re: Threaded/forked timer that terminates a function after n minutes passed
  • From: Stephan Brönnimann
• Re: pthread_join(): any way to limit how long it waits for?
  • From: Simon Elliott
• Compiling a Visual Studio project in Unix using gcc/icc
  • From: saad
• Re: Threaded/forked timer that terminates a function after n minutes passed
  • From: Jakub Moskal
• Re: Threaded/forked timer that terminates a function after n minutes passed
  • From: Jakub Moskal
• Re: libXt version
  • From: Fred Kleinschmidt
• Re: serial ports: how do I know data has been sent?
  • From: James Carlson
• Re: Lookup between 2 files ( korn shell )
  • From: Ralf Fassel
• Re: Unix specific C++ header files for Intel C compiler
  • From: saad
• Re: Lookup between 2 files ( korn shell )
  • From: pawan_test
• Re: Unix specific C++ header files for Intel C compiler
  • From: saad
• Re: Find out which character set is used
  • From: thomas . mertes
• Re: pthread_join(): any way to limit how long it waits for?
  • From: Maxim Yegorushkin
• libXt version
  • From: seema
• pthread_join(): any way to limit how long it waits for?
  • From: Simon Elliott
• Re: serial ports: how do I know data has been sent?
  • From: Simon Elliott
• Re: loading process environment variables
  • From: RickE
• Re: serial ports: how do I know data has been sent?
  • From: Simon Elliott
• Re: Unix specific C++ header files for Intel C compiler
  • From: Maxim Yegorushkin
• Re: encrypt a string and decrypt it back in Unix Shell Programming
  • From: Stephan Brönnimann
• Re: Threaded/forked timer that terminates a function after n minutes passed
  • From: Stephan Brönnimann
• Threaded/forked timer that terminates a function after n minutes passed
  • From: Jakub Moskal
• Unix specific C++ header files for Intel C compiler
  • From: saad
• Re: encrypt a string and decrypt it back in Unix Shell Programming
  • From: kiranhiremath
• Re: Writing a unix command prompt
  • From: Barry Margolin
• Re: loading process environment variables
  • From: phil-news-nospam
• Re: Writing a unix command prompt
  • From: Henry Townsend
• Re: Writing a unix command prompt
  • From: Barry Margolin
• Re: Writing a unix command prompt
  • From: Pascal Bourguignon
• Re: Compiling against libnet
  • From: Pigpenn
• Re: Writing a unix command prompt
  • From: Chris F.A. Johnson
• Re: Grep / Bash problem
  • From: Conrad J. Sabatier
• Re: Grep / Bash problem
  • From: Conrad J. Sabatier
• Re: Grep / Bash problem
  • From: Conrad J. Sabatier
• Re: Writing a unix command prompt
  • From: Barry Margolin
• Re: Find out which character set is used
  • From: Måns Rullgård
• Find out which character set is used
  • From: thomas . mertes
• Re: Grep / Bash problem
  • From: Robert Harris
• Re: Grep / Bash problem
  • From: Logan Shaw
• Re: Grep / Bash problem
  • From: Robert Harris
• Re: loading process environment variables
  • From: RickE
• Re: Grep / Bash problem
  • From: Logan Shaw
• Re: Grep / Bash problem
  • From: Logan Shaw
• Re: Writing a unix command prompt
  • From: Stephan Brönnimann
• Re: Grep / Bash problem
  • From: Bit Twister
• Re: Writing a unix command prompt
  • From: Stephan Brönnimann
• Re: Writing a unix command prompt
  • From: Stephan Brönnimann
• Re: Writing a unix command prompt
  • From: Robert Harris
• Re: Grep / Bash problem
  • From: Bill Marcum
• Re: loading process environment variables
  • From: phil-news-nospam
• Re: loading process environment variables
  • From: Mark Hobley
• Re: loading process environment variables
  • From: RickE
• Re: Grep / Bash problem
  • From: John W. Krahn
• Re: Grep / Bash problem
  • From: Elmer Fudd
• Writing a unix command prompt
  • From: repairman2003
• Re: Grep / Bash problem
  • From: Elmer Fudd
• Writing a unix command prompt
  • From: repairman2003
• Re: Grep / Bash problem
  • From: Logan Shaw
• Re: Grep / Bash problem
  • From: Conrad J. Sabatier
• Re: Question: making a blank directory tree from existing tree (OS X 10.4.3)
  • From: Elmer Fudd
• Grep / Bash problem
  • From: Elmer Fudd
• Re: loading process environment variables
  • From: RickE
• Re: loading process environment variables
  • From: Paul Pluzhnikov
• Re: loading process environment variables
  • From: Måns Rullgård
• Re: loading process environment variables
  • From: Pascal Bourguignon
• loading process environment variables
  • From: RickE
• Re: Capturing output from other process
  • From: Barry Margolin
• Re: Capturing output from other process
  • From: Pascal Bourguignon
• Capturing output from other process
  • From: John Smith
• Re: Stack Confusion with Buffer Overflow
  • From: Markus Pitha
• Re: Stack Confusion with Buffer Overflow
  • From: Pascal Bourguignon
• Re: Compiling against libnet
  • From: Casper H . S . Dik
• Re: Stack Confusion with Buffer Overflow
  • From: Casper H . S . Dik
• Re: write(2) trips SIGCHLD after EPIPE why?
  • From: Casper H . S . Dik
• Re: Stack Confusion with Buffer Overflow
  • From: Paul Pluzhnikov
• Re: GDB Break the program execution
  • From: Paul Pluzhnikov
• Re: Stack Confusion with Buffer Overflow
  • From: Barry Margolin
• Re: Compiling against libnet
  • From: Artie Gold
• Re: Lookup between 2 files ( korn shell )
  • From: Logan Shaw
• Re: Evil filename
  • From: Jan Andres
• Re: Lookup between 2 files ( korn shell )
  • From: Chris F.A. Johnson
• Re: Lookup between 2 files ( korn shell )
  • From: pawan_test
• Re: Lookup between 2 files ( korn shell )
  • From: pawan_test
• Re: Lookup between 2 files ( korn shell )
  • From: pawan_test
• Re: Lookup between 2 files ( korn shell )
  • From: Chris F.A. Johnson
• Lookup between 2 files ( korn shell )
  • From: pawan_test
• Re: Lookup between 2 files ( korn shell )
  • From: pawan_test
• Re: Lookup between 2 files ( korn shell )
  • From: Logan Shaw
• Re: Compiling against libnet
  • From: Pigpenn
• Lookup between 2 files ( korn shell )
  • From: pawan_test
• Re: Stack Confusion with Buffer Overflow
  • From: Markus Pitha
• Re: Compiling against libnet
  • From: Cat
• Compiling against libnet
  • From: Pigpenn
• Re: Stack Confusion with Buffer Overflow
  • From: Måns Rullgård
• Re: Stack Confusion with Buffer Overflow
  • From: Markus Pitha
• Re: number sort
  • From: William James
• Re: Stack Confusion with Buffer Overflow
  • From: Måns Rullgård
• Re: Stack Confusion with Buffer Overflow
  • From: Markus Pitha
• Re: Stack Confusion with Buffer Overflow
  • From: Måns Rullgård
• Re: Evil filename
  • From: Jordan Abel
• Re: Stack Confusion with Buffer Overflow
  • From: Pascal Bourguignon
• Stack Confusion with Buffer Overflow
  • From: Markus Pitha
• Re: write(2) trips SIGCHLD after EPIPE why?
  • From: Michael B Allen
• write(2) trips SIGCHLD after EPIPE why?
  • From: Michael B Allen
• Persistent linux program called by web...
  • From: vigotti
• Re: GDB Break the program execution
  • From: Pascal Bourguignon
• Re: GDB Break the program execution
  • From: Salvatore Di Fazio
• Re: GDB Break the program execution
  • From: Salvatore Di Fazio
• Re: GDB Break the program execution
  • From: Salvatore Di Fazio
• Re: Evil filename
  • From: Eric Sosman
• Re: Recursion problem using C
  • From: Giorgos Keramidas
• Re: number sort
  • From: Bill Marcum
• Re: child remains after parent exits
  • From: Paul Pluzhnikov
• Re: Recursion problem using C
  • From: Victor Wagner
• Re: child remains after parent exits
  • From: ivdneut@xxxxxxxxx
• Re: child remains after parent exits
  • From: ivdneut@xxxxxxxxx
• Re: number sort
  • From: Robert Harris
• Re: child remains after parent exits
  • From: Casper H . S . Dik
• Re: child remains after parent exits
  • From: Torgny Lyon
• Re: child remains after parent exits
  • From: Ralf Fassel
• Re: Recursion problem using C
  • From: Dreamcatcher
• Re: GDB Break the program execution
  • From: Paul Pluzhnikov
• number sort
  • From: whcui
• Re: child remains after parent exits
  • From: Paul Pluzhnikov
• Re: Recursion problem using C
  • From: Alex Fraser
• Re: child remains after parent exits
  • From: ivdneut@xxxxxxxxx
• Re: Recursion problem using C
  • From: Pascal Bourguignon
• Re: GDB Break the program execution
  • From: Pascal Bourguignon
• Re: Recursion problem using C
  • From: Thomas Maier-Komor
• Re: encrypt a string and decrypt it back in Unix Shell Programming
  • From: Alex Fraser
• Re: C++ POSIX implementation?
  • From: Maxim Yegorushkin
• Re: Recursion problem using C
  • From: Giorgos Keramidas
• Re: Recursion problem using C
  • From: Casper H . S . Dik
• Re: GDB Break the program execution
  • From: Giorgos Keramidas
• Recursion problem using C
  • From: Dreamcatcher
• GDB Break the program execution
  • From: Salvatore Di Fazio
• child remains after parent exits
  • From: ivdneut@xxxxxxxxx
• Re: encrypt a string and decrypt it back in Unix Shell Programming
  • From: kiranhiremath
• Re: encrypt a string and decrypt it back in Unix Shell Programming
  • From: Alex Fraser
• Re: encrypt a string and decrypt it back in Unix Shell Programming
  • From: Pascal Bourguignon
• encrypt a string and decrypt it back in Unix Shell Programming
  • From: kiranhiremath
• Re: Patching traceroute
  • From: Ian Zimmerman
• Re: C++ POSIX implementation?
  • From: Thomas Maier-Komor
• Re: C++ POSIX implementation?
  • From: Ian Collins
• C++ POSIX implementation?
  • From: darkspleen@xxxxxxxxx
• Re: UDp broadcast problem
  • From: Ian
• Re: Evil filename
  • From: Jan Andres
• Re: Evil filename
  • From: Keith Thompson
• Re: sharing memory with non-children
  • From: Jan Andres
• Re: Evil filename
  • From: Jan Andres
• Re: Patching traceroute
  • From: Thomas Maier-Komor
• Re: fork, exec, and killing a child process manually while it's running
  • From: Jordan Abel
• Re: fork, exec, and killing a child process manually while it's running
  • From: Bjorn Reese
• Re: fork, exec, and killing a child process manually while it's running
  • From: Mark B
• Re: howto interpret error
  • From: Gordon Burditt
• Re: fork, exec, and killing a child process manually while it's running
  • From: Gordon Burditt
• Re: fork, exec, and killing a child process manually while it's running
  • From: Fletcher Glenn
• howto interpret error
  • From: Adam
• Re: Passing Data to a Running Daemon in C
  • From: cicalese
• Patching traceroute
  • From: Pigpenn
• fork, exec, and killing a child process manually while it's running
  • From: simonboland
• Re: Reading data from gps on serial port
  • From: David Schwartz
• Re: Reading data from gps on serial port
  • From: James Brodie
• Re: sharing memory with non-children
  • From: Logan Shaw
• Re: Reading data from gps on serial port
  • From: David Schwartz
• Re: Reading data from gps on serial port
  • From: James Brodie
• Re: Reading data from gps on serial port
  • From: David Schwartz
• Reading data from gps on serial port
  • From: James Brodie
• Re: sharing memory with non-children
  • From: Ian Collins
• Re: Passing Data to a Running Daemon in C
  • From: David Schwartz
• Re: sharing memory with non-children
  • From: Michael Wojcik
• Re: Passing Data to a Running Daemon in C
  • From: cicalese
• Re: Passing Data to a Running Daemon in C
  • From: David Schwartz
• Passing Data to a Running Daemon in C
  • From: cicalese
• Looking for graphics adapter
  • From: lslomer
• Re: The fastest mechanism of IPC
  • From: Logan Shaw
• Re: The fastest mechanism of IPC
  • From: Paul Pluzhnikov
• UDp broadcast problem
  • From: LinuxGuy
• Re: sharing memory with non-children
  • From: Logan Shaw
• Re: sharing memory with non-children
  • From: Maxim Yegorushkin
• Re: How to detect that stdin was closed.
  • From: Hubble
• Re: sharing memory with non-children
  • From: Pascal Bourguignon
• Re: The fastest mechanism of IPC
  • From: Pascal Bourguignon
• Re: sharing memory with non-children
  • From: Logan Shaw
• Re: sharing memory with non-children
  • From: Ian Collins
• Re: The fastest mechanism of IPC
  • From: Paul Pluzhnikov
• Re: The fastest mechanism of IPC
  • From: Rich Teer
• Re: The fastest mechanism of IPC
  • From: Rodrick Brown
• The fastest mechanism of IPC
  • From: atom10jj@xxxxxxxxx
• sharing memory with non-children
  • From: Logan Shaw
• Re: How to detect that stdin was closed.
  • From: Barry Margolin
• Re: broadcast
  • From: Thomas Maier-Komor
• Re: How to detect that stdin was closed.
  • From: Rainer Temme
• How to detect that stdin was closed.
  • From: Karl_Schmitt_1969
• Re: garbage collection questions
  • From: "Nils O. Selåsdal"
• Re: Signal handling
  • From: Paul Pluzhnikov
• Re: Signal handling
  • From: sudeep
• Re: Signal handling
  • From: Paul Pluzhnikov
• Re: Signal handling
  • From: sudeep
• Signal handling
  • From: sudeep
• Re: send() returns 0 but poll() says I can write
  • From: Jan Vidar Krey
• Re: threading in g++
  • From: Paul Pluzhnikov
• Re: send() returns 0 but poll() says I can write
  • From: Jan Vidar Krey
• Re: rename(2) silliness
  • From: phil-news-nospam
• send() returns 0 but poll() says I can write
  • From: Jan Vidar Krey
• Re: threading in g++
  • From: Shark
• Re: Ensuring that a daemon runs as a single instance
  • From: David Schwartz
• Re: Ensuring that a daemon runs as a single instance
  • From: Stefaan A Eeckels
• Re: rename(2) silliness
  • From: Casper H . S . Dik
• Re: rename(2) silliness
  • From: phil-news-nospam
• Re: Ensuring that a daemon runs as a single instance
  • From: Mark Hobley
• Re: Ensuring that a daemon runs as a single instance
  • From: David Schwartz
• Re: Ensuring that a daemon runs as a single instance
  • From: Pascal Bourguignon
• Re: Ensuring that a daemon runs as a single instance
  • From: Logan Shaw
• Re: Ensuring that a daemon runs as a single instance
  • From: Pascal Bourguignon
• Re: Ensuring that a daemon runs as a single instance
  • From: Pascal Bourguignon
• Re: Ensuring that a daemon runs as a single instance
  • From: SM Ryan
• Re: Ensuring that a daemon runs as a single instance
  • From: Mark Hobley
• Re: Ensuring that a daemon runs as a single instance
  • From: Måns Rullgård
• Re: Ensuring that a daemon runs as a single instance
  • From: Pascal Bourguignon
• Ensuring that a daemon runs as a single instance
  • From: Mark Hobley
• Re: writing into FIFO using writev system call
  • From: param
• Re: How to set EOF of a file?
  • From: vansky
• Re: How to set EOF of a file?
  • From: vansky
• Re: UFTP source code
  • From: Barry Margolin
• Re: How to set EOF of a file?
  • From: Barry Margolin
• Re: writing into FIFO using writev system call
  • From: Kurtis D. Rader
• Re: How to implement a function to copy file on LINUX ?
  • From: SM Ryan
• Re: Signal question again. Last one for a while,
  • From: Chad
• Re: UFTP source code
  • From: Mark Hobley
• Re: APUE 2e
  • From: Paul Floyd
• Re: Signal question again. Last one for a while,
  • From: Fletcher Glenn
• Re: How to override compiler
  • From: Fletcher Glenn
• Re: serial ports: how do I know data has been sent?
  • From: Simon Elliott
• Re: How to set EOF of a file?
  • From: Giorgos Keramidas
• Implementing health check using 'Content Switching Module'
  • From: mshetty
• Re: How to set EOF of a file?
  • From: Pascal Bourguignon
• Re: How to set EOF of a file?
  • From: vansky
• Re: How to set EOF of a file?
  • From: vansky
• Re: broadcast
  • From: Pascal Bourguignon
• Re: broadcast
  • From: David Schwartz
• Re: How to set EOF of a file?
  • From: Pascal Bourguignon
• Re: recvfrom multiple servers
  • From: Ian Collins
• Re: How to override compiler
  • From: Logan Shaw
• writing into FIFO using writev system call
  • From: param
• How to override compiler
  • From: seema
• Re: broadcast
  • From: manish
• Re: broadcast
  • From: Gordon Burditt
• broadcast
  • From: manish
• Re: How to set EOF of a file?
  • From: vansky
• recvfrom multiple servers
  • From: manish
• Re: How to set EOF of a file?
  • From: vansky
• Re: How to set EOF of a file?
  • From: Pascal Bourguignon
• Re: How to set EOF of a file?
  • From: vansky
• Re: How to set EOF of a file?
  • From: Pascal Bourguignon
• Signal question again. Last one for a while,
  • From: Chad
• Re: How to set EOF of a file?
  • From: vansky
• Re: APUE 2e
  • From: jfathman
• Re: APUE 2e
  • From: Thomas Dickey
• Re: APUE 2e
  • From: Paul Floyd
• Re: lseek + read = ENOENT
  • From: Pascal Bourguignon
• Re: lseek + read = ENOENT
  • From: Casper H . S . Dik
• write a network bridge
  • From: fabrizio
• lseek + read = ENOENT
  • From: Sam Steingold
• Re: GNU build tools / which version
  • From: gelbeiche
• Re: How to set EOF of a file?
  • From: Pascal Bourguignon
• Re: APUE 2e
  • From: Rich Teer
• Re: APUE 2e
  • From: Rich Teer
• Re: APUE 2e
  • From: Thomas Dickey
• Re: APUE 2e
  • From: Bill Fulton
• Re: receiving broadcast packets
  • From: Maxim Yegorushkin
• Web Service Client
  • From: mturker
• Re: APUE 2e
  • From: Thomas Dickey
• Re: How to implement a function to copy file on LINUX ?
  • From: Geoff Clare
• Re: Unix source code
  • From: "Nils O. Selåsdal"
• Re: Unix source code
  • From: Jordan Abel
• receiving broadcast packets
  • From: LinuxGuy
• Re: How to set EOF of a file?
  • From: "Nils O. Selåsdal"
• Re: How to set EOF of a file?
  • From: vansky
• Re: How to set EOF of a file?
  • From: SM Ryan
• Re: How to implement a function to copy file on LINUX ?
  • From: SM Ryan
• Re: How to set EOF of a file?
  • From: Barry Margolin
• How to set EOF of a file?
  • From: vansky
• Re: UFTP source code
  • From: "Nils O. Selåsdal"
• Re: Unresolved symbol using STLport on HPUX 11
  • From: Paul Pluzhnikov
• Re: Question regarding signals
  • From: Pascal Bourguignon
• Re: How to implement a function to copy file on LINUX ?
  • From: Logan Shaw
• Re: Question regarding signals
  • From: Barry Margolin
• Question regarding signals
  • From: Chad
• Re: GNU build tools / which version
  • From: Måns Rullgård
• GNU build tools / which version
  • From: gelbeiche
• [request for help/code] simple "packet loss" measuring in C/C++
  • From: Krzysiek Orlikowski
• DMalloc and Solaris?
  • From: jim_marshall2268
• UFTP source code
  • From: smarto59
• Re: reading-writing loop
  • From: James Antill
• Re: argp error during include
  • From: Maxim Yegorushkin
• Re: APUE 2e
  • From: Thomas Maier-Komor
• Re: How to implement a function to copy file on LINUX ?
  • From: James Carlson
• Re: serial ports: how do I know data has been sent?
  • From: James Carlson
• argp error during include
  • From: Paulo Matos
• Re: Unix source code
  • From: Thomas Dickey
• Unresolved symbol using STLport on HPUX 11
  • From: Torsten Mueller
• Re: How to implement a function to copy file on LINUX ?
  • From: SM Ryan
• Re: Unix source code
  • From: Victor Wagner
• Re: serial ports: how do I know data has been sent?
  • From: David Schwartz
• Re: serial ports: how do I know data has been sent?
  • From: Mark Hobley
• Re: Unix source code
  • From: Måns Rullgård
• Re: Unix source code
  • From: Rodrick Brown
• Re: serial ports: how do I know data has been sent?
  • From: Simon Elliott
• c++/socket programming development top nyc financial firm
  • From: lf@xxxxxxxxxxxxx
• Re: reading-writing loop
  • From: JH Trauntvein
• Re: How to implement a function to copy file on LINUX ?
  • From: Geoff Clare
• Re: serial ports: how do I know data has been sent?
  • From: James Carlson
• Re: Evil filename
  • From: Michael Paoli
• Re: Evil filename
  • From: Michael Paoli
• Re: rename(2) silliness
  • From: Casper H . S . Dik
• Re: reading-writing loop
  • From: Ian Collins
• Re: reading-writing loop
  • From: Andrei Voropaev
• Re: reading-writing loop
  • From: manish
• Re: rename(2) silliness
  • From: "Nils O. Selåsdal"
• Re: reading-writing loop
  • From: "Nils O. Selåsdal"
• Re: help required
  • From: shady
• reading-writing loop
  • From: manish
• Re: serial ports: how do I know data has been sent?
  • From: David Schwartz
• Re: rename(2) silliness
  • From: Pascal Bourguignon
• Re: broadcasting
  • From: Barry Margolin
• Re: compressing multiple buffers
  • From: Pascal Bourguignon
• Re: rename(2) silliness
  • From: Casper H . S . Dik
• Re: rename(2) silliness
  • From: Casper H . S . Dik
• Re: compressing multiple buffers
  • From: nike
• Re: rename(2) silliness
  • From: Pascal Bourguignon
• Re: rename(2) silliness
  • From: Pascal Bourguignon
• Re: rename(2) silliness
  • From: "Nils O. Selåsdal"
• Re: compressing multiple buffers
  • From: Pascal Bourguignon
• Re: APUE 2e
  • From: Thomas Dickey
• Re: serial ports: how do I know data has been sent?
  • From: Simon Elliott
• rename(2) silliness
  • From: phil-news-nospam
• Re: serial ports: how do I know data has been sent?
  • From: James Carlson
• serial ports: how do I know data has been sent?
  • From: Simon Elliott
• Re: Serial ports and O_NONBLOCK
  • From: Simon Elliott
• Re: Cross compiling from solaris x86 to sparc?
  • From: Thomas Maier-Komor
• Re: broadcasting
  • From: Maxim Yegorushkin
• Re: broadcasting
  • From: manish
• Re: broadcasting
  • From: Maxim Yegorushkin
• broadcasting
  • From: manish
• Re: Finding mac address on solaris 10
  • From: Carlos
• compressing multiple buffers
  • From: nike
• Re: socket question
  • From: Lew Pitcher
• Re: TCP takes a long time to send packet
  • From: David Schwartz
• Re: TCP takes a long time to send packet
  • From: Barry Margolin
• Re: TCP takes a long time to send packet
  • From: David Schwartz
• Re: line by line tracing (gprof? not sure what to use)
  • From: Pascal Bourguignon
• Re: socket question
  • From: Barry Margolin
• socket question
  • From: stathis gotsis
• Re: TCP takes a long time to send packet
  • From: Barry Margolin
• line by line tracing (gprof? not sure what to use)
  • From: lw
• APUE 2e
  • From: Paul Floyd
• Re: memory leak in threaded getpwuid_r() usage
  • From: knt
• Re: Serial ports and O_NONBLOCK
  • From: James Carlson
• Re: memory leak in threaded getpwuid_r() usage
  • From: "Nils O. Selåsdal"
• TCP takes a long time to send packet
  • From: kvartan
• memory leak in threaded getpwuid_r() usage
  • From: knt
• Re: Number of elements in an array.
  • From: Peter Karlsson
• Cross compiling from solaris x86 to sparc?
  • From: John Smith
• Re: help required
  • From: Mark Hobley
• Re: help required
  • From: shady
• Re: Evil filename
  • From: Keith Thompson
• Re: Evil filename
  • From: Pascal Bourguignon
• Re: Evil filename
  • From: Thomas Maier-Komor
• Re: Evil filename
  • From: Keith Thompson
• Re: Unix source code
  • From: Veritas
• Re: How to implement a function to copy file on LINUX ?
  • From: vansky
• Re: How to implement a function to copy file on LINUX ?
  • From: SM Ryan
• Re: Evil filename
  • From: SM Ryan
• Re: How to implement a function to copy file on LINUX ?
  • From: vansky
• Re: How to implement a function to copy file on LINUX ?
  • From: Alex Fraser
• Re: How to implement a function to copy file on LINUX ?
  • From: vansky
• Re: How to implement a function to copy file on LINUX ?
  • From: Måns Rullgård
• How to implement a function to copy file on LINUX ?
  • From: vansky
• Re: Evil filename
  • From: Mark Rafn
• Re: Evil filename
  • From: Rich Teer
• Re: Evil filename
  • From: Keith Thompson
• Re: Evil filename
  • From: David Schwartz
• Re: Evil filename
  • From: Brian Raiter
• Re: Evil filename
  • From: David Schwartz
• Re: Evil filename
  • From: Måns Rullgård
• Re: Evil filename
  • From: Keith Thompson
• Re: Evil filename
  • From: Bjorn Reese
• Re: Evil filename
  • From: Victor Wagner
• Evil filename
  • From: Fletcher Glenn
• Re: Unix source code
  • From: Pascal Bourguignon
• Re: Unix source code
  • From: Torgny Lyon
• Unix source code
  • From: decoy
• Re: [LONG] Error calling function in a shared lib
  • From: Thomas Maier-Komor
• Re: Port Win app to Linux Questions: Memory management and OEM Char
  • From: Roger Leigh
• Re: AC_SYS_LARGEFILE in configure.in but...
  • From: Colossus
• Re: AC_SYS_LARGEFILE in configure.in but...
  • From: Colossus
• Re: Port Win app to Linux Questions: Memory management and OEM Char
  • From: vansky
• Re: Port Win app to Linux Questions: Memory management and OEM Char
  • From: Måns Rullgård
• Port Win app to Linux Questions: Memory management and OEM Char
  • From: vansky
• Re: HELP! Problem getting interposer/LD_PRELOAD working
  • From: ohaya
• Re: Code for lseek
  • From: Roger Leigh
• library names and AC_CHECK_LIB
  • From: gelbeiche
• Re: question about AC_CHECK_LIB
  • From: gelbeiche
• Code for lseek
  • From: Elephant
• Re: Linux Programming Question:: Get Free Disk Info (with path name if possible)
  • From: Artie Gold
• Re: HELP! Problem getting interposer/LD_PRELOAD working
  • From: those who know me have no need of my name
• Re: Perform action until event
  • From: Alex Fraser
• Re: I don't understand why the compiler does this.
  • From: Hubble
• RPC causes linux system to hang hard
  • From: Andrew Falanga
• Re: Fork, Volatile and Alarm
  • From: "Nils O. Selåsdal"
• Re: History of getopt - When was it included in stdio?
  • From: Geoff Clare
• Re: Fork, Volatile and Alarm
  • From: Roger Leigh
• Fork, Volatile and Alarm
  • From: Bill K.
• Re: History of getopt - When was it included in stdio?
  • From: Robert Harris
• Re: Linux Programming Question:: Get Free Disk Info (with path name if possible)
  • From: Roger Leigh
• Re: Linux Programming Question:: Get Free Disk Info (with path name if possible)
  • From: Hubble
• Re: Linux Programming Question:: Get Free Disk Info (with path name if possible)
  • From: vansky
• Re: Linux Programming Question:: Get Free Disk Info (with path name if possible)
  • From: Artie Gold
• Re: bi-directional socket communication
  • From: Barry Margolin
• Linux Programming Question:: Get Free Disk Info (with path name if possible)
  • From: vansky
• Re: bi-directional socket communication
  • From: kiwi
• Re: bi-directional socket communication
  • From: kiwi
• Re: bi-directional socket communication
  • From: David Schwartz
• History of getopt - When was it included in stdio?
  • From: Mark Hobley
• Re: bi-directional socket communication
  • From: David Schwartz
• Re: bi-directional socket communication
  • From: Karl Malbrain
• Re: bi-directional socket communication
  • From: kiwi
• Re: bi-directional socket communication
  • From: Karl Malbrain
• Re: bi-directional socket communication
  • From: kiwi
• Re: bi-directional socket communication
  • From: David Schwartz
• Re: bi-directional socket communication
  • From: Karl Malbrain
• Re: bi-directional socket communication
  • From: kiwi
• Re: bi-directional socket communication
  • From: David Schwartz
• Re: bi-directional socket communication
  • From: kiwi
• Re: question about AC_CHECK_LIB
  • From: Roger Leigh
• Re: bi-directional socket communication
  • From: David Schwartz
• Re: linker error: For a defined method in C++
  • From: joe
• Re: Perform action until event
  • From: lroland@xxxxxxxxx
• Re: bi-directional socket communication
  • From: kiwi
• Re: linker error: For a defined method in C++
  • From: Nikhil
• question about AC_CHECK_LIB
  • From: gelbeiche
• Re: bi-directional socket communication
  • From: Alex Fraser
• Re: linker error: For a defined method in C++
  • From: joe
• Re: bi-directional socket communication
  • From: Robert Harris
• linker error: For a defined method in C++
  • From: Nikhil
• Re: Perform action until event
  • From: Alex Fraser
• bi-directional socket communication
  • From: kiwi
• Re: I don't understand why the compiler does this.
  • From: Paul Pluzhnikov
• Re: I don't understand why the compiler does this.
  • From: Paul Pluzhnikov
• Re: Perform action until event
  • From: Fletcher Glenn
• Perform action until event
  • From: lroland@xxxxxxxxx
• Re: inetd wierd behaviour with instances limit
  • From: Michael Wojcik
• Re: My first .a file, but linker can't resolve references
  • From: lib newbie
• Re: "connect'" returns before server "accept"s
  • From: Michael Wojcik
• Re: Signal race conditions.
  • From: loic-dev
• Re: Copying to another user's directory
  • From: Mark Hobley
• Re: curses and newline
  • From: Simon Elliott
• Re: My first .a file, but linker can't resolve references
  • From: Paul Pluzhnikov
• Re: Valgrind false alarm?
  • From: Paul Pluzhnikov
• My first .a file, but linker can't resolve references
  • From: lib newbie
• Re: I don't understand why the compiler does this.
  • From: Paul Pluzhnikov
• Re: I don't understand why the compiler does this.
  • From: Jordan Abel
• Re: I don't understand why the compiler does this.
  • From: David Schwartz
• Re: I don't understand why the compiler does this.
  • From: Erik Max Francis
• Re: Valgrind false alarm?
  • From: Frank Cusack
• Re: Connection refused problem
  • From: Karl Malbrain
• Re: help required
  • From: Bill Marcum
• Re: I don't understand why the compiler does this.
  • From: David Schwartz
• Re: Copying to another user's directory
  • From: David Schwartz
• Re: Copying to another user's directory
  • From: Måns Rullgård
• Re: Copying to another user's directory
  • From: Mark Hobley
• Re: Valgrind false alarm?
  • From: Måns Rullgård
• Re: I don't understand why the compiler does this.
  • From: Brian Raiter
• Re: Connection refused problem
  • From: nobody
• Re: Unable to read data from file thru mmap() function
  • From: Pascal Bourguignon
• Re: Copying to another user's directory
  • From: lambert54
• Re: Copying to another user's directory
  • From: lambert54
• Re: Connection refused problem
  • From: Alex Fraser
• Connection refused problem
  • From: nobody
• Unable to read data from file thru mmap() function
  • From: Nikhil
• Re: I don't understand why the compiler does this.
  • From: Rob Arthan
• Re: "connect'" returns before server "accept"s
  • From: Andrei Voropaev
• Re: Valgrind false alarm?
  • From: Dag-Erling Smørgrav
• Re: Signal race conditions.
  • From: "Nils O. Selåsdal"
• Re: Sed Routine
  • From: Hubble
• Signal race conditions.
  • From: Sri
• help required
  • From: shady
• Re: Copying to another user's directory
  • From: Keith Thompson
• Re: Copying to another user's directory
  • From: Fletcher Glenn
• Copying to another user's directory
  • From: lambert54
• Re: "connect'" returns before server "accept"s
  • From: Joseph Dionne
• Re: "connect'" returns before server "accept"s
  • From: David Schwartz
• Re: I don't understand why the compiler does this.
  • From: Brian Raiter
• Re: Solaris gcc structure alignment
  • From: John Smith
• Re: Sed Routine
  • From: ~Glynne
• Re: Sed Routine
  • From: Giorgos Keramidas
• Select
  • From: Salvo
• Re: Valgrind false alarm?
  • From: Måns Rullgård
• Re: Valgrind false alarm?
  • From: Frank Cusack
• Re: Solaris gcc structure alignment
  • From: John Smith
• Re: Cross compiler for x86_64
  • From: John Smith
• Re: "connect'" returns before server "accept"s
  • From: chengiz
• Sed Routine
  • From: Jeff Kloek
• Re: C++ Command Line Parsers
  • From: Roger Leigh
• Re: C++ Command Line Parsers
  • From: Jordan Abel
• Re: C++ Command Line Parsers
  • From: Roger Leigh
• Re: problem with recv()- need help !!!
  • From: Fletcher Glenn
• Re: I don't understand why the compiler does this.
  • From: Simon Elliott
• Re: "connect'" returns before server "accept"s
  • From: Andrei Voropaev
• Re: Closing the FILE* from fdopen()
  • From: Casper H . S . Dik
• Re: I don't understand why the compiler does this.
  • From: Erik Max Francis
• Re: how to get thread count
  • From: "Nils O. Selåsdal"
• Re: C++ Command Line Parsers
  • From: Roger Leigh
• [LONG] Error calling function in a shared lib
  • From: ohaya
• I don't understand why the compiler does this.
  • From: Chad
• I don't understand why the compiler does this.
  • From: Chad
• I don't understand why the compiler does this.
  • From: Chad
• Re: Creating library of objectfiles depending on each other
  • From: Paul Pluzhnikov
• Re: Closing the FILE* from fdopen()
  • From: Phil Endecott
• Re: Closing the FILE* from fdopen()
  • From: Måns Rullgård
• Re: Closing the FILE* from fdopen()
  • From: Roger Leigh
• Re: Creating library of objectfiles depending on each other
  • From: John Smith
• Re: Closing the FILE* from fdopen()
  • From: "Nils O. Selåsdal"
• Closing the FILE* from fdopen()
  • From: Phil Endecott
• how to get thread count
  • From: jois . de . vivre
• Re: Creating library of objectfiles depending on each other
  • From: Pascal Bourguignon
• Re: Creating library of objectfiles depending on each other
  • From: Måns Rullgård
• Re: Creating library of objectfiles depending on each other
  • From: "Nils O. Selåsdal"
• Creating library of objectfiles depending on each other
  • From: John Smith
• problem with recv() - need help!!
  • From: michal . shmueli
• problem with recv()- need help !!!
  • From: michal . shmueli
• Re: Solaris gcc structure alignment
  • From: Ulrich Eckhardt
• I don't understand why the compiler does this.
  • From: Chad
• Re: Solaris gcc structure alignment
  • From: Paul Pluzhnikov
• Re: Solaris gcc structure alignment
  • From: John Smith
• Re: Valgrind false alarm?
  • From: Bjorn Reese
• Re: Solaris gcc structure alignment
  • From: Måns Rullgård
• Re: Solaris gcc structure alignment
  • From: John Smith
• Re: HELP! Problem getting interposer/LD_PRELOAD working
  • From: ohaya
• Re: Solaris gcc structure alignment
  • From: Pascal Bourguignon
• Re: Solaris gcc structure alignment
  • From: John Smith
• Re: Solaris gcc structure alignment
  • From: Måns Rullgård
• Re: Solaris gcc structure alignment
  • From: Casper H . S . Dik
• Solaris gcc structure alignment
  • From: John Smith
• Re: HELP! Problem getting interposer/LD_PRELOAD working
  • From: Casper H . S . Dik
• Re: HELP! Problem getting interposer/LD_PRELOAD working
  • From: ohaya
• Re: Finding mac address on solaris 10
  • From: John Smith
• Re: HELP! Problem getting interposer/LD_PRELOAD working
  • From: Casper H . S . Dik
• Re: Valgrind false alarm?
  • From: Bjørn Augestad
• Re: HELP! Problem getting interposer/LD_PRELOAD working
  • From: ohaya
• Re: HELP! Problem getting interposer/LD_PRELOAD working
  • From: ohaya
• Path MTU discovery in IPV6.
  • From: Prathap
• Path MTU discovery in IPV6.
  • From: Prathap
• Path MTU discovery in IPV6.
  • From: Prathap
• Re: HELP! Problem getting interposer/LD_PRELOAD working
  • From: Casper H . S . Dik
• C++ Command Line Parsers
  • From: Paulo Matos
• Re: HELP! Problem getting interposer/LD_PRELOAD working
  • From: ohaya
• HELP! Problem getting interposer/LD_PRELOAD working
  • From: ohaya
• I don't understand why the compiler does this.
  • From: Chad
• Re: Cross compiler for x86_64
  • From: Rich Teer
• Re: weird serial blocking behavior
  • From: Jim Alexander
• m4 macro for boost libs
  • From: gelbeiche
• Re: Valgrind false alarm?
  • From: David Schwartz
• Re: "connect'" returns before server "accept"s
  • From: David Schwartz
• Re: Cross compiler for x86_64
  • From: John Smith
• Re: Valgrind false alarm?
  • From: Jordan Abel
• Re: curses and newline
  • From: Thomas Dickey
• Re: listen() and signal()
  • From: Joseph Dionne
• Re: Valgrind false alarm?
  • From: Bjorn Reese
• Re: Kinds of sharing resources and reentrancy
  • From: Markus Elfring
• Kinds of sharing resources and reentrancy
  • From: Alex Vinokur
• listen() and signal() (was: "connect'" returns before server "accept"s)
  • From: Alex Vinokur
• Re: Valgrind false alarm?
  • From: Måns Rullgård
• Re: "connect'" returns before server "accept"s
  • From: Casper H . S . Dik
• Re: Valgrind false alarm?
  • From: Frank Cusack
• Re: "connect'" returns before server "accept"s
  • From: Kurtis D. Rader
• Re: "connect'" returns before server "accept"s
  • From: Barry Margolin
• Re: Valgrind false alarm?
  • From: Paul Pluzhnikov
• Re: "connect'" returns before server "accept"s
  • From: Joseph Dionne
• Re: TCP/UNIX Question
  • From: DMFH
• "connect'" returns before server "accept"s
  • From: chengiz
• Re: Valgrind false alarm?
  • From: Jordan Abel
• Re: CLOSE_WAIT state on sockets during high volume
  • From: jois . de . vivre
• Re: Valgrind false alarm?
  • From: Bjørn Augestad
• Re: Valgrind false alarm?
  • From: David Schwartz
• Re: Valgrind false alarm?
  • From: Erik Max Francis
• Re: Valgrind false alarm?
  • From: Bjørn Augestad
• Semaphore problem!SoS!!
  • From: aggelos
• Re: Valgrind false alarm?
  • From: Måns Rullgård
• Re: SMTP Proxy design question
  • From: Giorgos Keramidas
• Re: CLOSE_WAIT state on sockets during high volume
  • From: stuart . 9 . wilson
• Re: Valgrind false alarm?
  • From: Bjorn Reese
• Re: CLOSE_WAIT state on sockets during high volume
  • From: Casper H . S . Dik
• Re: CLOSE_WAIT state on sockets during high volume
  • From: stuart . 9 . wilson
• CLOSE_WAIT state on sockets during high volume
  • From: jois . de . vivre
• Re: Close (sockfd) fails
  • From: Rahul
• Re: SMTP Proxy design question
  • From: Rahul
• curses and newline
  • From: Simon Elliott
• Re: Serial ports and O_NONBLOCK
  • From: Simon Elliott
• Re: initialize the global variables in .so files
  • From: Maxim Yegorushkin
• Re: Serial ports and O_NONBLOCK
  • From: Simon Elliott
• Re: Valgrind false alarm?
  • From: "Nils O. Selåsdal"
• Re: Valgrind false alarm?
  • From: Erik Max Francis
• Re: Valgrind false alarm?
  • From: Måns Rullgård
• Re: Serial ports and O_NONBLOCK
  • From: Simon Elliott
• Re: Valgrind false alarm?
  • From: Erik Max Francis
• Re: Valgrind false alarm?
  • From: Bjørn Augestad
• Re: Valgrind false alarm?
  • From: "Nils O. Selåsdal"
• Re: SMTP Proxy design question
  • From: Barry Margolin
• Re: Valgrind false alarm?
  • From: Erik Max Francis
• Re: Valgrind false alarm?
  • From: Paul Pluzhnikov
• Re: Valgrind false alarm?
  • From: Paul Pluzhnikov
• initialize the global variables in .so files
  • From: Vinu
• Re: Serial ports and O_NONBLOCK
  • From: David Schwartz
• Re: socketaddr struct and incomplete type warnings
  • From: Steven Woody
• Re: Valgrind false alarm?
  • From: Erik Max Francis
• Re: Valgrind false alarm?
  • From: grant_holler
• Re: Valgrind false alarm?
  • From: Erik Max Francis
• Re: select function result is inconsistent with description man page
  • From: clayne
• Re: Valgrind false alarm?
  • From: Brian Raiter
• Re: Valgrind false alarm?
  • From: Erik Max Francis
• Re: Serial ports and O_NONBLOCK
  • From: Simon Elliott
• Re: Valgrind false alarm?
  • From: Måns Rullgård
• Re: .so file used as multithreaded
  • From: David Schwartz
• Re: Valgrind false alarm?
  • From: Erik Max Francis
• Re: .so file used as multithreaded
  • From: puzzlecracker
• Serial ports and O_NONBLOCK
  • From: Simon Elliott
• Re: Valgrind false alarm?
  • From: grant_holler
• Valgrind false alarm?
  • From: grant_holler
• Re: socketaddr struct and incomplete type warnings
  • From: Bjørn Augestad
• Re: Solaris SIGSEGV signal handlers
  • From: Norman Black
• Re: regexp
  • From: Maxim Yegorushkin
• Re: .so file used as multithreaded
  • From: Rich Teer
• Re: .so file used as multithreaded
  • From: Rich Teer
• Solaris SIGSEGV signal handlers
  • From: Norman Black
• SMTP Proxy design question
  • From: dgiagio
• Re: regexp
  • From: Imre Palik
• socketaddr struct and incomplete type warnings
  • From: Steven Woody
• Re: How do get a timer in a thread?
  • From: Norman Black
• Re: Need some suggestion on programming on Unix!!
  • From: Pascal Bourguignon
• Re: How to flush write() on stdout ?
  • From: Steven Woody
• Need some suggestion on programming on Unix!!
  • From: seema
• Re: How to flush write() on stdout ?
  • From: "Nils O. Selåsdal"
• Re: regexp
  • From: Maxim Yegorushkin
• Re: How to flush write() on stdout ?
  • From: Maxim Yegorushkin
• Re: How to flush write() on stdout ?
  • From: Steven Woody
• Re: How to flush write() on stdout ?
  • From: "Nils O. Selåsdal"
• Re: How to flush write() on stdout ?
  • From: Bjorn Reese
• How to flush write() on stdout ?
  • From: Steven Woody
• Re: select function result is inconsistent with description man page
  • From: Casper H . S . Dik
• Re: .so file used as multithreaded
  • From: Måns Rullgård
• Re: .so file used as multithreaded
  • From: puzzlecracker
• Re: .so file used as multithreaded
  • From: Rich Teer
• Re: select function result is inconsistent with description man page
  • From: hao
• Re: .so file used as multithreaded
  • From: David Schwartz
• Re: How do get a timer in a thread?
  • From: Steven Woody
• Re: How do get a timer in a thread?
  • From: Steven Woody
• .so file used as multithreaded
  • From: puzzlecracker
• Re: Cross compiler for x86_64
  • From: Valentin Nechayev
• Re: Tracking death of grand-child processes
  • From: Chuck Dillon
• Re: How do get a timer in a thread?
  • From: "Nils O. Selåsdal"
• Re: How do get a timer in a thread?
  • From: "Nils O. Selåsdal"
• Cross compiler for x86_64
  • From: John Smith
• regexp
  • From: Imre Palik
• Re: How do get a timer in a thread?
  • From: Steven Woody
• Re: need information on the following items
  • From: Roger Leigh
• Re: How do get a timer in a thread?
  • From: Norman Black
• Re: Tracking death of grand-child processes
  • From: Chris Friesen
• Re: How do get a timer in a thread?
  • From: Steven Woody
• Re: Close (sockfd) fails
  • From: Casper H . S . Dik
• Re: Close (sockfd) fails
  • From: Barry Margolin
• Re: Tracking death of grand-child processes
  • From: Barry Margolin
• Re: Comparative performance of executables with static and dynamic libraries
  • From: Imre Palik
• Re: Flushing Sockets in C?
  • From: Valentin Nechayev
• Re: Tracking death of grand-child processes
  • From: Rahul
• Close (sockfd) fails
  • From: Rahul
• Re: How do get a timer in a thread?
  • From: Casper H . S . Dik
• Re: How do get a timer in a thread?
  • From: Roland Csaszar
• Re: How do get a timer in a thread?
  • From: "Nils O. Selåsdal"
• How do get a timer in a thread?
  • From: Steven Woody
• Tracking death of grand-child processes
  • From: Henrik Klinkmann
• Re: select function result is inconsistent with description man page
  • From: David Schwartz
• Re: redirected stdout works for bc, not for factor. why?
  • From: Bjorn Reese
• Re: select function result is inconsistent with description man page
  • From: clayne
• Re: select function result is inconsistent with description man page
  • From: hao
• Re: redirected stdout works for bc, not for factor. why?
  • From: Jordan Abel
• Re: need information on the following items
  • From: Pascal Bourguignon
• need information on the following items
  • From: RajneeKanth
• Re: Cygwin + MySQL
  • From: Salvatore Di Fazio
• Re: redirected stdout works for bc, not for factor. why?
  • From: Andrei Voropaev
• Re: Cygwin + MySQL
  • From: Salvatore Di Fazio
• Re: redirected stdout works for bc, not for factor. why?
  • From: Barry Margolin
• Re: Curses Question
  • From: Stan Milam
• Re: Memory Fragmentation Tool
  • From: grant_holler
• Re: Memory Fragmentation Tool
  • From: Paul Pluzhnikov
• Memory Fragmentation Tool
  • From: grant_holler
• Re: regarding unix specific commands
  • From: Roger Leigh
• Re: regarding unix specific commands
  • From: Keith Thompson
• Re: Cygwin + MySQL
  • From: Keith Thompson
• Re: regarding unix specific commands
  • From: joe
• Re: regarding unix specific commands
  • From: Jordan Abel
• Re: regarding unix specific commands
  • From: Jordan Abel
• Re: regarding unix specific commands
  • From: Jordan Abel
• redirected stdout works for bc, not for factor. why?
  • From: gian***z
• Re: regarding unix specific commands
  • From: Roger Leigh
• Re: regarding unix specific commands
  • From: Bjorn Reese
• Re: Cygwin + MySQL
  • From: Salvatore Di Fazio
• Re: regarding unix specific commands
  • From: Pascal Bourguignon
• Re: Curses Question
  • From: Roger Leigh
• Re: Cygwin + MySQL
  • From: CCC
• Re: Cygwin + MySQL
  • From: Salvatore Di Fazio
• Re: Cygwin + MySQL
  • From: CCC
• [OT] Cygwin + MySQL
  • From: Salvatore Di Fazio
• Curses Question
  • From: Brian C
• Re: regarding unix specific commands
  • From: joe
• Re: regarding unix specific commands
  • From: Jordan Abel
• Re: regarding unix specific commands
  • From: Jordan Abel
• Re: regarding unix specific commands
  • From: fidlee
• Re: regarding unix specific commands
  • From: Pascal Bourguignon
• Re: select function result is inconsistent with description man page
  • From: clayne
• Re: regarding unix specific commands
  • From: clayne
• Re: regarding unix specific commands
  • From: fidlee
• Re: regarding unix specific commands
  • From: Barry Margolin
• regarding unix specific commands
  • From: fidlee
• regarding unix specific commands
  • From: fidlee

• Security
• UNIX
• Linux
• Coding
• Usenet

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

unix.derkeiler.com  > Newsgroups  > comp.unix.programmer  > 2006-01