- The added line is THIS COLOR.
- The deleted line is THIS COLOR.
[[FuguIta/BBS/10]]
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.
#author("2023-03-09T12:14:03+09:00;2022-01-19T14:35:04+09:00","default:kaw","kaw")
This page is archived. ~
Current active BBS is [[FuguIta/BBS]].
----
#contents
----
#article
**How to change encrypt password [#qeddb53c]
>[[m3th]] (2021-05-21 (Fri) 04:40:05)~
**Call for Testers - Major Changes in Distribution Images (amd64, LiveUSB) [#m6d665e5]
>[[kaw]] (2021-12-26 (Sun) 00:49:48)~
~
Can I change password ?~
Should I use newdrive command again? ~
I might lose data, if I mistake. ~
#FuguIta~
//
#comment
**6.9 [#saa5a0c8]
>[[m3th]] (2021-05-16 (Sun) 00:09:53)~
The FuguIta LiveUSB distribution image for the amd64 platform uses a disk partitioning method called "Hybrid MBR" to support both legacy BIOS and UEFI boot mechanisms.~
~
~>'''Notice: To avoid posts by spam, a message body without the word '#FuguIta' is rejected.'''~
It is very difficult to post message here. ~
#FuguIta~
This is a convenient method as it allows a single device to boot both legacy BIOS and UEFI, but it is a non-standard method and furthermore, the partition table is difficult to change later.~
~
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? ~
Therefore, I am planning to change the partitioning of the LiveUSB distribution image for amd64 platforms from Hybrid MBR to a regular MBR with a UEFI bootloader built in.~
~
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.&br;I think it is somewhat easier to post articles if you copy and paste the pre-edited articles in a text editor.&br;&br;Now, about the noasks file, first, please check the following matters and let me know the result.&br;&br;1) Do you have only one #FuguIta device attached to your PC? Or is there more than one?&br;&br;2) Is the data storage area an encrypted partition?&br;&br;Please let me know the above. -- [[kaw]] &new{2021-05-16 (Sun) 01:36:05};
- >'''Do you have only one #FuguIta device attached to your PC?'''&br;Yes,I do. The data storage area an encrypted partition. #FuguIta -- &new{2021-05-16 (Sun) 05:59:11};
//OK、あなたは暗号化パーティション付きのFuguItaデバイスを一つだけPCに着しているんですね。
-OK, so you have only one #FuguIta device with an encrypted partition attached to your PC.~
//あなたのnoasksファイルが無視されるのは、それが暗号化パーティションの中にあるからだと思います。あなたがパスフレーズを力するまではFuguItaはnoasksファイルを見ることができません。
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.~
//ですから、あなたはnoasksファイルを暗号化されていないパーティションに置いておく要があります。
So you need to keep the noasks file in an unencrypted partition.~
//例えば、noasksファイルを編集した後、それをsd0aに置くには以下のようにします。
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
//noasksファイルの容は以下のようになります
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
//このnoasksファイルが読み取られると、FuguItaはパスフレーズの力で停止します。
When this noasks file is read, FuguIta will stop with the input of the passphrase.~
//そのパスフレーズを力し、つづいて再度モード3の指定と、新たに現れた復号化デバイスを手動で入力して下さい。私が今、使っているMacBook Proが正にそのような使いかたをしています。
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.~
We currently have [[a test image>https://jp1.dl.fuguita.org/test/FuguIta-7.0-amd64-202112241.img.gz]] uploaded to mirrors.~
~
//次に、ファイル読み込み中に表示されるエラーメッセージですが、''"softraid0" "i/o error 5"''で検索したところ沢山ヒットしました。OpenBSDのデバイスドライバの問題のようです。
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]] &new{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]] &new{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]] &new{2021-05-16 (Sun) 14:05:40};
I would appreciate it if you could let me know if you can boot FuguIta LiveUSB using [[this image>https://jp1.dl.fuguita.org/test/FuguIta-7.0-amd64-202112241.img.gz]].~
~
Based on the results, I would like to decide whether to change the format of the distribution image or not.~
~
Reference: [[FuguIta's UEFI/GPT support>EBUG勉強会/20190223_UEFI_GPT]]~
//
#comment
**Another new tool on 6.9 [#b44793c3]
>[[kaw]] (2021-05-14 (Fri) 12:20:44)~
**日本語デスクトップ環境構築の記事 [#g835ff53]
>[[kaw]] (2021-12-21 (Tue) 00:54:01)~
~
エンジニアの報共有サイト Qiita に記事を投稿しました。
>>OpenBSDライブシステム「河豚板」の日本語デスクトップ環境を構築する~
https://qiita.com/ykaw/items/ca008a34d73d5f1f6dd8
>日本語デスクトップ環境に的を絞って説明していますので、網的な説明を行っている「河豚板ガイド」よりは見通しのよいものとなっていると思います。~
また、FirefoxやLibreOfficeなどの日本語設定については、現行バージョン用の体的な説明を行っていますので、この部分も有用かと思います。
//FuguIta 6.9では、もう一つ新しいツール remaster_dvd.sh が導されました。
//これはその名のとおり、FuguIta LiveDVDのISOイメージをリマスターします。
//このツールは、動作中のFuguIta LiveDVD、あるいはFuguIta LiveUSBのどちらでも使用可能です。
//以下にremaster_dvd.shの使用例を示します。
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.
//まず、作業用ディレクトリを作成し、sysmedia以下にあるLiveDVDのコンテンツをコピーします。
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
//コピーされたsysmediaディレクトリでremaster_dvd.shを実行します。
//基本的にはこれだけです。
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)
//remaster_dvd.shの実行が完了すると、作業用ディレクトリにISOイメージファイルが作成されています。
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
//sysmedia中にfuguita-6.9-amd64.ffsimgというファイルがありますが、この中にFuguItaのファイルツリーが格納されています。
//このファイルツリーのファイルを修正することで、LiveDVDをカスタマイズすることができます。
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
:
:
//
#comment
**New tool on FuguIta 6.9 [#r8011bc5]
>[[kaw]] (2021-05-12 (Wed) 11:05:49)~
**How to use new network configuration tool [#z73c1679]
>[[kaw]] (2021-11-19 (Fri) 21:15:04)~
~
#FuguIta's new network configuration tool, mentioned in the previous article, is currently being tested, but here is how to use it.~
~
gennetconfs generates configuration files for your network. The configuration done when FuguIta is started is also done by this gennetconfs, so please follow the instructions below.
// 使用法: gennetconfs [-b] [-q] [設定名]
// -b: バナーの表示を抑制します
// -q: 設定値に対する説明を抑制します
Usage: gennetconfs [-b] [-q] [config_name]
-b: Suppress the display of banners
-q: Suppress description of configuration items
//設定名を指定すると、/etc/netconfs/設定名 というディレクトリの中に設定ファイルを生成します。
//指定しない場合は、カレントディレクトリに生成します。
If a config_name is specified, configuration files will be created in the directory ''/etc/netconfs/'''''''config_name''''' . If it is not specified, it will be created in the current working directory.
//gennetconfsを実行すると、各種設定値の力を求められます。プロンプトが
// [foo] ->
//となっている場合は、デフォルト値がfooであり、ENTERのみを力するとfooが設定値として入力されたことになります。
When you run gennetconfs, you will be prompted to enter various configuration values. If the prompt is
[foo] ->
the default value is foo, and entering only ENTER will cause foo to be entered as the configuration value.~
//1. ホスト名の力
//ホスト名は、ドメイン付き(FQDN: Fully Qualified Domain Name)で力します。
//閉じたネットワークで使用する場合など、ドメイン無しで構わない場合はドメイン部分を省略できます。
~
1. Entering the Host Name~
Enter the host name with domain (FQDN: Fully Qualified Domain Name). You can omit the domain part if you do not need it, for example, when using it in a closed network.
Hostname with domain part (FQDN):
only host name without domain part is also OK.
-> fugu-demo.localnet
//2. 有効にするIPプロトコルバージョン
//デフォルトは「64」(IPv6, IPv4に有効化し、名前解決はIPv6を優先する)です。
~
2. which IP protocol version to enable~
The default is "64" (enable both IPv6 and IPv4, but give priority to IPv6 for name resolution).
IP protocol version(s) to be enabled: 4, 6, 46, 64 or "none"
4: enable only IPv4
6: enable only IPv6
46: give priority to IPv4 name resolution
64: give priority to IPv6 name resolution
none: operate as standalone
[64] ->
//「none」を指定した場合は、ネットワークを使用しないスタンドアロンな機器として動作し、gennetconfsによる設定はこれで終了します。
If "none" is specified, the device will operate as a standalone device that does not use the network, and the configuration by gennetconfs will be completed.~
//3. ネットワークインターフェースの指定
~
3. Specifying the network interface~
//続いて、ネットワークデバイスの一覧が表示されるので、設定を行いたいデバイスを１つだけ指定します。
Next, a list of network devices will be displayed, and you need to specify only one device that you want to configure.
Network Interfaces: Choose one
NIC type Name
-------- ----- ------------
bge1 ether Broadcom BCM57766
ure0 ether Realtek USB 10/100/1000 LAN
run0 wifi Ralink 802.11 n WLAN
[bge1] ->
//リストの一番頭に表示された機器がデフォルトになります。
//Wi-Fiデバイスを指定した場合は、引続きSSIDと暗号化キーの力を求められます。
The device that appears at the top of the list will be the default. If you specify a Wi-Fi device, you will be prompted to enter the SSID and encryption key.
[bge1] -> run0
Wi-Fi settings:
SSID -> OUR-WIFI-NETWORK
WPA Key -> OUR-WIFI-SECRET
//WPAの鍵でENTERのみを押すとWEPの力となります。
If you press only ENTER with the WPA key, you will be prompted to enter WEP.
WPA Key ->
WEP Key -> OUR-WEP-SECRET
//WEPの鍵でENTERのみを押すと暗号化なしでの接続を指定したことになります。
If you press only ENTER with the WEP key, it means that you specify the connection without encryption.~
//4. IPv6の設定
//IPv6を有効にした場合は、以下の設定力が表れます。
//説明にあるように、"auto"、あるいは手動によりアドレスを設定します。
//多くの場合、"auto"で対応可能です。
//"/prefixlen"を省略した場合、"/64"を指定したと見做されます。
~
4. IPv6 Settings~
If you have enabled IPv6, the following configuration input will appear. Set the address to "auto" or manually, as described in the description. In most cases, "auto" will work. If "/prefixlen" is omitted, it is assumed that "/64" is specified.
IPv6 - address and routing:
Enter "auto" or "IPv6_address[/prefixlen] [default_gateway]"
"auto" is an automatic setting by SLAAC.
The "/prefixlen" part can be an integer between 0 and 128.
If there is no default gateway, set the second field to "none" or leave it blank.
[auto] ->
//4. IPv4の設定
//IPv4を有効にした場合は、以下の設定力が表れます。
//説明にあるように、DHCPでは"auto"、そうでない場合は、手動によりアドレスを設定します。
//"/mask"を省略した場合は、適切と思われるネットマスクが仮定されます。
~
5. IPv4 Settings~
If you have enabled IPv4, you will be prompted to enter the following settings: "auto" for DHCP, as described in the description; otherwise, set the address manually.
If you omit "/mask", a netmask that seems appropriate will be assumed.
IPv4 - address and routing:
Enter "auto" or "IPv4_address[/mask] [default_gateway]"
"auto" is an automatic setting by DHCP.
The "/mask" part can be specified in either format, such as "/255.255.255.0" or "/24".
If there is no default gateway, set the second field to "none" or leave it blank.
[auto] -> 192.168.1.147/24 192.168.1.254
//5. DNSサーバの設定
//IPv4あるいはIPv6の設定で、手動によるアドレス設定を行った場合、DNSサーバの設定力が表れます。
//IPアドレスを直接指定して通信する場合はDNSサーバは要ありませんので、ENTERのみ入力します。
~
6. DNS Server Settings~
If you have configured IPv4 or IPv6 addresses manually, you will be prompted to enter DNS server settings. If you want to communicate directly by specifying IP addresses, you do not need to use DNS servers, so enter only ENTER.
DNS servers: up to 3 IP addresses, separated by spaces
-> 192.168.1.253
//最後に、今まで力した設定値を反映した設定ファイルが「/etc/netconfs/設定名」のディレクトリ下に書き出されます。
Finally, configuration files reflecting the configuration values you have entered will be written to the directory "/etc/netconfs/config_name".
writing configured values:
/etc/netconfs/default/myname
/etc/netconfs/default/mygate
/etc/netconfs/default/hosts
/etc/netconfs/default/hostname.bge1
/etc/netconfs/default/resolv.conf
~
//gennetconfsは設定ファイルを生成するだけで、その設定値を活性化させることはしません。
//設定値を有効にするには、chnetconfコマンドを使用します。
//このchnetconfも、FuguItaの起動時に部的に実行されています。
// Usage: $0 [-d config_name|-r|-f config_name] | [config_name]
// -d: don't perform /etc/netstart, link/copy files only
// -r: reset all network interfaces
// -f: force reconfiguration even if current conf doesn't exist
//chnetconfは、実際には以下のことを行います。
//-現在の設定を保持している/etcのファイルを消去します
//-てのネットワークインターフェースを不活性化します
//-指定されたconfig_nameの設定ファイルを/etc以下にリンク/コピーしたら、/etc/netstartを実行し、ネットワーク設定を活性化します
gennetconfs only generates the configuration files, it does not activate the configuration values.~
To activate the configuration values, use the chnetconf command. This chnetconf is also executed internally when FuguIta is started.
Usage: chnetconf [-d config_name| -r| -f config_name] | [config_name].
-d: don't perform /etc/netstart, link/copy files only
-r: reset all network interfaces
-f: force reconfiguration even if current conf doesn't exist
chnetconf actually does the following.
-clear the files in /etc that hold the current configuration
-deactivate all network interfaces
-After linking/copying the configuration files with the specified config_name under /etc/netconfs/config_name, run /etc/netstart to activate the network configuration
//FuguIta 6.9ではネットワークの設定を変更できるツールが提供されました。以下にその使用例を示します。~
//新しい6.9リリースでは、ネットワーク関連の設定ファイルは/etc/netconfs下のサブディレクトリに格納され、/etcから、それらのファイルにシンボリック・リンクが張られています。~
//初期ブートで行った設定は、/etc/netconfs/defaultの中にあります。
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
//例として、homeとofficeという２つの設定を追加してみます。~
//まず、officeから。これは、イーサネットに接続し、固定アドレス設定での使用を想定しています。~
//新しい設定を追加するには、/etc/netconfs以下にディレクトリを作成します。
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
//設定ファイルの作成には、従来から提供されているgennetconfsユティリティを使用します。その使用方法は初期ブートで行う設定と同じです。
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
//gennetconfsによる設定が完了すると、今作成したサブディレクトリの中に設定ファイルが作成されます。
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
//これらの設定を実際に反映させるには、chnetconfユティリティを使用します。~
//chnetconfを実行すると、/etcからこれらのファイルへ向ってシンボリックリンクが作成された後、/etc/netstartを部的に実行し、設定を変更します。
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
//引続き、同様にhomeの設定を作成してみます。こちらはWiFi接続でDHCPを使用することを想定しています。
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
//これで、従来のdefaultを含め、３つのネットワーク設定が作成されました。~
//これらの設定はchnetconfユティリティを使用して、いつでも切り換えることができます。
We have now created three network configurations, including the default. ~
You can switch between these settings at any time using the chnetconf utility.
//>chnetconfを利用すると、gennetconfsで生成した複数の設定をオンザフライで切り換えて使用することができます。
>Using chnetconf, you can switch between multiple configurations generated by gennetconfs on the fly.
//
#comment
**incorrect link for OpenBSD 6.9 patches [#tf462b87]
>[[Mel]] (2021-05-11 (Tue) 14:26:19)~
**New network configuration tool for #FuguIta [#y89e5aae]
>[[kaw]] (2021-11-16 (Tue) 13:24:17)~
~
in front page of #FuguIta there is "Patch 001 of OpenBSD 6.9 has been applied."~
OpenBSD 7.0 has [[changed how IP addresses and DNS autoconfiguration works>https://undeadly.org/cgi?action=article;sid=20210717141912]].~
~
when you click on the link, it goes to OpenBSD 6.8 list of patches.~
In response to this, FuguIta is [[pre-publishing a test version>https://jp1.dl.fuguita.org/test/]] with changes to the network configuration part of the boot (= gennetconfs utility).
-In the normal case, except for the hostname, the configuration items can be used with the default settings by simply entering the ENTER key.
-The protocol version to be used is "64" (both IPv6 and IPv4 can be used. IPv6 has priority in name resolution) is now the default.
-IPv6 and IPv4 can now be configured separately.
>If you want to try the LiveUSB version, you can either [[remaster it from LiveDVD>FuguIta/StartGuide#q4366f48]] or [[use the fiupdate tool>河豚板ガイド#re866f1d]] to update from the current version.~
~
For more information about the changes in the tool, please refer to the CVS development repository, [[a copy of which is available on GitHub>https://github.com/ykaw/FuguIta/commit/6643aebd56e04fc3996fd051a0d719309a79be64]].
//
- Fixed it. Thank you! #FuguIta -- [[kaw]] &new{2021-05-11 (Tue) 14:30:43};
#comment
**Video Streaming by FuguIta [#n1959a4a]
>[[kaw]] (2021-05-01 (Sat) 08:06:34)
**#FuguIta 7.0 ISO files [#c5c5a693]
>[[arfian]] (2021-11-11 (Thu) 08:01:15)~
~
I think it is a better idea when release a collection of new ISO we also provide the SHA256 or better SHA512 for better integrity and clarity. ~
Thanks...~
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>https://screego.net/]]. 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.
|&ref(screego-e.png,,50%);|
|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.
|&ref(pix1.jpg);|&ref(pix2.jpg);|
|CENTER:Operation Booth|CENTER:Screego Server|
|&ref(pix4.jpg);|&ref(pix3.jpg);|
|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>https://github.com/ykaw/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};
- SHA256 has been placed on each mirror site; MD5 will remain for a while for compatibility, as it is currently used by the update tool, fiupdate, to check for corrupted files. Currently, these files are only used to check for corruption of #FuguIta files, for example during download. To verify the legitimacy of the files, these message digests need to be signed with a private key and the public key needs to be distributed, but we are not prepared for that at this stage. This will be an issue for the future. -- [[kaw]] &new{2021-11-12 (Fri) 16:50:54};
#comment
**FuguIta development [#x488e4f5]
>[[Mel]] (2021-04-27 (Tue) 15:35:18)~
**I have found [ command. [#wa726a6f]
>[[m3th]] (2021-11-07 (Sun) 05:41:01)~
~
i try to follow how to setup development for #FuguIta from this JPN page "河豚板の開発ツールを使う - LiveDVDのカスタマイズと作成".~
#FuguIta-7.0-amd64-202111011.img.gz ~
~
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?~
$ ls -l /bin/[
-r-xr-xr-x 2 root bin 123320 Oct 17 13:25 /bin/[
$ /bin/[
[: missing ]
//
-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};
#comment
**syspatch [#w1dcb454]
>[[m3th]] (2021-04-24 (Sat) 18:32:09)~
- Curious! I have found same file other *BSD. Sorry for my post. #FuguIta -- [[m3th]] &new{2021-11-07 (Sun) 12:30:46};
- /bin/[ is equivalent to /bin/test.~
Let's see their inode numbers and link counts.~
$ ls -li /bin/[ /bin/test
16207 -r-xr-xr-x 2 root bin 123320 Oct 17 22:25 /bin/[
16207 -r-xr-xr-x 2 root bin 123320 Oct 17 22:25 /bin/test
And note that ksh has same built-in commands.~
~
Can I syspatch to #FuguIta?~
In FuguIta's scripts, i.e. /boottmp/rc, /boottmp/usbfadm and so on, [ command is used frequently.~
~#FuguIta -- [[kaw]] &new{2021-11-07 (Sun) 18:59:08};
//
-Because FuguIta is different from regular OpenBSD in many ways, syspatch cannot be used with FuguIta.~
#aname(vavpn)
**Video/Audio transmission over VPN by FuguIta [#x288f89b]
>[[kaw]] (2021-11-02 (Tue) 15:43:48)~
~
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.~
''The plan'' ~
~
Another reason why syspatch cannot be used is that the filesystem configuration is also very different from that of regular OpenBSD.~
I received a request to send video and audio from a studio to a venue using IP transmission equipment for an event.~
~
FuguIta provides the fiupdate utility to update the system, so please use it if you are using LiveUSB.~
And there were two limitations to this job as follows.~
~
For more information on updating FuguIta, please refer to the following article.~
>>1. a pair of IP transmission devices work well when directly connected, however, due to a problem with the web UI, we cannot change some of the settings, such as the IP address, which means that transmission over the Internet is impossible as it is.~
~
--Official Description - FuguIta Guide
---河豚板をアップデートする ("Updating FuguIta", written in Japanese)
http://fuguita.org/index.php?%B2%CF%C6%DA%C8%C4%A5%AC%A5%A4%A5%C9#h2ce3537
2. We can change the settings of the edge router in the studio, but we don't know about the router in the venue. In other words, we cannot confirm whether we can set up port forwarding so that the Internet can communicate with hosts in the venue's network.~
~
--Article in this BBS
---Live Update for FuguIta LiveUSB ~
http://fuguita.org/index.php?FuguIta%2FBBS#kc657395
#ref(L2-Tunnel.png,wrap,around,right,40%)
>To solve this problem, we decided to build a VPN between the studio and the venue, and connect the IP encoder in the studio to the IP decoder in the venue using Layer 2. Once the VPN line is established, communication is possible from either direction. And the two ends of the VPN can be thought of as being pseudo-directly connected by LAN cables.~
~
--Tutorial video by Zen_Floater2
---Updating FuguIta 6.8 using the fiupdate tool ~
https://www.bitchute.com/video/16CEJD3jJOJ2/
Of course, we use OpenBSD and FuguIta to solve this kind of problem.~
To build a VPN, [[WireGuard>https://www.wireguard.com/]], or [[wg(4)>https://man.openbsd.org/wg.4]], which appeared in OpenBSD 6.8, seemed to be useful.~
Using WireGuard in practice, we found that it was very easy to build a VPN circuit.~
#clear
Settings for WireGuard at the studio site is as follows:
---- hostname.wg1 --------------------
wgkey PRIVKEY-OF-THIS-PEER
wgport 7501
wgpeer PUBKEY-OF-HIS-PEER wgaip 172.16.54.1/32 wgpka 0
inet 172.16.54.254 255.255.255.0
mtu 1380
up
The reason the wg number is 1 is to account for the possibility that other peers may connect in the future. ~
The reason why wgpka is 0 is because the Nat router on the other side is not forwarding the port, so keep alives will not occur.~
~
~-- [[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};
#comment
**Prototype from snapshot [#x541ef23]
>[[kaw]] (2021-03-23 (Tue) 18:01:06)~
Next, we look at the venue.
---- hostname.wg0 --------------------
wgkey PRIVKEY-OF-THIS-PEER
wgport 8501
wgpeer PUBKEY-OF-HIS-PEER wgendpoint 153.246.158.51 7501 wgaip 172.16.54.0/24 wgpka 5
mtu 1380
inet 172.16.54.1 255.255.255.0
#ref(Network.png,wrap,around,left,40%)
There was one more problem that we had to solve in using WireGuard.~
That is, WireGuard is a Layer 3-only VPN.~
This time, we want to connect the IP encoder and the IP decoder pseudo-directly, so we need to connect them on Layer 2.~
~
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>http://fuguita.org/index.php?FuguIta%2FDownload]].
~
Your trial reports are welcome.~
Therefore, I now decided to use [[etherip(4)>https://man.openbsd.org/etherip.4]] to flow Ethernet frames into WireGuard VPN.~
This seemed to achieve our goal.~
#clear
Here is the configuration of the physical devices on the studio side. ~
bge0 is connected to LAN, and axe0 to the video encoder.
---- hostname.bge0 ------------------
inet 192.168.1.193 255.255.255.0 NONE
up
---- hostname.axe0 ------------------
up
And here is the endpoint of the etherip tunnel.
---- hostname.etherip1 --------------
tunnel 172.16.54.254 172.16.54.1
up
Then we build a [[bridge(4)>https://man.openbsd.org/bridge.4]] between the L2 endpoint and the physical device.
---- hostname.bridge1 ---------------
add etherip1
add axe0
up
Finally, we configure sysctls.
---- sysctl.conf --------------------
net.inet.ip.forwarding=1
net.inet.etherip.allow=1
The configuration of the venue side is almost the same as the studio side. Overall, the configuration is symmetrical.
---- hostname.msk0 ------------------
inet 192.168.1.193 255.255.255.0 NONE
---- hostname.axe0 ------------------
up
---- hostname.etherip0 --------------
tunnel 172.16.54.1 172.16.54.254
up
---- hostname.bridge0 ---------------
add etherip0
add axe0
up
---- sysctl.conf --------------------
net.inet.ip.forwarding=0
net.inet.etherip.allow=1
//
- 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};
#comment
**Change of mirror servers [#s5b8d5d2]
>[[kaw]] (2021-02-16 (Tue) 19:00:58)~
''The Result''~
~
Two new mirror servers in Europe are now in operation.~
With the combination of WireGuard+EtherIP, we were able to transmit video and audio in good condition.~
~
They are [[de.dl.fuguita.org and fr.dl.fuguita.org>FuguIta/Download]], the successors to eu.dl.fuguita.org.~
We transmitted a stream of about 25 Mbps on a line with a bandwidth of over 100 Mbps.~
~
eu.dl.fuguita.org will be out of service in a few weeks.~
However, we found that the video and audio transmissions were very sensitive to fluctuations in the time axis.~
In addition to the VPN line, we had an SSH connection for maintenance purposes, but when a certain amount of data was transmitted over this SSH line, the VPN packets would wait, causing the video to freeze for a short time.~
In order to solve this problem, we will need to use [[pf(4)>https://man.openbsd.org/pf.4]] to control packet priority.~
This will be an issue for next time.~
~
I would like to express our sincere gratitude to the administrators of eu.dl.fuguita.org and everyone who are providing the mirror servers.~
|CENTER:|CENTER:|c
|Video encoder+VPN endpoint|VPN endpoint+Video decoder|
|&ref(pix-encoder.jpg,,40%);|&ref(pix-decoder.jpg,,40%);|
|~|The venue|
|~|&ref(pix-venue.jpg,,40%);|
Lastly, I would like to discuss the benefits of using FuguIta.~
At each stage of designing, building, and deploying a VPN, we had multiple network configurations and needed to quickly switch between them or migrate the configurations between devices. FuguIta's usbfadm and gennetconfs/chnetconf tools made it possible for us to do these tasks quickly.
//
- Could you share your WireGuard's hostname.if(5) and pf.conf(5), for others to learn the setup? #FuguIta -- [[Alex]] &new{2021-11-02 (Tue) 21:41:36};
- Okay Alex, wait please. #FuguIta -- [[kaw]] &new{2021-11-02 (Tue) 22:47:07};
- added description for setup. pf.conf(5) doesn't have been modified. I left it default. #FuguIta -- [[kaw]] &new{2021-11-03 (Wed) 12:04:43};
#comment
**Laptop Connected to Monitor [#d67b26b7]
> (2021-01-30 (Sat) 07:41:07)~
**English version of FuguIta Guide [#zd31d80d]
>[[kaw]] (2021-11-02 (Tue) 11:41:34)~
~
I can use a second monitor with OpenBSD. I cannot use a second monitor with #FuguIta.~
[[English translation of #FuguIta Guide>https://liquorstane.ynh.fr/fuguita/]] is now available.~
This was made possible by the generous effort of Alfredo Vogel.~
~
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).~
I would like to express my gratitude to him for his great contribution.~
//
- 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]] &new{2021-02-01 (Mon) 09:21:51};
#comment
**Recent articles on FuguIta [#s3725834]
>[[kaw]] (2021-01-09 (Sat) 23:04:26)~
**FuguIta 7.0 [#s47acb52]
>[[vanitarium]] (2021-10-27 (Wed) 20:54:43)~
~
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>https://dataswamp.org/~solene/2020-11-18-fuguita.html]]~
~
- a review by Jesse Smith (Distrowatch.com)~
--DistroWatch Weekly, Issue 895 - [["Feature Story - FuguIta 6.8">https://distrowatch.com/weekly.php?issue=20201207#fuguita]]~
~
- tutorial videos by Zen_Floater2~
--[[FuguIta Tutorial 1>https://www.bitchute.com/video/m9bp39TgAfWv/]]
--[[FuguIta Tutorial 2>https://www.bitchute.com/video/rw2Ipuq6X7wU/]]
--[[Updating FuguIta 6.8 using the fiupdate tool>https://www.bitchute.com/video/16CEJD3jJOJ2/]] ~
#FuguIta I had a kernel panic because it did not find the wifi firmware: it returned that firmware folder was empty. Maybe it is the wrong URL? #FuguIta~
Correct URL is firmware.openbsd.org/~
>I am deeply grateful to the authors of these articles.~
//
- #FuguIta solved... dns name server error -- [[vanitarium]] &new{2021-10-27 (Wed) 21:39:35};
#comment
**FuguIta 6.8 tools [#h48b7ac9]
>[[kaw]] (2020-11-03 (Tue) 23:37:38)~
**FuguIta 7.0 [#yf1a9679]
>[[kaw]] (2021-10-19 (Tue) 23:30:02)~
~
Tools to create a live system based on OpenBSD 6.8 were uploaded at [[tools directory>https://jp1.dl.fuguita.org/tools/]].~
To use this tool, refer the article [[河豚板の開発ツールを使う - LiveDVDのカスタマイズと作成>河豚板ガイド#m0eda68f]] (LiveDVD - Using FuguIta development tools) in the page [[河豚板ガイド]] (FuguIta Guide).
#FuguIta-7.0-{i386,amd64} are currently under testing. They are available in the test directory of the download mirror.~
~
We look forward to your trial reports.~
//
- Should I use /mnt/livecd-config/7.0/amd64/noasks or copy it in /mnt directory? #FuguIta -- [[m3th]] &new{2021-10-31 (Sun) 03:57:29};
- #FuguIta : You should locate noasks at either /mnt or /mnt/livecd-config/7.0/amd64 . -- [[kaw]] &new{2021-11-01 (Mon) 13:31:18};
#comment
**Ventoy Compatibility? [#y323cb09]
>[[Fugu]] (2020-10-24 (Sat) 22:05:09)~
**Translate and host user guide help [#u7c16688]
>[[Vanitarium]] (2021-09-13 (Mon) 18:46:22)~
~
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.~
#FuguIta I am offering you to translate and edit the Japanese version into English and host it on my server. I can set it up as a wiki or a website. If you are happy with that let me know so I can let you proofread it and ok it.~
//
- I've never heard of Ventoy. This seems a quite interesting tool.&br;Looking at [[Ventoy's support list>https://www.ventoy.net/en/isolist.html]], 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 /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]] &new{2020-10-26 (Mon) 19:31:47};
- Thank you #FuguIta for replying. I am working at it now -- [[Vanitarium]] &new{2021-09-14 (Tue) 17:23:33};
- Thank you for starting to work on it. I'm sure it will be beneficial to many #FuguIta users. &br; So please let me know when the translation is all done and ready for review.-- [[kaw]] &new{2021-09-14 (Tue) 19:03:28};
- Thank you#FuguIta for replying.I am working at it now -- [[Vanitarium]] &new{2021-09-14 (Tue) 23:41:06};
#comment
**FuguIta-6.8 status [#oba9dfae]
>[[kaw]] (2020-10-24 (Sat) 00:30:25)~
**login prompt [#jf7f271b]
>[[m3th]] (2021-08-10 (Tue) 03:32:55)~
~
#FuguIta-6.8-i386 and FuguIta-6.8-amd64 are now under test.~
These are at [[test>http://jp1.dl.fuguita.org/test/]] directory at download mirrors.~
Without typing anything, can I see the login prompt like OpenBSD?~
This is my request. Without my help, mum can use Fuguita.~
~
Your trial report is greatly appreciated.~
#FuguIta~
//
- #FuguIta-6.8-{i386,amd64}-202010251 on the mirrors. This is a release candidate. -- [[kaw]] &new{2020-10-25 (Sun) 13:14:59};
#comment
**Live Update for FuguIta LiveUSB [#kc657395]
>[[kaw]] (2020-09-24 (Thu) 22:13:14)~
- That's exactly what I did for my mother. Please see the following tweets - https://twitter.com/yoshi_kaw/status/1206620780697505792~
~
I'm currently working on a Live Update for #FuguIta LiveUSB.~
This is in beta testing. ~
To accomplish this, you need to~
~
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]] &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};
#comment
**isotop on FuguIta [#vc6211a3]
>[[kaw]] (2020-09-08 (Tue) 14:07:35)~
1. boot #FuguIta normally and set up an operational environment.~
2. save that environment with usbfadm sync.~
3. set up this environment so that it is automatically loaded at boot time and automatically saved when it shutdown.~
~
[[isotop>https://3hg.fr/Isos/isotop/]] is a script to configure and customize vanilla OpenBSD into ready-to-use desktop environment.~
In other words, this is to do everything described in the [["Start Guide">FuguIta/StartGuide]].~
~
I have modified isotop to be able to run on #FuguIta.~
This will allow you to get to the login prompt without any human interaction.~
~
To run isotop.sh on FuguIta after download it, apply this patch &ref(isotop-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.
#ref(isotop_desktop1.png,wrap,50%);
In addition, by adding the DisplayManager.*.autoLogin entry in the /etc/X11/xenodm/xenodm.config file, you can start using X without a login prompt.~
For more information on this, see the online manual xenodm(1).~
~-- [[kaw]] &new{2021-08-12 (Thu) 06:04:43};
//
#comment
**The file layouts of FuguIta [#fcd95af5]
>[[kaw]] (2021-05-25 (Tue) 12:41:15)~
**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:~
https://www.youtube.com/watch?v=4wPSr1WPH3U~
~
And the document is at [[河豚板#OSC2020]]~
Now, I will try to describe the file layout structure of #FuguIta.
//
- To those who do not understand Japanese:&br;Auto-translated subtitles have been greatly improved.&br;&br;[[Talk about OpenBSD and #FuguIta>https://www.youtube.com/watch?v=4wPSr1WPH3U]] -- [[kaw]] &new{2020-08-07 (Fri) 14:22:35};
The first figure shows the file layout in boot mode 0 (Click the figure to enlarge).~
As examples, the paths /bin/ed, /usr/bin/vi, and pkg_added /usr/local/bin/emacs are shown.
#ref(fi-filesys-mode0.png,wrap,around,left,50%)
The root file system is rd(4). This rd(ram disk) device is attached to the kernel and has been already mounted from the system boot time.
Under the root, there is an unfamiliar directory called "boottmp".
This is where you will find the commands needed at the very beginning of the system boot, and utilities specific to FuguIta.
#comment
The FuguIta device itself, a DVD or USB flash drive, which holds the boot loader, OS kernel, and file system images. It is mounted read-only on /sysmedia.
**OSC2020新潟オンラインで河豚板の発表を行います。&br;Talk about FuguIta at OSC2020 Niigata [#e045c499]
>[[kaw]] (2020-07-22 (Wed) 15:27:51)~
The filesystem image in /sysmedia is mapped to /dev/vnd4 and mounted on /fuguita. This is the OpenBSD file tree. This is pretty much as it should be, except for a few modifications to fit to the live system. Also, this is read-only. So no files can be created, modified, or deleted under it.
/ram is a memory file system called TMPFS (temporary file system), which is both readable and writable.
Files that need to be modified, such as /etc/*.conf, your own data under /home/YOU, and the pkg_added program, are located on this. In addition, files that are rarely modified are replaced by symbolic links towards equivalent files in /fuguita. This will reduce the memory usage of TMPFS.
#clear
~
Open Source Conference 2020 Online/Niigataが7月25日(土)に開催されます。~
今回はオンラインでの開催になります。https://ospn.connpass.com/event/181888/ の開催概要ページよりZoom参加に登録頂くか、YouTube Liveにてご視聴下さい。~
#ref(fi-filesys-mode1.png,wrap,around,left,50%)
Next is boot mode 1.
This is the same as mode 0, but /usr is symbolically linked to /fuguita/usr.
This makes the boot faster and uses less memory than mode 0 by not copying/linking /usr to /ram.
However, /usr/local is not writable, so pkg_add is not possible.
#clear
~
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)>https://www.ebug.jp/]]. ~
Please register for Zoom participation from the overview page of https://ospn.connpass.com/event/181888/ , or watch it on YouTube Live.~
#ref(fi-filesys-mode2.png,wrap,around,left,50%)
Finally, there is boot mode 2.
This is much simpler than modes 0 and 1.
Only / and /ram are mounted, and all external devices are unmounted.
Of course, all files can be modified.
#clear
~
Note that usbfadm sync will only save the data that exists in /ram TMPFS at boot mode 0, 1, or 2.
//
- 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:
|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};
#comment
**Boot mode difference [#cd61aa39]
>[[Fugu]] (2020-07-19 (Sun) 15:51:32)~
**How to change encrypt password [#w94bbc7d]
>[[m3th]] (2021-05-21 (Fri) 04:40:05)~
~
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.~
Can I change password ?~
Should I use newdrive command again? ~
I might lose data, if I mistake. ~
#FuguIta~
//
-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.
- Use bioctl command with -P option.~
https://man.openbsd.org/bioctl.8
~-- [[kaw]] &new{2021-05-21 (Fri) 14:19:05};
- I changed password. Now, I can not reply 6.9 thread. I noticed that my /mnt/something directories are deleted when I reboot #FuguIta. Should I create them in /ram/home/m3th directory instead of /mnt -- [[m3th]] &new{2021-05-23 (Sun) 03:31:35};
- According to [[hier(7)>https://man.openbsd.org/hier]], /mnt is "Empty directory commonly used by system administrators as a ''temporary'' mount point".&br;usbfadm will only store files and directories that exist in tmpfs mounted in /ram. (excluding /tmp, which is also for temporary use).&br;>'''Should I create it in the /ram/home/m3th directory instead of /mnt?'''&br;Yes, I think that is the proper way. -- [[kaw]] &new{2021-05-23 (Sun) 23:14:53};
>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};
#comment
----
Former articles are at [[FuguIta/BBS/9]].
Former articles are at [[FuguIta/BBS/10]].
----
Return to [[Top>Welcome]]
![[PukiWiki]](image/pukiwiki.png "[PukiWiki]")
