On Wed, Jan 25, 2017 at 11:52:10AM +0200, Daniel Braniss wrote: > > > On 25 Jan 2017, at 10:47, Bernd Walter <[email protected]> wrote: > > > > On Wed, Jan 25, 2017 at 09:13:18AM +0100, Kurt Jaeger wrote: > >> Hi! > >> > >>>> 11.0-RC1 was superseded by 11.0-REL, so while that message is a bit > >>>> drastic, there's a point to it. > >>> > >>> With that argument only the latest version would be supported. > >> > >> https://www.freebsd.org/releases/ lists the supported releases. > >> There are no release candidates listed. > >> > >>> That said, it is a release candidate and as such one could argue that > >>> there never had been any official support at all. > >>> In that case however the message is wrong, because when a support has > >>> ended it implies that there was support. > >>> > >>> The check in the code is this one: > >>> .if (${OPSYS} == FreeBSD && (${OSVERSION} < 1003000 || (${OSVERSION} >= > >>> 1100000 && ${OSVERSION} < 1100122))) || \ > >>> (${OPSYS} == DragonFly && ${DFLYVERSION} < 400400) > >>> > >>> It is not about RC as such, it is explicitly about 11.0-RC. > >>> My OSVERSION is 1100121. > >>> So obviously support starts with the first release. > >>> Fair enough, but then the message is still wrong unless it was supported. > >> > >> What's stopping you from upgrading to -REL ? > > > > Buildworld on a raspberry isn't fun - if it works at all. > > Even if you crossbuild and just copy the binaries, the wear of > > MicroSD cards isn't something you want to test unless you really > > have to. > > most of the time this works for me: > mount host:/export-to-rpi/local /usr/local > echo ???WRKDIRPREFIX=/var/tmp??? >> /etc/make.conf > mount via nfs /var/tmp, i.e. > mount host:/export-to-rpi/tmp /var/tmp > also add swap via nfs: > mount host:/export-to-rpi/swap /mnt-swap > swapon /mnt-swap
This has nothing to do with updating the OS itself. That said, I assume host:/export-to-rpi/local is only used by a single host. It gets tricky with shared /usr/local, since the package registration is in a different path and ports/packages may also touch /etc - e.g. /etc/shells, or add service users for a specific software. It is possible to do, but unless you are very carefull things can easily get messy. Same goes for /tmp. Needless to say that swap isn't to be shared at all... But I'm not sure if swap on NFS is completely deadlock free. -- B.Walter <[email protected]> http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
