freebsd-hackers

• Thread Index

---

• Re: [PATCH] adding two new options to 'cp'
  • From: Rick C. Petty
• Re: VM question related to faults
  • From: John Baldwin
• Re: [PATCH] adding two new options to 'cp'
  • From: John Baldwin
• Re: [PATCH] adding two new options to 'cp'
  • From: Ivan Voras
• Re: absolute vs. relative offsets in disklabel
  • From: Dan Nelson
• Re: [PATCH] adding two new options to 'cp'
  • From: Ivan Voras
• Re: [PATCH] adding two new options to 'cp'
  • From: Ivan Voras
• absolute vs. relative offsets in disklabel
  • From: Dmitry Marakasov
• Re: [PATCH] adding two new options to 'cp'
  • From: Garance A Drosehn
• Re: [PATCH] adding two new options to 'cp'
  • From: Julian Elischer
• Re: [PATCH] adding two new options to 'cp'
  • From: Mike Meyer
• Re: [PATCH] adding two new options to 'cp'
  • From: Eric Anderson
• Re: [PATCH] adding two new options to 'cp'
  • From: Rick C. Petty
• Re: [PATCH] adding two new options to 'cp'
  • From: Eric Anderson
• Re: VM question related to faults
  • From: Attilio Rao
• Re: [PATCH] adding two new options to 'cp'
  • From: Mike Meyer
• Re: [PATCH] adding two new options to 'cp'
  • From: Eric Anderson
• Re: [PATCH] adding two new options to 'cp'
  • From: Rick C. Petty
• Re: _getlogin()
  • From: Joseph Koshy
• Re: [PATCH] adding two new options to 'cp'
  • From: Jason Slagle
• Re: [PATCH] adding two new options to 'cp'
  • From: Juan Rodriguez
• Re: [PATCH] adding two new options to 'cp'
  • From: Mike Meyer
• Re: [PATCH] adding two new options to 'cp'
  • From: Juan Rodriguez
• _getlogin()
  • From: mykola . stryebkov
• Re: [PATCH] adding two new options to 'cp'
  • From: Mike Meyer
• Re: [PATCH] adding two new options to 'cp'
  • From: Eric Anderson
• Re: [PATCH] adding two new options to 'cp'
  • From: Mike Meyer
• Re: [PATCH] adding two new options to 'cp'
  • From: Eric Anderson
• Re: VM question related to faults
  • From: Intron
• Re: VM question related to faults
  • From: mykola . stryebkov
• Re: VM question related to faults
  • From: Intron
• Re: disklabel differences FreeBSD, DragonFly
  • From: Dag-Erling Smørgrav
• Re: VM question related to faults
  • From: Kip Macy
• Re: VM question related to faults
  • From: Divacky Roman
• Re: i386 page fault clobbers error code in trap frame
  • From: Tijl Coosemans
• Re: i386 page fault clobbers error code in trap frame
  • From: Kip Macy
• Re: disklabel differences FreeBSD, DragonFly
  • From: Matthew Dillon
• Re: i386 page fault clobbers error code in trap frame
  • From: Tijl Coosemans
• Re: VM question related to faults
  • From: Intron
• Re: disklabel differences FreeBSD, DragonFly
  • From: Dmitry Marakasov
• Re: disklabel differences FreeBSD, DragonFly
  • From: David Gilbert
• Re: disklabel differences FreeBSD, DragonFly
  • From: Dmitry Marakasov
• Re: VM question related to faults
  • From: Peter Jeremy
• VM question related to faults
  • From: Divacky Roman
• Re: disklabel differences FreeBSD, DragonFly
  • From: M. Warner Losh
• Re: disklabel differences FreeBSD, DragonFly
  • From: Matthew Dillon
• Re: fdescfs functional in 6.1?
  • From: Rick C. Petty
• Re: fdescfs functional in 6.1?
  • From: Dan Nelson
• Re: [PATCH] adding two new options to 'cp'
  • From: Tim Kientzle
• Re: i386 page fault clobbers error code in trap frame
  • From: Kip Macy
• i386 page fault clobbers error code in trap frame
  • From: Tijl Coosemans
• Re: disklabel differences FreeBSD, DragonFly
  • From: Dmitry Marakasov
• Re: disklabel differences FreeBSD, DragonFly
  • From: Andreas Klemm
