Re: buildworld failure due to md5 not supported by openssl3

2023-11-24 Thread Ede Wolf
Am 24.11.23 um 18:53 schrieb Robert Elz: Date:Fri, 24 Nov 2023 17:21:42 +0100 From:Ede Wolf Message-ID: <5b8928a4-32b5-4015-8eb1-2432d3eb6...@nebelschwaden.de> | For what it is worth, as you have probably known it before, here my | confirmation: Sw

Re: buildworld failure due to md5 not supported by openssl3

2023-11-24 Thread Ede Wolf
Am 23.11.23 um 13:34 schrieb Robert Elz: Date:Thu, 23 Nov 2023 12:13:42 +0100 From:Ede Wolf Message-ID: <77602506-626c-4fff-90ec-48e2f4aaf...@nebelschwaden.de> | Ok, I did not see this as yet verified, because, as with MKKERBEROS=yes | and USE_KERBER

Re: buildworld failure due to md5 not supported by openssl3

2023-11-23 Thread Ede Wolf
So one thing to check is that while you didn't seem to be doing an update build, so everything should have been cleaned before it started, you might want to try making certain of that by manually cleaning it all (rm -fr on relevant directories) and trying again. It is possible that the change o

Re: buildworld failure due to md5 not supported by openssl3

2023-11-23 Thread Ede Wolf
Am 23.11.23 um 12:00 schrieb Martin Husemann: On Thu, Nov 23, 2023 at 11:58:08AM +0100, Ede Wolf wrote: Btw, this does not seem to be alpha-port specific. I've just tried to compile on amd64 for amd64, exactly the same mk.conf (with the obvious exception of CPUFLAGS) and of course changi

Re: buildworld failure due to md5 not supported by openssl3

2023-11-23 Thread Ede Wolf
Am 23.11.23 um 10:21 schrieb Ede Wolf: Am 22.11.23 um 17:00 schrieb Martin Husemann: On Wed, Nov 22, 2023 at 04:21:01PM +0100, Ede Wolf wrote: My build says somethig different about warnings and errors (Marking by me, of course): /data/src/crypto/external/bsd/libsaslc/lib/../dist/src

Re: buildworld failure due to md5 not supported by openssl3

2023-11-23 Thread Ede Wolf
Am 22.11.23 um 17:59 schrieb tlaro...@kergis.com: On Wed, Nov 22, 2023 at 04:21:01PM +0100, Ede Wolf wrote: [...] My mk.conf should be rather unspectacular as well: # cat /etc/mk.conf CPUFLAGS = -mcpu=21164a # world related stuff: NETBSDSRCDIR=/data/src BSDOBJDIR=/data/obj INSTALLWORLDDIR

Re: buildworld failure due to md5 not supported by openssl3

2023-11-23 Thread Ede Wolf
Am 22.11.23 um 17:49 schrieb Robert Elz: Date:Wed, 22 Nov 2023 16:21:01 +0100 From:Ede Wolf Message-ID: | # cat /etc/mk.conf | MKKERBEROS=no That one is the problem, the COPTS.crypto.c entry that Martin mentioned is not included if MKKERBEROS is &qu

Re: buildworld failure due to md5 not supported by openssl3

2023-11-23 Thread Ede Wolf
Am 22.11.23 um 17:00 schrieb Martin Husemann: On Wed, Nov 22, 2023 at 04:21:01PM +0100, Ede Wolf wrote: My build says somethig different about warnings and errors (Marking by me, of course): /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In function 'saslc__crypto_md

Re: buildworld failure due to md5 not supported by openssl3

2023-11-22 Thread Ede Wolf
Am 22.11.23 um 12:25 schrieb Martin Husemann: On Wed, Nov 22, 2023 at 12:00:10PM +0100, Ede Wolf wrote: Hello, just trying to crosscompile world, which fails with crypto not being able to be build, as MD5 is claimed to not be supported by openssl3. Is it just me or is anything known? cvs

buildworld failure due to md5 not supported by openssl3

2023-11-22 Thread Ede Wolf
Hello, just trying to crosscompile world, which fails with crypto not being able to be build, as MD5 is claimed to not be supported by openssl3. Is it just me or is anything known? cvs updated just an hour or so ago: /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In functio

