Re: umb(4) authentication
| > > | > > This email should be gold plated and moved to a permanent location in | > > the FAQ on how to help OpenBSD and how to request new features. | > > | > | > Please refrain from ridiculing people with good intentions. | > | I originally read Anders' mail as complimentary, but now I'm not so sure? | | Lee. | Hi Lee, Just ignore this Anders person. If a developer who works in this area doesn't reply in the next couple of days, you could either send the diffs to tech@ or reach out to a recent committer to the same area of code, you can see who committed via cvs or https://cvsweb.openbsd.org/src/ Brett.
Re: lynx: disable old protocols
On Fri, 11 Jul 2014 09:48:12 +0100 Stuart Henderson st...@openbsd.org wrote: | On 2014/07/11 01:18, Theo de Raadt wrote: | I too use gopher in lynx regularly, and would miss support. There is = | still a surprisingly active community using gopher. (floodgap, et al.) | | So install a package. | | Should we just move lynx to packages? | I find lynx really handy to have in base, e.g. installing on a new machine, users can just go to openbsd.org and cut and paste a pkg_path prior to installing anything, and read the faq. Using openbsd for the first time would have been a lot more painful without a browser in base.
Re: mirrorlist file proposal
On Mon, 9 Jun 2014 14:26:15 +0200 misc nick misc.n...@gmx.com wrote: | OpenBSD has one of the simplest and most compact installers out there. | | However, at the end of the installation you need to have another internet | connected OS in order to copy the address of the mirror you wish to use | for package management to your freshly installed OpenBSD. | You can also just use lynx (which by default resolves to openbsd.org) and navigate to the list via the 'getting releases' link. Brett.
Re: userland not building after tmux change
On Tue, 1 Apr 2014 16:46:43 +1100 Brett Mahar br...@coiloptic.org wrote: | Hi Tech@, | | Building current today on amd64 stops as below. | Theo has fixed, is working now.
userland not building after tmux change
Hi Tech@,
Building current today on amd64 stops as below.
Brett.
cc -O2 -pipe-c /usr/src/usr.bin/tmux/cmd-switch-client.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/cmd-unbind-key.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/cmd-unlink-window.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/cmd-wait-for.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/cmd.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/cmd-queue.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/colour.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/control.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/control-notify.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/environ.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/format.c
/* $OpenBSD: log.c,v 1.10 2014/03/31 21:42:45 nicm Exp $ */
cc -O2 -pipe-c /usr/src/usr.bin/tmux/grid-cell.c
/* $OpenBSD: tmux.h,v 1.445 2014/03/31 21:42:27 nicm Exp $ */
cc -O2 -pipe-c /usr/src/usr.bin/tmux/grid-view.c
#define MODE_MOUSE_UTF8 0x100
#define MODE_MOUSE_SGR 0x200
#define MODE_BRACKETPASTE 0x400
#define MODE_FOCUSON 0x800
#define ALL_MOUSE_MODES (MODE_MOUSE_STANDARD|MODE_MOUSE_BUTTON|MODE_MOUSE_ANY)
/* A single UTF-8 character. */
struct utf8_data {
u_char data[UTF8_SIZE];
size_t have;
size_t size;
cc -O2 -pipe-c /usr/src/usr.bin/tmux/grid.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/input-keys.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/input.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/job.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/key-bindings.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/key-string.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/layout-custom.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/layout-set.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/layout.c
cc -O2 -pipe-c /usr/src/usr.bin/tmux/log.c
/usr/src/usr.bin/tmux/log.c:43: error: conflicting types for 'log_open'
/usr/src/usr.bin/tmux/tmux.h:2334: error: previous declaration of 'log_open'
was here
*** Error 1 in usr.bin/tmux (sys.mk:87 'log.o')
*** Error 1 in usr.bin (bsd.subdir.mk:48 'all')
*** Error 1 in . (bsd.subdir.mk:48 'all')
*** Error 1 in /usr/src (Makefile:89 'build')
Small fixup for smtpd.conf.5
Hi, This points me in the right direction so I'm less confused. ok? Brett. Index: src/usr.sbin/smtpd/smtpd.conf.5 === RCS file: /usr/cvsync/src/usr.sbin/smtpd/smtpd.conf.5,v retrieving revision 1.113 diff -u -p -u -r1.113 smtpd.conf.5 --- src/usr.sbin/smtpd/smtpd.conf.5 6 Dec 2013 10:42:15 - 1.113 +++ src/usr.sbin/smtpd/smtpd.conf.5 12 Dec 2013 22:23:03 - @@ -288,7 +288,7 @@ Mail is added to a maildir. Its location, .Ar path , may contain format specifiers that are expanded before use -(see above). +(see below). If .Ar path is not provided, then
Re: Small fixup for smtpd.conf.5
| Well, deliver to mda has exactly the same issue. I'd say that format | specifiers could use their own subsection. | | While here I propose to replace \ by \(dq, as advised by | mandoc_char(7). This has the nice property of not fscking up the | display of your too-smart-for-its-own-good editor. | | Does this look better? Yes, and ok brett@. | | Index: smtpd.conf.5 | === | RCS file: /cvs/src/usr.sbin/smtpd/smtpd.conf.5,v | retrieving revision 1.113 | diff -u -p -p -u -r1.113 smtpd.conf.5 | --- smtpd.conf.5 6 Dec 2013 10:42:15 - 1.113 | +++ smtpd.conf.5 12 Dec 2013 23:05:29 - | @@ -39,7 +39,7 @@ the comment is effective until the end o | Argument names not beginning with a letter, digit, or underscore | must be quoted. | Arguments containing whitespace should be surrounded by double quotes | -.Pq \ . | +.Pq \(dq . | .Pp | Macros can be defined that will later be expanded in context. | Macro names must start with a letter, digit, or underscore, | @@ -288,7 +288,7 @@ Mail is added to a maildir. | Its location, | .Ar path , | may contain format specifiers that are expanded before use | -(see above). | +.Pq see Sx FORMAT SPECIFIERS . | If | .Ar path | is not provided, then | @@ -302,7 +302,7 @@ Mail is piped to the specified | .Ar program , | which is run with the privileges of the user the message is destined to. | This parameter may use conversion specifiers that are expanded before use | -(see above). | +.Pq see Sx FORMAT SPECIFIERS . | .It Xo | .Ic relay | .Op Ic backup Op Ar mx | @@ -806,7 +806,7 @@ many mappings as a list of comma separat | .Ar key Ns = Ns Ar value | descriptions. | .El | -.Pp | +.Ss FORMAT SPECIFIERS | Some configuration directives support expansion of their parameters at runtime. | Such directives (for example | .Ar deliver to maildir ,
Re: nfe driver
Date: Wed, 18 May 2011 09:16:39 -0500 (CDT) From: L. V. Lammert l...@omnitec.net To: tech@openbsd.org Subject: nfe driver Message-ID: pine.bso.4.53.1105180913130.1...@mail.omnitec.net Just upgraded a machine to AMD64, .. and the MB has an NVIDIA nForce MCP ethernet onboard. Unfortunately, the nfe driver configures but will not pass traffic. Before I drop in another card, would any data or troubleshooting be useful? Lee Hi Lee, I used to have an eMachines ET-1300, its motherboard was MCP61 from Nvidia, and the ethernet card used nfe driver. In OpenBSD 4.7 AMD64 it worked fine, later I used OpenBSD 4.8 i386, also no problem with ethernet. The computer is currently sitting in a cupboard on the other side of the world, so I haven't tried 4.9 on it. But hopefully this info will help you narrow down your problem - I guess either a regression or a broken ethernet card? Brett.