• Re: fdescfs functional in 6.1?
  • From: Jaye Mathisen
• Re: fdescfs functional in 6.1?
  • From: Dan Nelson
• fdescfs functional in 6.1?
  • From: Jaye Mathisen
• Re: disklabel differences FreeBSD, DragonFly
  • From: Mike Meyer
• Re: disklabel differences FreeBSD, DragonFly
  • From: Matthew Dillon
• Re: FBSD 5.5 and software timers
  • From: Michael Scheidell
• Re: New Welcome message for FreeBSD
  • From: Dmitry Marakasov
• Re: FBSD 5.5 and software timers
  • From: Sean C. Farley
• Re: How to Use ddb(4)?
  • From: maksim yevmenkin
• Re: disklabel differences FreeBSD, DragonFly
  • From: Mike Meyer
• Re: How to Use ddb(4)?
  • From: Maxime Henrion
• Re: FBSD 5.5 and software timers
  • From: M. Warner Losh
• Re: disklabel differences FreeBSD, DragonFly
  • From: Rick C. Petty
• Re: How to Use ddb(4)?
  • From: maksim yevmenkin
• Re: cvs commit: www/en/projects/ideas index.sgml
  • From: Alexander Leidinger
• Re: cvs commit: www/en/projects/ideas index.sgml
  • From: Alexander Leidinger
• RE: FBSD 5.5 and software timers
  • From: Michael Scheidell
• Re: cvs commit: www/en/projects/ideas index.sgml
  • From: Robert Watson
• Re: How to Use ddb(4)?
  • From: Maxime Henrion
• Re: disklabel differences FreeBSD, DragonFly
  • From: Matthew D. Fuller
• Re: Any success with bacula and DVD
  • From: Stanislav Sedov
• Re: Programs not accepting input?
  • From: Eric Schuele
• Re: FBSD 5.5 and software timers
  • From: M. Warner Losh
• Re: disklabel differences FreeBSD, DragonFly
  • From: Mike Meyer
• Re: disklabel differences FreeBSD, DragonFly
  • From: Rick C. Petty
• Re: WINE vs. FreeBSD
  • From: Tijl Coosemans
• Any success with bacula and DVD
  • From: george+freebsd
• Re: disklabel differences FreeBSD, DragonFly
  • From: Alex Zbyslaw
• Re: disklabel differences FreeBSD, DragonFly
  • From: Mike Meyer
• Re: WINE vs. FreeBSD
  • From: Julian Elischer
• Re: disklabel differences FreeBSD, DragonFly
  • From: Alex Zbyslaw
• Re: How to Use ddb(4)?
  • From: John Baldwin
• Re: disklabel differences FreeBSD, DragonFly
  • From: John Baldwin
• Re: [PATCH] adding two new options to 'cp'
  • From: John Baldwin
• Re: disklabel differences FreeBSD, DragonFly
  • From: Joerg Sonnenberger
• Re: WINE vs. FreeBSD
  • From: Tijl Coosemans
• Re: disklabel differences FreeBSD, DragonFly
  • From: Mike Meyer
• Re: disklabel differences FreeBSD, DragonFly
  • From: Mike Meyer
• Re: How to Use ddb(4)?
  • From: Maksim Yevmenkin
• Re: disklabel differences FreeBSD, DragonFly
  • From: Andreas Klemm
• Re: disklabel differences FreeBSD, DragonFly
  • From: Andreas Klemm
• Re: disklabel differences FreeBSD, DragonFly
  • From: Alex Zbyslaw
• Re: How to Use ddb(4)?
  • From: Dag-Erling Smørgrav
• Re: How to Use ddb(4)?
  • From: Hans Petter Selasky
• Re: How to Use ddb(4)?
  • From: Maksim Yevmenkin
• Re: How to Use ddb(4)?
  • From: Dag-Erling Smørgrav
• Re: disklabel differences FreeBSD, DragonFly
  • From: Mike Meyer
• Re: A bug in semctl()
  • From: Ed Schouten
• Re: disklabel differences FreeBSD, DragonFly
  • From: Rick C. Petty
• Re: [PATCH] adding two new options to 'cp'
  • From: Doug Barton
• Re: Building a sandboxed kernel
  • From: John Baldwin
• Re: A bug in semctl()
  • From: John Baldwin
