tech-userlevel  

Messages by Thread

• • Re: inetd(8): continue or exit on error? tlaronde
  • Re: inetd(8): continue or exit on error? tlaronde
  • Re: inetd(8): continue or exit on error? Michael van Elst
  • Re: inetd(8): continue or exit on error? David Brownlee
  • Re: inetd(8): continue or exit on error? tlaronde
  • Re: inetd(8): continue or exit on error? Taylor R Campbell
  • Re: inetd(8): continue or exit on error? tlaronde
  • Re: inetd(8): continue or exit on error? Taylor R Campbell
  • Re: inetd(8): continue or exit on error? tlaronde
  • Re: inetd(8): continue or exit on error? Mouse
  • Re: inetd(8): continue or exit on error? tlaronde
  • Re: inetd(8): continue or exit on error? David Holland
  • Re: inetd(8): continue or exit on error? tlaronde
  • Re: inetd(8): continue or exit on error? David Holland
• Re: Sanitizing (canonicalising) the block device name in mount_ffs ?? tlaronde
  • Re: Sanitizing (canonicalising) the block device name in mount_ffs ?? Mouse
  • Re: Sanitizing (canonicalising) the block device name in mount_ffs ?? tlaronde
  • Re: Sanitizing (canonicalising) the block device name in mount_ffs ?? Mouse
  • Re: Sanitizing (canonicalising) the block device name in mount_ffs ?? J. Hannken-Illjes
  • Re: Sanitizing (canonicalising) the block device name in mount_ffs ?? Robert Elz
• [BUG] in src/usr.sbin/inetd (?) tlaronde
• MAXPATHLEN vs PATH_MAX tlaronde
  • Re: MAXPATHLEN vs PATH_MAX David Holland
  • Re: MAXPATHLEN vs PATH_MAX tlaronde
  • Re: MAXPATHLEN vs PATH_MAX David Holland
  • Re: MAXPATHLEN vs PATH_MAX tlaronde
• Bugs in sbin/mount/pathadj.c? tlaronde
• pulling in changes to nsswitch from FreeBSD? Brett Lymn
  • porting nss-pam-ldapd (was: pulling in changes to nsswitch from FreeBSD?) Edgar Fuß
  • Re: pulling in changes to nsswitch from FreeBSD? Taylor R Campbell
  • Re: pulling in changes to nsswitch from FreeBSD? Brett Lymn
• NetBSD 10 and NetBSD 11... tlaronde
  • Re: NetBSD 10 and NetBSD 11... Jason Thorpe
  • Re: NetBSD 10 and NetBSD 11... Martin Husemann
  • Re: NetBSD 10 and NetBSD 11... tlaronde
  • Re: NetBSD 10 and NetBSD 11... tlaronde
  • Re: NetBSD 10 and NetBSD 11... Martin Husemann
  • Re: NetBSD 10 and NetBSD 11... tlaronde
  • Re: NetBSD 10 and NetBSD 11... Jason Thorpe
• unresolvable R_X86_64_NONE relocation against symbol `__sF' Edgar Fuß
  • Re: unresolvable R_X86_64_NONE relocation against symbol `__sF' RVP
  • Re: unresolvable R_X86_64_NONE relocation against symbol `__sF' Edgar Fuß
  • Re: unresolvable R_X86_64_NONE relocation against symbol `__sF' RVP
• Re: using gas/gld from devel/binutils Edgar Fuß
  • Re: using gas/gld from devel/binutils Martin Husemann
• debugging/tracing a setuid program Edgar Fuß
  • Re: debugging/tracing a setuid program Mouse
  • Re: debugging/tracing a setuid program Edgar Fuß
  • Re: debugging/tracing a setuid program Mouse
  • Re: debugging/tracing a setuid program Edgar Fuß
  • Re: debugging/tracing a setuid program Emmanuel Dreyfus
  • Re: debugging/tracing a setuid program Mouse
  • Re: debugging/tracing a setuid program Edgar Fuß
  • Re: debugging/tracing a setuid program Mouse
• Proposed chown(8)/chgrp(1) enhancement Paul Goyette
  • Re: Proposed chown(8)/chgrp(1) enhancement RVP
  • Re: Proposed chown(8)/chgrp(1) enhancement Joerg Sonnenberger
  • Re: Proposed chown(8)/chgrp(1) enhancement наб
  • Re: Proposed chown(8)/chgrp(1) enhancement Paul Goyette
  • Re: Proposed chown(8)/chgrp(1) enhancement Steffen Nurpmeso
