This page is archived.
Current active BBS is FuguIta/BBS.



6.9

m3th? (2021-05-16 (Sun) 00:09:53)

>Notice: To avoid posts by spam, a message body without the word '#FuguIta' is rejected.
It is very difficult to post message here.

#FuguIta

I would like to ask a noasks file on website.
My noasks file always ignore me. could you tell me your article as example on website?

# FuguIta system device
noask_rdev='sd0a'

# storage device
noask_confdev='sd0d'
noask_confdev='sd1d'

Which should I use as noask_confdev value?

While

Copying files from flash to ram ...

appears, I sometimes get

softraid0: sd3: i/o error5 @crypt block

error message.
Could you have any idea to solve this problem?

  • As for the difficulty in posting, it is probably due to the limitations of the function of the article plugin of the PukiWiki. Sorry for inconvenience.
    I think it is somewhat easier to post articles if you copy and paste the pre-edited articles in a text editor.

    Now, about the noasks file, first, please check the following matters and let me know the result.

    1) Do you have only one #FuguIta device attached to your PC? Or is there more than one?

    2) Is the data storage area an encrypted partition?

    Please let me know the above. -- kaw? 2021-05-16 (Sun) 01:36:05
  • >Do you have only one #FuguIta device attached to your PC?
    Yes,I do. The data storage area an encrypted partition. #FuguIta -- 2021-05-16 (Sun) 05:59:11
  • OK, so you have only one #FuguIta device with an encrypted partition attached to your PC.
    I think the reason your noasks file is ignored is because it is in an encrypted partition. FuguIta will not be able to see the noasks file until you enter your passphrase.
    So you need to keep the noasks file in an unencrypted partition.
    For example, after editing the noasks file, to put it on sd0a, you can do the following.
    # mount -uw /sysmedia    # make sd0a writable (assume /sysmedia mounted mounted on sd0a)
    # cp noasks /sysmedia    # put noasks file on it
    # mount -ur /sysmedia    # make sd0a read only again
    # reboot                 # reboot to test
    The contents of the noasks file will look like this
    # FuguIta system device
    noask_rdev=sd0a
    #
    # tmpfs size in MB
    noask_umem=0
    #
    # boot mode
    noask_setup_rw_mode=3
    #
    # storage device
    noask_confdev=sd0d    # put your encrypted partition
    #
    # data set name in USB flash drive
    noask_confdir=YOUR-CONFIG-NAME
    When this noasks file is read, FuguIta will stop with the input of the passphrase.
    Enter that passphrase, then specify mode 3 again, and manually enter the new decryption device that appears. This is exactly how I use my MacBook Pro right now.

    Next, the error message that appears while loading the file, I searched for "softraid0" "i/o error 5" and got many hits. It seems to be a problem with the OpenBSD device driver.

    -- kaw? 2021-05-16 (Sun) 06:35:46

  • Thank you for reply. My noasks file works. May I delete old noask_confdirs anytime to use rm command? I have three. #FuguIta -- m3th? 2021-05-16 (Sun) 13:10:04
  • Of course.
    If you do not plan to use them at all in the future, you can delete them with rm -rf.
    You can mount them with the async and noatime options for faster deletion.
    # mount -o async,noatime /dev/sdXd /mnt
    # cd /mnt/livecd-config/VER/ARCH
    # rm -rf YOUR-OLD-CONFDIRS
    # cd
    # umount /mnt

    #FuguIta -- kaw? 2021-05-16 (Sun) 14:05:40

Another new tool on 6.9

kaw? (2021-05-14 (Fri) 12:20:44)

Another new tool, remaster_dvd.sh, was introduced in FuguIta 6.9.
As the name suggests, it remasters FuguIta LiveDVD ISO images.
This tool can be used with either a running FuguIta LiveDVD or FuguIta LiveUSB.
The following is an example of remaster_dvd.sh usage.

First, create a working directory and copy the contents of LiveDVD under sysmedia.

fuguita69# mkdir work
fuguita69# cd work
fuguita69# cp -av /sysmedia .
/sysmedia -> ./sysmedia
/sysmedia/boot -> ./sysmedia/boot
/sysmedia/bsd-fi -> ./sysmedia/bsd-fi
/sysmedia/bsd-fi.mp -> ./sysmedia/bsd-fi.mp
/sysmedia/boot.catalog -> ./sysmedia/boot.catalog
/sysmedia/cdboot -> ./sysmedia/cdboot
/sysmedia/cdbr -> ./sysmedia/cdbr
/sysmedia/etc -> ./sysmedia/etc
/sysmedia/etc/boot.conf -> ./sysmedia/etc/boot.conf
/sysmedia/etc/random.seed -> ./sysmedia/etc/random.seed
/sysmedia/fuguita-6.9-amd64.ffsimg -> ./sysmedia/fuguita-6.9-amd64.ffsimg
fuguita69# ls -l
total 8
drwxr-xr-x  3 root  wheel  432 May 11 09:21 sysmedia

In the copied sysmedia directory, run remaster_dvd.sh. This is basically all there is to it.

fuguita69# cd sysmedia
fuguita69# ls -l
total 2008728
-rw-r--r--  1 root  wheel	90496 May 10 20:57 boot
-rwxr--r--  1 root  wheel	 2048 May  9 12:31 boot.catalog
-rw-r--r--  1 root  wheel    10273019 May 10 21:04 bsd-fi
-rw-r--r--  1 root  wheel    10302063 May 10 21:04 bsd-fi.mp
-rw-r--r--  1 root  bin		91668 May 10 01:31 cdboot
-rw-r--r--  1 root  bin		 2048 May 10 01:31 cdbr
drwxr-xr-x  2 root  wheel	   96 Apr 17  2014 etc
-rw-r--r--  1 root  wheel  1007681536 May 10 21:08 fuguita-6.9-amd64.ffsimg
fuguita69# remaster_dvd.sh
mkhybrid 1.12b5.1
Scanning .
Scanning ./etc

