freebsd-current

• Thread Index

---

• Re: /bin/sh doesn't run autoconf'ied configure scripts correctly
  • From: Mark Kirkwood
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: John Baldwin
• [PATCH] HEADSUP: kbdmux(4)/syscons(4) patch is about to hit the tree
  • From: Maksim Yevmenkin
• -current panics when usb device is detached
  • From: Maksim Yevmenkin
• Re: panic: PHOLD of exiting process
  • From: John Baldwin
• Re: [PATCH] kbdmux(4) update
  • From: Craig Boston
• Re: /bin/sh doesn't run autoconf'ied configure scripts correctly
  • From: Dag-Erling Smørgrav
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• Re: ATI on FreeBSD! FireGL Linux Driver Port
  • From: Alexander I. Mogilny
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• Re: [PATCH] upcoming kbdmux(4) integration
  • From: Jonathan Noack
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on alpha/alpha
  • From: FreeBSD Tinderbox
• world børken ?
  • From: Poul-Henning Kamp
• make buildworld error (/usr/src/lib/libc/rpc/getpublickey.c)
  • From: Mike Jakubik
• Re: [PATCH] possible fix for the runtime going backwards warnings
  • From: Patrick Bowen
• Re: RFC: separate 3dfx_linux module
  • From: Coleman Kane
• Re: bsnmpd breaks buildworld
  • From: Ruslan Ermilov
• Re: bsnmpd breaks buildworld
  • From: Steve Kargl
• Re: HEADSUP: new ath+hal [patch]
  • From: Sam Leffler
• bsnmpd breaks buildworld
  • From: Steve Kargl
• Fatal trap 12: page fault while in kernel mode in 5.5-PRERELEASE with IPSEC/isakmpd
  • From: David Boyd
• Re: RFC: separate 3dfx_linux module
  • From: Coleman Kane
• Re: RFC: separate 3dfx_linux module
  • From: Coleman Kane
• Re: RFC: separate 3dfx_linux module
  • From: Scott Long
• [PATCH] upcoming kbdmux(4) integration
  • From: Maksim Yevmenkin
• Re: HEADSUP: new ath+hal
  • From: Sam Leffler
• Re: RFC: separate 3dfx_linux module
  • From: Scott Long
• [PATCH] ukbd(4) - request for comments
  • From: Maksim Yevmenkin
• Re: HEADSUP: new ath+hal
  • From: Sam Leffler
• 64-bit SNMP interface counters
  • From: Harti Brandt
• Re: RFC: separate 3dfx_linux module
  • From: Scott Long
• Re: Kern_symlink(...) is not setting vattr.va_type
  • From: David Malone
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• Re: HEADSUP: new ath+hal
  • From: Yamamoto Shigeru
• Re: RFC: separate 3dfx_linux module
  • From: Yar Tikhiy
• Kern_symlink(...) is not setting vattr.va_type
  • From: Rohit Jalan
• Re: [PATCH] kbdmux(4) update
  • From: Maksim Yevmenkin
• today's 6.1 would not boot here
  • From: Mikhail T.
• RE: netgroup limits on -current ... [mountd(8)]
  • From: Thyer, Matthew
• Re: /bin/sh doesn't run autoconf'ied configure scripts correctly
  • From: Jeremy Messenger
• Re: /bin/sh doesn't run autoconf'ied configure scripts correctly
  • From: Mark Kirkwood
• Dumping prior to dumpon(8) (Re: cvs commit: src/sbin/dumpon dumpon.8)
  • From: Kris Kennaway
• Re: [PATCH] kbdmux(4) update
  • From: Markus Brueffer
• Re: /bin/sh doesn't run autoconf'ied configure scripts correctly
  • From: Doug Barton
• Optimized kernel copying functions
  • From: Attilio Rao
• Re: USB and clear endpoint stall
  • From: Fredrik Lindberg
• Re: WARNING: attempt to net_add_domain(netgraph) after domainfinalize()
  • From: Gleb Smirnoff
• Re: panic: PHOLD of exiting process
  • From: Peter Holm
• Re: /bin/sh doesn't run autoconf'ied configure scripts correctly
  • From: Dag-Erling Smørgrav
• Re: /bin/sh doesn't run autoconf'ied configure scripts correctly
  • From: Kris Kennaway
• /bin/sh doesn't run autoconf'ied configure scripts correctly
  • From: Kash Pande
• Re: USB and clear endpoint stall
  • From: Ian Dowse
• "fsck -fB" panics: snapacct_ufs2: bad block
  • From: Peter Jeremy
• Re: [PATCH] kbdmux(4) update
  • From: Maksim Yevmenkin
• Re: RFC: separate 3dfx_linux module
  • From: Coleman Kane
• Re: [PATCH] kbdmux(4) update
  • From: Scott Long
• Re: [PATCH] kbdmux(4) update
  • From: Markus Brueffer
• Re: [PATCH] kbdmux(4) update
  • From: Maksim Yevmenkin
• Re: [PATCH] kbdmux(4) update
  • From: Maksim Yevmenkin
• Re: RFC: separate 3dfx_linux module
  • From: Scott Long
• ATA DMA dump failures: take 2
  • From: Dmitry Pryanishnikov
• Re: [PATCH] kbdmux(4) update
  • From: Markus Brueffer
• RFC: separate 3dfx_linux module
  • From: Yar Tikhiy
• Re: calcru: runtime went backwards
  • From: Kazuaki Oda
• [PATCH] kbdmux(4) update
  • From: Maksim Yevmenkin
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Jason Evans
• Re: calcru: runtime went backwards
  • From: David Xu
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Poul-Henning Kamp
• Re: CFT: src/tools/tools/npcus
  • From: John Baldwin
• Re: CFT: src/tools/tools/npcus
  • From: Sam Leffler
• CFT: src/tools/tools/npcus
  • From: Sam Leffler
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Jason Evans
• Re: panic: PHOLD of exiting process
  • From: John Baldwin
• multimedia/libxine fails with recent autotools update
  • From: Stephane E. Potvin
• panic: PHOLD of exiting process
  • From: Peter Holm
• Re: em(4) stops forwarding
  • From: Michal Mertl
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Robert Watson
• Re: typo in dump manual?
  • From: Giorgos Keramidas
• Re: typo in dump manual?
  • From: Giorgos Keramidas
• typo in dump manual?
  • From: Andriy Tkachuk
• Re: FreeBSD-Current on hp nc6220
  • From: Scot Hetzel