• Re: A question about ipcperm() call?
  • From: John Baldwin
• Re: WINE vs. FreeBSD
  • From: John Baldwin
• RE: puc question
  • From: Helge.Oldach
• Re: disklabel differences FreeBSD, DragonFly
  • From: Brooks Davis
• Re: A bug in semctl()
  • From: Ed Schouten
• Re: How to Use ddb(4)?
  • From: maksim yevmenkin
• Warning Message from uma_zdestroy(9)
  • From: Intron
• Re: How to Use ddb(4)?
  • From: Dag-Erling Smørgrav
• Re: How to Use ddb(4)?
  • From: Intron
• Re: Re: disklabel differences FreeBSD, DragonFly
  • From: Sergey Babkin
• Re: disklabel differences FreeBSD, DragonFly
  • From: Steve Ames
• Re: disklabel differences FreeBSD, DragonFly
  • From: Joerg Sonnenberger
• Re: [PATCH] adding two new options to 'cp'
  • From: Oliver Fromme
• Need some articles on routing sockets in FreeBSD
  • From: Shriek
• Re: How to Use ddb(4)?
  • From: Dag-Erling Smørgrav
• How to Use ddb(4)?
  • From: Intron
• Re: disklabel differences FreeBSD, DragonFly
  • From: Andreas Klemm
• disklabel differences FreeBSD, DragonFly
  • From: Andreas Klemm
• Re: [PATCH] adding two new options to 'cp'
  • From: Matthew D. Fuller
• Re: [PATCH] adding two new options to 'cp'
  • From: Julian Elischer
• Re: [PATCH] adding two new options to 'cp'
  • From: Eric Anderson
• [PATCH] adding two new options to 'cp'
  • From: Eric Anderson
• Re: sys/dev/em/if_em.c
  • From: Julian Elischer
• Re: kqueue doesn't see if_tun
  • From: David Gilbert
• Re: sys/dev/em/if_em.c
  • From: Eric Anderson
• sys/dev/em/if_em.c
  • From: Murat Balaban
• puc question
  • From: Volker
• Re: A bug in semctl()
  • From: 李尚杰
• Re: A bug in semctl()
  • From: Maxim Konovalov
• A bug in semctl()
  • From: 李尚杰
• Re: Rebooting jails
  • From: Nate Nielsen
• FBSD 5.5 broke nanosleep in libc_r
  • From: Michael Scheidell
• Re: [Fwd: Interrupts question]
  • From: Alex Zbyslaw
• Re: [Fwd: Interrupts question]
  • From: Alex Zbyslaw
• Re: FBSD 5.5 and software timers
  • From: Michael Scheidell
• Re: [PATCH] Fancy rc startup style RFC
  • From: Eric Anderson
• Re: FBSD 5.5 and software timers
  • From: Michael Scheidell
• Re: FBSD 5.5 and software timers
  • From: Tim Kientzle
• Re: FBSD 5.5 and software timers
  • From: M. Warner Losh
• Re: FBSD 5.5 and software timers
  • From: M. Warner Losh
• RE: FBSD 5.5 and software timers
  • From: Michael Scheidell
• RE: FBSD 5.5 and software timers
  • From: Michael Scheidell
• Re: kqueue doesn't see if_tun
  • From: Alexander Leidinger
• Re: FBSD 5.5 and software timers
  • From: Peter Jeremy
• Re: Just a question
  • From: Michael D. Norwick
• Re: WINE vs. FreeBSD
  • From: Tijl Coosemans
• Re: Just a question
  • From: Giorgos Keramidas
• Just a question
  • From: Michael D. Norwick
• Re: Failing `make buildworld` with today's source
  • From: M. Warner Losh
• Re: kqueue doesn't see if_tun
  • From: John-Mark Gurney
• Re: FBSD 5.5 and software timers
  • From: Michael Scheidell
• kqueue doesn't see if_tun
  • From: David Gilbert
• Re: [emulation] WINE vs. FreeBSD
  • From: Julian Elischer
• Rebooting jails
  • From: Dirk Engling
• Re: WINE vs. FreeBSD
  • From: Daniel Eischen
• Re: WINE vs. FreeBSD
  • From: Tijl Coosemans
• Re: [emulation] WINE vs. FreeBSD
  • From: Gerald Pfeifer
