armin@bsd:~ tmux

open terminal failed: not a terminal

armin@bsd:~ echo $TERM

xterm-256color

armin@bsd:~

what am I missing here?

what worked in the end was killing the old tmux sessions, but I don't see why

you need to restart tmux after upgrading as the message instructed (no idea why tmux says "not a terminal" when it can't talk to the server process, because the protocol changed)

ouch, aside from the error being misleading, that will bite you if you still got something running there you require

that's not good

i thought i read something about reducing the size of a zpool mirror?

or is it always an export/import

As far as I know the only way to reduce the size of a zfs zpool is to create a new zpool of smaller size and copy the data to it.

i thought there was a trick to zpool attach but cant recall the specifics

hmm i thought it was that if you attach a mirror member of the desired smaller size, the entire mirror shrinks?

jmnbtslsQE: maybe that was it?

jmnbtslsQE: perhaps not: `cannot attach /dev/diskid/DISK-0000000012320911E0A8p4 to /dev/diskid/DISK-WD-WCASU3166144p4: device is too small`

rtprio: it looks like i had this confused with the opposite, expanding the size by adding a larger member

armin: if you can get you hands on the old binary (e.g. it might still be around in the pkg cache), then you can gracefully close the old session

can't attach it, but can add it and then remove the other parts

it will copy things over, seems to be working, but i haven't removed both old ones yet

and then attach the 2nd half of the mirror

yolo-ops

yikes installing freebsd on the hdd instead of the ssd in this mac mini. quite a difference in install speed (as you would expect)

i remember when macos used to do verbose booting, a long longgggggg time ago

crap, this time i installed xfce4 with sddm but i’m still geting a command line login screen at boot, not a gui login screen, what givvesss

did you enable sddm to start at boot? sysrc sddm_enable="YES"

nope, is that in a config file somewhere?

sysrc is a command to modify /etc/rc.conf, you can also do it manually if you want

ah i see, let me see if this does it

does the “YES” actually have to be in quotes?

gah it didn’t work, still booted to a unix prompt

/etc/rc.conf is sourced by a sh script (rc), so that string YES doesn't need quotes, as it doesn't have spaces or special characters

thats what i assumed - but even with quotes, it didn’t work

i sitll start up to a text login

and if you try service sddm start ?

I probably want to use the 'onestart' option in that case.

“sddm does not exist in /etc/rc.d or the local startup”

do you edit rc.conf with sysrc?

i edited it with nano in this case

enabled dbus also?

no?

oh dbus is already enabled in rc.conf, not by me

linXea: but sddm is already enabled, so onestart isn't needed (or start would say that it isn't enabled and something went wrong when trying to enable it)

hm, that error message reads like sddm in't installed, can you double check that you have indeed installed it?

it should have been installed via `desktop-installer`, how can i verify?

is there a command to list installed packages with pkg?

I agree, sure sddm is installed and also dbus

pkg info sddm

gah no packag matching sddm

wth!

and just pkg info lists all installed packages

i’m not sure what happened. did desktop-installer mess up, or did i somehow

only one way to find out i suppose

i wonder if maybe the num lock was off and i just hit “2” on the keypad and hit return and didn’t noticed i actually typed nonsense

that happens all the time because on macos there is no numlock, its just a numberpad all the time

ok i installed sddm via pkg and it works now. i’m not sure why i needed to do that though

huh, Puppet is dead (for non-enterprise users)? that'd mildly surprising

hmm so i ran through `desktop-installer` again, choose sddm over xdm, but it didn’t seem to actually install it. It just ignored my choice, so it would seem

ketas: why do you reply to my message on arch@ when you are only quoting Rick's message? are you expecting an answer from me?

ivy: well he said it, right? and it's super long massive discussion

should have removed second quote level

yeah if you just meant to reply to him it's fine, i'm just wondering if i need to do anything

i didn't leave you in :p

i just took that from your message indeed lol

but yeah why is nfs hassle to secure and configure

maybe i should be 82, not 42 to get it

oh and grow unix beard?

i just cut it all off again

When that happens you go into hibernation

ridcully: That's the thing, the upgrade should put the old binary somewhere *AND* tell you about it so that people actually can get access to their old sessions.

ridcully: At least I would have loved if it did.

ridcully: Simply telling the user that their terminal is broken (which in fact it is not) is not helpful here, either.

armin: the ticket about the error was closed in tmux without adressing the problem. and i guess leaving an old (potentially vulnarable) binary around was no option for fbsd

in linux there is supposedly the option to run the old binary from proc

the reason is more likely that building an old version of tmux as part of the build for the newer version just doesn't really make any sense. the change was noticed in UPDATING, which you are supposed to read before upgrading

There actually is such a warning, so I probably overlooked that one, indeed.

GoSox: You can also list services with service -l , and enabled services with service -e

ivy: openvox has been working ok, except for ruby versions and the unfortunate name

yo i made it to freebsd community awesome

hello

oh sorry we stopped giving out memberships yesterday

we did not

they were running it on a 486 still for some reason and the machine went down

there was a chap on undernet who was running on a 486 a while back

I was using a 486 until about 2002

i need to set my part_message and quit_message irc configs - hope all is good freebsd community

...k

rrcipge: Weclcome

they left ~9 seconds after their final message

anyone seen the loader screent ( "BIOS Drive c: is disk0) hang with a | (where the \ | / spinner is)

Anyone else using XLibre? I've had zero issues and been using it for a few months on one of my laptops. Migrated my remaining systems to it yesterday.

I am considering to switch to it. Have you used it with the twm windows manager?

* window manager :-)

ivy: do you regularly confirm stuff?