• Re: ping (DUP!) in FreeBSD 5.4
  • From: Nik
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Peter Fraser
• Re: ping (DUP!) in FreeBSD 5.4
  • From: Dmitry Pryanishnikov
• Re: ping (DUP!) in FreeBSD 5.4
  • From: Jim Thompson
• Re: ping (DUP!) in FreeBSD 5.4
  • From: Dmitry Pryanishnikov
• Re: Networking Puzzle
  • From: Marcin Jessa
• Re: calcru: runtime went backwards
  • From: Kazuaki Oda
• FreeBSD-Current on hp nc6220
  • From: eric
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Mike Jakubik
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Mark Kirkwood
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Mike Jakubik
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Mark Kirkwood
• ping (DUP!) in FreeBSD 5.4
  • From: Nik
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Jonathan Noack
• Re: Networking Puzzle
  • From: Alexandre \"Sunny\" Kovalenko
• Re: The sixty second pmc howto
  • From: Joseph Koshy
• calcru: runtime went backwards
  • From: David Xu
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Robert Watson
• Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Peter Fraser
• Page fault in thr_exit()
  • From: Kris Kennaway
• Re: The sixty second pmc howto
  • From: Andrew Gallatin
• Re: The sixty second pmc howto
  • From: Robert Watson
• Re: The sixty second pmc howto
  • From: Andrew Gallatin
• The sixty second pmc howto
  • From: Robert Watson
• Networking Puzzle
  • From: Cian Hughes
• Re: netgroup limits on -current ... [mountd(8)]
  • From: Wilkinson, Alex
• WARNING: attempt to net_add_domain(netgraph) after domainfinalize()
  • From: Mike Jakubik
• Re: [PATCH] possible fix for the runtime going backwards warnings
  • From: Kris Kennaway
• Re: partition for GELI disk
  • From: Dag-Erling Smørgrav
• Re: [PATCH] possible fix for the runtime going backwards warnings
  • From: Andrey Chernov
• Re: [PATCH] possible fix for the runtime going backwards warnings
  • From: John Baldwin
• Re: dhclient existing when run early in startup
  • From: Tobias Roth
• Re: mount_smbfs trouble after cvsup
  • From: Gavin Atkinson
• Re: [PATCH] possible fix for the runtime going backwards warnings
  • From: John Baldwin
• Re: dhclient existing when run early in startup
  • From: Kevin Oberman
• Re: [PATCH] possible fix for the runtime going backwards warnings
  • From: Kazuaki Oda
• Re: [PATCH] possible fix for the runtime going backwards warnings
  • From: Andrey Chernov
• Re: [PATCH] possible fix for the runtime going backwards warnings
  • From: John Baldwin
• Re: partition for GELI disk
  • From: Ulrich Spoerlein
• Re: Bad code in rcorder(8) (Was: Re: New RCorder: abi loaded too late)
  • From: Ulrich Spoerlein
• Re: Bad code in rcorder(8) (Was: Re: New RCorder: abi loaded too late)
  • From: Divacky Roman
• Re: [PATCH] possible fix for the runtime going backwards warnings
  • From: Andrey Chernov
• Re: proposed /sbin/init permission change
  • From: Thomas Quinot
• proposed /sbin/init permission change
  • From: Luigi Rizzo
• Re: [PATCH] possible fix for the runtime going backwards warnings
  • From: Kris Kennaway
• Re: Bad code in rcorder(8) (Was: Re: New RCorder: abi loaded too late)
  • From: Doug Barton
• Re: NanoBSD don't boot.
  • From: Dag-Erling Smørgrav
• Re: Can't resolve defined(?) symbol after ELF symbol versioning
  • From: othermark
• Re: partition for GELI disk
  • From: Pawel Jakub Dawidek
• Re: GELI boot on root partition
  • From: Balgansuren Batsukh
• Re: partition for GELI disk
  • From: Balgansuren Batsukh
• NanoBSD don't boot.
  • From: Peter Ankerstål
• Re: partition for GELI disk
  • From: Ulrich Spoerlein
• Re: Bad code in rcorder(8) (Was: Re: New RCorder: abi loaded too late)
  • From: Ulrich Spoerlein
• Re: [PATCH] possible fix for the runtime going backwards warnings
  • From: Stefan Ehmann
• [PATCH] possible fix for the runtime going backwards warnings
  • From: John Baldwin
• Re: GELI boot on root partition
  • From: Alex Dupre
• partition for GELI disk
  • From: Balgansuren Batsukh
• GELI boot on root partition
  • From: Balgansuren Batsukh
• Re: netgroup limits on -current ... [mountd(8)]
  • From: Vladimir Egorin
• kernel panic / acpi problem.
  • From: Martin Wilke
• Re: mount_smbfs trouble after cvsup
  • From: Tai-hwa Liang
• Re: Lots of calcru: runtime went backwards, never saw it before
  • From: Kris Kennaway
• Re: Lots of calcru: runtime went backwards, never saw it before
  • From: Andrey Chernov
• mount_smbfs trouble after cvsup
  • From: Bachilo Dmitry
• Re: dhclient existing when run early in startup
  • From: Tobias Roth
• Re: dhclient existing when run early in startup
  • From: Kevin Oberman
• Re: dhclient existing when run early in startup
  • From: Brooks Davis
• netgroup limits on -current ... [mountd(8)]
  • From: Wilkinson, Alex
• Re: Lots of calcru: runtime went backwards, never saw it before
  • From: Jiawei Ye
• dhclient existing when run early in startup
  • From: Kevin Oberman
• Re: Lots of calcru: runtime went backwards, never saw it before
  • From: Giorgos Keramidas
• Re: GELI question
  • From: Pawel Jakub Dawidek
• Re: Lots of calcru: runtime went backwards, never saw it before
  • From: Kris Kennaway
• Re: Lots of calcru: runtime went backwards, never saw it before
  • From: Andrey Chernov
• Re: Lots of calcru: runtime went backwards, never saw it before
  • From: Andrey Chernov
• Re: Lots of calcru: runtime went backwards, never saw it before
  • From: Kris Kennaway
• Re: Lots of calcru: runtime went backwards, never saw it before
  • From: Giorgos Keramidas
• Lots of calcru: runtime went backwards, never saw it before
  • From: Andrey Chernov
• RE: no dump on a gmirror ?
  • From: Larry Rosenman
• Re: no dump on a gmirror ?
  • From: Marcin Jessa
