Date: Wed, 25 Jan 2017 13:28:03 +0200 From: Daniel Braniss <danny@cs.huji.ac.il> To: ticso@cicely.de Cc: Kurt Jaeger <pi@opsec.eu>, Bernd Walter <ticso@cicely7.cicely.de>, freebsd-arm@freebsd.org, freebsd-ports@freebsd.org Subject: Re: 11.0-RC1 unsupported by ports? Message-ID: <4FF1A4D2-0A95-4416-B3EB-CFB2290A307E@cs.huji.ac.il> In-Reply-To: <20170125103914.GD7817@cicely7.cicely.de> References: <20170125042413.GK85666@cicely7.cicely.de> <20170125062045.GS13006@home.opsec.eu> <20170125075459.GL85666@cicely7.cicely.de> <20170125081318.GT13006@home.opsec.eu> <20170125084738.GM85666@cicely7.cicely.de> <41DFEC72-FA4B-4065-B057-D29EF43BD494@cs.huji.ac.il> <20170125103914.GD7817@cicely7.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 25 Jan 2017, at 12:39, Bernd Walter <ticso@cicely7.cicely.de> = wrote: >=20 > On Wed, Jan 25, 2017 at 11:52:10AM +0200, Daniel Braniss wrote: >>=20 >>> On 25 Jan 2017, at 10:47, Bernd Walter <ticso@cicely7.cicely.de> = wrote: >>>=20 >>> On Wed, Jan 25, 2017 at 09:13:18AM +0100, Kurt Jaeger wrote: >>>> Hi! >>>>=20 >>>>>> 11.0-RC1 was superseded by 11.0-REL, so while that message is a = bit >>>>>> drastic, there's a point to it. >>>>>=20 >>>>> With that argument only the latest version would be supported. >>>>=20 >>>> https://www.freebsd.org/releases/ lists the supported releases. >>>> There are no release candidates listed. >>>>=20 >>>>> 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. >>>>>=20 >>>>> The check in the code is this one: >>>>> .if (${OPSYS} =3D=3D FreeBSD && (${OSVERSION} < 1003000 || = (${OSVERSION} >=3D 1100000 && ${OSVERSION} < 1100122))) || \ >>>>> (${OPSYS} =3D=3D DragonFly && ${DFLYVERSION} < 400400) >>>>>=20 >>>>> 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. >>>>=20 >>>> What's stopping you from upgrading to -REL ? >>>=20 >>> 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. >>=20 >> most of the time this works for me: >> mount host:/export-to-rpi/local /usr/local >> echo ???WRKDIRPREFIX=3D/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 >=20 > This has nothing to do with updating the OS itself. somehow the subject was =E2=80=98compiling ports=E2=80=99 to build the = os I cross compile and that works fine. >=20 > That said, I assume host:/export-to-rpi/local is only used by a > single host. no, if you take care, we have been sharing /usr/local since way back. btw, it=E2=80=99s read only for the clients. > 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. the ports compilation keep things in /var/db, and that tends to cause = problems with pkg - since it insists in locking the sqlite db, so I see that on = the SD, and copy it to more secure location when I=E2=80=99m done (I keep losing track of = those small sd cards, there is hardly any place to put a label on them :-) > Same goes for /tmp. > Needless to say that swap isn't to be shared at all=E2=80=A6 that would certainly be foolish :-) > But I'm not sure if swap on NFS is completely deadlock free. so far It=E2=80=99s been just fine, e.g., compiling pkg takes up a lot = of resources and this was the only way it worked, not to mention gcc. I compiled all of the X11!=20 >=20 > --=20 > B.Walter <bernd@bwct.de> http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FF1A4D2-0A95-4416-B3EB-CFB2290A307E>