On Thu, Aug 08, 2024 at 10:14:46PM -0700, Greg A. Woods wrote:
> Anyone who still runs something prior to 9.4 cannot upgrade to 9.4 or
> newer without first figuring out what I just had to figure out, and it
> wasn't easy or obvious -- and notably neither google nor ddg were able
> to find that PR,
At Fri, 9 Aug 2024 01:25:24 + (UTC), RVP wrote:
Subject: Re: sysupgrade (using ftp for fetching) can't follow redirects on
nycdn.netbsd.org
>
> On Thu, 8 Aug 2024, Greg A. Woods wrote:
>
> > Requesting
> > https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest
On Thu, 8 Aug 2024, Greg A. Woods wrote:
Requesting
https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/i386/binary/sets/base.tgz
Redirected to /pub/NetBSD-daily/netbsd-9/202408050500Z/i386/binary/sets/base.tgz
ftp: Can't lookup
`/pub/NetBSD-daily/netbsd-9/202408050500Z/i386/binary/sets/
So I have this old i386 machine running NetBSD-9 on bare metal and I
decided to boot it up and try upgrading it with sysupgrade.
I did a "pkgin in sysupgrade", and then I noticed while fixing the
CACHEDIR setting to point to a place with space that sysupgrade would by
default try to
using sysutils/sysupgrade program. Everything went ok
in Xorg as I told in this mailing list.
Days after, I was trying to compile some programs and decided to install
the Xorg source set. I run #sysinst program from the running system to
install several sets. Also by mistake I installed kernel
Am 11.09.23 um 20:44 schrieb Rhialto:
On Mon 11 Sep 2023 at 19:36:13 +0200, Ede Wolf wrote:
Now, why sysupgrade needs that [weird kernel] package, is most
likely part of my question,
I remember using sysupgrade once in the past and needing to persuade it
to use the right kernel version, or
On Mon 11 Sep 2023 at 19:36:13 +0200, Ede Wolf wrote:
> Now, why sysupgrade needs that [weird kernel] package, is most
> likely part of my question,
I remember using sysupgrade once in the past and needing to persuade it
to use the right kernel version, or the right set of install sets,
blems.
sysupgrade fails, because an image it requests does not ecist. And checking
the site, it really is not there. What am I missing?
The netbsd-* set is for the kernel. Since you have a cubietruck, you probably
want netbsd-GENERIC.gz instead. Why does sysupgrade think it needs
that strange name
On Mon, Sep 11, 2023 at 06:54:36PM +0200, Ede Wolf wrote:
> Hello,
>
> not sure, wether this is the proper list, but I am having a cubietruck, that
> hasn't seen much love lately, and while trying to fix this with an upgrade,
> I am running into problems.
> sysupgrade fai
Hello,
not sure, wether this is the proper list, but I am having a cubietruck,
that hasn't seen much love lately, and while trying to fix this with an
upgrade, I am running into problems.
sysupgrade fails, because an image it requests does not ecist. And
checking the site, it really i
Hi Martin,
Martin Husemann wrote:
PS: what now? boot with CD-ROM and try to upgrade "over" again?
Yes, that should be the easy way out (or USB install image instead of CD).
one question, is sysupgrade uspposed to update the bootloader?
I noticed the two upgrade systems are
Hi!
as general news, proved that sysupgrade works... I used it to update my
venerable SparcStation 4 (SPARC 32bit v8) as well as my Sun Netra
(UltraSparc 64bit) and in both cases worked fine, very convenient since
both are running headless, remote log-in, no need for serial console or
such
Hi!
thanks, Martin, Bartosz!
Martin Husemann wrote:
No, there are no (known) binary compatibility issues.
Are you sure you upgraded with sets from the same architecture (e.g. i386
vs. amd64)?
unfortunately, that is exactly what happened. Bartosz spotted it. Since
the first issue I had, I con
In your initial mail you've posted command: sysupgrade auto
http://cdn.netbsd.org/pub/NetBSD/NetBSD-9.3/amd64
and here is mention of i386. Thats different architecture, and probably
system is messed badly now.
W dniu 07.11.2022 o 21:22, Riccardo Mottola pisze:
Hi,
Bartosz Maciejewski
On Mon, Nov 07, 2022 at 09:22:04PM +0100, Riccardo Mottola wrote:
> I think somehow 9.3 is not binary compatible with 9.2 the userland gets
> extracted, the sysupgrade breaks.
No, there are no (known) binary compatibility issues.
Are you sure you upgraded with sets from the same architectur
hink somehow 9.3 is not binary compatible with 9.2 the userland gets
extracted, the sysupgrade breaks.
Am I unlucky on this i386 system or is it a general issue? I never
upgraded with sysupgrade, but it would be so convenient for systems
without CD-ROM to boot, servers, etc.
Riccardo
PS: what no
lo,
>
> while upgrading various systems to 9.3, I wanted to test also the sysupgrade
> option.
> But how is it supposed to work? Can I use the sysupgrade installed in 9.2 and
> use it?
>
> On x86, I would have this version:
> sysupgrade-1.5nb10
>
> However, if I try
Hello,
while upgrading various systems to 9.3, I wanted to test also the
sysupgrade option.
But how is it supposed to work? Can I use the sysupgrade installed in
9.2 and use it?
On x86, I would have this version:
sysupgrade-1.5nb10
However, if I try to use it this way:
# sysupgrade auto
On Sat, Aug 17, 2019 at 10:33:04PM +0100, Luis P. Mendes wrote:
> sysupgrade fetches all tar sets chosen, but when trying to fetch
> kernels, it fails in the first one: netbsd-ARU_MBOX_OWNER
> It's not present at that address.
> sysupgrade aborts with a '404 Not found' e
Hi,
I've installed evbarm-earmv7hf in a Raspberry Pi 3B+, version 8.99.50.
In order to upgrade the system to the latest, tried to use sysupgrade
like:
/usr/pkg/sbin/sysupgrade auto
http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/evbarm-earmv7hf
sysupgrade fetches all tar sets chosen
Hi All,
I tried to do a sysupgrade for my system which I thought to be 7.1.1 and wanted
to upgrade to 7.1.2 (and afterwards 8.0). So I carried out a sysupgrade,
rebooted and I was surprised when executing uname that I got back 7.1 instead
of 7.1.2. It seems I didn't screw up anythin
On Tue, Jul 24, 2018 at 05:42:34PM +, m...@netbsd.org wrote:
> On Tue, Jul 24, 2018 at 04:39:17PM +0200, Kamil Rytarowski wrote:
> > On 24.07.2018 15:44, Miwa Susumu wrote:
> > > Hi all.
> > >
> > > I try update to NetBSD 8.0 from about six mon
On Tue, Jul 24, 2018 at 04:39:17PM +0200, Kamil Rytarowski wrote:
> On 24.07.2018 15:44, Miwa Susumu wrote:
> > Hi all.
> >
> > I try update to NetBSD 8.0 from about six months ago current.
> > by sysupgrade.
> >
>
> This would a downgrade and it's no
* Miwa Susumu (miwa...@gmail.com) wrote:
> by the way. how did you go to prompt?
Boot from DVD, mount root filesystem then edit /boot.cfg.
http://mail-index.netbsd.org/netbsd-users/2018/07/23/msg021128.html
--
Gua Chung Lim
"UNIX is basically a simple operating system,
but you have to be a geni
(sorry. i sent DM. resent to ML)
2018-07-24 23:39 GMT+09:00 Kamil Rytarowski :
>> I try update to NetBSD 8.0 from about six months ago current.
>> by sysupgrade.
>
> This would a downgrade and it's not fully supported and can brick your
> setup. It might be easier to
2018-07-24 23:06 GMT+09:00 Gua Chung Lim :
> Probably, you have to look at my recent thread.
> Read it throughly.
>
> http://mail-index.netbsd.org/netbsd-users/2018/07/22/msg02.html
thanks.
by the way. how did you go to prompt?
http://mail-index.netbsd.org/netbsd-users/2018/07/22/msg021117.ht
On 24.07.2018 15:44, Miwa Susumu wrote:
> Hi all.
>
> I try update to NetBSD 8.0 from about six months ago current.
> by sysupgrade.
>
This would a downgrade and it's not fully supported and can brick your
setup. It might be easier to reinstall unless you know what you
Probably, you have to look at my recent thread.
Read it throughly.
http://mail-index.netbsd.org/netbsd-users/2018/07/22/msg02.html
* Miwa Susumu (miwa...@gmail.com) wrote:
> Hi all.
>
> I try update to NetBSD 8.0 from about six months ago current.
> by sysupgrade.
>
>
Hi all.
I try update to NetBSD 8.0 from about six months ago current.
by sysupgrade.
after reboot then panic. at modules...?
https://imgur.com/a/LRuTSNs
sysupgrade support update from stable ? (e.g 7.1.2)
--
miwarin
> >
> > just got a netbsd 7 amd64 instance on aws up and ran:
> >
> > sysupgrade auto ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-7.1/amd64
> >
> > it ran all the way through until there were zero "postinstall fixes
> failed".
> > then rebooted the
Hi,
On Sat, May 20, 2017 at 1:17 PM, el kalin wrote:
>
> hi all...
>
> just got a netbsd 7 amd64 instance on aws up and ran:
>
> sysupgrade auto ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-7.1/amd64
>
> it ran all the way through until there were zero "postinstall fixes
hi all...
just got a netbsd 7 amd64 instance on aws up and ran:
sysupgrade auto ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-7.1/amd64
it ran all the way through until there were zero "postinstall fixes
failed". then rebooted the instance and looked at the boot log (dmesg) and
uname. they
Hi Leonardo,
Thanks, that was it!:)
Best regards,
r0ller
Eredeti levél
Feladó: Leonardo Taccari < leot@NetBSD.org (Link ->
mailto:leot@NetBSD.org) >
Dátum: 2017 május 15 13:27:06
Tárgy: Re: no console login after sysupgrade from 7.0 to 7.1
Címzett: netbsd-users@n
Hello r0ller!
r0ller writes:
> Hi All,
>
> I recently upgraded my 7.0 (amd64) to 7.1 using sysupgrade and although I was
> very cautious during the upgrade process when answering all the questions
> about the config file changes, I may have done something wrong. So currently
&
Hi All,
I recently upgraded my 7.0 (amd64) to 7.1 using sysupgrade and although I was
very cautious during the upgrade process when answering all the questions about
the config file changes, I may have done something wrong. So currently I cannot
logon as root via the console but interestingly
Fredrik Pettai writes:
> Right, It's easy to confuse them.
>
> I was originally referring to pkgsrc/sysutils/sysupgrade which jmmv@ made
> over a year ago...
> http://blog.netbsd.org/tnf/entry/introducing_sysbuild_and_sysupgrade
>
> And now I learned about Julian F
On Jan 19, 2014, at 13:39 , Benny Siegert wrote:
>> What's wrong with pkgsrc? Why needs the sysutils/sysupgrade package to be in
>> base?
>
> Note that these are two different codebases: sysupdate, as developed by
> Julian Fagir is not the same thing as the sys
blah… doing multiple thing at the same time sometimes causes confusion…
s/sysupdate/sysupgrade/g
http://www.netbsd.org/docs/guide/en/chap-upgrading.html#idm77006000
/P
signature.asc
Description: Message signed with OpenPGP using GPGMail
38 matches
Mail list logo
