Re: Using ports and updates to the release

2020-10-28 Thread Marc Espie
On Sun, Oct 11, 2020 at 09:12:13PM +0200, Ingo Schwarze wrote: > Hi Ed, > > Ed Gray wrote on Sun, Oct 11, 2020 at 07:21:32PM +0100: > > > I'm still fairly new to openbsd and the idea of using ports > > in general rather than binary packages. > > You are usually better off using packages than

Re: Internal microphone not working

2020-10-28 Thread Marcus MERIGHI
Hello Ashton, ash...@fagg.id.au (Ashton Fagg), 2020.10.28 (Wed) 01:31 (CET): > However, I'm having problems getting my internal microphone to work. what does $ sysctl kern.audio.record say? Marcus

Re: Internal microphone not working

2020-10-28 Thread Mihai Popescu
[ ... ] So, why do you trim outputs? Where is the full dmesg? Do you fear something? Do you realize that your and other people's problems with sound in particular CAN BE related to other hardware present in your computer or a specific configuration?

Re: Authenticating Location in HTTPD

2020-10-28 Thread Romain FABBRI
I use this config for wordpress : authenticate "WordPress" with "/htdocs/htpasswd" Place the htpasswd file at the root of your chroot This file should not be served of course Check your logs for errors if not working Romain -Message d'origine- De : owner-m...@openbsd.org De la part de

Re: Authenticating Location in HTTPD

2020-10-28 Thread Gleydson Soares
On Wed, Oct 28, 2020 at 09:40:24AM -0400, ben wrote: > Hello, Misc; > > I'm attempting to configure authentication for a location in httpd... > > server "example.com" { > listen on * port 80 > root "/htdocs/example.com/" > location "/" { > authenticate

Re: Internal microphone not working

2020-10-28 Thread Anders Damsgaard
* Ashton Fagg [2020-10-27 20:31:29 -0400]: I'm running a ThinkPad T14s. There's been some recent additions to the azalia driver to help make audio work a little better on this machine (it now works and seems to get configured correctly). However, I'm having problems getting my internal

Authenticating Location in HTTPD

2020-10-28 Thread ben
Hello, Misc; I'm attempting to configure authentication for a location in httpd... server "example.com" { listen on * port 80 root "/htdocs/example.com/" location "/" { authenticate with "/passwds" } } However upon navigating to the designated

Re: Internal microphone not working

2020-10-28 Thread Ashton Fagg
Marcus MERIGHI writes: > what does > $ sysctl kern.audio.record > say? [fagg@moon][~][0] -> sysctl kern.audio.record kern.audio.record=1

Re: search contains unknown domain in resolv.conf

2020-10-28 Thread Otto Moerbeek
On Tue, Oct 27, 2020 at 11:44:21PM +0300, Andreas X wrote: > ignore domain-search; > supersede domain-name mail.myserver.tld; > supersede domain-search mail.myserver.tld; > > None of these lines have worked in dhclient.conf The domain name need to be quoted. What did you do exactly? Did you

Re: Should I download 'distfiles/by_cipher ' or 'rsysnc --exlude by_chipher' ?

2020-10-28 Thread Stuart Henderson
On 2020-10-27, Martin wrote: > Do I need 'distfiles/by_cipher' in mirrored repo? > > Or may I exclude 'rsysnc --exlude by_cipher' while mirroring repository > without negative effects possible? > > Martin > > You don't usually want to mirror distfiles at all.

Re: Snapshot crash on boot, "entry point at: 0x1001000" (Intel Gemini Lake)

2020-10-28 Thread Theo de Raadt
This particular diff is in snapshots. That's a shortcut which will let more people try it quicker, and report back. > thanks to the fix from Mark, see > https://marc.info/?l=openbsd-tech=160383074317608=2 the problem is > solved for my machine. > > Best regards, > Sven > > On 10/10/20 11:56

Re: Internal microphone not working

2020-10-28 Thread Theo de Raadt
Ashton Fagg wrote: > I've translated that since I'm not sure those among us speak rude, > codescending clown. And now far fewer people want to help you. Such a winner...

Chromium not starting on Thinkpad R40E with 6.8

2020-10-28 Thread Anthony Campbell
I upgraded to the i386 version of 6.8-Release on three different Thinkpads R40E. On all of them, chromium fails to start, saying "Unable to allocate memory". I suppose these are so ancient that it's hardly surprising (can't be mamy still around), but I thought I'd report it anyway. Here is the

Re: Fwd: Re: man netstart(8) OpenBSD-6.8

2020-10-28 Thread pipus
aye agreed. Another option which we were also looking at it a community wiki as a separate src. So sys admins and devs can upload their own usage examples easily. With the caveat ofc that these are not official examples. If you could do something like a triple pipe ||| or even a "sudo !!!"

Re: Snapshot crash on boot, "entry point at: 0x1001000" (Intel Gemini Lake)

2020-10-28 Thread Sven Wolf
Hi, thanks to the fix from Mark, see https://marc.info/?l=openbsd-tech=160383074317608=2 the problem is solved for my machine. Best regards, Sven On 10/10/20 11:56 AM, Sven Wolf wrote: Hi, on my Lenovo V130 I've to build a custom kernel without radeondrm and amdgpu.

Re: Internal microphone not working

2020-10-28 Thread Ashton Fagg
Mihai Popescu writes: > [ ... ] > > So, why do you trim outputs? Where is the full dmesg? Do you fear something? > > Do you realize that your and other people's problems with sound in > particular CAN BE related to other hardware present in your computer or a > specific configuration? I'm not

