To make sure that everything starts up normally even when regular things are done, which should not influence the procedure, I left my ghostBSD installation alone for about a day

I inserted the external HDD in the tray, at the exact location where I had installed the Operating System, rebooted that MiniPC and fired up ghostBSD. A couple of nice things occur when you install ghostBSD instead of going flat with just freeBSD.

Configuration parameters for my HDMI IPS LED panel Zero was always added flawlessly since that is the display which I look at at boot

My secondary display which is connected to a mini DisplayPort (Zero) and then goes from mini DisplayPort to HDMI with an Active cable with circuitry in it, at the HDMI end, is automatically detected in the freeBSD configuration provided by the ghostBSD team.

That is a tremendously good feature which pleasantly surprised me.

Another BSD user told me here, that in the regular freeBSD installation you have to go and figure that out yourself, which is fine but not something I intended to do at this point.

Here are some images I just shot of the login screens with both IPS LED panels enabled

.🖋️ #bash #freeBSD #boxyBSD #sh #zsh #ksh #csh #netBSD #openBSD #POSIX #AskFediverse #WTF

@izder456

I am an individual who often does things in many fields, especially computing, in a weird and unexpected way. That's why I'm one of the efficient bèta testers for many different software programs which started in the days of the Waffle BBS's somewhere in the 90s of the last Century and still goes on to these days.
Going to the absolute beginning I even started to bèta test software on the Casio FX-700p; then I moved to the Commodore C64, the C128 where I debugged CPM software, then I moved on to the 286 PS2, the machine was loaded with the 287 Mathematics Co-processor, essential for running CAD software.

The reason for my specific booting of the SSD, the starter SSD, on the USB tray, a dual slot device, is because I currently have not made any specific space free for the operating system.

I miss going to my beautiful boxyBSD system which resides on the boxyBSD Network.

The reasons for that are somewhere in another thread, but it comes down to the fact that my brain dead ISP doesn't give us any IPv6 addresses from the get-go, while we pay them through the Nose for a puny 10MBit Connection on a obsolete xDSL router.

So I just went to one of my machines, a AMD MíniPC with 32GB RAM, didn't find any space where the operating system wanted to install on my resident m.2 SSD (no space due to Sound Engineering Audio projects) and my resident SATA SSD, for identical reasons.

In the end space was made on a SATA SSD which floats on my different SATA trays which are dual port.

I shrunk a partition and made 8GB free, which the installer divided in 7.1GB and 407+MB for Swap.

I immediately have to say that the installer teaches you what doesn't work and give you hints on where you can go and look for the reasons why.

I have an MBR SATA HDD, where I wanted to install the operating system.
The installer immediately warned me that I would get a non-bootable situation and it was right it didn't tell why but that's not important.

The SATA SSD was already converted from MBR to GPT, where of course it lost all data but that was unimportant, since it was scratch data. gPartEd warned me about the data loss

The semi-automatic installation liked the fact that the SSD was GPT, partitioned and happily did it's magic creating the file systems.

When after the installation, I powered down the tray and inserted a HDD in the open slot, not moving the SATA SSD, the FreeBSD boot environment told me that it could not find the boot partition.

For me that was a WTF moment since the SSD wasn't moved.

🖋️ #bash #freeBSD #boxyBSD #sh #zsh #ksh #csh #netBSD #openBSD #POSIX #AskFediverse

Due to my brain dead ISP which does not support IPv6 for clients in 2K25(!) I cant access my boxyBSD box.

boxyBSD is thus so far away from me 🙁

I have a client connection with fixed IPv4 IP somewhere, but it collapses when I use a free available IPv4 to IPv6 tunnel service.

Instead of sitting and twiddling my fingers on my Bass guitar(s) generating random() notes, I decided to get an image of the latest freeBSD and play with it locally, until I can get my ISP to provide all of us with a (set) of free IPv6 addresses because we pay them for a full service here in my country

>> log

$ wget -c download.freebsd.org/releases/…
--2025-03-23 13:32:46-- download.freebsd.org/releases/…
Resolving download.freebsd.org (download.freebsd.org)... 200.160.6.227, 2001:12ff:0:6224::15:0
Connecting to download.freebsd.org (download.freebsd.org)|200.160.6.227|:443... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 4826406912 (4.5G), 4255655894 (4.0G) remaining [application/octet-stream]
Saving to: ‘FreeBSD-14.2-RELEASE-amd64-dvd1.iso’

-14.2-RELEASE-amd64-dvd1 12%[++++ ] 559.57M 1.01MB/s eta 75m

<< ^Z

Yes they give a puny 1MB speed, you read that correctly

🖋️ #bash #freeBSD #boxyBSD #sh #zsh #ksh #csh #netBSD #openBSD #POSIX

Giving credit to the programmers of GPARTED(8)

gparted works its magic, by entering correct parameters to a suite of partition control & editing commands, which are sh envoked, so you can easily manipulate your partitions on all your SSDs HDDs from the comfort of your UI

When you want to batch manipulate partitions, you can study the log output and make sh scripts yourself, controlling partitions anywhere.
You also have the convenience of running gparted from sh so it still works its magic for you, without the UI!

I usually run cfdisk gdisk fdisk when I partition a fresh mechanical or SSD, later on I invoke gparted when I want to resize or move them

it also runs important commands at the end so that the kernel gets to know your new partition layout, which makes rebooting your machine to use them unneeded

I shrunk and resized a partition where I installed a program, which needed 75GB (*1024!) as installation space but only uses 56GB in the end. I left 12GB of breathing room on the partition after the shrink and of course grew the partition before with the same size, minus the alignment snip of 1MB

log:
myserver kernel: JFS: nTxBlock = 8192, nTxLock = 65536
myserver kernel: SGI XFS with ACLs, security attributes, realtime, scrub, repair, quota, debug enabled
myserver kernel: sdb: sdb1 sdb2 sdb3 sdb4
myserver kernel: sdb: sdb1 sdb2 sdb3 sdb4
^Z

@altbot

gparted.org

#gparted #partitions #bash #csh #ksh #sh #parameters #UEFI #Linux #options #programming #POSIX