Solved I finally have created an experimental BSD Project called CultBSD it uses uzip compressed with zstd level 19 compression its pretty fast.

christhegeek · Sep 5, 2021

oops

grahamperrin said:
christhegeek

Seeing xf86-video-amdgpu mentioned at <https://sourceforge.net/projects/cult-bsd/files/INSTALL xf86-video-amdgpu I forgot to install it.txt>

Is xf86-video-ati present? x11-drivers/xf86-video-ati

grahamperrin · Sep 5, 2021

With the USB flash drive:

grahamperrin said:
… UFO stuff appeared then disappeared (blackout)

I touched nothing

at 17:09 a display on DisplayPort put itself to sleep …

With a (much faster) hard disk drive on USB: just a brief blackout (expected), then the desktop environment appeared ☑

Code:

cultbsd@cultbsdpc ~> uname -aKU
FreeBSD cultbsdpc 13.0-RELEASE-p4 FreeBSD 13.0-RELEASE-p4 #0: Tue Aug 24 07:33:27 UTC 2021     root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64 1300139 1300139
cultbsd@cultbsdpc ~> pkg info -x xf86-video
pkg: No packages installed
cultbsd@cultbsdpc ~ [1]> kldstat
Id Refs Address                Size Name
 1  132 0xffffffff80200000  1f11f28 kernel
 2    1 0xffffffff82112000     a598 geom_uzip.ko
 3    1 0xffffffff8211d000     bdf8 cuse.ko
 4    1 0xffffffff82610000     639c linprocfs.ko
 5    3 0xffffffff82617000     db70 linux_common.ko
 6    1 0xffffffff82625000     3284 linsysfs.ko
 7    1 0xffffffff82629000    35b00 vboxguest.ko
11    1 0xffffffff8279f000     4b60 ng_ubt.ko
12    6 0xffffffff827a4000     aac8 netgraph.ko
13    2 0xffffffff827af000     a238 ng_hci.ko
14    3 0xffffffff827ba000     25a8 ng_bluetooth.ko
15    1 0xffffffff827bd000     3378 acpi_wmi.ko
16    1 0xffffffff827c1000     2340 uhid.ko
17    1 0xffffffff827c4000     4350 ums.ko
18    1 0xffffffff827c9000     3380 usbhid.ko
19    1 0xffffffff827cd000     31f8 hidbus.ko
20    1 0xffffffff827d1000     e538 snd_uaudio.ko
21    1 0xffffffff827e0000     3460 umodem.ko
22    1 0xffffffff827e4000     4d90 ucom.ko
23    1 0xffffffff827e9000     4600 if_cdce.ko
24    1 0xffffffff827ee000     3178 uether.ko
25    1 0xffffffff847a2000     e250 ng_l2cap.ko
26    1 0xffffffff847b1000    1ce48 ng_btsocket.ko
27    1 0xffffffff827f2000     3980 ng_socket.ko
28    1 0xffffffff847ce000    30ac8 linux64.ko
29    1 0xffffffff827f6000     2260 pty.ko
30    1 0xffffffff827f9000     3530 fdescfs.ko
31    1 0xffffffff827fd000   150c70 radeonkms.ko
32    2 0xffffffff8265f000    7f548 drm.ko
33    3 0xffffffff826df000     cbc8 linuxkpi_gplv2.ko
34    1 0xffffffff826ec000     2328 lindebugfs.ko
35    1 0xffffffff826ef000     e778 ttm.ko
36    1 0xffffffff826fe000     3258 radeon_TURKS_pfp_bin.ko
37    1 0xffffffff82702000     3658 radeon_TURKS_me_bin.ko
38    1 0xffffffff82706000     2cd8 radeon_BTC_rlc_bin.ko
39    1 0xffffffff82709000     7ef8 radeon_TURKS_mc_bin.ko
40    1 0xffffffff82711000     8138 radeon_TURKS_smc_bin.ko
41    1 0xffffffff8271a000    341f0 radeon_SUMO_uvd_bin.ko
42    1 0xffffffff8274f000     2a08 mac_ntpd.ko
cultbsd@cultbsdpc ~>

From <https://github.com/freebsd/drm-kmod/issues/108#issue-985940817>:

I reckon that there's somehow an issue with the order in which things are loaded/started.