• Re: panic: Trying sleep, but thread marked as sleeping prohibited
  • From: Christian Brueffer
• Re: -current is sluggish
  • From: Kris Kennaway
• Re: kernel panic / acpi problem.
  • From: Martin Wilke
• RE: no dump on a gmirror ?
  • From: Larry Rosenman
• Re: no dump on a gmirror ?
  • From: Doug Barton
• Re: rwlock patch for bridge
  • From: John Baldwin
• Re: It still here... panic: ufs_dirbad: bad dir
  • From: Matthew Dillon
• RE: no dump on a gmirror ?
  • From: Larry Rosenman
• Re: -current is sluggish
  • From: Kevin Oberman
• Re: -current is sluggish
  • From: Yar Tikhiy
• Re: kernel panic / acpi problem.
  • From: Ben Kaduk
• Re: attaching a keyboard later
  • From: Alain Hebert
• Re: attaching a keyboard later
  • From: Chuck Swiger
• Re: bge(4) problem
  • From: Geoffrey Giesemann
• Re: attaching a keyboard later
  • From: Brian Candler
• Re: bge(4) problem
  • From: David Barbero
• Re: attaching a keyboard later
  • From: Chuck Swiger
• Re: bge(4) problem
  • From: Peter Ross
• Re: attaching a keyboard later
  • From: Brian Candler
• Re: bge(4) problem
  • From: Gleb Smirnoff
• kernel panic / acpi problem.
  • From: Martin Wilke
• Re: em0: Fatal trap 12: page fault while in kernel mode
  • From: Gleb Smirnoff
• Re: em0: Fatal trap 12: page fault while in kernel mode
  • From: Denis Shaposhnikov
• bge(4) problem
  • From: Peter Ross
• Re: KDE 3.5.0 seems much chubbier than 3.4.2
  • From: Daniel O'Connor
• Re: attaching a keyboard later
  • From: Alain Hebert
• no dump on a gmirror ?
  • From: Thierry Herbelot
• Re: em0: Fatal trap 12: page fault while in kernel mode
  • From: Denis Shaposhnikov
• Re: MFC of "Unbreak Promise SATAII/150 controllers" ?
  • From: Thierry Herbelot
• Re: em0: Fatal trap 12: page fault while in kernel mode
  • From: Gleb Smirnoff
• em0: Fatal trap 12: page fault while in kernel mode
  • From: Denis Shaposhnikov
• Re: Bad system call (core dumped)
  • From: Robert Watson
• Re: Bad system call (core dumped)
  • From: Joseph Koshy
• Bad code in rcorder(8) (Was: Re: New RCorder: abi loaded too late)
  • From: Doug Barton
• Re: MFC of "Unbreak Promise SATAII/150 controllers" ?
  • From: Søren Schmidt
• Re: USB and clear endpoint stall
  • From: Ian Dowse
• Re: Is HEAD broken for anybody else?
  • From: Giorgos Keramidas
• Re: reversed behavior with nsswitch.conf
  • From: Alexander Leidinger
• USB and clear endpoint stall
  • From: Fredrik Lindberg
• Re: reversed behavior with nsswitch.conf
  • From: Tim Dettloff
• Re: MFC of "Unbreak Promise SATAII/150 controllers" ?
  • From: Thierry Herbelot
• Re: reversed behavior with nsswitch.conf
  • From: Alexander Leidinger
• Re: attaching a keyboard later
  • From: Brian Candler
• Re: MFC of "Unbreak Promise SATAII/150 controllers" ?
  • From: Søren Schmidt
• Re: New RCorder: abi loaded too late
  • From: Divacky Roman
• attaching a keyboard later
  • From: Oliver Lehmann
• MFC of "Unbreak Promise SATAII/150 controllers" ?
  • From: Thierry Herbelot
• Re: Is HEAD broken for anybody else?
  • From: Bjoern A. Zeeb
• Re: Is HEAD broken for anybody else?
  • From: Giorgos Keramidas
• Re: rwlock patch for bridge
  • From: Andrew Thompson
• Re: Is HEAD broken for anybody else?
  • From: Giorgos Keramidas
• Re: Is HEAD broken for anybody else?
  • From: Giorgos Keramidas
