On Sat, May 04, 2019 at 10:33:26AM +0300, Strahil Nikolov wrote:
> On May 4, 2019 10:11:07 AM GMT+03:00, Nick Holland
> <n...@holland-consulting.net> wrote:
> >On 5/3/19 2:32 PM, Strahil Nikolov wrote:
> >> On May 3, 2019 10:49:55 PM GMT+03:00, Nick Holland
> >> <n...@holland-consulting.net> wrote:
> >>> On 5/2/19 1:52 AM, Consus wrote:
> >>>> Hi,
> >>>>
> >>>> I've upgraded my systems from 6.4 to 6.5 without a glitch, but I
> >>>> see that /etc/networks and some other files (like malloc.conf.5)
> >>>> are
> >>> still
> >>>> present, although there is no use for them in the new release.
> >>>>
> >>>> Is there a reason why these files are not listed in "FIles to
> >>> remove"?
> >>>> Is there a way to track them? It's not like something gonna
> >>>> break,
> >>> but
> >>>> old configuration files (and manual pages) lying around can make
> >>>> someone's life harder during the debug session.
> >>>
> >>> There is no promise that an upgraded machine will be file-for-file
> >>> identical to a fresh install. Here is the list of problems this
> >>> might cause you, as you can see, it's a long list and quite
> >>> horrible:
> >>>
> >>> * If you use the same hw for 20 years, you might run out of disk
> >>> space?
> >>>
> >>> Ok, not very long and not very horrible.
> >>>
> >>> You are trying to solve a non-problem. And sometimes, 'specially
> >>> on an upgraded machine, it's great to see how things WERE when the
> >>> machine was set up. If you really care, go ahead, delete stuff.
> >>>
> >>> Nick.
> >>
> >> Hi All,
> >>
> >> As I linux guy (my experience in openBSD can be easily measured in
> >> days) I can share the view of less experienced user that was planing
> >> to upgrade from 6.4 to 6.5 and that eneded with a full reinstall.
> >>
> >> I tried to update a VM (stock setup) with a 10 GB disk from 6.4 to
> >> 6.5 and thus it seemed that booting from the 6.5 DVD will do the
> >> trick. Sadly the installer never checked the avalable space , but
> >> just started to do it's stuff until reporting that not enough space
> >> is available.
> >
> >The installer didn't check. Neither did you. Let's blame the
> >installer.
>
> Well, O can't presict how big are the new tars's size -yet the updater
> shoulddo that.
> If my /usr is too small - it should make the calculation for me and refuse to
> update.
>
> How do you estinate how much space do you need for the update ? Get the iso
> and extract each archive to predict that ?
> Nah let's blame the newbie.
>
> >Ok, sure, might be nice, but when there are a snootload of different
> >platforms with radically different size binaries, it's not trivial.
> Well, if it's done in linux , its doable in openBSD.
Of course it is doable. But nobody has done it. Probably because
nobody (developer or otherwise) thought it a priority.
I'd say that even while it is not a priority, the install/upgrade
proces already does the right thing in many, many circumstances.
A even more foolproof install/upgrade is nice to have, but given the
resources available, there are more pressing things to do.
-Otto