• FBSD 5.5 and software timers
  • From: Michael Scheidell
• Re: WINE vs. FreeBSD
  • From: Daniel Eischen
• Re: WINE vs. FreeBSD
  • From: Tijl Coosemans
• Re: A question about ipcperm() call?
  • From: Alexander Leidinger
• Re: A question about ipcperm() call?
  • From: Robert Watson
• Re: A question about ipcperm() call?
  • From: Robert Watson
• Re: Programs not accepting input?
  • From: Daniel O'Connor
• Re: Failing `make buildworld` with today's source
  • From: R. Tyler Ballance
• Re: i386 registers during a syscall
  • From: Julian Elischer
• Re: i386 registers during a syscall
  • From: Divacky Roman
• Re: A question about ipcperm() call?
  • From: Xin LI
• Re: A question about ipcperm() call?
  • From: Stanislaw Halik
• Re: i386 registers during a syscall
  • From: Julian Elischer
• A question about ipcperm() call?
  • From: 李尚杰
• Re: Platform dependent locations
  • From: M. Warner Losh
• Re: i386 registers during a syscall
  • From: Attilio Rao
• Re: WINE vs. FreeBSD
  • From: Daniel Eischen
• Platform dependent locations (was Re: Building a sandboxed kernel)
  • From: R. Tyler Ballance
• Re: New Welcome message for FreeBSD
  • From: Giorgos Keramidas
• Re: WINE vs. FreeBSD
  • From: Michael Nottebrock
• Re: WINE vs. FreeBSD
  • From: Michael Nottebrock
• Re: Building a sandboxed kernel
  • From: M. Warner Losh
• Re: WINE vs. FreeBSD
  • From: Tijl Coosemans
• Re: WINE vs. FreeBSD
  • From: Tijl Coosemans
• Re: New Welcome message for FreeBSD
  • From: Arseny Nasokin
• i386 registers during a syscall
  • From: Divacky Roman
• Re: Building a sandboxed kernel
  • From: Dag-Erling Smørgrav
• Re: Building a sandboxed kernel
  • From: R. Tyler Ballance
• Re: Machine-dependent code extension?
  • From: Giorgos Keramidas
• Re: Building a sandboxed kernel
  • From: Giorgos Keramidas
• An error about IPC permission checking
  • From: 李尚杰
• Re: WINE vs. FreeBSD
  • From: Divacky Roman
• Machine-dependent code extension?
  • From: R. Tyler Ballance
• Building a sandboxed kernel
  • From: R. Tyler Ballance
• Re: WINE vs. FreeBSD
  • From: Daniel Eischen
• Re: Programs not accepting input?
  • From: Greg 'groggy' Lehey
• Re: Re: Programs not accepting input?
  • From: Greg 'groggy' Lehey
• Re: WINE vs. FreeBSD
  • From: Kip Macy
• Re: WINE vs. FreeBSD
  • From: Michael Nottebrock
• Re: WINE vs. FreeBSD
  • From: Kip Macy
• Re: open ("/dev/lpt0" ...) hangup solved
  • From: Rick C. Petty
• WINE vs. FreeBSD
  • From: Michael Nottebrock
• open ("/dev/lpt0" ...) hangup solved
  • From: george+freebsd
• Re: FreeBSD 6.0/6.1: open ("/dev/lpt0" ...) hangs up
  • From: Julian H. Stacey
• Re: FreeBSD 6.0/6.1: open ("/dev/lpt0" ...) hangs up
  • From: Peter Jeremy
• Re: FreeBSD 6.0/6.1: open ("/dev/lpt0" ...) hangs up
  • From: Hans Petter Selasky
• Re: FreeBSD 6.0/6.1: open ("/dev/lpt0" ...) hangs up
  • From: Greg Black
• FreeBSD 6.0/6.1: open ("/dev/lpt0" ...) hangs up
  • From: george+freebsd
• Re: New Welcome message for FreeBSD
  • From: Giorgos Keramidas
• Re: New Welcome message for FreeBSD
  • From: Michael Vince
• Re: "swiN: clock sio" process taking 75% CPU
  • From: Gareth McCaughan
• Re: "swiN: clock sio" process taking 75% CPU
  • From: John Baldwin
• Re: New Welcome message for FreeBSD
  • From: Özkan KIRIK