• Re: Changes to IPFW start up scripts. [updated[
  • From: Vulpes Velox
• Is HEAD broken for anybody else?
  • From: Giorgos Keramidas
• Re: reversed behavior with nsswitch.conf
  • From: Joel Gunderson
• Changes to IPFW start up scripts.
  • From: Vulpes Velox
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Jason Evans
• Re: New RCorder: abi loaded too late
  • From: Doug Barton
• GELI question
  • From: Balgansuren Batsukh
• Re: reversed behavior with nsswitch.conf
  • From: Alexander Leidinger
• Re: buildworld problem
  • From: Vincent Blondel
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Brian Candler
• Re: It still here... panic: ufs_dirbad: bad dir
  • From: Matthew Dillon
• Re: -current is sluggish
  • From: Maksim Yevmenkin
• Re: It still here... panic: ufs_dirbad: bad dir
  • From: Peter Jeremy
• Re: It still here... panic: ufs_dirbad: bad dir
  • From: Matthew Dillon
• Re: LSI Trouble
  • From: Brian K. White
• Re: buildworld problem
  • From: Joseph Koshy
• Re: New RCorder: abi loaded too late
  • From: Jason Evans
• Re: New RCorder: abi loaded too late
  • From: Doug Barton
• Re: New RCorder: abi loaded too late
  • From: Doug Barton
• Re: New RCorder: abi loaded too late
  • From: Brooks Davis
• Re: New RCorder: abi loaded too late
  • From: Doug Barton
• LSI Trouble
  • From: Anton Nikiforov
• sio interrupt-level buffer overflows?
  • From: Goran Gajic
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Jason Evans
• Re: Virtual memory consumption (both user and kernel) inmodern CURRENT
  • From: David Leimbach
• Re: Virtual memory consumption (both user and kernel) inmodern CURRENT
  • From: Brian K. White
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Mike Jakubik
• CFT: wpa_supplicant key handling fix
  • From: Sam Leffler
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Jason Evans
• Re: rwlock patch for bridge
  • From: John Baldwin
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Mike Jakubik
• Re: New RCorder: abi loaded too late
  • From: Brooks Davis
• Re: HEADSUP: new ath+hal
  • From: Sam Leffler
• Re: HEADSUP: new ath+hal
  • From: Sam Leffler
• Re: buildworld problem
  • From: Vincent Blondel
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Jason Evans
• Re: reversed behavior with nsswitch.conf
  • From: Foo
• New RCorder: abi loaded too late
  • From: Xin LI
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Dmitry Pryanishnikov
• Re: buildworld broken with NO_MODULES= and MODULES_WITH_WORLD=
  • From: Boris Samorodov
• Re: buildworld broken with NO_MODULES= and MODULES_WITH_WORLD=
  • From: Ruslan Ermilov
• Re: memguard monitoring of more than 1 memory_type?
  • From: Pawel Jakub Dawidek
• Re: buildworld broken with NO_MODULES= and MODULES_WITH_WORLD=
  • From: Boris Samorodov
• Re: buildworld broken with NO_MODULES= and MODULES_WITH_WORLD=
  • From: Ruslan Ermilov
• buildworld broken with NO_MODULES= and MODULES_WITH_WORLD=
  • From: Boris Samorodov
• Re: HEADSUP: new ath+hal
  • From: Michal Mertl
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Tarasov Alexey
• panic at reboot (spin lock held too long)
  • From: Thierry Herbelot
• Re: buildworld problem
  • From: Joseph Koshy
• Re: dc no worky in -current
  • From: M. Warner Losh
• Re: HEADSUP: new ath+hal
  • From: Yamamoto Shigeru
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: David Xu
• Re: KDE 3.5.0 seems much chubbier than 3.4.2
  • From: Jason Evans
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Kris Kennaway
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Kris Kennaway
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Mike Jakubik
• Re: hosts.allow default behaviour: IPv6 on its own lines
  • From: Warner Losh
• Re: options for centralized 'passwd' database for a diskless lab ?
  • From: Stefan Bethke
• Re: buildworld problem
  • From: Vincent Blondel
• Re: hosts.allow default behaviour: IPv6 on its own lines
  • From: Hajimu UMEMOTO
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Giorgos Keramidas
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Dmitry Pryanishnikov
• Re: buildworld problem
  • From: Brian Candler
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Brian Candler
• Re: KDE 3.5.0 seems much chubbier than 3.4.2
  • From: Daniel O'Connor
• hosts.allow default behaviour: IPv6 on its own lines
  • From: Dmitry Morozovsky
• reversed behavior with nsswitch.conf
  • From: Alexander Leidinger
• Re: sshd/telnetd stops responding under load
  • From: Peter Jeremy
• Re: dc no worky in -current
  • From: Benzi Mizrahi
• Re: HEADSUP: new ath+hal
  • From: Sam Leffler
• Re: buildworld problem
  • From: Joseph Koshy
• Re: Cyrus-imap preformance share on fix
  • From: Mike Jakubik
• Re: HEADSUP: new ath+hal
  • From: Yamamoto Shigeru
• Cyrus-imap preformance share on fix
  • From: Benjamin D Adams
• dc no worky in -current
  • From: Daniel Eischen
• sshd/telnetd stops responding under load
  • From: Jiawei Ye
• Re: panic: Trying sleep, but thread marked as sleeping prohibited
  • From: Suleiman Souhlal
• rwlock patch for bridge
  • From: Andrew Thompson
• Re: calcru: runtime went backwards
  • From: Poul-Henning Kamp
• buildworld problem
  • From: Vincent Blondel
• Re: calcru: runtime went backwards
  • From: Giorgos Keramidas
• Re: Extended Attributes API
  • From: Joerg Schilling
• Re: Extended Attributes API
  • From: Jason Evans
• Re: calcru: runtime went backwards
  • From: Jiawei Ye
• Re: Extended Attributes API
  • From: Harti Brandt
• Re: Extended Attributes API
  • From: Geoffrey Giesemann
• Re: Extended Attributes API
  • From: Michael Reifenberger
• Extended Attributes API
  • From: Geoffrey Giesemann
• Re: options for centralized 'passwd' database for a diskless lab ?
  • From: Danny Braniss
• Re: panic: Trying sleep, but thread marked as sleeping prohibited
  • From: Christian Brueffer
• IMAP problem I found on another mailing list
  • From: Benjamin D Adams
• Re: Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: David Xu
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• Virtual memory consumption (both user and kernel) in modern CURRENT
  • From: Dmitry Pryanishnikov
• Re: panic: Trying sleep, but thread marked as sleeping prohibited
  • From: Ian Dowse
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on alpha/alpha
  • From: FreeBSD Tinderbox
• Re: panic: Trying sleep, but thread marked as sleeping prohibited
  • From: Mark Tinguely
• Re: Buildworld broken on amd64
  • From: Doug Ambrisko
• Re: Buildworld broken on amd64
  • From: Steve Kargl
• Buildworld broken on amd64
  • From: Steve Kargl
• panic: Trying sleep, but thread marked as sleeping prohibited
  • From: Christian Brueffer
• Regarding the diagnostic utility for the PCI bus
  • From: karthy shanmugavel
• Re: memtest - an idea
  • From: Holger Kipp
• Re: options for centralized 'passwd' database for a diskless lab ?
  • From: Chuck Swiger
• Re: memtest - an idea
  • From: Peter Jeremy
• memtest - an idea
  • From: Vladimir Konrad
• options for centralized 'passwd' database for a diskless lab ?
  • From: Luigi Rizzo
• Re: Error in make buildkernel from todays -current
  • From: Ruslan Ermilov
• Error in make buildkernel from todays -current
  • From: Tarc
• (idle) USB generates interrupts as fast as they can be serviced
  • From: Ian FREISLICH
• Re: Error in make buildworld from todays -current
  • From: Doug Barton
• Re: Bad system call (core dumped)
  • From: David Xu
• Re: Bad system call (core dumped)
  • From: Joseph Koshy
• Re: Bad system call (core dumped)
  • From: David Xu
• Re: Bad system call (core dumped)
  • From: Bachilo Dmitry
• Re: Bad system call (core dumped)
  • From: Joseph Koshy
• Re: Bad system call (core dumped)
  • From: Bachilo Dmitry
• Re: Bad system call (core dumped)
  • From: Joseph Koshy
• Re: Bad system call (core dumped)
  • From: Bachilo Dmitry
• Re: bsd-airtools
  • From: Sean Chittenden
• [head tinderbox] failure on sparc64/sparc64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• Re: bsd-airtools
  • From: Sam Leffler
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• [head tinderbox] failure on alpha/alpha
  • From: FreeBSD Tinderbox
• Error in make buildworld from todays -current
  • From: Patrick Bowen
• Re: bsd-airtools
  • From: Patrick Bowen
• Re: HEADSUP: new ath+hal
  • From: Marcin Jessa
• Re: HEADSUP: new ath+hal
  • From: Patrick Bowen
• HEADSUP: new ath+hal
  • From: Sam Leffler
• Re: acpica memory leak?
  • From: Jung-uk Kim
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Giorgos Keramidas
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Andrew Gallatin
• Re: insta-panic in softclock() -> acctwatch()
  • From: Giorgos Keramidas
• Re: insta-panic in softclock() -> acctwatch()
  • From: Gleb Smirnoff
• patchset-8-fix1 for 6.x release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Daichi GOTO
• Re: Malloc bugs exhibited in ports/mail/dovecot
  • From: Robin Breathe
• insta-panic in softclock() -> acctwatch()
  • From: Giorgos Keramidas
• Re: calcru: runtime went backwards
  • From: Poul-Henning Kamp
• Re: calcru: runtime went backwards
  • From: Kris Kennaway
• Re: calcru: runtime went backwards
  • From: Yuriy Tsibizov
• Re: Radio Streaming
  • From: Ulrich Spoerlein
• Radio Streaming
  • From: Vincent Blondel
• Re: calcru: runtime went backwards
  • From: Poul-Henning Kamp
• Re: calcru: runtime went backwards
  • From: Yuriy Tsibizov
• Re: calcru: runtime went backwards
  • From: Poul-Henning Kamp
• Re: A problem on IBM Netfinity 5000
  • From: Brian Candler
• Wall broken with sysutils/screen
  • From: Ceri Davies
• Re: calcru: runtime went backwards
  • From: Niki Denev
• Re: calcru: runtime went backwards
  • From: Kris Kennaway
• Re: calcru: runtime went backwards
  • From: Yuriy Tsibizov
• calcru: runtime went backwards
  • From: Yuriy Tsibizov
• Re: Atheros and new hal
  • From: Dillon Kass
• Atheros and new hal
  • From: gusmao
• Re: [jakub@redhat.com:Linking against libpthread via -pthread?
  • From: Daniel Eischen
• Error building acpi_wakecode.S
  • From: James Bowman
• Re: [jakub@redhat.com:Linking against libpthread via -pthread?
  • From: Alexander Kabaev
• A problem on IBM Netfinity 5000
  • From: FreeBSDer China
• Re: [jakub@redhat.com:Linking against libpthread via -pthread?
  • From: Daniel Eischen
• GELI improvements.
  • From: Pawel Jakub Dawidek
• Re: Portsnap support on CURRENT
  • From: Martin Wilke
• Re: acpica memory leak?
  • From: Morten Rodal
• Re: [jakub@redhat.com:Linking against libpthread via -pthread?
  • From: Steve Kargl
• Re: [jakub@redhat.com:Linking against libpthread via -pthread?
  • From: Daniel Eischen
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Anish Mistry
• Re: Portsnap support on CURRENT
  • From: Colin Percival
• Re: [jakub@redhat.com:Linking against libpthread via -pthread?
  • From: Alexander Kabaev
• Re: -current is sluggish
  • From: Giorgos Keramidas
• Re: -current is sluggish
  • From: Jonathan Noack
• Re: -current is sluggish
  • From: Giorgos Keramidas
• Re: ath patch+hal for test
  • From: Patrick Bowen
• Re: -current is sluggish
  • From: Krzysztof Kowalik
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Robert Watson
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Robert Watson
• Re: -current is sluggish
  • From: Jonathan Noack
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Kris Kennaway
• Re: -current is sluggish
  • From: Krzysztof Kowalik
• Re: [jakub@redhat.com:Linking against libpthread via -pthread?
  • From: Steve Kargl
• Re: -current is sluggish
  • From: Maksim Yevmenkin
• Re: -current is sluggish
  • From: Max Laier
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Kris Kennaway
• Re: -current is sluggish
  • From: Andrew R. Reiter
• -current is sluggish
  • From: Maksim Yevmenkin
• Re: Portsnap support on CURRENT
  • From: Kris Kennaway
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Giorgos Keramidas
• Re: Portsnap support on CURRENT
  • From: Freddie Cash
• Re: Portsnap support on CURRENT
  • From: Scott Robbins
• Portsnap support on CURRENT
  • From: Paul Mather
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Julian Elischer
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Poul-Henning Kamp
• Re: [jakub@redhat.com:Linking against libpthread via -pthread?
  • From: Dan Nelson
• Re: [jakub@redhat.com:Linking against libpthread via -pthread?
  • From: Steve Kargl
• Re: [jakub@redhat.com:Linking against libpthread via -pthread?
  • From: Dan Nelson
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Andrew Gallatin
• Re: patchset-8 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Dario Freni
• [jakub@redhat.com:Linking against libpthread via -pthread?
  • From: Steve Kargl
• hesiod.h problem while upgrading to current
  • From: Michael Jejer
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Poul-Henning Kamp
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Andrew Gallatin
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Andrew Gallatin
• [panic] Fatal trap 12: page fault while in kernel mode
  • From: Daniel Gerzo
• Re: Bad system call (core dumped)
  • From: Fernan Aguero
• Re: FreeBSD showing version number upon login
  • From: Brian Candler
• Re: Bad system call (core dumped)
  • From: Kris Kennaway
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Poul-Henning Kamp
• Re: memguard monitoring of more than 1 memory_type?
  • From: Peter Jeremy
• Bad system call (core dumped)
  • From: Bachilo Dmitry
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Mike Jakubik
• Re: patchset-8 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Cy Schubert
• Re: FreeBSD Port to UltraSparc T1 "Niagara"
  • From: Doug White
• Re: [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Poul-Henning Kamp
• [TEST/REVIEW] cpu time accounting patch, step 2
  • From: Poul-Henning Kamp
• Re: FreeBSD showing version number upon login
  • From: alex
• Feature request for IPFW
  • From: Erik Nørgaard
• Re: memguard monitoring of more than 1 memory_type?
  • From: Pawel Jakub Dawidek
• Re: patchset-8 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Dario Freni
• Re: FreeBSD showing version number upon login
  • From: Matthew D. Fuller
• Re: FreeBSD showing version number upon login
  • From: Kris Kennaway
• Re: FreeBSD showing version number upon login
  • From: alex
• Re: FreeBSD showing version number upon login
  • From: Kris Kennaway
• Re: FreeBSD Port to UltraSparc T1 "Niagara"
  • From: Joao Barros
• Re: FreeBSD showing version number upon login
  • From: Chris
• Re: FreeBSD showing version number upon login
  • From: Andrew R. Reiter
• Re: Panic In mi_switch+0x7e
  • From: John Baldwin
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: John Baldwin
• Re: semi-interesting panic when rebooting
  • From: John Baldwin
• Re: FreeBSD showing version number upon login
  • From: Frank Altpeter
• FreeBSD Port to UltraSparc T1 "Niagara"
  • From: Ricardo A. Reis
• patchset-8 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Daichi GOTO
• Re: FreeBSD showing version number upon login
  • From: Brian Candler
• Re: 7.0-CURRENT Hang
  • From: Cy Schubert
• Re: FreeBSD showing version number upon login
  • From: Kurt Jaeger
• RE: FreeBSD showing version number upon login
  • From: Darren Pilgrim
• Re: ath patch+hal for test
  • From: Beech Rintoul
• Re: FreeBSD showing version number upon login
  • From: Marcin Jessa
• Re: FreeBSD showing version number upon login
  • From: Poul-Henning Kamp
• Re: FreeBSD showing version number upon login
  • From: Frank Altpeter
• Re: FreeBSD showing version number upon login
  • From: Marcin Jessa
• Re: 7.0-CURRENT Hang
  • From: Yar Tikhiy
• Re: FreeBSD showing version number upon login
  • From: alex
• Re: FreeBSD showing version number upon login
  • From: Marcin Jessa
• Re: cvs commit: src/sys/dev/em if_em.c if_em.h
  • From: Gleb Smirnoff
• Re: FreeBSD showing version number upon login
  • From: Kris Kennaway
• FreeBSD showing version number upon login
  • From: Alex
• Re: ath patch+hal for test
  • From: Ryan R
• Re: ath patch+hal for test
  • From: Ryan R
• Re:Re: snap10 works, snap12 doesn't
  • From: Michael Jejer
• semi-interesting panic when rebooting
  • From: Matthew Jacob
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Andrew Gallatin
• Re: cvs commit: src/sys/dev/em if_em.c if_em.h
  • From: Harald Schmalzbauer
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: John Baldwin
• Panic In mi_switch+0x7e
  • From: Cy Schubert
• Re: 7.0-CURRENT Hang
  • From: Cy Schubert
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Giorgos Keramidas
• Re: 7.0-CURRENT Hang
  • From: Watanabe Kazuhiro
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Giorgos Keramidas
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Giorgos Keramidas
• Re: Which signal occurs due to a page protection violation?
  • From: David Xu
• Re: Parallel buildkernel (still) broken?
  • From: Ian FREISLICH
• Re: Which signal occurs due to a page protection violation?
  • From: Sam Lawrance
• Re: snap10 works, snap12 doesn't
  • From: Michael W. Lucas
• Re: panic: Memory modified after free
  • From: Doug White
• Re: 7.0-CURRENT Hang
  • From: Yar Tikhiy
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Andrew Gallatin
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: John Baldwin
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Andrew Gallatin
• Re: memguard monitoring of more than 1 memory_type?
  • From: Steve Kargl
• Re: memguard monitoring of more than 1 memory_type?
  • From: Yar Tikhiy
• Re: [ATA] [patch] crashes, deadlock, memory leaks, . plus LSI RAID write support
  • From: Søren Schmidt
• Re: 7.0-CURRENT Hang
  • From: Cy Schubert
• memguard monitoring of more than 1 memory_type?
  • From: Steve Kargl
• Re: 7.0-CURRENT Hang
  • From: Yar Tikhiy
• Re: 7.0-CURRENT Hang
  • From: Cy Schubert
• Re: 7.0-CURRENT Hang
  • From: Yar Tikhiy
• Re: Parallel buildkernel (still) broken?
  • From: Stefan Ehmann
• Re: Parallel buildkernel (still) broken?
  • From: Ruslan Ermilov
• Re: Parallel buildkernel (still) broken?
  • From: Ruslan Ermilov
• Re: Parallel buildkernel (still) broken?
  • From: Stefan Ehmann
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: John Baldwin
• Re: Peter's talk on amd64 audio online
  • From: Doug Poland
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Steve Kargl
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Gary Jennejohn
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Robert Watson
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Giorgos Keramidas
• Re: panic: mutex Giant not owned at sys/kern/vfs_subr.c:2029
  • From: Gleb Smirnoff
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Gary Jennejohn
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Giorgos Keramidas
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Gary Jennejohn
• panic: mutex Giant not owned at sys/kern/vfs_subr.c:2029
  • From: Cy Schubert
• Re: HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Giorgos Keramidas
• Re: Peter's talk on amd64 audio online
  • From: Mike Jakubik
• Re: Peter's talk on amd64 audio online
  • From: Julian Elischer
• ath patch+hal for test
  • From: Sam Leffler
• Re: 7.0-CURRENT Hang
  • From: Cy Schubert
• Re: 7.0-CURRENT Hang
  • From: Cy Schubert
• Re: audit group
  • From: Doug Barton
• Re: Peter's talk on amd64 audio online
  • From: Mike Jakubik
• [ATA] [patch] crashes, deadlock, memory leaks, . plus LSI RAID write support
  • From: Garry Belka
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Andrew Gallatin
• Re: unprivileged users are able to kill certain jailed processes
  • From: Chad Leigh -- Shire.Net LLC
• Re: unprivileged users are able to kill certain jailed processes
  • From: Julian Elischer
• Re: panic: mutex Giant not owned at sys/kern/vfs_subr.c: 2029
  • From: Doug Barton
• Re: unprivileged users are able to kill certain jailed processes
  • From: Chad Leigh -- Shire.Net LLC
• Re: audit group
  • From: Randy Bush
• Re: Cannot boot the 7-current's GENERIC kernel on some old PCs (Pentium/P54C, DX4ODP)
  • From: Alexander Leidinger
• Re: audit group
  • From: Kris Kennaway
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: John Baldwin
• Re: unprivileged users are able to kill certain jailed processes
  • From: Björn König
• audit group
  • From: Randy Bush
• AnyDATA USB Modem
  • From: Jan Dušátko
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Andrew Gallatin
• Re: Parallel buildkernel (still) broken?
  • From: Ian FREISLICH
• Re: Parallel buildkernel (still) broken?
  • From: Ruslan Ermilov
• Re: Parallel buildkernel (still) broken?
  • From: M. Warner Losh
• Re: Parallel buildkernel (still) broken?
  • From: Stefan Ehmann
• snap10 works, snap12 doesn't
  • From: Michael W. Lucas
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Andrew Gallatin
• Re: Peter's talk on amd64 audio online
  • From: Julian Elischer
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Yar Tikhiy
• Parallel buildkernel (still) broken?
  • From: Ian FREISLICH
• Re: Peter's talk on amd64 audio online
  • From: Giorgos Keramidas
• Re: unprivileged users are able to kill certain jailed processes
  • From: Andre Oppermann
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Andre Oppermann
• Cannot boot the 7-current's GENERIC kernel on some old PCs (Pentium/P54C, DX4ODP)
  • From: Watanabe Kazuhiro
• Re: Peter's talk on amd64 audio online
  • From: Marcin Jessa
• Re: Peter's talk on amd64 audio online
  • From: Panagiotis Astithas
• Re: patchset-7 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Daichi GOTO
• Re: Peter's talk on amd64 audio online
  • From: Marcin Jessa
• Re: Peter's talk on amd64 audio online
  • From: Marcin Jessa
• Re: Peter's talk on amd64 audio online
  • From: Alistair Sutton
• Re: Peter's talk on amd64 audio online
  • From: Colin Percival
• Re: Peter's talk on amd64 audio online
  • From: Marcin Jessa
• Re: patchset-7 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Daichi GOTO
• Re: patchset-7 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Dario Freni
• Re: panic: mutex Giant not owned at sys/kern/vfs_subr.c: 2029
  • From: Gleb Smirnoff
• Peter's talk on amd64 audio online
  • From: Julian Elischer
• Re: em(4) stops forwarding
  • From: MonkeyBrains
• RE: machdep.cpu_idle_hlt and SMP perf?
  • From: Mike Tancsa
• Re: patchset-7 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Dario Freni
• Re: unprivileged users are able to kill certain jailed processes
  • From: Joseph Koshy
• Re: unprivileged users are able to kill certain jailed processes
  • From: Björn König
• Re: unprivileged users are able to kill certain jailed processes
  • From: Robert Watson
• Re: unprivileged users are able to kill certain jailed processes
  • From: Björn König
• unprivileged users are able to kill certain jailed processes
  • From: Björn König
• Re: patchset-7 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Daichi GOTO
• Re: patchset-7 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Danny Braniss
• Re: panic: Memory modified after free
  • From: Matthew D. Fuller
• Re: panic: Memory modified after free
  • From: Steve Kargl
• Re: panic: Memory modified after free
  • From: Doug White
• panic: mutex Giant not owned at sys/kern/vfs_subr.c: 2029
  • From: Doug Barton
• patchset-7 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Daichi GOTO
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• Re: patchset-7 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010)
  • From: Dario Freni
• [head tinderbox] failure on alpha/alpha
  • From: FreeBSD Tinderbox
• RE: machdep.cpu_idle_hlt and SMP perf?
  • From: Daniel Eriksson
• panic: Giant not owned in vfs_subr.c:2029
  • From: Ruslan Ermilov
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Kris Kennaway
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: M. Warner Losh
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Doug Barton
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Marcin Jessa
• Re: jail leak
  • From: Stefan Bethke
• Re: jail leak
  • From: Bjoern A. Zeeb
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Ivan Voras
• Re: jail leak
  • From: Kris Kennaway
• Re: jail leak
  • From: Chad Leigh -- Shire.Net LLC
• jail leak
  • From: Kris Kennaway
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: David Xu
• Re: [head tinderbox] failure on amd64/amd64
  • From: Robert Watson
• Re: [head tinderbox] failure on amd64/amd64
  • From: Max Laier
• [head tinderbox] failure on amd64/amd64
  • From: FreeBSD Tinderbox
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Andrew Gallatin
• Re: machdep.cpu_idle_hlt and SMP perf?
  • From: Kris Kennaway
• machdep.cpu_idle_hlt and SMP perf?
  • From: Andrew Gallatin
• Re: subdisk6: detached --> Fatal trap 9
  • From: Jason Evans
• [head tinderbox] failure on alpha/alpha
  • From: FreeBSD Tinderbox
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Robert Watson
• Re: buglets with pts - with patch
  • From: Michal Mertl
• Re: For the love of God, is it even possible to make the Atheros ath.patch & updated HAL actually work?
  • From: Guy Brand
• Re: buglets with pts - with patch
  • From: Michal Mertl
• Re: em(4) stops forwarding
  • From: Scott Long
• Re: hwpmc & kernel modules?
  • From: Joseph Koshy
• [head tinderbox] failure on i386/pc98
  • From: FreeBSD Tinderbox
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Doug Barton
• Re: em(4) stops forwarding
  • From: Jack Vogel
• [head tinderbox] failure on i386/i386
  • From: FreeBSD Tinderbox
• buglets with pts - with patch
  • From: Michal Mertl
• Re: mapping "random" physical memory into kernel
  • From: Scott Long
• Re: mapping "random" physical memory into kernel
  • From: Andrew Gallatin
• Re: mapping "random" physical memory into kernel
  • From: Scott Long
• mapping "random" physical memory into kernel
  • From: Andrew Gallatin
• [head tinderbox] failure on alpha/alpha
  • From: FreeBSD Tinderbox
• Re: nextboot (was Re: boot block differences between 4.x and 6.x ?)
  • From: John Baldwin
• Re: nextboot (was Re: boot block differences between 4.x and 6.x ?)
  • From: Julian Elischer
• Re: em(4) stops forwarding
  • From: Julian Elischer
• Re: nextboot (was Re: boot block differences between 4.x and 6.x ?)
  • From: John Baldwin
• hwpmc & kernel modules?
  • From: Andrew Gallatin
• Re: em(4) stops forwarding
  • From: Scott Long
• Re: em(4) stops forwarding
  • From: Michal Mertl
• Re: em(4) stops forwarding
  • From: Fabian Keil
• Re: em(4) stops forwarding
  • From: Yamamoto Shigeru
• Re: em(4) stops forwarding
  • From: Scott Long
• Re: xorg 6.9.0 mem leak
  • From: Randy Bush
• Re: KDE 3.5.0 seems much chubbier than 3.4.2
  • From: Daniel O'Connor
• Re: em(4) stops forwarding
  • From: Michal Mertl
• Re: xorg 6.9.0 mem leak
  • From: Alexander Leidinger
• Re: xorg 6.9.0 mem leak
  • From: Randy Bush
• Re: xorg 6.9.0 mem leak
  • From: Randy Bush
• Re: xorg 6.9.0 mem leak
  • From: Randy Bush
• Re: xorg 6.9.0 mem leak
  • From: Randy Bush
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Peter Jeremy
• Re: unstable kernels in -current right now?
  • From: Jeff Roberson
• Re: KDE 3.5.0 seems much chubbier than 3.4.2
  • From: Peter Jeremy
• unstable kernels in -current right now?
  • From: Matthew Jacob
• Re: KDE 3.5.0 seems much chubbier than 3.4.2
  • From: Daniel O'Connor
• Re: KDE 3.5.0 seems much chubbier than 3.4.2
  • From: Peter Jeremy
• Re: xorg 6.9.0 mem leak
  • From: Thomas Gellekum
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Mike Jakubik
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Tom Rhodes
• Re: xorg 6.9.0 mem leak
  • From: Joe Marcus Clarke
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Robert Watson
• Re: xorg 6.9.0 mem leak
  • From: Jung-uk Kim
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Kris Kennaway
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Mike Jakubik
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Robert Watson
• Re: [RFC] what do we do with picobsd ?
  • From: Dario Freni
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Kris Kennaway
• Re: [RFC] what do we do with picobsd ?
  • From: Dario Freni
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Robert Watson
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Mike Jakubik
• HEADSUP: New pts code triggers panics on amd64 systems.
  • From: Steve Kargl
• Re: xorg 6.9.0 mem leak
  • From: Josh Carroll
• Re: KDE 3.5.0 seems much chubbier than 3.4.2
  • From: Daniel O'Connor
• Re: xorg 6.9.0 mem leak
  • From: Randy Bush
• Re: For the love of God, is it even possible to make the Atheros ath.patch & updated HALactually work?
  • From: Sam Leffler
• Re: xorg 6.9.0 mem leak
  • From: Freddie Cash
• Re: xorg 6.9.0 mem leak
  • From: Matt Reimer
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Robert Watson
• Re: xorg 6.9.0 mem leak
  • From: Gary Palmer
• Re: xorg 6.9.0 mem leak
  • From: Randy Bush
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Julian Elischer
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Robert Watson
• Re: HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Kövesdán Gábor
• Re: [RFC] what do we do with picobsd ?
  • From: Julian Elischer
• RE: For the love of God, is it even possible to make the Atheros ath.patch & updated HALactually work?
  • From: Daniel Dvorak
• HEADS UP: Audit integration into CVS in progress, some tree disruption
  • From: Robert Watson
• subdisk6: detached --> Fatal trap 9
  • From: Jason Evans
• Re: nextboot (was Re: boot block differences between 4.x and 6.x ?)
  • From: Scott Long
• Re: [RFC] what do we do with picobsd ?
  • From: Julian Elischer
• Re: For the love of God, is it even possible to make the Atheros ath.patch & updated HAL actually work?
  • From: Andrew Atrens
• Re: [RFC] what do we do with picobsd ?
  • From: Dario Freni
• Re: nextboot (was Re: boot block differences between 4.x and 6.x ?)
  • From: Julian Elischer
• Re: nextboot (was Re: boot block differences between 4.x and 6.x ?)
  • From: Julian Elischer
• Re: xorg 6.9.0 mem leak
  • From: Kris Kennaway
• For the love of God, is it even possible to make the Atheros ath.patch & updated HAL actually work?
  • From: Ryan R
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Doug Barton
• Re: xorg 6.9.0 mem leak
  • From: Randy Bush
• Re: xorg 6.9.0 mem leak
  • From: Jason Evans
• Re: xorg 6.9.0 mem leak
  • From: Randy Bush
• Re: xorg 6.9.0 mem leak
  • From: Jason Evans
• Re: xorg 6.9.0 mem leak
  • From: Randy Bush
• Memory modified panic -- was: Re: cvs commit: src/sys/kern kern_malloc.c
  • From: Steve Kargl
• Re: KDE 3.5.0 seems much chubbier than 3.4.2
  • From: Randy Bush
• Re: em(4) stops forwarding
  • From: Scott Long
• Re: KDE 3.5.0 seems much chubbier than 3.4.2
  • From: Jason Evans
• Re: xorg 6.9.0 mem leak
  • From: Jason Evans
• Re: nextboot (was Re: boot block differences between 4.x and 6.x ?)
  • From: John Baldwin
• em(4) stops forwarding
  • From: Michal Mertl
• Re: xorg 6.9.0 mem leak
  • From: David Scheidt
• Re: Patch to fix i915 drm with vgapci changes
  • From: John Baldwin
• nextboot (was Re: boot block differences between 4.x and 6.x ?)
  • From: Oliver Fromme
• Re: panic: Memory modified after free
  • From: Giorgos Keramidas
• Re: boot problem with atapicam
  • From: Michiel Boland
• Re: boot problem with atapicam
  • From: Thomas Quinot
• Re: boot problem with atapicam
  • From: Thomas Quinot
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Robert Watson
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Robert Watson
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Panagiotis Astithas
• Re: Patch to fix i915 drm with vgapci changes
  • From: Stefan Ehmann
• Re: [RFC] what do we do with picobsd ?
  • From: Peter Jeremy
• Re: panic: Memory modified after free
  • From: Pawel Jakub Dawidek
• Re: ServerWorks HT1000 Chipset SATA support
  • From: Mike Jakubik
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Doug Barton
• Re: ServerWorks HT1000 Chipset SATA support
  • From: Søren Schmidt
• Newly developed mailling list search engine needs more testing
  • From: Choy Kho Yee
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Daniel Eischen
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Daniel Eischen
• Re: panic: Memory modified after free
  • From: Steve Kargl
• Re: KDE 3.5.0 seems much chubbier than 3.4.2
  • From: Daniel O'Connor
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Kris Kennaway
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Sean McNeil
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Daniel Eischen
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Sean McNeil
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Robert Watson
• Re: panic: Memory modified after free
  • From: Steve Kargl
• Re: [RFC] what do we do with picobsd ?
  • From: Dario Freni
• Re: MFC of bump in libcom_err.so another mistake?
  • From: Robert Watson
• ServerWorks HT1000 Chipset SATA support
  • From: Mike Jakubik

• Security
• UNIX
• Linux
• Coding
• Usenet

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

unix.derkeiler.com  > Mailing-Lists  > FreeBSD  > current  > 2006-02