Here are two small fixes to the pf(4) man page to make pfioc_natlook
and pfr_addr match net/pfvar.h.
OK?
Index: pf.4
===
RCS file: /cvs/src/share/man/man4/pf.4,v
retrieving revision 1.74
diff -u -p -r1.74 pf.4
--- pf.410 Feb
This diff adds the key binding 'q' and function 'quit-window' to mg's
dired mode. Comments/oks?
mark
Index: buffer.c
===
RCS file: /cvs/src/usr.bin/mg/buffer.c,v
retrieving revision 1.90
diff -u -p -r1.90 buffer.c
--- buffer.c17
The man page has an error... it should read:
.It q
quit-window
- Forwarded message from Mark Lumsden -
Date: Sat, 1 Jun 2013 15:05:16 +
From: Mark Lumsden
To: tech@openbsd.org
Subject: mg(1) 'q' for quit-window in dired mode
User-Agent: Mutt/1.5.21 (2010-09-15)
This diff adds the
Some machines (eg VMs running in VMware) display hundreds of wakeup devices,
polluting dmesg output with many lines of output. One VM dmesg I was shown
indicated 816 wakeup devices.
Since it is unlikely that any real machines have more than 16 wakeup devices,
truncate the count at 16, and after th
On Sat, Jun 01, 2013 at 06:35:24AM -0700, Mike Larkin wrote:
> [...]
> SIMPLEQ_FOREACH(wentry, &sc->sc_wakedevs, q_next) {
> - printf(" %.4s(S%d)", wentry->q_node->name,
> - wentry->q_state);
> + if (wakeup_dev_ct < 16)
> + printf("
On Sat, Jun 01, 2013 at 07:40:56PM +0200, Gregor Best wrote:
> On Sat, Jun 01, 2013 at 06:35:24AM -0700, Mike Larkin wrote:
> > [...]
> > SIMPLEQ_FOREACH(wentry, &sc->sc_wakedevs, q_next) {
> > - printf(" %.4s(S%d)", wentry->q_node->name,
> > - wentry->q_state);
> > +
On Sat, Jun 01, 2013 at 06:57:21AM -0700, Mike Larkin wrote:
> [...]
> Sure, go ahead.
> [...]
Then I propose the following variant of the patch:
Index: dev/acpi/acpi.c
===
RCS file: /cvs/src/sys/dev/acpi/acpi.c,v
retrieving revision
> Date: Sat, 1 Jun 2013 06:35:24 -0700
> From: Mike Larkin
>
> Some machines (eg VMs running in VMware) display hundreds of wakeup devices,
> polluting dmesg output with many lines of output. One VM dmesg I was shown
> indicated 816 wakeup devices.
>
> Since it is unlikely that any real machines
On Sat, Jun 01, 2013 at 08:02:40PM +0200, Mark Kettenis wrote:
> > Date: Sat, 1 Jun 2013 06:35:24 -0700
> > From: Mike Larkin
> >
> > Some machines (eg VMs running in VMware) display hundreds of wakeup devices,
> > polluting dmesg output with many lines of output. One VM dmesg I was shown
> > ind
On Sat, Jun 01, 2013 at 08:01:58PM +0200, Gregor Best wrote:
> On Sat, Jun 01, 2013 at 06:57:21AM -0700, Mike Larkin wrote:
> > [...]
> > Sure, go ahead.
> > [...]
>
> Then I propose the following variant of the patch:
>
code and dmesg looks fine, ok reyk@
acpi0: wakeup devices PCI0(S3) USB_(S1
Currently, ICMP(v4) checksums are calculated using in_cksum(), which
requires the following m_data/m_len dance:
hlen = ip->ip_hl << 2;
m->m_data += hlen;
m->m_len -= hlen;
icp = mtod(m, struct icmp *);
icp->icmp_cksum = 0;
icp->icmp_cksum = in_cksum(
On Mon, May 20, 2013 at 11:57:55PM +0600, Alexandr Shadchin wrote:
> On Thu, May 02, 2013 at 10:11:23PM +0600, Alexandr Shadchin wrote:
> > Hi,
> >
> > This update xf86-input-synaptics to the latest release 1.7.0.
> > http://koba.devio.us/distfiles/xf86-input-synaptics-1.7.0.diff
> >
> > Tested o
Mike Larkin azathoth.net> writes:
> It's sometimes nice to know what devices can wake up a machine, and from what
> sleep state. But I'm fine suppressing these also. Don't want this to end up
> being a bikeshed :)
why not dnprintf them?
> Mike Larkin azathoth.net> writes:
>
> > It's sometimes nice to know what devices can wake up a machine, and from
> > what
> > sleep state. But I'm fine suppressing these also. Don't want this to end up
> > being a bikeshed :)
>
> why not dnprintf them?
good grief. We are displaying the info
On Sun, Jun 2, 2013 at 12:05 AM, Theo de Raadt wrote:
>> Mike Larkin azathoth.net> writes:
>>
>> > It's sometimes nice to know what devices can wake up a machine, and from
>> > what
>> > sleep state. But I'm fine suppressing these also. Don't want this to end up
>> > being a bikeshed :)
>>
>> wh
> Date: Sun, 2 Jun 2013 00:09:25 +0300
> From: Alexey Suslikov
>
> On Sun, Jun 2, 2013 at 12:05 AM, Theo de Raadt
> wrote:
> >> Mike Larkin azathoth.net> writes:
> >>
> >> > It's sometimes nice to know what devices can wake up a machine, and from
> >> > what
> >> > sleep state. But I'm fine s
On Sun, Jun 2, 2013 at 12:14 AM, Mark Kettenis wrote:
>> Date: Sun, 2 Jun 2013 00:09:25 +0300
>> From: Alexey Suslikov
>>
>> On Sun, Jun 2, 2013 at 12:05 AM, Theo de Raadt
>> wrote:
>> >> Mike Larkin azathoth.net> writes:
>> >>
>> >> > It's sometimes nice to know what devices can wake up a mac
wow.
don't you read? the wakeup devices (or at least the first few) are
only being printed to give a few developers who care about suspend/resume
a hand.
that's it. it is for us, not for you.
> just an idea (I know more knobs are not good), but sysctl already have some
> acpi related informati
In /usr/src/games/trek
When computer calculates warpcost, labels are incorrectly transposed for
"stardates" and "cost". This is affirmed by the fact that time should go
down as warp speed goes up, and energy consumed should also go up with
warp speed. Additionally, the cost of "w/ shlds up" double
On Sun, Jun 02, 2013 at 12:20:56AM +0300, Alexey Suslikov wrote:
> On Sun, Jun 2, 2013 at 12:14 AM, Mark Kettenis
> wrote:
> >> Date: Sun, 2 Jun 2013 00:09:25 +0300
> >> From: Alexey Suslikov
> >>
> >> On Sun, Jun 2, 2013 at 12:05 AM, Theo de Raadt
> >> wrote:
> >> >> Mike Larkin azathoth.net
Hi Ted,
Ted Roby wrote on Sat, Jun 01, 2013 at 02:25:50PM -0700:
> In /usr/src/games/trek
>
> When computer calculates warpcost, labels are incorrectly transposed for
> "stardates" and "cost". This is affirmed by the fact that time should go
> down as warp speed goes up, and energy consumed shou
Diff below fixes our wcsto{f,d,ld}() implementations in the following
ways:
- It handles "inf", "infinity", "nan", and "nan(whatever)" forms.
- It rejects strings like "-" and "+" by excluding the sign
characters when checking that we've actually matched some characters
to parse.
- Because
22 matches
Mail list logo