• Re: "swiN: clock sio" process taking 75% CPU
  • From: Gareth McCaughan
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: R. Tyler Ballance
• Re: Programs not accepting input?
  • From: Daniel O'Connor
• Re: Re: Programs not accepting input?
  • From: Robert Watson
• Re: New Welcome message for FreeBSD
  • From: Tarasov Alexey
• Re: Re: Programs not accepting input?
  • From: Greg 'groggy' Lehey
• Re: Programs not accepting input?
  • From: Greg 'groggy' Lehey
• Re: Improving FreeBSD's hardware compatibility
  • From: User Freebsd
• New Welcome message for FreeBSD
  • From: Timur Yuldashev
• Re: Re: Re: Programs not accepting input?
  • From: Sergey Babkin
• Re: Improving FreeBSD's hardware compatibility
  • From: John-Mark Gurney
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Only OpenSource
• Re: Improving FreeBSD's hardware compatibility
  • From: Oliver Fromme
• Re: Re: Programs not accepting input?
  • From: Sergey Babkin
• Re: [Fwd: Interrupts question]
  • From: Oliver Fromme
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: pfgshield-freebsd
• Re: Improving FreeBSD's hardware compatibility
  • From: Intron
• Re: Re: Programs not accepting input?
  • From: Peter Jeremy
• Re: Programs not accepting input?
  • From: Peter Jeremy
• RE: [Fwd: Interrupts question]
  • From: John Polstra
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: David Nugent
• Re: VIA padlock performance
  • From: Jesse Ahrens
• Re: "swiN: clock sio" process taking 75% CPU
  • From: Gareth McCaughan
• Re: "swiN: clock sio" process taking 75% CPU
  • From: John Baldwin
• Re: On the use of Tun interfaces.
  • From: Stefan Bethke
• Re: VIA padlock performance
  • From: Michael Reifenberger
• more if_tun frustration.
  • From: David Gilbert
• Re: VIA padlock performance
  • From: Oliver Fromme
• Re: VIA padlock performance
  • From: Christian Brueffer
• Re: VIA padlock performance
  • From: Michael Reifenberger
• Re: VIA padlock performance
  • From: Michael Reifenberger
• Re: VIA padlock performance
  • From: Oliver Fromme
• Re: "swiN: clock sio" process taking 75% CPU
  • From: victor cruceru
• Re: VIA padlock performance
  • From: Andrzej Tobola
• Re: [Fwd: Interrupts question]
  • From: Alex Zbyslaw
• Re: VIA padlock performance
  • From: Oliver Fromme
• Re: [Fwd: Interrupts question]
  • From: Oliver Fromme
• sshd throwing signal 6 (sigabrt)
  • From: Ulf Zimmermann
• Re: odd behavior in apache 2.0.58 today
  • From: Doug Barton
• Re: "swiN: clock sio" process taking 75% CPU
  • From: John Baldwin
• Re: odd behavior in apache 2.0.58 today
  • From: John Von Essen
• Re: odd behavior in apache 2.0.58 today
  • From: Doug Barton
• odd behavior in apache 2.0.58 today
  • From: John Von Essen
• Re: "swiN: clock sio" process taking 75% CPU
  • From: Gareth McCaughan
• Re: On the use of Tun interfaces.
  • From: David Gilbert
• Re: "swiN: clock sio" process taking 75% CPU
  • From: Deomid Ryabkov
• Re: On the use of Tun interfaces.
  • From: matt
• Re: VIA padlock performance
  • From: Christian Brueffer
• Re: [Fwd: Interrupts question]
  • From: Alex Zbyslaw
• VIA padlock performance
  • From: Michael Reifenberger
• "swiN: clock sio" process taking 75% CPU
  • From: Gareth McCaughan
• Re: [RFT]: InFlight Mode Patch
  • From: Alexander Leidinger
• Re: [RFT]: InFlight Mode Patch
  • From: Avleen Vig
• On the use of Tun interfaces.
  • From: David Gilbert
• Re: [RFT]: InFlight Mode Patch
  • From: Julian Elischer
• Re: [Fwd: Interrupts question]
  • From: John Baldwin
• Re: [Fwd: Interrupts question]
  • From: Alex Zbyslaw
• Re: [Fwd: Interrupts question]
  • From: John Baldwin