Re: iscsid - lfs and ipv6 issues

2023-11-19 Thread Ede Wolf
Am 19.11.23 um 13:42 schrieb Ede Wolf: Secondly: The iscsi target is ctld on FreeBSD. Currently even without any authentication. Now I doubt that an offline reporting is the case, because, relabelling the lun to 4.2BSD and mounting it with ffs does work. Without anything else being done on

Re: iscsid - lfs and ipv6 issues

2023-11-19 Thread Ede Wolf
Am 19.11.23 um 13:23 schrieb Michael van Elst: On Sun, Nov 19, 2023 at 12:34:13PM +0100, Ede Wolf wrote: Hello, first of all a very big thanks to all of you. Since it seems I am the only one who is using ipv6 with iscsi, I do not need a fix. I can live (as I am doing now) with ipv4. I just

Re: iscsid - lfs and ipv6 issues

2023-11-19 Thread Ede Wolf
Am 17.11.23 um 23:22 schrieb Michael van Elst: lis...@nebelschwaden.de (Ede Wolf) writes: I am having two issues with iscsid/iscsictl. First, it seems, I cannot mount an lfs formatted iscsi lun, no matter wether this drive is gpt/wedge or plain disklabelled: # mount -t lfs /dev/dk0 /import

iscsid - lfs and ipv6 issues

2023-11-17 Thread Ede Wolf
Hello, I am having two issues with iscsid/iscsictl. First, it seems, I cannot mount an lfs formatted iscsi lun, no matter wether this drive is gpt/wedge or plain disklabelled: # mount -t lfs /dev/dk0 /import/ mount_lfs: /dev/dk0 on /import: Operation not supported by device Secondly, I am u

Re: disklabel: delete a partition?

2023-11-17 Thread Ede Wolf
Am 16.11.23 um 00:19 schrieb John D. Baker: When using 'disklabel' interactively ('disklabel -i ...'), assigning a partition a size of zero (0) deletes the partition. Thanks very much indeed. Took a while for me to being able to test this, as the box was building packages, but it works as well.

Re: disklabel: delete a partition?

2023-11-15 Thread Ede Wolf
Am 15.11.23 um 12:14 schrieb Ede Wolf: Hello, I have two partitions, sd0e and sd0f, that I would like to merge into a single, large partition, presumibly a larger sd0e. Both are empty. However, using disklabel, I am not able to find a way to delete both to recreate sd0e. Even, when

disklabel: delete a partition?

2023-11-15 Thread Ede Wolf
Hello, I have two partitions, sd0e and sd0f, that I would like to merge into a single, large partition, presumibly a larger sd0e. Both are empty. However, using disklabel, I am not able to find a way to delete both to recreate sd0e. Even, when setting sd0f as type "unsused", it asks for sta

Re: 10.0 ipv6 "autohost" behavior

2023-11-14 Thread Ede Wolf
Am 14.11.23 um 12:36 schrieb David Brownlee: On Tue, 14 Nov 2023 at 01:19, vom513 wrote: Hello all, So back a while I had tried out a 10.0 snapshot (before the recent RC1). I noticed that IPv6 didn’t work as it had been for me on 9.3 for example. I was going to post a message/question but

builing world: fts_open failed: No such file or directory

2023-11-14 Thread Ede Wolf
Disclaimer: This is on alpha, but since I am somwhat confident, this is an user error, not a port issue, I've went here. After successfully building and booting the new kernel, building world: time -p ./build.sh -r -O /data/work/obj distribution install=/ is failing, as fts_open cannot be foun

Re: 10.0 ipv6 "autohost" behavior

2023-11-14 Thread Ede Wolf
Am 14.11.23 um 02:19 schrieb vom513: Hello all, So back a while I had tried out a 10.0 snapshot (before the recent RC1). I noticed that IPv6 didn’t work as it had been for me on 9.3 for example. I was going to post a message/question but never got around it. After installing 10.0 RC1 on a s

Re: [cross]compiling world and mk.conf

