resflash issueshttps://gitlab.com/bconway/resflash/-/issues2023-03-03T17:06:57Zhttps://gitlab.com/bconway/resflash/-/issues/27Add SSH Instructions2023-03-03T17:06:57Zkeith ScottAdd SSH InstructionsNew user to resflash and am planning on converting my obsd firewall and nas over to resflash.
I have created a bootable usb disk and have be able to get my /etc/hostname,myname,mygate files into /cfg/etc then reboot and after the box re...New user to resflash and am planning on converting my obsd firewall and nas over to resflash.
I have created a bootable usb disk and have be able to get my /etc/hostname,myname,mygate files into /cfg/etc then reboot and after the box restarts my networking is good. But I am stuck trying to add a user (for ssh) to the box as I don't want to ssh in as root. Below is where I've got to.
useradd bob
passwd bob
nano /etc/group
Added bob to wheel
mount /cfg
cp /etc/passwd /etc/group /etc/pwd.db /etc/spwd.db /cfg
umount /cfg
reboot
Then I try and login, but it's hasn't worked, and If I login as root and remove my user and add it again, I've managed to block root from being able to login, I will try adding the whole /etc/ folder to /cfg/etc but if your able to help, then it would be appreciated.
Thankshttps://gitlab.com/bconway/resflash/-/issues/26write failed, file system is full2023-02-24T10:42:22ZKarsten Horsmannwrite failed, file system is fullHi Brian,
i run that command with latest resflash (master 5fbeafa50214e94b8f0f181997b25e62fc473f11) tools and i got evertime an error in the generated images. Build runs without error.
System flashed and afterwards its unusable cause it...Hi Brian,
i run that command with latest resflash (master 5fbeafa50214e94b8f0f181997b25e62fc473f11) tools and i got evertime an error in the generated images. Build runs without error.
System flashed and afterwards its unusable cause it breaks on Relocating on boot.
build command:
`build_resflash.sh --pkg_path https://cloudflare.cdn.openbsd.org/pub/OpenBSD/7.2/packages/amd64/ --pkg_list autossh--,bash--,curl--,darkstat--,dhcpcd--,dnsmasq--,git--,gmake--,iftop--,joe--,vim--no_x11,libssh2--,miniupnpd--,nmap--,pftop--,rsync--,python3,xz--,ddclient--,sngrep--,ngrep-- -s 115200 --syspatch 4836 /home/karsten/rdest`
bootlog:
```
root on sd0d (5c813e4be8f16aee.d) swap on sd0b dump on sd0b
Automatic boot in progress: starting file system checks.
/dev/sd0d (5c813e4be8f16aee.d): file system is clean; not checking
/dev/sd0a (5c813e4be8f16aee.a): file system is clean; not checking
/dev/sd0f (5c813e4be8f16aee.f): file system is clean; not checking
resflash: Relocating /dev /etc /varfd0 at fdc0 drive 1: density unknown
/usr/libuid 0 on /tmp/resflash.2ZOjt5: file system full
/tmp/resflash.2ZOjt5: write failed, file system is full
tar: End of archive volume 1 reached
pf enabled
starting network
reordering libraries: done.
openssl: generating isakmpd RSA keys... done.
openssl: generating iked ECDSA keys... done.
ssh-keygen: generating new host keys: RSA ECDSA ED25519
starting early daemons: syslogd pflogd ntpd.
starting RPC daemons:.
savecore: /dev/sd0b: Device not configured
checking quotas: done.
clearing /tmp
rm: resflash.2ZOjt5: Device busy
rm: resflash.2ZOjt5: Device busy
```https://gitlab.com/bconway/resflash/-/issues/25Skipping releases when upgrading?2022-12-22T22:29:39ZGSISkipping releases when upgrading?For example, is 6.9 -> 7.2 possible?
I know that vanilla OpenBSD doesn't support this, but I was unable to find any info specific to resflash.For example, is 6.9 -> 7.2 possible?
I know that vanilla OpenBSD doesn't support this, but I was unable to find any info specific to resflash.https://gitlab.com/bconway/resflash/-/issues/24resflash (partially?) fails when using --syspatch flag with OpenBSD 7.12022-12-20T19:30:12ZRyan Freemanresflash (partially?) fails when using --syspatch flag with OpenBSD 7.1Hi, thanks for your work on this tooling, it seems quite nifty. I am working on figuring a way to work resflash tooling in with my own tooling I have managing configs for several dozen different machines for $WORKPLACE.
It seems resfla...Hi, thanks for your work on this tooling, it seems quite nifty. I am working on figuring a way to work resflash tooling in with my own tooling I have managing configs for several dozen different machines for $WORKPLACE.
It seems resflash is bit by the same problem that bit me when writing some rset-powered system upgrade helpers: syspatch on 7.1 will only install the first errata, then issue a message warning that it needs to be run again to fetch the remaining patches with exit code 2.
```
openbsd71-build-amd64# ./resflash/build_resflash.sh -s 115200 --swap 128 --syspatch 4088 /u/rdest
resflash 7.1.0
Validating OpenBSD base dir: /u/rdest
Creating disk image: resflash-amd64-4088MB-com0_115200-20221018_1201.img (2s)
Creating filesystem: resflash-amd64-4088MB-com0_115200-20221018_1201.fs (1s)
Populating filesystem and configuring fstab
Running fw_update (0s)
Populating kernel relink and running syspatch
*** WARNING: Syspatch failed, check /tmp/resflash.7gWLbY/02.mkchroot.02.syspatch for connectivity and version compatibility. ***
(88s)
Populating filesystem complete (126s)
Writing filesystem to disk image and calculating filesystem checksum (150s)
Calculating disk image checksum (97s)
Build complete! (377s)
File sizes:
1.9G resflash-amd64-4088MB-com0_115200-20221018_1201.fs
4.0G resflash-amd64-4088MB-com0_115200-20221018_1201.img
Disk usage:
1.2G resflash-amd64-4088MB-com0_115200-20221018_1201.fs
1.9G resflash-amd64-4088MB-com0_115200-20221018_1201.img
```
contents of /tmp/resflash.7gWLbY/02.mkchroot.02.syspatch:
```
Installing patch 001_wifi
syspatch: updated itself, run it again to install missing patches
Relinking to create unique kernel... done; reboot to load the new kernel
```
The rset tooling (scriptedconfiguration.org) I put together for update automation of regular OpenBSD installs uses the following little `syspatch-helper` script to scoot the issue:
```
#!/bin/ksh
#
# keep running syspatch until it succeeds.
# also re-run if syspatch updates itself.
#
# exit code 1: reorder_kernel still running, sleep and try again
# exit code 2: syspatch updated itself, and should run again.
# exit code 0: syspatch finished patching and there are no more patches.
#
# NOTE: syspatch also exits with code 2 if there aren't any more patches.
# skirt the issue by first checking "syspatch -c" for output.
#
check=$(doas syspatch -c)
[[ -z $check ]] && exit 0
exitcode=3
while (($exitcode > 0)); do
doas syspatch
exitcode=$?
(($exitcode == 1)) && sleep 5
done
echo "$check" > /tmp/syspatch.new
```
I set out to see if i could make `mkchroot.sh` do something similar to my helper script, but retaining error output logs if bad things happen (repeatedly). I set a failsafe threshold to a magic value of '5'.
```
49 # start at 3, syspatch does not utilize 3 (yet)
50 # failsafe is to let the script still fail if syspatch somehow
51 # tries to re-run indefinitely with exitcode 2.
52 SYSPEXIT=3 failsafe=0
53 while [[ ${SYSPEXIT} -gt 0 ]]; do
54 if ! chroot ${BUILDPATH}/fs syspatch >> \
55 ${BUILDPATH}/02.mkchroot.02.syspatch 2>&1; then
56 SYSPEXIT=$?
57 else
58 SYSPEXIT=0
59 fi
60 # specifically check for exit value '2' here, we shouldn't see '1' at all
61 # (relink still running)
62 [[ ${SYSPEXIT} -eq 2 ]] && let failsafe++
63 if [[ ${failsafe} -ge 5 ]]; then
64 ${ESCECHO} "\n*** WARNING: Syspatch failed, check" \
65 "${BUILDPATH}/02.mkchroot.02.syspatch for connectivity and version" \
66 "compatibility. ***"
67 break
68 fi
69 done
```
I got really bound up by trying to run the `chroot ${BUILDPATH}/fs syspatch ...` bit without the if statement and just capturing the exit code. Once I realized this and reinstated the `if !..` for that line, hardcoding SYSPEXIT to 0 on success, it works!
```
openbsd71-build-amd64# ./resflash/build_resflash.sh -s 115200 --swap 128 --syspatch 4088 /u/rdest
resflash 7.1.0
Validating OpenBSD base dir: /u/rdest
Creating disk image: resflash-amd64-4088MB-com0_115200-20221018_1541.img (3s)
Creating filesystem: resflash-amd64-4088MB-com0_115200-20221018_1541.fs (0s)
Populating filesystem and configuring fstab
Running fw_update (0s)
Populating kernel relink and running syspatch (86s)
Populating filesystem complete (127s)
Writing filesystem to disk image and calculating filesystem checksum (108s)
Calculating disk image checksum (123s)
Build complete! (362s)
File sizes:
1.9G resflash-amd64-4088MB-com0_115200-20221018_1541.fs
4.0G resflash-amd64-4088MB-com0_115200-20221018_1541.img
Disk usage:
1.2G resflash-amd64-4088MB-com0_115200-20221018_1541.fs
1.9G resflash-amd64-4088MB-com0_115200-20221018_1541.img
```
here is a diff if you like this approach, thanks!
```
diff --git a/mkchroot.sh b/mkchroot.sh
index 9906b1a..b34bb8d 100644
--- a/mkchroot.sh
+++ b/mkchroot.sh
@@ -59,12 +59,27 @@ if [ -n "${syspatch+1}" ]; then
cp ${BUILDPATH}/fs/usr/share/relink/kernel/${KERNEL}/relink.log \
${BUILDPATH}/02.mkchroot.01.relink
- if ! chroot ${BUILDPATH}/fs syspatch >> \
- ${BUILDPATH}/02.mkchroot.02.syspatch 2>&1; then
- ${ESCECHO} "\n*** WARNING: Syspatch failed, check" \
- "${BUILDPATH}/02.mkchroot.02.syspatch for connectivity and version" \
- "compatibility. ***"
- fi
+ # start at 3, syspatch does not utilize 3 (yet)
+ # failsafe is to let the script still fail if syspatch somehow
+ # tries to re-run indefinitely with exitcode 2.
+ SYSPEXIT=3 failsafe=0
+ while [[ ${SYSPEXIT} -gt 0 ]]; do
+ if ! chroot ${BUILDPATH}/fs syspatch >> \
+ ${BUILDPATH}/02.mkchroot.02.syspatch 2>&1; then
+ SYSPEXIT=$?
+ else
+ SYSPEXIT=0
+ fi
+ # specifically check for exit value '2' here, we shouldn't see '1' at all
+ # (relink still running)
+ [[ ${SYSPEXIT} -eq 2 ]] && let failsafe++
+ if [[ ${failsafe} -ge 5 ]]; then
+ ${ESCECHO} "\n*** WARNING: Syspatch failed, check" \
+ "${BUILDPATH}/02.mkchroot.02.syspatch for connectivity and version" \
+ "compatibility. ***"
+ break
+ fi
+ done
rm ${BUILDPATH}/fs/var/db/kernel.SHA256
echo " ($(($(date +%s) - st))s)"
fi
```https://gitlab.com/bconway/resflash/-/issues/23Expand to whole disk size2022-02-15T19:39:10ZIvo MarinoExpand to whole disk sizeHi there, just wondering if there is any way to expand the rootfs to the whole disk size? Currently running an img which has been flashed directly to a 8GB CF card, not all the "disk space" seems to be used. Thanks for feedbackHi there, just wondering if there is any way to expand the rootfs to the whole disk size? Currently running an img which has been flashed directly to a 8GB CF card, not all the "disk space" seems to be used. Thanks for feedbackhttps://gitlab.com/bconway/resflash/-/issues/22recent updates to fw_update to support multiarch causing fw_update to fail in...2022-02-22T18:48:24Zhazel limarecent updates to fw_update to support multiarch causing fw_update to fail in mkchroot.shthis line of code in a recent update to /usr/sbin/fw_update to derive VTYPE is causing
mkchroot.sh to fail with sed: 0: /var/run/dmesg.boot: No such file or directory
which of course has NOT been created at this point..(system never ...this line of code in a recent update to /usr/sbin/fw_update to derive VTYPE is causing
mkchroot.sh to fail with sed: 0: /var/run/dmesg.boot: No such file or directory
which of course has NOT been created at this point..(system never has booted)
for a workaround and since I am NOT cross building I will simply copy said file from the build host into the chroot as a workaround) but needs a better solution I feel..
VTYPE=$( sed -n "/^OpenBSD $VNAME\([^ ]*\).*$/s//\1/p" \
/var/run/dmesg.boot | sed '$!d' )
[[ $VTYPE == -!(stable) ]] && HTTP_FWDIR=snapshotshttps://gitlab.com/bconway/resflash/-/issues/21Maybe add ‘syspatch’ to the image build process?2021-12-13T19:13:15ZBrian CervenkaMaybe add ‘syspatch’ to the image build process?I can do a PR but was just wondering if there’s a philosophical reason to not.
It seems that where the build script does fw_update, it should also do a syspatch?I can do a PR but was just wondering if there’s a philosophical reason to not.
It seems that where the build script does fw_update, it should also do a syspatch?https://gitlab.com/bconway/resflash/-/issues/20Dead link in README.md2021-02-03T22:23:41ZnebDead link in README.mdThe BSD Now episode link is dead.
The episode can be found on [Jupiter Broadcasting](https://www.jupiterbroadcasting.com/85542/bsd-gnow-bsd-now-99/) and [YouTube](https://www.youtube.com/watch?v=2TePV1AdsqI&t=177)The BSD Now episode link is dead.
The episode can be found on [Jupiter Broadcasting](https://www.jupiterbroadcasting.com/85542/bsd-gnow-bsd-now-99/) and [YouTube](https://www.youtube.com/watch?v=2TePV1AdsqI&t=177)https://gitlab.com/bconway/resflash/-/issues/19Tracking issue for tar process hung in needbuf/D state, requiring hard reboot2021-11-19T21:16:37ZBrian ConwayTracking issue for tar process hung in needbuf/D state, requiring hard rebootBackground:
https://marc.info/?l=openbsd-bugs&m=156412299418191
https://marc.info/?l=openbsd-bugs&m=159181442320329Background:
https://marc.info/?l=openbsd-bugs&m=156412299418191
https://marc.info/?l=openbsd-bugs&m=159181442320329https://gitlab.com/bconway/resflash/-/issues/18Failed to build i386 images on amd642020-06-15T02:04:15ZVanja CvelbarFailed to build i386 images on amd64I'm trying to build an i386 image on amd64.
When the script tries to run usermod to set the root password from the chroot it fails with
`chroot: usermod: Exec format error`
I guess that the i386 binary from the image can not be run on ...I'm trying to build an i386 image on amd64.
When the script tries to run usermod to set the root password from the chroot it fails with
`chroot: usermod: Exec format error`
I guess that the i386 binary from the image can not be run on the host.
`# tar zxfph ../../OpenBSD/6.7/i386/base67.tgz`
`# cp ../../OpenBSD/6.7/i386/bsd ./`
`# tar zxfph var/sysmerge/etc.tgz`
`# cd ../..`
`# ./build_resflash.sh -s 115200 1200 projects/i386`
`resflash 6.7.1`
`Validating OpenBSD base dir: projects/i386`
`Creating disk image: resflash-i386-1200MB-com0_115200-20200605_1236.img`
`Creating filesystem: resflash-i386-1200MB-com0_115200-20200605_1236.fs`
`Populating filesystem and configuring fstab`
`chroot: usermod: Exec format error`
`*** Error encountered. BUILDPATH: /tmp/resflash.YftaZ1 ***`
`# uname -psrv`
`OpenBSD 6.7 GENERIC#1 amd64`
`# cd projects/i386/`
`# ./usr/sbin/usermod`
`./usr/sbin/usermod[1]: syntax error: `(' unexpected` `https://gitlab.com/bconway/resflash/-/issues/17fw_update fails in Vagrant VirtualBox2020-06-08T01:36:01ZJim Dennisfw_update fails in Vagrant VirtualBoxAttempting to build resflash images from within the Vagrant generic/openbsd6 (https://app.vagrantup.com/generic/boxes/openbsd6) virtual machine, running under VirtualBox on a MacPro (MacOS Cataline version 10.15.2) when I run: `../resfla...Attempting to build resflash images from within the Vagrant generic/openbsd6 (https://app.vagrantup.com/generic/boxes/openbsd6) virtual machine, running under VirtualBox on a MacPro (MacOS Cataline version 10.15.2) when I run: `../resflash/build_resflash.sh -s 115200 2048 ./base` it dies while running `fw_update`; the contents of `/home/tmp/resflash.J12ciU/02.mkchroot.03.pkg_add.pkg_list`:
```
Bad system call (core dumped)
```
Commenting out the clause in `mkchroot.sh` related to `fw_update` seems to resolve that issue. (I could not find documentation on using the "skip" mode alluded to in the comments).https://gitlab.com/bconway/resflash/-/issues/16Use new boot loader for octeon2020-06-08T01:37:27ZChristian GutUse new boot loader for octeonI try to use this project to build a router on octeon devices. I am a little bit turned down by the need for creating custom kernels for the different root partitions. This eliminates one of the arguments against ram disk kernels for me....I try to use this project to build a router on octeon devices. I am a little bit turned down by the need for creating custom kernels for the different root partitions. This eliminates one of the arguments against ram disk kernels for me.
In the next OpenBSD release 6.6 there will be a new boot loader (based on a normal kernel), that allows boot.conf to be used. Would this enable us to put "boot" (the boot loader "kernel") into the fat filesystem and then using boot.conf to select either sd0d or sd0e as boot and root device?
Not sure if this is the right place for discussion. Let me know if you want to divert this to email before.https://gitlab.com/bconway/resflash/-/issues/15add support for dependency resolution with pkg_dir2019-06-25T15:03:28ZMaarten Lippmannadd support for dependency resolution with pkg_dirI've a system I'm building with backuppc, which requires samba to back up CIFS/SMB shares. That samba has to be compiled with libarchive (so can't be pulled precompiled from a package repo) to work with backuppc.
If I create a directo...I've a system I'm building with backuppc, which requires samba to back up CIFS/SMB shares. That samba has to be compiled with libarchive (so can't be pulled precompiled from a package repo) to work with backuppc.
If I create a directory with the custom compiled samba package and use -p, resflash fails because it can't find dependencies. I don't want to have to find all samba and backuppc dependencies and ftp them down by hand and put them in a directory (or even worse compile them all by hand), that's what pkg_add is for.
My suggestion is to leverage pkg_path when provided in combination with pkg_dir. When that's done, first the packages are installed from pkg_dir, their dependencies fetched with pkg_path if needed, and any additional needed packages are later installed in case the pkg_list flag is also provided. I was able to make this work, suggested diff below.
Here's a command line example for this scenario. Only the locally compiled samba package is in /usr/rpkg. The additional pkg_path helps get all dependencies for it, and backuppc and its dependencies are then fetched through the -pkg-list flag
```
./build_resflash.sh -p /usr/rpkg --pkg_path https://cdn.openbsd.org/pub/OpenBSD/6.5/packages/amd64/ --pkg_list backuppc -s 115200 3814 /usr/release/
```
I changed the pkgdir if statement to add a check in case there is also a pkg_path.
Suggested code change:
```
# Install packages from pkgdir, if directed
if [ -n "${pkgdir+1}" ]; then
echo "Installing packages: ${pkgdir}"
mkdir -p ${BUILDPATH}/fs/tmp/pkg
cp ${pkgdir}/*.tgz ${BUILDPATH}/fs/tmp/pkg
if [ -n "${pkgpath+1}" ]; then
echo 'nameserver 8.8.8.8' >> ${BUILDPATH}/fs/etc/resolv.conf
echo 'lookup file bind' >> ${BUILDPATH}/fs/etc/resolv.conf
echo "Package path provided: ${pkgpath}"
if ! chroot ${BUILDPATH}/fs sh -c "env PKG_PATH=${pkgpath} pkg_add -v -D unsigned /tmp/pkg/*.tgz" \
>> ${BUILDPATH}/02.mkchroot.01.pkg_add.pkgdir 2>&1; then
echo "*** WARNING: Package installation failed, check" \
"${BUILDPATH}/02.mkchroot.01.pkg_add.pkgdir for binary compatibility. ***"
fi
else
if ! chroot ${BUILDPATH}/fs sh -c 'pkg_add -v -D unsigned /tmp/pkg/*.tgz' \
>> ${BUILDPATH}/02.mkchroot.01.pkg_add.pkgdir 2>&1; then
echo "*** WARNING: Package installation failed, check" \
"${BUILDPATH}/02.mkchroot.01.pkg_add.pkgdir for binary compatibility. ***"
fi
fi
fi
```
relevant diff:
```
59,63c59,73
<
< if ! chroot ${BUILDPATH}/fs sh -c 'pkg_add -v -D unsigned /tmp/pkg/*.tgz' >> \
< ${BUILDPATH}/02.mkchroot.01.pkg_add.pkgdir 2>&1; then
< echo "*** WARNING: Package installation failed, check" \
< "${BUILDPATH}/02.mkchroot.01.pkg_add.pkgdir for binary compatibility. ***"
---
> if [ -n "${pkgpath+1}" ]; then
> echo 'nameserver 8.8.8.8' >> ${BUILDPATH}/fs/etc/resolv.conf
> echo 'lookup file bind' >> ${BUILDPATH}/fs/etc/resolv.conf
> echo "Package path provided: ${pkgpath}"
> if ! chroot ${BUILDPATH}/fs sh -c "env PKG_PATH=${pkgpath} pkg_add -v -D unsigned /tmp/pkg/*.tgz" \
> >> ${BUILDPATH}/02.mkchroot.01.pkg_add.pkgdir 2>&1; then
> echo "*** WARNING: Package installation failed, check" \
> "${BUILDPATH}/02.mkchroot.01.pkg_add.pkgdir for binary compatibility. ***"
> fi
> else
> if ! chroot ${BUILDPATH}/fs sh -c 'pkg_add -v -D unsigned /tmp/pkg/*.tgz' \
> >> ${BUILDPATH}/02.mkchroot.01.pkg_add.pkgdir 2>&1; then
> echo "*** WARNING: Package installation failed, check" \
> "${BUILDPATH}/02.mkchroot.01.pkg_add.pkgdir for binary compatibility. ***"
> fi
```
EDIT:
corrected some markdown formatting.https://gitlab.com/bconway/resflash/-/issues/14Some more clarification on usage for non BSD users2019-01-30T14:03:27ZMatthew HipwellSome more clarification on usage for non BSD usersHi,
I am trying to use your script to prolong the life of my 12 year old Via C3 based firewall/router after support for 32 bit architectures was dropped by PFsense.
I am a Linux user, not familiar with BSD and am struggling to set up ...Hi,
I am trying to use your script to prolong the life of my 12 year old Via C3 based firewall/router after support for 32 bit architectures was dropped by PFsense.
I am a Linux user, not familiar with BSD and am struggling to set up the build environment, and work out how to use the /cfg directory to configure the machine post install. I have successfully run the generic image on the firewall and should be able to configure it once I work out what the what the read only file system workflow is, but I would prefer to build and maintain a simple image myself. Most of my confusion is from the steep learning curve involved in learning how BSD does things, for this single use case.
It would help me if you could clarify in your usage section:
1. That script is to be run on a working OpenBSD system.
2. What is meant by "Create an OpenBSD base directory with a minimum of the following" ie. what is "`bsd` (sp or mp supported)" and where can it be obtained and the same with the two following items.
3. An example directory structure of item 2.
The above would help me muddle through, but ideally a real world example of the procedure of creating an image for a specific use case, with packages preinstalled and configured would help me understand the build process properly.
Cheers, Mathttps://gitlab.com/bconway/resflash/-/issues/13shutdown -h -p now fails due to unveil error2019-10-21T01:22:23ZPaul Suhshutdown -h -p now fails due to unveil errorTrying to do "shutdown -h -p now" fails with error message
shutdown: unveil: Read-Only file system
This may be due to the bug here:
https://marc.info/?l=openbsd-bugs&m=154056998503006&w=2
This looks like an OpenBSD bug rather than a ...Trying to do "shutdown -h -p now" fails with error message
shutdown: unveil: Read-Only file system
This may be due to the bug here:
https://marc.info/?l=openbsd-bugs&m=154056998503006&w=2
This looks like an OpenBSD bug rather than a resflash bug, but at the same time GENERIC doesn't support a RO file system. Anyway I wanted to file it so that there's some visibility to resflash users.https://gitlab.com/bconway/resflash/-/issues/12Installation of python3.6 needs wxallowed on filesystem.2018-10-05T15:11:23ZKarsten HorsmannInstallation of python3.6 needs wxallowed on filesystem.How can i used "wxallowed" as option to resflash?
```shell
pkg_add 'python%3.6'
python3: Permission denied
tail -f /var/log/message
/usr/local/bin/python3(30591): W^X binary outside wxallowed mountpoint
mount -u -o wxallowed /
python3
P...How can i used "wxallowed" as option to resflash?
```shell
pkg_add 'python%3.6'
python3: Permission denied
tail -f /var/log/message
/usr/local/bin/python3(30591): W^X binary outside wxallowed mountpoint
mount -u -o wxallowed /
python3
Python 3.6.4 (default, Mar 27 2018, 09:58:38)
[GCC 4.2.1 Compatible OpenBSD Clang 5.0.1 (tags/RELEASE_501/final)] on openbsd6
Type "help", "copyright", "credits" or "license" for more information.
```
https://www.openbsd.org/faq/upgrade60.htmlhttps://gitlab.com/bconway/resflash/-/issues/11Idea / Feature Request - Support for arm642021-12-09T22:11:12ZKarsten HorsmannIdea / Feature Request - Support for arm64Hello,
i play around with an Pine64 Rock64. Would be nice to see if resflash could support this.
I tried OpenBSD 6.3-current cos my Rock64 had otherwise no lan interface. Works now.
Whats your opinion on this? I would try to supply a p...Hello,
i play around with an Pine64 Rock64. Would be nice to see if resflash could support this.
I tried OpenBSD 6.3-current cos my Rock64 had otherwise no lan interface. Works now.
Whats your opinion on this? I would try to supply a patch or test it on Pine64 Rock64 and Raspberry Pi 3.
http://dmesgd.nycbug.org/index.cgi?do=view&id=3616https://gitlab.com/bconway/resflash/-/issues/10How to use syspatch (in build or within image) process?2021-11-29T15:18:41ZKarsten HorsmannHow to use syspatch (in build or within image) process?I build my resflash images from the normal OpenBSD 6.3 installations.
So normaly the could be upgradable via syspatch(8).
On my router with resflash it told me "Read-only filesystem, aborting"
Okay, parts of it are in MFS - thats also ...I build my resflash images from the normal OpenBSD 6.3 installations.
So normaly the could be upgradable via syspatch(8).
On my router with resflash it told me "Read-only filesystem, aborting"
Okay, parts of it are in MFS - thats also "bad".
Any ideas?
`
# mount -rw /
[r1:~]
# mount
/dev/sd0d on / type ffs (local, noatime, nodev)
mfs:6415 on /tmp type mfs (asynchronous, local, noatime, nodev, nosuid, size=655 36 512-blocks)
mfs:85784 on /dev type mfs (asynchronous, local, noatime, noexec, size=12288 512 -blocks)
mfs:32489 on /etc type mfs (asynchronous, local, noatime, nodev, nosuid, size=13 3120 512-blocks)
mfs:93233 on /var type mfs (asynchronous, local, noatime, nodev, noexec, size=13 1072 512-blocks)
mfs:35488 on /usr/lib type mfs (asynchronous, local, noatime, nodev, nosuid, siz e=100352 512-blocks)
mfs:3325 on /usr/libexec type mfs (asynchronous, local, noatime, nodev, size=122 88 512-blocks)
[r1:~]
# syspatch -c
001_perl
002_libtls
005_httpd
[r1:~]
# syspatch
Get/Verify syspatch63-001_perl.tgz 100% |***************| 4922 KB 00:01
Installing patch 001_perl
Read-only filesystem, aborting
[r1:~]
`https://gitlab.com/bconway/resflash/-/issues/9resflash i386 / PCEngines alix2d13 OpenBSD 6.3 kernel panic on reboot - ALIX....2018-05-02T10:32:43ZKarsten Horsmannresflash i386 / PCEngines alix2d13 OpenBSD 6.3 kernel panic on reboot - ALIX.2 v0.99mMy old router (runs before flashrd over years) dont like to reboot with OpenBSD / resflash.
shutdown -r now works.
tinybios is latest afaik.
`OpenBSD 6.3-stable (GENERIC) #2: Sun Apr 22 00:39:58 UTC 2018
...My old router (runs before flashrd over years) dont like to reboot with OpenBSD / resflash.
shutdown -r now works.
tinybios is latest afaik.
`OpenBSD 6.3-stable (GENERIC) #2: Sun Apr 22 00:39:58 UTC 2018
Welcome to OpenBSD: The proactively secure Unix-like operating system.
Please use the sendbug(1) utility to report bugs in the system.
Before reporting a bug, please try to reproduce it with the latest
version of the code. With bug reports, please try to ensure that
enough information to reproduce the problem is enclosed, and if a
known fix for it exists, include that as well.
You have mail.
# reboot
resflash: Saving /etc files
syncing disks... panic: unmount: dangling vnode
Stopped at db_enter+0x4: popl %ebp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*355471 65038 0 0x3 0 0 reboot
db_enter() at db_enter+0x4
panic() at panic+0xcc
dounmount_leaf(d17db800,80000,f37b2704) at dounmount_leaf+0x128
dounmount(d17db800,80000,f37b2704) at dounmount+0xb6
vfs_unmountall() at vfs_unmountall+0x85
vfs_shutdown(f37b2704) at vfs_shutdown+0x34
boot(0) at boot+0x48
__stack_smash_handler(0,f35fe3ec) at __stack_smash_handler
sys_reboot(f37b2704,f35fe3b8,f35fe3b0) at sys_reboot+0x1e
syscall() at syscall+0x1a0
--- syscall (number -813791088) ---
end of kernel
0x7:
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports. Insufficient info makes it difficult to find and fix bugs.
ddb> trace
db_enter() at db_enter+0x4
panic() at panic+0xcc
dounmount_leaf(d17db800,80000,f37b2704) at dounmount_leaf+0x128
dounmount(d17db800,80000,f37b2704) at dounmount+0xb6
vfs_unmountall() at vfs_unmountall+0x85
vfs_shutdown(f37b2704) at vfs_shutdown+0x34
boot(0) at boot+0x48
__stack_smash_handler(0,f35fe3ec) at __stack_smash_handler
sys_reboot(f37b2704,f35fe3b8,f35fe3b0) at sys_reboot+0x1e
syscall() at syscall+0x1a0
--- syscall (number -813791088) ---
end of kernel
0x7:
ddb> show uvm
Current UVM status:
pagesize=4096 (0x1000), pagemask=0xfff, pageshift=12
61017 VM pages: 31 active, 0 inactive, 0 wired, 58603 free (6676 zero)
min 10% (25) anon, 10% (25) vnode, 5% (12) vtext
pages 0 anon, 0 vnode, 0 vtext
freemin=2033, free-target=2710, inactive-target=0, wired-max=20339
faults=149112, traps=166948, intrs=16552, ctxswitch=48127 fpuswitch=29
softint=24716, syscalls=356100, kmapent=16
fault counts:
noram=0, noanon=0, noamap=0, pgwait=0, pgrele=0
ok relocks(total)=6547(6547), anget(retries)=46892(0), amapcopy=54893
neighbor anon/obj pg=2236/43905, gets(lock/unlock)=21193/6547
cases: anon=36583, anoncow=10309, obj=19426, prcopy=1767, przero=81027
daemon and swap counts:
woke=0, revs=0, scans=0, obscans=0, anscans=0
busy=0, freed=0, reactivate=0, deactivate=0
pageouts=0, pending=0, nswget=0
nswapdev=0, nanon=0, nanonneeded=0 nfreeanon=0
swpages=0, swpginuse=0, swpgonly=0 paging=0
kernel pointers:
objs(kern)=0xd0c30c84
ddb> show panic
unmount: dangling vnode `
`
ddb> boot reboot
rebooting...
PC Engines ALIX.2 v0.99m
640 KB Base Memory
261120 KB Extended Memory
01F0 Master 848A SanDisk SDCFHSNJC-004G
Phys C/H/S 7751/16/63 Log C/H/S 968/128/63
BIOS setup:
(9) 9600 baud (2) 19200 baud *3* 38400 baud (5) 57600 baud (1) 115200 baud
(C) CHS mode *L* LBA mode (W) HDD wait (V) HDD slave *U* UDMA enable
(E) PXE boot enable
*M* Memory test
(P) late PCI init
*R* Serial console enable
(X) Xmodem upload
(Q) Quit
`https://gitlab.com/bconway/resflash/-/issues/8More documentation howto use the pkg_add in the build process2018-04-19T20:21:25ZKarsten HorsmannMore documentation howto use the pkg_add in the build processHello, i like the idea with resflash and it was a littlebit tricky to get pkg_add working with resflash build process.
Would be nice if you provide two examples.
1.) example usage for --pkg_path path1:path2 --pkg_list pkg1,pkg2
2.) for...Hello, i like the idea with resflash and it was a littlebit tricky to get pkg_add working with resflash build process.
Would be nice if you provide two examples.
1.) example usage for --pkg_path path1:path2 --pkg_list pkg1,pkg2
2.) for -p pkg_dir usage. (use pkg_add -nv <name> to fetch you paket to PKG_CACHE folder)
I personal found any information in the ML archive. But it would be handy to find it in the readme.
Thanks