Kia ora koutou katoa,
On Tue, 2024-03-05 at 11:19 +0100, Havard Eidnes wrote:
>
> Secondly: is it something particular we are doing on the NetBSD
> end of things which contributes to this problem? Doesn't other
> OSes return ENOBUFS if syslogd isn't able to keep up by consuming
> the messages
On Sat, 2024-01-27 at 16:17 -0800, Chris Hanson wrote:
> It looks like there are CVS commits that haven’t made it to the
> GitHub mirror yet.
>
> Anyone know what’s up with that?
>
> -- Chris
>
The Mercurial mirror also hasn't been updated for a week.
Ngā mihi,
Lloyd
Kia ora koutou katoa,
On Wed, 2024-01-24 at 22:13 +0100, Rhialto wrote:
> T..
> he CHANGES file from upstream
> https://git.savannah.gnu.org/git/grep.git
> lists:
>
> ...
>
> related to commit 70e236167c3973fc428d2b5b297218fde9b68e73, committed
> 2010-03-17
And the source browser is at.
Kia ora,
In one out of one samples I checked, the result of mktemp was only
checked for != NULL rather than a more robust check. That same sample
(xsrc/external/mit/smproxy/dist/save.c) also preferred to use mkstemp.
mktemp() got removed from POSIX because using it is just wrong. Given
how much
Maybe rebuild Postfix with the option -DSSL_SECOP_PEER ? That causes
Postfix to always set security level 0 when using TLS.
Cheers,
Lloyd
On 14/11/23 10:56, Joerg Sonnenberger wrote:
NIST has been sunsetting SHA1 for a long time, 2016 in fact. In many cases,
there is a better trust chain
for Comodo intermediary certificates and admins should be installing those.
I'm not sure that's what Comodo has, even though it is the
On 20/10/23 00:32, Roy Marples wrote:
I've just landed dhcpcd-10.0.4 into -current and pkgsrc which fixes this issue.
Sorry for the delay.
Let me know if it works for you!
Thanks. I'll give it a go as soon as the change makes it into
anonhg.netbsd.org, which might take a day or two.
On 19/10/23 02:12, Greg Troxel wrote:
I realize this could be a vast number of things, flaky power, bad power
supply, bad RAM, but it feels correlated with updating. I think this
updated included a zfs actually-return-memory fix (which is very welcome
but epsilon scary).
Is anyone else
On 8/10/23 15:30, Lloyd Parkes wrote:
I added some debugging to /libexec/dhcpcd-run-hooks and things started
working ... better.
I created an empty file called /var/log/debug and added "exec >>
/var/log/debug 2>&1" to the top of /libexec/dhcpcd-run-hooks.
With t
On 8/10/23 14:54, Lloyd Parkes wrote:
That was all with dhcpcd 10.0.3. I'll try and look into the source code
and see why the reason field might make a difference. It could just be
something causing trouble in the early boot and the reason is just a
coincidence.
I added some debugging
On 7/10/23 05:01, Roy Marples wrote:
So it took 12 seconds to complete the DHCP transaction and validate the
addresses are good before applying the DHCP lease.
Without -B, dhcpcd will fork to the background right away so any assignments
from the DHCP lease won't apply right away.
Is this
Hi all,
I've installed 10.99.9 from about a day ago onto an old Raspberry Pi and
I just can't get it to correctly set its hostname from DHCP. (I have
removed the hostname=rpi from /etc/rc.conf).
What I have discovered so far is that if I manually run "dhcpcd -d" then
no hostname gets set. If
On 18/09/23 04:15, Benny Siegert wrote:
Hi!
I tried to build NetBSD-current from source on a Macbook Air M2. However, the
tools build fails because gcc cannot find zstd while linking. My command line
was:
% ./build.sh -j 6 -N 1 -U -O ../obj -m evbarm -a aarch64 release
Any ideas?
Maybe
On 4/09/23 08:47, Taylor R Campbell wrote:
We're preparing to ship TLS trust anchors in base and configure them
so that applications like ftp(1) and pkg_add(1) can do TLS validation
out of the box.
Nice.
I will have to wait until after the repository conversion systems come
back online.
PPPoE is a point to point protocol and the public IP addresses
114.23.17.255 and 114.23.164.222 are normal IP addresses. 114.23.164.222
is my local IP address and 114.23.17.255 is my ISP's IP address. Both
can be treated as /32.
AFAICT the important fact is that the route to 114.23.164.222
On 31/07/23 02:18, logothesia wrote:
Hi folks,
I have a very simple WG network with only two machines: 10.0.0.1 (NetBSD), and
10.0.0.2 (linux). Indeed they can ping each other just fine, but attempting to
ping 10.0.0.1 from itself yields the following error:
% ping 10.0.0.1
PING 10.0.0.1
On 9/07/23 10:06, David Brownlee wrote:
What would be a good benchmark to stress the system a little?
A while back someone mentioned pkgsrc/benchmarks/glmark2 and so I
started using that. It seems reasonable.
Cheers,
Lloyd
On Tue, 2023-06-06 at 19:54 +0200, Sagar Acharya wrote:
> I'm using current httpd server shipped with NetBSD to host my website
> at link below. It is awesome. I am shocked as to how complicated
> server hosting is made by commercial companies!
The NetBSD is very minimal and it is missing many
You can use "userconf" commands from the boot prompt to disable
auto-detection of problematic devices. You should be able to interrupt
the boot and disable ugen0 with the command "userconf disable ugen*".
You can also put that command into boot.cfg so that you don't have to
interrupt the boot
The manual page for httpd says that certificate needs to be in PEM
format and that -I changes the port number. Perhaps using -Z to specify
the certificate changes default port for you, perhaps it doesn't you'll
have to experiment.
On 29/05/23 03:55, Sagar Acharya wrote:
Dear folks,
I tried
And now it works fine.
The only change I made was to update my build host to the latest
10_BETA. I had already updated the base and comp sets on that host
before I sent my first email because it smelled like tool(chain) confusion.
Thanks for the advice even though I didn't end up needing it.
Hi all,
I recently started trying to build 10_BETA for some of my non-amd64
platforms using my 10_BETA amd64 build hosts and it just won't work.
It looks like something is going wrong with the host tools and they are
trying to use host includes when they should be using in-tree includes.
One
On 20/04/23 10:34, Brook Milligan wrote:
I am trying to build an old kernel with build.sh on a recent (9.99.108) amd64
system. However, compiling nbmake fails immediately with errors like
/usr/bin/ld: buf.o:(.bss+0x0): multiple definition of `debug_file';
arch.o:(.bss+0x0): first
On 5/04/23 18:00, matthew green wrote:
ps see "man 7 entropy" for how to fix the problem you observed.
FWIW I have PR 57254 in Gnats that provides a patch to /etc/rc.d/entropy
so that whenever the system boots with insufficient entropy appropriate
messages are logged. It doesn't change
On 22/03/23 03:45, Stephen Borrill wrote:
On Sat, 18 Mar 2023, Lloyd Parkes wrote:
On 18/03/23 05:14, Stephen Borrill wrote:
On an HP Microserver Gen10 Plus, I found that soon after booting, I
get the following alert:
...
Current CritMax WarnMax WarnMin CritMin
On 18/03/23 05:14, Stephen Borrill wrote:
On an HP Microserver Gen10 Plus, I found that soon after booting, I get
the following alert:
...
Current CritMax WarnMax WarnMin CritMin Unit
[ipmi0]
11-LOM-CORE: 59.253 0.000 110.471 degC
Oh, it's used to pass the compression level though pax to gzip. That's
explain it. Maybe we should switch to --use-compress-program="nbgzip
-LEVEL"???
Cheers
On 16/02/23 06:28, Martin Husemann wrote:
On Thu, Feb 16, 2023 at 06:18:54AM +1300, Lloyd Parkes wrote:
I saw this to
I saw this too. I think the way we select the gzip compression level
(using the GZIP environment variable) is now deprecated for some reason.
Cheers,
Lloyd
On 16/02/23 04:44, Martin Husemann wrote:
On Wed, Feb 15, 2023 at 03:09:37PM +0100, Christian Groessler wrote:
Hi,
probably known and
This could be a hardware issue and it could be a hardware issue that
Linux is "fixing" for you.
I have seen this exact broken behaviour before when connecting
headphones to a headset socket or vice versa. I can't remember which way
round it was.
It is entirely reasonable for modern OSes and
On 7/01/23 03:47, Mayuresh wrote:
On Thu, Jan 05, 2023 at 10:12:27AM +1300, Lloyd Parkes wrote:
2) For the the fact that the device appears to be getting attached to
sysmon_envsys(9) even though device configuration failed.
I filed for the other two, but did not find the word sysmon_envsys
On 4/01/23 23:32, Mayuresh wrote:
envstat hangs (doesn't come out with Ctrl-C) on a laptop with following
description:
# uname -a
NetBSD asusn 10.0_BETA NetBSD 10.0_BETA (GENERIC) #0: Mon Dec 19 14:00:35 UTC
2022 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
#
On 22/12/22 02:33, Mayuresh wrote:
On Wed, Dec 21, 2022 at 09:25:30AM +1300, Lloyd Parkes wrote:
I was installing on amd64 and the installer let me choose either MBR or GPT,
I notice a separate image marked "bios"
NetBSD-10.0_BETA-amd64-bios-install.img.gz
NetBSD-10.0_
Hi all,
It's been a while since I've run the NetBSD installer, so I don't now
how recent the changes I've seen are, but I do like them.
I was installing on amd64 and the installer let me choose either MBR or
GPT, which is nice. The NUC I was installing on is old enough that it
can only UEFI
On 6/12/22 22:35, Sagar Acharya wrote:
I installed package py310-pdf-parser . It should install module py_pdf_parser
as should be imported in python3.10.
It throws an error
No such module.
You should normally provide more details, such as where you got the
package from and a short
On 19/11/22 12:31, Brook Milligan wrote:
I am running a linux application (no source code unfortunately) and
encountering an error that seems from the message (which is cryptic) to be
related to a getrandom() function call. This is with a NetBSD/amd64 9.99.99
kernel dating from August.
I
Hi all,
I thought I ought to refresh the NetBSD running on my Xeons, but current
kernels panic during boot. This affects 9.99.105 and a bunch of earlier
versions, but I don't know how much earlier.
I finally found a serial cable that works with our boot loader so I now
have some console
I wrote a quick and dirty program to trigger vast amounts of File memory
usage only to remind myself of something important.
Having File memory use all available RAM with only scraps left is not a
problem by itself. The memory is there to be used and it is getting
used. I used to have to
You aren't the first person to have problems with memory pressure. We
really are going to have to get around to documenting the memory
management algorithms and all the tuning knobs.
I used to use this page (https://imil.net/NetBSD/mirror/vm_tune.html),
but I have no idea how current it is.
On 3/09/22 22:40, Joerg Sonnenberger wrote:
On Sat, Sep 03, 2022 at 10:00:04AM +1200, Lloyd Parkes wrote:
Does anyone know of a maintained DHCP relay implementation?
The better question for me is: are DHCP relayer server still in use?
DHCP relays are used a lot, but the ISC one probably
Hi all,
Are there any plans to switch the DHCP server we have to the new Kea one
from ISC? The relay that comes with it dumps core when relaying DHCP
responses.
I've fixed my copy of dhcrelay, but when I went to send the patch
upstream, I saw this
Please note that this project is
It might not be ZFS related. But it could be.
Someone else reported excessive, ongoing, increasing "File" usage a
while back and I was somewhat dismissive because they were running a
truckload of apps at the same time (not in VMs).
I did manage to reproduce his problem on an empty non-ZFS
I have seen some somewhat official recommendations from HPE to leave
such controllers in RAID mode and to then create an individual RAID 0
target for each disk.
It seems more complicated than is needed, but it's what they said to do
and it did seem to work.
Cheers
On 13/08/22 19:35,
On 10/07/22 14:59, Robert Elz wrote:
Fixing these things is a noble goal, but breaking the buikd to
make that happen is not.
I didn't envision breaking the build, but I also have to admit that I
didn't envision how this wouldn't break the build either.
Maybe a new build.sh operation?
On 10/07/22 00:55, Roland Illig wrote:
Shouldn't there be an automatic check for these? Running this check
after a "make distribution" should be fairly easy.
That sounds like an excellent idea to me.
Fixing the problems will be much harder than finding them, but there is
no good excuse
On 8/07/22 21:01, RVP wrote:
On Fri, 8 Jul 2022, br0nko wrote:
8 partitions:
# size offset fstype [fsize bsize cpg/sgs]
a: 2369473 63 4.2BSD 0 0 0 # (Cyl.
0*- 1156)
c: 2312129 63 unused 0 0 # (Cyl.
0*-
On 8/07/22 19:57, br0nko wrote:
On Thursday, July 7th, 2022 at 11:25 PM, Mike Pumford
wrote:
On 07/07/2022 15:40, br0nko wrote:
Hi,
0: NetBSD (sysid 169)
start 63, size 1568384 (766 MB, Cyls 0/1/1-97/160/62), Active
beg: cylinder 0, head 1, sector 1
end: cylinder 97, head 160, sector
I keep forgetting this.
On 20/04/22 06:36, Brian Buhrow wrote:
...
Any ideas would be greatly appreciated.
You should be able to boot in single user mode and ask the kernel not to
configure the bge driver. You should be able to run userconf in single
user mode with "boot -sc" and
On 10/04/22 23:57, Martin Husemann wrote:
I think I have just fixed this...
I think you have as well.
Thanks,
Lloyd
On 9/04/22 23:25, Martin Husemann wrote:
First question is if the files exist in that install medium - can you
netboot into that netbsd-INSTALL.gz again, go to the shell and
check contents of /usr/mdec?
I did manage to find my way this far before getting distracted by a
slightly more
I installed NetBSD current from late March by net booting
netbsd-INSTALL.gz on and amd64 system of mine. The net boot and disk
boot were both done with UEFI and sysinst correctly offered to create
GPT filesystems for me.
Even though the FAT system partition was created correctly, bootx64.efi
On 25/01/22 17:57, Greg A. Woods wrote:
I have fixes that restore the previous option to use "untrusted"
hardware as an entropy source. They may need some updating to be truly
complete in the most recent -current, as I'm still back at 9.99.81.
The change was more subtle than that I think.
Hi Tom,
On 25/10/21 14:01, Thomas Mueller wrote:
One of these bugs relates to entropy and how it impedes building many packages
in pkgsrc.
I seemed to get around this bug on one computer but not the other.
It's the old story that it's not a bug, but a feature. It's quite
possible that it
On 27/07/21 12:19 am, Paul Ripke wrote:
On Mon, Jul 26, 2021 at 05:53:19PM +1200, Lloyd Parkes wrote:
That's 12GB of RAM in use and 86MB of RAM free. Sounds pretty awful to me.
Sounds normal to me - I don't expect to see any free RAM unless I've just
- exited a large process
- deleted
It has been a very long time since I had to look at UVM stuff, but
luckily past me post to
https://mail-index.netbsd.org/tech-repository/2010/02/01/msg000364.html.
Well done past me.
Copying from that post, I was using
vm.anonmin = 10
vm.filemin = 5
vm.execmin = 5
vm.anonmax = 90
On 30/05/21 8:55 am, Rhialto wrote:
Another thing I noticed is that /etc/rc.d/resize_disklabel looks at the
wrong MBR partition to check for NetBSD: it looks at partition 1 but
should look at partition 0.
resize_disklabel is designed for use on the Raspberry Pi where the
NetBSD partition
On 30/04/21 9:50 pm, Joerg Sonnenberger wrote:
On Fri, Apr 30, 2021 at 05:31:53PM +1200, Lloyd Parkes wrote:
ceph4% hg --version
Mercurial Distributed SCM (version 5.3.2)
Please note that this is quite an old version and a lot of work on
improving both CPU time and memory use has
On 30/04/21 8:36 pm, Hauke Fath wrote:
Out of curiosity: Do you use a ZIL SLOG* volume with that setup? I
remember cvs operations used to be a lot slower on spinning rust than
on SSD.
I'm not using a SLOG. I couldn't be bothered setting one up on my crash
and burn systems. It doesn't seem
Hi all,
The problem reports people have in their emails are completely
inadequate for trying to determine what is going wrong for people trying
to access the NetBSD source.
Since I was the first person to post an inadequate report in this first
batch, I'll go first at trying to do better.
On 19/04/21 10:21 am, Lloyd Parkes wrote:
On 17/04/21 6:30 pm, Lloyd Parkes wrote:
I am using the Mercurial repository at https://anonhg.NetBSD.org/src
for fetching the source code because it's nice and quick
So I'm now downloading the source code through CVS instead of
Mercurial because
On 17/04/21 6:30 pm, Lloyd Parkes wrote:
I am using the Mercurial repository at https://anonhg.NetBSD.org/src
for fetching the source code because it's nice and quick
So I'm now downloading the source code through CVS instead of Mercurial
because nobody else seems to be having the same
On 15/04/21 2:19 pm, matthew green wrote:
the steps are fairly simple:
- update -currnet srcs
- build.sh with no -u (update), and set -V HAVE-GCC=10 as a
option. this ensures that everything is actually rebuilt
with the new compiler.
I'm guessing that should be "-V HAVE_GCC=10", but
With some trepidation, I'm going to dip into this conversation even
though I haven't read all of. I don't have the mental fortitude for
that. I have two suggestions, one short and one long.
Firstly, we could just have an rc.d script that checks to see if the
system has /var/db/entropy-file
On 20/03/21 3:41 pm, Lloyd Parkes wrote:
I also tried my Intel based laptop, but I only had an MBR image and HP
seemed to have removed the old BIOS boot option in their newer
firmware so I couldn't even boot the image.
I just tried the 9.1 image on my ASUS UX550V laptop and it did load
HI all,
On 18/03/21 10:03 am, Rhialto wrote:
For example, if I look at an "AMD Ryzen 3" cpu, which supposedly has
integrated graphics "AMD Radeon Vega 8, integrated GPU". Grepping -i for
"Vega" in src/sys/external/bsd/drm2/dist/drm yields no results; I take
it this is a bad sign?
I booted a
On 2/03/21 6:51 am, Riccardo Mottola wrote:
I thouht your cited entropy fix was a "once time" not to be reissued
again (when? at every reboot? kernel update?)
I don't think it is that user friendly to recularly "feed" this
entropy... and it gets lost at the next reboot? Could we have a script
On 28/02/21 9:50 am, Riccardo Mottola wrote:
python38 hangs during build. I tried several times, it hangs in
exactly the same place again. I don't know of course where the issue
comes from, since all is new now :)
Do you have any console messages? Maybe messages about blocking the
python
This is all off the top of my head and while I use ZFS almost daily, not
on NetBSD :-(, it's been a few years since I poked at the internals.
Your action of creating a symlink seems like a reasonable
workaround/solution to your issue. You should be able to create the
symlink in any directory
> On 29/12/2016, at 10:39 AM, Brian Buhrow wrote:
>
> hello. thanks for the feedback. The earlier post about looking at
> the mtree source code gave a clue about what to do. The build is running
> as root and not in a chrooted environment. So, mtree is doing lookups
Hi Brian,
Can you provide the snippet of the log from a build with -N 2 that shows the
command line for nbmakefs? If you have trouble coming up with a log small
enough for you to feel comfortable cross-posting, feel free to email it to me
directly, or use something like pastebin.
nbmakefs
> On 16/08/2016, at 7:41 PM, matthew green wrote:
>
>> I've been trying to find when this breakage occurred,
>
> it happened when your port switched to GCC 5. sorry :-)
Yeah. While looking for the “backend” directory I saw gcc.old and gcc. A quick
look showed me they
> On 12/08/2016, at 3:34 AM, Thor Lancelot Simon wrote:
>
> It's curious that this doesn't break the tools build, and doesn't
> prevent using the built tools to build a kernel! If this can break
> the cross-build of the target compiler, I think we must have suddenly
> sprouted
71 matches
Mail list logo