On Sun, Jun 17, 2012 at 9:43 PM, Alexandre Ratchov a...@caoua.org wrote:
On Thu, Jun 14, 2012 at 12:54:49PM +0200, Tomas Bodzar wrote:
Hi all,
have someone working audio input with Qemu on OpenBSD?
IIRC, sdl is play-only. Adding a sndio backend could add
record-only support (and possibly
On 18 June 2012 15:46, Raymond Lillard rlill...@sonic.net wrote:
On 06/17/2012 12:31 PM, Peter J. Philipp wrote:
Having followed OpenBSD for quite some time I noticed that good developers
come and go. They come in, make something great happen, and disappear
again.
Also there have been forks
The secretive nature is concerning. But I hope that this situation
can somehow turn out to be beneficial to both projects in the long
term.
As long as my favourite and most relied upon OS continues to evolve, I
will be happy. And I will certainly continue to buy from and donate
to the OpenBSD
On 14/06/2012 3:44 AM, Dominguez, Roland wrote:
I just came across this article and was wondering if it's legit:
http://www.h-online.com/open/news/item/OpenBSD-forked-to-create-Bitrig-161695
4.html
Those who do not study history...
On Jun 17, 2012, at 7:53 PM, Ted Unangst wrote:
On Sun, Jun 17, 2012 at 11:43, Holger Glaess wrote:
i dident wont start about smp on openbsd but
what about this porject ?
Did you read the part below? I think it's pretty clear this project
isn't going to have much relevance for
On 2012-06-18 02:46, Raymond Lillard wrote:
Reason 4: Stability
The new project FAQ states they intend to be less
restrictive with the codebase when it comes to
experimenting with features. Maybe in the long run
some of the new features may be introduced into OBSD,
but in the near term I
yes. some more, some less.
The feature argument - surely any barriers there must mean that that
ideal goes against everything OpenBSD stands for. I wonder if that's
just a developer enticer.
I wouldn't mind better ARM support but I don't see why that couldn't
be done under the OpenBSD project
Their work getting rid of GNU stuff will, inevitably, affect OpenBSD (if
they succeed at that anyway).
Hmm, I personally prefer BSD Style licence. For me, BSD Philosophy has
much more freedom. NOT Copyleft. ( I love it very much ) I'd like to see
more BSD style stuffs coming in.
anyway
No, there is no single mutex around PF specifically in OpenBSD, the
whole kernel is wrapped in a biglock.
I think if they work out all the nits and dead-ends we may have
something to learn from this effort, but I don't see this code coming
back to OpenBSD.
It's not critical because they can
On Jun 18, 2012, at 11:31 AM, Ryan McBride wrote:
No, there is no single mutex around PF specifically in OpenBSD, the
whole kernel is wrapped in a biglock.
I think if they work out all the nits and dead-ends we may have
something to learn from this effort, but I don't see this code coming
Well. From PC-BSD ,FreeBSD gained much benefit. Hope that might happen here
too.
Regards,
Jay.
On Sat, Jun 16, 2012 at 10:24:02PM -0700, Robert Connolly wrote:
Hello.
The acpiac(4) man page mentions that the AC power source status can be
monitored by sensorsd(8), but sensorsd(8) does not monitor this sensor as
far as I know. apmd(8) does however.
Could the acpiac(4) man page be
On Sun, 17 Jun 2012 22:36:55 -0400
Nick Holland n...@holland-consulting.net wrote:
On 06/17/12 18:24, Jiri B wrote:
Hello,
could anybody recommend OpenBSD compatible 8-ports serial card? I'd
like to build a small console server.
Thank you.
jirib
So cheap, it's worth a try:
NO. GPL IS COUNTER-PRODUCTIVE TO TRUE FREE SOFTWARE.
YES, I KNOW I AM SHOUTING. PLEASE EDUCATE YOURSELF
ABOUT THE PERVERTED GOALS OF THE FSF.
On Mon, Jun 18, 2012, at 02:55 PM, Indunil Jayasooriya wrote:
Their work getting rid of GNU stuff will, inevitably, affect OpenBSD (if
they succeed at
speaking of stuck CAPSLOCK, anyone else having DEL/INS problems on US keyboards
w/ Euro key on 5? They're cheapo USB Dell manufactured by Logitech. Tweaking
wscons flags didn't help (not running X11); should I remap keys individually?
-- p
NO. GPL IS COUNTER-PRODUCTIVE TO TRUE FREE SOFTWARE.
Hello.
During boot I see:
acpitz0 at acpi0: critical temperature is 200 degC
The acpitz(4) man page mentions that the system will power down if this
critical temperature is reached. I assume this temperature is retrieved
from BIOS, but I do not have an option in BIOS setup for it.
Can I hard
On Mon, Jun 18, 2012 at 06:35:58AM -0700, Robert Connolly wrote:
Hello.
During boot I see:
acpitz0 at acpi0: critical temperature is 200 degC
The acpitz(4) man page mentions that the system will power down if this
critical temperature is reached. I assume this temperature is retrieved
So, from what I can tell, PCC has been removed from the core tree. I
have not been able to find the story behind why it was moved out, except
some minor mention of a lack of maintainer? Is there still any active
effort to move the code base of OpenBSD away from GCC dependence?
--
Aaron W.
On Wed, Jun 13, 2012 at 12:54 AM, Philip Guenther guent...@gmail.com wrote:
On Tuesday, June 12, 2012, bj.perso wrote:
FreeBSD and NetBSD seem affected, how about OpenBSD ?
Nope. The necessary check(s) for setting bogus return addresses has been
in
place since, uh, 2004. Ditto for always
$ diff mv.1.new mv.1
79c79
when the respective destination path is a non-empty directory,
---
when the respective destination path is a non-empy directory,
--
Scott McEachern
https://www.blackstaff.ca
Trying to compile libemu (http://libemu.carnivore.it/) on 5.1. Make
all breaks at:
gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I ../.. -Werror -Wall -g
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGE_FILES -g -O2
-Wstrict-prototypes -MT scprofiler.o -MD -MP -MF .deps/scprofiler.Tpo
-c -o
Nevermind. Disabled the flags in the Makefile and I was done.
--
http://www.glumbert.com/media/shift
http://www.youtube.com/watch?v=tGvHNNOLnCk
This officer's men seem to follow him merely out of idle curiosity.
-- Sandhurst officer cadet evaluation.
Securing an environment of Windows platforms
On 06/18/12 14:44, Scott McEachern wrote:
$ diff mv.1.new mv.1
79c79
when the respective destination path is a non-empty directory,
---
when the respective destination path is a non-empy directory,
Erm, sorry 'about that...
$ diff -u mv.1 mv.1.new
--- mv.1Wed Jun 6 14:22:11 2012
bofh wrote:
Nevermind. Disabled the flags in the Makefile and I was done.
Sounds like you're ignoring the problem which is usually a bad thing to do.
You're probably missing a header, or possibly the sequencing of the header
files is wrong. (inet(3) may help)
On 2012-06-18, bofh goodb...@gmail.com wrote:
Trying to compile libemu (http://libemu.carnivore.it/) on 5.1. Make
all breaks at:
gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I ../.. -Werror -Wall -g
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGE_FILES -g -O2
-Wstrict-prototypes -MT
On 2012 Jun 18 (Mon) at 17:16:25 + (+), Aaron W. Hsu wrote:
:lack of maintainer
That is exactly the case. Nobody actually did the work make it rock our
socks.
--
Shaw's Principle:
Build a system that even a fool can use,
and only a fool will want to use it.
That' sad - who got lost?
STEFAN
Gesendet: Montag, 18. Juni 2012 um 23:44 Uhr
Von: Peter Hessler phess...@theapt.org
An: Aaron W. Hsu arcf...@sacrideo.us
Cc: misc@openbsd.org
Betreff: Re: Story behind PCC's removal? On 2012 Jun 18 (Mon) at 17:16:25
+ (+), Aaron W. Hsu wrote:
:lack of
Committed, thanks!
On Mon, Jun 18, 2012 at 12:35 PM, Scott McEachern sc...@blackstaff.ca
wrote:
On 06/18/12 14:44, Scott McEachern wrote:
$ diff mv.1.new mv.1
79c79
when the respective destination path is a non-empty directory,
---
when the respective destination path is a non-empy
On Mon, Jun 18, 2012 at 10:16 AM, Aaron W. Hsu arcf...@sacrideo.us wrote:
Is there still any active
effort to move the code base of OpenBSD away from GCC dependence?
There's some grassroots effort to make Clang a viable option, but
nothing super organized at the moment.
geez, it's a /segway/
-- p
Dont steal the thread.
On Jun 18, 2012 9:55 AM, Peter Laufenberg open...@laufenberg.ch wrote:
speaking of stuck CAPSLOCK, anyone else having DEL/INS problems on US
keyboards w/ Euro key on 5? They're cheapo USB Dell manufactured by
Logitech. Tweaking wscons flags
I want to initiate a shutdown if the temperature gets too high. I have been
using sensorsd(8), but sensorsd(8) only reacts once to the high (or low)
event, leaving it up to the program/script to run timers to keep checking
if the temperature gets worse. For my satisfaction, the timers would have
My loongson patches didn't make 5.1 so either run -current (recommended)
or backport my patches to 5.1
Either way, you won't get JavaScript, so please keep that in mind (or
help me out! :) )
~Brian
How about setting low to the warning level, and high to the shutdown
level? That way you should be able to handle all 3 states w/o timers.
below being normal, within where it notifies and steps down CPU and
above where it does shutdown.
2012/6/19 Robert Connolly robertconnolly1...@gmail.com
I
æ¨å¥½misayuki
æå
¬å¸æ¯ææä¸å®æ°é¢ç
å
ç¨è½¦ç¥¨å¯èµ°å¯¹è½¦å¤ç°ä»£èµ°å¼,
å¦è´µå
¬å¸ææ¤é è¦, æå
¬å¸å°
ç«è¯ä¸ºæ¨æèµ°å¡ã
ç¨è½¦ç¹ä»ä¼ï¼æ¬¢è¿æ¥çµå¨è¯¢ã
ＱＱ: 815821020 å¼ å¾·æ
çµè¯ :l35 3O75 9889
11:19:21
sensorsd(8)'s low goes in the other direction. If I set low to 60C, it
will go off if the CPU is running at 50C. Sensorsd(8) isn't made for such
fine control as some of us would like.
If the battery is low, we want the sensor to alert us. If the temperature
is low, we do not want to be alerted.
35 matches
Mail list logo
