Re: Turn off Swap on boot disk

> On Nov 21, 2019, at 23:54, Theo de Raadt wrote: > > wait until you see the next thing i'm interested in. modern > machines will barely notice it, but alix's will quake. I look forward to what’s in store. As for all the other helpful comments (from Theo and others), thank you. The worklo

Re: Sonos and OpenBSD PF - anyone on-list with experience ?

Thanks all for your ideas.  I'll spend a little time on it over the next few days and see how far I can get. 22 Nov 2019, 16:34 by s...@spacehopper.org: > On 2019-11-22, Peter N. M. Hansteen wrote: > >> On Fri, Nov 22, 2019 at 12:56:51PM +0100, Rachel Roch wrote: >> >> >>> They sent me th

bgpd not exporting default route

Hi, I'm probably being completely dumb here, but I'm adding an additional perimiter router to my network which is running OpenBSD 6.6. My current perimiter is a 6.4 instance (soon to be upgraded !) which talks BGP to internal firewalls. The config below works perfectly on 6.4, but on 6.6, the

Update Groups: Submitting Iran BSD User Group (IRBUG)

0 C Iran P Teheran T Teheran F Last Thursday of the month O Iran BSD User Group (IRBUG) I Faraz Vahedi M k...@irbug.org U https://www.irbug.org/ N *BSD

Re: No WAF detected

On 2019-11-22, Kihaguru Gathura wrote: > Hi, > > htbridge (https://www.immuniweb.com/websec/) no longer detects WAF on one of > my > web servers configured with OpenBSD-httpd and PF on same machine; > sample of pf.conf configuration as follows. PF isn't a web application firewall (WAF). > Which

Re: Running Windows inside vmm/vmd VM.

On Sat, Nov 23, 2019 at 12:18 AM Jordan Geoghegan wrote: > > However the timekeeping situation for my Linux VMs is bleak. On both > Void and Alpine, no clocks are even detected. In the dmesg it complains > about the TSC clock source being unstable. Ultimately, we're left with > only jiffies as a c

Re: pkg_info -Q bug?

Thanks Stuart, I tried that package and it indeed does what i needed :) But I decided to scratch my itch anyway and dug a bit into the pkg_info code to figure out what was going on and I found the culprit: is the match_locations function in the PackageRepositoryList class that all the matches from

Re: sysupgrade to 6.6 failed at comp66.tgz

>> - maybe sysupgrade needs to be patched to avoid this issue? >> > > Probably not. sysupgrade has assumptions baked in to it which have > evidently been rendered invalid either by another tool or by the > person using them. That tool is where the patch most likely ought > to be directed. > >

Re: Problems with route installation to fib from OSPF

Hi Joao, just a short follow up: I can reproduce the issue with OpenBSD 6.6 and -current (from today). I could verify that it is related to the additional route with different prio. As a workaround for your prod environment you could filter this host route in bgpd. I'll look into finding a fix f

Re: sysupgrade to 6.6 failed at comp66.tgz

On 2019-11-23 13:45, Rachel Roch wrote: - maybe sysupgrade needs to be patched to avoid this issue? Probably not. sysupgrade has assumptions baked in to it which have evidently been rendered invalid either by another tool or by the person using them. That tool is where the patch most likely

Re: sysupgrade to 6.6 failed at comp66.tgz

> This topic has been beat to death. deraadt@ and other have made it clear that > if you do not install all the sets, you are running an unsupported > configuration. It has been stated that if people keep bitching, they're just > going to merge the release sets into one set. > > I like the fa

Re: sysupgrade to 6.6 failed at comp66.tgz

This topic has been beat to death. deraadt@ and other have made it clear that if you do not install all the sets, you are running an unsupported configuration. It has been stated that if people keep bitching, they're just going to merge the release sets into one set. I like the fact that

Re: sysupgrade to 6.6 failed at comp66.tgz

On 2019-11-23 14:20, Rachel Roch wrote: This topic has been beat to death. deraadt@ and other have made it clear that if you do not install all the sets, you are running an unsupported configuration. It has been stated that if people keep bitching, they're just going to merge the release s

Re: sysupgrade to 6.6 failed at comp66.tgz

> You can't seriously be calling "-x* -game*" an unsupported configuration ?  > Seems to me > like a sensible thing to do on any box that's going to be headless for its > entire life > and only ever accessed via SSH (or text console at a push). Lines 159-160 of /usr/sbin/sysupgrade read as fol

Re: sysupgrade to 6.6 failed at comp66.tgz

On 24/11/2019 09:20, Rachel Roch wrote: You can't seriously be calling "-x* -game*" an unsupported configuration ?  Seems to me like a sensible thing to do on any box that's going to be headless for its entire life and only ever accessed via SSH (or text console at a push). I agree in princip

how to configure directory in which X server logfile is written?

In a fresh install of 6.6/amd64, if I login on a console as a non-root user and start X via 'startx', the X server tries to write log information in the file $HOME/.local/share/xorg/Xorg.0.log I have two questions: 1. Is there any way to change the directory $HOME/.local/share/xorg/ in w

Re: T430 power draw unexpectedly high

In , Dave Trudgian writes [[6.6 or a recent snapshot, Thinkpad T430]] > Under OpenBSD with the system sitting idle at a GUI, WiFi active, 50% > brightness I see ~15W power draw from the battery. This is with `apmd > -A` and the output of `ap