Date: Thu, 20 Jul 2017 11:51:26 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Re: Critique this plan? Message-ID: <0cd3cf82-12c0-6334-cc75-483227783c62@FreeBSD.org> In-Reply-To: <E1dY8bf-0008Pi-3m@rmmprod05.runbox> References: <E1dY8bf-0008Pi-3m@rmmprod05.runbox>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --hxnKBEbeDNVTiErCHLBnLAotR3EKKRcMU Content-Type: multipart/mixed; boundary="VPGUmSMeAue1Q4BUEK26XmcisDN2KMIJO"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-current@freebsd.org Message-ID: <0cd3cf82-12c0-6334-cc75-483227783c62@FreeBSD.org> Subject: Re: Critique this plan? References: <E1dY8bf-0008Pi-3m@rmmprod05.runbox> In-Reply-To: <E1dY8bf-0008Pi-3m@rmmprod05.runbox> --VPGUmSMeAue1Q4BUEK26XmcisDN2KMIJO Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/07/20 11:22, Jeffrey Bouquet wrote: > It seems I've a brick wall [too many ports to use pkg effectively ] -= - [ 3551 ]=20 > and too many need ' pkg lock ' in ' v11 ' for ino64 fixes, 12.0-CURRENT= , and quite a few > others fail to build from ports, either compiler, so are also 'pkg lock= ' or in a few > instances binaries/trees copied from other installs, so that my DESKTOP= can continue > running a if it were 2003 Microsoft based, vs 2004 Freebsd January base= d, where a reinstall > seems in order OR, I should just sit and wait til 13.0-CURRENT and proc= eed that way. You're proposing to make a backup of your system in spare space on your hard drive, and then install a pristine system and backport your various changes to it in order to bring your system up to date? Waiting for 13.0-CURRENT probably won't solve all your compilation and package management problems, or at least, not all of them. You'ld be better off updating now, but trying to clean up all your local changes as far as possible so that future upgrades are less traumatic. > .................. > Meantime, how is the following as a workaround > mv /usr/src /src-2017 > mv /usr/obj /obj-2017 > mkdir -p /usr/src > mkdir -p /usr/obj > cd /usr/src > bw, etc > .................... > or > ..................... > [ clean install ] > mount -t ufs /dev/gpt/2004root /mnt-root > mount -t ufs /dev/gpt/2004var /mnt-var > mount -t ufs /dev/gpt/2004tmp /mnt-tmp > mount -t ufs /dev/gpt/2004usr /mnt-usr > into which I surmise an installworld would fail as multiple DESTDIRS a= re included.=20 You can do: mount -t ufs /dev/gpt/2004root /mnt mount -t ufs /dev/gpt/2004var /mnt/var mount -t ufs /dev/gpt/2004tmp /mnt/tmp mount -t ufs /dev/gpt/2004usr /mnt/usr so your copy of your 2004 system is laid out below /mnt as it would be when live. If you also do: mount -t devfs devfs /mnt/dev then you can chroot into /mnt, although I'm not sure quite how useful that would be to you. > ................. > nullfs ? > ............... > Revert to all-in-one / system, no /var /tmp /usr? > ............. > or some new install=20 > ............. > None of these are plans as of yet, save proceeding without any upgrad= e whatsoever. I recall > unpacking base.txz [etc] to fix a failing installworld in the recent pa= st, so any foolproof > method of that would also be welcome. But I suspect much would remain = undone,=20 > initial *proper* setup of /etc/mail, /etc/groups, as well as the loss o= f fine-tunings I've > done over the past 13 years or so, if it were done preplanned as a new-= then-rsync-the-old > system-over-it sort of reinstall [ not looking forward to undoing year= s of week-by-week > this-rc that-rc fixups... newbie in so many areas who just copy-p= asted the > work of others into this system, to excellent, usually effect. ]=20 > ..............=20 Yeah. You've a lot of work ahead reviewing each of your changes and porting what you need to the new version. As a matter of routine system maintenance, it is good practice to try and revert local changes and track updates to the default system when possible -- ie. to adopt any upstream fixes as they become available. > Apologies for the email that went on three times longer [ more verbos= e ] than I planned, sort > of making its Subject: a misstatement of the body of the em= ail. > ...................... > ................... If you're planning on working from a new install, my advice would be to summarize what functionality you want from your system as a series of bullet points and then only port whichever of your changes you need in a directed fashion to achieve each of those points. Do this as cleanly as possible, so you can achieve your required functionality with the minimum amount of configuration work / local patches. Cheers, Matthew --VPGUmSMeAue1Q4BUEK26XmcisDN2KMIJO-- --hxnKBEbeDNVTiErCHLBnLAotR3EKKRcMU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJZcIs1XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTn1EwP/AsTnSThokwhElrCRvCuE0i+ 7NanbK/Y2RUo8dEf/7cOJYlmrtX6Moh7bpi6eAhpyM+ChxyWukiPU/CE7h4PPAQ8 ONG6hNSppaRatp8vi8LTIAsWBomXXAmTHTnUQ5uG/LOoIBOB/0a0Gk+LX3x4z3vU EAZl0hl/hGTKXEuZHYf/OYqn9/gJvjc5ULtIF8nNHNVp2dVGnn1KwAKBsagKR+CQ 1Tjs1WL5GUbOy1Hh2OUA4SWLYCAAzWMeBZ3dMiJoc9TUp/yLwOFysL/bEuGzURPt U8l+V1hUIcGJTv/CVlUxSS9QAYVpESGlvGxb+0ne80XJodDMlqJ9Lk9L9PZP8ppJ 5yxd4aiNHoG5cyu7S7vuH2honW8hLI4yF+eX4RT/uX0NQ2pgTiwkPN1+CMFM6J0Z CBtNzU3iecV2HtHdFVaA4ESWXTpy37hg1FM9AEl7B0l18JnX5fa+9emDasCuZiZ3 7kL5JLcouJytzH+8FOVka/Rdc4e5ZA0B4qKwdCdAFYobhfwVvsmlYbs6eGqreROI TOBWdE/H+LNLBIMcLc/80TndsC0nl/NV6uI4DgM7PdJrVQbqIxD2bgLgYeervUOt XTqeY0XGZO0lXb5taFuqHKP69EiKbW6NL+XOVL+piboB8exGnzCfVGWb7a1mzohs F0aR/tCNGKhH/H0SbRLM =WCPu -----END PGP SIGNATURE----- --hxnKBEbeDNVTiErCHLBnLAotR3EKKRcMU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0cd3cf82-12c0-6334-cc75-483227783c62>