@linveo said:
Do you want switched over to an AMD Ryzen node?
Thank you for the offer! Since it sounds like everybody else has already gone to AMD, I think it is better for me to stay on Intel for now so we can test both of the platforms out and make sure we have a solid solution going forward.
@Not_Oles said:
[ 2.884958] WARNING: 8 errors while detecting hardware; check system log. # What's with this?
Not sure, but it might be just scanning all the possible hardware upon the initial boot. Since you only see two errors in the next boot, it might have marked most of them 'not found' or something like that so it wouldn't keep trying.
@Not_Oles said:
[ 30.963838] rebooting... # Why the reboot?
I am guessing that it is resizing the filesystem and rebooting to make sure the changes are applied before doing anything else.
Also those two errors for the hardware detection look like they are related to VMware which is obviously not present here.
@Not_Oles said: [ 2.884958] WARNING: 8 errors while detecting hardware; check system log. # What's with this?
Not sure, I guess it's just the kernel probing what devices are available. I haven't really figured out what it is complaining about, the only thing I have found was the vmware and vmt0 errors.
@Not_Oles said: [ 30.963838] rebooting... # Why the reboot?
On the first boot it resizes the partition and the root filesystem and then reboots - that's standard practice with NetBSD images at least.
@linveo said:
Do you want switched over to an AMD Ryzen node?
Thank you for the offer! Since it sounds like everybody else has already gone to AMD, I think it is better for me to stay on Intel for now so we can test both of the platforms out and make sure we have a solid solution going forward.
Sounds good, let me know if you ever want to switch over.
@linveo said:
Do you want switched over to an AMD Ryzen node?
Thank you for the offer! Since it sounds like everybody else has already gone to AMD, I think it is better for me to stay on Intel for now so we can test both of the platforms out and make sure we have a solid solution going forward.
@Crab Thanks for dedication to the Community and to versatile and dependable solutions!
I first thought to try installing pkgsrc with pkgin or maybe install CVS with pkgin and then install pkgsrc via CVS. But, from the errors below, it seems like pkgin needs SSL certificates before it will work?
Since pkgin didn't seem to work, I tried grabbing the current pkgsrc tar archive from ftp.netbsd.org/pub/pkgsrc, which seemed to work okay.
Next up is to try bootstrapping pkgsrc. I will post about whether I get pkgsrc bootstrap to work.
What's the best procedure for going from the minimal install to a happy, functioning pkgsrc?
Thanks!
Tom
linveo# date
Sat Sep 28 21:20:00 UTC 2024
linveo# which pkgin
linveo# which pkg_add
/usr/sbin/pkg_add
linveo# which cvs
linveo# uname -p
x86_64
linveo# uname -r
10.0
linveo# PKG_PATH="http://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/$(uname -p)/$(uname -r|cut -f '1 2' -d.)/All/"
linveo# export PKG_PATH
linveo# echo $PKG_PATH
http://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/x86_64/10.0/All/
linveo# pkg_add pkgin
pkgin-23.8.1nb4: copying /usr/pkg/share/examples/pkgin/repositories.conf.example to /usr/pkg/etc/pkgin/repositories.conf
linveo# echo $?
0
linveo# which pkgin
/usr/pkg/bin/pkgin
linveo# which ed
/bin/ed
linveo# pkgin search cvs
processing remote summary (https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/x86_64/10.0/All)...
00B8DAF521780000:error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:/usr/src/crypto/external/bsd/openssl/dist/ssl/statem/statem_clnt.c:1889:
00B8DAF521780000:error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:/usr/src/crypto/external/bsd/openssl/dist/ssl/statem/statem_clnt.c:1889:
00B8DAF521780000:error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:/usr/src/crypto/external/bsd/openssl/dist/ssl/statem/statem_clnt.c:1889:
pkgin: Could not fetch https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/x86_64/10.0/All/pkg_summary.gz: Authentication error
linveo# pkgin install pkgsrc
00A81C7068740000:error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:/usr/src/crypto/external/bsd/openssl/dist/ssl/statem/statem_clnt.c:1889:
00A81C7068740000:error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:/usr/src/crypto/external/bsd/openssl/dist/ssl/statem/statem_clnt.c:1889:
00A81C7068740000:error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:/usr/src/crypto/external/bsd/openssl/dist/ssl/statem/statem_clnt.c:1889:
pkgin: Could not fetch https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/x86_64/10.0/All/pkg_summary.gz: Authentication error
linveo#
linveo# cd /usr
linveo# ftp ftp.netbsd.org
Trying [2001:470:a085:999::21]:21 ...
Connected to ftp.netbsd.org.
220 ftp.NetBSD.org FTP server (NetBSD-ftpd 20230930) ready.
Name (ftp.netbsd.org:root): ftp
331 Guest login ok, type your name as password.
Password:
230-
The NetBSD Project FTP Server located in San Jose, CA, USA
1 Gbps connectivity
WELCOME! /( )`
\ \___ / |
+--- Currently Supported Platforms ----+ /- _ `-/ '
| acorn32, algor, alpha, amd64, amiga, | (/\/ \ \ /\
| amigappc, arc, atari, bebox, cats, | / / | ` \
| cesfic, cobalt, dreamcast, emips, | O O ) / |
| epoc32, evbarm{,64}, evbmips, evbppc,| `-^--'`< '
| evbsh3, ews4800mips, hp300, | (_.) _ ) /
|hpc{arm,mips,sh}, hppa, i386, ibmnws, | .___/` /
|iyonix, landisk, luna68k,mac{68k,ppc},| `-----' /
| mipsco, mmeye, mvme68k, mvmeppc, | <----. __ / __ \
|netwinder, news68k, newsmips, next68k,| <----|====O)))==) \) /====
|ofppc, pmax, prep, rs6000, sandpoint, | <----' `--' `.__,' \
|sgimips, shark, sparc{,64}, sun{2,3}, | | |
| vax, x68k, xen, zaurus | \ /
+--------------------------------------+ ______( (_ / \_____
See our website at http://www.NetBSD.org/ ,' ,-----' | \
We log all FTP transfers and commands. `--{__________) (FL) \/
230-
EXPORT NOTICE
Please note that portions of this FTP site contain cryptographic
software controlled under the Export Administration Regulations (EAR)
of the United States of America.
None of this software may be downloaded or otherwise exported or
re-exported into (or to a national or resident of) any country
to which the U.S. has embargoed goods. Also, people personally
on the block lists of the United States Department of Treasury
or the United States Department of Commerce are prohibited.
By downloading or using said software, you are agreeing to the
foregoing and you are representing and warranting that you are not
located in, under the control of, or a national or resident of any
such country or on any such list.
230 Guest login ok, access restrictions apply.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> cd pub/pkgsrc/current
250 CWD command successful.
ftp> get pkgsrc.tar.gz.SHA1
local: pkgsrc.tar.gz.SHA1 remote: pkgsrc.tar.gz.SHA1
229 Entering Extended Passive Mode (|||54086|)
150 Opening BINARY mode data connection for 'pkgsrc.tar.gz.SHA1' (64 bytes).
100% |*****************************************************| 64 6.68 KiB/s 00:00 ETA
226 Transfer complete.
64 bytes received in 00:00 (0.54 KiB/s)
ftp> get pkgsrc.tar.gz
local: pkgsrc.tar.gz remote: pkgsrc.tar.gz
229 Entering Extended Passive Mode (|||54087|)
150 Opening BINARY mode data connection for 'pkgsrc.tar.gz' (84995861 bytes).
100% |*****************************************************| 83003 KiB 1.35 MiB/s 00:00 ETA
226 Transfer complete.
84995861 bytes received in 00:59 (1.35 MiB/s)
ftp> bye
221-
Data traffic for this session was 84995925 bytes in 2 files.
Total traffic for this session was 84999287 bytes in 2 transfers.
221 Thank you for using the FTP service on ftp.NetBSD.org.
linveo# ls -l pkgsrc*
-rw-r--r-- 1 root wheel 84995861 Sep 28 01:15 pkgsrc.tar.gz
-rw-r--r-- 1 root wheel 64 Sep 28 01:15 pkgsrc.tar.gz.SHA1
linveo#
linveo# tar xvzf pkgsrc.tar.gz
linveo# echo $?
0
linveo# linveo# ls -lR pkgsrc | wc -l
441701
linveo# linveo# cd bootstrap/
linveo# ls
CVS README.FreeBSD README.Interix README.NetBSD README.UnixWare
README README.GNUkFreeBSD README.Linux README.OSF1 README.macOS
README.AIX README.HPUX README.MidnightBSD README.OpenBSD bootstrap
README.Cygwin README.Haiku README.Minix3 README.OpenServer5 cleanup
README.DragonFly README.IRIX README.MirBSD README.Solaris testbootstrap
linveo# linveo# date
Sun Sep 29 02:46:19 UTC 2024
linveo# pwd
/usr/pkgsrc/bootstrap
linveo# ./bootstrap | tee bootstrap-out
ERROR: Please unset PKG_PATH before running bootstrap.
linveo# export PKG_PATH=""
linveo# ./bootstrap | tee bootstrap-out
===> bootstrap command: ./bootstrap
===> bootstrap started: Sun Sep 29 02:48:43 UTC 2024
Working directory is: /usr/pkgsrc/bootstrap/work
===> running: /usr/bin/sed -e 's|@DEFAULT_INSTALL_MODE@|'0755'|' /usr/pkgsrc/sysutils/install-sh/files/install-sh.in > /usr/pkgsrc/bootstrap/work/bin/install-sh
===> running: /bin/chmod +x /usr/pkgsrc/bootstrap/work/bin/install-sh
===> Creating default mk.conf in /usr/pkgsrc/bootstrap/work
===> running: /bin/sh /usr/pkgsrc/bootstrap/work/bin/install-sh -d -o root -g wheel /usr/pkgsrc/bootstrap/work/sbin
===> running: /bin/sh /usr/pkgsrc/bootstrap/work/bin/install-sh -d -o root -g wheel /usr/pkgsrc/bootstrap/work/share/mk
===> Bootstrapping mk-files
===> running: (cd /usr/pkgsrc/pkgtools/bootstrap-mk-files/files && env CP=/bin/cp OPSYS=NetBSD MK_DST=/usr/pkgsrc/bootstrap/work/share/mk ROOT_GROUP=wheel ROOT_USER=root SED=/usr/bin/sed SYSCONFDIR=/usr/pkg/etc /bin/sh ./bootstrap.sh)
===> Bootstrapping bmake
===> running: /bin/sh /usr/pkgsrc/bootstrap/work/bin/install-sh -d -o root -g wheel /usr/pkgsrc/bootstrap/work/bmake
===> running: (cd /usr/pkgsrc/bootstrap/work/bmake && /bin/sh configure --prefix=/usr/pkgsrc/bootstrap/work --with-default-sys-path=/usr/pkgsrc/bootstrap/work/share/mk --with-machine-arch=x86_64 )
Using: filemon_ktrace.c
checking whether system has timezone Europe/Berlin... yes
checking for gcc... no
checking for cc... no
checking for cl.exe... no
checking for clang... no
configure: error: in '/usr/pkgsrc/bootstrap/work/bmake':
configure: error: no acceptable C compiler found in $PATH
See 'config.log' for more details
===> exited with status 1
aborted.
linveo#
In the README it does say to have a working make and a compiler in your PATH. I did skim the README, but mistook the need for the compiler to be related to the cleanup command. My interpretation doesn't seem to make sense now.
From the README in /use/pkgsrc/bootsrap :
The bootstrap script will exit if the bootstrap directory already exists,
for example if you have run the script before. In this case, clean it up
by running:
# ./cleanup
Make sure that you have a working C compiler and make(1) binary in
your path.
So, as of right now, I haven't managed to bootstrap pkgsrc (because no compiler is installed), and I haven't managed to get binary packages installed because of what I think might be SSL errors with pkgin.
Maybe I will get a little further tomorrow! Yaaay!
@Not_Oles said: I first thought to try installing pkgsrc with pkgin or maybe install CVS with pkgin and then install pkgsrc via CVS. But, from the errors below, it seems like pkgin needs SSL certificates before it will work?
I think a certctl rehash is missing (I need to add that to the image creation). PKG_PATH is already set in /etc/pkg_install.conf for that image, so with a fresh install you can currently do:
NetBSD 10.0 (GENERIC) #0: Thu Mar 28 08:33:33 UTC 2024
Welcome to NetBSD!
We recommend that you create a non-root account and use su(1) for root access.
test# certctl rehash
test# pkg_add pkgin
pkgin-23.8.1nb4: copying /usr/pkg/share/examples/pkgin/repositories.conf.example to /usr/pkg/etc/pkgin/repositories.conf
test# pkgin upgrade
processing remote summary (https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/x86_64/10.0/All)...
pkg_summary.gz 100% 6170KB 220.4KB/s 00:28
calculating dependencies...done.
nothing to do.
test#
@cmeerw said: I think a certctl rehash is missing (I need to add that to the image creation). PKG_PATH is already set in /etc/pkg_install.conf for that image
@cmeerw Thanks for introducing me to certctl And /etc/pkg_install.conf
linveo# man certctl
man: Formatting manual page...
CERTCTL(8) System Manager's Manual CERTCTL(8)
NAME
certctl - configure OpenSSL certificate trust anchors
SYNOPSIS
certctl [-nv] [-C config] [-c certsdir] [-u distrustdir] cmd [args...]
certctl [options] list
certctl [options] rehash
certctl [options] trust cert
certctl [options] untrust cert
certctl [options] untrusted
DESCRIPTION
The certctl utility manages certificates used by OpenSSL-based
applications as trust anchors for certificate validation in TLS or other
purposes, for example by ftp(1) in HTTPS. certctl allows configuring the
set of certificates and persistently excluding individual certificates.
[ . . . ]
HISTORY
certctl first appeared in NetBSD 10.0. A utility of the same name
previously appeared in FreeBSD 12.2.
NetBSD 10.0 August 16, 2023 NetBSD 10.0
linveo# cat /etc/openssl/certs.conf
netbsd-certctl 20230816
# $NetBSD: certs.conf,v 1.1.2.2 2023/09/04 17:33:27 martin Exp $
#
# Configuration file for certctl(8) to manage HTTPS root CA
# certificates in /etc/openssl/certs.
#
path /usr/share/certs/mozilla/server
# For manual control over /etc/openssl/certs, e.g. if you want to
# install a separate CA bundle from pkgsrc, uncomment the next line:
#manual
linveo#
Next is to read up on "unset." Sounds like a shell built-in, so that all I need to do is run unset PKG_PATH.
Hmm. Well, maybe I don't have to look too far.
linveo# ps
PID TTY STAT TIME COMMAND
15318 pts/0 O+ 0:00.00 ps
19420 pts/0 Ss 0:00.02 -sh
1315 ttyE0 Is+ 0:00.00 /usr/libexec/getty Pc constty
linveo#
Yeah, I am using the sh shell, which I guess is the default.
linveo# man sh
[ . . . ]
unset [-efvx] name ...
If -v is specified, the specified variables are unset and
unexported. Readonly variables cannot be unset. If -f is
specified, the specified functions are undefined. If -e is given,
the specified variables are unexported, but otherwise unchanged,
alternatively, if -x is given, the exported status of the variable
will be retained, even after it is unset.
If no flags are provided -v is assumed. If -f is given with one
of the other flags, then the named variables will be unset, or
unexported, and functions of the same names will be undefined.
The -e and -x flags both imply -v. If -e is given, the -x flag is
ignored.
The exit status is 0, unless an attempt was made to unset a
readonly variable, in which case the exit status is 1. It is not
an error to unset (or undefine) a variable (or function) that is
not currently set (or defined.)
[ . . . ]
linveo#
Looks like maybe it's enough to unset PKG_PATH and to again remove /usr/pkgsrc/bootstrap/work. But maybe I should ditch PKG_PATH from .profile?
@Not_Oles said: Next up might be to retry bootstrapping pkgsrc!
I don't think you need to do any bootstrapping on NetBSD, just cd to the package you want to build and type make there.
NetBSD already contains the necessary tools for using pkgsrc; on other platforms you need to bootstrap pkgsrc to get the package management tools installed.
The language @cmeerw quoted does not seem to appear in either /use/pkgsrc/bootstrap/README or /use/pkgsrc/bootstrap/README.NetBSD.
So, to clean up, maybe all I need to do is remove /usr/pkgsrc/bootstrap/work.
Next up might be to build something with pkgsrc. Maybe Lynx or notqmail.
Maybe move soon from NetBSD 10 to NetBSD-current. I probably need to add /src in a similar way to how the compiler set was added. Then update with CVS. Then maybe NetBSD-current will rebuild itself from /src. Amazing!
@Not_Oles said: Maybe move soon from NetBSD 10 to NetBSD-current. I probably need to add /src in a similar way to how the compiler set was added. Then update with CVS. Then maybe NetBSD-current will rebuild itself from /src. Amazing!
Unless you really want to rebuild everything from source, you can just use sysupgrade (from pkgsrc) and point it to the latest HEAD build.
@cmeerw said: Unless you really want to rebuild everything from source
Thanks @cmeerw! Not so much that I want to rebuild everything from source. It's mainly that I can rebuild everything from source. And I'm not sure that I can rebuild everything until I actually do rebuild everything.
Once the rebuild completes successfully, it means that anything big or little can be changed. Not that I am capable of making the changes myself, but the NetBSD guys always were extremely friendly and extremely helpful and super fast to respond! I imagine that NetBSD culture still is the same.
certificates are now set up correctly out of the box (thanks @Not_Oles for pointing that out)
use "log" option on the root filesystem
pre-install "modules" and "rescue" packages
set savecore=NO in rc.conf and fetch_pkg_vulnerabilities="YES" in daily.conf
@linveo could you update to the new image please? Hopefully, this should be fairly stable now.
(Note: the image is AMD only - although I could use a patched kernel, I think it's better to stick with official kernels to avoid having the VM break when updating the kernel)
certificates are now set up correctly out of the box (thanks @Not_Oles for pointing that out)
use "log" option on the root filesystem
pre-install "modules" and "rescue" packages
set savecore=NO in rc.conf and fetch_pkg_vulnerabilities="YES" in daily.conf
@linveo could you update to the new image please? Hopefully, this should be fairly stable now.
(Note: the image is AMD only - although I could use a patched kernel, I think it's better to stick with official kernels to avoid having the VM break when updating the kernel)
Thanks @cmeerw! This is great because it permits Linux users everywhere to have easy access to NetBSD. Plus also, NetBSD fans easily can run NetBSD in lots of inexpensive cloud environments, as long as providers like Linveo are kind enough to add the image.
May I please ask which NetBSD install sets are included in your new image?
Would it make sense to provide a NetBSD-current image with all sets included?
To what extent could your new image be used generally on Linux with Qemu? I guess the image would run on any architecture which supports Qemu emulation of AMD64?
@Not_Oles said: May I please ask which NetBSD install sets are included in your new image?
I am installing "base etc kern-GENERIC man modules rescue" now.
@Not_Oles said: Would it make sense to provide a NetBSD-current image with all sets included?
I don't think it would make a lot of sense as the image would be quite large and as NetBSD-current changes daily, the image would need to change very frequently as well. I think it makes a lot more sense to use 10.0 as a starting point and then update to current. sysupgrade is a very nice tool that makes updating to current (and keeping up to date) very easy.
Essentially you would
install sysupgrade (pkg_add sysupgrade)
set RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/$(uname -m)" in /usr/pkg/etc/sysupgrade.conf
touch set.* files in /etc/mtree for additional package you want to install during the upgrade
sysupgrade auto
@Not_Oles said: To what extent could your new image be used generally on Linux with Qemu? I guess the image would run on any architecture which supports Qemu emulation of AMD64?
The main thing here is how to get network interfaces and SSH keys configured in the VM. VirtFusion seems to do that by making a small CD filesystem available that contains yaml files with the configuration data. I am looking for that filesystem, reading the yaml files and configuring the NetBSD system. I am actually not using the full cloud-init package to do that (as that would pull in way too many dependencies for my taste), but just using a small lua script for that.
On your linveo VM you might see a sd0 drive (although that drive seems to disappear some time after the VM has been set up).
sysupgrade is a very nice tool that makes updating to current (and keeping up to date) very easy.
Essentially you would
install sysupgrade (pkg_add sysupgrade)
set RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/$(uname -m)" in /usr/pkg/etc/sysupgrade.conf
touch set.* files in /etc/mtree for additional package you want to install during the upgrade
sysupgrade auto
Suppose I try following @cmeerw's kind instructions for running sysupgrade on my presently installed VM -- in other words, not yet the newly updated @cmeerw image which he just mentioned above.
Start by installing sysupgrade:
linveo# date
Fri Oct 4 19:23:32 UTC 2024
linveo# pkg_add sysupgrade
sysupgrade-1.5nb10: copying /usr/pkg/share/examples/sysupgrade/default.conf to /usr/pkg/etc/sysupgrade.conf
linveo#
Next, set RELEASEDIR in /usr/pkg/etc/sysupgrade.conf:
linveo# date
Fri Oct 4 23:55:56 UTC 2024
linveo# cd /usr/pkg/etc
linveo# ls
pkgin sysupgrade.conf
linveo# cat -n sysupgrade.conf
1 # $NetBSD: default.conf,v 1.2 2012/10/11 00:16:46 jmmv Exp $
2
3 # Configuration of automatic system upgrades by sysupgrade(8).
4 #
5 # See sysupgrade.conf(5) for details on the syntax of this file and the
6 # meaning of the configuration variables. Note that not all the supported
7 # configuration variables are listed in this sample configuration file.
8
9 # Path to the release files (local path or remote URL).
10 #RELEASEDIR="ssh://[email protected]/home/sysbuild/release/$(uname -m)"
11 #RELEASEDIR="/home/sysbuild/release/$(uname -m)"
12 #RELEASEDIR="https://cdn.NetBSD.org/pub/NetBSD/NetBSD-9.1/$(uname -m)"
13 # Upgrade to the latest snapshot of the current branch
14 #RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/$(uname -m)"
15 # Upgrade to the latest snapshot of a stable branch
16 RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/$(uname -m)"
17
18 # Name of the kernel to be installed.
19 KERNEL=AUTO # Guess from /netbsd (requires config(1)).
20
21 # Whitespace-separated list of sets to install.
22 SETS=AUTO # Guess from /etc/mtree/set.* files.
23
24 # Whitespace-separated list of postinstall(8) checks to automatically fix.
25 POSTINSTALL_AUTOFIX="obsolete"
26
27 # Whether to run etcupdate or not as part of an upgrade.
28 #
29 # Running etcupdate is the only interactive step in the upgrade process, so
30 # setting this variable to 'no' effectively makes upgrades unattended. You
31 # can later run etcupdate at a later step by hand.
32 #ETCUPDATE=no
33
34 # Whether to delete the downloaded files after an upgrade or not.
35 #
36 # If you set ETCUPDATE=no, you will most likely want to disable
37 # auto-cleaning as well. The reason for this is that, if you want to later
38 # do "sysupgrade etcupdate" using the same etc.tgz file downloaded during
39 # the upgrade, you will need the same etc.tgz file to be present.
40 #AUTOCLEAN=no
41
42 # Archive file extension of the sets. For now it can be either 'tgz' or
43 # 'tar.xz'.
44 #ARCHIVE_EXTENSION=tar.xz
linveo# ed sysupgrade.conf
1920
16
RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/$(uname -m)"
s/^/# /p
# RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/$(uname -m)"
a
RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/$(uname -m)"
.
w
2001
16,17p
# RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/$(uname -m)"
RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/$(uname -m)"
q
linveo#
Next, "touch set.* files in /etc/mtree" for additional sets.
What I already have in etc/mtree might be missing at least set.misc, set.modules, set.rescue, and set.text. Plus it also is missing the X sets, but I am okay with skipping X for the time being. Maybe I am okay with skipping modules, too.
linveo# cd /etc/mtree
linveo# ls -l
total 4896
-r--r--r-- 1 root wheel 68983 Mar 28 2024 NetBSD.dist
-r--r--r-- 1 root wheel 880419 Mar 28 2024 set.base
-r--r--r-- 1 root wheel 3048246 Mar 28 2024 set.comp
-r--r--r-- 1 root wheel 48302 Mar 28 2024 set.etc
-r--r--r-- 1 root wheel 914350 Mar 28 2024 set.man
-r--r--r-- 1 root wheel 20222 Mar 28 2024 special
linveo#
The touched files do not have any content, unlike all the other files in /etc/mtree.
linveo# date
Sat Oct 5 00:06:52 UTC 2024
linveo# cd /etc/mtree
linveo# ls -l
total 4896
-r--r--r-- 1 root wheel 68983 Mar 28 2024 NetBSD.dist
-r--r--r-- 1 root wheel 880419 Mar 28 2024 set.base
-r--r--r-- 1 root wheel 3048246 Mar 28 2024 set.comp
-r--r--r-- 1 root wheel 48302 Mar 28 2024 set.etc
-r--r--r-- 1 root wheel 914350 Mar 28 2024 set.man
-r--r--r-- 1 root wheel 20222 Mar 28 2024 special
linveo# touch set.misc set.rescue set.text
linveo# ls -l
total 4896
-r--r--r-- 1 root wheel 68983 Mar 28 2024 NetBSD.dist
-r--r--r-- 1 root wheel 880419 Mar 28 2024 set.base
-r--r--r-- 1 root wheel 3048246 Mar 28 2024 set.comp
-r--r--r-- 1 root wheel 48302 Mar 28 2024 set.etc
-r--r--r-- 1 root wheel 914350 Mar 28 2024 set.man
-rw-r--r-- 1 root wheel 0 Oct 5 00:07 set.misc
-rw-r--r-- 1 root wheel 0 Oct 5 00:07 set.rescue
-rw-r--r-- 1 root wheel 0 Oct 5 00:07 set.text
-r--r--r-- 1 root wheel 20222 Mar 28 2024 special
linveo#
Okay, now let's try running sysupgrade auto -- I will post about what happens.
--------
Meanwhile, here are a few interesting snippets from my homework skimming:
linveo# man sysupgrade
man: Formatting manual page...
SYSUPGRADE(8) System Manager's Manual SYSUPGRADE(8)
NAME
sysupgrade - upgrades a NetBSD system to a newer version
SYNOPSIS
common_flags ::= [-c config_name] [-d destdir] [-o variable=value]
DESCRIPTION
sysupgrade is a utility that automates the process of upgrading a
possibly-running NetBSD system to a newer release.
sysupgrade works by first fetching the release sets from a remote site or
from a local directory, then by upgrading the system using such release
sets and finally by taking care of bringing the system configuration up
to date. In other words, sysupgrade does nothing special on its own: it
is just a utility that automates a highly manual process and relies on
other tools within the system to perform its job.
sysupgrade has a subcommand-based interface: every command performs a
single step of the upgrade procedure, and the `auto' command orchestrates
a complete upgrade by invoking the rest of the commands in a specific
order. There are a set of options that apply to all commands (those
stated before the command name), and every particular command may accept
its own options and arguments as shown in the synopsis.
The behavior of sysupgrade is defined by a configuration file that
specifies how to apply an update to the system (see sysupgrade.conf(5)).
For example, the configuration states which distribution sets ought to be
installed, where they need to be downloaded from, and whether the system
configuration files should be upgraded.
[ . . . ]
EXAMPLES AND TROUBLESHOOTING
The most common way of executing sysupgrade is by using the `auto'
command and relying in the default configuration file:
$ sysupgrade auto
[ . . . ]
SEE ALSO
sysbuild(1), sysupgrade.conf(5), etcupdate(8), postinstall(8)
AUTHORS
The sysupgrade utility was developed by Julio Merino <[email protected]>.
[ . . . ]
linveo# man mtree
man: Formatting manual page...
MTREE(8) System Manager's Manual MTREE(8)
NAME
mtree - map a directory hierarchy
SYNOPSIS
mtree [-bCcDdejLlMnPqrStUuWx] [-i | -m] [-E tags] [-F flavor] [-f spec]
[-I tags] [-K keywords] [-k keywords] [-N dbdir] [-O onlyfile]
[-p path] [-R keywords] [-s seed] [-X exclude-file]
DESCRIPTION
The mtree utility compares a file hierarchy against a specification,
creates a specification for a file hierarchy, or modifies a
specification.
[ . . . ]
HISTORY
The mtree utility appeared in 4.3BSD-Reno. [ . . . ]
[ . . . ]
linveo#
linveo# date
Sat Oct 5 01:02:03 UTC 2024
linveo# sh /usr/sbin/postinstall -s /var/cache/sysupgrade/etc.tar.xz -d / fix defaults makedev mtree opensslcertsrehash periodic ptyfsoldnodes rc
Note: Creating temporary directory /tmp/_postinstall.25531.0/etc.tgz
Note: Extracting files from /var/cache/sysupgrade/etc.tar.xz
Source directory: /tmp/_postinstall.25531.0/etc.tgz
(extracted from: /var/cache/sysupgrade/etc.tar.xz)
Target directory: /
defaults fix:
(Checking for pf.boot.conf from /tmp/_postinstall.25531.0/etc.tgz/etc/defaults instead of /tmp/_postinstall.25531.0/etc.tgz/usr.sbin/pf/etc/defaults)
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/defaults/npf.boot.conf to /etc/defaults/npf.boot.conf
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/defaults/rc.conf to /etc/defaults/rc.conf
makedev fix:
(Checking for MAKEDEV from /tmp/_postinstall.25531.0/etc.tgz/dev instead of /tmp/_postinstall.25531.0)
Copied /tmp/_postinstall.25531.0/etc.tgz/dev/MAKEDEV to /dev/MAKEDEV
(Checking for MAKEDEV.local from /tmp/_postinstall.25531.0/etc.tgz/dev instead of /tmp/_postinstall.25531.0/etc.tgz/etc)
mtree fix:
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/mtree/special to /etc/mtree/special
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/mtree/NetBSD.dist to /etc/mtree/NetBSD.dist
opensslcertsrehash fix:
periodic fix:
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/security to /etc/security
ptyfsoldnodes fix:
[1] Bad system call (core dumped) ${HOST_SH} "${MAKEDEV_DIR}/MAKEDEV" -s pty0 2>... |
Done ${AWK} "\
BEGIN { before_re = \".*device=...
Cannot find device major numbers for pty master and slave
rc fix:
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d/bluetooth to /etc/rc.d/bluetooth
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d/certctl_init to /etc/rc.d/certctl_init
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d/ip6addrctl to /etc/rc.d/ip6addrctl
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d/ipfs to /etc/rc.d/ipfs
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d/iscsid_volumes to /etc/rc.d/iscsid_volumes
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d/named to /etc/rc.d/named
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d/npf to /etc/rc.d/npf
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d/postfix to /etc/rc.d/postfix
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d/resize_root to /etc/rc.d/resize_root
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d/securelevel to /etc/rc.d/securelevel
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d/sshd to /etc/rc.d/sshd
Copied /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d/sysdb to /etc/rc.d/sysdb
(Checking for blocklistd from /tmp/_postinstall.25531.0/etc.tgz/etc/rc.d instead of /tmp/_postinstall.25531.0/etc.tgz/external/bsd/blocklist/etc/rc.d)
postinstall fixes passed: defaults makedev mtree opensslcertsrehash periodic rc
postinstall fixes failed: ptyfsoldnodes
linveo#
I see another core dump and a post install fix that failed.
It'd be handy/useful to others if you wrapped those outputs in spoiler tags.
In stasis until the shitposting stops/abates.
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural. It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
linveo# date; reboot
Sat Oct 5 02:54:22 UTC 2024
Connection to xxx.xxx.xxx.xxx closed by remote host.
Connection to xxx.xxx.xxx.xxx closed.
chronos@penguin:~/servers/linveo$ sleep 60
chronos@penguin:~/servers/linveo$ `head -n 1 login`
Last login: Fri Oct 4 23:55:24 2024 from xxx.xxx.xxx.xxx
NetBSD 10.99.12 (GENERIC) #0: Wed Oct 2 21:21:26 UTC 2024
Welcome to NetBSD!
We recommend that you create a non-root account and use su(1) for root access.
linveo# date
Sat Oct 5 02:55:46 UTC 2024
linveo# uname -a
NetBSD linveo.metalvps.com 10.99.12 NetBSD 10.99.12 (GENERIC) #0: Wed Oct 2 21:21:26 UTC 2024 [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC amd64
linveo#
In the context of; paste in your content with it all highlighted, then select Spolier.
You've sussed it though.
In stasis until the shitposting stops/abates.
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural. It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
certificates are now set up correctly out of the box (thanks @Not_Oles for pointing that out)
use "log" option on the root filesystem
pre-install "modules" and "rescue" packages
set savecore=NO in rc.conf and fetch_pkg_vulnerabilities="YES" in daily.conf
@linveo could you update to the new image please? Hopefully, this should be fairly stable now.
(Note: the image is AMD only - although I could use a patched kernel, I think it's better to stick with official kernels to avoid having the VM break when updating the kernel)
Thanks for making these updates. This new template is now available. I appreciate all the work you've done to further the usage of NetBSD!
@linveo said: Thanks for making these updates. This new template is now available. I appreciate all the work you've done to further the usage of NetBSD!
It still seems to be rebuilding from the old image (for me on kvmtx12). I can see that you have downloaded the updated image (netbsd-10.0-v3.qcow2).
@linveo said: Thanks for making these updates. This new template is now available. I appreciate all the work you've done to further the usage of NetBSD!
It still seems to be rebuilding from the old image (for me on kvmtx12). I can see that you have downloaded the updated image (netbsd-10.0-v3.qcow2).
I have removed the old template from that node. If you try again it should pull in the latest version. I thought by changing the version number, VF would grab a new version to cache, but I guess not.
@linveo said: Thanks for making these updates. This new template is now available. I appreciate all the work you've done to further the usage of NetBSD!
It still seems to be rebuilding from the old image (for me on kvmtx12). I can see that you have downloaded the updated image (netbsd-10.0-v3.qcow2).
I have removed the old template from that node. If you try again it should pull in the latest version. I thought by changing the version number, VF would grab a new version to cache, but I guess not.
Haha! I didn't get that far. I was thinking of putting the about-to-be-posted content into a file and running something like sed -i 's/^/>! /g' file and then copy/pasting the result. Your suggestion is a lot easier! So, thanks for your kind help!
Next up for me might be reading about how to compile all of NetBSD from source, getting the sources (probably with CVS) and trying the compile. I am thinking of trying with my present install based on @cmeerw's previous image. I think it's been . . . like ~30 years . . . since the last time I tried this!
Made another update to the NetBSD 10.0 image to use more useful parameters during filesystem creation (only realised over the weekend that the scripts I based my image creation on used some rather questionable filesystem settings that result in an almost insane number of inodes after resizing).
As a bonus I then tried to also make an image for NetBSD 9.4. This required an additional reboot when resizing the partition/filesystem, but the end result should be very similar to the 10.0 image. (Note: 9.4 doesn't have any SSL certificates, so I am setting the default PKG_PATH to the http URL instead of https).
Hopefully, these are now stable enough and I can wait for NetBSD 10.1 for the next update.
BTW, for those interested in some of the technical details, I noticed that you can end up with a screwed up filesystem that might silently eat some of your data if you are not careful with all the resize stuff (but without ever seeing any warning from the tools) - that's PR #58723. A cosmetic bug in the df output I noticed has already been fixed on HEAD - PR #58718
@cmeerw said: some rather questionable filesystem settings that result in an almost insane number of inodes after resizing
With your two new images and with the NetBSD PRs that you mentioned, it looks like both you and NetBSD itself successfully have moved beyond the inodes issue.
Normally I would try to read up on the issue before asking a question, but, maybe, if you don't mind, you could please tell me whether you think the the inodes issue might exist on my install from your older image, and how to run a quick check.
@Not_Oles said: Normally I would try to read up on the issue before asking a question, but, maybe, if you don't mind, you could please tell me whether you think the the inodes issue might exist on my install from your older image, and how to run a quick check.
Yes, your image will be affected, a quick way to tell is to run df -mi /
In the iAvail column it will likely show something like 20 million inodes (instead of maybe 3 million), but in the 1M-blocks column you'll likely only see around 20000 blocks (instead of maybe 24300), e.g.
I still have to study up, but here is the output of the df -ml / command you suggested showing results as you predicted:
linveo# date
Mon Oct 7 23:27:04 UTC 2024
linveo# df -mi /
Filesystem 1M-blocks Used Avail %Cap iUsed iAvail %iCap Mounted on
/dev/dk2 20231 1920 17299 9% 307359 19440415 1% /
linveo#
I still need to try the rebuild from source. When I get a chance, I will do that and post about what happens. Trying the compile will be a lot of fun even if it doesn't work for any reason, including maybe the filesystem.
@cmeerw said:
Made another update to the NetBSD 10.0 image to use more useful parameters during filesystem creation (only realised over the weekend that the scripts I based my image creation on used some rather questionable filesystem settings that result in an almost insane number of inodes after resizing).
As a bonus I then tried to also make an image for NetBSD 9.4. This required an additional reboot when resizing the partition/filesystem, but the end result should be very similar to the 10.0 image. (Note: 9.4 doesn't have any SSL certificates, so I am setting the default PKG_PATH to the http URL instead of https).
Hopefully, these are now stable enough and I can wait for NetBSD 10.1 for the next update.
BTW, for those interested in some of the technical details, I noticed that you can end up with a screwed up filesystem that might silently eat some of your data if you are not careful with all the resize stuff (but without ever seeing any warning from the tools) - that's PR #58723. A cosmetic bug in the df output I noticed has already been fixed on HEAD - PR #58718
I have loaded up the latest NetBSD 10 template and added a new one for 9.4. Thanks again!
If you have any instructions I can follow to create qcow2 templates, I can try as well. I was given some documentation from VF to create my own, but not sure how well it will work.
Comments
Same here! Thanks @cmeerw! Thanks @linveo!
Thank you for the offer! Since it sounds like everybody else has already gone to AMD, I think it is better for me to stay on Intel for now so we can test both of the platforms out and make sure we have a solid solution going forward.
@Not_Oles said:
It's resizing on the first boot and then rebooting?
Not sure, but it might be just scanning all the possible hardware upon the initial boot. Since you only see two errors in the next boot, it might have marked most of them 'not found' or something like that so it wouldn't keep trying.
I am guessing that it is resizing the filesystem and rebooting to make sure the changes are applied before doing anything else.
Also those two errors for the hardware detection look like they are related to VMware which is obviously not present here.
Not sure, I guess it's just the kernel probing what devices are available. I haven't really figured out what it is complaining about, the only thing I have found was the vmware and vmt0 errors.
On the first boot it resizes the partition and the root filesystem and then reboots - that's standard practice with NetBSD images at least.
Sounds good, let me know if you ever want to switch over.
linveo.com | Shared Hosting | KVM VPS | Dedicated Servers
@Crab Thanks for dedication to the Community and to versatile and dependable solutions!
Reference: https://pkgsrc.org/
What I think I want to do is to install pkgsrc.
I first thought to try installing pkgsrc with pkgin or maybe install CVS with pkgin and then install pkgsrc via CVS. But, from the errors below, it seems like pkgin needs SSL certificates before it will work?
Since pkgin didn't seem to work, I tried grabbing the current pkgsrc tar archive from ftp.netbsd.org/pub/pkgsrc, which seemed to work okay.
Next up is to try bootstrapping pkgsrc. I will post about whether I get pkgsrc bootstrap to work.
What's the best procedure for going from the minimal install to a happy, functioning pkgsrc?
Thanks!
Tom
In the README it does say to have a working make and a compiler in your PATH. I did skim the README, but mistook the need for the compiler to be related to the
cleanupcommand. My interpretation doesn't seem to make sense now.From the README in /use/pkgsrc/bootsrap :
So, as of right now, I haven't managed to bootstrap pkgsrc (because no compiler is installed), and I haven't managed to get binary packages installed because of what I think might be SSL errors with pkgin.
Maybe I will get a little further tomorrow! Yaaay!
I think a
certctl rehashis missing (I need to add that to the image creation).PKG_PATHis already set in/etc/pkg_install.conffor that image, so with a fresh install you can currently do:I think you can install the compiler by just doing:
Alternatively, you could use
sysinstto install additional packages (but need to be careful to not let sysinst overwrite any existing configuration)@cmeerw Thanks for introducing me to
And 
certctl/etc/pkg_install.confThanks again @cmeerw
Thanks to Linveo for the test VPSes! 
Showing the output of
progressat a random momet during the download and extraction:Upon finishing:
Next up might be to retry bootstrapping pkgsrc!
Thanks again @cmeerw!
Thanks again Linveo! 
So, "unset PKG_PATH" is not the same as "export PKG_PATH=""". Apparently I need to have no PKG_PATH variable at all?
But we said
Next is to read up on "unset."
Sounds like a shell built-in, so that all I need to do is run
unset PKG_PATH.Hmm. Well, maybe I don't have to look too far.
Yeah, I am using the
shshell, which I guess is the default.Looks like maybe it's enough to
unset PKG_PATHand to again remove/usr/pkgsrc/bootstrap/work. But maybe I should ditch PKG_PATH from.profile?Wait! That PKG_PATH line already is commented out!
And there seems to be no PKG_PATH variable. . . .
Why did
./bootstrapthrow that error based on PKG_PATH?Now I'm confused! Haha!
More tomorrow, since it's getting late here. . . .
It's even later than "getting late." But, anyway, one more try. And one more error.
So I guess I have to remove pkg_install-20240307.
Or maybe remove something of which contains pkg_install-20240307 as a part? 
More tomorrow.
Thanks BSD! 
Thanks Linveo! 
I don't think you need to do any bootstrapping on NetBSD, just cd to the package you want to build and type
makethere.ROTFL!
I really like that fine guys like @cmeerw catch my many mistakes! That's great!
The language @cmeerw quoted appears in both the NetBSD packages collection documentation at https://www.netbsd.org/docs/software/packages.html and also on the pkgsrc.org home page.
The language @cmeerw quoted does not seem to appear in either
/use/pkgsrc/bootstrap/READMEor/use/pkgsrc/bootstrap/README.NetBSD.So, to clean up, maybe all I need to do is remove
/usr/pkgsrc/bootstrap/work.Next up might be to build something with pkgsrc. Maybe Lynx or notqmail.
Maybe move soon from NetBSD 10 to NetBSD-current. I probably need to add /src in a similar way to how the compiler set was added. Then update with CVS. Then maybe NetBSD-current will rebuild itself from /src. Amazing!
Thanks *BSD! Thanks NetBSD! Thanks @cmeerw! Thanks Linveo!
Unless you really want to rebuild everything from source, you can just use
sysupgrade(from pkgsrc) and point it to the latest HEAD build.Thanks @cmeerw!
Not so much that I want to rebuild everything from source. It's mainly that I can rebuild everything from source. And I'm not sure that I can rebuild everything until I actually do rebuild everything.
Once the rebuild completes successfully, it means that anything big or little can be changed. Not that I am capable of making the changes myself, but the NetBSD guys always were extremely friendly and extremely helpful and super fast to respond! I imagine that NetBSD culture still is the same.
I have created a new NetBSD 10.0 image with these changes:
savecore=NOinrc.confandfetch_pkg_vulnerabilities="YES"indaily.conf@linveo could you update to the new image please? Hopefully, this should be fairly stable now.
(Note: the image is AMD only - although I could use a patched kernel, I think it's better to stick with official kernels to avoid having the VM break when updating the kernel)
Thanks @cmeerw! This is great because it permits Linux users everywhere to have easy access to NetBSD. Plus also, NetBSD fans easily can run NetBSD in lots of inexpensive cloud environments, as long as providers like Linveo are kind enough to add the image.
May I please ask which NetBSD install sets are included in your new image?
Would it make sense to provide a NetBSD-current image with all sets included?
To what extent could your new image be used generally on Linux with Qemu? I guess the image would run on any architecture which supports Qemu emulation of AMD64?
Thanks again! Best wishes!
I am installing "base etc kern-GENERIC man modules rescue" now.
I don't think it would make a lot of sense as the image would be quite large and as NetBSD-current changes daily, the image would need to change very frequently as well. I think it makes a lot more sense to use 10.0 as a starting point and then update to current.
sysupgradeis a very nice tool that makes updating to current (and keeping up to date) very easy.Essentially you would
sysupgrade(pkg_add sysupgrade)RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/$(uname -m)"in/usr/pkg/etc/sysupgrade.confset.*files in/etc/mtreefor additional package you want to install during the upgradesysupgrade autoThe main thing here is how to get network interfaces and SSH keys configured in the VM. VirtFusion seems to do that by making a small CD filesystem available that contains yaml files with the configuration data. I am looking for that filesystem, reading the yaml files and configuring the NetBSD system. I am actually not using the full cloud-init package to do that (as that would pull in way too many dependencies for my taste), but just using a small lua script for that.
On your linveo VM you might see a
sd0drive (although that drive seems to disappear some time after the VM has been set up).Suppose I try following @cmeerw's kind instructions for running sysupgrade on my presently installed VM -- in other words, not yet the newly updated @cmeerw image which he just mentioned above.
sysupgrade:/usr/pkg/etc/sysupgrade.conf:What I already have in
etc/mtreemight be missing at least set.misc, set.modules, set.rescue, and set.text. Plus it also is missing the X sets, but I am okay with skipping X for the time being. Maybe I am okay with skipping modules, too.The touched files do not have any content, unlike all the other files in
/etc/mtree.Okay, now let's try running
sysupgrade auto-- I will post about what happens.--------
Meanwhile, here are a few interesting snippets from my homework skimming:
Here is the output from running
sysupgrade auto.Probably I should run the fix given at the end for the failed postinstall checks.
What about the lines that say
"[1] Bad system call (core dumped) /usr/sbin/etcupdate -a -l ${sflags}"
and
"[1] Bad system call (core dumped) ${HOST_SH} "${MAKEDEV_DIR}/MAKEDEV" -s pty0 2>... |"?
Here is what happened when the fix ran:
I see another core dump and a post install fix that failed.
So, what now?
Also, is the system going to be able to reboot?
. . . Haha!
It'd be handy/useful to others if you wrapped those outputs in spoiler tags.
In stasis until the shitposting stops/abates.
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural.
It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
Thanks for asking for spoiler tags! I had been thinking about doing that! It is a lot of output.
@AlwaysSkint You said "wrap."
Thanks!
https://mail-index.netbsd.org/current-users/2024/06/01/msg045326.html
Seems to reboot okay!
Rerunning the command which produced the ptyfsoldnodes failure seems to succeed after the reboot.
Ahh, yes...
Guess upgrading the kernel first, rebooting and then updating userland would have been the safer option
So maybe:
sysupgrade fetch,sysupgrade kernel, reboot,sysupgrade autoIn the context of; paste in your content with it all highlighted, then select Spolier.
You've sussed it though.
In stasis until the shitposting stops/abates.
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural.
It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
Thanks for making these updates. This new template is now available. I appreciate all the work you've done to further the usage of NetBSD!
linveo.com | Shared Hosting | KVM VPS | Dedicated Servers
It still seems to be rebuilding from the old image (for me on kvmtx12). I can see that you have downloaded the updated image (netbsd-10.0-v3.qcow2).
I have removed the old template from that node. If you try again it should pull in the latest version. I thought by changing the version number, VF would grab a new version to cache, but I guess not.
linveo.com | Shared Hosting | KVM VPS | Dedicated Servers
Thanks, it did install with the new image now.
Haha! I didn't get that far. I was thinking of putting the about-to-be-posted content into a file and running something like
sed -i 's/^/>! /g' fileand then copy/pasting the result. Your suggestion is a lot easier! So, thanks for your kind help!BTW, did you check IPv6 setup? Had another quick look into FreeBSD land, and I don't think IPv6 was set up for me there.
Next up for me might be reading about how to compile all of NetBSD from source, getting the sources (probably with CVS) and trying the compile. I am thinking of trying with my present install based on @cmeerw's previous image. I think it's been . . . like ~30 years . . . since the last time I tried this!
Looks like the info on how to build NetBSD from source is in Part VI of the NetBSD Guide.
OpenBSD ftw!
Made another update to the NetBSD 10.0 image to use more useful parameters during filesystem creation (only realised over the weekend that the scripts I based my image creation on used some rather questionable filesystem settings that result in an almost insane number of inodes after resizing).
As a bonus I then tried to also make an image for NetBSD 9.4. This required an additional reboot when resizing the partition/filesystem, but the end result should be very similar to the 10.0 image. (Note: 9.4 doesn't have any SSL certificates, so I am setting the default
PKG_PATHto thehttpURL instead ofhttps).Hopefully, these are now stable enough and I can wait for NetBSD 10.1 for the next update.
@linveo could you update the NetBSD 10.0 image and add the NetBSD 9.4 image please?
BTW, for those interested in some of the technical details, I noticed that you can end up with a screwed up filesystem that might silently eat some of your data if you are not careful with all the resize stuff (but without ever seeing any warning from the tools) - that's PR #58723. A cosmetic bug in the
dfoutput I noticed has already been fixed on HEAD - PR #58718With your two new images and with the NetBSD PRs that you mentioned, it looks like both you and NetBSD itself successfully have moved beyond the inodes issue.
Normally I would try to read up on the issue before asking a question, but, maybe, if you don't mind, you could please tell me whether you think the the inodes issue might exist on my install from your older image, and how to run a quick check.
Thanks @cmeerw!
Yes, your image will be affected, a quick way to tell is to run
df -mi /In the
iAvailcolumn it will likely show something like 20 million inodes (instead of maybe 3 million), but in the1M-blockscolumn you'll likely only see around 20000 blocks (instead of maybe 24300), e.g.@cmeerw
I still have to study up, but here is the output of the
df -ml /command you suggested showing results as you predicted:I still need to try the rebuild from source. When I get a chance, I will do that and post about what happens. Trying the compile will be a lot of fun even if it doesn't work for any reason, including maybe the filesystem.
As always, thanks for your kind help!
OpenBSD 7.6 has been released.
I wish they release drivers for Raspberry Pi Zero 2 W - or atleast FreeBSD.
I have loaded up the latest NetBSD 10 template and added a new one for 9.4. Thanks again!
If you have any instructions I can follow to create qcow2 templates, I can try as well. I was given some documentation from VF to create my own, but not sure how well it will work.
linveo.com | Shared Hosting | KVM VPS | Dedicated Servers
This is what you get with a new NetBSD 10 install: