01:01:59 armin@bsd:~ tmux 01:02:00 open terminal failed: not a terminal 01:02:00 armin@bsd:~ echo $TERM 01:02:00 xterm-256color 01:02:00 armin@bsd:~ 01:02:03 what am I missing here? 01:04:58 what worked in the end was killing the old tmux sessions, but I don't see why 01:06:39 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) 01:08:03 ouch, aside from the error being misleading, that will bite you if you still got something running there you require 01:08:25 that's not good 02:28:19 i thought i read something about reducing the size of a zpool mirror? 02:28:43 or is it always an export/import 02:50:31 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. 03:18:15 i thought there was a trick to zpool attach but cant recall the specifics 04:48:15 hmm i thought it was that if you attach a mirror member of the desired smaller size, the entire mirror shrinks? 05:14:41 jmnbtslsQE: maybe that was it? 05:24:00 jmnbtslsQE: perhaps not: `cannot attach /dev/diskid/DISK-0000000012320911E0A8p4 to /dev/diskid/DISK-WD-WCASU3166144p4: device is too small` 06:15:19 rtprio: it looks like i had this confused with the opposite, expanding the size by adding a larger member 06:23:36 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 06:26:33 can't attach it, but can add it and then remove the other parts 06:26:51 it will copy things over, seems to be working, but i haven't removed both old ones yet 06:27:36 and then attach the 2nd half of the mirror 06:27:41 yolo-ops 07:20:01 yikes installing freebsd on the hdd instead of the ssd in this mac mini. quite a difference in install speed (as you would expect) 07:23:06 i remember when macos used to do verbose booting, a long longgggggg time ago 07:45:29 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 08:07:07 did you enable sddm to start at boot? sysrc sddm_enable="YES" 08:07:42 nope, is that in a config file somewhere? 08:09:46 sysrc is a command to modify /etc/rc.conf, you can also do it manually if you want 08:10:02 ah i see, let me see if this does it 08:16:42 does the “YES” actually have to be in quotes? 08:21:36 gah it didn’t work, still booted to a unix prompt 08:24:39 /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 08:25:03 thats what i assumed - but even with quotes, it didn’t work 08:25:14 i sitll start up to a text login 08:27:41 and if you try service sddm start ? 08:28:51 I probably want to use the 'onestart' option in that case. 08:29:02 “sddm does not exist in /etc/rc.d or the local startup” 08:30:49 do you edit rc.conf with sysrc? 08:31:01 i edited it with nano in this case 08:32:10 enabled dbus also? 08:32:25 no? 08:33:37 oh dbus is already enabled in rc.conf, not by me 08:33:40 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) 08:34:36 hm, that error message reads like sddm in't installed, can you double check that you have indeed installed it? 08:34:58 it should have been installed via `desktop-installer`, how can i verify? 08:35:16 is there a command to list installed packages with pkg? 08:35:34 I agree, sure sddm is installed and also dbus 08:35:49 pkg info sddm 08:36:14 gah no packag matching sddm 08:36:15 wth! 08:36:37 and just pkg info lists all installed packages 08:38:33 i’m not sure what happened. did desktop-installer mess up, or did i somehow 08:38:51 only one way to find out i suppose 08:44:40 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 08:44:54 that happens all the time because on macos there is no numlock, its just a numberpad all the time 09:01:47 ok i installed sddm via pkg and it works now. i’m not sure why i needed to do that though 09:42:31 huh, Puppet is dead (for non-enterprise users)? that'd mildly surprising 09:47:37 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 10:47:04 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? 11:08:38 ivy: well he said it, right? and it's super long massive discussion 11:09:04 should have removed second quote level 11:09:25 yeah if you just meant to reply to him it's fine, i'm just wondering if i need to do anything 11:10:04 i didn't leave you in :p 11:11:11 i just took that from your message indeed lol 11:11:37 but yeah why is nfs hassle to secure and configure 11:12:24 maybe i should be 82, not 42 to get it 11:12:39 oh and grow unix beard? 11:12:49 i just cut it all off again 11:18:31 When that happens you go into hibernation 11:48:59 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. 11:49:22 ridcully: At least I would have loved if it did. 11:50:01 ridcully: Simply telling the user that their terminal is broken (which in fact it is not) is not helpful here, either. 12:21:38 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 12:21:55 in linux there is supposedly the option to run the old binary from proc 12:23:25 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 12:31:01 https://cgit.freebsd.org/ports/diff/sysutils/tmux/pkg-message?id=458a737a70fdcd2882396967fcd19d2632400847 12:31:21 There actually is such a warning, so I probably overlooked that one, indeed. 13:05:33 GoSox: You can also list services with service -l , and enabled services with service -e 14:21:51 ivy: openvox has been working ok, except for ruby versions and the unfortunate name 15:45:53 yo i made it to freebsd community awesome 15:46:03 hello 15:46:11 oh sorry we stopped giving out memberships yesterday 15:46:20 we did not 15:46:21 they were running it on a 486 still for some reason and the machine went down 15:48:51 there was a chap on undernet who was running on a 486 a while back 15:49:20 I was using a 486 until about 2002 15:49:36 i need to set my part_message and quit_message irc configs - hope all is good freebsd community 15:49:49 ...k 16:45:02 rrcipge: Weclcome 16:45:31 they left ~9 seconds after their final message 18:21:09 anyone seen the loader screent ( "BIOS Drive c: is disk0) hang with a | (where the \ | / spinner is) 23:38:47 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. 23:42:12 I am considering to switch to it. Have you used it with the twm windows manager? 23:42:30 * window manager :-) 23:55:59 ivy: do you regularly confirm stuff?