Re: snapshot boot fails with error "entry point at 0x1001000"

2020-10-28 Thread Fabian
Hi all, For the record, Mark Kettenis' patch below fixed the boot stuck problem on my Intel NUC Kit NUC7PJYH mini server, see the following email thread: https://marc.info/?l=openbsd-misc=160391516603159 Thanks a lot for this. Cheers. Fabian > Hi Mark, > > on my Lenovo V130 the patch works.

Re: Following the upgrade to 6.8, sshguard is reporting that it fails to start

2020-10-28 Thread Daniel Jakots
On Wed, 28 Oct 2020 16:53:03 -0500, Todd wrote: > Following the upgrade to 6.8, rcctl is reporting that sshguard fails > to start. > > rcctl check sshguard > sshguard(failed) > [...] > apu$ rcctl get sshguard > > > sshguard_class=daemon > sshguard_flags=-l

Re: wg(4) listen on a specific interface / address

2020-10-28 Thread Brian Brombacher
> On Oct 28, 2020, at 6:21 PM, Brian Brombacher wrote: > >  > >> On Oct 28, 2020, at 5:07 PM, Pierre Emeriaud >> wrote: >> >> Le mar. 27 oct. 2020 à 23:46, j...@snoopy.net.nz a >> écrit : >>> >>> >>> >>> Hi Pierre, >>> >>> The error may indicate that port 53 on 127.0.0.1 is

Re: wg(4) listen on a specific interface / address

2020-10-28 Thread Theo de Raadt
Pierre Emeriaud wrote: > Le mar. 27 oct. 2020 à 23:46, j...@snoopy.net.nz a écrit > : > > > > > > > > Hi Pierre, > > > > The error may indicate that port 53 on 127.0.0.1 is already used by another > > service. This appears to be confirmed by your netstat example. This is > > probably a dns

Re: wg(4) listen on a specific interface / address

2020-10-28 Thread Pierre Emeriaud
Hi Brian Le mar. 27 oct. 2020 à 23:07, Brian Brombacher a écrit : > > I wonder if multiple ports, 5053, 5153 (and so on) redirected using pf rdr-to > rules may work? That way you can setup rules like first IP + port 53 > redirect to 5053, second IP + 53 redirect to 5153? > > May be worth a

Re: wg(4) listen on a specific interface / address

2020-10-28 Thread Pierre Emeriaud
Le mar. 27 oct. 2020 à 23:46, j...@snoopy.net.nz a écrit : > > > > Hi Pierre, > > The error may indicate that port 53 on 127.0.0.1 is already used by another > service. This appears to be confirmed by your netstat example. This is > probably a dns service. Thanks Joe. This is indeed a dns

Following the upgrade to 6.8, sshguard is reporting that it fails to start

2020-10-28 Thread Todd
I have been using the sshguard package for the last several releases. Following the upgrade to 6.8, rcctl is reporting that sshguard fails to start. rcctl check sshguard sshguard(failed) Below is the relevant information I can think of to provide. Are there additional troubleshooting

Re: wg(4) listen on a specific interface / address

2020-10-28 Thread Brian Brombacher
> On Oct 28, 2020, at 5:07 PM, Pierre Emeriaud > wrote: > > Le mar. 27 oct. 2020 à 23:46, j...@snoopy.net.nz a > écrit : >> >> >> >> Hi Pierre, >> >> The error may indicate that port 53 on 127.0.0.1 is already used by another >> service. This appears to be confirmed by your netstat

Re: OpenBSD 6.8 release boot stuck on Intel NUC NUC7PJYH

2020-10-28 Thread Fabian
Hi Sven, misc, Thanks for your email and the effort of putting up a patched EFI boot file. Much appreciated. It took a long time to make a release in my case. I too can confirm that the patch by Marc Kettenis linked below [1] resolved the boot issue on the Intel NUC. It boots fine again now, and

Re: Using ports and updates to the release

2020-10-28 Thread Ed Gray
Hi Marc, Thanks for your reply. I think maybe this belongs to ports more than misc. But it's a general query about releases and ports as well. My question was actually about updating the ports tree from an older release version before trying to use it rather than whether to use ports or

Re: Chromium not starting on Thinkpad R40E with 6.8

2020-10-28 Thread Ashton Fagg
Anthony Campbell writes: > I upgraded to the i386 version of 6.8-Release on three different > Thinkpads R40E. On all of them, chromium fails to start, saying "Unable > to allocate memory". > > I suppose these are so ancient that it's hardly surprising (can't be > mamy still around), but I

Re: Chromium not starting on Thinkpad R40E with 6.8

2020-10-28 Thread Stuart Henderson
On 2020-10-28, Anthony Campbell wrote: > I upgraded to the i386 version of 6.8-Release on three different > Thinkpads R40E. On all of them, chromium fails to start, saying "Unable > to allocate memory". How does your datasize limit look? Try bumping it as high as it will go ("infinity" in

Re: Chromium not starting on Thinkpad R40E with 6.8

2020-10-28 Thread Stuart Henderson
On 2020-10-28, Ashton Fagg wrote: > Anthony Campbell writes: > >> I upgraded to the i386 version of 6.8-Release on three different >> Thinkpads R40E. On all of them, chromium fails to start, saying "Unable >> to allocate memory". >> >> I suppose these are so ancient that it's hardly surprising