On 2020-11-27 16:03, Karel Gardas wrote:
,,,
> To me this looks like too much pray for luck. With such amount of data,
> I would stay with ZFS...
I've heard that from a lot of people.
And yet, those same people, when pressed, will tell you that a ZFS-equipped
system will crash much more often
Hi,
Jason Tubnor(ja...@tubnor.net) on 2020.11.25 15:52:19 +1100:
> Hi,
>
> We are planning for migration from ripd to ospf, however both protocols
> will need to work together as the migration rolls through.
>
> I was looking at the 'redistribute rtlabel' option, even after digging into
> the
On Fri, 27 Nov 2020 15:14:18 - (UTC)
Stuart Henderson wrote:
> On 2020-11-27, Duncan Patton a Campbell wrote:
> >
> > If I have a config file that looks like this
> >
> > chroot "/var/www"
> >
> > # $OpenBSD: httpd.conf,v 1.20 2018/06/13 15:08:24 reyk Exp $
> >
> > server "default"
> > {
Nice experiment, but I hope you don't do that in production nor
somewhere where data integrity is needed.
Your SAS drives, what does their maker claim about "nonrecoverable read
errors per bits read" for example?
As an example let's look on 6TB seagate, 10^15 read bits per one
On Wed, Nov 25, 2020 at 10:10:03PM -, Stuart Henderson wrote:
> > It's not right. Use pkg_delete -cX first. There are package files in
> > many other places that need to go away.
>
> Be very careful with -c! It may remove configuration files that you
> actually want to keep.
>
You're right.
Gack, what a way to screw up my day off. :-)
I never thought anyone would refer to DISA STIGs in this mailing list.
On Fri, Nov 27, 2020 at 8:12 AM Ed Ahlsen-Girard wrote:
>
SNIP
> I can verify that there is no US Defense Information Systems Agency
> (DISA) Security Technical Implementation
Nils Blomqvist wrote:
> I need a PCI card with USB 3 ports. Something like this is what I
> had in mind: https://amzn.to/2V8NgtT (SEDNA - PCI Express USB 3.1).
>
> Can anyone point me in the right direction for finding out if a
> particular card is supported, or a list of supported ones?
All
There is nothing in the manual page which suggests you can put
newlines in those positions.
Duncan Patton a Campbell wrote:
>
>
> If I have a config file that looks like this
>
> chroot "/var/www"
>
> # $OpenBSD: httpd.conf,v 1.20 2018/06/13 15:08:24 reyk Exp $
>
> server "default"
> {
I need a PCI card with USB 3 ports. Something like this is what I
had in mind: https://amzn.to/2V8NgtT (SEDNA - PCI Express USB 3.1).
Can anyone point me in the right direction for finding out if a
particular card is supported, or a list of supported ones?
On 2020-11-27, Duncan Patton a Campbell wrote:
>
> If I have a config file that looks like this
>
> chroot "/var/www"
>
> # $OpenBSD: httpd.conf,v 1.20 2018/06/13 15:08:24 reyk Exp $
>
> server "default"
> {
> If anyone has some idea about the syntax of this setup I'd really like to
> hear
On Wed, 25 Nov 2020 23:33:34 +0100
Peter Nicolai Mathias Hansteen wrote:
(snip)
> I am not aware of any publicly available set of documents that
> provide the direct checkoffs for OpenBSD with respect to specific
> compliance regimes, but I’m fairly certain that you will find useful
> answers by
On Thu, 26 Nov 2020 11:35:45 -0500
Nick Holland wrote:
> On 2020-11-25 17:10, Brogan Beard wrote:
> [...]
>
> Something to consider: run the AV against your boxes -- elsewhere!
>
> I have a similar situation at $DAYJOB. Not OpenBSD, but an OS that
> similarly has little malware written for
If I have a config file that looks like this
chroot "/var/www"
# $OpenBSD: httpd.conf,v 1.20 2018/06/13 15:08:24 reyk Exp $
server "default"
{
listen on * tls port 443
tls
{
certificate
"/etc/letsencrypt/live/babayaga.neotext.ca/fullchain.pem"
27.11.2020 13:04, kasak пишет:
27.11.2020 12:58, Zé Loff пишет:
On Fri, Nov 27, 2020 at 12:05:49PM +0300, kasak wrote:
Mine configuration requires to use a brigde:
I have files:
cat /etc/hostname.bridge0
add vether0
add em1
add tap1
up
files hostname.em1 and tap1 just contain "up"
and
Den fre 27 nov. 2020 kl 10:08 skrev kasak :
> Mine configuration requires to use a brigde:
> I have files:
>
> gater:~$ doas pfctl -sr
> block return all
> pass all flags S/SA
> block drop in on em0 all
> pass out on em0 inet from 172.16.0.0/12 to any flags S/SA nat-to
> 212.233.112.10
> pass
27.11.2020 12:58, Zé Loff пишет:
On Fri, Nov 27, 2020 at 12:05:49PM +0300, kasak wrote:
Mine configuration requires to use a brigde:
I have files:
cat /etc/hostname.bridge0
add vether0
add em1
add tap1
up
files hostname.em1 and tap1 just contain "up"
and file hostname.vether0 contain:
On Fri, Nov 27, 2020 at 12:05:49PM +0300, kasak wrote:
> Mine configuration requires to use a brigde:
>
> I have files:
>
> cat /etc/hostname.bridge0
> add vether0
> add em1
> add tap1
> up
>
> files hostname.em1 and tap1 just contain "up"
>
> and file hostname.vether0 contain:
>
> inet
Mine configuration requires to use a brigde:
I have files:
cat /etc/hostname.bridge0
add vether0
add em1
add tap1
up
files hostname.em1 and tap1 just contain "up"
and file hostname.vether0 contain:
inet 172.16.0.1 255.240.0.0 NONE description "LAN Link"
this is ifconfig:
em1: flags=8b43
Hi folks,
I got a bazillion of error messages in /var/log/daemon
:
Nov 27 08:33:25 gate6a pflogd[26893]: Corrupted log file.
Nov 27 08:33:25 gate6a pflogd[26893]: Invalid/incompatible log file, move it
away
Nov 27 08:33:25 gate6a pflogd[26893]: Logging suspended: open error
Nov 27 08:33:32
19 matches
Mail list logo
