On Sun, Jun 22, 2014 at 08:04:27PM -0700, Philip Guenther wrote:
On Tue, Jun 17, 2014 at 3:45 PM, Gustav Fransson Nyvell gus...@nyvell.se
wrote:
I want to alert you to this strange observation.
$ sysctl -a
...
hw.cpuspeed=3101
hw.setperf=100
...
This on an Intel i7 3920XM.
YASUOKA Masahiko yasu...@yasuoka.net writes:
ok?
ok
Fix compile without IPSEC.
Pointed out by Ivan Solonin.
Index: sys/netinet/udp_usrreq.c
===
RCS file: /disk/cvs/openbsd/src/sys/netinet/udp_usrreq.c,v
retrieving revision
On 06/23/14 05:04, Philip Guenther wrote:
On Tue, Jun 17, 2014 at 3:45 PM, Gustav Fransson Nyvell
gus...@nyvell.se mailto:gus...@nyvell.se wrote:
I want to alert you to this strange observation.
$ sysctl -a
...
hw.cpuspeed=3101
hw.setperf=100
...
This on an Intel
Hi,
Using ftp(1) with HTTP(S) scheme and Basic auth, it is currently not
possible to have username (or password) with a '@' inner.
For example, this URI is badly parsed:
ftp https://mym...@example.com:my-passw...@another-domain.example.com/blabla
According to RFC2617, '@' is a valid character
Diff below implements file/line number decoding in ddb for ELF; e.g.,
ddb{2} trace
Debugger() at Debugger+0x9 [../../../../arch/amd64/amd64/db_interface.c:406]
ddb_sysctl() at ddb_sysctl+0x1b4 [../../../../ddb/db_usrreq.c:104]
sys___sysctl() at sys___sysctl+0x214
Hi,
This patch adds some intelligence to emacs mode filename completion when dealing
with quotes in ksh.
Example:
$ ls '/booTAB
$ ls 'boot point
becomes:
$ ls 'boot' point
Index: emacs.c
===
RCS file:
GCC supports an aligned attribute to specify a minimum alignment for
types/objects. However, if an object is allocated on the stack and
its alignment exceeds the preferred stack boundary, then GCC 4.2
silently ignores the alignment.
[...]
Since newer GCC properly support overly aligned
Hi,
there should be some more validations in boot.c. Not just to validate
the filesystem, but to make sure that the program won't crash later on
because it assumes some values...
First chunk: The sectors per cluster have to be a power of 2, otherwise
it's possible to send fsck_msdos over the
And again...
Could have saved myself time by checking FreeBSD in detail first.
They fixed the issue by adding a simple check:
According to FAT specs, the size of a cluster shall not exceed 64 KB.
That is even a rare case, 32 KB shouldn't be crossed for compatibility
reasons.
Therefore, it's
Henning Brauer lists-openbsdt...@bsws.de writes:
since no consensus could be found yet for a new command line option to
ifconfig, heck, not even about wether it is needed, I propose this for
now.
I didn't reply to your proposal but since you've just committed the
ifconfig part, I think I
j...@wxcvbn.org (Jérémie Courrèges-Anglas) writes:
Henning Brauer lists-openbsdt...@bsws.de writes:
since no consensus could be found yet for a new command line option to
ifconfig, heck, not even about wether it is needed, I propose this for
now.
I didn't reply to your proposal but since
On Mon, Jun 23, 2014 at 9:59 AM, Miod Vallat m...@online.fr wrote:
I love this. I have verified that kernels for all our gcc4 platforms
still build with this diff.
Awesome! I also heard back from guenther@ that he completed an i386
base build without warnings too.
Do we want to test this any
If you really want to be pedantic, it should be if defined(PIPEX) ||
defined(IPSEC)
YASUOKA Masahiko [yasu...@yasuoka.net] wrote:
ok?
Fix compile without IPSEC.
Pointed out by Ivan Solonin.
Index: sys/netinet/udp_usrreq.c
So I have been trying to write a new audio driver (for Xonar DS if
anyone interested) and therefore reading audio(9).
I was confused for a while by the use of will here. I think it's not
clear enough that these functions should be called by the driver code.
I'm not a native speaker, so may be
I'm volunteering for this job. I know that other people have already
expressed interest in such a task. Can we please postpone
ifp-if_xflags |= IFXF_NOINET6;
until the situation is more clear? I think 5.6 is a safe bet.
No. Apparently you are the only one who keeps postponing action,
On Sun, Jun 22, 2014 at 11:47 PM, Jérémie Courrèges-Anglas j...@wxcvbn.org
wrote:
YASUOKA Masahiko yasu...@yasuoka.net writes:
ok?
ok
On Sun, Jun 22, 2014 at 7:28 PM, YASUOKA Masahiko yasu...@yasuoka.net
wrote:
ok?
Fix compile without IPSEC.
Pointed out by Ivan Solonin.
...and Theo just reverted this because it broke RAMDISK compiles!
Messing with kernel options #ifdefs without testing by building a release
is unwise.
On Mon, 23 Jun 2014 16:33:46 -0700
Philip Guenther guent...@gmail.com wrote:
On Sun, Jun 22, 2014 at 7:28 PM, YASUOKA Masahiko yasu...@yasuoka.net
wrote:
ok?
Fix compile without IPSEC.
Pointed out by Ivan Solonin.
...and Theo just reverted this because it broke RAMDISK compiles!
On Mon, Jun 23, 2014 at 10:14 PM, YASUOKA Masahiko yasu...@yasuoka.net
wrote:
On Mon, 23 Jun 2014 16:33:46 -0700
Philip Guenther guent...@gmail.com wrote:
...
Messing with kernel options #ifdefs without testing by building a release
is unwise. People messing with changing kernel options
19 matches
Mail list logo
