Like, because OpenBSD is for, like, REBELS, mn! Which is like,
totally gnarly dude!
On Thu, 31 Mar 2016 10:58:00 +0200
"Max Power" wrote:
> Hi guys!
> Why the release 5.8 and 5.9 did not comply with the canonical date
> of the 1th November and of the 1th May?
>
> Thanks in advance for your
I have more up to date versions of these patches around here.
The problem with them is that fundamentally, the WAPBL implementation
as it is assumes that it may infinitely steal
buffers from the buffer cache and hold onto them indefinitely - and it
assumes it can always get buffers from it. While
Good morning everyone,
I am wondering is there a way to allow either via /etc/ipsec.conf or
/etc/isakmpd/isakmpd.policy to configure a road warrior type of IPsec VPN
access to my router that accomodates multiple types of IPsec clients that
regrettably have limitations in the auth/enc/DH groups they
Apologies if this was already sent, I am having difficulty with my email
lately and this didn't look like it sent earlier.
Good morning everyone,
I am wondering is there a way to allow either via /etc/ipsec.conf or
/etc/isakmpd/isakmpd.policy to configure a road warrior type of IPsec VPN
access to
I see the writes are not being done to disk in case of a simple cvs update,
and the machine locks up for a solid couple of minutes afterwards also.
This happens in a dual CPU config with plenty of free memory, even with
stefan, mpi and kettenis recent diffs. For a curious kernel reader, where
could
Steve Litt wrote:
> I was a DEC PDP/11 TSX over RT-11 guy back then, but as I remember, a
> terminal was a television that printed letters and numbers plus a
> keyboard on which you could type.
I have to disagree a little bit in that actual TVs were too low-rez for
good 80-column text, which has
I would hazard a guess that if you are running a random diff, the
problem is with the diff you are running - not those other things.
On Fri, Apr 1, 2016 at 9:30 AM, Amit Kulkarni wrote:
> I see the writes are not being done to disk in case of a simple cvs update,
> and the machine locks up for a
Hello All,
Unless I have made a significant mistake in interpreting the diagnostic steps,
if an OpenBSD host/server has multiple interfaces that are connected to the
same subnet, it is not guaranteed that inbound traffic to one of those
interfaces is replied to from the same interface on whic
Nope, my cvs tree is clean. i only applied those diffs since they are small.
On Fri, Apr 1, 2016 at 10:56 AM, Bob Beck wrote:
> I would hazard a guess that if you are running a random diff, the
> problem is with the diff you are running - not those other things.
>
> On Fri, Apr 1, 2016 at 9:30 A
Hi,
Now that sudo is out of base, I am wondering -- do I need to add it again,
or does doas.conf allow for specifying commands with arguments?
Obviously not like this (doas doesn't like that), but akin to:
permit nopass support as root cmd /usr/sbin/rcctl restart ntpd
I don't want the
see doas.conf(5):
args ... Arguments to command. If specified, the command arguments
provided by the user need to match for the command to be
successful. Specifying args alone means that command should
be run without any arguments.
Y
On Fri, Apr 1, 2016 at 2:33 PM, Tor Houghton wrote:
> Now that sudo is out of base, I am wondering -- do I need to add it again,
> or does doas.conf allow for specifying commands with arguments?
>
> Obviously not like this (doas doesn't like that), but akin to:
>
> permit nopass support as
On Fri, Apr 01, 2016 at 02:47:42PM -0700, Philip Guenther wrote:
[snip]
> Sooo close. To quote doas.conf(5):
>
[snip]
> 'args' is *literal* there, so the correct config line would be
> permit nopass support as root cmd /usr/sbin/rcctl args restart ntpd
>
Hahaha, holy fballs! *donk* (I
Hi,
Just upgraded my laptop/netbook to 2016-MAR-30 amd64 snapshot.
I build a few ports, things seemed fine. Made it sleep by shutting the
lid. Trying to wake it up by opening lid, pressing a key (e.g., space-bar)
as it used to work previously by waking up the machine. However,
with this snapshot,
Machine is a Thinkpad x230. First crash after an update.
--
dmesg from bsd.rd:
OpenBSD 5.9-current (GENERIC) #1849: Thu Mar 31 14:46:38 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 16845570048 (16065MB)
avail mem
On Fri, Apr 1, 2016 at 9:24 PM, Luke Tidd wrote:
> Machine is a Thinkpad x230. First crash after an update.
...
> Fri Apr 1 22:06:05 EDT 2016
> uvm_fault(0xff041c9df100, 0x0, 0, 1) -> e
> kernel: page fault trap, code=0
> Stopped at spec_open_clone+0x80: movzbl 0 (%rdi),%edx
> ddb{0}>
On Sat, Apr 02, 2016 at 12:24:13AM -0400, Luke Tidd wrote:
> Machine is a Thinkpad x230. First crash after an update.
Thanks for the report. Pleasae report bugs to the bugs@ mailing list
because not everybody reads misc@. The change that led to this has been
reverted:
https://marc.info/?l=openbsd
The change responsible for that has already been reverted
http://marc.info/?l=openbsd-cvs&m=145951161601747&w=2
Snapshots dated after that time should be fine.
On Sat, Apr 02, 2016 at 12:24:13AM -0400, Luke Tidd wrote:
> Machine is a Thinkpad x230. First crash after an update.
>
> --
My sndio configuration is default, OBSD 5.9.
When I run a media file in e.g. mpv, and pause it without closing, and
try to listen to smth in chrome _as another user_, there is no sound:
[12530:2084997376:0402/012418:ERROR:sndio_output.cc(65)] Couldn't open audio
device.
Reverse is true, if I lis
19 matches
Mail list logo
