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.
kaw (2020-01-09 (Thu) 19:16:20)
I wrote a installer to introduce Desktop Environment on #FuguIta.
Desktop: ROX-Filer, xfce, mate, lumina, (not tested yet: GNOME, KDE)
WM: cwm, twm, fvwm, icewm and jwm
and can setup softwares for Japanese (font, kterm, input method).
Save this installdesktop.sh.txt as installdesktop.sh and run it.
armand-mx (2019-12-23 (Mon) 12:35:18)
Hi, Kaw!
How can I install IceWM in #FuguIta as my main window manager?
How many MB or GB of space should I use for the swap partition for the installation of FuguIta?
fuguita-6.6-amd64 # du -sh /usr/local 248K /usr/localIceWM is able to be installed from ports by pkg_add command:
fuguita-6.6-amd64 # pkg_add icewm icewm-1.6.1:libao-1.2.0p1: : ok icewm-1.6.1:libogg-1.3.4: : ok icewm-1.6.1:libvorbis-1.3.6: : ok icewm-1.6.1:libiconv-1.16p0: : ok icewm-1.6.1:flac-1.3.3: : ok icewm-1.6.1:libsndfile-1.0.28: : ok icewm-1.6.1:bzip2-1.0.8: : ok icewm-1.6.1:gettext-runtime-0.20.1p0: : ok icewm-1.6.1:libffi-3.2.1p5: : ok icewm-1.6.1:xz-5.2.4: : ok icewm-1.6.1:sqlite3-3.29.0: : ok icewm-1.6.1:python-3.7.4: : ok icewm-1.6.1:pcre-8.41p2: : ok icewm-1.6.1:glib2-2.60.7: : ok icewm-1.6.1:desktop-file-utils-0.24p0: : ok icewm-1.6.1:fribidi-1.0.7p0: : ok icewm-1.6.1:jpeg-2.0.3v0: : ok icewm-1.6.1:tiff-4.0.10: : ok icewm-1.6.1:png-1.6.37: : ok icewm-1.6.1:jasper-2.0.14: : ok icewm-1.6.1:libxml-2.9.9: : ok icewm-1.6.1:shared-mime-info-1.10p5: : ok icewm-1.6.1:gdk-pixbuf-2.38.2: : ok icewm-1.6.1: : ok Running*tags: : ok fuguita-6.6-amd64 # du -sh /usr/local 147M /usr/localAfter IceWM installed, /usr/local has grown about 150MB.
fuguita-6.6-amd64 # pkg_add rox-filer rox-filer-2.11p3:atk-2.32.0: : ok rox-filer-2.11p3:hicolor-icon-theme-0.17: : ok rox-filer-2.11p3:gtk-update-icon-cache-3.24.12: : ok rox-filer-2.11p3:lzo2-2.10p1: : ok rox-filer-2.11p3:cairo-1.16.0: : ok rox-filer-2.11p3:graphite2-1.3.13p0: : ok rox-filer-2.11p3:harfbuzz-2.6.2: : ok rox-filer-2.11p3:pango-1.42.4p3: : ok rox-filer-2.11p3:libcroco-0.6.13: : ok rox-filer-2.11p3:librsvg-2.46.0: : ok rox-filer-2.11p3:gnome-icon-theme-3.12.0p5: : ok rox-filer-2.11p3:gnome-icon-theme-symbolic-3.12.0p3: : ok rox-filer-2.11p3:gtk+2-2.24.32p5: : ok rox-filer-2.11p3: : ok Running*tags: : ok fuguita-6.6-amd64 # du -sh /usr/local 417M /usr/localAdding ROX-Filer, about 400MB of RAM will be used.
-- kaw 2019-12-24 (Tue) 02:28:22
#!/bin/sh # In case of xenodm # if [ -x /usr/local/bin/dbus-launch -a -z "${DBUS_SESSION_BUS_ADDRESS}" ]; then eval `dbus-launch --sh-syntax --exit-with-session` fi rox -t top -p pin exec icewmand here's a .xsession file I'm using:
#!/bin/sh # # In case of startx # # # if [ -x /usr/local/bin/dbus-launch -a -z "${DBUS_SESSION_BUS_ADDRESS}" ] # then # eval `dbus-launch --sh-syntax --exit-with-x11` # fi # In case of xenodm # if [ -x /usr/local/bin/dbus-launch -a -z "${DBUS_SESSION_BUS_ADDRESS}" ]; then eval `dbus-launch --sh-syntax --exit-with-session` fi # set locate to Japanese Language # export LANG=ja_JP.UTF-8 # Japanse Input Method (UIM) # # # uim-gtk # export XMODIFIERS='@im=uim' # export GTK_IM_MODULE=uim # export QT_IM_MODULE=uim # uim-xim & # uim-toolbar-gtk & # Japanse Input Method (SCIM) # # scim-anthy export XMODIFIERS="@im=SCIM" export GTK_IM_MODULE=xim export QT_IM_MODULE=xim scim -d # Startup Window Manager # wm=icewm # Rewrite this for other WM case "$wm" in cwm) xsetroot -solid gray12 xclock -geometry 115x115-0+0 -analog -update 1 -fg white -bg '#000020' -hd gray25 -hl white & kterm -geometry 179x65+0+0 -fg white -bg black -cr orange -sl 1000 -sn -st & exec cwm ;; jwm|icewm|wmx|fvwm|twm) rox -t top -p pin exec $wm ;; xfce) exec startxfce4 ;; *) exec twm ;; esacPlease omit or modify the lines corresponding to Japanese locale settings. And rewrite wm=icewm when you wish to use other window manager.
-- kaw 2019-12-25 (Wed) 11:00:37
-- kaw 2019-12-26 (Thu) 21:30:00
kaw (2019-11-14 (Thu) 00:52:42)
As described in FuguIta/6.6, when FuguIta-6.6-arm64 runs without a swap partition, its behaviour becomes unstable.
In connection with this, #FuguIta's remastering tool "usbfadm" is being planned to be able to create a swap partition.
kaw (2019-10-31 (Thu) 18:24:34)
The test release of #FuguIta 6.6 is now in the test directory of mirrors.
In 6.6, please notice followings;
- The ISO image is larger than 700MB. Please use DVD media to burn it.
- Also, use USB flash drive larger than 2GB.
Mel (2019-08-26 (Mon) 17:06:02)
otsukaresamadesu
Melと申します。
i try latest 6.5 image (amd64) on Lenovo T460s ... this Lenovo is configured for EFI boot. USB containing 6.5 #FuguIta image can not boot.
in site i see test image for 6.4 ... but mirror do not have the test images.
kaw (2019-05-12 (Sun) 08:49:09)
#FuguIta's download mirror sites changed and added
Use the nearest mirror from your location.
kaw (2019-05-10 (Fri) 14:26:27)
tools to create a live system based on OpenBSD 6.5
were uploaded at tools directory.
Refer FuguIta/FAQ/SelfBuild for creating.
aleksa (2019-03-25 (Mon) 19:41:13)
Hello, kaw!
How can i update FuguIta?
For example, if i have the patched-014 6.4-i386-version with a bunch of installed apps running on a usb drive in mode 3,
is it possible to just substitute that big FFSIMG on sd0a for the one taken from the patched-015 FuguIta-6.4-i386-201903231.img?
How can i update FuguIta?
Yes, of course, you can do it.
(You know, LiveCD cannot be re-written, so in that case, prepare another CD media to burn newly released FuguIta)
There are some ways to update LiveUSB version of FuguIta.
I'll introduce two methods, for example.
- method 1: replace the kernels and the filesystem image
This is described in FuguIta Guide (Google Translate is your friend).
- 1: Boot NEW USB with mode 0. (Boot time configurations may be the minimal)
- 2: mount OLD USB (assume it's sd1)
# mount /dev/sd1a /mnt- 3: copy NEW kernels and a filesystem image to old USB
# cp /sysmedia/bsd-fi /mnt # cp /sysmedia/bsd-fi /mnt # cp /sysmedia/fuguita-6.4-i386.ffsimg /mnt- 4: umount sd1, then halt
- 5: reboot NEW USB and confirm that's updated.
# uname -a # OS version # sysctl kern.version # kernel version # cat /usr/fuguita/version # release of fuguita- method 2: migrate installed apps, config files and your data to NEW USB
- 1: Boot OLD USB with mode 3 you've been used until now
- 2: Invoke usbfadm, then attach NEW USB and change sync target to it
# usbfadm Welcome to usbfadm. USB flash drive administration tool for FuguIta Version/Arch: 6.4/arm64 (FuguIta-6.4-arm64-201903231) Boot mode: usbflash Data stored in: /dev/sd0d Data Saved as: aleksa_apps Type ? for help. sd0d : aleksa_apps ->target Searching USB flash drives Please make sure the device inserted. Then press ENTER -> sd0a +sd0d sd0i sd1a +sd1d sd1i target device->sd1d- 3: Do 'sync' command to NEW USB
sd1d : aleksa_apps ->sync Sync current tmpfs as ``aleksa_apps'' , OK? [y/N] -> y sending incremental file list ....snip.... sent 14,595,555 bytes received 2,592 bytes 572,476.35 bytes/sec total size is 29,789,283 speedup is 2.04 sd1d : aleksa_apps ->bye Bye bye... # halt- 4: Reboot with NEW USB, and check it's OK.
These procedures are valid when OLD and NEW USB are both based on same OpenBSD version. If it isn't (e.g. 6.4 to 6.5), you need to pkg_add manually on a new system, and need to migrate app's config files and your data files to NEW USB by hand.
Finally, I think method 2 is little bit safer. -- kaw 2019-03-26 (Tue) 01:10:40
kaw (2019-03-13 (Wed) 17:42:48)
Unlike most Unix-like OSes, #FuguIta does not mount them at boot time, even if the user writes partition entries in /etc/fstab.
That's because FuguIta scans the all partitions of attached disks to by the script /boottmp/rc. According to that result, it determines apropriate partitions (and vnode devices) to be mounted.
FuguIta generates /etc/fstab after the partition is mounted. Therefore, even if the user adds partition entries to fstab, they will be overwritten at next boot time.
To solve this problem, FuguIta-6.4-201903131 introduced the /usr/fuguita/etc/fstab.tail file.
Describe the partition entries to be mounted in fstab.tail with the same format as /etc/fstab, save with usbfadm.
Those partitions will be mounted at next boot of mode 3.
Note that this is functional only when boot mode is 3.
Vasile Guta-Ciucr (2019-02-28 (Thu) 23:37:23)
Hi,
Can this live system be used to install to HDD, or is designed to work only live?
Former articles are at FuguIta/BBS/8.
Return to Top