Size of boot image is 4 sectors -> No-emulation CD boot sector
Total translation table size: 0
Total rockridge attributes bytes: 1111
Total directory bytes: 2048
Path table size(bytes): 22
502200 extents written (980 Mb)

When the execution of remaster_dvd.sh is completed, an ISO image file will have been created in the working directory.

fuguita69# ls -l ..
total 2008808
-rw-r--r--  1 root  wheel  1028505600 May 14 02:34 FuguIta-6.9-amd64-202105141.iso
drwxr-xr-x  3 root  wheel	  384 May 14 02:34 sysmedia
fuguita69# ls -l
total 2008720
-rw-r--r--  1 root  wheel	90496 May 10 20:57 boot
-rwxr--r--  1 root  wheel	 2048 May 14 02:34 boot.catalog
-rw-r--r--  1 root  wheel    10273019 May 10 21:04 bsd-fi
-rw-r--r--  1 root  wheel    10302063 May 10 21:04 bsd-fi.mp
-rw-r--r--  1 root  bin		91668 May 10 01:31 cdboot
-rw-r--r--  1 root  bin		 2048 May 10 01:31 cdbr
drwxr-xr-x  2 root  wheel	   96 Apr 17  2014 etc
-rw-r--r--  1 root  wheel  1007681536 May 10 21:08 fuguita-6.9-amd64.ffsimg

In sysmedia, you will find a file called like fuguita-6.9-amd64.ffsimg, which contains the FuguIta file tree. By modifying the files in this file tree, you can customize LiveDVD.

fuguita69# vnconfig vnd0 fuguita-6.9-amd64.ffsimg
fuguita69# mount /dev/vnd0a /mnt
fuguita69# ls -l /mnt
total 52
-rw-r--r--   1 root  wheel   578 May  7 17:43 .cshrc
-rw-r--r--   1 root  wheel   468 May  7 17:43 .profile
drwxr-xr-x   2 root  wheel   512 May  7 17:43 altroot
drwxr-xr-x   2 root  wheel  1024 May  7 17:46 bin
drwxr-xr-x   2 root  wheel   512 May  8 04:16 dev
drwxr-xr-x  23 root  wheel  1536 May  8 04:35 etc
drwxr-xr-x   2 root  wheel   512 May  7 17:43 home
drwxr-xr-x   2 root  wheel   512 May  7 17:43 mnt
drwx------   3 root  wheel   512 May  8 04:35 root
drwxr-xr-x   2 root  wheel  1536 May  7 17:46 sbin
lrwxrwx---   1 root  wheel    11 May  7 17:43 sys -> usr/src/sys
drwxrwxrwt   2 root  wheel   512 May  8 04:19 tmp
drwxr-xr-x  14 root  wheel   512 May  8 04:09 usr
drwxr-xr-x  23 root  wheel   512 May  7 17:43 var
.... modify files as you like ...

Once the customization is complete, close the file system image and remaster it.

fuguita69# umount /mnt
fuguita69# vnconfig -u vnd0
fuguita69# remaster_dvd.sh
mkhybrid 1.12b5.1
Scanning .
Scanning ./etc
  :
  :

New tool on FuguIta 6.9

kaw? (2021-05-12 (Wed) 11:05:49)

FuguIta 6.9 provides a new tool to change network settings. The following is an example of its use.
In the new 6.9 release, network-related configuration files are stored in a subdirectory under /etc/netconfs, and symbolic links are provided from /etc to these files.
The settings you made during the initial boot are located in /etc/netconfs/default.

fuguita69# cd /etc
fuguita69# ls -l | grep netconfs
lrwxr-xr-x  1 root  wheel        27 May 12 00:49 hosts -> /etc/netconfs/default/hosts
lrwxr-xr-x  1 root  wheel        28 May 12 00:49 myname -> /etc/netconfs/default/myname
drwxr-xr-x  3 root  wheel        48 May 12 00:49 netconfs
lrwxr-xr-x  1 root  wheel        33 May 12 00:49 resolv.conf -> /etc/netconfs/default/resolv.conf
lrwxr-xr-x  1 root  wheel        33 May 12 00:49 sysctl.conf -> /etc/netconfs/default/sysctl.conf
fuguita69# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 32768
       index 3 priority 0 llprio 3
       groups: lo
       inet6 ::1 prefixlen 128
       inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
       inet 127.0.0.1 netmask 0xff000000
msk0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
       lladdr 00:17:42:6b:8a:92
       index 1 priority 0 llprio 3
       groups: egress
       media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause)
       status: active
enc0: flags=0<>
       index 2 priority 0 llprio 3
       groups: enc
       status: active
run0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
       lladdr cc:e1:d5:15:0e:cb
       index 4 priority 4 llprio 3
       groups: wlan
       media: IEEE802.11 autoselect (DS1 mode 11g)
       status: no network
       ieee80211: nwid ""
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33136
       index 5 priority 0 llprio 3
       groups: pflog

As an example, let's add two settings, home and office.
First, let's start with office. This assumes an Ethernet connection and a fixed address configuration.
To add a new configuration, create a directory under /etc/netconfs.

fuguita69# cd /etc/netconfs
fuguita69# ls -l
total 8
drwxr-xr-x  2 root  wheel  192 May 12 00:41 default
fuguita69# mkdir office

To create the configuration file, use the gennetconfs utility that is traditionally provided.
Its usage is the same as the configuration done in the initial boot.

fuguita69# cd office
fuguita69# gennetconfs
host name (without domain) -> fuguita
IP version(s) to use: 4, 6, 46, 64 or n
  46: IPv4 preferred over IPv6 in address resolution
  64: reversed to 46
   n: stand alone operation
[46]-> 4
==[ifconfig -a]=========================
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 32768
       index 3 priority 0 llprio 3
       groups: lo
       inet6 ::1 prefixlen 128
       inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
       inet 127.0.0.1 netmask 0xff000000
msk0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
       lladdr 00:17:42:6b:8a:92
       index 1 priority 0 llprio 3
       groups: egress
       media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause)
       status: active
enc0: flags=0<>
       index 2 priority 0 llprio 3
       groups: enc
       status: active
run0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
       lladdr cc:e1:d5:15:0e:cb
       index 4 priority 4 llprio 3
       groups: wlan
       media: IEEE802.11 autoselect (DS1 mode 11g)
       status: no network
       ieee80211: nwid ""
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33136
       index 5 priority 0 llprio 3
       groups: pflog
========================================
Available network interface(s): msk0 run0
network interface to setup [msk0] -> msk0
FQDN of this host -> fuguita.office.local
DNS setup;
  Manual : Enter up to three IPv4/IPv6 addresses, separated by spaces
  DHCP  : Just press ENTER .
  no DNS : Enter "none".
-> 192.168.20.254
IPv4 addr of this host -> 192.168.20.115
netmask                -> 255.255.255.0
default route          -> 192.168.20.254

When the configuration using gennetconfs is completed, the configuration file will be created in the subdirectory you just created.

fuguita69# ls -l
total 48
-rw-r-----  1 root  wheel   37 May 12 01:14 hostname.msk0
-rw-r--r--  1 root  wheel   82 May 12 01:14 hosts
-rw-r--r--  1 root  wheel   12 May 12 01:14 mygate
-rw-r--r--  1 root  wheel   21 May 12 01:14 myname
-rw-r--r--  1 root  wheel   73 May 12 01:14 resolv.conf
-rw-r--r--  1 root  wheel  106 May 12 01:14 sysctl.conf
fuguita69# ls -l /etc/ | grep netconfs
lrwxr-xr-x  1 root  wheel        27 May 12 00:49 hosts -> /etc/netconfs/default/hosts
lrwxr-xr-x  1 root  wheel        28 May 12 00:49 myname -> /etc/netconfs/default/myname
drwxr-xr-x  4 root  wheel        96 May 12 01:13 netconfs
lrwxr-xr-x  1 root  wheel        33 May 12 00:49 resolv.conf -> /etc/netconfs/default/resolv.conf
lrwxr-xr-x  1 root  wheel        33 May 12 00:49 sysctl.conf -> /etc/netconfs/default/sysctl.conf

To make these settings actually take effect, use the chnetconf utility.
When you run chnetconf, it will create symbolic links from /etc to these files, and then run /etc/netstart internally to modify the configuration.

fuguita69# chnetconf
16.0K  default
28.0K  office
fuguita69# chnetconf office
fuguita69# ls -l /etc/ | grep netconfs
lrwxr-xr-x  1 root  wheel        34 May 12 01:15 hostname.msk0 -> /etc/netconfs/office/hostname.msk0
lrwxr-xr-x  1 root  wheel        26 May 12 01:15 hosts -> /etc/netconfs/office/hosts
lrwxr-xr-x  1 root  wheel        27 May 12 01:15 mygate -> /etc/netconfs/office/mygate
lrwxr-xr-x  1 root  wheel        27 May 12 01:15 myname -> /etc/netconfs/office/myname
drwxr-xr-x  4 root  wheel        96 May 12 01:13 netconfs
lrwxr-xr-x  1 root  wheel        32 May 12 01:15 resolv.conf -> /etc/netconfs/office/resolv.conf
lrwxr-xr-x  1 root  wheel        32 May 12 01:15 sysctl.conf -> /etc/netconfs/office/sysctl.conf
fuguita69# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 32768
       index 3 priority 0 llprio 3
       groups: lo
       inet6 ::1 prefixlen 128
       inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
       inet 127.0.0.1 netmask 0xff000000
msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
       lladdr 00:17:42:6b:8a:92
       index 1 priority 0 llprio 3
       groups: egress
       media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause)
       status: active
       inet 192.168.20.115 netmask 0xffffff00 broadcast 192.168.1.255
enc0: flags=0<>
       index 2 priority 0 llprio 3
       groups: enc
       status: active
run0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
       lladdr cc:e1:d5:15:0e:cb
       index 4 priority 4 llprio 3
       groups: wlan
       media: IEEE802.11 autoselect (DS1 mode 11g)
       status: no network
       ieee80211: nwid ""
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33136
       index 5 priority 0 llprio 3
       groups: pflog
fuguita69# ping www.google.com
PING www.google.com (172.217.175.68): 56 data bytes
64 bytes from 172.217.175.68: icmp_seq=0 ttl=115 time=28.318 ms
64 bytes from 172.217.175.68: icmp_seq=1 ttl=115 time=25.842 ms
64 bytes from 172.217.175.68: icmp_seq=2 ttl=115 time=26.137 ms
^C
--- www.google.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 25.842/26.765/28.318/1.104 ms

Continuing on, let's create a home configuration as well. This one assumes a WiFi connection and DHCP is used.

