On Fri, Feb 7, 2014 at 4:03 PM, David Coppa dco...@gmail.com wrote:
On Fri, Feb 7, 2014 at 3:49 PM, Mark Kettenis mark.kette...@xs4all.nl wrote:
Date: Thu, 6 Feb 2014 23:07:58 -0800
From: Martynas Venckus marty...@venck.us
Yup.Does this diff fix it for you?
Here's a diff that sticks a
On 02/04/2014 01:49 AM, Robert Urban wrote:
On 02/03/2014 10:12 PM, Mike Larkin wrote:
I'd run with acpi debug enabled, try to see if we are dropping an event.
On a 5.4 test system I compiled a new generic MP kernel with option
ACPI_DEBUG
and booted it. I set up a serial console.
During
It was pointed out in a FreeBSD PR that one of the the nc(1) man page
examples no longer works. FreeBSD imports OpenBSD netcat.
With a commit on Wed Mar 20 09:27:56 2013 UTC nc.1 rev 1.62:
Don't shutdown nc(1)'s network socket when stdin closes. Matches
*Hobbit*'s original netcat and GNU netcat;
On Mon, Feb 10, 2014 at 11:23:33AM -0500, Allan Jude wrote:
It was pointed out in a FreeBSD PR that one of the the nc(1) man page
examples no longer works. FreeBSD imports OpenBSD netcat.
With a commit on Wed Mar 20 09:27:56 2013 UTC nc.1 rev 1.62:
Don't shutdown nc(1)'s network socket
As mentioned before on misc@, some user got confused and copied the
entire rc.conf file to rc.conf.local and then proceeded editing it. This
patch brings the rc.conf man page closer to the text that is in the
OpenBSD faq. Hopefully it will help newcomers avoiding this mistake.
Index:
Em 10-02-2014 18:28, Mark Kettenis escreveu:
Date: Mon, 10 Feb 2014 18:05:38 -0200
From: Giancarlo Razzolini grazzol...@gmail.com
As mentioned before on misc@, some user got confused and copied the
entire rc.conf file to rc.conf.local and then proceeded editing it. This
patch brings the
On 2014/02/10 18:42, Giancarlo Razzolini wrote:
Em 10-02-2014 18:28, Mark Kettenis escreveu:
Date: Mon, 10 Feb 2014 18:05:38 -0200
From: Giancarlo Razzolini grazzol...@gmail.com
As mentioned before on misc@, some user got confused and copied the
entire rc.conf file to rc.conf.local and
The existing text, Create and edit a _new_ rc.conf.local file seems
fine to me - man pages are generally non-verbose - if copying was intended,
the manual would have said so.
Disagree. Create and edit... is ambiguous. I can create
a new file by copying an old file and often do so. If you
Em 10-02-2014 19:34, Marco S Hyman escreveu:
The existing text, Create and edit a _new_ rc.conf.local file seems
fine to me - man pages are generally non-verbose - if copying was intended,
the manual would have said so.
Disagree. Create and edit... is ambiguous. I can create
a new file by
I'm looking for people with one of the following unsupported Intel
wireless chips:
Intel Centrino Wireless-N 2200 (shows up as Wireless-N 2000 in dmesg)
Intel Centrino Wireless-N 135
Intel Centrino Wireless-N 105
If you have one of these, please try the attached diff. It might give
you a
Works as expected on:
iwn0 at pci2 dev 0 function 0 Intel Centrino Wireless-N 2000 rev 0xc4: msi,
MIMO 2T2R, BGN, address 9c:4e:36:47:d3:24
Thanks!
-ml
On Mon, Feb 10, 2014 at 11:10:02PM +0100, Mark Kettenis wrote:
I'm looking for people with one of the following unsupported Intel
Hello,
I patched the sparc64 bootloader to allow users to manually specify
network config and where to load the kernel from via openfirmware
parameters instead of always requiring rarp/bootparams/bootp.
This enables remote bootstrapping of semi-recent sun boxes (like
the T1000) on networks where
Hello,
While hacking on the sparc64 bootloader (patch in another mail) I
had some questions about the recently added super-early entropy
loading code.
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/arch/sparc64/stand/ofwboot/boot.c.diff?r1=1.19;r2=1.20
From the commit message:
Try to load
Here's some documentation of it for www/
I think there should also be some mention of this functionality in
diskless(8), but I don't know where to put it, and I don't want to
just .Xr it to boot_sparc64 because diskless is for all archs and
none of the other boot_*s are referenced.
Index:
On Mon, Feb 10, 2014 at 20:58, Jean-Philippe Ouellet wrote:
2) I suspect that seeding your PRNG with data sent in the clear
isn't a great idea in the first place.
3) If you're netbooting anyway, by the time you actually fetch the
kernel you've already done a bunch of network operations.
I prefer this ...
--- rc.conf.8 Tue Feb 11 21:24:16 2014
+++ rc.conf.new.8 Fri Jan 3 00:44:18 2014
@@ -47,11 +47,11 @@
.Pp
It is advisable to leave
.Nm rc.conf
-untouched, and instead create and edit a new
+untouched. The
+.Nm rc.conf
+file includes a check for
.Nm rc.conf.local
I would completely support the addition of these options to dd.
I know and feel the same way. But I consider 2/dev/null in shell
scripts more evil. Instead of inventing something new, I used GNU.
Perhaps we should ask ourselves the question why this gets printed on
stderr instead of stdout?
Well, moving the output to stdout now would create a more grave
Here's a diff that sticks a bit closer to the original code. It's
equivalent to your diff, and admittedly purely a matter of taste which
version to prefer.
I prefer my version better. It's not '93 anymore and compilers are
able to convert 0.0L and -1.0L precisely, otherwise we have a huge
On Tue, Feb 11, 2014 at 6:35 AM, Martynas Venckus
marty...@cvs.openbsd.org wrote:
Here's a diff that sticks a bit closer to the original code. It's
equivalent to your diff, and admittedly purely a matter of taste which
version to prefer.
I prefer my version better. It's not '93 anymore and
20 matches
Mail list logo
