On 2025-07-19, Michael Joy wrote:
> --b1=_2ngZBRzU5QvOmksSDzxuwCkKxfQN9IkwPmPbrzFaCU8
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: quoted-printable
>
> Did a sysupgrade yesterday and since then I can't open ungoogled-chromium o=
as mentioned recentl
Thanks so much Kirill
On Saturday, July 19th, 2025 at 7:47 PM, Kirill A. Korinsky
wrote:
>
>
> On Sat, 19 Jul 2025 20:29:19 +0200,
> Michael Joy michaeljo...@protonmail.com wrote:
>
> > Did a sysupgrade yesterday and since then I can't open ungoogled-chromium
&g
On Sat, 19 Jul 2025 20:29:19 +0200,
Michael Joy wrote:
>
> Did a sysupgrade yesterday and since then I can't open ungoogled-chromium
> or kitty. I'm not at all worried about kitty but I use
> ungoogled-chromium as my primary browser. I've attached dmesg.boot and
Did a sysupgrade yesterday and since then I can't open ungoogled-chromium or
kitty. I'm not at all worried about kitty but I use ungoogled-chromium as my
primary browser. I've attached dmesg.boot and the terminal output while trying
to open ungoogled-chromium. I've done anot
On 2025-05-12 09:12 +02, Janne Johansson wrote:
>> > sysupgrade -b ?
>>
>> Oh. I think I've misunderand the semantics of sysupgrade and
>> /bsd.upgrade. I had thought that the upgrade would (like an interactive
>> install) do a newfs on each partition wit
> > sysupgrade -b ?
>
> Oh. I think I've misunderand the semantics of sysupgrade and
> /bsd.upgrade. I had thought that the upgrade would (like an interactive
> install) do a newfs on each partition with a mount point specified
> But now that I think of it, it seems
In <https://marc.info/?l=openbsd-misc&m=174702671731147&w=1>, I wrote:
> I have an OpenBSD system for which /home isn't in /etc/fstab.
[[...]]
> Today (trying to upgrade from 7.6-stable/amd64 to 7.7/amd64) I discovered
> that this breaks sysupgrade (and autoinstall
I ran into the same problem (/home and /var/www on separate encrypted
partitions, I avoided full-disk encryption in order to be able to
distant reboot).
For this time, I just unmounted /home before sysupgrade(8) and hoped
I'd remember to do the same next time.
On 2025-05-12 07:09, Jon
- Forwarded message from Jan Stary -
Date: Mon, 12 May 2025 08:36:54 +0200
From: Jan Stary
To: Jonathan Thornburg
Subject: Re: interactive-shell escapes in sysupgrade/autoinstall?
If you are willing to manualy intervene during a sysupgrade,
you can just as well boot into bsd.rd and do
> I have an OpenBSD system for which /home isn't in /etc/fstab. Rather,
> Today (trying to upgrade from 7.6-stable/amd64 to 7.7/amd64) I discovered
> that this breaks sysupgrade (and autoinstall): sysupgrade downloads the
> install sets to /home/_sysupgrade/ just fine (since a
ng to upgrade from 7.6-stable/amd64 to 7.7/amd64) I discovered
that this breaks sysupgrade (and autoinstall): sysupgrade downloads the
install sets to /home/_sysupgrade/ just fine (since at the time I type
'sysupgrade' I've already done a normal multiuser boot, including assembling
and
On Fri, May 9, 2025 at 9:56 AM Janne Johansson wrote:
> Same goes for if you
> must place /home/_sysupgrade somewhere else for space reasons, make
> sure the softlink is relative and it will keep on working during
> upgrades also.
Thanks for this -- I had been making it work with &#
Hello Ruda,
rsyk...@disroot.org wrote on Fri, May 09, 2025 at 04:10:46PM +0200:
> On 2025-05-09 12:53, Janne Johansson wrote:
>> Ruda wrote:
I had that with systems where /var/www is a symlink into
another (small) slice/partition like "/".
>>> Thanks. I had /var/www symlinked to /home/
On 2025-05-09 12:53, Janne Johansson wrote:
> I had that with systems where /var/www is a symlink into
> another (small) slice/partition like "/".
Thanks. I had /var/www symlinked to /home/www, and that
was, for some reason, enough to cause the trouble. I removed
the symlink and the upgrade w
> > I had that with systems where /var/www is a symlink into
> > another (small) slice/partition like "/".
>
> Thanks. I had /var/www symlinked to /home/www, and that
> was, for some reason, enough to cause the trouble. I removed
> the symlink and the upgrade went fine. What is not understood,
> ho
Am 09.05.2025 12:17 schrieb rsyk...@disroot.org:
What is not understood,
however, is the fact that the symlink went *not* to a small partition;
my /home was
/dev/sd0k 295G227G 53.8G81%/home
Might happen that /home is not mounted in that moment?
Try to unmount it and see if/w
On 2025-05-09 11:02, Philipp Buehler wrote:
Am 09.05.2025 10:29 schrieb rsyk...@disroot.org:
The complain is about / , which, upon reboot, seems to be rd0a,
something I do not really understand what that is.
Can anybody tell me what is probably going wrong?
I had that with systems where /
Am 09.05.2025 10:29 schrieb rsyk...@disroot.org:
The complain is about / , which, upon reboot, seems to be rd0a,
something I do not really understand what that is.
Can anybody tell me what is probably going wrong?
I had that with systems where /var/www is a symlink into
another (small) slice/
Dear list,
upon running sysupgrade, after the reboot I it seems
as if I run out of space on /
/: write failed, file system is full
tar: Failed write to file ./var/www/bin/bgpctl: No space left on the
device
but before the attempt I see:
odin:~$ df -h
Filesystem SizeUsed Avail
rocess of patching and installing a newly
> > compiled kernel after running `sysupgrade`, so as to avoid having
> > to wait 4+ hours each time I install a new version.
>
> You lost me: what exactly is it that takes 4 hours?
>
`sysupgrade`, so as to avoid having to
wait 4+ hours each time I install a new version.
I can’t figure out how to do it. Here’s what I tried:
- fetch latest sources, apply my changes
- `# make obj; make config; make`for `
/sys/arch/amd64/compile/{RAMDISK,GENERIC,GENERIC.MP}
- `install` the new bsd.rd
On Tue, Jan 14, 2025 at 10:05:08PM GMT, Stuart Henderson wrote:
> On 2025-01-14, Joel Carnat wrote:
>> Hi,
>> I had OpenBSD 7.6, latest syspatch, installed and running properly with
>> WindowMaker, thunar, Firefox ESR. For reasons, I upgraded to the latest
>> sna
On 2025-01-14, Joel Carnat wrote:
> Hi,
>
> I had OpenBSD 7.6, latest syspatch, installed and running properly with
> WindowMaker, thunar, Firefox ESR. For reasons, I upgraded to the latest
> snapshot, using `sysupgrade -s`. Once rebooted, I updated all my
> packages us
Hi,
I had OpenBSD 7.6, latest syspatch, installed and running properly with
WindowMaker, thunar, Firefox ESR. For reasons, I upgraded to the latest
snapshot, using `sysupgrade -s`. Once rebooted, I updated all my
packages using `pkg_add -u -D installed; pkg_delete -a`. Then I rebooted
once again
> Hello
>
> Lenovo ThinkPad 14
>
> I have a 7.4 VMD server with 3 VMs as BU locally at home. No internet
> coming in.
>
> I tried to do sysupgrade from 74 to 75 and it failed, it stop after the
> Daemons line! Showing a grey screen.
>
> Then: with different ssd di
Hello
Lenovo ThinkPad 14
I have a 7.4 VMD server with 3 VMs as BU locally at home. No internet
coming in.
I tried to do sysupgrade from 74 to 75 and it failed, it stop after the
Daemons line! Showing a grey screen.
Then: with different ssd disk, i tried to install 75, having the same
failure
On 19/11/2024 15:07, Peter Wens wrote:
This is fixed in upstream (3.2.2).
Check: https://github.com/OpenVPN/easy-rsa/
commit/7df616ba1ed4add956d0353b68fce9d865f46c82
Thanks. Working now.
Steve
Probably pilot error, again, but...
Since the sysupgrade, I can no longer create or revoke OpenVPN keys.
In both cases I get the following:
./easyrsa revoke old-user
Easy-RSA error:
Unsupported SSL library: 4
EasyRSA Version Information
Version: 3.1.1
Generated: Thu Oct 13 06:37:48 CDT
Hi Steve,
This is fixed in upstream (3.2.2).
Check:
https://github.com/OpenVPN/easy-rsa/commit/7df616ba1ed4add956d0353b68fce9d865f46c82
Best regards,
Peter
On 11/19/24 2:16 PM, Steve Fairhead wrote:
Probably pilot error, again, but...
Since the sysupgrade, I can no longer create or
I took the new sysupgrade for a spin on an old laptop running OpenBSD 6.7
The 6.7 sysupgrade has no idea how to get or test new signing keys. No problem,
the current sysupgrade knows.
So, I grabbed the current sysupgrade script from cvsweb.openbsd.org to my laptop
Then, I ran sysupgrade -s
It
On Fri, 11 Oct 2024 15:40:06 - (UTC), Stuart Henderson wrote:
> On 2024-10-11, Amelia A Lewis wrote:
[snipped: sshd not starting on machine with sysupgrade-overfilled /usr
slice]
>> I'm too verbose. Short version: a) with sshd not working and no console
>> access, is
hi
update problem lookup like a problem with the vxlan interface .
if you have more then one , 7.6 crash to ddb
Holger
On 12.10.24 22:12, Holger Glaess wrote:
hi
sorry wrong versions.
was 7.5 to 7.6
holger
On 12.10.24 21:25, Holger Glaess wrote:
hi
at reboot after sysupgrade i
hi
sorry wrong versions.
was 7.5 to 7.6
holger
On 12.10.24 21:25, Holger Glaess wrote:
hi
at reboot after sysupgrade i got an core
===> Adding the _dhcp6leased group
===> Adding the _dhcp6leased user
panic: rw_enter: inpnotify locking against myself
Stopped at db_enter+0x14:
hi
at reboot after sysupgrade i got an core
===> Adding the _dhcp6leased group
===> Adding the _dhcp6leased user
panic: rw_enter: inpnotify locking against myself
Stopped at db_enter+0x14: popq %rbp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
239340 5005
On 2024-10-11, Amelia A Lewis wrote:
> /dev/sd1a 1005M143M812M15%2160 153742 2% /
> /dev/sd1h 149G2.8G139G 2%1970 9868364 1%
> /home
> /dev/sd1p 181G1.8G170G 2% 72 11959222 1%
> /pub
> /dev/sd1d 3.9G 10.0K
Heyo,
I performed sysupgrade on two locally-available OBSD systems on
Tuesday, which went as smoothly as expected, and then initiated
sysupgrade on a machine in colocation. It came back up (per ping), but
refused ssh connections to allow me to complete the upgrade (pkg_add
-u). Investigation
o me too.
> Will I need to manually boot the next snapshot bsd kernel to fix ?
> In the meantime it still routes and serve wg VPN
>
> On Fri, Oct 4, 2024, 11:31 Stuart Henderson
> wrote:
> On 2024-10-03, Michael Joy wrote:
> > Hey all, just did a sysupgrade -s on current. It
n Fri, Oct 4, 2024, 11:31 Stuart Henderson wrote:
On 2024-10-03, Michael Joy wrote:
> Hey all, just did a sysupgrade -s on current. It all appeared to be fine
> until the second reboot. Since then I'm hung on:
>
> Init: getty repeating too quickly on port /dev/ttyC0, sleepin
On 2024/10/05 09:45, Pierre Peyronnel wrote:
> Happened to me too.
>
> Will I need to manually boot the next snapshot bsd kernel to fix ?
I don't know whether it was a kernel diff or a userland diff that was
the problem. But manually upgrading the machine (kernel+userland) to
the next snapshot (o
Happened to me too.
Will I need to manually boot the next snapshot bsd kernel to fix ?
In the meantime it still routes and serve wg VPN
On Fri, Oct 4, 2024, 11:31 Stuart Henderson
wrote:
> On 2024-10-03, Michael Joy wrote:
> > Hey all, just did a sysupgrade -s on current. It all ap
On 2024-10-03, Michael Joy wrote:
> Hey all, just did a sysupgrade -s on current. It all appeared to be fine
> until the second reboot. Since then I'm hung on:
>
> Init: getty repeating too quickly on port /dev/ttyC0, sleeping
>
> I'll probably go through the cause
Hey all, just did a sysupgrade -s on current. It all appeared to be fine until
the second reboot. Since then I'm hung on:
Init: getty repeating too quickly on port /dev/ttyC0, sleeping
I'll probably go through the cause tomorrow and find a solution. Just trying to
be useful by maki
I've been infrequently following snapshots with a vbox installation and
have been experiencing hangs like this for a year or two now. Everything
works great on my actual hardware.
The VM boots fine after resetting, but the subsequent fsck and performing
the skipped upgrade steps is mildly annoyin
was updated - but didn't see anything change of
significance.
I'm familiar with restoring the ownerships and rights to /dev/ugen0.00
and /dev/usb0 (in my case) after the sysupgrade.
Running "upsdrvctl start" now returns an error, including:
USB communication driver (libusb 1.0)
My last response to Otto seems to have had a lot of noise appended. I
replied via gmail, which seems to have added all sorts of things, as my own
SPF/DMARC rules seem too strict, and seem to stop the mailing list
relaying. Will review.
Humbly,
Steve
ct dir: rm -rf/usr/obj/*
>
> Then try again.
Nuking /usr/obj/* did the trick. Thanks!
I think I'll tweak my process to use a fresh tree checkout after a
sysupgrade (as suggested by Marc Peters - thanks!).
Steve
On Mon, 22 Apr 2024 at 22:09, Steve Fairhead wrote:
> Hi folks,
On Mon, Apr 22, 2024 at 10:09:51PM +0100, Steve Fairhead wrote:
> Hi folks,
>
> (Apologies if this is a dupe. Looks to me like this didn't originally get
> far.)
>
> Pretty sure this is pilot error, so please be gentle.
>
> I sysupgraded 3 machines (all different) to 7.5; no problems. I then
>
tp://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Do you sysupgrade to 7.5 (all OK here), and then you want to build the
kernel and the base using the src for 7.5?
For what purpose do you do that?
--
*
Dios en su cielo, todo bien en la Tierra
Hi folks,
(Apologies if this is a dupe. Looks to me like this didn't originally get
far.)
Pretty sure this is pilot error, so please be gentle.
I sysupgraded 3 machines (all different) to 7.5; no problems. I then
updated installed packages; again no problem.
Then I updated the source trees:
cd
Дана 24/04/08 06:56PM, Nick Holland написа:
> My 100% guess is that you have a machine that's very dependent upon
> ACPI, and the install kernel's ACPI support is very minimal, or
> has a funny UEFI system. Or a funny BIOS. Some machines work better
> as UEFI, some work better running BIOS. A fi
On 4/7/24 10:42, Страхиња Радић wrote:
Дана 24/04/07 12:46PM, Страхиња Радић написа:
Ok. The alternative would be to find a way to make 7.5 efifb work on my laptop.
The version of efifb from 7.4 works (that is how I installed 7.4 in the first
place), unlike 7.5 efifb.
I'd just like to add tha
the 7.4 to 7.5 upgrades I had an initial success then two failures.
Not confidence building since these firewalls are at remote sites.
Not sure where the problem lies, here is what I've experienced:
pcEngines apu2 boards, running sysupgrade - have been running OpenBSD
since abou
g remote (ssh to boards) with no problems.
>
>Doing the 7.4 to 7.5 upgrades I had an initial success then two failures. Not
>confidence building since these firewalls are at remote sites.
>
>Not sure where the problem lies, here is what I've experienced:
>
>pcEngines apu2 boar
problem lies, here is what I've experienced:
pcEngines apu2 boards, running sysupgrade - have been running OpenBSD
since about 6.2 and doing remote (ssh to board) for several releases
w/o any problems
Did successful sysupgrade on one board the evening before 7.5 release
notification using
Дана 24/04/07 12:46PM, Страхиња Радић написа:
> Ok. The alternative would be to find a way to make 7.5 efifb work on my
> laptop.
> The version of efifb from 7.4 works (that is how I installed 7.4 in the first
> place), unlike 7.5 efifb.
I'd just like to add that it efifb might not even be the
Дана 24/04/07 10:32AM, Stuart Henderson написа:
> None of the ramdisk kernels include these large drivers (no difference
> in that respect between 7.4 and 7.5, or any other release).
Ok. The alternative would be to find a way to make 7.5 efifb work on my laptop.
The version of efifb from 7.4 work
On 2024-04-07, Страхиња Радић wrote:
> (manually retyped to avoid large attachments):
thank you!
> 2. The result of entering `boot -c` at the `boot>` prompt with /bsd.upgrade
> having the execute bit set (so 7.5 /bsd.upgrade would boot by default):
>
> OpenBSD 7.5 (RAMDISK_CD) #76: Wed Ma
Дана 24/04/07 11:57AM, Sebastien Marie написа:
> Here, you are comparing GENERIC.MP kernel with RAMDISK_CD kernel.
>
> A RAMDISK_CD kernel is a reduced kernel with only what is necessary to
> install openbsd. radeondrm and amdgpu are NOT part of it, and it is
> expected.
Is there any way for me t
Страхиња Радић writes:
> As a follow-up to my previous post, after rereading [1], I tried to compare
> the
> status of radeondrm, efifb and amdgpu in 7.4 /bsd boot and 7.5 /bsd.upgrade
> boot. I got this (manually retyped to avoid large attachments):
>
> 1. The result of entering `boot -c` at
As a follow-up to my previous post, after rereading [1], I tried to compare the
status of radeondrm, efifb and amdgpu in 7.4 /bsd boot and 7.5 /bsd.upgrade
boot. I got this (manually retyped to avoid large attachments):
1. The result of entering `boot -c` at the `boot>` prompt with /bsd.upgrade
On Thu, Mar 21, 2024 at 11:14 AM Florian Obser wrote:
>
> On 2024-03-21 10:33 +01, Christer Solskogen
> wrote:
> > Nick Holland reported this with a HP T430 Thin Client already in May
> > 2022, and I see the same problem on two of my new firewalls. I was
> > hoping a HDMI dummy plug would work a
ure when or what marks the bsd.upgrade file as -x, but that
> at least that happens.
that's the bootloader (to prevent upgrade loops, the bootloader will
only consider bsd.upgrade that is +x).
> Is there anything I can do to try to help?
>
> As long as a monitor is atta
at happens.
Is there anything I can do to try to help?
As long as a monitor is attached, sysupgrade works just as intended.
--
chs
On Sun, 18 Feb 2024 10:57:27 +0100,
Stuart Henderson wrote:
>
> It's not too bad as long as the person building firmware tgz gets a
> heads-up before the version number is updated.
>
Specially that right now it still can be run as:
env VERSION=74 fw_update -p http://firmware.openbsd.org/firmw
On 2024-02-18, Theo de Raadt wrote:
> Kirill A. Korinsky wrote:
>
>> On Sat, 17 Feb 2024 22:27:52 +0100,
>> Sonic wrote:
>> >
>> > Seems it's looking for a 7.5 directory (-current apparently just moved
>> > to 7.5-beta) instead of the snapshot directory.
>> >
>>
>> And using snapshot directory
Kirill A. Korinsky wrote:
> On Sat, 17 Feb 2024 22:27:52 +0100,
> Sonic wrote:
> >
> > Seems it's looking for a 7.5 directory (-current apparently just moved
> > to 7.5-beta) instead of the snapshot directory.
> >
>
> And using snapshot directory fails because wrong signature:
>
> ~ $ doas
On Sat, 17 Feb 2024 22:27:52 +0100,
Sonic wrote:
>
> Seems it's looking for a 7.5 directory (-current apparently just moved
> to 7.5-beta) instead of the snapshot directory.
>
And using snapshot directory fails because wrong signature:
~ $ doas fw_update -p http://firmware.openbsd.org/firmwar
Today "sysupgrade -s" failed to fetch updated firmware:
=
Verifying sets.
Fetching updated firmware.
fw_update: failed.
Cannot fetch http://firmware.openbsd.org/firmware/7.5//SHA256.sig (404
Not Found)
Upgrading.
=
Seems it's looking for
Mark writes:
> "> That will never happen."
>
> And some serious reason?
/usr/sbin/sysupgrade is 218 lines short _with_ comments and I for
one like it that way.
It's difficult to screw up by using it and easy to figure out what
it did if you do.
> It was a great id
On 2023-11-18 15:57 +01, m...@emailgroups.net wrote:
> On Sat, Nov 18, 2023, at 11:57, Mark wrote:
>> "> That will never happen."
>>
>> And some serious reason?
>>
>> It was a great idea indeed. :/
>
> They don't go out of their way to assist with foot shooting.
Oh, we like foot guns as much as
On Sat, Nov 18, 2023, at 11:57, Mark wrote:
> "> That will never happen."
>
> And some serious reason?
>
> It was a great idea indeed. :/
They don't go out of their way to assist with foot shooting.
The files under /usr take up about 8 GB and I've installed gnome
and what not.
Just get a bigge
"> That will never happen."
And some serious reason?
It was a great idea indeed. :/
Theo de Raadt , 17 Kas 2023 Cum, 18:20 tarihinde şunu
yazdı:
> Odd Martin Baanrud wrote:
>
> > Perhaps sysupgrade should be enhanced, so one could either choose which
> sets shoul
Mihai Popescu :
> Make it Rust or GTK based, but please include the support for http, it
> is more convenient to do it remotely using www.
Do OpenBSD running seriously on Ruby, Python, etc, etc and then we discuss
about www that appears the only think we can still like to run over it,
and sorry f
> I still have gsysupgrade lying around somewhere. It's a gtk app. I never
> made a port for it because I got sidetracked rewriting it to use qt.
> It isn't written in rust? The shame.
Make it Rust or GTK based, but please include the support for http, it
is more convenient to do it remotely usi
Florian Obser wrote:
> On 2023-11-17 16:06 +01, Odd Martin Baanrud wrote:
> > Hello Jan,
> >
> > Thanks for the tip.
> > The upgrade went smoothly.
> > I ran “sysupgrade -n”, deleted the game set and the X sets and rebooted.
> >
> > Perhaps sysup
Odd Martin Baanrud wrote:
> Perhaps sysupgrade should be enhanced, so one could either choose which sets
> should be upgraded, or even beter, the tool could figure out which sets are
> installed, and upgrade just those.
That will never happen.
On 2023-11-17 16:06 +01, Odd Martin Baanrud wrote:
> Hello Jan,
>
> Thanks for the tip.
> The upgrade went smoothly.
> I ran “sysupgrade -n”, deleted the game set and the X sets and rebooted.
>
> Perhaps sysupgrade should be enhanced, so one could either choose
> which set
Hello Jan,
Thanks for the tip.
The upgrade went smoothly.
I ran “sysupgrade -n”, deleted the game set and the X sets and rebooted.
Perhaps sysupgrade should be enhanced, so one could either choose which sets
should be upgraded, or even beter, the tool could figure out which sets are
installed
IF you have a good reason to not let sysupgrade do a full install
(space? on my RPI that's the case), you can simply
sysupgrade -sfn
rm /home/_sysupgrade/x*
reboot
On 11/16/23 20:25, Odd Martin Baanrud wrote:
Hello,
I’m planning to upgrade my router from 7.3 to 7.4 using sysupgrade, but I’ve
one concern.
Some time ago, I upgraded a RPi4 from 7.2 to 7.3, and X got installed, even
though it wasn’t before the upgrade.
I thaught sysupgrade only upgraded the
Hello,
I’m planning to upgrade my router from 7.3 to 7.4 using sysupgrade, but I’ve
one concern.
Some time ago, I upgraded a RPi4 from 7.2 to 7.3, and X got installed, even
though it wasn’t before the upgrade.
I thaught sysupgrade only upgraded the installed sets.
How does it work on 7.3?
On my
On 4/14/23 3:08 AM, Stuart Henderson wrote:
On 2023-04-13, Jeff Ross wrote:
On 4/12/23 12:22 PM, Jeff Ross wrote:
OpenBSD 7.3 (GENERIC.MP) #1125 Sat Mar 25 10:36:29 MDT 2023
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8469549056 (8077MB)
avail mem = 81934622
On 4/14/23 9:14 AM, Rod Person wrote:
On Wed, 12 Apr 2023 12:22:14 -0600
Jeff Ross wrote:
Hi all,
I did a sysupgrade from 7.2 to 7.3 on an HP EliteDesk (amd64). The
upgrade went great but now the computer will not boot.
I also have the same issue and I also have an HP Elite (8300)...
I was
On Wed, 12 Apr 2023 12:22:14 -0600
Jeff Ross wrote:
> Hi all,
>
> I did a sysupgrade from 7.2 to 7.3 on an HP EliteDesk (amd64). The
> upgrade went great but now the computer will not boot.
>
I also have the same issue and I also have an HP Elite (8300)...
I was able to get
On 2023-04-13, Jeff Ross wrote:
> On 4/12/23 12:22 PM, Jeff Ross wrote:
>>
>> OpenBSD 7.3 (GENERIC.MP) #1125 Sat Mar 25 10:36:29 MDT 2023
>> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>> real mem = 8469549056 (8077MB)
>> avail mem = 8193462272 (7813MB)
>> random: good see
On 4/12/23 12:22 PM, Jeff Ross wrote:
Hi all,
I did a sysupgrade from 7.2 to 7.3 on an HP EliteDesk (amd64). The
upgrade went great but now the computer will not boot.
Here's what I get at boot:
(typed from photo--disregard any typos)
[ using 3644008 bytes of bsf ELF symbol
Hi all,
I did a sysupgrade from 7.2 to 7.3 on an HP EliteDesk (amd64). The
upgrade went great but now the computer will not boot.
Here's what I get at boot:
(typed from photo--disregard any typos)
[ using 3644008 bytes of bsf ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991,
On Tue, 21 Mar 2023 17:22:09 +0100, u...@mailo.com wrote:
> Did snapshot sysupgrade
>
> On reboot in tty0:
> syspatch: Error retrieving https://mirror.ihost.md/pub/OpenBSD/7.3/packages/a
> md64/SHA256.sig: 404 not found
>
> Issuing pkg_add -u:
> https://mirror.ihost.md/
Did snapshot sysupgrade
On reboot in tty0:
syspatch: Error retrieving
https://mirror.ihost.md/pub/OpenBSD/7.3/packages/amd64/SHA256.sig: 404 not found
Issuing pkg_add -u:
https://mirror.ihost.md/pub/OpenBSD/7.3/packages/amd64/: no such dir
I see other mirrors
https://cdn.openbsd.org/pub
> On Dec 14, 2022, at 03:03, Bodie wrote:
>> On 14.12.2022 11:34, Why 42? The lists account. wrote:
>> Right you are, that's the one :-/ I used to be a SPARC kinda guy, but
>> those are all gone now.
>
> OT - they are not, but those prices...
>
> https://shop.eol.systems/servers/serve
On 14.12.2022 11:34, Why 42? The lists account. wrote:
On Mon, Dec 12, 2022 at 11:11:24PM -0500, Nick Holland wrote:
On 12/12/22 07:22, Why 42? The lists account. wrote:
>
> Hi All,
>
> Today sysupgrade failed for me, but I'm not sure why? Here's the output:
[ ... ]
T
On Tue, Dec 13, 2022 at 11:12:18AM -, Stuart Henderson wrote:
> On 2022-12-12, Why 42? The lists account. wrote:
> > Today sysupgrade failed for me, but I'm not sure why? Here's the output:
>
> As the various mirrors get updated, this should be coming back to no
On Mon, Dec 12, 2022 at 11:11:24PM -0500, Nick Holland wrote:
> On 12/12/22 07:22, Why 42? The lists account. wrote:
> >
> > Hi All,
> >
> > Today sysupgrade failed for me, but I'm not sure why? Here's the output:
> [ ... ]
>
> There is a p
On 2022-12-12, Why 42? The lists account. wrote:
> Today sysupgrade failed for me, but I'm not sure why? Here's the output:
As the various mirrors get updated, this should be coming back to normal now.
On Mon, Dec 12, 2022 at 8:19 AM Stuart Henderson
wrote:
>
> On 2022-12-12, Amit Kulkarni wrote:
> > retry, and all should be ok.
>
> No, there is a problem with the files.
>
Sorry for that Robb and Stuart.
On 12/12/22 07:22, Why 42? The lists account. wrote:
Hi All,
Today sysupgrade failed for me, but I'm not sure why? Here's the output:
[ ... ]
There is a problem with the distribution network currently. Hopefully
will be resolved soon.
Doing a quick check, looks like only amd6
On Mon, Dec 12, 2022 at 07:39:49AM -0600, Amit Kulkarni wrote:
> retry, and all should be ok.
What's the basis of your statement, did something change?
It still fails for me (now @16:15 CET).
I also tried a different mirror, same failure (below).
@Stuart: Although sysupgrade output s
On 2022-12-12, Amit Kulkarni wrote:
> retry, and all should be ok.
No, there is a problem with the files.
>> I have never really used signify before, but this command from the man
>> page also generates an error:
>> > mjoelnir:_sysupgrade 12.12 13:03:30 # signify -C -p
>> > /etc/signify/openbsd
retry, and all should be ok.
On Mon, Dec 12, 2022 at 7:18 AM Why 42? The lists account.
wrote:
>
>
> Hi All,
>
> Today sysupgrade failed for me, but I'm not sure why? Here's the output:
> > # sysupgrade -s -n
> > Fetching from http://ftp.fau.de/pub/OpenBSD/
Hi All,
Today sysupgrade failed for me, but I'm not sure why? Here's the output:
> # sysupgrade -s -n
> Fetching from http://ftp.fau.de/pub/OpenBSD/snapshots/amd64/
&g
1 - 100 of 381 matches
Mail list logo