fuguita69# pwd
/etc/netconfs/office
fuguita69# mkdir /etc/netconfs/home
fuguita69# cd /etc/netconfs/home
fuguita69# gennetconfs
host name (without domain) -> fuguita
IP version(s) to use: 4, 6, 46, 64 or n
  46: IPv4 preferred over IPv6 in address resolution
  64: reversed to 46
   n: stand alone operation
[46]-> 46
==[ifconfig -a]=========================
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 32768
       index 3 priority 0 llprio 3
       groups: lo
       inet6 ::1 prefixlen 128
       inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
       inet 127.0.0.1 netmask 0xff000000
msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
       lladdr 00:17:42:6b:8a:92
       index 1 priority 0 llprio 3
       groups: egress
       media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause)
       status: active
       inet 192.168.20.115 netmask 0xffffff00 broadcast 192.168.1.255
enc0: flags=0<>
       index 2 priority 0 llprio 3
       groups: enc
       status: active
run0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
       lladdr cc:e1:d5:15:0e:cb
       index 4 priority 4 llprio 3
       groups: wlan
       media: IEEE802.11 autoselect (DS1 mode 11g)
       status: no network
       ieee80211: nwid ""
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33136
       index 5 priority 0 llprio 3
       groups: pflog
========================================
Available network interface(s): msk0 run0
network interface to setup [msk0] -> run0
FQDN of this host -> fuguita.home.local
Wi-Fi SSID -> WIFI-SSID
   WPA Key -> WPA-PASSWD
DNS setup;
  Manual : Enter up to three IPv4/IPv6 addresses, separated by spaces
  DHCP  : Just press ENTER .
  no DNS : Enter "none".
->
fuguita69# ls -l
total 40
-rw-r-----  1 root  wheel   59 May 12 01:29 hostname.run0
-rw-r--r--  1 root  wheel   76 May 12 01:29 hosts
-rw-r--r--  1 root  wheel   19 May 12 01:29 myname
-rw-r--r--  1 root  wheel    0 May 12 01:29 resolv.conf
-rw-r--r--  1 root  wheel   54 May 12 01:29 resolv.conf.tail
-rw-r--r--  1 root  wheel  106 May 12 01:29 sysctl.conf
fuguita69# chnetconf
16.0K  default
24.0K  home
28.0K  office
fuguita69# chnetconf home
run0: no link....got link
run0: 192.168.10.61 lease accepted from 192.168.10.231 (f8:b7:97:2d:89:66)
fuguita69# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 32768
       index 3 priority 0 llprio 3
       groups: lo
       inet6 ::1 prefixlen 128
       inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
       inet 127.0.0.1 netmask 0xff000000
msk0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
       lladdr 00:17:42:6b:8a:92
       index 1 priority 0 llprio 3
       media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause)
       status: active
enc0: flags=0<>
       index 2 priority 0 llprio 3
       groups: enc
       status: active
run0: flags=248843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF6TEMP,AUTOCONF6> mtu 1500
       lladdr cc:e1:d5:15:0e:cb
       index 4 priority 4 llprio 3
       groups: wlan egress
       media: IEEE802.11 autoselect (DS1 mode 11g)
       status: active
       ieee80211: nwid WIFI-SSID chan 11 bssid 1c:b1:7f:27:5c:de -61dBm wpakey wpaprotos wpa2 wpaakms psk
       wpaciphers ccmp wpagroupcipher ccmp
       inet 192.168.10.61 netmask 0xffffff00 broadcast 192.168.10.255
       inet6 fe80::cee1:d5ff:fe15:ecb%run0 prefixlen 64 scopeid 0x4
       inet6 2409:xx:xxxx:xxxx:669c:3666:1e5d:1e95 prefixlen 64 autoconf pltime 604797 vltime 2591997
       inet6 2409:xx:xxxx:xxxx:ded5:bc35:e07a:fa89 prefixlen 64 autoconf temporary pltime 84961 vltime 172794
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33136
       index 5 priority 0 llprio 3
       groups: pflog

We have now created three network configurations, including the default.
You can switch between these settings at any time using the chnetconf utility.

incorrect link for OpenBSD 6.9 patches

Mel? (2021-05-11 (Tue) 14:26:19)

in front page of #FuguIta there is "Patch 001 of OpenBSD 6.9 has been applied."

when you click on the link, it goes to OpenBSD 6.8 list of patches.

  • Fixed it. Thank you! #FuguIta -- kaw? 2021-05-11 (Tue) 14:30:43

Video Streaming by FuguIta

kaw? (2021-05-01 (Sat) 08:06:34)

In Niigata Prefecture, where I live, there is a traditional event called "Ushi no Tsuno Tsuki" ("Poke of bull horns" - bullfighting).

The first event of the year was held on April 29th, and I participated as a member of the team that delivered the video.

I was in charge of delivering the video directly to the smartphones and tablets of the audience at the event.

In this event, the MC and the remote guest interact via ZOOM, and the purpose of my job was to show the audience what was going on.

This was my first attempt at this, and the followings are required.

  • low latency
  • video only, no audio (to be heard over the PA)
  • no need to install any application, just a browser.

To achieve this, I made the following choices

  • Free WiFi turned out to be difficult to use for this purpose.
    • Establish a local network and operate inside it.
    • Install a WiFi access point.
  • Adopt WebRTC technology.
    • TLS is required for WebRTC

Based on the above conditions, you will need the following

  • dhcpd
  • TLS httpd with certified domain
  • local DNS

All of the above features are available in OpenBSD from the start, except for the web browser and WebRTC. So I decided to use #FuguIta as a base for implementing these.

For the video distribution software, We used Screego. Conveniently, Screego is supplied as an executable binary for OpenBSD.

