Re: domain names and internationalization?
Christoph Moench-Tegeder wrote: >## Rick Macklem (rmack...@uoguelph.ca): > >> I am hoping someone knows what DNS does in this area (the >> working group list uses terms like umlaut, which I have never >> even heard of;-). > >The dry start on that topic is RFC5890 >https://datatracker.ietf.org/doc/html/rfc5890 >The Wikipedia overview looks really decent: >https://en.wikipedia.org/wiki/Internationalized_domain_name >What else? Thanks. Both the RFC and wikipedia article were useful. It turns out that the messy part for NFSv4 is that the RFCs specified that the labels were in Unicode (U-labels) and not A-labels. --> RFC 7530 also wants the code to translate an A-label to a U-label and then compare U-labels. (Not sure why that is preferable to a case independent comparison of the A-labels, but maybe the intent was that an A-label would compare the same as a U-label in a domain name?) The FreeBSD man page for hostname(1) and gethostname(3) don't seem to limit the labels in the name to A-label format. Does anyone use non-ascii (ie. a U-label with multibyte characters in it) in a machine's hostname? Right now the coding of nfsuserd(8) does not conform to the RFCs, but should work for domain names where all the labels are A-labels (either LDN or "xn--" followed by a Punycode encoded unicode string). rick Gruß <-- see? eszett :) Christoph -- Spare Space
Re: Good practices with bectl
Summary: Using bectl for upgrades
RELEASE=Whatever
> bectl create ${RELEASE}
> bectl mount ${RELEASE}
BASEDIR=/tmp/be_mount. # Use mount point returned by bectl mount
[freebsd-update method]
> freebsd-update -b ${BASEDIR} -d ${BASEDIR}/var/db/freebsd-update \
upgrade -r ${RELEASE}
> freebsd-update -b ${BASEDIR} -d ${BASEDIR}/var/db/freebsd-update install
# Ignore admonitions to reboot, since we're using a boot environment
> freebsd-update -b ${BASEDIR} -d ${BASEDIR}/var/db/freebsd-update install
> bectl activate ${RELEASE}
#> bectl activate -t ${RELEASE} # Failsafe (if the machine is too far away
to simply walk over and
switch to the old BE):
> reboot
[upgrade from source method]
> make DESTDIR=${BASEDIR} installkernel
> etcupdate -p -D $BASEDIR
> make DESTDIR=${BASEDIR} installworld
> etcupdate -D $BASEDIR
> make DESTDIR=${BASEDIR} -DBATCH_DELETE_OLD_FILES delete-old
delete-old-libs
> bectl activate ${RELEASE}
#> bectl activate -t ${RELEASE} # Failsafe (if the machine is too far away
to simply walk over and
switch to the old BE):
> reboot
Alexander Leidinger escreveu no dia quarta,
21/09/2022 à(s) 11:45:
> Quoting David Wolfskill (from Wed, 21 Sep 2022
> 03:25:52 -0700):
>
> > On Wed, Sep 21, 2022 at 11:27:06AM +0200, Alexander Leidinger wrote:
> >> ...
> >> make DESTDIR=${BASEDIR} -DBATCH_DELETE_OLD_FILES delete-old
> delete-old-libs
> >>
> >> Usually I replace the delete-old-libs with check-old, as I don't want
> >> to blindly delete them (some ports may depend on them... at least for
> >> the few libs which don't have symbol versioning).
> >>
> >
> > A way to address that issue that may work for you is to install
> > appropriate misc/compat* ports/packages.
>
> I'm running exclusively on -current. In the cases where this happens,
> there are no compat packages yet. And I rather update the ports than
> to install a compat package. It doesn't hurt me to keep the libs
> during the pkg rebuild.
>
> In the generic case I prefer to stay safe and keep the libs until I
> validated that nothing uses them anymore. That's the reason why I made
> the delete-old-libs functionality separate from delete-old already in
> the initial implementation.
>
> Bye,
> Alexander.
> --
> http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
> http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
>
--
Nuno Teixeira
FreeBSD Committer (ports)
Re: Good practices with bectl
On 20/09/22 19:19, Alan Somers wrote:
On Tue, Sep 20, 2022 at 4:14 PM Nuno Teixeira wrote:
Hello to all,
I will use becl for the first time for current upgrades.
Just to check that I'm thinking correctly:
Create a test environment for upgrade:
bectl create -r test (should I use '-r'?)
Activate test:
bectl activate test
reboot
...
upgrade OS on test
reboot
...
if a problem happens, reboot default from BE loader
---
if everything fine destroy default and rename test to default
bectl destroy -o default
bectl rename test default
repeat on next upgrade
Don't know if a faster way exists with chroot or bectl jail...
Any hints appreciated.
Thanks,
--
Nuno Teixeira
FreeBSD Committer (ports)
I don't think you need to use "-r". Also, you're forgetting one of
the best things about boot environments: you can upgrade them even
when not booted into them. That's faster than upgrading the running
BE. Here is the procedure I use:
RELEASE=Whatever
sudo bectl create ${RELEASE}
sudo bectl mount ${RELEASE}
BASEDIR=/tmp/be_mount.# Use mount point returned by bectl mount
sudo freebsd-update -b ${BASEDIR} -d ${BASEDIR}/var/db/freebsd-update
upgrade -r ${RELEASE}
sudo freebsd-update -b ${BASEDIR} -d ${BASEDIR}/var/db/freebsd-update install
# Ignore admonitions to reboot, since we're using a boot environment
sudo freebsd-update -b ${BASEDIR} -d ${BASEDIR}/var/db/freebsd-update install
sudo bectl activate ${RELEASE}
I like to use `sudo bectl activate -t ${RELEASE}`, it activates new
partition to be ROOT only for the next boot. If something goes wrong,
you just need to power cycle the machine and it will boot on previous
partition.
After a success boot you must run `sudo bectl activate RELEASE` again to
make it permanent.
sudo reboot
This general procedure works just as well if you're upgrading from source, too.
sudo make DESTDIR=${BASEDIR} installworld
sudo mergemaster -m $PWD -D $BASEDIR -U
-Alan
Re: Good practices with bectl
Quoting David Wolfskill (from Wed, 21 Sep 2022
03:25:52 -0700):
On Wed, Sep 21, 2022 at 11:27:06AM +0200, Alexander Leidinger wrote:
...
make DESTDIR=${BASEDIR} -DBATCH_DELETE_OLD_FILES delete-old delete-old-libs
Usually I replace the delete-old-libs with check-old, as I don't want
to blindly delete them (some ports may depend on them... at least for
the few libs which don't have symbol versioning).
A way to address that issue that may work for you is to install
appropriate misc/compat* ports/packages.
I'm running exclusively on -current. In the cases where this happens,
there are no compat packages yet. And I rather update the ports than
to install a compat package. It doesn't hurt me to keep the libs
during the pkg rebuild.
In the generic case I prefer to stay safe and keep the libs until I
validated that nothing uses them anymore. That's the reason why I made
the delete-old-libs functionality separate from delete-old already in
the initial implementation.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
pgpNgN_xBrE1T.pgp
Description: Digitale PGP-Signatur
Re: Good practices with bectl
On Wed, Sep 21, 2022 at 11:27:06AM +0200, Alexander Leidinger wrote:
> ...
> make DESTDIR=${BASEDIR} -DBATCH_DELETE_OLD_FILES delete-old delete-old-libs
>
> Usually I replace the delete-old-libs with check-old, as I don't want
> to blindly delete them (some ports may depend on them... at least for
> the few libs which don't have symbol versioning).
>
A way to address that issue that may work for you is to install
appropriate misc/compat* ports/packages.
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
In 2022, the governors of Texas and Florida resurrect the racist
ploys of the "White Citizens’ Council" of 1962 -- at taxpayers' expense.
See https://www.catwhisker.org/~david/publickey.gpg for my public key.
signature.asc
Description: PGP signature
Re: Good practices with bectl
Quoting Alan Somers (from Tue, 20 Sep 2022
16:19:49 -0600):
sudo bectl activate ${RELEASE}
Failsafe (if the machine is too far away to simply walk over and
switch to the old BE):
bectl activate -t ${RELEASE}
Needs an activate without -t later.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
pgpXQ2xA9dSvy.pgp
Description: Digitale PGP-Signatur
Re: Good practices with bectl
Quoting Nuno Teixeira (from Wed, 21 Sep 2022
00:11:41 +0100):
(...)
maybe:
> yes | make DESTDIR=${BASEDIR} delete-old delete-old-libs
make DESTDIR=${BASEDIR} -DBATCH_DELETE_OLD_FILES delete-old delete-old-libs
Usually I replace the delete-old-libs with check-old, as I don't want
to blindly delete them (some ports may depend on them... at least for
the few libs which don't have symbol versioning).
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
pgpXRih39w_V7.pgp
Description: Digitale PGP-Signatur
Re: Good practices with bectl
* Nuno Teixeira [20220921 00:11]:
> (...)
> maybe:
> > yes | make DESTDIR=${BASEDIR} delete-old delete-old-libs
Exactly, DESTDIR is used by all the targets.
BTW, you can just set BATCH_DELETE_OLD_FILES=yes (either on the
command-line or in make.conf) instead of using "yes" here.
--
Felix Palmen {private} fe...@palmen-it.de
-- ports committer (mentee) --{web} http://palmen-it.de
{pgp public key} http://palmen-it.de/pub.txt
{pgp fingerprint} 6936 13D5 5BBF 4837 B212 3ACC 54AD E006 9879 F231
signature.asc
Description: PGP signature