2023-11-08 Thread Ede Wolf
Am 08.11.23 um 20:14 schrieb Valery Ushakov: On Wed, Nov 08, 2023 at 13:07:09 +0100, Martin Husemann wrote: Alternatively you can use conditionals in mk.conf, like: .if ${MACHINE} == "sparc" CFLAGS+= -mcpu=v8 -mtune=supersparc .endif *tsk tsk*... :) CPUFLAGS = -mcpu=v8 -mtune=... please

Re: [cross]compiling world and mk.conf

2023-11-08 Thread Ede Wolf
Am 08.11.23 um 13:20 schrieb Greg Troxel: Martin Husemann writes: Alternatively you can use conditionals in mk.conf, like: .if ${MACHINE} == "sparc" CFLAGS+= -mcpu=v8 -mtune=supersparc .endif or .if ${MACHINE_ARCH} != shark MKKDEBUG=yes .endif I would strongly recommend the .if method an

[cross]compiling world and mk.conf

2023-11-08 Thread Ede Wolf
Hello, I am heading for my first cross compile, but reading chapter 33 or man make/release, I am having one principal problem of understanding: Of course, if I have a central machine to cross compile for different hosts, I am having a different mk.conf for each remote host or host group/arch

Re: sysupgrade issues - missing netbsd-ARU_MBOX_OWNER

2023-09-11 Thread Ede Wolf
Am 11.09.23 um 20:44 schrieb Rhialto: On Mon 11 Sep 2023 at 19:36:13 +0200, Ede Wolf wrote: Now, why sysupgrade needs that [weird kernel] package, is most likely part of my question, I remember using sysupgrade once in the past and needing to persuade it to use the right kernel version, or

Re: sysupgrade issues - missing netbsd-ARU_MBOX_OWNER

2023-09-11 Thread Ede Wolf
Am 11.09.23 um 19:04 schrieb Martin Husemann: On Mon, Sep 11, 2023 at 06:54:36PM +0200, Ede Wolf wrote: Hello, not sure, wether this is the proper list, but I am having a cubietruck, that hasn't seen much love lately, and while trying to fix this with an upgrade, I am running into pro

sysupgrade issues - missing netbsd-ARU_MBOX_OWNER

2023-09-11 Thread Ede Wolf
Hello, not sure, wether this is the proper list, but I am having a cubietruck, that hasn't seen much love lately, and while trying to fix this with an upgrade, I am running into problems. sysupgrade fails, because an image it requests does not ecist. And checking the site, it really is not the

Re: route.conf and ip6 routes

2020-05-04 Thread Ede Wolf
Got it: inet6 -net Mißinterpreted the man page (dash as stdin instead of literal) Thanks Am 04.05.20 um 20:11 schrieb Ede Wolf: Hello, I am struggeling to find the correct syntax for specifying static routes in route.conf I've tried both: net fd7a:2452:12ef:17::/64 fd8a:94b1

route.conf and ip6 routes

2020-05-04 Thread Ede Wolf
Hello, I am struggeling to find the correct syntax for specifying static routes in route.conf I've tried both: net fd7a:2452:12ef:17::/64 fd8a:94b1:cb84:1:a254:99ff:fe72:5f43 and inet6 net fd7a:2452:12ef:17::/64 fd8a:94b1:cb84:1:a254:99ff:fe72:5f43 Neither works. What of course does work,

Re: sysctl.conf not read at boot time

2020-04-30 Thread Ede Wolf
hrieb ignat...@cs.uni-bonn.de: Hello, On Thu, Apr 30, 2020 at 05:37:18PM +0200, Ede Wolf wrote: So f.e. I've added: net.inet6.ip6.forwarding=1 to /etc/sysctl.conf But this does not get respected. [...] What am I missing? That variable is set by /etc/rc.d/networking depending on the va

sysctl.conf not read at boot time

2020-04-30 Thread Ede Wolf
Hello, feeling a little dumb, but somehow I do not manage to get sysctl.conf to be processsed during boot. So f.e. I've added: net.inet6.ip6.forwarding=1 to /etc/sysctl.conf But this does not get respected. However, manually I can run: /etc/rc.d/sysctl start /sbin/sysctl -f /etc/sysctl.con