Thanks for your response.
# dmesg
OpenBSD 6.6-stable (VPN) #5: Fri Sep 4 18:52:23 CEST 2020
root@VPN:/usr/src/sys/arch/amd64/compile/VPN
real mem = 34297917440 (32709MB)
avail mem = 33245429760 (31705MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS
Suzuki-sama
otsukaresamadesu
(sorry i could type kana, my macppc is not setup good enough)
First of all, I am very thankful that I (we) could use your server
for CVS reposysnc. It is great service to the community.
Personally, I was not inconvenienced so please don't apologize.
Thank you very
On Wed, Oct 14, 2020 at 8:24 PM wrote:
>
> A number of people are working on integrating OpenBSD into Qubes.
>
> In particular, OpenBSD's hardening and mitigations are potentially very
> useful in talking to the NIC: Xen vulnerabilities have been repeatedly
> found that would allow a guest with PC
Hi Misc,
I'm looking forward to OpenBSD 6.8 release.
On OpenBSD 6.8 page, `Released Oct XXX` is writing..
https://www.openbsd.org/68.html
When will it be released?
Sent with [ProtonMail](https://protonmail.com) Secure Email.
Hi,
I'd like to report a problem with resuming from hibernation on Thinkpad X13 AMD.
BTW, everything else seems to work just fine :)
System version: OpenBSD 6.8 GENERIC.MP#115 amd64
Relevant logs from /var/log/messages:
Oct 16 08:57:29 orion /bsd: drm0 at amdgpu0
Oct 16 08:57:29 orion /bsd: am
{Free,Net}BSD have wait6(2), which is even more general than wait4(2),
and allows one to implement POSIX-mandated waitid(2). See e.g.
https://man.netbsd.org/wait.2 .
Is the reason this (or something substantially similar) is missing from
OpenBSD that we don't want it, or just that nobody has d
On Fri, Oct 16, 2020 at 01:52:14PM +, Valdrin Muja wrote:
> On OpenBSD 6.8 page, `Released Oct XXX` is writing..
> When will it be released?
Octobris 0x1e scilicet!
(Just kidding. No one knows for sure. It just arrives in due time when ready.)
Erling
Hello at all,
my httpd.conf
-
prefork 10
logdir "/var/log"
types {
include "/usr/share/misc/mime.types"
}
server "host1.example.com" {
listen on * tls port 443
no log
root "/htdocs/host1"
tls {
On Wed, 14 Oct 2020 at 14:06, Jan Betlach wrote:
>
>
> I am about to install -current on my new T14s with Ryzen 4750u as well.
>
> I have browsed r/openbsd, there are two recent posts related to this. I have
> also chatted on Freenode / #openbsd as there are couple of guys running
> -current on
Hi Ashton,
I have the T15 and it has more or less the same hardware and it seems
to work good..
Getting OpenBSD and WIndows 10 to play nice and share the same drive
is not as easy as I would like
Both OS are happy until the other OS is there :) ...
I have the Nvida hybrid :( GPU (because of a 4 K s
I've just installed -current on my Thinkpad T14s, and I have a weird
problem with getting sound to work properly.
It seems that sound does work, but only through the headphone jack.
I've made sure everything is unmuted in mixerctl, but nonetheless
there's no output at all from the built in speaker
On Fri, Oct 16, 2020 at 11:35:40AM +0200, Anders Andersson wrote:
How could any hardening in OpenBSD protect from someone owning the
hardware? Or do you mean that an OpenBSD guest would run with
exclusive access to the NIC and then every other guest is routed
through that guest?
Yes, exactly. T
@stuart Thank for the suggestion - unfortunately after following the steps
in that link the same error occurred (entry point at: 0x1001000); I
reverted to the obsd kernel (i.e., at boot time, “b obsd”), it’s booting
and the system seems to be working OK, but without dmesg - when I try to
run dmesg,
13 matches
Mail list logo