Furthermore, this network is not completely independent and needs to remain in communication with the Internet. This is because smartphones communicate with sites on the Internet to determine the status of the network. If there is no communication with the Internet, the smartphone will complain. In addition, time synchronization is required for TLS communication, and therefore, NTP must be available. For these purposes, I decided to create a NAT in PF. I decided to limit the bandwidth of the communication through the NAT, because the main purpose of this Internet access line is to upload the video of the event to YouTube, and to communicate with the remote performers via ZOOM.

Based on the above, I decided to configure and operate the network as follows.

screego-e.png
Network of this event (click to enlarge)

As for the web browser for the video distribution, We had originally planned to use Windows, but since the title bar of the window was displayed on the video to be distributed, and the video input with an aspect ratio of 16:9 was somehow changed to 4:3, I decided to use FuguIta for this purpose as well, and use MPlayer to convert the aspect ratio of the video to 16:9 and send it by Chromium.

The operation of the day is as follows.

pix1.jpgpix2.jpg
Operation BoothScreego Server
pix4.jpgpix3.jpg
WiFi Access PointVideo Sender

As a result, it worked as planned, but there were a few problems.

  • Screego terminated abnormally once and delivery was temporarily interrupted.
  • WiFi access point saturation
  • Traffic exceeding the set bandwidth of the Internet uplink (misconfiguration of pf.conf?)

We will need to improve on these issues in the future.

This time, I planted a monitor script modified from SAG in both the Screego server and the browser for sending images, so We will analyze the logs and plan countermeasures.

  • Thanks for sharing a use case for #FuguIta. I use #FuguIta now as security system. I use motion(1) from ports, and capture RTSP data from 2 cheap IP camera. motion(1) detect motion and starts recording. Now it is very simple, it does not send any email notification to me. -- Mel? 2021-05-02 (Sun) 07:41:15
  • This is the first time I have heard about motion(1). Thank you for telling me about it.
    #FuguIta -- kaw? 2021-05-02 (Sun) 10:47:08

FuguIta development

Mel? (2021-04-27 (Tue) 15:35:18)

i try to follow how to setup development for #FuguIta from this JPN page "河豚板の開発ツールを使う - LiveDVDのカスタマイズと作成".

i download the construction tool tools-6.8-amd64.tar.gz. there is .ffsimg file (media/fuguita-6.8-amd64.ffsimg).