– if it's order and timing, then symptoms (i.e. endless blackout and no response to human input) might be more likely to occur if 'stuff' can't be achieved in good time i.e. with a USB flash drive.

xf86-video-ati may be a grey area.

christhegeek · Sep 5, 2021

I have installed ati now in this new edition .
It will have lxqt with herbstluftwm
Can you test it and see if it works ? when it will be uploaded ?
The only problem i have is with sddm i think my old mechanical hard disk has serious problems now and i will throw it away , i used it to store the files my bad.
I started using lzma for the compressed root. I believe its a most secure way

I will plan to make a brand new plasma release using my newer ssd disk, also i will change the theme completely.

christhegeek · Sep 7, 2021

I had a problem with the hard disk i used to make and store these releases
New upload today , i hope without any problems anymore !

The first beta will be uploaded today after i do some testing .
I'm sure it will gonna work.
Also i have an idea to ask user what driver he want to go with while booting .
Also i don't know what driver is required for really old nvidia gpus that won't work with nvidia-driver

grahamperrin · Sep 11, 2021

Code:

% sha256 cultbsd.img
SHA256 (cultbsd.img) = 403a612ac36da758a84ebc3a51d4b9c4b694fa74179acf3eac049ba4da0b70e3
%

christhegeek does the checksum match what you have for CultBSD Zen-Edition Beta1 a.k.a. Zen-Mate Edition?

Before and after writing the image (to a drive that was used for an earlier version of CultBSD):

Code:

% lsblk da3
DEVICE         MAJ:MIN SIZE TYPE                                          LABEL MOUNT
da3              2:68   14G GPT                                               - -
  da3p1          2:69  512K freebsd-boot                             gpt/mdboot -
  da3p2          2:70   40M efi                                               - -
  da3p3          2:71  9.0G freebsd-ufs                              gpt/mdroot -
  da3p4          2:72  900M freebsd-ufs                             gpt/thehome -
  da3p5          2:73  125M freebsd-ufs                              gpt/theetc -
  da3p6          2:74  400M freebsd-ufs                              gpt/thetmp -
  <FREE>         -:-    18M -                                                 - -
% time sudo dd if=cultbsd.img of=/dev/da3 bs=5M && sync
grahamperrin's password:
1433+1 records in
1433+1 records out
7516192768 bytes transferred in 867.148725 secs (8667709 bytes/sec)
0.015u 6.980s 14:36.47 0.7%     21+166k 30668+7171io 21pf+0w
% lsblk da3
DEVICE         MAJ:MIN SIZE TYPE                                          LABEL MOUNT
da3              2:68   14G GPT                                               - -
  da3p1          2:55  512K freebsd-boot                             gpt/mdboot -
  da3p2          2:56   40M efi                                               - -
  da3p3          2:57  5.0G freebsd-ufs                              gpt/mdroot -
  da3p4          2:80   66M freebsd-ufs                              gpt/theetc -
  da3p5          2:87  266M freebsd-ufs                              gpt/thetmp -
  da3p6          2:88  1.6G freebsd-ufs                             gpt/thehome -
%

Issues:

omission of a swap partition, when installing, is problematic – there's no free space in which to create one
the installer should invite the user to set a keyboard layout before inviting the user to set a password
the live system on a USB flash drive is not sufficiently responsive for things such as web browsing.

If /etc/fstab includes this line:

/dev/gpt/FreeBSD%20swap none swap sw,late 0 0

– then it should be easier for the OS to use something other than the boot disk for FreeBSD swap.

Lesser issues:

the installer for the first beta describes itself as for the fourth pre-alpha
the installer uses umount in a way that causes unknown file system responses
need to think about alignment of partitions, see for example <https://forums.FreeBSD.org/threads/81891/post-529462>
SLiM is not suitable for multiple displays (upstream development ceased seven years ago) – better managers exist
gnome-keyring-daemon seems to be a problem for the live system, at least when attempting to shut down.

Installed to VirtualBox, with packages upgraded and subsequent installation of guest additions: <https://bsd-hardware.info/?probe=3884638db2>

grahamperrin · Sep 11, 2021

the live system on a USB flash drive is not sufficiently responsive for things such as web browsing.

This was also noticeable before the first beta.

