Re: Testers needed for ahc(4) diff
On 07/04/11 09:59, Henning Brauer wrote: looks like you did everything right, except trhat you don't actually have an ahc controller :) Yes, Theo pointed that out within about 10 seconds of my posting the dmesg. My brain got muddled between ahc and ahci.
Re: Testers needed for sdmmc_scsi.c diff
On 07/08/11 17:52, Matthew Dempsky wrote: Please check that SD cards still work with this diff. Index: sdmmc_scsi.c === RCS file: /cvs/src/sys/dev/sdmmc/sdmmc_scsi.c,v retrieving revision 1.28 diff -u -p -r1.28 sdmmc_scsi.c --- sdmmc_scsi.c9 Jul 2011 00:39:29 - 1.28 +++ sdmmc_scsi.c9 Jul 2011 00:51:34 - Hi, Just tested with i386 current using msdosfs and ffs and all is well. 4gb microsd card in a sd card adapter. Brett.
Re: wpi: add sensor for rfkill
On Tue, 22 May 2012 20:20:38 +0200 Gregor Best g...@ring0.de wrote: Hi people, the attached patch adds an indicator sensor to wpi devices that describes the current RFKill status. If the RF killswitch is engaged, the sensor reads Off, if it is not engaged and the device can operate, it reads On. If this is okay, I plan on adding similar sensors to other wireless devices, but in that case I'd need help testing those because I only have access to wpi devices. -- Gregor Best Hi Gregor, I wonder if it will be possible to tell interfaces to ignore the rfkill switches if this goes in? I have an exopc tablet and it is impossible to run regular linux on it, because the rfkill is hardwired permanently off, so no wifi possible. Also I have seen a laptop (I think it was a HP) where the rfkill button is broken off, so again no wifi possible, as its killed by rfkill. Brett.
Re: vmyield diff (2) please test
On Thu, 14 Jun 2012 03:48:12 +0200 Ariane van der Steldt ari...@stack.nl wrote: Hi, This diff implements yielding in the vm system, with the intention to make expensive system calls preempt every once in a while, to allow userland system calls to progress. The diff has a name ofcourse: vmyield.2.diff Please test this on your machines. -- Ariane Hi Ariane and tech@, Using this since Thursday on both amd64 and i386 current, rebuilt systems, have not noticed any issues. Brett.
Re: Reduce IPI traffic from signals
On Mon, 23 Jul 2012 20:45:17 +0400 Alexander Polakov p...@sdf.org wrote: This diff reduces IPI traffic for a case when process A is sending a lot of signals to process B running on a different CPU. userret() delivers all process signals at once, so there is no need to send an interrupt for every signal. The problem was noticed by rtorrent 0.9.2 users, which does exactly this, which led to process/system hangs and slowness. Tested and known to help on amd64 by me and dcoppa@. Hi Alexander and tech, I've tried this on i386-current built July 25, building ports of rtorrent 0.9.2 and libtorrent 13.2 (instead of the reverted versions). With upload and download rates between 40-50k in each direction, systat reports ipi between 13 and 5696 prior to this patch being applied (on a June 25th -current). The ipi sits between 10 and 82 with this patch. The keyboard navigation in the rtorrent ncurses interface seems a bit more responsive, too. Brett.
Re: upstream vendors and why they can be really harmful
On Tue, 6 Nov 2012 13:38:32 +0100 Marc Espie es...@nerim.net wrote: Basically, we have a pattern, mostly observed with kde (and a bit with gnome) which is really harmful for us. They occupy a few people in our team FULLTIME with respect to gnome, they're the reason we still DON'T have a full kde4 in our tree (hopefully to be addressed shortly), and they're the reason why sometimes we do drop old stuff (like killing gtk+1, and people really wanting to kill some gtk2/qt3 stuff). It's also quickly turning Posix and Unix into a travesty: either you have the linux goodies, or you don't. And if you don't, you can forget anything modern... Not to disparage the hard work by Antoine and others on Gnome and KDE, but if upstream are going to entwine their code with non-standard OSs, then why bother with them? If everyone but the mainstream Linux distros dropped their projects, it seems a more likely way of getting through to the upstream developers than joining their project or sending them emails. I use Joe's Window Manager, it compiles in less than a minute straight from the sources with no patching or tweaking. I don't have semi-transparent windowbars and I had to make a couple of tweaks so I could hear a beep when I get an IM, apart from that, what can a modern window manager do that is worth the some porter's pain (and extra 10-20% cpu consumption to run) anyway? Stuff like X is a different matter, if upstream must be battled, I would say send the troops to defend what is hard to do without, not what is easy to do without. Brett.
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: 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.
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 ,
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')
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.
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.
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.
