Re: gpart is junk

Am 28.09.12 11:31, schrieb Steffen Daode Nurpmeso: Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: | but still not anywhere as readable as bsdlabel. | | | I did specifically say 'machine readable'. The XML is well-formed, |XML is stupid. everything you can do with XML can be

Re: Providing a default graphical environment on FreeBSD

Am 17.09.12 17:42, schrieb Poul-Henning Kamp: In message blu0-smtp510b16745b704c714268e2d5...@phx.gbl, Lorenzo Cogotti writ es: Hi, I was wondering about the possibility of FreeBSD to provide an official supported graphical environment. We already do: It's called X11 :-) and for the

tree doesnt compile

/usr/src/sys/modules/vesa/../../i386/isa/vesa.c: In function 'vesa_set_mode': /usr/src/sys/modules/vesa/../../i386/isa/vesa.c:1117: error: duplicate case value anyone seeing this as well or is this a local f***up ? ___ freebsd-hackers@freebsd.org

Re: tree doesnt compile

Am 25.08.2009 um 13:23 schrieb Marc Balmer: /usr/src/sys/modules/vesa/../../i386/isa/vesa.c: In function 'vesa_set_mode': /usr/src/sys/modules/vesa/../../i386/isa/vesa.c:1117: error: duplicate case value anyone seeing this as well or is this a local f***up ? fwiw, problem is still

Re: is there any chance to get HP blade servers supported again?

, but got no information). We just installed FreeBSD 8.0BETA3 (i386) on two HP BL460C, quad Xeon, with HP smart Array200i and QLogic QMH2462 4Gb FC HBA and networking works. At least that's what my colleague, who is onsite, just told me on the phone. - Marc Balmer

Re: Common interface for sensors/health monitoring

Am 23.08.2009 um 17:08 schrieb Alexander Leidinger: On Sat, 22 Aug 2009 21:02:32 +0200 Aurélien Méré aurelien.m...@amc-os.com wrote: I'm just afraid by reading your email that the situation doesn't seem to have evolved since the discussion regarding the SoC, maybe even more taboo, and that

Re: Common interface for sensors/health monitoring

Am 23.08.2009 um 18:24 schrieb Alexander Leidinger: On Sun, 23 Aug 2009 17:13:42 +0200 Marc Balmer m...@msys.ch wrote: Am 23.08.2009 um 17:08 schrieb Alexander Leidinger: On Sat, 22 Aug 2009 21:02:32 +0200 Aurélien Méré aurelien.m...@amc-os.com wrote: I'm just afraid by reading your

Re: Common interface for sensors/health monitoring

for on of these (ab)uses...). I am sure these features could be added if only the code was in the tree to hack on... - Marc Balmer ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail

Re: Common interface for sensors/health monitoring

Am 22.08.2009 um 18:29 schrieb Alexander Leidinger: On Sat, 22 Aug 2009 08:50:23 +0200 Marc Balmer m...@msys.ch wrote: The OpenBSD sensors framework lacks some desireable features, e.g. event capabilities like getting an event if a certain threshold is exceeded. And it propbably was used

syslog() reentrant when compiling with -pthread?

that compiling with -pthread links in the thread safe libc_r library instead of libc. As syslog() seems to part of libc on FreeBSD, is it safe to assume that syslog() is indeed thread safe on FreeBSD when compiling with the -pthread switch? Thanks, Marc Balmer

Re: syslog() reentrant when compiling with -pthread?

Am 06.10.2004 um 16:48 schrieb Dan Nelson: The only unsafe part is openlog(), so set that up before you start any threads and you'll be okay. Once the log fd is opened, the syslog() call looks to be thread-safe. Everything in there is done with local variables and atomic writes. At least on