With the user doing nothing: long after the desktop environment appears, there's frequent thrashing of the drive.

grahamperrin · Sep 11, 2021

Installed to a VirtualBox guest, booted with EFI enabled, after allowing things to idle for a while there was a complete blackout (no response to input, no visible pointer, no response to ACPI shutdown).

The tail of the VirtualBox log (lines 1,324–1,342):

Code:

…
00:01:02.869591 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 1024x768 if necessary
00:42:54.542125 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0xca (30013812 usec ago) CmdIf1=0x00 (-1 usec ago)
00:43:29.331884 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:43:29.332011 PIIX3 ATA: execution time for ATA command 0xca was 64 seconds
00:43:29.332991 VMMDev: GuestHeartBeat: Guest is alive (gone 36 124 967 895 ns)
00:43:29.336482 PIIX3 ATA: execution time for ATA command 0xc8 was 34 seconds
00:43:29.346015 PIIX3 ATA: Ctl#0: finished processing RESET
00:43:30.669837 VMMDev: Guest Additions capability report: (0x5 -> 0x1) seamless: yes, hostWindowMapping: no, graphics: no
00:43:30.670056 VMMDev: Guest Additions capability report: (0x1 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:43:30.670089 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:43:30.670105 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:43:30.670168 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners
00:43:30.670204 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
00:43:30.670260 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:43:30.670272 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:43:30.671204 Shared Clipboard: X11 event thread exiting
00:49:36.820612 VMMDev: SetVideoModeHint: Got a video mode hint (1280x720x32)@(0x0),(1;0) at 0
00:49:59.122460 GUI: UIMediumEnumerator: Medium-enumeration started...
00:49:59.294101 GUI: UIMediumEnumerator: Medium-enumeration finished!

I performed a reset, expecting the UFS file system to be repaired …

grahamperrin · Sep 11, 2021

UFS: file system repairs

grahamperrin said:
I performed a reset, expecting the UFS file system to be repaired …

I started once in multi-user mode, then in single user mode to tell whether automated repairs before multi-user mode were effective.

~~The file system could not be repaired:~~

** dev/ada0p3 (NO WRITE)

Restarted again in single user mode, again I got NO WRITE:

Exited to multi-user mode, stopped the display manager, used script(1) to gain an overview:

Code:

Script started on Sat Sep 11 08:36:01 2021
Welcome to fish, the friendly interactive shell
Type [32mhelp[m for instructions on how to use fish
[?2004h]0;fish /root[30m[m
[32mroot[m@[mcultbsdpc[m [31m~[m[m# [K
[18Cc
[19C[38;5;196mc
[19C[30m[m[38;5;240msh
[19C[30m[m[38;5;196ms[38;5;240mh
[20C[30m[m[38;5;196mh
[21C[30m[m[38;5;26mcsh
[21C[30m[m
[21C
[30m[m[?2004l]0;csh /root[30m[m
root@cultbsdpc:~ # gpart show

=>       40  268435376  ada0  GPT  (128G)
         40       1024     1  freebsd-boot  (512K)
       1064      81920     2  efi  (40M)
      82984  268352432     3  freebsd-ufs  (128G)

=>      34  33554365  ada1  GPT  (16G)
        34      2014        - free -  (1.0M)
      2048  33552351     1  freebsd-swap  (16G)

root@cultbsdpc:~ # fsck_ffs -fn /dev/ada0p3

** /dev/ada0p3 (NO WRITE)
** Last Mounted on /
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=10022120 (8 should be 0)
CORRECT? no

** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
LINK COUNT FILE I=1843201  OWNER=root MODE=0
SIZE=0 MTIME=Sep 11 08:36 2021  COUNT 0 SHOULD BE -1
ADJUST? no

UNREF FILE  I=1843202  OWNER=root MODE=100644
SIZE=834 MTIME=Sep 11 08:36 2021

RECONNECT? no


CLEAR? no

UNREF FILE I=7692300  OWNER=test MODE=100600
SIZE=2 MTIME=Sep 11 07:10 2021

CLEAR? no

UNREF FILE I=10021524  OWNER=test MODE=100644
SIZE=13168 MTIME=Sep 11 06:41 2021

CLEAR? no

UNREF FILE I=10022034  OWNER=test MODE=100600
SIZE=4120 MTIME=Sep 11 07:17 2021

CLEAR? no

UNREF FILE I=10022035  OWNER=test MODE=100644
SIZE=32768 MTIME=Sep 11 07:11 2021

CLEAR? no

UNREF FILE  I=10022914  OWNER=test MODE=100600
SIZE=42022 MTIME=Sep 11 07:16 2021

RECONNECT? no


CLEAR? no

UNREF FILE  I=10025126  OWNER=test MODE=100644
SIZE=0 MTIME=Sep 11 07:51 2021

RECONNECT? no


CLEAR? no

** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no

SUMMARY INFORMATION BAD
SALVAGE? no

BLK(S) MISSING IN BIT MAPS
SALVAGE? no

335878 files, 2711731 used, 29777204 free (18268 frags, 3719867 blocks, 0.1% fragmentation)
root@cultbsdpc:~ # exit

exit
[1m[30m⏎[m                                                                               
⏎
[K[?2004h]0;fish /root[30m[m[32mroot[m@[mcultbsdpc[m [31m~[m[m# [K
[18Ce
[19C[38;5;240mxit
[19C[30m[m[38;5;196me[38;5;240mxit
[19C[30m[m[38;5;196mx[38;5;240mit
[20C[30m[m[38;5;26mex[38;5;240mit
[20C[30m[m[38;5;26mi[38;5;240mt
[21C[30m[m[38;5;196mexi[38;5;240mt
[21C[30m[m[38;5;196mt
[22C[30m[m[38;5;26mexit
[22C[30m[m
[22C
[30m[m[?2004l]0;exit /root[30m[m
[30m[m[?2004l
Script done on Sat Sep 11 08:37:11 2021

NB fish(1) creates a horrible mess with script(1).

Solved - Occasionally ugly results from script(1)

script(1) , for example. Much of it is a mess, and unrelated to my keystrokes. Is this type of mess maybe more likely to occur with fish(1)?

forums.freebsd.org

Postscript

Eventually I realised my mistake – attempting to check the partition when I should have targeted the mount point.

Still, it seems strange that repairs were not automated …

grahamperrin · Sep 11, 2021

em(4) and saved state

Before saving the guest:

After starting from the saved state, there's no network connection, it's necessary to manually bring up the interface:

No such problem with a different guest that also runs FreeBSD 13.0-RELEASE-p4.

grahamperrin · Sep 11, 2021

UFS DIRTY and not repaired

grahamperrin said:
repairs were not automated …

Here's part of your problem:

soft update journaling disabled

– please, was this intentionally disabled?

Code:

test@cultbsdpc ~> date ; uname -a
Sat Sep 11 10:35:52 BST 2021
FreeBSD cultbsdpc 13.0-RELEASE-p4 FreeBSD 13.0-RELEASE-p4 #0: Tue Aug 24 07:33:27 UTC 2021     root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
test@cultbsdpc ~> freebsd-version -kru
13.0-RELEASE-p4
13.0-RELEASE-p4
13.0-RELEASE-p4
test@cultbsdpc ~> tunefs -p /
tunefs: POSIX.1e ACLs: (-a)                                disabled
tunefs: NFSv4 ACLs: (-N)                                   disabled
tunefs: MAC multilabel: (-l)                               disabled
tunefs: soft updates: (-n)                                 enabled
tunefs: soft update journaling: (-j)                       disabled
tunefs: gjournal: (-J)                                     disabled
tunefs: trim: (-t)                                         disabled
tunefs: maximum blocks per file in a cylinder group: (-e)  4096
tunefs: average file size: (-f)                            16384
tunefs: average number of files in a directory: (-s)       64
tunefs: minimum percentage of free space: (-m)             8%
tunefs: space to hold for metadata blocks: (-k)            6400
tunefs: optimization preference: (-o)                      time
tunefs: volume label: (-L)                                 
test@cultbsdpc ~>

grahamperrin · Sep 11, 2021

fstab(5) and fsck_ffs(8)

The first line of /etc/fstab seems to be incomplete.

Prior to edition:

Code:

/dev/gpt/mdroot1631317232 / ufs rw
proc /proc procfs rw 0 0

After adding a header, white space for clarity, and a line for swap:

Code:

# Device                   Mountpoint  FStype  Options  Dump  Pass#
/dev/gpt/mdroot1631317232  /           ufs     rw
proc                       /proc       procfs  rw       0     0
/dev/gpt/FreeBSD%20swap    none        swap    sw,late  0     0

After adding fifth and sixth fields for the root file system:

Code:

# Device                   Mountpoint  FStype  Options  Dump  Pass#
/dev/gpt/mdroot1631317232  /           ufs     rw       1     1
proc                       /proc       procfs  rw       0     0
/dev/gpt/FreeBSD%20swap    none        swap    sw,late  0     0

Still, it seems that the file system is not automatically checked when appropriate. Attempting to start normally:

eternal_noob · Sep 11, 2021

This is why people are unwilling to run home baked "projects" of an OS. You never now what's repaired to death.
A bunch of installer scripts - yes. Obscure ISOs - no.

grahamperrin · Sep 11, 2021

eternal_noob said:
people are unwilling to run

It's a beta, experimental.

eternal_noob · Sep 11, 2021

I don't necessarily mean this project.

christhegeek · Sep 11, 2021

1) It will use a swap file or a swap partition from now and on , i made this mainly for myself and i have too much ram to need swap
2) I have enabled soft updates when i have created the partition
3) I haven't tried on virtualbox
4) I have tried and installed it in many machines also i have other people that have it installed (the one of them is very popular in linux community it has right now) i guess he would feel bad i hadn't included the swap partition or file. The latest releases from today will have a swap file or have a swap partition .
The number of machines that is working that i know about are about 9 different pcs and some of them has really old specs
5) There is a problem with the startup fsck script i forgot to copy the modified version indeed
6) This is probably from a very very old release that would have problems because i had technical problems with the old hdd
The sequence is not the same
lsblk da3
DEVICE MAJ:MIN SIZE TYPE LABEL MOUNT
da3 2:68 14G GPT - -
da3p1 2:69 512K freebsd-boot gpt/mdboot -
da3p2 2:70 40M efi - -
da3p3 2:71 9.0G freebsd-ufs gpt/mdroot -
da3p4 2:72 900M freebsd-ufs gpt/thehome -
da3p5 2:73 125M freebsd-ufs gpt/theetc -
da3p6 2:74 400M freebsd-ufs gpt/thetmp -
<FREE> -:- 18M - - -
7) Download the latest releases to test it.

christhegeek · Sep 11, 2021

Yes some of these umounts are not needed at all the mounted drives are already unmounted previeously need to be removed just
i have inserted these commands when i was debugging it.
Also when i delete and clean the target disk i will improve the script to notice how many partition the target disk has and delete them accordingly
right now it tries to delete 6 partitions in that drive and if the disk has only 3 then it will have error messages.

I will create a cool graphical installer in Qt .

grahamperrin said:
Code:

% sha256 cultbsd.img SHA256 (cultbsd.img) = 403a612ac36da758a84ebc3a51d4b9c4b694fa74179acf3eac049ba4da0b70e3 %

christhegeek does the checksum match what you have for CultBSD Zen-Edition Beta1 a.k.a. Zen-Mate Edition?

Before and after writing the image (to a drive that was used for an earlier version of CultBSD):

Code:

% lsblk da3 DEVICE MAJ:MIN SIZE TYPE LABEL MOUNT da3 2:68 14G GPT - - da3p1 2:69 512K freebsd-boot gpt/mdboot - da3p2 2:70 40M efi - - da3p3 2:71 9.0G freebsd-ufs gpt/mdroot - da3p4 2:72 900M freebsd-ufs gpt/thehome - da3p5 2:73 125M freebsd-ufs gpt/theetc - da3p6 2:74 400M freebsd-ufs gpt/thetmp - <FREE> -:- 18M - - - % time sudo dd if=cultbsd.img of=/dev/da3 bs=5M && sync grahamperrin's password: 1433+1 records in 1433+1 records out 7516192768 bytes transferred in 867.148725 secs (8667709 bytes/sec) 0.015u 6.980s 14:36.47 0.7% 21+166k 30668+7171io 21pf+0w % lsblk da3 DEVICE MAJ:MIN SIZE TYPE LABEL MOUNT da3 2:68 14G GPT - - da3p1 2:55 512K freebsd-boot gpt/mdboot - da3p2 2:56 40M efi - - da3p3 2:57 5.0G freebsd-ufs gpt/mdroot - da3p4 2:80 66M freebsd-ufs gpt/theetc - da3p5 2:87 266M freebsd-ufs gpt/thetmp - da3p6 2:88 1.6G freebsd-ufs gpt/thehome - %

Issues:

omission of a swap partition, when installing, is problematic – there's no free space in which to create one

the installer should invite the user to set a keyboard layout before inviting the user to set a password

the live system on a USB flash drive is not sufficiently responsive for things such as web browsing.

If /etc/fstab includes this line:

/dev/gpt/FreeBSD%20swap none swap sw,late 0 0

– then it should be easier for the OS to use something other than the boot disk for FreeBSD swap.

Lesser issues:

the installer for the first beta describes itself as for the fourth pre-alpha

the installer uses umount in a way that causes unknown file system responses

need to think about alignment of partitions, see for example <https://forums.FreeBSD.org/threads/81891/post-529462>

SLiM is not suitable for multiple displays (upstream development ceased seven years ago) – better managers exist

gnome-keyring-daemon seems to be a problem for the live system, at least when attempting to shut down.

View attachment 11284 View attachment 11285 View attachment 11286 View attachment 11287 View attachment 11288

Installed to VirtualBox, with packages upgraded and subsequent installation of guest additions: <https://bsd-hardware.info/?probe=3884638db2>

I

christhegeek · Sep 11, 2021

I have tested it to my machine and other 9 pcs (one of them is popular in the linux community but without swap and an old pc he will curse me he had installed last time he wrote :-( )
But still its an experiment.
There are more than one way to make a live image maybe this way is less professional , i made it that way to have less time loading and to be able to save to home folder files and change the configuration files /etc if i want to use it somewhere else , i wanted it to be able to use it from another computer. I may turn to ghostbsd style but if i create a project with many applications and heavier desktop like plasma the user should have enough ram to load it to memory disk or else it won't run at all

grahamperrin · Sep 11, 2021

christhegeek said:
… 7) Download the latest releases to test it.

Checksums

Code:

% rm cultbsd.img
% sha256 cultbsd-zen-Tiles-herbstluftwm.img.lzma
SHA256 (cultbsd-zen-Tiles-herbstluftwm.img.lzma) = 87c23189b3d2ec0a95fa42715c467a8ac6a549a046fc21c8ad93da0c0f0f6633
% lzma --decompress --keep cultbsd-zen-Tiles-herbstluftwm.img.lzma
% rm CULTBSD-FIRST-BETA-UPLOADED-FIXED-README.txt
% sha256 cultbsd-zen-Tiles-herbstluftwm.img
SHA256 (cultbsd-zen-Tiles-herbstluftwm.img) = 1daad8cb919f8309e7048f090b14b75750417ff97f2a72be0261aab7e5060921
%

First impressions

Alt-F4 does not close windows, and so on. Intensely weird, when this type of window manager is a novelty.

Installing to a virtual disk:

– failed, but not an issue with CultBSD:

Image (live system) written to a physical disk, I'll test later:

Code:

root@mowa219-gjp4-8570p-freebsd:/Volumes/t500/VirtualBox/BSD/others/CultBSD # dd if=cultbsd-zen-Tiles-herbstluftwm.img of=/dev/da0 bs=5M && sync
1433+1 records in
1433+1 records out
7516192768 bytes transferred in 798.484267 secs (9413076 bytes/sec)
root@mowa219-gjp4-8570p-freebsd:/Volumes/t500/VirtualBox/BSD/others/CultBSD # gpart recover da0
da0 recovered
root@mowa219-gjp4-8570p-freebsd:/Volumes/t500/VirtualBox/BSD/others/CultBSD # ls -hl cultbsd-zen-Tiles-herbstluftwm*
-rw-r--r--  1 grahamperrin  grahamperrin   7.0G Sep 11 13:46 cultbsd-zen-Tiles-herbstluftwm.img
-rw-r--r--  1 grahamperrin  grahamperrin   3.4G Sep 11 13:46 cultbsd-zen-Tiles-herbstluftwm.img.lzma
-rw-------  1 grahamperrin  grahamperrin   5.7G Sep 11 14:35 cultbsd-zen-Tiles-herbstluftwm.vdi
root@mowa219-gjp4-8570p-freebsd:/Volumes/t500/VirtualBox/BSD/others/CultBSD # cd
root@mowa219-gjp4-8570p-freebsd:~ #

grahamperrin · Sep 11, 2021

grahamperrin said:
Image (live system) written to a physical disk, I'll test later:

This version is very poorly suited to multiple displays, non-intuitive:

firefox seemed to run, as a process without a window, long after (Control-Q) quit.

Similarly, welcome seemed to run, without a window, longer than it should; there was a related dialogue when attempting to log out.

Log out seemed to fail. I waited until long after disappearance of the panel at the top of the screen, then switched to ttyv1 and killed SLiM.

christhegeek · Sep 11, 2021

Yes it will log out using a shortcut because logout terminates the mate-session not herbstluftwm

grahamperrin said:
This version is very poorly suited to multiple displays, non-intuitive:

View attachment 11314 View attachment 11315

firefox seemed to run, as a process without a window, long after (Control-Q) quit.

Similarly, welcome seemed to run, without a window, longer than it should; there was a related dialogue when attempting to log out.

Log out seemed to fail. I waited until long after disappearance of the panel at the top of the screen, then switched to ttyv1 and killed SLiM.

grahamperrin · Sep 11, 2021

christhegeek said:
herbstluftwm

Is there a GUI to activate an alternative window manager? If not, I'll install SDDM and KDE Plasma.

christhegeek said:
1) It will use a swap file or a swap partition from now and on ,

There's still no swap:

christhegeek · Sep 11, 2021

Yes i have created the swap file but followed the old freebsd guide and it doesn't work now i should add a script to load the file doesn't loads anymore from rc.conf with swap_file parameter.
Nevermind i fixed these problems and will reupload it today !
Always read the sourceforge project's files page for release notes etc !

CultBSD , A new FreeBSD based Project - Browse Files at SourceForge.net

CultBSD , A new FreeBSD based Project ("distribution") cultbsd

sourceforge.net

problems fixed
1) The installer doesn't switch Slim's autologin off . fixed
2) Forgot to remove resolv.conf again , fixed
3) The swapfile doesn't get activated , fixed the installer now creates a swap partition and make the corresponding fstab configuration
4) Trying to log-out from menu just kills mate-session and doesn't stop herbstluftwm
-- Added a shortcut to logout super+shift+x (if i remember correctly i hope i've updated that for new users created also i believe i did)
5) Added a welcome full-screen video it opens only once don't worry. Might be a little annoying.

grahamperrin · Sep 11, 2021

Thanks,

christhegeek said:
3) The swapfile doesn't get activated , fixed the installer now creates a swap partition and make the corresponding fstab configuration

A partition is probably best.

Alternatively, FYI <https://docs.freebsd.org/en/books/handbook/config/#create-swapfile> so, for example (with the relevant line added to /etc/fstab):

Code:

root@cultbsdpc:~ # swapinfo -h
Device              Size     Used    Avail Capacity
root@cultbsdpc:~ # swapon -aL
swapon: adding /dev/md0 as swap device
root@cultbsdpc:~ # swapinfo -h
Device              Size     Used    Avail Capacity
/dev/md0            6.0G       0B     6.0G     0%
root@cultbsdpc:~ # grep swap /etc/fstab
md  none  swap  sw,file=/usr/swap0,late  0  0
root@cultbsdpc:~ # swapoff -a
swapoff: removing /dev/md0 as swap device
root@cultbsdpc:~ # swapinfo -h
Device              Size     Used    Avail Capacity
root@cultbsdpc:~ #

grahamperrin · Sep 12, 2021

From <https://sourceforge.net/projects/cult-bsd/files/>:

… SLIM DISPLAY MANAGER WILL NOT AUTOLOGIN …

With an alternative display manager, it's remarkable that the username field shows something other than the username.

grahamperrin · Sep 12, 2021

cultbsd-zen-tiles-v2.img

The welcome application window obscures what might be clickable items in the background, can not be moved, hidden or closed.

The application fails to quit, prevents log out: