Your message?

Notice: To avoid posts by spam, a message body without the word '#FuguIta' is rejected. ~
Please include the word in your message text.
**Video Streaming by FuguIta [#n1959a4a]
>[[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

-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.

|CENTER: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.

|CENTER:Operation Booth|CENTER:Screego Server|
|CENTER:WiFi Access Point|CENTER:Video 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]] &new{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. &br;#FuguIta -- [[kaw]] &new{2021-05-02 (Sun) 10:47:08};


**FuguIta development [#x488e4f5]
>[[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]] &new{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]] &new{2021-04-28 (Wed) 07:42:24};


**syspatch [#w1dcb454]
>[[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.~
--Official Description - FuguIta Guide
---河豚板をアップデートする ("Updating FuguIta", written in Japanese)
--Article in this BBS
---Live Update for FuguIta LiveUSB ~
--Tutorial video by Zen_Floater2
---Updating FuguIta 6.8 using the fiupdate tool ~
~-- [[kaw]] &new{2021-04-25 (Sun) 13:20:46};
- I have used fiupdate. Now, #FuguIta is 6.8-amd64-202104141 -- [[m3th]] &new{2021-04-25 (Sun) 15:02:05};


**Prototype from snapshot [#x541ef23]
>[[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]] &new{2021-04-27 (Tue) 15:25:04};


**Change of mirror servers [#s5b8d5d2]
>[[kaw]] (2021-02-16 (Tue) 19:00:58)~
Two new mirror servers in Europe are now in operation.~
They are [[ and>FuguIta/Download]], the successors to
~ will be out of service in a few weeks.~
I would like to express our sincere gratitude to the administrators of and everyone who are providing the mirror servers.~



**Laptop Connected to Monitor [#d67b26b7]
> (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/ >
 # vnconfig vnd0
 # 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 > /sysmedia/
 # mount -ur /sysmedia
~-- [[kaw]] &new{2021-02-01 (Mon) 09:21:51};


**Recent articles on FuguIta [#s3725834]
>[[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.~
- a review by Solène Rapenne~
-- [[FuguITA: OpenBSD live-cd>]]~
- a review by Jesse Smith (
--DistroWatch Weekly, Issue 895 - [["Feature Story - FuguIta 6.8">]]~
- tutorial videos by Zen_Floater2~
--[[FuguIta Tutorial 1>]]
--[[FuguIta Tutorial 2>]]
--[[Updating FuguIta 6.8 using the fiupdate tool>]] ~

>I am deeply grateful to the authors of these articles.~



**FuguIta 6.8 tools [#h48b7ac9]
>[[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のカスタマイズと作成>河豚板ガイド#m0eda68f]] (LiveDVD - Using FuguIta development tools) in the page [[河豚板ガイド]] (FuguIta Guide).



**Ventoy Compatibility? [#y323cb09]
>[[Fugu]] (2020-10-24 (Sat) 22:05:09)~
Hello kaw:~
Any chance of getting #FuguIta working with ventoy at
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.&br;Looking at [[Ventoy's support list>]], it seems that the operation of #FuguIta has failed.&br;In the first place, it seems that BSD-based OS such as OpenBSD itself is not supported very well. &br;-- [[kaw]] &new{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]] &new{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>河豚板ガイド#b882fb9c]] of the FuguIta Guide. -- [[kaw]] &new{2020-10-26 (Mon) 10:49:35};
- Chainloaded from Grub using set root=(hdX,msdosX) and kopenbsd /  #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]] &new{2020-10-26 (Mon) 19:31:47};


**FuguIta-6.8 status [#oba9dfae]
>[[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]] &new{2020-10-25 (Sun) 13:14:59};


**Live Update for FuguIta LiveUSB [#kc657395]
>[[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
 # 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)
 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
      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...
 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
We welcome your trial report.
- revised this script, See . -- [[kaw]] &new{2020-10-05 (Mon) 10:58:51};
- #FuguIta-6.7-*-202010071 has this. (Still can't handle tarball, sorry arm64 user) -- [[kaw]] &new{2020-10-16 (Fri) 00:40:20};


**isotop on FuguIta [#vc6211a3]
>[[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 on FuguIta after download it, apply this patch &ref(; .~
Then run install script as a root.
 $ ftp
 $ patch <
 # sh
Here's a screenshot of FuguIta configured by isotop.



**Archive video of FuguIta Talk on OSC2020 Niigata [#w928318a]
>[[kaw]] (2020-08-01 (Sat) 03:37:52)~
Video of Talk about #FuguIta at OSC2020 Niigata has been published:~
And the document is at [[河豚板#OSC2020]]~

- To those who do not understand Japanese:&br;Auto-translated subtitles have been greatly improved.&br;&br;[[Talk about OpenBSD and #FuguIta>]] -- [[kaw]] &new{2020-08-07 (Fri) 14:22:35};


**OSC2020新潟オンラインで河豚板の発表を行います。&br;Talk about FuguIta at OSC2020 Niigata [#e045c499]
>[[kaw]] (2020-07-22 (Wed) 15:27:51)~
Open Source Conference 2020 Online/Niigataが7月25日(土)に開催されます。~
今回はオンラインでの開催になります。 の開催概要ページより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 , or watch it on YouTube Live.~

- YouTube Live Stream will be broadcast at .~
The live stream will begin at 12:30JST (03:30UTC) on 25 Sat, July 2020.~
There will be three BSD-related talks:
|CENTER:Time (UTC)|CENTER:Title|CENTER:Affiliation|CENTER:Speaker|h
|06:00-06:15|Introduction of NetBSD|Japan NetBSD Users Group (JNUG)|Jun Ebihara|
|06:15-06:30|Introduction of FuguIta|Echigo BSD Users Group (EBUG)|Yoshihiro Kawamata|
|06:30-06:45|Introduction of&br;vyos-cli: VyOS CLIs for Ubuntu|Echigo Network Operators Group (ENOG)|Masakazu Asama&br;(also member of EBUG)|
These talks will be available as archives at a later date.
~-- [[kaw]] &new{2020-07-22 (Wed) 23:46:40};


**Boot mode difference [#cd61aa39]
>[[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]] &new{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?]] &new{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]] &new{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]] &new{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]] &new{2020-07-22 (Wed) 14:55:26};
- Thank you for the detailed information.&br;Is vanilla OpenBSD slowing down because the CPU temperature is considered high and the CPU clock frequency is low?&br;If let apmd enabled and manually change the CPU clock with the apm command, can you see anything relevant? -- [[kaw]] &new{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.  &br;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. &br;  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. &br; 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.&br;Best wishes. -- [[Fugu]] &new{2020-07-23 (Thu) 23:05:59};
- Thank you Fugu, see you in the Live Stream! #FuguIta -- [[kaw]] &new{2020-07-24 (Fri) 11:28:18};

Former articles are at [[FuguIta/BBS/9]].
Return to [[Top>Welcome]]

Front page   New Page list Search Recent changes   Help   RSS of recent changes