• jemalloc profiling tlaronde
  • Re: jemalloc profiling RVP
  • Re: jemalloc profiling tlaronde
• mailx (Re: CVS commit: src/usr.bin/tip) Valery Ushakov
  • Re: mailx (Re: CVS commit: src/usr.bin/tip) Robert Elz
• Re: flock(2): locking against itself? Mouse
  • Re: flock(2): locking against itself? RVP
  • Re: flock(2): locking against itself? Mouse
  • Re: flock(2): locking against itself? David Holland
  • Re: flock(2): locking against itself? David Holland
  • Re: flock(2): locking against itself? Mouse
  • Re: flock(2): locking against itself? Brett Lymn
  • Re: flock(2): locking against itself? Mouse
  • Re: flock(2): locking against itself? Brett Lymn
  • Re: flock(2): locking against itself? Mouse
  • Re: flock(2): locking against itself? RVP
  • Re: flock(2): locking against itself? Mouse
  • Re: flock(2): locking against itself? Brett Lymn
• style: clean up mentions of old-style C Roland Illig
  • Re: style: clean up mentions of old-style C Robert Elz
  • Re: style: clean up mentions of old-style C Valery Ushakov
  • Re: style: clean up mentions of old-style C David Holland
  • Re: style: clean up mentions of old-style C Joerg Sonnenberger
  • Re: style: clean up mentions of old-style C David Holland
  • Re: style: clean up mentions of old-style C Joerg Sonnenberger
  • Re: style: clean up mentions of old-style C Anders Magnusson
  • Re: style: clean up mentions of old-style C Mouse
  • Re: style: clean up mentions of old-style C David Holland
  • Re: style: clean up mentions of old-style C Roland Illig
• Rationale for some rules in style guide Roland Illig
  • Re: Rationale for some rules in style guide Mouse
  • Re: Rationale for some rules in style guide Brett Lymn
  • Re: Rationale for some rules in style guide Joerg Sonnenberger
  • Re: Rationale for some rules in style guide Mouse
  • Re: Rationale for some rules in style guide Michael van Elst
  • Re: Rationale for some rules in style guide Joerg Sonnenberger
  • Re: Rationale for some rules in style guide Carlo Arenas
  • Re: Rationale for some rules in style guide Joerg Sonnenberger
  • Re: Rationale for some rules in style guide Valery Ushakov
  • Re: Rationale for some rules in style guide Brett Lymn
  • Re: Rationale for some rules in style guide Robert Elz
  • Re: Rationale for some rules in style guide Reinoud Zandijk
  • Re: Rationale for some rules in style guide Robert Elz
  • Re: Rationale for some rules in style guide Reinoud Zandijk
  • Re: Rationale for some rules in style guide Robert Elz
• vacation(1) addition Hauke Fath
  • Re: vacation(1) addition Hauke Fath
  • Re: vacation(1) addition David Brownlee
  • Re: vacation(1) addition Hauke Fath
• followup style(5) change David Holland
• mount(8) enhancement Reinoud Zandijk
  • Re: mount(8) enhancement Mouse
  • Re: mount(8) enhancement Mouse
  • Re: mount(8) enhancement Robert Elz
• style(5) proposal: forbid extern in .c Taylor R Campbell
  • Re: style(5) proposal: forbid extern in .c Jason Thorpe
  • Re: style(5) proposal: forbid extern in .c Roland Illig
  • Re: style(5) proposal: forbid extern in .c Jason Thorpe
  • Re: style(5) proposal: forbid extern in .c Paul Goyette
  • Re: style(5) proposal: forbid extern in .c Manuel Bouyer
  • Re: style(5) proposal: forbid extern in .c Izumi Tsutsui
  • Re: style(5) proposal: forbid extern in .c Taylor R Campbell
  • Re: style(5) proposal: forbid extern in .c Izumi Tsutsui
  • Re: style(5) proposal: forbid extern in .c Mouse
  • Re: style(5) proposal: forbid extern in .c Mouse
  • Re: style(5) proposal: forbid extern in .c Valery Ushakov
  • re: style(5) proposal: forbid extern in .c matthew green
  • Re: style(5) proposal: forbid extern in .c Robert Elz
  • Re: style(5) proposal: forbid extern in .c Roland Illig
• GSOC Project Discussion : Audio visualizer for the NetBSD base system Eshan Kelkar
• log2l() missing Thomas Klausner
• SHA3 implementation problem Thomas Klausner
  • Re: SHA3 implementation problem Taylor R Campbell
