i forgot, what are good ways to change the terminals (plain/pure/non-X) to black on white text, temporarily, and also saving that setting?

Title: 271388 – irc/soju: update to v0.6.1

is ashish here ?

RhodiumToad, Thank you; good to know/be reminded that "pkg" knows about "flavor" & package+flavor name depends per port(🤡)

the hard part would be, how could pkg know or guess what flavor is required if you specify only a package origin (i.e. cat/port rather than a packagename)

for some flavor types, like x11/nox11 variants of packages, are very different in functionality

pkg-query(8) does not mention if it works on (un)installed packages ... wait per "EXAMPLES" section, only installed ones

RhodiumToad: do we have a "default" flavour?

parv: pkg rquery queries a repository

pkg query queries the local installed pkg db

meena: every origin has a default flavor, yes

RhodiumToad, I read that; thought was limited to "repository"-related data (URL, ABI, etc). Appreciate the correction

rquery can only query a subset of the package data, i.e. only the parts that are entered into the repository metadata

so you can't get things like (iirc) file manifests or so on

but annotations are in the metadata, so you can see those

Does not find -x11 version: pkg rquery '%n %Av %At' -x vim # Try with s/vim/vim-x11; "-x" is not effective

Now OTOH: pkg search -x vim # 👍🏽

parv: I get the same amount of stuff for pkg search vim and pkg search -x vim (23)

meena, Use of "-x" is now a habit after non-x search not finding things most of the time; also now would need to only tweak the search term & not have to worry about lack of "-x" option

I also thought pkg-rquery would find "vim-x11" with "-x" with term of "vim" but did not

-x seems to be behaving pretty weirdly

pkg rquery -I -x 'vim' finds a lot of stuff

oh I see

you're infected with a GNUism

has to be pkg rquery -x '%n Av %At' vim

pkg rquery -x '%n %Av %At' vim

(remember, all options come before all arguments)

RhodiumToad, Right diagnosis doctor.

Sorry meena, RhodiumToad to bother with mistyped command

.oO( Oh man /me is laughing at own error )

How is the freebsd bluetooth audio support between: shit and non existent? :D

last I heard, there was a virtual_oss bluetooth audio connector, but I never tried it

ok I guess if the normal bluetooth is plane zero I shouldnt even dare to look at the RPI 3-4 bluetooth support with FBSD

pretty sure bluetooth is not supported on rpi3-4 on fbsd

unless possibly via an external usb dongle?

note that the internal audio isn't supported on rpi 3/4 either

Other BSDs are probably even worse, FBSD usually number 1 in new hw support compared to the other two.

Hi, I have gotten 4 checksum errors on all 4 physical disks in a raidz2 volume. pastebin.com/y9S7WMeu

Title: $ sudo zpool status -v - Pastebin.com

smartmontools do not show any wear or error information for the disks

It seems like a memmory or controller error.

can happen

Question is how can I remove the "files" that are listed in the output?

Based on the output in pastebin.com/y9S7WMeu

Title: $ sudo zpool status -v - Pastebin.com

Is there anything that I can or should do?

hang around, someone else may know

looks like metadata

pastebin.com/Xyn0cj4T <-- does anyone know which periodic script this is ?

Title: cat /etc/periodic.confdaily_status_security_chksetuid_fs="ufs,zfs"daily_st - Pastebin.com

in what version?

13.2

I killed them all yesterday, now it's back on, most likely because it runs on /backups which has millions of files

greping for find just shows: / /ssd_bkp /zroot /usr/obj /usr/ports /usr/home /backups /backups/veeam67 /backups/dd /backups/test /backups/mfs /backups/mail /backups/logs /ssd_bkp/mfs /dev/null (find)

there's no script that respects those settings, where did you get them from?

the chksetuid script in 13.2 processes all zfs and ufs filesystems that have neither noexec nor nosuid set

the trick is to set nosuid on all data filesystems

I copied them from another 13.2 server, hmm, maybe I am going cuckoo

/etc/periodic/security/100.chksetuid is the script in question

the only option it recognizes is one to disable it completely

so for zfs I just setuid=off on the zfs pool ?

you do whatever it takes to make it show up as "nosuid" in the output of mount

I believe it's a dataset property

(rather than a pool one)

backups on /backups (zfs, local, nosuid, nfsv4acls)

cool

I heard you like backups so we put backups on /backups.

indeed!

would setting nosuid on the dataset change the snapshots somehow ?

I tried doing a zfs send/receive and now it errors out with: cannot receive incremental stream: destination backups/veeam has been modified

is there a way i could get the original sshd_config thats supposed to shop with my ssh version?

I replaced it, and that broke sftp, because I may have used a config from a different system :s

ah found the problem

it was from a bsd where I installed another openssh in /usr/local... so the sftp subsystem pointed to /usr/local/libexec instead of /usr/libexec

if you know your freebsd version you can get the sshd_config from the original sources easily enough.

you can get any original config file by downloading and extracting base.txz for that version

yeah, if you don't mind downloading a large file

Title: freebsd-src/sshd_config at releng/13.2 · freebsd/freebsd-src · GitHub

<3

I have a few hosts running 13.2 that are periodically dumping this message to the console: Deprecated code (to be removed in FreeBSD 14): Asymmetric crypto features via /dev/crypto

But they don't mention what the calling program or jail is. How to track this down?

spork_css: aye, that doesn't seem very useful

spork_css: can you use dtrace to see what opens /dev/crypto ?

i have no idea if this is spectacularly explosive on a production system

spork_css: I'm guessing it is either 30e25f930445e1b76d16f3219b627b7b92aa2a42 or ecedef531b0c481f424513004db59c4e8943cf2b

and see reviews.freebsd.org/D26810 for more info on the latter

Title: ⚙ D26810 Mark asymmetric cryptography via OCF deprecated for 14.0.

and reviews.freebsd.org/D24346 also

Title: ⚙ D24346 Remove support for the algorithms deprecated in r348876.

spork_css: so basically you need to figure out what's trying algos like 3DES, blowfish, etc.

probably something that also wants openssl < 1.1.0

I have some very old jails, including one on 8.4 (not on the internet)... might have to move that to bhyve if that's it.

i forgot, what are good ways to change the terminals (plain/pure/non-X) to black on white text, temporarily, and also saving that setting?