01:07:24 the latest drm-kmod from https://github.com/freebsd, does it correspond to the linux kernel 5.10? 01:07:36 or to newer linux kernels? 03:36:39 Oleg: Considering the name of the port is drm-510-kmod, it's probably fairly likely. 03:49:53 Soni: that hostname!!! 03:50:43 thanks =^-^= 03:51:12 why do you need a hostname here? 04:36:28 anyone got a guide for how to _manually_ set up zfs "zroot" on /mnt during installation in a way that actualyl works? The "guided zfs on root" thing doesn't guide much and insists on using entire disk... 04:37:39 I tried to do it manually, but whatever I do - set mountpoints etc... on boot after install, it _only_ mounts zroot/ROOT/default, and nothing else 04:43:04 kolla yes 04:43:11 kolla 1 min, I think I've blogged about it, lemme check 04:43:49 kolla nah, I did not blog about it, but I know where you can find it. 1 minute :- 04:44:42 kolla here, check this out: https://cgit.freebsd.org/src/tree/usr.sbin/bsdinstall/scripts/zfsboot#n146 04:44:43 Title: zfsboot « scripts « bsdinstall « usr.sbin - src - FreeBSD source tree 04:55:10 kolla: Also maybe worth reading: https://wiki.freebsd.org/MasonLoringBliss/ZFSandGELIbyHAND 04:55:11 Title: MasonLoringBliss/ZFSandGELIbyHAND - FreeBSD Wiki 05:02:10 mason: do you know for how long we have to wait until freebsd drm-kmod starts corresponding to version 5.13 of the linux kernel? I ran into the same issue this guy did: https://forums.gentoo.org/viewtopic-t-1136289-postdays-0-postorder-asc-start-0.html . 05:02:11 Title: Gentoo Forums :: View topic - [SOLVED] Intel graphics, no signal once kernel loads i915 05:07:05 Oleg: The efnet #freebsd-xorg folks might know. 05:07:10 I don't unfortunately. 05:07:24 antranigv: thanks! 05:08:18 I really find it awkward that the installer insists on using entire disks and doesn't even let the user decide how much of the disks to use 05:08:32 kolla: The installer gives you a shell to partition if you want. 05:08:45 Can't get much more flexible than that. 05:09:13 yes, but that requires skills beyond normal to get it working 05:10:13 that is why I asked, because no matter how nice and tiny and finished I made the zpool manually, after install, on bootup, it _only_ mount the zroot/ROOT/default, and no other zfs 05:10:40 It's not that bad to do 05:11:26 well, clearly the "auto" thing does some magic I didn't do, despite 20-30 lines of manually defining it all 05:12:13 I set all mountpoints correctly, I zpool set bootfs, I could export and import zroot manually and all looked nice 05:12:26 but on reboot... bah meh, no 05:12:48 an empty /usr doesn't get the system far :) 05:13:31 Did you make sure it was all in place before letting the installer populate it? 05:13:43 Or was everything populated, and just not mounting on boot? 05:14:39 This might be cargo-cult of me, but I think you still need vfs.root.mountfrom= 05:14:48 in loader.conf 05:15:33 yes, everything is populated correctly... I boot from installer USB stick, I can import the zpool and all is there, all filesystems, nicely populated 05:16:34 if I let the installed have a go with entire disks, that is default... I don't get any vfs.root.mountfrom= in loader.conf 05:17:08 it would be ok to let it have all disks if I could shrink the pool afterwards... but I believe that isn't an option 05:17:25 Using GPT partitions is the way to go, yeah. 05:17:53 if installer could create a rather minimal zroot pool, it wouldn't be hard to expand it afterwards though... 05:18:25 yes, have to use GPT, 8 x 4TB disks 05:20:27 odd thing is.. I have this other identical system that I installed 3 years ago or so, and I don't recall having this struggle 05:21:28 kolla: I'd recommend taking notes on how you're doing the partitioning, and then having my guide there to make sure as you go through that you're not missing anything. 05:21:45 wellwell, I will try to follow the last guide there, thanks again :) 05:21:57 mason: yes 05:22:30 Well. Do your own thing but make sure if the guide is doing something that you're either doing an equivalent or that you explicitly don't need to. 05:27:53 Good luck anyway. Hitting the sack here. 05:36:32 thanks, and... good idea to also inclide EFI partitions, my systems are indeed legacy (though 64bit), but who knows, maybe I want to move it over to EFI system later 05:36:40 good night :) 05:54:37 also... really wish the installer iso was prepared for running sshd, which today isn't any "out of the box" experience, with read-only /etc/ssh and /etc/passwd 05:55:12 08:04:06 do old freebsd cd releases include binary packages or distfiles? 08:13:57 dksnd: on other cd's or dvds there were packages... depends how old 08:14:07 by old we surely mean 4.6? 08:14:20 around 2005-2006 08:15:02 http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/ISO-IMAGES/ 08:15:04 Title: Index of /pub/FreeBSD-Archive/old-releases/i386/ISO-IMAGES/ 08:15:07 it's all here 08:16:13 i don't think anything included ports distfiles... so you need to search for that somewhere else 08:16:14 but those are pretty useless without the ports/packages 08:16:24 you have packages 08:16:40 but old source is pita 08:17:12 i bet you can get old kde running 08:17:34 won't put money on that though 08:18:04 what's the use case of that? 08:19:50 a retrocomputing experiment 08:20:08 hmm 08:20:23 i have no idea what packages are in 6.0r cd2 08:20:38 that's supposedly full of them 08:21:41 never used that feature 08:21:46 but it comes handy 08:22:16 i also have too many ports distfiles... 08:22:36 somehow i've stored them 08:23:05 unsure if there is mirror of them 08:23:14 seems way too much data 08:24:15 no problem with base though 08:24:30 every installer has copy 08:26:23 i think you could install *some* things from selected packages included in installer medias 08:27:32 funny how windows or dos might be easier to retro-setup 08:28:23 eh 08:28:36 i could install 4.6 for fun 08:28:50 4.6 because that's where i started at 08:33:46 e? 08:48:18 e? 09:21:13 so I installed freebsd 5.3, but it refuses to boot lol 10:34:17 xd 10:36:23 https://gitlab.com/DeaDSouL/NixGems 10:36:23 it's UNIX & GNU/Linux useful things written in a chetsheet style using VIM markers in a text file 10:36:23 if you're interested in helping out, you're more than welcome to 10:36:23 As you're so welcome to use it 10:36:24 Title: Mubarak Alrashidi / NixGems · GitLab 11:26:35 it prints a menu "F2 FreeBSD" and nothing happens then 11:27:30 I can use a livecd to manually load its kernel and provide the root path interactively 11:40:33 does it mean F2 key will boot the corresponding partition? 11:41:30 I used boot0cfg on the entire hdd and disklabel on the freebsd slice 11:47:47 interesting, when I use an external loader to boot to the partition directly, it shows a boot menu and a devil ascii art 11:48:26 it seem to mount the root automatically from that menu 12:17:45 àpparently "packet,noupdate" options did the trick 12:18:50 dksnd: which software has those options? 12:19:01 boot0cfg 13:19:50 sh doesn't like non-ascii characters it seems 15:24:00 hello. i just did a pkg-upgrade on my freebsd 13.1 laptop with kde, and after reboot, i no longer get sddm login screen; just black screen with cursor 15:24:19 using pkg quarterly. was working fine before this update. anyone else facing similar issue? any known fix? 15:24:36 sddm log does not show any (obvious) errors 15:30:08 what does Xorg.log say 15:30:51 i don't see any errors there either. i think Xorg is fine, because i the rendered cursor 15:31:13 i think it's something specific to kde plasma and/or sddm 15:31:24 ldd `which sddm` 15:31:56 returns bunch of suff...anything specifc i should look at? 15:32:08 Missing 15:32:28 doesn't show anything missing 15:32:41 do you have the port cloned ? 15:32:46 ports* 15:33:11 i do; probably need to update, but yes 15:33:27 compile it by hand see if that fixes it 15:33:40 hmm, ok. just sddm or all of plasma? 15:33:43 as long as you dont change the dewfault options you wont have issue with pkg 15:34:15 actually as root service sddm stop 15:34:24 yea, i don't think i ever needed to touch sddm options on this laptop 15:34:37 echo "startplasma" > ~/.xinitrc && startx 15:34:39 see if that works 15:35:17 think I got the start script wrong but start will give you the correct name 15:35:28 if that fails then yeah recompile the full kde* 15:37:06 and note it will take "a while" 15:51:58 CorvetteZR1 I had a few problems like that 15:52:45 I don't think that the problem is with sddm, I can ssh in and I see plasma etc starting 15:54:02 If I start killing things in reverse order of pid then it will restart services and I get KDE up 15:54:26 This seems intermittent, and I haven't yet started taking notes and recording pstacks 15:55:20 sorry, had to take a call...will try that now cpet 15:55:40 paulf, cool, i'll play with it and see 15:57:01 cpet, looks like it's same behaviour with startplasma and startx...black screen, only cursor 15:57:11 so it's probably not a sddm thing then, looks like plasma specific 15:57:28 looking for mpts / 0mp 15:57:50 I wonder if my ZNC has lost messages 15:57:57 I also tried renaming ~/.config to ~/.config.bak and rebooting which had no problems 15:58:24 but I didn't want to lose all my settings so that was just for testing 15:58:59 actually, when i right click, i get the kde right click menu 15:59:07 so it's just the actual desktop that's not being rendered 15:59:56 it can even draw the kde settings window, but there is nothing in it 16:00:10 kolla: Hey, don't know if you saw the link, but while it's maybe vaguely tedious, you can get ssh going from the install environment: https://wiki.freebsd.org/MasonLoringBliss/InstallEnvironment 16:00:11 Title: MasonLoringBliss/InstallEnvironment - FreeBSD Wiki 16:00:27 Would have mentioned this last night if I knew you wanted it, but I'd gone to bed. 16:00:48 does freebsd have scrolling in tty? shift+ pageup not working for me... 16:01:25 yeah thats not the key combo 16:01:29 and this keyboard does not appear to have a scroll lock 16:01:32 ctrl alt pgup I think 16:01:58 no, that's not doing it 16:06:42 you will need a scroll lock :) 16:21:08 ah, got it...Fn K 16:21:50 i'm seeing bunch of TypeErrors from main.qml 16:22:32 TypeError: Connect read property ;configuration' of null 16:22:47 something is definitely messed up with plasma 16:24:19 is there a plasma5 meta port? 16:24:31 is plasma5-plasma it? 16:24:44 ah, it sure is :) 16:32:08 ok, i think it's working now 16:32:42 i saw some OpenGL errors when starting with startx. i reinstalled the nvidia-driver-390 port (because i have an old fermi). reboot and now it's loading 16:32:51 thanks for your help cpet and paulf ! 16:56:45 I'm interested in dualbooting freebsd alongside openbsd as a gaming platform (steam/wine), what pitfalls can I expect, and should I just go with linux instead? 17:02:36 why don't you try it and find out 17:07:39 because it's a bunch of work and if it sucks anyways it'd be nice to get some opinions in advance 17:10:04 ssm_ well, most FreeBSD people dualboot with Windows/Linux, most OpenBSD people don't dualboot at all, this will be a very hard research :D 17:11:47 I used to build a lot of multi-boot images - often with 3-4 OSes each. 17:12:03 The age of virtualization sorta killed off the need for much of that. 17:12:38 Though. . . dual-booting FreeBSD & OpenBSD should be pretty trivial. 17:13:32 Start with FreeBSD, be sure to install the FreeBSD boot manager (and leave un-partitioned (sliced) space on your first drive for OpenBSD. 17:13:37 wasn't worried about the difficulty of dual booting, just wanted to know how well wine (&| the linuxulator w/steam) works comparatively to linux 17:13:53 When you install OpenBSD, but sure not to let it touch your MBR. 17:13:59 And you shoudl be golden. 17:14:06 I'm using efi, so I don't think there should be any problems 17:16:03 I love FreeBSD, but if I wanted a *nix OS for Steam, I'd go with ArchLinux, since it's what Steam Decks are built with. . . best gurantee of support & compatability. 17:16:32 That said, there's plenty of happy people doing it with RHAT & Debian derivatives. 17:36:31 Steam on Debian is reliable. The actual Linux application you install is still based on some old Ubuntu. 17:37:35 I don't want to know about debian or arch, I want to know how well freebsd supports it 17:38:46 I can't stand linux, if I just wanted the easy solution I wouldn't have even asked in the first place 17:39:49 Was replying to CrtxReavr, but sure. 17:40:18 Tell us how it works out, anyway. I'd be curious to know. 17:40:39 ssm_, whats wrong with slackware ? 17:41:15 cpet: No package dependencies. Imports PulseAudio and elogind. 17:42:35 best parts of slackware! 17:43:07 we do as well 17:43:28 * mason hums https://www.youtube.com/watch?v=IshuAyeaNaY to himself 17:43:29 Title: I Do Not Want What I Haven't Got - YouTube 17:43:59 cpet: That's part of why I recommend Debian for the purpose - very happy with neither of those. 17:44:17 That said, I've been curious for years now about how Steam on FreeBSD (sans wine) is progressing. 17:45:12 just recompile x without pulse 17:45:27 cpet: no linux distribution has administration tools I enjoy using; when something goes wrong (which I expect is just inevitable with linux) I won't know how to fix it 17:47:40 what sort of admin tools are required that arent in *nix 17:47:51 most sysadmins create there own 17:48:40 right now im on a openbsd host logged into a freebsd system next to this one 17:49:34 ssm_: FWIW, if you get into an install, realize that you're probably safer building drm-kmod from ports, as the binary packages can be problematic as you move up minor revisions. While this is being looked at and will be address someday, for today you want to build it locally for the installed version. 17:49:50 s/address/&ed/ 17:51:17 theres an option that rebuils a portt after each kernel 17:51:24 i do this and prevent issues with drm* 17:52:16 Ah, TIL. What's the option? 17:57:35 PORTS_MODULES 17:57:35 Set this to the list of ports you wish to rebuild every 17:57:35 time the kernel is built. 17:57:38 in make.conf 17:58:52 cpet, that mean they'd be build by buildkernel? 17:59:06 yeap 17:59:08 s/build/built 17:59:13 Cool. 17:59:34 this breaks freebsd-update if you add or remove options 17:59:50 this this is nice if you use current 18:00:08 I'm a luddite who maintains is world & kernel from src. 18:00:32 too each there own 18:00:47 Indeed. 18:00:49 Lots of rope. 18:01:14 pkg install tmux firefox xorg xfce4 hexchat drm-kmod 18:01:22 is all I do now heh 18:01:44 Why tmux? 18:01:46 changing drm-kmod for tigervnc 18:01:50 As opposed to screen, I mean. 18:02:03 its whats on open and got used to it 18:02:19 hmm 18:02:40 I've literally built-up over three decades of screen muscle memory. 18:02:40 on a lame point its not gnu 18:02:41 :) 18:03:21 however ive been on some peoples servers and they have screen doesnt bother me i just like tmux 18:03:23 CrtxReavr: I've heard you can remap tmux now to match your finger memories. Also, it's permissively licensed. As for me, it's free software and I like it, and I've actually needed it for serial consoles in the past, so I stick with it. 18:03:43 Not a big GPL fan, certainly, but I prefer functionality over license zealousy. 18:03:48 ^ 18:03:59 I actually quite like the GPL, just not how some folks interpret it. 18:04:28 tmux (and dvtm if you want something slimmer) can do lot of useful window layouts, unlike screen 18:04:37 BSD and other licenses are a lore more business friendly. 18:04:57 And if making terminal session reattachable is the only thing you want then dtach is much simpler 18:04:58 tmux works nicely when you have process limitations :P 18:05:04 Eh, having been part of several businesses that build things based on GPL'd code, I think that's more notional than real. 18:05:24 then get mad when they are forced to submit src 18:05:35 again too each there own regarding licenses 18:05:40 I mean. . . my employer flat-out forbids running anything covered under gpl3. 18:05:52 Also tmux's interface is quite nice for scripting access to the terminal states, should you for some reason want that. 18:05:52 I like 'em all. Free sofware, gimme more of it. 18:11:23 can someone explain to me what this answer is? https://forums.freebsd.org/threads/cron-pam_opie-so-and-freebsd-9-1.36934/ 18:11:24 Title: cron, pam_opie.so and FreeBSD 9.1 | The FreeBSD Forums 18:12:23 " Thus updating libs and binaries but not restarting the services that was already running..." 18:13:29 Someone know if it's possible to run Mac OS on bhyve technically? 18:13:35 * CrtxReavr cringes when he sees people using the reboot command. 18:13:46 what's bad with reboot? 18:14:04 Just not best practices. . . 18:14:06 yeah what did i do wrong 18:14:18 I use it quite often, init* smells too much SyS-V 18:14:24 (often as in, if I ever have to reboot) 18:14:26 You know how your system has the rc.d/* scripts. . 18:14:33 sure 18:14:41 And when your system boots, they all get run with the 'start' keyword? 18:14:46 reboot is just an alias isn't it? 18:15:21 the script's get invoked if you mean that 18:16:22 Well, the scripts don't get run wtih the stop keyword on reboot, if that's what you mean. 18:16:29 Not unless there's been a recent change. 18:16:59 hmm Im not sure if I remember correctly, I dont often reboot - today I had to shutdown a BSD host and honestly just pushed the power knob (Which uses ACPI).. 18:17:01 I mean, depending on what you're running, that may not be a big deal. . . but that's where it comes down to best practices. 18:17:07 so I thought I remember that the scripts issued with "Stopping XYZ..." 18:18:39 Normally, the shutdown(8) utility is used when the system needs to be 18:18:39 halted or restarted, giving users advance warning of their impending doom 18:18:39 and cleanly terminating specific programs. 18:18:46 That's straight from reboot(8). 18:18:55 hmm okay 18:19:23 So. . . ``shutdown -r now` 18:19:55 so reboot just sends SIGKILL? 18:20:06 ah well SIGTERM and SIGKILL 18:20:13 or ``shutdown -p now`` instead of halt. 18:20:15 Right. 18:20:28 which is not too bad since the programs are supposed to handle this :) but yeah maybe not soo great either 18:20:42 And you may be on a system where there's a shutdown or cleanup procedure for a specific service. 18:20:43 but yeah I simply dont reboot that often, not using FreeBSD as desktop 18:20:51 Like a relational database, or some shit. 18:20:57 ya databases are evil 18:21:31 It's just best practice to avoid use of the halt & reboot commands. 18:21:32 ... what 18:26:56 ok so i keep getting errors regarding pam_opie.so not being found. this library file does not exist on my system. 18:31:18 SymbioticFemale, the link you provided... basically restart the services or reboot the machine 18:32:13 i see. that won't solve my issue then since i've restarted since any update. 18:32:57 SymbioticFemale: it was removed from freebsd 18:34:15 hi all. strange observation I don't understand. I have an additional loopback interface configured with some addresses assigned to it (for use in jails). when I try and ping an address assigned to lo1 e.g. 127.0.1.1, the traffic appears in tcpdump over lo0 instead. 18:35:01 that's because 127.0.1.1 is in the 127.0.0.1/8 network of lo0 18:36:15 so to compensate for pam_opie.so being removed, can i just comment out any lines in pam.d/* that reference it? 18:36:27 SymbioticFemale: yes; or rmove thehose lines 18:36:46 thanks! 18:37:59 ah yeah, thanks. for some reason I thought loopback was a /24. what addresses would you typically assign to a second loopback then? 18:39:28 do you really need a second interface for it? 18:39:59 hm. probably not. I guess the thinking was to just keep lo0 as standard as possible, but I suppose I could just assign the additional addresses as alises for that 18:40:32 the address is fine, but i'd skip using lo1 unless you had a great reason to do so. 18:41:19 cool thanks, will just assign them to lo0 - should work the same in terms of setting them as jail IPs 18:42:47 Can anyone tell me how to fix this? "The following files are affected by updates. No changes have been downloaded, however, because the files have been modified locally: /var/db/etcupdate/log". Happened after a freebsd-update fetch/install 18:43:17 rtprio: thanks again. it solved my problem and i can login again :-D 18:43:33 👍 18:43:43 not found anything substantial in the freebsd docs/handbook.. not sure if I overlooked something. 18:44:34 i'd look in the `man etcupdate` but i'd probably unmodify that file. 18:46:24 not sure how I'd "unmodify" it.. is there a stock version to compare it to? 18:54:57 i'd probably move it to the side and try to run it again 18:56:30 cpet: there was also a period when screen would randomly segfault on terminal window resize or just plain attach with a different window size than was when detached, it was absolutely infuriating 18:56:56 and that is how I switched to tmux 18:57:25 though I do have its command key bound to ^A 19:05:01 i did that as well 19:33:10 Remilia, was that in 1993? 19:34:36 tmux didnt handle window sizing properly until recently, and even then there's some special "super-long-to-type" options for it 19:34:46 (for reattaching anyways) 19:35:20 It's been a LONG time since I've observed issues like Remilia is describing with screen. 19:35:28 whereas screens reattach has automatically resized for literally decades 19:35:46 i've never seen that and i've been using screen since the 90s 19:35:49 -shrug- 19:35:53 CrtxReavr: it was from 2007 to around 2012 19:36:39 I've seen screen freak out when switching between certain combinations of terminal types. 19:36:46 I think it still happens according to a friend, I just no longer use screen myself 19:37:05 Probably an envirionmental thing, vs. an issue with screen itself. 19:37:12 thats my guess 19:37:34 CrtxReavr: PuTTY + FreeBSD, nothing else 19:37:46 Putty emulates lots of things. 19:37:52 maybe i've just been lucky in picking the right sized terminals to not cause it to crash on reattach this whole time ;-) 19:38:06 Plus, bytes do occasionally get munged. 19:38:15 nacelle: I am not sure what was wrong with tmux resizing tbh, unless you mean when you have two terminals attached to one session and one of them is smaller 19:38:26 Remilia: that is the problem 19:38:35 A ^L or ``echo ^VAlt-O`` can do wonders. 19:38:47 nacelle: you mean screen would resize the terminal window on the smaller side? 19:38:58 tmux attach -f ignore-size,active-pane 19:39:46 CrtxReavr: I mean, it is most definitely not an issue with screen if it segfaults due to terminal resizingf 19:39:57 it is expected behaviour 19:40:18 a tool like screen *should* crash unexpectedly 19:40:23 Again. . . used screen for over 30 years. . . 19:40:42 I've never encountered that, but you have. . . 19:40:45 irssi handles the resizing without issues 19:40:49 What conclusion are we to draw? 19:41:09 * Remilia .oO(I see . . . those are. . . the. . . fabled. . . ellipses. . .) 19:41:12 <=== irssi inside of screen, all day, every day. 19:41:27 I can't remember ever seeing screen(1) crash. 19:41:27 nacelle: yeah I ran irssi 19:41:44 and attaching to irssi led to segfault once every 1-3 weeks 19:41:45 CrtxReavr: I am doing irssi in screen and irssi in tmux all day, every day... -sigh- 19:41:55 I've seen it crash, but not on any chronic or systematic basis. 19:42:09 it only started sometime in 2007 19:42:24 Update your shit? 19:42:26 I havent bothered to upgrade the tmux on the box where i'm running screen, where its tmux doesnt support the ignore-size bit 19:42:48 also, I always used the latest versions of ports since I do not use binary packages 19:43:07 I guess ‘update your shit’ means using the git HEAD? 19:43:26 instead of ports 19:43:32 screen? why use that when tmux is so much better and cleaner code? 19:43:43 pertho: religion, I assume 19:43:49 tmux doesnt do all the screen does yet 19:43:58 Or "if it's not broken, don't fix it." 19:43:59 if you're used to what screen does and tmux doesnt do it... you still use screen 19:44:05 tmux is also noticeably lighter on my 1 GHz 6W Jaguar SoC 19:44:08 it does everything I need it to 19:44:17 try harder 19:44:36 nacelle: You mean attaching to serial tty? 19:44:49 no, i never use it for that, eww 19:45:07 tmux can attach to bhyve stuff and that is enough for me 19:45:09 (I am a minicom nerd) 19:45:12 14:43 < pertho> screen? why use that when tmux is so much better and cleaner code? 19:45:18 Did you come up with that on your own? 19:45:41 Then I have no clue what screen-specific feature you are talking about. 19:45:53 I already talked about some of it 19:46:26 CrtxReavr: screen has (or had?) a lot of really ancient, legacy code 19:46:40 tmux doesnt handle resizing well, and only recently (in the past year) took on the correct fix that works like screen -always has-, but you have to enable it with a horrible command line option 19:46:51 its not just like "screen -x" and bam yer in 19:47:08 I've never had issue with the way tmux handles resizes FWIW. 19:47:31 CrtxReavr: I'll go with pertho on this one. screen(1) uses the GNU brace style. It's far more pleasing looking at tmux source. 19:47:43 ccx: I definitely have, to the point of pursuing the fix with the tmux devs. 19:47:48 which is why its in place. 19:47:51 That said, I don't look at it ever so that hasn't been a factor for me. :P 19:47:56 * CrtxReavr facepalms. 19:48:18 Was it FreeBSD-specific? Because I've haven't encountered it in past decade or so. 19:48:58 no 19:49:29 tmux handles resizing fine; perhaps you should polish your tmuxrc 19:49:46 its been there forever. if you reattach in tmux without any options, the tmux virtual terminal stays the same size as the originating session 19:49:46 yeah I've not had issues with tmux resizing 19:49:52 I still think it is a matter of religion, I am not going to tell anyone to switch to tmux but when people tell me ‘screen is better, tmux is bad’ I can only shrug 19:49:52 it wont resize to your current terminal 19:50:27 setw -g aggressive-resize on in your tmux.conf 19:50:47 nacelle: it resizes for me as long as there are no other sessions with smaller sizes 19:50:50 automatically 19:50:55 I have no clue why 19:51:02 i'm not disconnecting my other sessions 19:51:05 (and it has been doing that since I started using it) 19:51:32 rtprio: I use ignore-size 19:51:59 the correct fix for me has been to use -f ignore-size,active-pane 19:52:12 (active-pain!) 19:53:05 "By default, all windows in a session are constrained to the size of the smallest client connected to that session, even if both clients are looking at different windows. It seems that in this particular case, Screen has the better default where a window is only constrained in size if a smaller client is actively looking at it. This behaviour can be fixed by setting tmux’s aggressive-resize option." hmm 19:54:18 I have mutliple workstations in my house, with multiple floors, and a phone that I journey out into the world with. From all of these I can access the same tmux sessions (through various vpns and whatnot, of course)... I dont disconnect my existing tmuxes, which a lot of paranoid people do (same with screen - how many people use screen -rd vs screen -x ? probably heavily for -rd and far less for -x, 19:54:25 though -x is -far- more convenient for the lazy) 19:54:36 I find tmux default perfectly reasonable there. But that option has been there for ages. 19:54:51 aggressive-resize doesnt take care of it iirc 19:54:57 its been a while since i've dug into this 19:55:12 (which is approximately when ignore-size came around) 19:56:03 So you want to crop the screen on some clients? Weird, but you do you. 19:56:07 (I'm not asking for a solution) 19:56:30 I want the terminal to be wrapped normally on each client 19:56:40 the irssi status bar should be roughly readable, etc. 19:56:44 its not hard 19:56:47 its not weird 20:00:16 It is hard if the application uses cursor-moving escapes and relies on certain terminal size. It will break certain applications if the actual and assumed terminal sizes are different. You may not use those applications but it's certainly not a setting that should be default. 20:03:01 It is a sad fact of the tty design that it hasn't been designed to be easily reflowable, but it's one of the many warts we've been stuck with for past 40 years. 20:05:16 Someone know how I can define an outgoing interface for an ipv6 defaultroute when I've two interfaces in same network? 20:06:48 megaTherion: I don't know if this works but try creating a static route for :: with a next-hop of % 20:07:32 So like fe80::abcd%igb0 20:08:50 bahamat: thanks, good idea - that worked 20:08:56 damn I totally forgot about the % prefix syntax 20:28:42 ccx: I disagree with not as a default, but i'm basing that on screen having it that way as default for 30+ years - it worked well there imo, but thats just me 21:52:19 as a single user, I just use `tmux -u new -DAs default` and as far as I know, just tmux defaults 22:24:10 "-s default" is kind of redundant, no? 23:46:49 mason: regarding ssh to iso boot, yes that is what I ended up with doing... like I wrote, not entirely an "out of the box" experience :) 23:47:36