• make(1): is this a bug or PEBKAC? Mouse
  • Re: make(1): is this a bug or PEBKAC? Roland Illig
  • Re: make(1): is this a bug or PEBKAC? Mouse
  • Re: make(1): is this a bug or PEBKAC? Roland Illig
  • Re: make(1): is this a bug or PEBKAC? Mouse
  • Re: make(1): is this a bug or PEBKAC? David Holland
  • Re: make(1): is this a bug or PEBKAC? Mouse
• Controlling Daemons (inetd or aunchd or relaunchd?) Qingyao Sun
  • Re: Controlling Daemons (inetd or aunchd or relaunchd?) Brett Lymn
  • Re: Controlling Daemons (inetd or aunchd or relaunchd?) Bruno Melo
  • Re: Controlling Daemons (inetd or aunchd or relaunchd?) Steffen Nurpmeso
  • Re: Controlling Daemons (inetd or aunchd or relaunchd?) Steffen Nurpmeso
• mail(1) editline defaults to vi mode? Valery Ushakov
  • Re: mail(1) editline defaults to vi mode? Mouse
  • Re: mail(1) editline defaults to vi mode? Robert Elz
  • Re: mail(1) editline defaults to vi mode? Steffen Nurpmeso
  • Re: mail(1) editline defaults to vi mode? Mouse
  • Re: mail(1) editline defaults to vi mode? David Holland
  • Re: mail(1) editline defaults to vi mode? Mouse
  • Re: mail(1) editline defaults to vi mode? David Holland
• split(1): add '-c' to continue creating files Jan Schaumann
  • Re: split(1): add '-c' to continue creating files Jan Schaumann
  • Re: split(1): add '-c' to continue creating files Ignatios Souvatzis
  • Re: split(1): add '-c' to continue creating files Jan Schaumann
  • Re: split(1): add '-c' to continue creating files Mouse
  • Re: split(1): add '-c' to continue creating files Martin Husemann
  • Re: split(1): add '-c' to continue creating files Edgar Fuß
  • Re: split(1): add '-c' to continue creating files Jan Schaumann
  • Re: split(1): add '-c' to continue creating files Mouse
  • Re: split(1): add '-c' to continue creating files Valery Ushakov
  • Re: split(1): add '-c' to continue creating files Robert Elz
  • Re: split(1): add '-c' to continue creating files Jan Schaumann
• BearSSL: alternative to openSSL? tlaronde
• Ordering of sh(1) pathname expansion Taylor R Campbell
  • Re: Ordering of sh(1) pathname expansion Robert Elz
• split(1): auto-extend suffix length Jan Schaumann
  • Re: split(1): auto-extend suffix length ignatios
  • Re: split(1): auto-extend suffix length Jan Schaumann
• shutdown sequence and UPS poweroff Greg Troxel
  • Re: shutdown sequence and UPS poweroff David Holland
  • Re: shutdown sequence and UPS poweroff David Brownlee
  • Re: shutdown sequence and UPS poweroff Greg Troxel
  • Re: shutdown sequence and UPS poweroff David Brownlee
  • Re: shutdown sequence and UPS poweroff Greg Troxel
• POSIX changes in upcoming (maybe this year) standard (tsort) Robert Elz
  • Re: POSIX changes in upcoming (maybe this year) standard (tsort) наб
• dynamic linker change to handle multiple PT_LOAD segments Christos Zoulas
  • Re: dynamic linker change to handle multiple PT_LOAD segments Jason Thorpe
  • Re: dynamic linker change to handle multiple PT_LOAD segments Christos Zoulas
  • Re: dynamic linker change to handle multiple PT_LOAD segments PHO
• jot: producing too much output? Mouse
  • Re: jot: producing too much output? Robert Elz
  • Re: jot: producing too much output? Mouse
  • Re: jot: producing too much output? Robert Elz
  • Re: jot: producing too much output? Mouse
  • Re: jot: producing too much output? Robert Elz
  • Re: jot: producing too much output? is
  • Re: jot: producing too much output? Mouse
  • Re: jot: producing too much output? Michael van Elst
  • Re: jot: producing too much output? Mouse
  • Re: jot: producing too much output? Robert Elz
  • Re: jot: producing too much output? Martin Neitzel
  • Re: jot: producing too much output? Robert Elz
  • Re: jot: producing too much output? Robert Elz
  • Re: jot: producing too much output? Mouse
• POSIX and pax -s '/re/subst/s' Robert Elz
• regex change enh

• Earlier messages
• Later messages