• Re: automatic KSE for multithreaded programs
  • From: Daniel Eischen
• automatic KSE for multithreaded programs
  • From: Mathieu Prevot
• [Fwd: Interrupts question]
  • From: Alex Zbyslaw
• [RFT]: InFlight Mode Patch
  • From: Benjamin Close
• Re: dlsym() on implicit loaded symbols
  • From: Kostik Belousov
• Re: Error Api OpenLdap
  • From: Dan Nelson
• Re: LinkLib Issues In freebsd Lazarus
  • From: Jeremy Messenger
• Re: LinkLib Issues In freebsd Lazarus
  • From: Bob Richards
• Re: LinkLib Issues In freebsd Lazarus
  • From: Bob Richards
• Error Api OpenLdap
  • From: Eder
• Re: LinkLib Issues In freebsd Lazarus
  • From: Steve Kargl
• Re: LinkLib Issues In freebsd Lazarus
  • From: Ivan Voras
• Re: LinkLib Issues In freebsd Lazarus
  • From: Steve Kargl
• LinkLib Issues In freebsd Lazarus
  • From: Bob Richards
• Re: dlsym() on implicit loaded symbols
  • From: Roland Dittel
• Re: dlsym() on implicit loaded symbols
  • From: Simon 'corecode' Schubert
• Re: dlsym() on implicit loaded symbols
  • From: Roland Dittel
• Re: BSD tar broken file name parsing
  • From: Tim Kientzle
• Re: linux gdb doesnt work at all, fbsd one with problems
  • From: Václav Haisman
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Peter Jeremy
• Re: fork inside ip_input
  • From: M. Warner Losh
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: M. Warner Losh
• Re: dlsym() on implicit loaded symbols
  • From: Simon 'corecode' Schubert
• linux gdb doesnt work at all, fbsd one with problems
  • From: Divacky Roman
• Genius slimstar pro keyboard
  • From: wolfie
• Re: Sysinstall: Write the FreeBSD version at the top of the display
  • From: Joao Barros
• dlsym() on implicit loaded symbols
  • From: Roland Dittel
• Re: fork inside ip_input
  • From: mykola . stryebkov
• Re: fork inside ip_input
  • From: Simon 'corecode' Schubert
• Re: fork inside ip_input
  • From: Julian Elischer
• fork inside ip_input
  • From: Mykola Stryebkov
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Joerg Sonnenberger
• Re: [ANN] unionfs patchset-16 release, it is ready for the merge
  • From: Daichi GOTO
• Re: [SoC]: question about execve()
  • From: Divacky Roman
• [ANN] unionfs patchset-16 release, it is ready for the merge
  • From: Daichi GOTO
• [SoC]: question about execve()
  • From: Divacky Roman
• Re: Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Sergey Babkin
• Re: Sysinstall: Write the FreeBSD version at the top of the display
  • From: Martin Nilsson
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Kamal R. Prasad
• tim's talk starting now.
  • From: Julian Elischer
• Re: Sysinstall: Write the FreeBSD version at the top of the display
  • From: Gábor Kövesdán
• Sysinstall: Write the FreeBSD version at the top of the display
  • From: Joao Barros
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Alexander Leidinger
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Mike Meyer
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Intron
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Attilio Rao
• Re: Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Sergey Babkin
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: pfgshield-freebsd
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Oliver Fromme
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Mike Meyer
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Rick C. Petty
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Mike Meyer
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: pfgshield-freebsd
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Joerg Sonnenberger
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Kamal R. Prasad
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Joerg Sonnenberger
• improving drivers (was: Re: kern/99979: Get Ready for Kernel Module in C++)
  • From: Alexander Leidinger
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Peter Jeremy
• Re: /boot/boot, where?
  • From: mal content
• Re: /boot/boot, where?
  • From: Dag-Erling Smørgrav
