i've put a zfs mirror on a couple of external usb drives. i wanna start over so what's the right way to clear the drives? do i even need to do anything (like gpart destroy -F ...) or can i just gpart create... zpool create...?

demido: as long as the data is backed up, unmount all the drives, in the zpool.. execute zpool destroy <poolname>, then rebuild

ok ty

ok got external usb nvme drive setup with gpt partition and zfs! i ran gpart create -s GPT da1, then gpart add -l foo -t freebsd-zfs -a 1M da1, then sudo zpool create extrn gpt/foo, then chown -R demido:operator /extrn, then copy files into /extrn, then zpool export extrn. do i also need to umount da1 for clean unplugging, or is zfs export enough?

anyone reply after i got d/c?

does cut an paste work from any of the vnc server/clients to the client host? Ie I have a vncviewer on a Mac can cut and paste be made to work between the vnc session and the Mac?

I must pull my finger out and write a report for the next quarterly

where was your finger dare i ask?

figuratively not doing any useful work

so it wasn't in ur bhole right?

demido: there's nothing to unmount after zpool export as it obviously unmount all fs before exporting the pool

ok ty. i just thought maybe there were 2 layers since i put gpt partition on disk before adding zpool create. but now i know, tyvm!

crb: its possible with some combinations, but likely you'll need to experiment to find a working one depending on client & target OS.

crb: look through e.g. tigervnc tigervnc.org/doc/vncviewer.html IIRC its enabled by default there

having a time trying to find a 1 pcie x16 to 2 x8 riser with notches open in the back so i can put an x16 card in an x8 slot

notches on the back of pcie slots should be the standard

when I running freebsd-version -k -r -u I get this pastebin.com/Fz2GcD3S , but when I running freebsd-update fetch install it says No updates needed to update system to 14.2-RELEASE-p3. , No updates are available to install.

I just updated a infrequently used FreeBSD desktop system to Plasma6, via pkg upgrade. After typing in my password the login screen goes black (with mouse cursor) for a moment and cycles back to the same login screen. I'm using the same password that worked just fine under Plasma5 earlier today.

nwe: most likely, -p2 and -p3 didn't touch kernel code so it was not rebuilt for these patch levels

nwe: looking at freebsd.org/security/advisories and freebsd.org/security/notices it seems to be the case here

Schamschula, anything logged?

I'm guessing something's crashing and kicking you back to the login screen.

cyric: aha, then I understand. Thanks for the help and the link :) will look there too.

CrtxReavr: Any particular log I should be looking for?

Start with just running 'dmesg'

Then /var/log/message I suppose.

Maybe look for core files?

Strange, but I only see one file in /var/log: utx.log

I've disabled sddm. I'll see if I can manually start the desktop

How are you launching ssdm?

Via /etc/rc.conf

Hmm

Honestly, it's been a while since I ran a FreeBSD workstation.

If I don't disable it there, my only option is to boot int single user mode.

s/int/into/

The prescribed method back the, was to launch it via /etc/ttys on the ttyv8 line.

seems broken

Hey, I'm completely new to (Free)BSD, I want to try it out for a personal server with only one user. What are some benefits over a Linux install ? I've been curious as I moved most services to podman recently, and BSD provides jails which some argue are better.

xaltsc: you can run podman on freebsd with jails as its backbone

getz: You mean as the container runner ?

A bit work to run podman pods created on

Linux, but you can easily recreate them for FreeBSD

i used linuxulator and it worked fine

xaltsc: To simplify: you can run jails or you can use podman which uses jails underneath. But out-of-the-box existing podman images created on Linux won't work

getz: first time I hear this name. "Linux binary compatibility" - how is it different than linux.ko, linux64.ko etc?

to run linux stuff just append --os=linux to podman

getz: Asking out of curiosity. I run linux VMs under bhyve and have no need to change this approach.

Do the memstick images come with ssh running btw ?

getz: ok, as I understand this software loads the modules that I mentioned.

xaltsc: iirc no and you need sysrc sshd_enable="YES"

regis: yeah i think we're talking about the same stuff, theres also linuxkpi for drivers but thats something else

getz: Yup, I'm running AMD GPU drivers via linuxkpi and can't wait for proper 5/6GHz WiFi support through linuxkpi ;)

regis: Actually, I meant the RPI images. Can I just edit a file on the sdcard to enable sshd before booting it ?

xaltsc: Souinds doable but you need to stick this card into system capable of mounting UFS or ZFS (unsure if RPi images have ZFS nowadays)

I have ZFS on root on my Laptop, but UFS is definitely foreign to me. Why does BSD use this ?

It works and not every use case calls for using ZFS.

My question may then be rephrased as: why was ext2/extN created (since it seems to be derived from UFS) ?

EXT2 is based on ideas taken from UFS. It's a simple filesystem that just works. UFS2 later added some features like journaling but overall it's rather poor where it comes to configurability. ZFS however may not be ideal on machines with low amount of RAM like RPi and behaves differently in many scenarios. UFS is simple, ZFS is a heavily configurable, completely different filesystem which not

every use-case need. It may for example become memory hungry. As I said: not every use-case calls for using ZFS.

extfs was created because the purpose of Linux was to create a new kernel from scratch. if they just copied everything from existing Unix systems, there would be no point to it

(also, the licensing state of the BSD source code was much less clear back when Linux was created, and the original 4-clause BSD license isn't GPL compatible)

License-wise they likely couldn't slap GPL on code copied from BSD.

Update on my desktop issue: I followed the suggestion from forums.freebsd.org/threads/is-it-po…le-to-upgrade-plasma5-plasma6.97141 and completely removed plasma[56] qt[56] and kf[56] and reinstalled plasma6-plasma and sddm. I can now log in to the GUI, but only if I first choose the Plasma (X11) desktop session in the login in screen.

Is there a way to default to that? It seems to default to Plasma (Wayland), which is rather broken.

wayland is default

on some gpu's it's almost ok

man sddm.conf does give a hint! DisplayServer!

But there would need at leat a decade for wayland to become stable

DisplayServer is X11, not so much WayLand

Probably never will work with wl

From my understanding the KDE Plasma team is likely to "start" work on possible Wayland support after 6.4 is a thing

I'm new to FreeBSD and just listen in on what that team has to say. So consider this more a rumor than a fact