nSSL support on OpenBSD -current
>
> No matter what I try I keep coming back to errors like:
>
> cargo:libressl_version_number=309f
>
> --- stderr
> thread 'main' panicked at
>
> /home/lobo/.cargo/registry/src/index.crates.io-6f17d22bba15001f
On 2024-07-10, Rob Schmersel wrote:
> Hi,
>
> Looking for advice on how one can build rust programs that require
> openSSL support on OpenBSD -current
>
> No matter what I try I keep coming back to errors like:
>
> cargo:libressl_version_number=309f
>
>
Hi,
Looking for advice on how one can build rust programs that require
openSSL support on OpenBSD -current
No matter what I try I keep coming back to errors like:
cargo:libressl_version_number=309f
--- stderr
thread 'main' panicked at
/home/lobo/.cargo/registry/src/index.crates.io
package with the wacky description is `xz`, I'm more concerned
> > than I would be otherwise.
>
> The same could have happened to any package, there's nothing special
> about xz there.
>
> > I can see in `/var/log/messages` the snapshot update occurred without
t 07:17:35PM +0700, hahahahacker2009 wrote:
> > > > I'm on -current #168 (Thu Jul 4 18:00:50 MDT 2024) and I
> > > > cannot suspend (sleep) my computer using zzz. When I run zzz,
> > > > the screen enter power save mode, the machine seems to be
> > > > sleeping:
Vào Th 6, 5 thg 7, 2024 vào lúc 21:27 hahahahacker2009
đã viết:
>
> Vào Th 6, 5 thg 7, 2024 vào lúc 21:18 Mike Larkin
> đã viết:
> >
> > On Fri, Jul 05, 2024 at 07:17:35PM +0700, hahahahacker2009 wrote:
> > > I'm on -current #168 (Thu Jul 4 18:00:50 MDT 20
Vào Th 6, 5 thg 7, 2024 vào lúc 21:18 Mike Larkin
đã viết:
>
> On Fri, Jul 05, 2024 at 07:17:35PM +0700, hahahahacker2009 wrote:
> > I'm on -current #168 (Thu Jul 4 18:00:50 MDT 2024) and I
> > cannot suspend (sleep) my computer using zzz. When I run zzz,
> > the scre
th the wacky description is `xz`, I'm more concerned
> > than I would be otherwise.
>
> The same could have happened to any package, there's nothing special
> about xz there.
>
> > I can see in `/var/log/messages` the snapshot update occurred without
> > issue. Logs after
, there's nothing special
about xz there.
> I can see in `/var/log/messages` the snapshot update occurred without
> issue. Logs after the physical reboot show no core dump and only have
> complaints about filesystems not being properly unmounted - expected when
> the plug is pulled.
On Fri, Jul 05, 2024 at 07:17:35PM +0700, hahahahacker2009 wrote:
> I'm on -current #168 (Thu Jul 4 18:00:50 MDT 2024) and I
> cannot suspend (sleep) my computer using zzz. When I run zzz,
> the screen enter power save mode, the machine seems to be
> sleeping: the lights on the power
and share to help get to the bottom of
this? The impacted computer has been running current and humming along
happily in a network closet for over a year.
Respectfully,
Ron
I'm on -current #168 (Thu Jul 4 18:00:50 MDT 2024) and I
cannot suspend (sleep) my computer using zzz. When I run zzz,
the screen enter power save mode, the machine seems to be
sleeping: the lights on the power button goes blinking for 2s,
and then the machine wake up.
The machine is Dell
On Tue, Apr 23, 2024 at 04:32:12PM -0300, Thanos Tsouanas wrote:
>
> So, the good news is that it seems to be a hardware problem:
> I installed 7.4 on a usb stick just to test it and it did
> work, but when I booted back to the same 7.5 that it didn't,
> it was recognized properly this time, to
On Tue, Apr 23, 2024 at 4:23 AM Alexandre Ratchov wrote:
> > > On Mon, Apr 22, 2024 at 01:14:43PM -0300, Thanos Tsouanas wrote:
> > > > [...]
> > > > uaudio0: class v1, full-speed, sync, channels: 0 play, 0 rec, 3 ctls
> > >
> > > 0 channels seems wrong. So, you confirm that this device used to
On Mon, Apr 22, 2024 at 01:14:43PM -0300, Thanos Tsouanas wrote:
> Hello,
>
> I have just sysupgraded from 7.4 to 7.5 on my thinkpad X1C9
> in which I was using an external audio interface (OL DAC by
> JDS Labs), but I cannot get it to work anymore.
>
> Using sndioctl to change server.device
me problem under the latest current snapshot.
Also, trying a different USB audio interface everything works
fine (Allen & Heath ZED-14).
Any clues what may cause this or how to fix?
Cheers,
--
Thanos Tsouanas
http://www.tsouanas.org/
0x0b71b7b501d1 in _GLOBAL__sub_I_DIBuilder.cpp ()
---Type to continue, or q to quit---
from /usr/local/llvm16/lib/../lib/libLLVM-16.so
#13 0x0b7108be0989 in ?? () from /usr/libexec/ld.so
#14 0x0005 in ?? ()
#15 0x592ba000 in ?? ()
#16 0x in ?? ()
Current l
On 2024-01-26, Kirill Miazine wrote:
> here's how I can reproduce it here -- just by opening
> https://domene.shop/login page and waiting some seconds:
>
> $ firefox https://domene.shop/login
> Exiting due to channel error.
> Exiting due to channel error.
> Exiting due to channel error.
>
Louis Brauer(lo...@emacs.ch) on 2024.01.28 20:54:17 +:
> I've just installed 7.4-current on an ARM64 machine and tried to pkg_add the
> "htop" package. It fails and this is the output of pkg_add:
>
> # pkg_add htop
> quirks-7.0:updatedb-0p0: ok
> quirks-7.0 si
I've just installed 7.4-current on an ARM64 machine and tried to pkg_add the
"htop" package. It fails and this is the output of pkg_add:
# pkg_add htop
quirks-7.0:updatedb-0p0: ok
quirks-7.0 signed on 2024-01-21T11:57:22Z
quirks-7.0: ok
htop-3.2.2:bzip2-1.0.8p0: ok
htop-3.2.2:pcre2-1
El Fri, 26 Jan 2024 16:23:22 +0100
Kirill Miazine escribió:
> Most recent package on amd64 snapshot from yesterday:
>
> OpenBSD 7.4-current (GENERIC.MP) #1625: Thu Jan 25 09:16:39 MST 2024
>
> gdb says
>
> [...]
> #0 shmget () at /tmp/-:2
> 2 /tmp/-
has additional
error line:
PCRE2 library was built without JIT support
maybe Xvnc -- or PCRE -- are somehow contributing here
• Kirill Miazine [2024-01-26 16:23]:
Most recent package on amd64 snapshot from yesterday:
OpenBSD 7.4-current (GENERIC.MP) #1625: Thu Jan 25 09:16:39 MST 2024
gdb
> Most recent package on amd64 snapshot from yesterday:
>
> OpenBSD 7.4-current (GENERIC.MP) #1625: Thu Jan 25 09:16:39 MST 2024
>
> gdb says
> [...]
> #0 shmget () at /tmp/-:2
> 2 /tmp/-: No such file or directory.
> in /tmp/-
Not sure is that only come from to fire
Most recent package on amd64 snapshot from yesterday:
OpenBSD 7.4-current (GENERIC.MP) #1625: Thu Jan 25 09:16:39 MST 2024
gdb says
[...]
#0 shmget () at /tmp/-:2
2 /tmp/-: No such file or directory.
in /tmp/-
On 2024-01-01, Ax0n wrote:
> On Fri, Dec 29, 2023 at 7:33 PM Stuart Henderson
> wrote:
>
>> Pity, without the deletes a transcript of a run of pkg_add -u -v
>> might have shown why the packages didn't get updated. They should have,
>> and in most cases they do.
>>
>
> Here's the pkg_add -uiv
On Fri, Dec 29, 2023 at 7:33 PM Stuart Henderson
wrote:
> Pity, without the deletes a transcript of a run of pkg_add -u -v
> might have shown why the packages didn't get updated. They should have,
> and in most cases they do.
>
Here's the pkg_add -uiv output that I saved while removing
On 2023-12-29, Ax0n wrote:
> On Fri, Dec 29, 2023, 11:21 Theo de Raadt wrote:
>
>> Then your machine is not -current, not by a long shot.
>>
>> We moved to libc.so.98.0 on Dec 12.
>>
>> At least two rounds of new packages have shown up since then.
>>
>
On Fri, Dec 29, 2023, 11:21 Theo de Raadt wrote:
> Then your machine is not -current, not by a long shot.
>
> We moved to libc.so.98.0 on Dec 12.
>
> At least two rounds of new packages have shown up since then.
>
> I do believe there are circumstances where pkg_add fail
Ax0n wrote:
> And yes, quite a lot of stuff referencing libc.so.97.1 in /usr/local - 223
> files in bin, 361 in lib, 0 in sbin.
Then your machine is not -current, not by a long shot.
We moved to libc.so.98.0 on Dec 12.
At least two rounds of new packages have shown up since then.
reboot
/etc/installurl is http://mirrors.sonic.net/pub/OpenBSD
And yes, quite a lot of stuff referencing libc.so.97.1 in /usr/local - 223
files in bin, 361 in lib, 0 in sbin.
I've been running -current and just rolling snapshots on this machine since
March 2021, somewhere between 6.8 and 6.9
Stuart Henderson wrote:
> On 2023-12-27, Ax0n wrote:
> > I had been running #1471 since December 5th without issue, and this week
> > upgraded to the latest snapshot (#1567) after which some apps such as
> > Firefox won't run. They display "msyscall a8000 error" followed by a
> > core dump.
On 2023-12-27, Ax0n wrote:
> I had been running #1471 since December 5th without issue, and this week
> upgraded to the latest snapshot (#1567) after which some apps such as
> Firefox won't run. They display "msyscall a8000 error" followed by a
> core dump. dmesg(1) shows a bogus syscall. I did
b...@fea.st wrote:
> On Thu, Dec 28, 2023, at 00:41, Ax0n wrote:
> > I had been running #1471 since December 5th without issue, and this week
> > upgraded to the latest snapshot (#1567) after which some apps such as
> > Firefox won't run. They display "msyscall a8000 error" followed by a
> >
On Thu, Dec 28, 2023, at 00:41, Ax0n wrote:
> I had been running #1471 since December 5th without issue, and this week
> upgraded to the latest snapshot (#1567) after which some apps such as
> Firefox won't run. They display "msyscall a8000 error" followed by a
> core dump. dmesg(1) shows a bogus
sysmerged and updated packages.I waited until the next snapshot hit
mirrors, and verified that this issue persists with build #1572 and fresh
packages as well. Lenovo X1 Carbon Gen 8. dmesg in body. I can put core
dumps somewhere if it helps.
OpenBSD 7.4-current (GENERIC.MP) #1572: Wed Dec 27 03
This is not new.
>From time to time, manual crossover build steps occur.
We don't build them into the tree, because that turn into future burden.
Eric Grosse wrote:
> When I've built -current on several machines recently, the procedure dies at
> ===> share/termtypes
> /us
When I've built -current on several machines recently, the procedure dies at
===> share/termtypes
/usr/bin/tic -C -x /usr/src/share/termtypes/termtypes.master > termcap
/usr/bin/tic -x -o terminfo /usr/src/share/termtypes/termtypes.master
"/usr/src/share/termtypes/termtypes.ma
hi,
On Sun, Nov 26, 2023 at 05:28:09PM +0100, quen...@schibler.fr wrote:
> Hello !
>
> I upgraded to current using sysupgrade -s so I could get the latest wayland
> related packages.
> I looked on openports and found that a sway port exists
> https://openports.pl/path/wayl
Hello !
I upgraded to current using sysupgrade -s so I could get the latest wayland
related packages.
I looked on openports and found that a sway port exists
https://openports.pl/path/wayland/sway.
When I pkg_info -Q sway, the package is not found. Does that mean that on
snapshots a port
Following up on the above, on current with the most recent version of all
packages, the initial attempt to start iridium core dumps with the
following:
```
[rdahlgren@builder :: ~] $ iridium
[59856:-1030190016:1120/113635.371153:ERROR:bus.cc(407)] Failed to connect
to the bus: Failed to connect
The symptoms of the freeze are similar to those described by i915kms
> users, but the C400 laptop (1.2GH Pentium-M, 768M RAM) has the i830M
> built-in graphics.
>
> This freeze also happens with NetBSD, FreeBSD, and several Linuxes.
> It works, however, with OpenBSD 4.8 & 4.9.
>
&
lity of current distros makes me think it is an X-windows issue.
The i830M is mentioned in the following:
The Intel 8xx and 9xx families of integrated graphics chipsets have a unified
memory architecture meaning that system memory is used as video RAM. For the
i810 and i815 family of chipsets, opera
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2023 OpenBSD. All rights reserved. https://www.OpenBSD.org
OpenBSD 7.4-current (GENERIC) #1353: Fri Oct 20 09:50:25 MDT 2023
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 2130558976
You need new packages following the curses update.
i386 are ready (faster build than usual due to a few broken
ports), amd64 should be soon.
On 2023-10-19, Mikhail wrote:
>
> kern.version=OpenBSD 7.4-current (GENERIC.MP) #1413: Wed Oct 18 22:19:27 MDT
> 2023
> dera...@amd64.open
kern.version=OpenBSD 7.4-current (GENERIC.MP) #1413: Wed Oct 18 22:19:27 MDT
2023
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
I have
set -g default-terminal screen-256color
in my ~/.tmux.conf since yesterday vim doesn't start properly until I
set TERM to 'xterm
Rudolf Leitgeb wrote:
> On Fri, 2023-10-06 at 11:06 -0600, Theo de Raadt wrote:
>
> > Other operating systems do not have a vast number of people using
> > daily snapshots in the way our users do, so it is only our users who
> > have this experience.
>
> Your expectation is, that people using
On Fri, 2023-10-06 at 11:06 -0600, Theo de Raadt wrote:
> Other operating systems do not have a vast number of people using
> daily snapshots in the way our users do, so it is only our users who
> have this experience.
Your expectation is, that people using snap shots, because they are
part of
Marc Espie wrote:
> Specifically, OpenBSD decides whether it's running "bleeding edge" current
> (snapshot) or a release/stable based on what the kernel says.
OpenBSD does not decide. It has labels to delineate transitions in the
process. Maybe we should go versionless?
Marc Espie wrote:
> On Thu, Oct 05, 2023 at 12:45:56PM -0400, Ronald Dahlgren wrote:
> > Hello friends,
> >
> > I’ve been running -current for several months now. Recently I started using
> > “-D snap” when updating packages with pkg_add.
> >
> > I
On Thu, Oct 05, 2023 at 12:45:56PM -0400, Ronald Dahlgren wrote:
> Hello friends,
>
> I’ve been running -current for several months now. Recently I started using
> “-D snap” when updating packages with pkg_add.
>
> I ask the list to help me understand what, if anything, I ne
On 2023-10-05, Ingo Schwarze wrote:
> The command "sysctl -n kern.version" tells you what a machine
> is currently running:
>
> OpenBSD X.Y-beta = ongoing development *before* X.Y
> OpenBSD X.Y with no suffix = release
Either release, or a pre-release snapshot - close to release these
; just the same that always applies when running -current.
Can you clarify what you mean by that ?
One of the reasons I moved to snapshots is that a release is close,
and another is that 7.3-STABLE has not seen a package update for
chromium in quite a while.
I believe it is still at v111. There's been
Hi Ronald,
Ronald Dahlgren wrote on Thu, Oct 05, 2023 at 12:45:56PM -0400:
> I’ve been running -current for several months now. Recently I started
> using “-D snap” when updating packages with pkg_add.
If you install a snapshot right now, what you actually get is
extremely close t
Hello friends,
I’ve been running -current for several months now. Recently I started using
“-D snap” when updating packages with pkg_add.
I ask the list to help me understand what, if anything, I need to do with
my machines that run snapshots when 7.4 is released. Will I need to perform
seemed to correspond to my sysupgrade also no longer working
> > without passing in the "-s" flag. Is there anything I need to do locally
> > to fix this? This is my first time running -current, so there might be
> > some manual steps I'm missing. Thanks for any help!
>
Try "pkg_add -D snap -u".
Best,
g
Is there anything I need to do locally
> to fix this? This is my first time running -current, so there might be
> some manual steps I'm missing. Thanks for any help!
Add "-D snap" to the pkg_add command
://cdn.openbsd.org/pub/OpenBSD/7.4/packages/amd64/: no such dir
This seemed to correspond to my sysupgrade also no longer working
without passing in the "-s" flag. Is there anything I need to do locally
to fix this? This is my first time running -current, so there might be
some manual steps
On 9/18/23 8:59 PM, Stuart Henderson wrote:
On 2023-09-18, Mark Patruck wrote:
i've already wrote to dlg@, but also want to know if others see
the same behavior or at least inform about it.
pfsync(4) in combination with rdomain(4) doesn't work anymore on
a fresh -current. I see packets
On 2023-09-18, Mark Patruck wrote:
> i've already wrote to dlg@, but also want to know if others see
> the same behavior or at least inform about it.
>
> pfsync(4) in combination with rdomain(4) doesn't work anymore on
> a fresh -current. I see packets on pfsync0, but nothing leave
Hi,
i've already wrote to dlg@, but also want to know if others see
the same behavior or at least inform about it.
pfsync(4) in combination with rdomain(4) doesn't work anymore on
a fresh -current. I see packets on pfsync0, but nothing leaves
the machine, so no states are synchronised
ay
and marked the system as clean. But will try now what you say.
Now dmesg:
OpenBSD 7.3-current (GENERIC.MP) #1231: Sun Jun 11 09:25:51 MDT 2023
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16856313856 (16075MB)
avail mem = 16325795840 (15569MB)
On 6/12/23 07:54, Pau A.S. wrote:
Hi,
...
This has led to a FS corruption which I do not know how to fix, only in one
partition. Upon boot, the system runs fsck on them but the output is that
they are clean with some level of fragmentation.
In any case, /usr/local is corrupted. Is there a way
Hi,
I am running -current on a thinkpad lenovo L13. I am not on my computer now
but I will send dmesg asap.
I have noticed that setting a video or an image to full screen with any
program (vlc, telegram-desktop, mplayer) leads to a system crash. I do not
know how to gather the information or log
On 2023/06/06 15:39, Thomas Huber wrote:
> This issue seems to be related to hardware limits eg. not enough RAM.
> I came across these errors on a 1gig openbsd.amsterdam VM (thanks mischa for
> your great
> service!!)
> But all the mentioned go projects build fine on larger OpenBSD-VMs (eg. 4gig
VM.
Thanks Stuart for helping out again and verifying the build step.
On Thu, 1 Jun 2023 at 16:34, Thomas Huber wrote:
> On Thu, 1 Jun 2023 at 16:28, Stuart Henderson
> wrote:
>
>> On 2023-06-01, Thomas Huber wrote:
>> > Hi @misc,
>> >
>> > I face a
On Thu, 1 Jun 2023 at 16:28, Stuart Henderson
wrote:
> On 2023-06-01, Thomas Huber wrote:
> > Hi @misc,
> >
> > I face a problem with -current when building golang projects.
> > This worked fine on 7.2 and I think it stopped working with 7.3 release.
> > Now I
On 2023-06-01, Thomas Huber wrote:
> Hi @misc,
>
> I face a problem with -current when building golang projects.
> This worked fine on 7.2 and I think it stopped working with 7.3 release.
> Now I try it on -current.
>
> I get the following error:
> "go: error obtainin
On 6/1/23 08:33, Thomas Huber wrote:
> Hi @misc,
>
> I face a problem with -current when building golang projects.
> This worked fine on 7.2 and I think it stopped working with 7.3 release.
> Now I try it on -current.
>
> I get the following error:
> "go: error
Hi @misc,
I face a problem with -current when building golang projects.
This worked fine on 7.2 and I think it stopped working with 7.3 release.
Now I try it on -current.
I get the following error:
"go: error obtaining buildID for go tool compile: signal: bad system call
(core d
If you're developing C or C++ code on OpenBSD, this might be of
interest:
https://marc.info/?l=openbsd-tech=168171382927798=2
-Otto
gt;
>
> On Tue, 7 Mar 2023 at 12:48, Peter Hessler wrote:
>>
>> On 2023 Mar 07 (Tue) at 12:42:33 + (+), Tom Smyth wrote:
>> :Folks upgrading from 7.2 to 7.3 current snapshot
>> :dig seems to crash ...
>> :
>> :
>> :/usr/sbin/dig localhost
On 2023-03-07, Peter Hessler wrote:
> On 2023 Mar 07 (Tue) at 12:42:33 + (+), Tom Smyth wrote:
>:Folks upgrading from 7.2 to 7.3 current snapshot
>:dig seems to crash ...
>:
>:
>:/usr/sbin/dig localhost
>:Bad system call (core dumped)
>:
>
> dig (et al) mov
Mar 07 (Tue) at 12:42:33 + (+), Tom Smyth wrote:
> :Folks upgrading from 7.2 to 7.3 current snapshot
> :dig seems to crash ...
> :
> :
> :/usr/sbin/dig localhost
> :Bad system call (core dumped)
> :
>
> dig (et al) moved from /usr/sbin/ to /usr/bin/ in 6.7, y
On 2023 Mar 07 (Tue) at 12:42:33 + (+), Tom Smyth wrote:
:Folks upgrading from 7.2 to 7.3 current snapshot
:dig seems to crash ...
:
:
:/usr/sbin/dig localhost
:Bad system call (core dumped)
:
dig (et al) moved from /usr/sbin/ to /usr/bin/ in 6.7, you should update
your config to use
Folks upgrading from 7.2 to 7.3 current snapshot
dig seems to crash ...
/usr/sbin/dig localhost
Bad system call (core dumped)
dmesg below
OpenBSD 7.3-beta (GENERIC.MP) #1094: Mon Mar 6 17:59:01 MST 2023
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem
On Mon, Feb 06, 2023 at 10:04:10AM -0800, Logan Ellis wrote:
> Hi Jonathan,
>
> Wanted to provide update: I was able to build a release image from source
> using another amd64 VM and I incorporated your changes. The disk is now
> detected by the installer using `sysctl hw.disknames`. `fdisk -g
]
c:1221381330 unused
—dmesg—
OpenBSD 7.2-current (RAMDISK_CD) #0: Sun Feb 5 12:46:58 PST 2023
noc...@buildbox.lan:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 16987197440 (16200MB)
avail mem = 16468348928 (15705MB)
random: good seed
fo` at
> > the boot prompt lists the nvme. This occurs with both 7.2-current as well
> > as a 7.2 release builds. For boot loaders, I attempted an option-key boot
> > as well as booting from refind. Neither worked. I have also attempted to
> > install the `apple-boot-firmwar
issue. `machine diskinfo` at the
> boot prompt lists the nvme. This occurs with both 7.2-current as well as a
> 7.2 release builds. For boot loaders, I attempted an option-key boot as well
> as booting from refind. Neither worked. I have also attempted to install the
> `apple-boot-firmw
-current as well as a 7.2
release builds. For boot loaders, I attempted an option-key boot as well as
booting from refind. Neither worked. I have also attempted to install the
`apple-boot-firmware` into the install image using the FAQ instructions on
bootstrapping firmware. As a long shot, I also
I tried again, without full disk encryption and it works. System booted
properly to a console login prompt.
On Sun, Nov 27, 2022 at 08:40:57PM +, Mikolaj Kucharski wrote:
> Hi,
>
> I was able to go through installer on today's arm64 snapshot with full
> disk encryption setup. With some
Hi,
I was able to go through installer on today's arm64 snapshot with full
disk encryption setup. With some manual `sh MAKEDEV sd0 sd1` during the
installer I managed to install, but then after first boot passphrase and
boot> prompt I see
booting sr0a:/bsd: 9769...
FACP CSRT DBG2 GTDT IORT APIC
I was trying to install OpenBSD-current from snapshots, UEFI mode boot
and GPT disk - the install went fine, but the boot after installation
remains stuck at efi0 entry listing. I have to use the switch off
button to exit from this.
The install and boot works if I use Legacy mode boot with MBR
Hello,
I did an OpenBSD-current installation from snapshots on a computer I
use to run OpenBSD a few months ago. I used UEFI boot with GPT disk
format since it was working fine in the past. I was able to boot the
installer, the setup completed fine, but the boot process was stuck at
efi0: device
:
OpenBSD 7.2-current (GENERIC.MP) #767: Tue Oct 4 23:38:08 MDT 2022
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 34215931904 (32630MB)
avail mem = 33161555968 (31625MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
On 2022-10-05, Courtney wrote:
> $ ssh -V
> OpenSSH_9.1, LibreSSL 3.6.0
>
> scp has been stalling on my system and hanging up my networking stack.
Do you know when it started?
What snapshot are/were you running?
It is always helpful to include dmesg when reporting a problem.
> I am probably
$ ssh -V
OpenSSH_9.1, LibreSSL 3.6.0
scp has been stalling on my system and hanging up my networking stack.
I am probably doing this wrong, but I have been having to delete, down, up
and sh /etc/netstart to recover networking, or doing a reboot.
It seems to happen with larger files, whether I
On 2022-07-02 08:47, Hrvoje Popovski wrote:
On 2.7.2022. 0:11, Mischa wrote:
Hi All,
Just updated one of my -current test VMs to the snapshot of June 30.
The boot process takes extremely long. As soon as it's booting:
Hi,
update to latest snaphost and console output will be fast again
On 2.7.2022. 0:11, Mischa wrote:
> Hi All,
>
> Just updated one of my -current test VMs to the snapshot of June 30.
> The boot process takes extremely long. As soon as it's booting:
Hi,
update to latest snaphost and console output will be fast again :)
OpenBSD 7.1-current (GENE
Mischa writes:
> Hi All,
>
> Just updated one of my -current test VMs to the snapshot of June 30.
> The boot process takes extremely long. As soon as it's booting:
>
> ###
> Using drive 0, partition 3.
> Loading..
> probing: pc0 com0 mem[638K 3838M 4352M a20=o
Hi All,
Just updated one of my -current test VMs to the snapshot of June 30.
The boot process takes extremely long. As soon as it's booting:
###
Using drive 0, partition 3.
Loading..
probing: pc0 com0 mem[638K 3838M 4352M a20=on]
disk: hd0+
OpenBSD/amd64 BOOT 3.53
\
com0: 115200 baud
On Tue, Jun 7, 2022 at 11:34 AM Zé Loff wrote:
>
> On Tue, Jun 07, 2022 at 04:26:11PM +0300, Barbaros Bilek wrote:
> > Hello Misc,
> >
> > I think there is an issue about PF tables at current.
> > Here my working PF config sample before 7.1-Current.
> > blo
On Tue, Jun 07, 2022 at 04:26:11PM +0300, Barbaros Bilek wrote:
> Hello Misc,
>
> I think there is an issue about PF tables at current.
> Here my working PF config sample before 7.1-Current.
> block log quick inet from
> pfctl -f /etc/pf.conf
> Another software fills
Hello Misc,
I think there is an issue about PF tables at current.
Here my working PF config sample before 7.1-Current.
block log quick inet from
pfctl -f /etc/pf.conf
Another software fills this Malicious table with this command:
# pfctl -t Malicious -T add 1.2.3.4
1 table created
Stuart Henderson wrote:
> On 2022/06/04 15:23, Theo de Raadt wrote:
> > Stuart Henderson wrote:
> >
> > > If you are running -current and have not updated base recently, you
> > > may run inTO "pkg_add: Unknown option: always-update ".
> >
On 2022/06/04 15:23, Theo de Raadt wrote:
> Stuart Henderson wrote:
>
> > If you are running -current and have not updated base recently, you
> > may run inTO "pkg_add: Unknown option: always-update ".
> > To fix it, just update to a newer base
Stuart Henderson wrote:
> If you are running -current and have not updated base recently, you
> may run inTO "pkg_add: Unknown option: always-update ".
> To fix it, just update to a newer base snapshot.
What happened is that a developer made a change to the pkg tools which
If you are running -current and have not updated base recently, you
may run inTO "pkg_add: Unknown option: always-update ".
To fix it, just update to a newer base snapshot.
On Fri, 13 May 2022 at 11:07, Darren Tucker wrote:
> I've had two people ask me about this device in the last few days
> so I thought I'd post a followup describing what I did and found.
> As a reminder, this is an gl.inet GL-MV1000[0] (aka Brume) device.
Current status:
> Using t
1 - 100 of 3829 matches
Mail list logo
