00:33:38 I have a dataset zroot/usr/home which is mounted at /usr/home. My homedir is under /usr/home, as I would expect it to be. When I create a new user with adduser I get a new dataset zroot/usr/home/NEW_USER and I don't want that behaviour. I'd like to have all new users be under the existing dataset. How do I achieve that? 00:35:14 Until now, I've been the only user on the system, so have never noticed this behaviour till today lol 00:37:58 mns: it's a relatively new addition; there' a -Z flag for it 00:38:44 see also adduser.conf(5) for a more persistent setting 00:39:30 ahh ok 00:40:49 kevans: thanks! I don't know how I missed this option when reading the man page :( I don't think it was mentioned in the Handbook 00:42:45 mns: that's not terribly surprising, the handbook doesn't catch up very quickly 00:48:28 I guess so. So this must be a really recent change. I'm on 14.3-RELEASE 00:50:12 yes, within the last year or so 01:03:14 cool, good to know 01:36:22 I was curious when this was added in: https://github.com/freebsd/freebsd-src/commit/215c0a5158f17f515f365fc28a9ff0b367be8fc9 11 Apr 2024. 02:59:58 mns: I noticed that during a install recently. I attempted to try it without rtfm and failed. I just redid everything as normal. I was nervous about improting the pool. 07:37:17 well, having a dataset for each user allows more fine-grained control over them, you can give the user permissions to manage parts of their data set via zfs allow and you can have the individual homes encrypted and only decrypt on login via pam_zfs_key 08:09:26 nimaje: ty for info sounds exciting to mess with. 09:13:18 dch, ping 09:16:29 * dch waves to jbo 09:17:11 dch, absolutely lowest priority item but: did you get to check the poudriere-image cross-compile thingy yesterday? 09:17:24 yeah it worked for me 09:17:42 I didn't pick anything fancy, did you see the backlog around midnight? 09:17:48 so you got an image out of poudriere-image on an x86 host which works on an aarch64 target? 09:17:54 dch, aah no. I must have missed that - apologies. 09:18:05 I don't have cross-machine backlogs :< 09:18:13 no worries, its irc, this is expected :D 10:08:05 rtprio: slowly going up. SMART long test seems (?) stuck at 50%. Now 198 Offline_Uncorrectable ----C- 100 100 000 - 16 (was 8 yesterday). I'm certainly going to use a spare while I return the offending disk. 10:38:55 I have been strugeling with the Elantech touchpad on my thinkpad p53 since I got it, It has never worked on Freebsd but works just fine on Netbsd, Openbsd and linux. Never tried windowds. But on freebsd its just dead just as described in this bug report by someone else: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266742 10:38:55 Today I accidentally held down the middle mouse button below the touchpad and while holding it, the touchpad works and so does the left and right buttons, letting go of middle button and they are all dead. Where do I go from here? 10:40:06 I am on 15.0-current, generic-nodebug kernel. I also have a custom kernel with nvidia passthrough patches that show the exact same behavor. 10:41:43 Should I make a new bug report of this or is it an "easy" fix? 11:11:18 Hello , I have a USB cd reader , but when I use it, I have a permission denied, my device is recognised like /dev/cd0, how to use it please? 11:12:49 dwho, you'll most likely want to setup a devd rule 11:13:35 err... devfs rule 11:14:24 jbo: ok , I have going to document it 11:14:53 I don't have a specific example for a USB optical drive for you but https://man.freebsd.org/cgi/man.cgi?devfs.rules 11:15:25 creek: why would you make a new problem report instead of adding your observations to the existing one? 11:15:33 jbo: thanks 11:17:09 nimaje thats what I was thinking but I cant be sure its the same problem, really, and the hardware is a bit different. But I was thinking of adding to it. 14:49:26 Freebsd 14.3, installed gnome desktop, all looks fine, but cannot log on back after wake from sleep 14:49:32 this frustrates me so much 14:50:00 every version I try to do desktop, it's gonna be something... 14:50:23 desktops are the last things I want to tinker with 15:12:21 Is it the "desktop" locked up? Is it still on the network? 15:25:16 https://imgur.com/a/Kxw0JJE this is the result basically 15:26:56 and I am pretty sure it's two small tweaks away but I just haven't seen it working out of the first try 18:45:23 ivy: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288409 18:58:48 dacav: it already seems to be a setgid executable here as well 19:00:06 O_o wut 19:00:43 -r-xr-sr-x 1 root mail 68016 Jul 14 11:08 /usr/libexec/dma 19:00:48 Oh well, if that was already fixed, then the bug can be closed, I suppose 19:00:53 well, no 19:00:59 that's only part of the problem you're reporting 19:01:24 you're 100% correct that the permissions are too wide and should be fixed 19:01:42 Oh, I see. You're only looking at the binary permissions 19:01:58 yeah 19:02:08 the fact that the binary is already setgid just gives us a clear path forward 19:02:13 Then, according to the discussion we had the other day, probably the binaries should be changed to be owned by some dedicated user, say 'dma' 19:02:16 s/user/group 19:02:25 owned by root:dma 19:02:28 we have a `mailnull` user/group that dma would drop privileges to if run as root 19:04:22 I wonder if it'd be silly to just install the binary setuid/setgid mailnull to begin with, and fix the config permissions 19:12:50 How would a permission patch like this one affect the user's system during upgrade? 19:13:11 e.g. will the upgrade just fix the permission? Or will it query the user to notify them about the change? 19:13:17 s/user/root/ 21:05:55 does anyone know if the the freebsd autofs is supposed to support nested mountpoints? 23:05:31 isn't there some UNIX/GNU/Linux X Window System (X) text editor that lets you edit by column, not just row? I know I used one years ago on Slackware and/or FreeBSD but can't find it... 23:49:47 edit by column? 23:50:22 like writting in Japanese ? 23:50:32 not necessarily 23:50:54 more like for writing/editing your own plaintext charts/tables or also ASCII/ANSI art 23:59:10 ahhh ok