Hello guys,
I try to setup an openbgpd setup involving multipath configuration ...with no
success.
My bgpd.conf is like that
prefix-set privnetworks {
10.55.0.0/16
On Tue, May 14, 2024 at 05:19:43AM -0300, Crystal Kolipe wrote:
> On Sun, May 12, 2024 at 10:26:55PM +0200, Tomasz Rola wrote:
> > I am sure gdb has some merits but for whatever C programs I wrote so
> > far, a much more useful debugging technique was putting printf in
> > right places and isolate
On May 14 12:24:28, romand...@gmail.com wrote:
> If someone had spare capacity, (say, in their homelab, ~80% available,
> about same amount 10k/mon would buy in AWS spot instances), and wanted to
> share it with the open source community in general and OpenBSD devs in
> particular, and were
I'm not a coder; but I found source for viomb; which calls uvm_pglistalloc;
which calls uvm_pmr_getpages which mentions ENOMEM:
https://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/uvm/uvm_pmemrange.c?rev=1.66=text/plain
There I found this comment:
* fail if any of these conditions is
On Tue, May 14, 2024 at 01:54:52AM +0200, Peter J. Philipp wrote:
> Hi,
>
> A few more people responded, I'm falling behind on priorities though because
Hi again,
https://mainrechner.de/Buecher2024/batch1.png
Here is the first batch that will be mailed out on Friday at the latest. I
still
Hi Philip,
On Tue May 14 19:40:04 2024 Philip Guenther wrote:
> If you like, you could try the following patch to pax to more gracefully
> handle filesystems with time resolution more granular than nanoseconds.
After applying your patch, as I'd done before reporting the issue, I
sycronized my
On Tue, May 14, 2024 at 01:58:18PM -0400, F Bax wrote:
> Recently installed 7.5 amd64 in qemu VM (8G RAM) under proxmox. See this
> message many times on console and dmesg.
>
> viomb0 unable to allocate 256 physmem pages, error 12
>
> What does this mean? How to resolve this issue?
Hi,
When
Recently installed 7.5 amd64 in qemu VM (8G RAM) under proxmox. See this
message many times on console and dmesg.
viomb0 unable to allocate 256 physmem pages, error 12
What does this mean? How to resolve this issue?
If you like, you could try the following patch to pax to more gracefully
handle filesystems with time resolution more granular than nanoseconds.
The whitespace will presumably be mauled by gmail so use patch's -l option.
Philip Guenther
Index: ar_subs.c
If someone had spare capacity, (say, in their homelab, ~80% available,
about same amount 10k/mon would buy in AWS spot instances), and wanted to
share it with the open source community in general and OpenBSD devs in
particular, and were willing to do some ops and eat the electricity bill,
how
On Tue May 14 18:11:16 2024 Страхиња Радић wrote:
> Antipatterns are bad. I don't mean the ellipsis in `ls -l ...`. I mean
> things like
>
> cat file | grep hello | cat | sed 's/hello/world/g' | cat - > output
>
> for file in `echo `ls *` `; do echo $file; done
>
> ls -l | awk '{ print $5
Дана 24/05/14 11:52AM, Walter Alejandro Iglesias написа:
> I learned about the convenience of adding the '-r' option in the "while
> read" loop many years ago when I was writing a script to convert roff to
> html, the problem aroused with the backslash in roff comments (.\").
That's more or less
On Tue, May 14, 2024 at 05:19:43AM -0300, Crystal Kolipe wrote:
> On Sun, May 12, 2024 at 10:26:55PM +0200, Tomasz Rola wrote:
> > I am sure gdb has some merits but for whatever C programs I wrote so
> > far, a much more useful debugging technique was putting printf in
> > right places and isolate
On Tue May 14 11:40:42 2024 Tomasz Rola wrote:
> I am sure gdb has some merits but for whatever C programs I wrote so
> far, a much more useful debugging technique was putting printf in
> right places and isolate the problem,
I got used to doing this too. I started doing it intuitively, I'm
On Tue May 14 11:11:33 2024 wrote:
> When `while ... read ...` idiom is used, it is advisable to clear IFS
> to turn off field splitting, and use -r to avoid interpretation of
> backslash sequences in the input:
>
> while IFS= read -r dir; do # ...
>
> Back to parsing the output of ls(1)
On Sun, May 12, 2024 at 10:26:55PM +0200, Tomasz Rola wrote:
> I am sure gdb has some merits but for whatever C programs I wrote so
> far, a much more useful debugging technique was putting printf in
> right places and isolate the problem, and after that doing some mental
> work to actually
16 matches
Mail list logo