• /boot/boot, where?
  • From: mal content
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Jan Grant
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: mag
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Intron
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Jason Slagle
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Garance A Drosihn
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: pfgshield-freebsd
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: mag
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: mag
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Mike Meyer
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Rick C. Petty
• FreeBSD Status Report Second Quarter 2006
  • From: Max Laier
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Attilio Rao
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: M. Warner Losh
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: M. Warner Losh
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Warner Losh
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: John Baldwin
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: John Baldwin
• Re: Intel Vanderpool (VT) on FreeBSD or FreeBSD Xen
  • From: Kip Macy
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Garance A Drosehn
• Intel Vanderpool (VT) on FreeBSD or FreeBSD Xen
  • From: Mohacsi Janos
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: M. Warner Losh
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: John Baldwin
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: mag
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: mag
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: mag
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Dag-Erling Smørgrav
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: mag
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: M. Warner Losh
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: M. Warner Losh
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: M. Warner Losh
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: M. Warner Losh
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Matthias Andree
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: John Baldwin
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Joerg Sonnenberger
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Dag-Erling Smørgrav
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: mag
• Re: Stop further socket() or connect() calls.
  • From: Oliver Fromme
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Matthias Andree
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Xin LI
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Dag-Erling Smørgrav
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: mag
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Dag-Erling Smørgrav
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Dag-Erling Smørgrav
• Re: gdb able to debug both fbsd and linux binaries
  • From: Greg 'groggy' Lehey
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Václav Haisman
• Re: FreeBSD MIDI support
  • From: John-Mark Gurney
• Re: File Mirror Software
  • From: John-Mark Gurney
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: Julian Elischer
• Re: kern/99979: Get Ready for Kernel Module in C++
  • From: mag
• Re: FreeBSD MIDI support
  • From: Alexander Leidinger
• Re: gdb able to debug both fbsd and linux binaries
  • From: Alexander Kabaev
• RE: FreeBSD MIDI support
  • From: Yuriy Tsibizov
• File Mirror Software
  • From: Brad Falzon
• Re: 6.1 kernel panic
  • From: Steven Hartland
• FreeBSD MIDI support
  • From: zarko bulatovic
• Re: 6.1 kernel panic
  • From: Steven Hartland
• Re: 6.1 kernel panic
  • From: Steven Hartland
• Re: gdb able to debug both fbsd and linux binaries
  • From: Kip Macy
• Re: SATA300 Controllers
  • From: Jia-Shiun Li
• gdb able to debug both fbsd and linux binaries
  • From: Divacky Roman
• Re: 6.1 kernel panic
  • From: Steve Kargl
• Inconsistent snapshots?
  • From: Stephen J. Roznowski
• Re: 6.1 kernel panic
  • From: Steven Hartland
• 6.1 kernel panic
  • From: Steven Hartland
• Re: BSD tar broken file name parsing
  • From: Brooks Davis
• Re: Call for Status Reports: 07/07
  • From: Max Laier
• Re: Static built binaries having unknown ELF binary types
  • From: Joseph Koshy
• Re: Static built binaries having unknown ELF binary types
  • From: Steve Kargl
• Static built binaries having unknown ELF binary types
  • From: Victor Roman Archidona
• Re: Promise PDC20267 / ide bug?
  • From: Steven Hartland
• Promise PDC20267 / ide bug?
  • From: Steven Hartland
• BSD tar broken file name parsing
  • From: Steven Hartland
• Re: SATA300 Controllers
  • From: Søren Schmidt
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Doug Barton
• Re: SATA300 Controllers
  • From: Rick C. Petty
• Re: SATA300 Controllers
  • From: Wilko Bulte
• Re: SATA300 Controllers
  • From: Mike Jakubik
• Re: SATA300 Controllers
  • From: Scott Long
• Re: SATA300 Controllers
  • From: Wilko Bulte
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Miguel Mendez
• Re: SATA300 Controllers
  • From: Alain Hebert
• Re: SATA300 Controllers
  • From: Boris Samorodov
• Re: NVIDIA FreeBSD kernel feature requests
  • From: John Baldwin
• Re: SATA300 Controllers
  • From: Mike Horwath
• Re: SATA300 Controllers
  • From: Freddie Cash
• SATA300 Controllers
  • From: Derrick T. Woolworth
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Sam Leffler
• Re: getc in BSD (was FLEX issues)
  • From: Randall Hyde
• Re: NVIDIA FreeBSD kernel feature requests
  • From: John Baldwin
• Re: Return value of malloc(0)
  • From: John Baldwin
• Re: Stop further socket() or connect() calls.
  • From: mal content
• Re: Stop further socket() or connect() calls.
  • From: Daan Vreeken [PA4DAN]
• Re: assyms.s
  • From: M. Warner Losh
