Ok people I still didn't have the pleasure of performing a fully working upgrade. Nothing to do i always mess things up when merging files i guess... I understand i shouldn't merge files like /etc/group or passwd but there are many other files i really don't know if i should keep the new copy or I shouldn't. Can you guys help me with this? How do you generally do ? Is there a minimum set of files you pay particular attention to when upgrading the system? Let's start with the basics... i am running this system: NetBSD 10.99.10 (GENERIC) amd64 if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Is it reasonable that i perform an upgrade every now and then on this ? sysupgrade auto http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/amd64 if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); }

Upgrade too complicated on NetBSD

netbsdnoob

Ok people I still didn't have the pleasure of performing a fully working upgrade.
Nothing to do i always mess things up when merging files i guess...
I understand i shouldn't merge files like /etc/group or passwd but there are many other files i really don't know if i should keep the new copy or I shouldn't.

Can you guys help me with this? How do you generally do ? Is there a minimum set of files you pay particular attention to when upgrading the system?

Let's start with the basics... i am running this system:

NetBSD 10.99.10 (GENERIC) amd64

Is it reasonable that i perform an upgrade every now and then on this ?

sysupgrade auto http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/amd64

rvp

netbsdnoob See this thread for how I upgrade my NetBSD. Nary a problem so far...

Said it once but, will say it one more time ... I only use sysinst to do upgrades. Boot the newer image and choose upgrade instead of install

netbsdnoob

pin yeah that was what i was thinking... but i didn't get why sysupgrade doesn't handle etc files the same way as sysinst... what's sysinst actually doing?

Also is there a way to do the upgrade without actually creating a bootable device? like just installing the stuff on my same hard drive in my home directory?

nettester

I don't have any experience with upgrading NetBSD but by pure logic it would make sense to keep files you modified by hand or which are obviously unique to your system (like passwd or group). For everything else i wouldn't see a reason to keep old files.

netbsdnoob

nettester yes that's what i thought but i still was able to mess up my system.
There were files with mtree in the name probably related to drivers/modules. Then there are files i just don't know what do with.

netbsdnoob

rvp i have an additional problem ... after a failed upgrade... i booted from my installation cd and did an "upgrade" there so to get back my previous base system+kernel. Everything works fine now! Finally!

Anyway now i tried again to run sysupgrade auto "path to the latest HEAD amd64 bla bla bla" and i get this:

/usr/pkg/sbin/sysupgrade: /usr/bin/git: not found
sysupgrade: E: Failed to determine kernel name; please set KERNEL explicitly

I am puzzled... i mean i have git, it is just not on that path it is at /usr/pkg/bin/git

What is happening now? ahah

kc9udx

ln -s /bin/git /usr/pkg/bin/git