hrm

hardware raid does what it says, raid0,1,5, 10, 50..whatever..but they dont CRC the data like zfs does. and there was raid5 write hole,

battery backups / ups foobar

A system crash or other interruption of a write operation can result in states where the parity is inconsistent with the data due to non-atomicity of the write process, such that the parity cannot be used for recovery in the case of a disk failure. This is commonly termed the write hole which is a known data corruption issue in older and low-end RAIDs, caused by interrupted destaging of writes to disk.

raid 1+0 or raid 10 is the money raid...you can have tons of failure..but still recover...you got money $$$$

hardware raid 10 rocks!

lose half the disk space for it

d=2N

d/2=N maxium number of disk failures

raid 10 disk(d) and (N)mirrored sets

the money raid!

hot spares in the array cabinet kick in

for the performance you waste half the disk space...

a stripe of mirrors

en.wikipedia.org/wiki/Nested_RAID_levels heh

According to manufacturer specifications and official independent benchmarks, in most cases RAID 10[8] provides better throughput and latency than all other RAID levels[9] except RAID 0 (which wins in throughput).[10]

some of those links are dead

internet of shit...

seagate use to have better page explaining this stupid

Greetings,

EHLO

rtprio: this is not #smtp :D

sorry, i wasn't "extending a hello" to you

So... lots of talk about PQR and Kyber being adopted by NIST... liboqs (which is ported: freshports.org/security/liboqs) contains the implementation, however does anyone yet use PQR on FreeBSD?

with the small number of supported clients I doubt it is much of a deal not adopting it yet... but I heard it overwrites the global openssl alorithms to force use of kyber system-wide thus I have been told it doesn't need to be explicitly supported by any server/client?

hi, could you explain how this sh line is processed? if ping -q -c 1 -t 1 "$1"; then echo 'success'

does "if <command>" succeed when command exits with 0?

correct

okay. damn. well, it's hour 40+ of me chasing that dhclient issue

it's turning out that what I assumed was a bug, was in fact a fix that unintentionally repaired other, bugged functionality, to what it was meant to be doing in the first place

that is, if you take a freebsd pc that has a saved dhcp lease, connect it to a network, boot it up, and it doesn't get a DHCPOFFER response, then before it reuses the saved lease, it does a primitive sanity check by pinging the saved router/gateway.

until 12.1 this sanity check was being ignored due to a quirk in dhclient's programming. though also add_new_routes() and add_new_resolv_conf() wasn't being called.

now my router isn't binding to its saved lease anymore after a power outage, because the ISP's infrastructure takes 10 minutes to restart

note that the sanity check is not perfect, because if the pc is transported to a new location that uses the same subnet but doesn't use dhcp, it will happily bind and possibly cause an ip conflict

Why on are arrow keys not working in vi via putty?

most likely the TERM? try with something simple, that works everywhere, like vt100

It's just putty on this one laptop though. . . and strangely, it works fine in vim.

if you think, it's putty:s fault, compare the configuration from your working setup. maybe the term-emulation there is different? other escape-sequences sent for cursor? ...

or it's just vi being vi? does ':set compatible' make vim behave the same?

yuripv, no. . . vim still works with compatible set.

CrtxReavr: Are you using the arrows in command mode, or insert mode?

Both.

Well, insert & navigation mode.

I interpret "command mode" is after hitting :

CrtxReavr: Command mode is after hitting <esc>

Insert mode is when you hit 'a', 'i', or 'o'

I've been using vi for like three decades. . . don't really need your lecture.

The reason why I asked was that I wasn't sure if FreeBSD's vi implementation even supported arrow keys in insert mode, but I just gave it a try and it did, which had honestly surprised me

It does.. . always has, since at least 3.0

FreeBSD's vi is nvi.

5

that's why I install nvim on my machines

at least this one's got consistent behaviour for the same name

I have an ongoing battle with p5-DBD-MariaDB, there's a package conflict... who do I annoy to get it looked at?

I want MariaDB client and server, but it always wants to delete those packages and install the MySQL ones instead

mmlj4, what's the error?

^^^

I was usually able to compile the port directly, but it still want to pull in the MySQL client, and now it won't even compile all of the dependencies

check this post, maybe it helps about upgrading, also it event talks about MySQL. forums.freebsd.org/threads/why-does…packages-and-how-to-keep-them.90298

the fatal error was when trying to install cmake (something that wasn't even attempted before, it just dutifilly just made and installed just the one package

I'll look, thanks

well, I don't have an upgrade problem, so that's not it

Hecate: the one thing I don't like about vim and nvim is the default behavior of the P (prepend before) command, where in nvi the cursor stays on the same screen column, but in vim and nvim, it moves onto the end of the inserted text. Thankfully that can be resolved with a remap: nnoremap P P`[

there's a thread on p5-DBD-MariaDB,: bugs.freebsd.org/bugzilla/show_bug.cgi?id=277889

Dooshki: I have to admit I never use P :)

when using ports, after I make and/or make install, where does it store the package it created? or is there a flag I have to pass to get make to actually store the package file?

make package

pkg cache is stored in /var/cache/pkg/

there is also pkg-create(8)

oh. thanks.