i understand this is for OpenBSD 6.8, if i want 6.9 this ffsimg should be updated. but, my question is, how do you create this .ffsimg file for each new release of OpenBSD?

  • When 6.9 will be released, I'll download *69.tgz files and then extract all of them.
    Next, I'll some modifications to adapt this to FuguIta. They are:
    • extract /var/sysmerge/*etc.tgz
    • fix dangling symlinks in /usr/{bin,sbin}
    • remove /usr/share/relink/kernel.tgz (KARL makes no sense for Live System)
    • prepare files under /usr/fuguita
    • add /usr/fuguita/{bin,sbin} to $PATH
    • sh ./MAKEDEV std (in a chrooted environment)
    • pkg_add rsync, rlwrapper and pv, then ldconfig (in a chrooted environment)
    • modify /etc/hosts, /etc/mtree/special and /etc/sysctl.conf
    • add /etc/localtime, /etc/firsttime, /etc/installurl, /etc/man.conf, /var/db/host.random, /root/.Xauthority and /etc/skel/.Xauthority
    • prepare /etc/rc.diff which will be applied at boot time
    • prepare /usr/fuguita/etc/mode0symlinks.cpio.gz with /usr/fuguita/sbin/gen_mode0sldir utility (This is for fast boot. FuguIta works without this file)

Above is the standard procedure to setup the content of *.ffsimg, and may have any variations by every OpenBSD release.
And also, it may possibly vary anymore at your case.

-- kaw? 2021-04-28 (Wed) 05:40:16

  • kaw-sama thanks for sharing how to create the .ffsimg. lot of work. thanks for all your work with #FuguIta. -- Mel? 2021-04-28 (Wed) 07:42:24

syspatch

m3th? (2021-04-24 (Sat) 18:32:09)

Can I syspatch to #FuguIta?

  • Because FuguIta is different from regular OpenBSD in many ways, syspatch cannot be used with FuguIta.

    For example, the FuguIta kernel was built to run the Live System, so it is not possible to use syspatches that are intended for use with the GENERIC kernel.

    Another reason why syspatch cannot be used is that the filesystem configuration is also very different from that of regular OpenBSD.

    FuguIta provides the fiupdate utility to update the system, so please use it if you are using LiveUSB.

    For more information on updating FuguIta, please refer to the following article.

  • I have used fiupdate. Now, #FuguIta is 6.8-amd64-202104141 -- m3th? 2021-04-25 (Sun) 15:02:05

Prototype from snapshot

kaw? (2021-03-23 (Tue) 18:01:06)

Prototyped a trial version of #FuguIta based on OpenBSD-current (6.9-beta).
It is only available for the amd64 architecture.
Get it from "test" directory on download mirrors.
Your trial reports are welcome.

  • i tried it in vmd, it works. i have Panasonic CF-J10 running 6.8 #FuguIta but i probably will not test it on that machine. the problem is since 6.9-beta is a -current i can't install packages. i try to install "motion" and some dependency is not correct. -- Mel? 2021-04-27 (Tue) 15:25:04

Change of mirror servers

kaw? (2021-02-16 (Tue) 19:00:58)

Two new mirror servers in Europe are now in operation.

They are de.dl.fuguita.org and fr.dl.fuguita.org, the successors to eu.dl.fuguita.org.

eu.dl.fuguita.org will be out of service in a few weeks.

I would like to express our sincere gratitude to the administrators of eu.dl.fuguita.org and everyone who are providing the mirror servers.

Laptop Connected to Monitor

(2021-01-30 (Sat) 07:41:07)

I can use a second monitor with OpenBSD. I cannot use a second monitor with #FuguIta.

r600_cp: Failed to load firmware "radeon/SUMO2_pfp.bin"
[drm] *ERROR* Failed to load firmware!
drm:pid0:radeondrm_attachhook *ERROR* Fatal error during GPU init
drm0 detached
radeondrm0 detached


I saved settings after downloading the firmware, rebooted, and do have "/radeon/SUMO2_pfp.bin". I assume this error happens because the boot process executes the GPU init before I can choose boot mode 3. Is there an easy way to fix this error, myself?

Sorry. I am inexperienced with BSD (and computers).

  • As you would expect, this is because #FuguIta's kernel tries to load the firmware before mounting filesystem which holds file of the firmware.
    To solve this problem, FuguIta's kernel must have the firmware in the root filesystem which is built in the kernel.

    In case of LiveDVD, you must rebuild ISO image to have the firmware built-in.
    This is quite complexed process, so you may select to use FuguIta LiveUSB or vanilla OpenBSD.

    If you use LiveUSB, you can write the firmware to built-in root filesystem with following process:
    # gzip -dc /sysmedia/bsd-fi.mp > bsd-fi.mp
    # vnconfig vnd0 bsd-fi.mp
    # mount /dev/vnd0a /mnt
    # mkdir -p /mnt/etc/firmware
    # (copy radeon's firmwares under /mnt/etc/firmware)
    # umount /mnt
    # vnconfig -u vnd0
    # mount -uw /sysmedia
    # gzip -c9 bsd-fi.mp > /sysmedia/bsd-fi.mp
    # mount -ur /sysmedia

    -- kaw? 2021-02-01 (Mon) 09:21:51

Recent articles on FuguIta

kaw? (2021-01-09 (Sat) 23:04:26)

Recently, I found reviews and tutorial videos about #FuguIta on the net, so I will introduce them.

I am deeply grateful to the authors of these articles.

FuguIta 6.8 tools

kaw? (2020-11-03 (Tue) 23:37:38)

Tools to create a live system based on OpenBSD 6.8 were uploaded at tools directory.
To use this tool, refer the article 河豚板の開発ツールを使う - LiveDVDのカスタマイズと作成 (LiveDVD - Using FuguIta development tools) in the page 河豚板ガイド (FuguIta Guide).

Ventoy Compatibility?

Fugu? (2020-10-24 (Sat) 22:05:09)

Hello kaw:

Any chance of getting #FuguIta working with ventoy at www.ventoy.net/en/index.html.

No pressure - just asking since Fugu's broader goals align with such a tool.

Thank you.

  • I've never heard of Ventoy. This seems a quite interesting tool.
    Looking at Ventoy's support list, it seems that the operation of #FuguIta has failed.
    In the first place, it seems that BSD-based OS such as OpenBSD itself is not supported very well.
    -- kaw? 2020-10-25 (Sun) 13:09:07
  • Hello Kaw: \n I just tried the cd and miniroot iso and img files of OpenBSD and could get to boot screens without issue. #FuguIta profile load looks for a hard drive and cannot proceed further. Is moving that part to ramdisk possible? I was thinking of antiX user settings load to RAM setup. -- Fugu? 2020-10-25 (Sun) 15:49:03
  • FuguIta tries to mount all partitions of all disk devices in order at boot time.
    This is to find the partition where the FuguIta system is stored and the partition for data storage.
    FuguIta booted from Ventoy is booted from a virtual disk, so it is unlikely that you will be able to find the device that contains the FuguIta system.
    You may be able to boot in fresh boot mode (modes 0, 1 or 2) by placing the ISO image on physical FAT / NTFS or ExtFS, as described in the chapter Coexisting FuguIta with Windows or Linux of the FuguIta Guide. -- kaw? 2020-10-26 (Mon) 10:49:35
  • Chainloaded from Grub using set root=(hdX,msdosX) and kopenbsd /bsd-fi.mp. #FuguIta dd'ed and newdrive via usbfadm onto flash drive failed to boot on this Dell system but worked on a Thinkpad. Thank you. -- Fugu? 2020-10-26 (Mon) 19:31:47

FuguIta-6.8 status

kaw? (2020-10-24 (Sat) 00:30:25)

#FuguIta-6.8-i386 and FuguIta-6.8-amd64 are now under test.
These are at test directory at download mirrors.

Your trial report is greatly appreciated.

  • #FuguIta-6.8-{i386,amd64}-202010251 on the mirrors. This is a release candidate. -- kaw? 2020-10-25 (Sun) 13:14:59

Live Update for FuguIta LiveUSB

kaw? (2020-09-24 (Thu) 22:13:14)

I'm currently working on a Live Update for #FuguIta LiveUSB.
This is in beta testing.

To update with this utility, place the gzipped ISO image (not the *.img.gz file!) and the MD5 checksum file in the current directory.
Then run the fiupdate command.

# cat /usr/fuguita/version
6.7-amd64-202008261
# ls -l
total 606528
-rw-r--r--  1 root  wheel  310528773 Sep 24 18:47 FuguIta-6.7-amd64-202009041.iso.gz
-rw-r--r--  1 root  wheel      11660 Sep 24 18:47 MD5
# fiupdate 202009041

fiupdate - Live Updater for FuguIta LiveUSB
  Version/Arch: 6.7/amd64  (FuguIta-6.7-amd64-202008261)

Note:
This sorftware is now under beta test.
Please use this at YOUR OWN RISK.

We recommend that you execute this command with fresh boot (boot mode 0 or 1).

Or you should quit all application softwares and save all your data
before you update this FuguIta device.

Are you sure? [y/N] -> y

Checking:
     environment: ok
	  mounts: ok
  existing files: ok
	checksum: (MD5) FuguIta-6.7-amd64-202009041.iso.gz: OK
all done, OK.

extracting FuguIta-6.7-amd64-202009041.iso.gz...
 296MiB 0:00:48 [6.12MiB/s] [================================>] 100% ETA 0:00:00

Now ready to update FuguIta-6.7-amd64-202008261 to FuguIta-6.7-amd64-202009041.

This machine will reboot immediately after update completed.

Do you proceed? [y/N] -> y
stopping all daemons...
cron(ok)
ntpd(ok)
pflogd(ok)
slaacd(ok)
smtpd(ok)
sndiod(ok)
sshd(ok)
syslogd(ok)
overwriting uniprocessor kernel...
8.68MiB 0:00:03 [2.31MiB/s] [================================>] 100% ETA 0:00:00
overwriting multiprocessor kernel...
8.71MiB 0:00:03 [2.23MiB/s] [================================>] 100% ETA 0:00:00
overwriting filesystem image...
 894MiB 0:04:25 [3.36MiB/s] [================================>] 100% ETA 0:00:00

update completed. now rebooting...
syncing disks... done
rebooting...

We welcome your trial report.

  • revised this script, See https://jp1.dl.fuguita.org/test/ . -- kaw? 2020-10-05 (Mon) 10:58:51
  • #FuguIta-6.7-*-202010071 has this. (Still can't handle tarball, sorry arm64 user) -- kaw? 2020-10-16 (Fri) 00:40:20

isotop on FuguIta

kaw? (2020-09-08 (Tue) 14:07:35)

isotop is a script to configure and customize vanilla OpenBSD into ready-to-use desktop environment.

I have modified isotop to be able to run on #FuguIta.

To run isotop.sh on FuguIta after download it, apply this patch fileisotop-665-fi.sh.diff .
Then run install script as a root.

$ ftp https://framagit.org/3hg/isotop/raw/master/src/isotop.sh
$ patch < isotop-665-fi.sh.diff
# sh isotop.sh

Here's a screenshot of FuguIta configured by isotop.

isotop_desktop1.png

Archive video of FuguIta Talk on OSC2020 Niigata

kaw? (2020-08-01 (Sat) 03:37:52)

Video of Talk about #FuguIta at OSC2020 Niigata has been published:
https://www.youtube.com/watch?v=4wPSr1WPH3U

And the document is at 河豚板#OSC2020

OSC2020新潟オンラインで河豚板の発表を行います。
Talk about FuguIta at OSC2020 Niigata

kaw? (2020-07-22 (Wed) 15:27:51)

Open Source Conference 2020 Online/Niigataが7月25日(土)に開催されます。
今回はオンラインでの開催になります。https://ospn.connpass.com/event/181888/ の開催概要ページよりZoom参加に登録頂くか、YouTube Liveにてご視聴下さい。

Open Source Conference 2020 Online/Niigata will be held on Saturday, July 25th.
This event will be held online and I will have a 15 minute talk about #FuguIta in the name of EBUG (Echigo BSD Users Group).
Please register for Zoom participation from the overview page of https://ospn.connpass.com/event/181888/ , or watch it on YouTube Live.

  • YouTube Live Stream will be broadcast at https://www.youtube.com/watch?v=XSKG1rK3nKQ .
    The live stream will begin at 12:30JST (03:30UTC) on 25 Sat, July 2020.
    There will be three BSD-related talks:
    Time (UTC)TitleAffiliationSpeaker
    06:00-06:15Introduction of NetBSDJapan NetBSD Users Group (JNUG)Jun Ebihara
    06:15-06:30Introduction of FuguItaEchigo BSD Users Group (EBUG)Yoshihiro Kawamata
    06:30-06:45Introduction of
    vyos-cli: VyOS CLIs for Ubuntu
    Echigo Network Operators Group (ENOG)Masakazu Asama
    (also member of EBUG)
    These talks will be available as archives at a later date.

    -- kaw? 2020-07-22 (Wed) 23:46:40

Boot mode difference

Fugu? (2020-07-19 (Sun) 15:51:32)

Hello Kaw:

Is there a difference in boot mode of OpenBSD and #FuguIta? I have a Dell PC where OpenBSD is very slow without disabling acpimadt whereas #FuguIta has no such problems.

Any guidance will be gratefully received.

Thank you.

  • The kernel config of #FuguIta is almost same as GENERIC.
    Differences are as follows:
    nimbus9 amd64 # diff -u GENERIC RDROOT
    --- GENERIC    Mon Jul 20 12:43:03 2020
    +++ RDROOT     Mon Jul 20 12:40:08 2020
    @@ -49,7 +49,7 @@
     option                UDF             # UDF (DVD) file system
     option                MSDOSFS         # MS-DOS file system
     option                FIFO            # FIFOs; RECOMMENDED
    -#option               TMPFS           # efficient memory file system
    +option                TMPFS           # efficient memory file system
     option                FUSE            # FUSE
     
     option                SOCKET_SPLICE   # Socket Splicing for TCP and UDP
    @@ -88,7 +88,7 @@
     pseudo-device nmea    1       # NMEA 0183 line discipline
     pseudo-device msts    1       # MSTS line discipline
     pseudo-device endrun  1       # EndRun line discipline
    -pseudo-device vnd     4       # vnode disk devices
    +pseudo-device vnd     6       # vnode disk devices
     pseudo-device ksyms   1       # kernel symbols device
     #pseudo-device        dt              # Dynamic Tracer
     
    @@ -134,7 +134,12 @@
     option                NTFS            # NTFS support
     option                HIBERNATE       # Hibernate support
     
    -config                bsd     swap generic
    +config                bsd root on rd0a swap on wd0b and sd0b
    +option                RAMDISK_HOOKS
    +option                MINIROOTSIZE=3800
    +option                NKPTP=5
    +
    +pseudo-device   rd              1 # ramdisk
     
     mainbus0 at root
     
    nimbus9 amd64 # 
    So I don't know why it behaves differently.

    Since the storage device used is different between regular OpenBSD(internal HDD, SSD...) and FuguIta(DVD, USB Flashdrive, SD card...) there may be something wrong with the built-in disk device.

    In any case, I think we need to see what's slowing down regular OpenBSD.
    • disk I/O
    • stray interrupts
    • anything else?

      -- kaw? 2020-07-20 (Mon) 12:50:48

  • Thank you for the detailed response. It has to do with buggy bios - APIC. Thank you for sharing #FuguIta with us. -- Fugu?? 2020-07-21 (Tue) 09:49:27
  • With following procedure, you can check whether the internal disk or its corresponding BIOS function causes the problem:
    • In internal disk, make a directory named "ISO" at the root of a partition which is FAT, NTFS, Linux ExtFS or OpenBSD FFS.
    • Put a FuguIta's ungziped ISO image into "ISO" directory.
    • Boot FuguIta with LiveDVD or LiveUSB.
    • The internal disk will be listed as follows:
      scanning partitions: cd0a sd0i sd0j
      FuguIta's operating device(s): cd0a sd0i
      Which is FuguIta's operating device? [default: cd0a] -> sd0i  # in case that sd0 is internal disk
    • Select internal device, then continue booting.

If FuguIta runs slow as OpenBSD with this procedure, the problem could lay on internal disk device. -- kaw? 2020-07-21 (Tue) 16:28:11

  • I had quite a few ideas to test this:
    • Chroot install
    • chain load from a different OS
    • install via different system and move hard drive
    • use a different boot manager
    • install #Fuguita and hack via ramdisk

and one other escaping attention now.
To this end, I started reading through the show and list variables in the UKC config and found that #FuguIta has a lot more that get initialized than vanilla OpenBSD. When that did not work out, I once again disabled acpimadt, installed the operating system and waited for it to boot. The scenario now stood at reordering libraries (library_aslr). I let it complete the first time and then disabled the service via rcctl. This made a dramatic impact on reboot.
Presently, after having run sysupgrade (following -current), the performance is acceptable as good as on a ThinkPad.
My speculation is to do with the execute bit. I haven't read the source code to be certain of this but would appreciate your knowledgeable thoughts on it. I will try the above solution if video and browser performance in unacceptable with my continued testing. -- Fugu? 2020-07-21 (Tue) 19:37:36

  • Summary Update: During upgrade/install, the acpimadt needs to be disabled during runtime only. All things work except for the cpu temperature which is stuck at a very high inordinate value. The only similarity found is when the install medium is flash disk. Fans, hibernate, sleep - power management; userland setup; networking have no problems. Interestingly, #FuguIta also spends some time in kernel reordering but being a ram-mounted filesystem, the time spent is comparatively smaller. This is a two-hard drive machine and OpenBSD live USB is now getting stuck before Install/Upgrade/Interrupt message prompt (custom part of #FuguIta) - seems to be directly correlational to number of partitions. Pressing power option still gives back the prompt. Although the device will not be high workload intensive, lack of temperature monitoring (#FuguIta live also lists the same numbers) is unnerving. -- Fugu? 2020-07-22 (Wed) 14:55:26
  • Thank you for the detailed information.
    Is vanilla OpenBSD slowing down because the CPU temperature is considered high and the CPU clock frequency is low?
    If let apmd enabled and manually change the CPU clock with the apm command, can you see anything relevant? -- kaw? 2020-07-23 (Thu) 12:54:58
  • Hello Kaw: What I meant to say is everything works as in a supported machine except the sensor for reading the cpu temperature is broken.
    My guess is that this failure to initialize during boot is what causes the problem. #FuguIta does not display this behavior since the boot process has custom setup at this exact point where OpenBSD seemingly hangs. Just before shell access, there is an info which says XSDT entry 8 is corrupt. Not sure if OpenBSD devs would want this bug report since this is BIOS initiated.
    When I say userland setup, the fans (two of them) scale according to workload. I stress tested by encoding a video and simultaneously running a 4K Blender video. Everything works once the module is disabled during install/upgrade (workaround with sysupgrade -n) - one time activity only.
    I genuinely look forward to seeing you presenting #FuguIta this weekend. The only time I had these issues was with booting lilo on Slackware though FreeBSD works without complaint.
    Best wishes. -- Fugu? 2020-07-23 (Thu) 23:05:59
  • Thank you Fugu, see you in the Live Stream! #FuguIta -- kaw? 2020-07-24 (Fri) 11:28:18

Former articles are at FuguIta/BBS/9.


Return to Top


Attach file: filepix4.jpg 115 download [Information] filepix3.jpg 130 download [Information] filepix2.jpg 125 download [Information] filepix1.jpg 131 download [Information] filescreego-e.png 125 download [Information] filefiupdate.sh.txt 174 download [Information] fileisotop-665-fi.sh.diff 398 download [Information] fileisotop_desktop1.png 393 download [Information]
Reload  New Edit Freeze Diff Attach Copy Rename  Top Index Search Recent Backups  Help  RSS
Last-modified: 2021-05-21 (Fri) 04:40:06 (122d)