Live data from Hacker News

FreeBSD 12.2-BETA1

lists.freebsd.org

41–50 of 55 posts

Re: FreeBSD 12.2-BETA1

#41

Earlier quoted context omitted.

It's more the number of reboots and invocations of freebsd-update. Since these are all manual steps, you need to keep track of where you are and invoke the next step manually. The current process for upgrading FreeBSD is roughly, assuming that you're just using packages and not ports is: * freebsd-update upgrade * freebsd-update install * reboot * freebsd-update install * pkg upgrade * reboot * freebsd-update install…

I absolutely agree. I run FreeBSD on my NAS to take advantage of ZFS but every time I update it I have to Google the process or find my notes since it's incredibly non-intuitive.

freebsd-update prints out what you need to do next at each step though. If it wants you to reboot and run it again it says that.

Re: FreeBSD 12.2-BETA1

#42
post #26

Earlier quoted context omitted.

Why do you not use poudriere? And build automatically everything from ports then install the build-ed packages on you machine's?

I feel poudriere takes too much time and disk space building literally everything. I would like it to pick up dependencies from pkg and only build stuff from source when I have options changed. Incidentally I wrote a shell script that does this.

>I feel poudriere takes too much time and disk space building literally everything.

No not really just your packages and the dependencies of those.

Re: FreeBSD 12.2-BETA1

#43
post #26

Earlier quoted context omitted.

Why do you not use poudriere? And build automatically everything from ports then install the build-ed packages on you machine's?

This is something I've been meaning to look into, but it still doesn't change the postgis30/postgresql11-server dependency in the current ports tree. I'm sure I could work around it, but then I start to ask myself whether I'd rather do FreeBSD software administration or create an OpenSuse VM, install the packaged software (which is already the right version and already has the right config options), and work on my GI…

>but it still doesn't change the postgis30/postgresql11-server dependency in the current ports tree

If you tell make.conf that postgres12 is the default it will compile postgis for that version, same with php/ruby/mysql and so on.

Re: FreeBSD 12.2-BETA1

#44

Earlier quoted context omitted.

It's more the number of reboots and invocations of freebsd-update. Since these are all manual steps, you need to keep track of where you are and invoke the next step manually. The current process for upgrading FreeBSD is roughly, assuming that you're just using packages and not ports is: * freebsd-update upgrade * freebsd-update install * reboot * freebsd-update install * pkg upgrade * reboot * freebsd-update install…

Sounds like a great yak-shaving opportunity, to write a script that automates it

Which everyone does, if one has more then 2 machines ;)

Re: FreeBSD 12.2-BETA1

#45

Earlier quoted context omitted.

It's more the number of reboots and invocations of freebsd-update. Since these are all manual steps, you need to keep track of where you are and invoke the next step manually. The current process for upgrading FreeBSD is roughly, assuming that you're just using packages and not ports is: * freebsd-update upgrade * freebsd-update install * reboot * freebsd-update install * pkg upgrade * reboot * freebsd-update install…

I absolutely agree. I run FreeBSD on my NAS to take advantage of ZFS but every time I update it I have to Google the process or find my notes since it's incredibly non-intuitive.

Or you just read the printout until it says fetch first ;)

Re: FreeBSD 12.2-BETA1

#46
post #42

Earlier quoted context omitted.

I feel poudriere takes too much time and disk space building literally everything. I would like it to pick up dependencies from pkg and only build stuff from source when I have options changed. Incidentally I wrote a shell script that does this.

>I feel poudriere takes too much time and disk space building literally everything. No not really just your packages and the dependencies of those.

Ok, slight exaggeration. The dependencies get quite huge though, especially when you are using something substantial.

Re: FreeBSD 12.2-BETA1

#47

Earlier quoted context omitted.

> no CAP has a bubble could you please tell me what that means ? I googled "CAP bubble computer" and the results were unrelated.

They were referring to if there was any bulging on any of the capacitors on any of the components in the computer.

ah thanks I wasn't sure what CAP meant now it's all clear.

Re: FreeBSD 12.2-BETA1

#48

I really like FreeBSD, and I run it on my home server, but the whole update process really needs a lot of work. The process described in this announcement is accurate in my experience: Run freebsd-update twice, reboot, run freebsd-update again, reinstall or rebuild applications, reboot again, run freebsd-update yet again. The upgrade process works well, but it's much more manual than it is in the Linux world. When Pk…

While I mostly agree, you also hit the power of the freebsd system: you can do something different. In linux if you want PostgreSQL 12+PostGIS 3.0 with xml support and the packages deliver PostgreSQL 12+PostGIS 3.0 without xml you are stuck without xml support as the package systems don't make it easy for lay people to select options. With FreeBSD you get that power if you want it.

It should be easier though.

Re: FreeBSD 12.2-BETA1

#49

I really like FreeBSD, and I run it on my home server, but the whole update process really needs a lot of work. The process described in this announcement is accurate in my experience: Run freebsd-update twice, reboot, run freebsd-update again, reinstall or rebuild applications, reboot again, run freebsd-update yet again. The upgrade process works well, but it's much more manual than it is in the Linux world. When Pk…

I usually upgrade by recompiling the OS. Minor updates only take a few minutes to compile using filemon and the WITH_META_MODE=YES environment variable. The advantage is that it's easy to maintain out-of-tree patches to the source.
Post reply on HN