Hi, I am running OpenBSD 7.5 and when I try to compile stuff this
happens:
jesse@openbsd ~/source/suckless/st % make
st build options:
Deep recursion on subroutine "main::handle_config" at /usr/bin/pkg-config line
331.
Deep recursion on subroutine "main::handle_config" at /usr/bin/pkg-config line
On Fri, Aug 30, 2024 at 05:22:50PM +, Anon Loli wrote:
> In my opinion, OpenBSD has lied to us, primarily that bad manual pages are
> considered as bugs.
I find it hard to believe that a bad or incorrect manual page could NOT
be considered a bug.
Imagine the financial and hardware/software di
On 9/15/24 9:42 AM, Rubén Llorente wrote:
I have a production site with lots of rules which look like:
location "/someplace/*.ext" { pass }
location "/someplace/something.ht*" { block }
I meant for more than one rule in the location block.
Based on your example, the following will not pass th
I have a production site with lots of rules which look like:
location "/someplace/*.ext" { pass }
location "/someplace/something.ht*" { block }
Paul Pace wrote:
I just discovered that location block rules in httpd.conf can only be on
separate lines. For example, the following does not pass th
I just discovered that location block rules in httpd.conf can only be on
separate lines. For example, the following does not pass the syntax test
(httpd -n):
location "foo" { block, no log }
But this passes:
location "foo" {
block
no log
}
However, server block rules can cont
Sorry it took so long to test.
That didn't work for me. So it must be something related to current vs
the gtk version.
John McCue writes:
> Hi
>
> I can get to https://lobste.rs/ on OpenBSD 7.5 without any
> issues.
>
> But I installed emacs-29.4-gtk2 instead of the gtk3 package.
> The gtk3 pa
Jonathan Thornburg wrote:
And a related question: I have a pool of ~10 external USB3 backup
disks (all consumer-grade WD or Seagate 2.5" spinning rust, either
2TB or 4TB capacity each), all currently setup with FFS2 filesystems
on top of softraid crypto (/bioctl -c C/). Each backup is to a si
Hi,
On Sun, Sep 15, 2024 at 12:12:08AM -0700, Jonathan Thornburg wrote:
> Thinking about how to detect/correct bit-rot in these backups, it
> occurs to me that I could hack up some Perl to walk the filesystem
> tree on a mounted backup disk, /stat()/ and read each file, and build
> a database of (
On 2024-09-15, Jonathan Thornburg wrote:
> Does OpenBSD support any file systems with built-in checksums to
> (try to) ensure metadata and/or data integrity in the face of "bit rot"
> disk (or memory/cpu/USB) errors?
No.
On 2024-09-15, Kirill A Korinsky wrote:
> On Sun, 15 Sep 2024 09:12:08
On Sun, 15 Sep 2024 09:12:08 +0200,
Jonathan Thornburg wrote:
>
> But before I reinvent the wheel, can anyone point me to software
> which already does this? Bonus points if the software is already
> in ports.
>
yabitrot?
--
wbr, Kirill
Hello,
I'm still with ugen locked down to disable bluetooth and my wireless card is
apparently unsupported. Indeed I live with securelevel=2.
Time to time I find myself to be in the situation where I boot network
disconnected, and on demand, when I need to upload to my server, I connect my
cab
On Sun, Sep 15, 2024 at 12:22 AM Jonathan Thornburg
wrote:
>
> Does OpenBSD support any file systems with built-in checksums to
> (try to) ensure metadata and/or data integrity in the face of "bit rot"
> disk (or memory/cpu/USB) errors? I'm not looking for ZFS-style storage
> pools or logical vol
Does OpenBSD support any file systems with built-in checksums to
(try to) ensure metadata and/or data integrity in the face of "bit rot"
disk (or memory/cpu/USB) errors? I'm not looking for ZFS-style storage
pools or logical volume management, "just" checksums to catch silent
metadata and/or data
13 matches
Mail list logo
