LES BSD Thread!

1567810

Comments

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    @Crab What's up in the FreeBDSD world?

    @FrankCastle And in the OpenBSD world?

    I hope everyone gets the servers they want!

  • @Not_Oles said: Before I do anything, though, I just want to double check with @cmeerw because he's been working on the NetBSD images. If there is anything that @cmeerw might want to do or check or ask me to do or check, I want to make sure that whatever @cmeerw wants is done.

    I believe your version of the image might actually just resize the partition and file system on the next reboot (that's because in the first version I didn't mount the filesystem with the "log" option).

    Later versions now use the "log" option - this is preferable, but it means that resizing (after the first boot) gets more complicated (or even dangerous).

    So I think, just try a restart of the machine and see if the filesystem gets resized.

    After that, I think it still makes sense to move to the new image to get some more useful block sizes and inode counts for the filesystem (it should get resized to the full capacity on the first boot, but further resizes won't be automatic).

    Thanked by (1)Not_Oles
  • @Not_Oles said: @FrankCastle And in the OpenBSD world?

    BTW, I actually tried booting into the OpenBSD 7.6 installer (via netboot.xyz) when it was released, but it did hang just before getting to user space.

    Thanked by (1)Not_Oles
  • @Not_Oles said:
    @FrankCastle And in the OpenBSD world?

    A new version just came out a couple weeks ago so I've been slowing upgrading all of my VMs to this latest version.

    Thanked by (1)Not_Oles
  • @cmeerw said:

    @Not_Oles said: @FrankCastle And in the OpenBSD world?

    BTW, I actually tried booting into the OpenBSD 7.6 installer (via netboot.xyz) when it was released, but it did hang just before getting to user space.

    I've upgraded a handful of my 7.5 instances to 7.6 thus far with no issues. I haven't done my Linveo VM yet but when I do if I run into any problems I'll let you know. I didn't have any problems getting 7.5 installed using netboot.xyz though so I don't expect any issues with 7.6 either.

    Thanked by (1)Not_Oles
  • Not_OlesNot_Oles Hosting ProviderContent Writer
    linveo# df -h
    Filesystem     Size   Used  Avail %Cap Mounted on
    /dev/dk2        20G    19G   1.5M  99% /
    kernfs         1.0K   1.0K     0B 100% /kern
    ptyfs          1.0K   1.0K     0B 100% /dev/pts
    procfs         4.0K   4.0K     0B 100% /proc
    tmpfs          1.0G   4.0K   1.0G   0% /tmp
    tmpfs          1.0G   4.0K   1.0G   0% /var/shm
    linveo# uptime
     7:42PM  up 2 mins, 1 user, load averages: 0.02, 0.02, 0.00
    linveo# 
    

    Rebooting from the Linveo panel worked!

    linveo# date
    Wed Oct 16 19:47:49 UTC 2024
    linveo# df -h 
    Filesystem     Size   Used  Avail %Cap Mounted on
    /dev/dk2        40G    19G    19G  49% /
    kernfs         1.0K   1.0K     0B 100% /kern
    ptyfs          1.0K   1.0K     0B 100% /dev/pts
    procfs         4.0K   4.0K     0B 100% /proc
    tmpfs          1.0G   4.0K   1.0G   0% /tmp
    tmpfs          1.0G   4.0K   1.0G   0% /var/shm
    linveo# 
    

    Inode check for @cmeerw :)

    linveo# df -mi /
    Filesystem   1M-blocks      Used     Avail %Cap      iUsed     iAvail %iCap Mounted on
    /dev/dk2         40880     19218     19617  49%     795510   39114712    1% /
    linveo# 
    

    @linveo said: I upped your VM to 50GB

    How come only 40880 1M-blocks total when @linveo increased the size to 50GB? Does using so many extra inodes somehow take up a substantial portion of the "missing" 9120 blocks?


    Since there now is more disk space and since the system still seems to be working okay, it might be fun to continue the system build, just to see whether it breaks, and, if so, where and how and why. Of course, after retrying the system build, we can go ahead and reinstall. :)

    I hope everyone gets the servers they want!

  • @Not_Oles said: How come only 40880 1M-blocks total when @linveo increased the size to 50GB? Does using so many extra inodes somehow take up a substantial portion of the "missing" 9120 blocks?

    Yes, that's the inodes/filesystem overhead (and there is a 512 MB swap partition).

    BTW, you can also look at the partitions with gpt show ld0 and dkctl ld0 listwedges

    Thanked by (1)Not_Oles
  • Not_OlesNot_Oles Hosting ProviderContent Writer

    @Not_Oles said: Uh . . . File system is full.

    Finally I got around to retrying build.sh from where the file system became full, above.

    linveo# su - tom
    linveo$ cd src
    linveo$ export CVSROOT="[email protected]:/cvsroot"
    linveo$ export CVS_RSH="ssh"
    linveo$ date
    Sat Oct 19 23:45:48 UTC 2024
    linveo$ time ./build.sh -U -u -j 2 -m amd64 -O ~/obj release
    ===> build.sh command:    ./build.sh -U -u -j 2 -m amd64 -O /home/tom/obj release
    ===> build.sh started:    Sat Oct 19 23:45:56 UTC 2024
    ===> NetBSD version:      10.99.12
    ===> MACHINE:             amd64
    ===> MACHINE_ARCH:        x86_64
    ===> Build platform:      NetBSD 10.99.12 amd64
    ===> HOST_SH:             /bin/sh
    ===> share/mk MAKECONF:   /etc/mk.conf
    ===> MAKECONF file:       /etc/mk.conf (File not found)
    ===> TOOLDIR path:        /home/tom/obj/tooldir.NetBSD-10.99.12-amd64
    ===> DESTDIR path:        /home/tom/obj/destdir.amd64
    ===> RELEASEDIR path:     /home/tom/obj/releasedir
      [ . . . ]
    

    The rebuild seems to be running okay. I will post again when it either breaks or completes.

    Thanks to @linveo for a nice VPS and for additional disk space! <3 Thanks to @cmeerw for his NetBSD images, help, and encouragement! <3

    Thanked by (1)linveo

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    Wow!

    ===> Successful make release
    ===> build.sh ended:      Sun Oct 20 00:10:23 UTC 2024
    ===> Summary of results:
             build.sh command:    ./build.sh -U -u -j 2 -m amd64 -O /home/tom/obj release
             build.sh started:    Sat Oct 19 23:45:56 UTC 2024
             NetBSD version:      10.99.12
             MACHINE:             amd64
             MACHINE_ARCH:        x86_64
             Build platform:      NetBSD 10.99.12 amd64
             HOST_SH:             /bin/sh
             share/mk MAKECONF:   /etc/mk.conf
             MAKECONF file:       /etc/mk.conf (File not found)
             TOOLDIR path:        /home/tom/obj/tooldir.NetBSD-10.99.12-amd64
             DESTDIR path:        /home/tom/obj/destdir.amd64
             RELEASEDIR path:     /home/tom/obj/releasedir
             Updated makewrapper: /home/tom/obj/tooldir.NetBSD-10.99.12-amd64/bin/nbmake-amd64
             Successful make release
             build.sh ended:      Sun Oct 20 00:10:23 UTC 2024
    ===> .
         1467.24 real       715.16 user       150.22 sys
    linveo$ 
    

    Um . . . what now?

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer
    edited October 20

    It looks like we only needed a little more space than we had.

    When we ran out of file space before the size increase:

    linveo# df -hi /
    Filesystem     Size   Used  Avail %Cap      iUsed     iAvail %iCap Mounted on
    /dev/dk2        20G    19G   1.5M  99%     795510   18952264    4% /
    linveo# 
    

    Now, after the filesystem size increase and after finishing the build:

    linveo# df -hi /
    Filesystem     Size   Used  Avail %Cap      iUsed     iAvail %iCap Mounted on
    /dev/dk2        40G    21G    17G  54%     809416   39100806    2% /
    linveo# 
    

    It's probably very simple, but I have to figure out how to install the newly built distribution and then see if the VM will reboot.

    Then we can reinstall from @cmeerw's new image to fix the inode issue.

    Hmm. I wonder if there might be a way to fix the inode issue without reinstalling the VM from the new image. Like, for example, create and move critical parts of the OS into a memory resident filesystem, then wipe and reinstall the disk based filesystem, download full NetBDSD to the new disk based filesystem, get sources, and rebuild. :)

    I hope everyone gets the servers they want!

  • edited October 20

    @Not_Oles said:
    @Crab What's up in the FreeBDSD world?

    Since everything "just works" every day and night, there's not much to report but 100% uptime across the board!

    FreeBSD 14.2 is going to arrive in early December, so that'll bring some new excitement and bunch of work to get all the systems updated, but not expecting any hiccups there.

    People have been very busy with this thread and I am super happy to see that. Thank you @linveo for providing these great resources to the community and @cmeerw for the excellent work on NetBSD!

    Also I wanted to add a tip of the day, check out this great command line utility with an awesome modern approach: https://github.com/aristocratos/bpytop

    Thanked by (1)Not_Oles
  • edited October 20

    @Not_Oles said: .. we only needed a little more space..

    Risky:

    tune2fs -m1 /dev/dk2

    ;)

    Thanked by (1)Not_Oles

    It wisnae me! A big boy done it and ran away.
    NVMe2G for life! until death (the end is nigh)

  • @Not_Oles said: It looks like we only needed a little more space than we had.

    So it would have worked with the new filesystem settings with the original disk space allocation.

    @Not_Oles said: Hmm. I wonder if there might be a way to fix the inode issue without reinstalling the VM from the new image. Like, for example, create and move critical parts of the OS into a memory resident filesystem, then wipe and reinstall the disk based filesystem, download full NetBDSD to the new disk based filesystem, get sources, and rebuild.

    Well... there is a 512 MB swap partition you could use as a temporary alternative root filesystem.

    Thanked by (1)Not_Oles
  • linveolinveo Hosting ProviderOG

    One of our awesome customers put together a guide on installing OpenBSD via ISO on our services. Take a look!

    https://btxx.org/posts/openbsd-linveo/

    Thanked by (2)AlwaysSkint Not_Oles

    linveo.com | Shared Hosting | KVM VPS | Dedicated Servers

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    Thanks @linveo! The OpenBSD install post looks great! From the above linked overview, there are links to a step-by-step walkthrough, which links to a page about setting up a desktop environment.

    I hope to try the OpenBSD install after I get NetBSD to rebuild itself as -current (done), install the newly rebuilt kernel (upcoming), and reboot (upcoming), and then install (upcoming) the already built, -current userland (done).

    @linveo If you haven't already, maybe you could kindly pass on to your customer our invitation to join us here in the LES BSD thread? Thanks again!

    I hope everyone gets the servers they want!

  • @linveo said:
    One of our awesome customers put together a guide on installing OpenBSD via ISO on our services. Take a look!

    https://btxx.org/posts/openbsd-linveo/

    Interesting, I only ever get as far as this with OpenBSD:

    scsibus6 at softraid0: 256 targets

    Not that I really want to use OpenBSD, was just curious...

    Thanked by (1)Not_Oles
  • Not_OlesNot_Oles Hosting ProviderContent Writer

    Here is moving our previous faithful and hard working kernel to "retired" status, copying the newly compiled kernel from the /obj directory to /, and adjusting the mode to match the previous kernel.

    linveo# date
    Tue Oct 22 18:55:26 UTC 2024
    linveo# pwd
    /home/tom/obj/sys/arch/amd64/compile/GENERIC
    linveo# ls -l netbsd
    -rwxr-xr-x  1 tom  users  29572928 Oct 19 23:56 netbsd
    linveo# ls -l /netbsd
    -rw-r--r--  1 root  wheel  29572760 Oct  5 00:39 /netbsd
    linveo# mv /netbsd /netbsd-old
    linveo# cp netbsd /
    linveo# ls -l /netbsd*
    -rwxr-xr-x  1 root  wheel  29572928 Oct 22 18:59 /netbsd
    -rw-r--r--  1 root  wheel  29572760 Oct  5 00:39 /netbsd-old
    linveo# chmod 644 /netbsd
    linveo# ls -l /netbsd*
    -rw-r--r--  1 root  wheel  29572928 Oct 22 18:59 /netbsd
    -rw-r--r--  1 root  wheel  29572760 Oct  5 00:39 /netbsd-old
    linveo# date; shutdown -r now
    Tue Oct 22 19:07:28 UTC 2024
    Shutdown NOW!
    shutdown: [pid 5108]
    linveo#                                                                                
    *** FINAL System shutdown message from [email protected] ***          
    System going down IMMEDIATELY                                                  
                                                                                   
                                                                                   
    
    System shutdown time has arrived
    
    About to run shutdown hooks...
    Stopping cron.
    Stopping inetd.
    Saved entropy to /var/db/entropy-file.
    Forcibly unmounting /tmp
    Forcibly unmounting /var/shm
    Removing block-type swap devices
    swapctl: removing /dev/dk1 as swap device
    Tue Oct 22 19:07:33 UTC 2024
    
    Done running shutdown hooks.
    Connection to xxx.xxx.xxx.xxx closed by remote host.
    Connection to xxx.xxx.xxx.xxx closed.
    chronos@penguin:~/servers/linveo$ 
    

    Now to reboot and hopefully come back up running our self-compiled NetBSD-current GENERIC kernel.

    Did it work? :)

    chronos@penguin:~/servers/linveo$ `head -n 1 login`
    Last login: Tue Oct 22 18:17:38 2024 from xxx.xxx.xxx.xxx
    NetBSD 10.99.12 (GENERIC) #1: Sat Oct 19 23:52:58 UTC 2024
    
    Welcome to NetBSD!
    
    We recommend that you create a non-root account and use su(1) for root access.
    linveo# date
    Tue Oct 22 19:09:54 UTC 2024
    linveo# 
    

    Next up is to install and, if changes are needed, to adjust the configuration of our newly compiled NetBSD-current userland. When the new userland has been installed, we will have reached our goal of running self-compiled NetBSD-current! All the sources will be really handy -- we can look at or change anything. If we get the userland up, then maybe we can try @AlwaysSkint's risky method of restructuring the filesystem to fix the inodes issue, or just reinstall from an ISO where the inodes issue already is fixed.

    Thanks to @linveo for the really nice VPS! <3 Thanks to @cmeerw, @AlwaysSkint and the other guys here for suggestions and for catching my mistakes. <3

    I hope everyone gets the servers they want!

  • @Not_Oles said: If we get the userland up, then maybe we can try @AlwaysSkint's risky method of restructuring the filesystem to fix the inodes issue

    You mean the tunefs -m? That won't do anything to fix the inodes issue - it only allows non-root users to use a bit more of the filesystem space.

    Thanked by (2)Not_Oles AlwaysSkint
  • @cmeerw said: tunefs -m

    My bad, I'm old skool:

    tune2fs applies only to ext[2-4] filesystems

    I tweak the superblock allocation on some filesystems to eke out a little more space
    egs. tune2fs -m0 /dev/system-backups and tune2fs -m1 /dev/system-tmp
    Typically, I don't reduce root, however.

    Thanked by (1)Not_Oles

    It wisnae me! A big boy done it and ran away.
    NVMe2G for life! until death (the end is nigh)

  • @cmeerw said:
    Interesting, I only ever get as far as this with OpenBSD:

    This is the problem with x86_64 image. Regular x86 works fine.

    Thanked by (1)Not_Oles
  • @Crab said:

    @cmeerw said:
    Interesting, I only ever get as far as this with OpenBSD:

    This is the problem with x86_64 image. Regular x86 works fine.

    https://btxx.org/posts/openbsd-linveo/ actually seems to use the amd64 image.

    Thanked by (1)Not_Oles
  • BTW, a few weeks ago I mentioned the cpuid tool - as of cpuid 20241023 my changes for NetBSD have been integrated, so it now also works on NetBSD.

    Thanked by (1)Not_Oles
  • Not_OlesNot_Oles Hosting ProviderContent Writer

    @cmeerw said:
    BTW, a few weeks ago I mentioned the cpuid tool - as of cpuid 20241023 my changes for NetBSD have been integrated, so it now also works on NetBSD.

    For convenient reference, here is a link to the mention of cpuid by @cmeerw on September 24:

    https://lowendspirit.com/discussion/comment/186451/#Comment_186451

    where @cmeerw said:

    @cmeerw said: BTW, https://www.etallen.com/cpuid.html is a very useful tool to get all that detailed CPU information - just sent the author a patch to make it compile under NetBSD.

    There are several more mentions of cpuid in additional posts which can be seen by scrolling further down on September 24.

    Congrats to @cmeerw on getting his patch accepted!

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    Reference: https://www.netbsd.org/docs/guide/en/chap-updating.html

    After what a few days ago seemed like a successful build and reboot of a new kernel,

    finally, today, I got around to trying to install the a-few-days-ago compiled userland.

    I think I am in the same /home/tom/src directory that I used to build the distribution, but some things don't seem quite right. For example, build.sh is empty.

    NetBSD 10.99.12 (GENERIC) #1: Sat Oct 19 23:52:58 UTC 2024
    
    Welcome to NetBSD!
    
    We recommend that you create a non-root account and use su(1) for root access.
    linveo# cd /home/tom
    linveo# cd src
    linveo# pwd
    /home/tom/src
    linveo# ls
    BUILDING      Successful    common        doc           lib           share         usr.sbin
    CVS           Summary       compat        etc           libexec       sys
    Makefile      UPDATING      crypto        external      regress       tests
    Makefile.inc  bin           dist          games         rescue        tools
    README.md     build.sh      distrib       include       sbin          usr.bin
    linveo# date
    Sat Oct 26 23:17:34 UTC 2024
    linveo# time ./build.sh -O ../obj -T ../tools -U install=/
            0.00 real         0.00 user         0.00 sys
    linveo# linveo# wc S*
           0       0       0 Successful
           0       0       0 Summary
           0       0       0 total
    linveo# wc build.sh 
           0       0       0 build.sh
    linveo# cat build.sh
    linveo#
    

    I do have

    linveo# pwd
    /home/tom/obj
    linveo# linveo# ls -l releasedir/amd64/binary/sets/
    total 205996
    -rw-r--r--  1 tom  users       954 Oct 20 00:10 MD5
    -rw-r--r--  1 tom  users      2637 Oct 20 00:10 SHA512
    -rw-r--r--  1 tom  users  38278856 Oct 20 00:06 base.tar.xz
    -rw-r--r--  1 tom  users  10913096 Oct 20 00:05 base32.tar.xz
    -rw-r--r--  1 tom  users  82581160 Oct 20 00:10 comp.tar.xz
    -rw-r--r--  1 tom  users    510172 Oct 20 00:06 etc.tar.xz
    -rw-r--r--  1 tom  users   2550444 Oct 20 00:06 games.tar.xz
    -rw-r--r--  1 tom  users   4143972 Oct 20 00:06 gpufw.tar.xz
    -rw-r--r--  1 tom  users   8910200 Oct 19 23:58 kern-GENERIC.tar.xz
    -rw-r--r--  1 tom  users   9135068 Oct 19 23:58 kern-GENERIC_KASLR.tar.xz
    -rw-r--r--  1 tom  users   6645472 Oct 19 23:58 kern-XEN3_DOM0.tar.xz
    -rw-r--r--  1 tom  users   2533980 Oct 19 23:58 kern-XEN3_DOMU.tar.xz
    -rw-r--r--  1 tom  users   5705380 Oct 20 00:07 man.tar.xz
    -rw-r--r--  1 tom  users   3488776 Oct 20 00:07 manhtml.tar.xz
    -rw-r--r--  1 tom  users   4167024 Oct 20 00:07 misc.tar.xz
    -rw-r--r--  1 tom  users  10104552 Oct 20 00:07 modules.tar.xz
    -rw-r--r--  1 tom  users   3517528 Oct 20 00:07 rescue.tar.xz
    -rw-r--r--  1 tom  users  15288428 Oct 20 00:08 tests.tar.xz
    -rw-r--r--  1 tom  users   1921928 Oct 20 00:08 text.tar.xz
    linveo#
    

    I think I could just go extract base, comp, etc, games, man, misc, modules, rescue, tests, and text from /. Then run postinstall and etcupdate. But, what happened to build.sh in /home/tom/src? That's the same build.sh that was used to build the kernel. Maybe the loss of the build.sh file had something to do with running out of filesystem space? Maybe something to do with the inode issue? Did I make a mistake?

    It's getting about time to reinstall. But it's fun to mess around with stuff! :)

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    Just for fun, trying again, as root, to build and install the userland.

    Reference: https://www.netbsd.org/docs/guide/en/chap-updating.html

    Build

    linveo# pwd
    /usr
    linveo# ls
    bin                             libexec                         sbin
    games                           local                           share
    include                         mdec                            src
    lib                             pkgsrc.tar.gz                   src-new-checkout-20241014.tar
    libdata                         pkgsrc.tar.gz.SHA1
    linveo# mkdir obj tools
    linveo# cd src
    linveo# date
    Mon Oct 28 03:21:24 UTC 2024
    linveo# time ./build.sh -O ../obj -T ../tools -U distribution
    ===> build.sh command:    ./build.sh -O ../obj -T ../tools -U distribution
    ===> build.sh started:    Mon Oct 28 03:21:37 UTC 2024
    ===> NetBSD version:      10.99.12
    ===> MACHINE:             amd64
    ===> MACHINE_ARCH:        x86_64
    ===> Build platform:      NetBSD 10.99.12 amd64
    ===> HOST_SH:             /bin/sh
    ===> No $TOOLDIR/bin/nbmake, needs building.
    ===> Bootstrapping nbmake
      [ . . . ]
    make distribution started at:  Mon Oct 28 03:21:47 UTC 2024
    make distribution finished at: Mon Oct 28 08:04:55 UTC 2024
    ===> Successful make distribution
    ===> build.sh ended:      Mon Oct 28 08:04:55 UTC 2024
    ===> Summary of results:
             build.sh command:    ./build.sh -O ../obj -T ../tools -U distribution
             build.sh started:    Mon Oct 28 03:21:37 UTC 2024
             NetBSD version:      10.99.12
             MACHINE:             amd64
             MACHINE_ARCH:        x86_64
             Build platform:      NetBSD 10.99.12 amd64
             HOST_SH:             /bin/sh
             No $TOOLDIR/bin/nbmake, needs building.
             Bootstrapping nbmake
             share/mk MAKECONF:   /etc/mk.conf
             MAKECONF file:       /etc/mk.conf (File not found)
             TOOLDIR path:        /usr/src/../tools
             DESTDIR path:        /usr/src/../obj/destdir.amd64
             RELEASEDIR path:     /usr/src/../obj/releasedir
             Created /usr/src/../tools/bin/nbmake
             Updated makewrapper: /usr/src/../tools/bin/nbmake-amd64
             Successful make distribution
             build.sh ended:      Mon Oct 28 08:04:55 UTC 2024
    ===> .
        16998.48 real      7004.42 user      1923.08 sys
    linveo# 
    

    Install

    linveo# date
    Mon Oct 28 16:05:05 UTC 2024
    linveo# pwd
    /usr/src
    linveo# ./build.sh -O ../obj -T ../tools -U install=/
    ===> build.sh command:    ./build.sh -O ../obj -T ../tools -U install=/
    ===> build.sh started:    Mon Oct 28 16:06:28 UTC 2024
    ===> NetBSD version:      10.99.12
    ===> MACHINE:             amd64
    ===> MACHINE_ARCH:        x86_64
    ===> Build platform:      NetBSD 10.99.12 amd64
    ===> HOST_SH:             /bin/sh
    ===> share/mk MAKECONF:   /etc/mk.conf
    ===> MAKECONF file:       /etc/mk.conf (File not found)
    ===> TOOLDIR path:        /usr/src/../tools
    ===> DESTDIR path:        /usr/src/../obj/destdir.amd64
    ===> RELEASEDIR path:     /usr/src/../obj/releasedir
    ===> Updated makewrapper: /usr/src/../tools/bin/nbmake-amd64
    installsets ===> distrib/sets   (with: INSTALLDIR=/ INSTALLSETS=)
      [ . . . ]
    obsolete check:
            Remove obsolete file /usr/lib/i386/libarchive.so.5.0
            Remove obsolete file /usr/lib/i386/libblocklist.so.0.0
            Remove obsolete file /usr/lib/i386/libbsdmalloc.so.0.0
            Remove obsolete file /usr/lib/i386/libc.so.12.220
            Remove obsolete file /usr/lib/i386/libgomp.so.2.1
            Remove obsolete file /usr/lib/i386/libm.so.0.13
            Remove obsolete file /usr/lib/i386/libsqlite3.so.1.4
            Remove obsolete file /usr/lib/i386/libstdc++.so.9.0
    postinstall checks passed: atf autofsconfig blocklist bluetooth catpages ddbonpanic defaults dhcpcd dhcpcdrundir envsys fontconfig gid gpio hosts iscsi makedev manconf motd named opensslcertsconf opensslcertsrehash pam periodic pf ptyfsoldnodes pwd_mkdb rc ssh tcpdumpchroot uid varrwho varshm wscons x11 xkb
    postinstall checks failed: mtree obsolete
    To fix, run:
        /bin/sh /usr/src/../obj/usr.sbin/postinstall/postinstall -s /usr/src -d / fix mtree obsolete
    Note that this may overwrite local changes.
       ================================
    make installworld started at:  Mon Oct 28 16:06:29 UTC 2024
    make installworld finished at: Mon Oct 28 16:17:20 UTC 2024
    ===> Successful installworld to /
    ===> build.sh ended:      Mon Oct 28 16:17:20 UTC 2024
    ===> Summary of results:
             build.sh command:    ./build.sh -O ../obj -T ../tools -U install=/
             build.sh started:    Mon Oct 28 16:06:28 UTC 2024
             NetBSD version:      10.99.12
             MACHINE:             amd64
             MACHINE_ARCH:        x86_64
             Build platform:      NetBSD 10.99.12 amd64
             HOST_SH:             /bin/sh
             share/mk MAKECONF:   /etc/mk.conf
             MAKECONF file:       /etc/mk.conf (File not found)
             TOOLDIR path:        /usr/src/../tools
             DESTDIR path:        /usr/src/../obj/destdir.amd64
             RELEASEDIR path:     /usr/src/../obj/releasedir
             Updated makewrapper: /usr/src/../tools/bin/nbmake-amd64
             Successful installworld to /
             build.sh ended:      Mon Oct 28 16:17:20 UTC 2024
    ===> .
    linveo# 
    

    Example Results In /bin

    • Before
    linveo# ls -l /bin
    total 1978
    -r-xr-xr-x  2 root  wheel   23656 Oct  2 21:21 [
    -r-xr-xr-x  1 root  wheel   23632 Oct  2 21:21 cat
    lrwxr-xr-x  1 root  wheel      11 Oct  2 21:21 chgrp -> /sbin/chown
    -r-xr-xr-x  1 root  wheel   24120 Oct  2 21:21 chio
    -r-xr-xr-x  1 root  wheel   19240 Oct  2 21:21 chmod
    -r-xr-xr-x  1 root  wheel   35504 Oct  2 21:21 cp
    -r-xr-xr-x  1 root  wheel   60576 Oct  2 21:21 cpio
    -r-xr-xr-x  1 root  wheel  194800 Oct  2 21:21 csh
    -r-xr-xr-x  1 root  wheel   29048 Oct  2 21:21 date
    -r-xr-xr-x  1 root  wheel   42936 Oct  2 21:21 dd
    -r-xr-xr-x  1 root  wheel   24400 Oct  2 21:21 df
    -r-xr-xr-x  1 root  wheel   18072 Oct  2 21:21 domainname
    -r-xr-xr-x  1 root  wheel   17864 Oct  2 21:21 echo
    -r-xr-xr-x  1 root  wheel   67736 Oct  2 21:21 ed
    -r-xr-xr-x  1 root  wheel   27480 Oct  2 21:21 expr
    -r-xr-xr-x  1 root  wheel   19536 Oct  2 21:21 getfacl
    -r-xr-xr-x  1 root  wheel   18096 Oct  2 21:21 hostname
    -r-xr-xr-x  1 root  wheel   18752 Oct  2 21:21 kill
    -r-xr-xr-x  1 root  wheel  297256 Oct  2 21:21 ksh
    -r-xr-xr-x  1 root  wheel   19232 Oct  2 21:21 ln
    -r-xr-xr-x  1 root  wheel   39768 Oct  2 21:21 ls
    -r-xr-xr-x  1 root  wheel   18688 Oct  2 21:21 mkdir
    -r-xr-xr-x  1 root  wheel   28976 Oct  2 21:21 mt
    -r-xr-xr-x  1 root  wheel   28336 Oct  2 21:21 mv
    -r-xr-xr-x  1 root  wheel  170272 Oct  2 21:21 pax
    -r-xr-xr-x  1 root  wheel   74784 Oct  2 21:21 ps
    -r-xr-xr-x  1 root  wheel   18496 Oct  2 21:21 pwd
    -r-sr-xr-x  1 root  wheel   24368 Oct  2 21:21 rcmd
    -r-xr-xr-x  1 root  wheel   33984 Oct  2 21:21 rcp
    -r-xr-xr-x  1 root  wheel   28496 Oct  2 21:21 rm
    -r-xr-xr-x  1 root  wheel   18024 Oct  2 21:21 rmdir
    -r-xr-xr-x  1 root  wheel   43624 Oct  2 21:21 rump.dd
    -r-xr-xr-x  1 root  wheel   33800 Oct  2 21:21 setfacl
    -r-xr-xr-x  1 root  wheel  241032 Oct  2 21:21 sh
    -r-xr-xr-x  1 root  wheel   18864 Oct  2 21:21 sleep
    -r-xr-xr-x  1 root  wheel   37928 Oct  2 21:21 stty
    -r-xr-xr-x  1 root  wheel   17208 Oct  2 21:21 sync
    -r-xr-xr-x  1 root  wheel   89240 Oct  2 21:21 tar
    -r-xr-xr-x  2 root  wheel   23656 Oct  2 21:21 test
    linveo# 
    
    • After
    linveo# ls -l /bin
    total 1906
    -r-xr-xr-x  2 root  wheel   22056 Oct 28 07:52 [
    -r-xr-xr-x  1 root  wheel   22024 Oct 28 07:52 cat
    lrwxr-xr-x  1 root  wheel      11 Oct 28 07:52 chgrp -> /sbin/chown
    -r-xr-xr-x  1 root  wheel   22232 Oct 28 07:52 chio
    -r-xr-xr-x  1 root  wheel   17584 Oct 28 07:52 chmod
    -r-xr-xr-x  1 root  wheel   33528 Oct 28 07:52 cp
    -r-xr-xr-x  1 root  wheel   57720 Oct 28 07:47 cpio
    -r-xr-xr-x  1 root  wheel  190856 Oct 28 07:52 csh
    -r-xr-xr-x  1 root  wheel   27264 Oct 28 07:52 date
    -r-xr-xr-x  1 root  wheel   41384 Oct 28 07:52 dd
    -r-xr-xr-x  1 root  wheel   22744 Oct 28 07:52 df
    -r-xr-xr-x  1 root  wheel   17024 Oct 28 07:52 domainname
    -r-xr-xr-x  1 root  wheel   16832 Oct 28 07:52 echo
    -r-xr-xr-x  1 root  wheel   66048 Oct 28 07:52 ed
    -r-xr-xr-x  1 root  wheel   26088 Oct 28 07:52 expr
    -r-xr-xr-x  1 root  wheel   17808 Oct 28 07:52 getfacl
    -r-xr-xr-x  1 root  wheel   17064 Oct 28 07:52 hostname
    -r-xr-xr-x  1 root  wheel   17632 Oct 28 07:52 kill
    -r-xr-xr-x  1 root  wheel  290256 Oct 28 07:52 ksh
    -r-xr-xr-x  1 root  wheel   17688 Oct 28 07:52 ln
    -r-xr-xr-x  1 root  wheel   37832 Oct 28 07:52 ls
    -r-xr-xr-x  1 root  wheel   17360 Oct 28 07:52 mkdir
    -r-xr-xr-x  1 root  wheel   27288 Oct 28 07:52 mt
    -r-xr-xr-x  1 root  wheel   26776 Oct 28 07:52 mv
    -r-xr-xr-x  1 root  wheel  165184 Oct 28 07:52 pax
    -r-xr-xr-x  1 root  wheel   71160 Oct 28 07:52 ps
    -r-xr-xr-x  1 root  wheel   17168 Oct 28 07:52 pwd
    -r-sr-xr-x  1 root  wheel   22536 Oct 28 07:52 rcmd
    -r-xr-xr-x  1 root  wheel   32096 Oct 28 07:52 rcp
    -r-xr-xr-x  1 root  wheel   26848 Oct 28 07:52 rm
    -r-xr-xr-x  1 root  wheel   16984 Oct 28 07:52 rmdir
    -r-xr-xr-x  1 root  wheel   41832 Oct 28 07:52 rump.dd
    -r-xr-xr-x  1 root  wheel   32296 Oct 28 07:52 setfacl
    -r-xr-xr-x  1 root  wheel  235616 Oct 28 07:52 sh
    -r-xr-xr-x  1 root  wheel   17536 Oct 28 07:52 sleep
    -r-xr-xr-x  1 root  wheel   36496 Oct 28 07:52 stty
    -r-xr-xr-x  1 root  wheel   16568 Oct 28 07:52 sync
    -r-xr-xr-x  1 root  wheel   85432 Oct 28 07:47 tar
    -r-xr-xr-x  2 root  wheel   22056 Oct 28 07:52 test
    linveo# 
    

    Run postinstall

    linveo# date
    Mon Oct 28 16:29:53 UTC 2024
    linveo# /bin/sh /usr/src/../obj/usr.sbin/postinstall/postinstall -s /usr/src -d / fix mtree obsolete
    Source directory: /usr/src
    Target directory: /
    mtree fix:
            Copied /tmp/_postinstall.18047.0/NetBSD.dist to /etc/mtree/NetBSD.dist
    obsolete fix:
            Removed obsolete file /usr/lib/i386/libarchive.so.5.0
            Removed obsolete file /usr/lib/i386/libblocklist.so.0.0
            Removed obsolete file /usr/lib/i386/libbsdmalloc.so.0.0
            Removed obsolete file /usr/lib/i386/libc.so.12.220
            Removed obsolete file /usr/lib/i386/libgomp.so.2.1
            Removed obsolete file /usr/lib/i386/libm.so.0.13
            Removed obsolete file /usr/lib/i386/libsqlite3.so.1.4
            Removed obsolete file /usr/lib/i386/libstdc++.so.9.0
    postinstall fixes passed: mtree obsolete
    postinstall fixes failed:
    linveo# 
    

    Run etcupdate

    Tried etcupdate for the first time, as far as I recall. It has lots of output! Left it for later.

    /usr/sbin/etcupdate -s /usr/src
    

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer
    edited October 28

    So . . . the NetBSD-current VM still reboots successfully. I want to work more on etcupdate. And everything else. But maybe we have arrived at the goal of building and running NetBSD-current. Maybe it's time to reinstall with @cmeerw's newer image that has the number of inodes fixed.

    If I rebuild NetBSD-current a few dozen more times, maybe I can start to remember to build as tom instead of root. It seems also that I can use "-j 2" with build.sh, and maybe that will decrease the build times.

    If anybody catches other mistakes that I am making, I'd be glad to learn more!

    Thanks to @linveo for a very fast, very nice VPS! <3 Thanks to NetBSD! <3 Thanks to the guys here in the LES BSD thread and to everyone else at LES! <3

    linveo# shutdown -r now
    Shutdown NOW!
    shutdown: [pid 19887]
    linveo#                                                                                
    *** FINAL System shutdown message from [email protected] ***          
    System going down IMMEDIATELY                                                  
                                                                                   
                                                                                   
    
    System shutdown time has arrived
    
    About to run shutdown hooks...
    Stopping cron.
    Stopping inetd.
    Saved entropy to /var/db/entropy-file.
    Forcibly unmounting /tmp
    Forcibly unmounting /var/shm
    Removing block-type swap devices
    swapctl: removing /dev/dk1 as swap device
    Mon Oct 28 17:14:44 UTC 2024
    
    Done running shutdown hooks.
    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` | tee -a 20241027-build.sh-usr-src
    Last login: Mon Oct 28 03:57:04 2024 from xxx.xxx.xxx.xxx
    NetBSD 10.99.12 (GENERIC) #1: Sat Oct 19 23:52:58 UTC 2024
    
    Welcome to NetBSD!
    
    We recommend that you create a non-root account and use su(1) for root access.
    linveo# date
    Mon Oct 28 17:16:24 UTC 2024
    linveo# 
    

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    How effective was adding -j 2 at reducing build.sh compile time?

    From above at https://lowendspirit.com/discussion/comment/188830/#Comment_188830 we can see that the time taken to compile the NetBSD-current distribution without any "jobs" -j flag was about 4 hours and 43 minutes:

    make distribution started at:  Mon Oct 28 03:21:47 UTC 2024
    make distribution finished at: Mon Oct 28 08:04:55 UTC 2024
    

    The procedure for investigating was that /usr/src, /usr/tools, and /usr/obj were moved aside and replaced by new versions. The new /usr/src was extracted from the same tar file as previously used without the -j 2 option.

    This time the job was run by user tom instead of by root.

    Here is the full command:

    linveo$ date; time ./build.sh -j 2 -O ../obj -T ../tools -U distribution; date

    And here is the result summary showing that make distribution took 2 hours and 57 minutes:

    make distribution started at:  Mon Oct 28 22:27:46 UTC 2024                                       
    make distribution finished at: Tue Oct 29 01:24:08 UTC 2024                                       
    ===> Successful make distribution   
    ===> build.sh ended:      Tue Oct 29 01:24:08 UTC 2024
    ===> Summary of results:
             build.sh command:    ./build.sh -j 2 -O ../obj -T ../tools -U distribution
             build.sh started:    Mon Oct 28 22:27:46 UTC 2024
             NetBSD version:      10.99.12
             MACHINE:             amd64
             MACHINE_ARCH:        x86_64
             Build platform:      NetBSD 10.99.12 amd64
             HOST_SH:             /bin/sh
             share/mk MAKECONF:   /etc/mk.conf
             MAKECONF file:       /etc/mk.conf (File not found)
             TOOLDIR path:        /usr/src/../tools
             DESTDIR path:        /usr/src/../obj/destdir.amd64
             RELEASEDIR path:     /usr/src/../obj/releasedir
             Updated makewrapper: /usr/src/../tools/bin/nbmake-amd64
             Successful make distribution
             build.sh ended:      Tue Oct 29 01:24:08 UTC 2024
    ===> .
        10582.23 real      7028.72 user      1949.24 sys
    Tue Oct 29 01:24:08 UTC 2024
    linveo$ 
    

    So, -j 2 saved 1 hour and 46 minutes or 37%. :star:

    Below is the output of top during the -j 2 compile.

    @linveo Thanks again for the fast VPS! <3 Are you happy to see this usage sustained for three of four hours at a time multiple times per week or even per day? If this usage is too much, I can go run it on a dedi, no problem at all.

    load averages:  2.27,  2.26,  2.25;               up 0+07:56:12                          01:10:49
    48 processes: 2 runnable, 45 sleeping, 1 on CPU
    CPU states: 37.2% user,  0.0% nice, 13.6% system,  0.0% interrupt, 49.1% idle
    Memory: 1749M Act, 989M Inact, 30M Exec, 2656M File, 301M Free
    Swap: 512M Total, 512M Free / Pools: 865M Used / Network: 27K In, 147K Out
    
      PID USERNAME PRI NICE   SIZE   RES STATE       TIME   WCPU    CPU COMMAND
     1276 root      85    0    22M 5532K poll/1      2:27  7.32%  7.32% sshd-session
     1503 root      85    0    22M 7964K kqueue/1    2:02  0.00%  0.00% tmux
        0 root     222    0     0K   37M icmp_w/0    0:31  0.00%  0.00% [system]
    29144 tom       85    0    13M 2672K poll/1      0:17  0.00%  0.00% nbmake
    24027 tom       85    0    13M 2692K poll/1      0:14  0.00%  0.00% nbmake
    18380 tom       85    0    13M 2660K poll/1      0:04  0.00%  0.00% nbmake
    18271 tom       85    0    13M 2660K poll/1      0:03  0.00%  0.00% nbmake
    10561 root      43    0    13M 2248K CPU/0       0:00  0.00%  0.00% top
      870 tom       35    0    54M   21M RUN/0       0:00  0.00%  0.00% cc1
    23446 tom        0    0     0K    0K RUN/0       0:00  0.00%  0.00% sh
    29499 root      85    0    22M 6404K poll/1      0:00  0.00%  0.00% sshd-session
     1272 root      85    0    22M 6216K poll/1      0:00  0.00%  0.00% sshd-session
    23336 root      85    0    26M 4612K poll/0      0:00  0.00%  0.00% sshd-session
     6524 postfix   85    0    21M 4576K kqueue/0    0:00  0.00%  0.00% pickup
     1100 postfix   85    0    21M 4520K kqueue/0    0:00  0.00%  0.00% qmgr
    

    I hope everyone gets the servers they want!

  • linveolinveo Hosting ProviderOG

    @Not_Oles said:

    @linveo Thanks again for the fast VPS! <3 Are you happy to see this usage sustained for three of four hours at a time multiple times per week or even per day? If this usage is too much, I can go run it on a dedi, no problem at all.

    I am happy when people are using the VMs for a good purpose like this!

    Thanked by (1)Not_Oles

    linveo.com | Shared Hosting | KVM VPS | Dedicated Servers

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    Reinstalled with NetBSD 10 image.

    Thanks to @cmeerw for creating the image! <3 Thanks to @linveo for making @cmeerw's NetBSD 10 image available! <3

    Note the significant change in inodes available.

    Formerly:

    @Not_Oles said:

    linveo# df -mi /
    Filesystem   1M-blocks      Used     Avail %Cap      iUsed     iAvail %iCap Mounted on
    /dev/dk2         40880     19218     19617  49%     795510   39114712    1% /
    linveo# 
    

    After NetBSD 10 reinstall:

    linveo# df -mi /
    Filesystem   1M-blocks      Used     Avail %Cap      iUsed     iAvail %iCap Mounted on
    /dev/dk2         49133       465     46211   0%      15723    6281875    0% /
    linveo# 
    
    Thanked by (1)AlwaysSkint

    I hope everyone gets the servers they want!

  • Hi bsd guys, new freebsd user here, taking advantage of Linveo's offer to learn a little FreeBSD and soon OpenBSD.

    I have a question: which firewall should I use when learning freebsd? I have read the documentation and I see that there are at least 3 firewalls available. However, I don't know which one is recommended for FreeBSD, or which one is used by most people who use FreeBSD. At the moment I am learning PF firewall since I see that if I am not mistaken it is the one used by PFSense and the one that seems to me to be the most used among the FreeBSD community, however, since it is developed for OpenBSD, I do not know if it is the most indicated to use in FreeBSD.

    My doubt here is really which is the firewall that integrates better with the operating system?

    Ruby, JS Programmer and Linux user

Sign In or Register to comment.