• Re: NVIDIA FreeBSD kernel feature requests
  • From: M. Warner Losh
• Re: vop_stratgey name
  • From: Kamal R. Prasad
• Re: Stop further socket() or connect() calls.
  • From: mal content
• Re: getc in BSD (was FLEX issues)
  • From: Steve Kargl
• Re: assyms.s
  • From: Attilio Rao
• vop_stratgey name
  • From: Andriy Gapon
• assyms.s
  • From: Aditya Godbole
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Kip Macy
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Avleen Vig
• Re: getc in BSD (was FLEX issues)
  • From: Giorgos Keramidas
• Re: getc in BSD (was FLEX issues)
  • From: Mike Meyer
• Re: getc in BSD (was FLEX issues)
  • From: James Bailie
• Re: Stop further socket() or connect() calls.
  • From: Peter Jeremy
• getc in BSD (was FLEX issues)
  • From: Randall Hyde
• Stop further socket() or connect() calls.
  • From: mal content
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Christian Zander
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Christian Zander
• [patch] display jail id in /usr/bin/top
  • From: Cheng-Lung Sung
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Robert Watson
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Robert Watson
• Re: NVIDIA FreeBSD kernel feature requests
  • From: M. Warner Losh
• Re: NVIDIA FreeBSD kernel feature requests
  • From: M. Warner Losh
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Joseph Koshy
• Re: contiguous memory allocation problem
  • From: Julian Elischer
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Sam Smith
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Michal Mertl
• Re: contiguous memory allocation problem
  • From: Ian Dowse
• Re: contiguous memory allocation problem
  • From: Hans Petter Selasky
• Re: contiguous memory allocation problem
  • From: Steve Kargl
• Re: contiguous memory allocation problem
  • From: Randall Hyde
• Re: contiguous memory allocation problem
  • From: Ian Dowse
• Re: Return value of malloc(0)
  • From: Andre Albsmeier
• Re: Return value of malloc(0)
  • From: Andre Albsmeier
• Re: contiguous memory allocation problem
  • From: Ian Dowse
• Re: contiguous memory allocation problem
  • From: Hans Petter Selasky
• Re: contiguous memory allocation problem
  • From: Ian Dowse
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Miguel Mendez
• Re: contiguous memory allocation problem
  • From: Hans Petter Selasky
• Re: Alternative compiler toolchain ?
  • From: Alexander Leidinger
• Re: contiguous memory allocation problem
  • From: David Malone
• Re: Alternative compiler toolchain ?
  • From: Attilio Rao
• Re: Alternative compiler toolchain ?
  • From: Steve Kargl
• Re: Alternative compiler toolchain ?
  • From: joerg
• Re: Alternative compiler toolchain ?
  • From: Steve Kargl
• Re: Alternative compiler toolchain ?
  • From: Max Laier
• Re: Alternative compiler toolchain ?
  • From: Attilio Rao
• Re: Alternative compiler toolchain ?
  • From: Maslan
• Re: High-speed transfers
  • From: Hans Petter Selasky
• High-speed transfers
  • From: Thierry Herbelot
• Re: contiguous memory allocation problem
  • From: Peter Jeremy
• Re: Alternative compiler toolchain ?
  • From: Matthias Andree
• Re: contiguous memory allocation problem
  • From: Hans Petter Selasky
• Re: Alternative compiler toolchain ?
  • From: Joseph Koshy
• Re: Alternative compiler toolchain ?
  • From: Alexander Leidinger
• Re: Return value of malloc(0)
  • From: Matthias Andree
• Re: contiguous memory allocation problem
  • From: Hans Petter Selasky
• Re: Alternative compiler toolchain ?
  • From: Divacky Roman
• Re: freebsd port onto IBM/Lenovo T 40
  • From: Kamal R. Prasad
• Re: Alternative compiler toolchain ?
  • From: Dan Nelson
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Doug Ambrisko
• Re: Alternative compiler toolchain ?
  • From: Alastair G. Hogge
• Re: Alternative compiler toolchain ?
  • From: Steve Kargl
• Re: NVIDIA FreeBSD kernel feature requests
  • From: Kip Macy
• Alternative compiler toolchain ?
  • From: Jean-Marc Lienher

We are proud to have Web Hosting and Rack Housing from 9 Net Avenue Deutschland.
(13)