freebsd-hackers
- Fwd: Kernel conference Australia
- Re: hosted, or not (Re: Renaming all symbols in libmp(3))
- Re: hosted, or not (Re: Renaming all symbols in libmp(3))
- Re: hosted, or not (Re: Renaming all symbols in libmp(3))
- Re: portupgrade spurious skips
- From: Alexander Leidinger
- Re: hosted, or not (Re: Renaming all symbols in libmp(3))
- hosted, or not (Re: Renaming all symbols in libmp(3))
- Re: Renaming all symbols in libmp(3)
- Re: portupgrade spurious skips
- Re: Renaming all symbols in libmp(3)
- portupgrade spurious skips
- Re: Renaming all symbols in libmp(3)
- Re: Renaming all symbols in libmp(3)
- Re: Renaming all symbols in libmp(3)
- Re: Renaming all symbols in libmp(3)
- Re: Renaming all symbols in libmp(3)
- Re: Renaming all symbols in libmp(3)
- Re: x11 status
- Re: Renaming all symbols in libmp(3)
- Re: Renaming all symbols in libmp(3)
- Re: Renaming all symbols in libmp(3)
- Re: Renaming all symbols in libmp(3)
- Re: x11 status
- Renaming all symbols in libmp(3)
- Re: Google SoC 2009 Idea
- Re: Google SoC 2009 Idea
- Re: Google SoC 2009 Idea
- Re: Google SoC 2009 Idea
- Re: Google SoC 2009 Idea
- From: Siddharth Prakash Singh
- Re: [PATCH] Support for thresholds in du(1)
- Re: [PATCH] Support for thresholds in du(1)
- Re: [PATCH] Support for thresholds in du(1)
- [PATCH] Support for thresholds in du(1)
- Re: Google SoC 2009 Idea
- Re: How to change an interface?
- How to change an interface?
- Re: x11 status
- Re: Google SoC 2009 Idea
- From: Alexander Leidinger
- Re: x11 status
- Re: Google SoC 2009 Idea
- Re: x11 status
- x11 status
- Re: Google SoC 2009 Idea
- From: Siddharth Prakash Singh
- Re: Google SoC 2009 Idea
- Re: Google SoC 2009 Idea
- Re: Google SoC 2009 Idea
- Re: Google SoC 2009 Idea
- Re: Google SoC 2009 Idea
- From: Siddharth Prakash Singh
- Re: Google SoC 2009 Idea
- Google SoC 2009 Idea
- From: Siddharth Prakash Singh
- Re: shmmax tops out at 2G?
- Re: shmmax tops out at 2G?
- Re: shmmax tops out at 2G?
- Re: shmmax tops out at 2G?
- Re: shmmax tops out at 2G?
- Re: shmmax tops out at 2G?
- Re: shmmax tops out at 2G?
- Re: shmmax tops out at 2G?
- Re: removal of NGROUPS_MAX dependancy from base
- Re: FBSD 7.0-p3 NIC driver problem (Realtek)
- From: Fernando Apesteguía
- Re: FBSD 7.0-p3 NIC driver problem (Realtek)
- Re: FBSD 7.0-p3 NIC driver problem (Realtek)
- From: Fernando Apesteguía
- Re: removal of NGROUPS_MAX dependancy from base
- Re: variable args in kernel module?
- Re: removal of NGROUPS_MAX dependancy from base
- variable args in kernel module?
- ethernet card error
- Re: FBSD 7.0-p3 NIC driver problem (Realtek)
- Re: FBSD 7.0-p3 NIC driver problem (Realtek)
- From: Fernando Apesteguía
- Re: FBSD 7.0-p3 NIC driver problem (Realtek)
- FBSD 7.0-p3 NIC driver problem (Realtek)
- From: Fernando Apesteguía
- gbde and missing lock file
- gbde and missing lock files
- Re: Obtaining l2 misses and cpu utilization in a module
- Re: Obtaining l2 misses and cpu utilization in a module
- OT: svn commit: r188764 - head/sys/kern
- Re: Obtaining l2 misses and cpu utilization in a module
- Module Dependencies
- Re: Simulating bad network conditions
- HotPar '09: Attendance Now Open to Everyone
- Obtaining l2 misses and cpu utilization in a module
- Re: Simulating bad network conditions
- Re: Simulating bad network conditions
- Re: Simulating bad network conditions
- Re: Tyan S2895 7.1 amd64 >8Gb RAM support? - resolved
- Re: Simulating bad network conditions
- Re: Simulating bad network conditions
- Simulating bad network conditions
- Re: TUNABLE_INT question
- Re: booting/loading a tool, not kernel
- Re: TUNABLE_INT question
- Re: TUNABLE_INT question
- Re: TUNABLE_INT question
- Kernel Crashes
- Re: booting/loading a tool, not kernel
- Re: booting/loading a tool, not kernel
- Re: booting/loading a tool, not kernel
- Re: booting/loading a tool, not kernel
- booting/loading a tool, not kernel
- Re: pahole - Finding holes in kernel structs
- Re: When does the pool get bigger?
- Re: When does the pool get bigger?
- Re: Tyan S2895 7.1 amd64 >8Gb RAM support?
- Re: When does the pool get bigger?
- When does the pool get bigger?
- Re: Tyan S2895 7.1 amd64 >4Gb RAM support?
- Re: TUNABLE_INT question
- Re: TUNABLE_INT question
- Re: Tyan S2895 7.1 amd64 >4Gb RAM support?
- TUNABLE_INT question
- Tyan S2895 7.1 amd64 >4Gb RAM support?
- Re: bus_dmamem_alloc() and BUS_DMA_WAITOK
- bus_dmamem_alloc() and BUS_DMA_WAITOK
- removal of NGROUPS_MAX dependancy from base
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- Re: bus_setup_intr (9)
- Re: bus_setup_intr (9)
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- bus_setup_intr (9)
- Re: strange output in /var/log/messages
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- Re: strange output in /var/log/messages
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- strange output in /var/log/messages
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- Re: pahole - Finding holes in kernel structs
- pahole - Finding holes in kernel structs
- Re: How to troubleshoot why ath0 can't connect to a passwordless wireless network?
- Re: userland driver?
- Re: a little bit of c++ in kernel [module]
- Re: a little bit of c++ in kernel [module]
- Re: a little bit of c++ in kernel [module]
- Re: a little bit of c++ in kernel [module]
- Re: understanding of PTD symbol
- Re: a little bit of c++ in kernel [module]
- Re: generalizing fd allocation code to id allocation
- Re: generalizing fd allocation code to id allocation
- Re: taskqueue (9)
- userland driver?
- understanding of PTD symbol
- Re: a little bit of c++ in kernel [module]
- Re: CFT: Graphics support for /boot/loader
- Re: generalizing fd allocation code to id allocation
- From: Hans Petter Selasky
- Re: generalizing fd allocation code to id allocation
- generalizing fd allocation code to id allocation
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: a little bit of c++ in kernel [module]
- taskqueue (9)
- Re: How to troubleshoot why ath0 can't connect to a passwordless wireless network?
- a little bit of c++ in kernel [module]
- Re: How to troubleshoot why ath0 can't connect to a passwordless wireless network?
- Re: How to troubleshoot why ath0 can't connect to a passwordless wireless network?
- superio and "shared" io port
- How to troubleshoot why ath0 can't connect to a passwordless wireless network?
- Re: broken ports
- Re: broken ports
- Re: impossible packet length ...
- Re: impossible packet length ...
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: ZFS and Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Possible VFS KPI and KBI breakage on stable/7
- Re: impossible packet length ...
- Re: impossible packet length ...
- Re: FreeBSD 6.3/7.1 and Linux disk performance test
- Re: impossible packet length ...
- Re: setting up net/cvsup-mirror correctly
- Re: setting up net/cvsup-mirror correctly
- setting up net/cvsup-mirror correctly
- Re: FreeBSD 6.3/7.1 and Linux disk performance test
- Re: FreeBSD 6.3/7.1 and Linux disk performance test
- FreeBSD 6.3/7.1 and Linux disk performance test
- Re: Super I/O driver [generic gpio driver]
- RE: ZFS and Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: NO_WERROR vs kernel builds
- Re: CFT: Graphics support for /boot/loader
- Re: i386: rtc, nvram and the upper bank
- Re: i386: rtc, nvram and the upper bank
- Re: i386: rtc, nvram and the upper bank
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- From: Christian Gusenbauer
- Re: CFT: Graphics support for /boot/loader
- i386: rtc, nvram and the upper bank
- Super I/O driver
- Re: CFT: Graphics support for /boot/loader
- (openbsd) sensors framework
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- From: Alexandre Biancalana
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- From: Oleksandr Tymoshenko
- Re: CFT: Graphics support for /boot/loader
- Re: CFT: Graphics support for /boot/loader
- From: Bruno Van Den Bossche
- Re: CFT: Graphics support for /boot/loader
- CFT: Graphics support for /boot/loader
- Re: linking .a lib with another library
- Re: blockable sleep lock (sleep mutex) 16
- Re: linking .a lib with another library
- Re: kobj methods (DEVMETHOD) that have differing signatures (in src/sys)
- Re: SSH Problem
- linking .a lib with another library
- Re: kobj methods (DEVMETHOD) that have differing signatures (in src/sys)
- NO_WERROR vs kernel builds
- kobj methods (DEVMETHOD) that have differing signatures (in src/sys)
- Re: write-only variables in src/sys/ - possible bugs
- Re: write-only variables in src/sys/ - possible bugs
- Re: blockable sleep lock (sleep mutex) 16
- Re: write-only variables in src/sys/ - possible bugs
- Re: bus_dma (9). What exactly means "Loading of memory allocation" ?
- Re: write-only variables in src/sys/ - possible bugs
- Re: pmap.h: No such file or directory---- Debugging error
- pmap.h: No such file or directory---- Debugging error
- Re: usinig cvs diff to make a patch
- Re: usinig cvs diff to make a patch
- Re: usinig cvs diff to make a patch
- Re: usinig cvs diff to make a patch
- Re: usinig cvs diff to make a patch
- usinig cvs diff to make a patch
- Re: Fw: request responsibility timeout
- Re: freebsd-hackers Digest, Vol 305, Issue 6
- Re: Fw: request responsibility timeout
- Re: write-only variables in src/sys/ - possible bugs
- Re: write-only variables in src/sys/ - possible bugs
- Re: write-only variables in src/sys/ - possible bugs
- Re: write-only variables in src/sys/ - possible bugs
- Re: write-only variables in src/sys/ - possible bugs
- Re: write-only variables in src/sys/ - possible bugs
- Re: write-only variables in src/sys/ - possible bugs
- write-only variables in src/sys/ - possible bugs
- Re: Dynamic ddb commands
- Re: blockable sleep lock (sleep mutex) 16
- Re: Dynamic ddb commands
- Fw: request responsibility timeout
- Re: bus_dma (9). What exactly means "Loading of memory allocation" ?
- Re: Dynamic ddb commands
- Re: Dynamic ddb commands
- Re: blockable sleep lock (sleep mutex) 16
- Re: blockable sleep lock (sleep mutex) 16
- Re: INTR_FILTER?
- Re: INTR_FILTER?
- Re: INTR_FILTER?
- Re: INTR_FILTER?
- Re: INTR_FILTER?
- Re: INTR_FILTER?
- Re: bus_dma (9). What exactly means "Loading of memory allocation" ?
- Re: bus_dma (9). What exactly means "Loading of memory allocation" ?
- Re: bus_dma (9). What exactly means "Loading of memory allocation" ?
- bus_dma (9). What exactly means "Loading of memory allocation" ?
- Re: telnetd[20170]: ttloop: peer died: Resource temporarily unavailable
- gcc 4.3.2 libgcc_s.so exception handling broken?
- Invitación a conectarnos en LinkedIn
