Re: Accessibility in the FreeBSD installer and console
> On 9. Jul 2022, at 03:22, Klaus Küchemann wrote: > > >> Am 07.07.2022 um 19:32 schrieb Hans Petter Selasky : >> >> Hi, >> >> The only argument I've heard from some non-sighted friends about not using >> FreeBSD natively is that ooh, MacOSX is so cool. It starts speaking from the >> start if I press this and this key. ……. > > Hi, > > I would like to shortly introduce myself. > I am indispensable for all your friends and everybody else > and yes, I can speak (and I can even hear)- > I am the de facto standard for everything audio for Apple users and I even > can > make users of other OSes very very happy. > >> >> Am 08.07.2022 um 12:53 schrieb Hans Petter Selasky : >> Hi, >> Here is the complete patch for Voice-Over in the FreeBSD console: >> >> https://reviews.freebsd.org/D35754 >> >> You need to install espeak from pkg and then install the >> /etc/devd/accessibility.conf file and then run sysctl >> kern.vt.accessibility.enable=1 after booting the new kernel. >> >> It is freaking awesome! >> >> There might be some bugs, but it worked fine for me! >> >> —HPS > > Congratulations ! > > But while reading the docs of your system`s bluetooth drivers I became a bit > afraid > that I won’t be fully supported , I hope this is unfounded. > > It’s not only that I’m a shiny white culty thing .. > your friends can leave me in their ears and can simultaneously hear the > surroundings AND the Audio output. > That’s why I’m indispensable… > > Will you ensure that at least one bt-chip will support me in your system and > will you > care for the corresponding drivers? > > If yes I would be happy to meet you in your VT-console , > > And when you later even support vice versa: > -SpeechToText- , > It’s possible that we become friends for life . > > > Best Regards, > yours > > AirPodsPro :-) But why would you ever leave your family that was designed from the ground up to match you and any need you could potentially have? And why would you not share any word your "owner" (the person who spent money on you, so they could use you) says with your creator and all its connected systems and entities, so that they could be fully analyzed and monetized? -m p.s. seriously, if you want the full Apple experience, you really should stay within their ecosystem. Trying to compete with that (with all its questionable implications in terms of digital sovereignty) is pointless, especially if you are neither broke nor care too much about privacy. If these things mean nothing to you, just buy the off the shelf solution and save the time that tinkering with free alternatives (that will never be as smooth as "the real thing") would require and spend it on things that mean something to you (friends, family, charity).
Re: BLAKE3 unstability?
On Sat, Jul 9, 2022 at 11:57 AM Evgeniy Khramtsov wrote: > I can reproduce via: > > $ truncate -s 10G /tmp/test > $ mdconfig -f /tmp/test -S 4096 > $ zpool create test /dev/md1 > $ zfs create -o checksum=blake3 test/b > $ dd if=/dev/random of=/test/b/noise bs=1M count=4096 > $ sync > $ zpool scrub test > $ zpool status > OK. I'll leave it to the OpenZFS folks then. The boot path isn't involved in this at all :) Thanks for the reproducer. Warner
Re: BLAKE3 unstability?
I can reproduce via: $ truncate -s 10G /tmp/test $ mdconfig -f /tmp/test -S 4096 $ zpool create test /dev/md1 $ zfs create -o checksum=blake3 test/b $ dd if=/dev/random of=/test/b/noise bs=1M count=4096 $ sync $ zpool scrub test $ zpool status
Re: BLAKE3 unstability?
Be advised that blake3 went into the bootloader yesterday and has been only lightly tested. Don't think this would cause your checksum errors since the boot loader is read only. Warner On Sat, Jul 9, 2022, 10:27 AM Evgeniy Khramtsov wrote: > -CURRENT as of: > > commit eec3290266bc09b4c4b4d875d2269d611adc0016 (main) > Author: Ganbold Tsagaankhuu > Date: Sat Jul 9 13:06:52 2022 + > > Add RK3568 SoC support to pinctrl driver. > > Submitted by: sos > Reviewed by:manu > Differential Revision: > https://reviews.freebsd.org/D31330 > > New boot environment created via bectl, zfs set checksum=blake3 new_be, > pkg -r /tmp/be_N upgrade, reboot into new BE, login failed after > sysutils/pam_xdg failed integrity check. > > Rebooted into previous BE, did zpool scrub and got 32 checksum errors > without files specified before getting panic (no trace due to drm-kmod?). > > bectl destroy / zfs destroy of new env with blake3 restored pool back to > 0 checksum error state. > > No out-of-tree base modifications present, only a custom kernel config. > >
BLAKE3 unstability?
-CURRENT as of: commit eec3290266bc09b4c4b4d875d2269d611adc0016 (main) Author: Ganbold Tsagaankhuu Date: Sat Jul 9 13:06:52 2022 + Add RK3568 SoC support to pinctrl driver. Submitted by: sos Reviewed by:manu Differential Revision: https://reviews.freebsd.org/D31330 New boot environment created via bectl, zfs set checksum=blake3 new_be, pkg -r /tmp/be_N upgrade, reboot into new BE, login failed after sysutils/pam_xdg failed integrity check. Rebooted into previous BE, did zpool scrub and got 32 checksum errors without files specified before getting panic (no trace due to drm-kmod?). bectl destroy / zfs destroy of new env with blake3 restored pool back to 0 checksum error state. No out-of-tree base modifications present, only a custom kernel config.
Heads up: you need to rebuild all nfs modules from sources
Hi, Commits over the last couple of days and ones happening over the next few days change the internal KPI between the nfs modules (nfscommon.ko, nfscl.ko and nfsserver.ko). As such, after pulling an up to date main from the git repo you need to build all nfs modules from the new sources. I am not doing a version bump, since mav@ indicated it was not necessary and there will be several changes over multiple commits. rick
