History of FuguIta/8.0 (No. 6)

• History
• View the diff.
• View the diff current.
• View the source.
• Go to FuguIta/8.0.
  • 1 (2026-10-25 (Sun) 13:28:12)
  • 2 (2026-10-25 (Sun) 13:32:21)
  • 3 (2026-10-26 (Mon) 02:07:10)
  • 4 (2026-10-28 (Wed) 07:27:41)
  • 5 (2026-11-04 (Wed) 08:03:20)
  • 6 (2026-11-04 (Wed) 15:52:17)
  • 7 (2026-11-04 (Wed) 15:52:17)

---

FuguIta 8.0†

Pre-Releases†

Following test versions are in the "test/prerelease" directory of every mirror.

• FuguIta-8.0-i386-202610252
  • The first test version of FuguIta 8.0
  • OpenBSD 8.0 patches up to 005 have been applied.

• FuguIta-8.0-{i386,amd64}-202610261
• FuguIta-8.0-arm64-202610281
  • some minor fixes

• FuguIta-8.0-{i386,amd64,arm64}-202611033
  • release cadidate

Release†

• FuguIta-8.0-{i386,amd64,arm64}-202611041
  We are pleased to announce the official release of FuguIta 8.0, based on OpenBSD 8.0.
  • /etc is now a separate filesystem
    Due to changes in the specifications of the pledge system call, /etc/localtime, which is used to configure the local time zone, must now be either a realpath or a symbolic link to /usr/share/zoneinfo/*. In addition, the target under /usr/share/zoneinfo/* must also be a realpath.
    However, in FuguIta's filepath, these files are organized using symbolic links. As a result, programs that do not declare rpath in their pledge restrictions can no longer properly configure the local time zone.
    To address this issue, FuguIta 8.0 now mounts /etc directly as a TMPFS filesystem.
    
    To configure the local time zone, execute the following command:

    # cp /usr/share/zoneinfo/Asia/Tokyo /etc/localtime

    Note that, at present, the files under /usr/share/zoneinfo/* are not yet realpaths. Therefore, /etc/localtime cannot be configured as a symbolic link pointing to one of these files.

    # ln -sf /usr/share/zoneinfo/Asia/Tokyo /etc/localtime

    Using this method will not configure the local time zone; the system will remain on UTC.

• Web browser behavior has been fixed
  On OpenBSD, Firefox and Chromium use configuration files under /etc/firefox and /etc/chromium to restrict their behavior and the files they can access, thereby enhancing security.
  In FuguIta, however, the file paths specified in /etc/firefox/unveil.* and /etc/chromium/unveil.* did not match the actual filesystem layout. Consequently, certain functions, such as video playback and text input through an Input Method (IM), did not always work correctly.
  In FuguIta 8.0, when Firefox or Chromium is installed using dtjsetup, the corresponding unveil.* files are automatically modified to match FuguIta's filesystem layout.
  
  The modified files are placed in /etc/firefox.fuguita-mode0, while the original files are preserved in /etc/firefox.orig. Chromium uses the same arrangement.

• All patches up to and including patch-005 for OpenBSD 8.0 have been applied.