00:00:22 Did I say zfs import? My bad. I meant "zpool import". Sorry about that. 00:01:12 rwp: it seems unlikely filesystem corruption would cause CAM/AHCI errors, no? 00:01:45 unixwitch, True. Agreed. 00:02:05 and no need for zfs import here since their root filesystem (the one with the problem) is UFS 00:02:29 They might want access to the data now from the live boot disk. I would. I could then copy things off from it. 00:02:40 The only things I've done with it recently were copy lots of bits off of the zfs mirror to my Mac… 00:03:04 …and before that, upgrade stuff, maybe to 14.0. 00:03:27 I don't think / has anything on it that I haven't copied to it from my main machine. 00:03:47 Instead of buying a new disk, singular, perhaps it is time to buy two disks and then you could mirror them, avoiding this failure problem in the future. :-) 00:04:07 Like, my FreeBSD-specific fish history isn't _that_ valuable. 00:04:37 You said you had root on UFS and the ZFS array was data that was elsewhere. If the root disk is dead then all of / the OS part is gone. And the ZFS array would have whatever you put on it. 00:05:20 Right. My giant pool full of backups is OK. I assume. 00:05:24 an alternative would be, if you already have a mirrored zfs pool, you could just put the root on there rather than using a separate UFS root 00:05:58 It depends upon how those disks are partitioned, and if the hardware boots UEFI or not. 00:06:36 I have a question about the base vi/nvi. From vi(1): Ctrl+W "Switch to the next lower screen in the window, ...". What does this mean exactly? 00:06:40 It's a newfangled ProLiant MicroServer. The new boot screen takes like three minutes to totally boot. It's…intimidating for a non-sysadmin like me. 00:06:53 I would buy 2x Samsung EVO SSDs of the smallest size you can get, probably 250GB now, for US$50 each and mirror them. 00:07:04 base vi does not support split editing, correct? 00:07:08 topcat001, Amazingly vi has split windows now. 00:07:28 oh really! :split does not work though 00:07:39 what about :hsplit or :vsplit 00:08:11 You are talking with an Emacs user here so I will have to read the vi man page now. 00:08:57 well, NORMALLY I'd just boot up my FreeBSD machine and try the base vi, but… 00:09:21 amazingly vsplit works! However I cannot find doc for it 00:09:40 hsplit does not work 00:10:08 The man page says "vs[plit] [+cmd] [file] Edit a different file by opening a new screen to the right of the current screen. 00:11:21 I know real vim had only one kind of split for a while. 00:11:47 I found it now. I was searching for "split" :) 00:11:53 thanks 00:12:36 Come to the Dark Emacs side. We have cookies! :-) 00:12:51 oh I have used emacs for a long time too :D 00:14:09 adiabatic, You only have this one FreeBSD system? (Shock! Horror! Nausea!) Create a VM on your other system or something! 00:14:58 I used to have a Digital Ocean droplet running FreeBSD but then I realized I wasn't using anything fancy about it so I dropped back to a normal boring webhost 00:16:01 The vi man page is a little confusing because to me it does not seem to use consistent terminology dealing with split screens, or windows, or buffers, or whatever. Makes it hard to search just for commands that deal with multiple screens. Have to read each and every word, determine what it is applying to, decide it is not multiple buffers, and move on to the next item. 00:16:10 now ctrl-w works as expected. It is quite interesting that only vertical is supported, and I am glad splits are at all possible 00:16:36 adiabatic, Not even on your own desktop or laptop? No need for a cloud host. 00:17:01 I got Debian working on my old MacBook Pro but I realized I spent more time updating it than using it 00:17:08 so I gave it away 00:17:11 topcat001, It's emacs envy. Can vi emulate emacs yet? Emacs has been able to emulate vi for decades. :-) 00:17:30 Although now that you mention it, my webhost provides chroot jails from FreeBSD… 00:18:09 `uname` says `FreeBSD`. 00:18:19 well rwp technically emacs has many more features :) 00:18:58 I actually searched for screen as well but since it has many hits I missed the vsplit. Another pair of eyes helps :) 00:19:01 Curious what "uname -mr" says there. 00:19:46 Me too! 00:19:48 13.2-RELEASE-p4 amd64 00:20:13 So mostly up to date. Pretty recent. Close enough when every reboot annoys your paying customer base. 00:20:38 I troll vi/vim users but I used vi for a long time in the past. I never picked up vim and vim has different keys for many things over vi and I trip over the differences. 00:21:15 Which actually encouraged me to use vim less, because it just wasn't the same and I tripped over things with it. And the colors they chose by default were abhorrent! 00:21:27 * rwp gotta run IRL TTYL 00:30:17 I certainly have emacs envy for it's extensibility, however I couldn't get used to its key chording sadly. 00:33:35 Here, $EDITOR is /usr/bin/vim, my go-to terminal editor is Helix, but my main editor is 21st-century Emacs (Visual Studio Code). 00:36:05 Except Electron based editors would be "eight gigabytes and constantly swapping" :) 00:38:00 That's one of the reasons why I call it "21st-century Emacs" — it's highly extensible bloatware. 01:04:40 except it consumes 260MB here and does not swap anything 01:06:44 When I put a new hard drive in my laptop why didn't freebsd or gpart recognize it ? I only saw it when I turned it into an mbr ? 01:07:03 Camcontrol saw it 01:15:29 topcat001, On 14 here, both "split" & "vsplit" work to split the buffer in 2 directions 01:18:33 jb1277976: new disks don't usually come with a partition table, you have to create one yourself (e.g. with gpart). freebsd should still recognise it though, e.g. in 'camcontrol devlist' 01:18:46 (if freebsd didn't recognise it, you wouldn't be able to create the partition table...) 01:20:03 topcat001, s/buffer/window/ # rwp, hold your horsey there. I am myself not consistent with the terminology 01:23:11 unixwitch thanks. i used diskinfo -v and installed lsblk i got it. love this os 01:32:20 to test i attached ada1 which is my m.2 sata ssd i just installed in to my pool and boom it reslived really quick lol zfs dosen't play 01:32:39 s/reslived/resilvered/ 01:40:51 How do I list dependencies for a port? 01:44:01 CrtxReavr, Run "make pretty-print-run-depends-list"; s/run/build/ as needed 01:49:43 parv, there any way to make that print packages names, instead? 01:50:12 I need a port with no package, but I want to install packages for the dependencies. 01:53:38 There is some "make" variable to install packages instead of compiling ports that I do not remember 01:56:10 tmux pkgconf libvent 01:56:13 whoops 02:02:01 CrtxReavr, See /usr/ports/Mk/bsd.port.mk; search for USE_PACKAGE_DEPENDS & USE_PACKAGE_DEPENDS_ONLY 02:04:11 rwp: good news — $50 Samsung 870 EVOs are 500 GB, not half that 02:09:29 CrtxReavr, As for printing depend-package list, shove the output of ""make pretty-print-run-depends-list" to "pkg search": make pretty-print-run-depends-list | sed -E 's/^[^"]+"//; s/" to run.$//; s/ /\n/g' | sort | xargs -n 1 pkg search 04:01:34 hi! bit of a funny question, but... is ng_tty(4) nonfunctional since the "new" TTY layer in 8.0? 04:02:20 and if not, how can you install the NETGRAPHDISC line discipline on a tty? tty(4) says that TIOCSETD is nonfunctional since 8.0 04:31:28 Hi all! I have a FreeBSD 14.0 CURRENT host that I installed a few weeks ago. I am still doing some tests on it - I noticed tyhat I cannot install packages via `pkg` anymore, even ones that I know exist. What happened? 04:31:59 jail question.. I set one up as a vnet jail using the directions in the handbook, and it can't reach the host - and only the host. it can ping other devices on my LAN and the internet in general. 04:34:07 deepthaw: does the host have an address on the bridge? 04:34:56 it looks like the handbook instructions are missing a step - they add IP settings to the bridge in rc.conf, but forget to apply them right now 04:36:29 oddline: would that be bridge0? looks like the same as re0 (192.168.1.66) 04:36:41 oddly - I just restarted wireguard on the jail and now it can ping the host. :\ 04:37:20 ah, you've got more complicated networking happening inside the jail then? 04:38:44 Yeah. The jail runs a wireguard vpn. I'm trying to mount an NFS share that's on the host. 04:39:18 i'll say this - i'm learning a lot about networking 04:40:00 ok - I'm a little rusty on my freebsd networking, so take this with a grain of salt, but I think you shouldn't have an address set on both the bridge _and_ the bridge's member interface (which you say is re0 for you?) 04:40:23 maybe having it set on the member too is harmless and does nothing, idk 05:24:15 I think I have all my jail networking figured out even if a lot more interfaces have the same IP address than I'd like. 05:24:36 And I neded up realizing I can't mount nfs within the jail anyways so I swapped to nullfs 05:28:12 deepthaw: the IP address should only be on the bridge interface, not the member interface. having it on both will probably cause strange problems 05:28:37 ifconfig_re0="up"; ifconfig_bridge0="inet 1.2.3.4/24 addm re0 up" 05:31:09 If I don't have it on the epair20a interface, it's very inconsistent as to whether the jail can talk to it. But since I'm not using NFS anymore, it's not relevant so I'll make sure both interfaces don't have the ip. 05:32:29 the problem must be elsewhere, because that definitely isn't required for jail<>host communication 05:35:05 Yeah - I suspect it's a pretty delicate setup already. It's a vnet jail running wireguard, which was copied from a different physical server. 05:35:20 but now that it works i won't touch it and will just revisit it later 06:12:16 hi 06:12:31 for some reason i was in the wrong room 06:13:04 i’m unable to boot x isn’t starting and i’m getting all kinds of odd errors 06:13:34 how can i get to a prompt so i can see what is going on? 06:14:51 You need gpu drivers 06:15:11 Also, ctrl+alt+F2 06:15:19 should get you to tty2 06:15:32 There you have terminalismus secondus 10:09:38 Greetings. I want to dualboot Windows 10 and FreeBSD 14.0-RELEASE. I have installed Windows 10 first. I booted FreeBSD with my USB stick, I went into the "LIVE CD", but I was not able to extend the EFI partition(Created by Windows's installer). 10:10:09 How can I extend it? I have ~600GB left. 10:16:26 pr-asadi: why you want to enlarge the EFI partition? Windows normally makes a 100MB EFI partition, the FreeBSD EFI loader is <1MB. 10:22:44 elirco: I know it is enough. I just want to know why I could not, besides having ~600GB space left. 10:33:30 pr-asadi: maybe there is no way to change that. it is quite common that the Windows installer decides what is "best for you" :) 10:34:25 elirco: Hmm. I am gonna remove Windows 10 and install FreeBSD 14.0-RELEASE first. Then I will see it is about Windows or not. 10:35:11 afaik FreeBSD creates a smaller EFI partiton if you install it first. 10:35:21 the real question is: what are you trying to achieve? 10:35:53 To know why it did not let me. gpart(1) says "No space left on device" 10:36:01 But I have ~600GB space left. 10:36:19 I can shrink it, but cannot extend it. 10:36:59 most probably there already is a partition right after the EFI partition (i.e. a Windows partition). 10:37:15 There is. 10:37:26 In that case you have to move the other partition first and create space for extending the EFI partition. 10:38:05 it is possible, but a more risky operation then just enlarging a partition at the end. 10:38:05 Is it the same in all OSes? I remember I could extend my partition on Antix Linux. 10:38:25 you cannot extend a partition if the space after it is already allocated to a different partition 10:38:40 it requires shrinking AND moving the other partition 10:39:01 Knoppix should be able to to this easily 10:39:08 with a GUI even 10:39:48 I'd take a backup though before moving NTFS partitions. That always can go wrong, you never know. 10:40:24 s/Knoppix/GParted liuve CD/ 10:40:27 if it is a fresh install it would probably be faster to reinstall Windows 10:40:33 Remilia: elirco: Well, I cannot enlarge/extend a partion when there is another partition after it? It's the same on all OSes? 10:40:43 pr-asadi: obviously it is? 10:41:01 how would you be able to without shrinking and moving the partition right after? 10:41:37 there is a whole lot of metadata in there and partitions were not even designed to be moved 10:41:42 There are Tools like "GParted" that allow you to resize it anyhow, but GParted internally splits that "resize" into "Resize Windows partition, move Windows partition, enlarge EFI partition. 10:41:44 Well. I did not know this. Or perhaps I had just forgotten it. Thank you Remilia, elicro. 10:42:23 I won't resize it, I just wanted to know why I could not. But I found out by your help. 10:42:28 elicro: ^ 10:42:45 pr-asadi: MBR and GPT partitions must to be continuous and they contain metadata in OS/filesystem-specific locations 10:43:03 * elirco shows thumbs up to pr-asadi 10:43:18 even if the OS tells you there is 600 GB of free space, that free space is inside that partition 10:44:02 Remilia: MBR and GPT... -> Understood. Thanks for the information. 10:44:44 you often can quickly and easily shrink a parittion, which will give you space *after* that partition, but to expand a preceding one you have to move *every single block* of that shrunk partition over to the end 10:44:59 some tools know to skip unused blocks 10:45:37 but in your case, with a fresh install of Windows, it would most likely be faster to reinstall and specify partitions manually 10:45:54 while GPArted can do that moving of *every single block*, it may take hours to complete and if you are unlucky you need to repair your Windows installation afterwards. 10:46:20 so +1 for fresh install 10:46:23 (note that Windows needs a recovery partition) 10:46:45 elirco: OH yes, that's why I could extend a partition on Antix Linux, GParted moved those blocks. 10:47:04 It took a few hours though. 10:47:27 pr-asadi: that explains a lot 10:47:42 * pr-asadi agrees 10:56:13 elirco: I have also another question. I want to make my home separate. I should make it `/usr/home`, or just `/home`? 10:58:48 see the man page for hier 10:59:20 and also ls -l / 10:59:39 namely /home is a symbolic link 10:59:48 I know /home is a symbolic link. 10:59:52 I had used FreeBSD. 11:00:06 do you plan to replace /usr/home with a symbolic link then? 11:00:19 But, I want to make it separate. First time, I created "/", "/var", "/tmp", "/usr". My home was under "/usr". 11:00:50 I do not want it to be under "/usr" this time. Should I make a partition with "/usr/home" mountpoint or "/home" mountpoint? 11:01:03 so you want a separate partition for home, right? 11:01:07 Yes. 11:01:14 which filesystem? 11:01:20 UFS 11:01:34 will / also be UFS? 11:01:38 or ZFS? 11:01:42 either you use /home, deleting the existing symlink and /usr/home and creating /usr/home symlink 11:02:01 or you do not do anything, choosing separate home partition in the guided partitioner in bsdinstall 11:02:12 elirco: All partitions are UFS> 11:02:39 unless that option was removed (sysinstall had that) 11:02:45 Remilia: I have not seen "separate home partition" in the installer yet. 11:03:07 see my line above, starting with 'either' 11:03:08 I'd use the FreeBSD installer with "manual partitioning" create 2 partiton with labels "root" and "home" and mount points "/" and "/usr/home" 11:03:54 huh that is almost like single root 11:04:01 Guided partitioning used to require the whole disk, is that still the case? 11:04:37 I have not tried it on systems with existing partitions 11:04:49 elirco: Well. My partions would be "/", "/tmp", "/var", "/usr", "/usr/home" then. Is it correct? All of them UFS. 11:05:01 elirco: Yes. AFAIK it needs the whole disk. 11:05:32 I just do not understand the desire to mount at /home when you can mount at /usr/home and leave the /home symlink intact 11:06:49 Remilia: The Traditional Split File System Partitions are "/", "/var", "/tmp", "/usr". Home is under /usr by default 11:07:21 I want to make it a separate partition. I just want to know, should I make the separate partition's mountpoint either "/home", or "/usr/home". 11:07:34 as of 14.0, the installer will use /home rather than using /usr/home and symlinking to /home 11:07:44 [11:01:41] either you use /home, deleting the existing symlink and /usr/home and creating /usr/home symlink 11:07:49 or you use /usr/home and do nothing 11:07:58 up to you 11:08:09 +1 for /usr/home 11:08:21 you can also mount it at /boot/usr/var/log/tmp/home 11:08:26 and create two symlinks 11:08:55 or at /123/456/789/this/is/not/really/home 11:09:11 might be fun too 11:09:27 the enemy will never know where to find it 11:10:19 putting home directories in /usr was a bit of a hack from back in the days when /usr would often be a separate, larger partition 11:10:45 from the changelog for 14.0: 11:10:49 > The pw(8) and bsdinstall(8) programs now create home directories for users in /home by default rather than /usr/home. The default symbolic link for /home, referencing /usr/home, is no longer created. bbb2d2ce4220 11:11:29 you can still use either, but /home imo makes more sense, especially if you're making it a separate partition 11:11:34 Remilia: It seems I could not explain well. I did not mean that. I mean, by default if you do not make a separate home partition, the home will be /usr/home and /home would be a symlink to /usr/home. I just want to make it a separate partition. I just need to know which mountpoint should I give to my separate home partition. 11:11:52 pr-asadi: the point people are trying to make is that doing it either way will work just fine 11:12:14 oddline: Thanks for the information you shared. 11:12:18 I suggest mounting it directly at /home. others have suggested the other way (mount at /usr/home and keep the symlink). 11:12:46 oddline: the point people are... -> Understood. 11:13:08 elirco: Remilia: oddline: Thank you all 11:14:01 you can mount it anywhere, symlinks are for backwards compatibility and /home or /usr/home are locations typically checked for home directories 11:14:28 actual user home path is obtained from the password database 11:16:46 Hi 11:16:58 i'm planning to upgrade to 14 11:17:10 Remilia: Understood. Thank you for your time. 11:17:11 does the upgrade process automatically create a boot env ? 11:17:25 or i need to create it manually ? 11:17:40 freebsd-update will create boot environments automatically for each step 11:18:22 ok, so if anything goes wrong, i can revert 11:18:56 are boot environments enabled as default? 11:19:02 i never used them 11:19:09 but I receive the following 11:19:17 elirco: try "bectl list" 11:19:51 root@elfreebsdo1:~ # bectl list 11:19:52 libbe_init("") failed. 11:20:21 elirco, do you use zfs ? 11:20:29 as rootfs ? 11:20:39 yes 11:20:56 then i don't know, i don't remember enabling anything to get it work 11:21:20 hmmm... 11:21:47 i will check on my other PC if the bahvior is the same 11:22:08 https://wiki.freebsd.org/BootEnvironments 11:22:10 Title: BootEnvironments - FreeBSD Wiki 11:23:32 it seems that you use a non standard dataset layout 11:23:38 that bectl cannot manage 11:23:38 'libbe_init("") failed' sounds like a userland issue 11:23:45 oh that is also possible 11:23:50 elirco: try "bectl check" 11:26:01 root@elfreebsdo1:~ # bectl check 11:26:01 root@elfreebsdo1:~ # echo $? 11:26:02 255 11:27:53 my other laptop has the same problem 11:28:05 both are dual boot with Win and FBSD 11:28:47 here is my partition layout: https://bsd.to/YwFp 11:28:48 Title: dpaste/YwFp (Plain Text) 11:30:04 dataset layout ? 11:30:06 freebsd version ? 11:30:42 how did you dualboot ? which bootloader are you using ? 11:32:00 root@elfreebsdo1:~ # zpool list 11:32:00 NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT 11:32:01 root 816G 56.2G 760G - - 3% 6% 1.00x ONLINE - 11:32:11 root@elfreebsdo1:~ # freebsd-version -kru 11:32:12 14.0-RELEASE-p3 11:32:12 14.0-RELEASE-p3 11:32:13 14.0-RELEASE-p3 11:32:32 Bootloader is loader1.efi 11:33:05 root@elfreebsdo1:~ # ls -lh /boot/efi/EFI/freebsd/loader.efi 11:33:06 -rwxr-xr-x 1 root wheel 645K Nov 21 17:29 /boot/efi/EFI/freebsd/loader.efi 11:33:06 root@elfreebsdo1:~ #freebsd 11:33:57 elirco: for boot environments the GPT layout does not matter at all 11:34:02 what does zfs list show? 11:34:17 they use ZFS datasets 11:34:44 tsoome: https://bsd.to/gZLM 11:34:45 Title: dpaste/gZLM (Plain Text) 11:36:13 what's the output of `mount`? 11:37:13 output of mount: https://bsd.to/fg8A 11:37:14 Title: dpaste/fg8A (Plain Text) 11:38:37 zpool get bootfs ? 11:39:03 root@elfreebsdo1:~ # zpool get bootfs 11:39:04 NAME PROPERTY VALUE SOURCE 11:39:04 root bootfs - default 11:39:34 and zpool list ? 11:40:58 root@elfreebsdo1:~ # zpool list 11:40:59 NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT 11:40:59 root 816G 56.2G 760G - - 3% 6% 1.00x ONLINE - 11:43:08 btw my other dual boot laptop has the same issue. so it may be the way I am setting up dual boot. (despite the fact i do it pretty straight forward) 11:43:10 well, the beadm/bectl is expecting dataset layout /ROOT/bename - where bename is custom name ("default" is used by installer) and poolname is also custom ("zroot" by installer). 11:43:57 how are those datasets created? shouldn't the installer do this? 11:44:05 then bootfs zpool property is set to "/ROOT/bename" -- this property is used by boot loader 11:44:11 the installer *does* this 11:44:17 installer should, yes 11:44:20 when using guided partitioning 11:44:31 is it a problem i chose "root" and not "zroot" as name for my pool? 11:44:39 no 11:44:47 but if you upgraded from before BEs were a thing 11:45:03 the problem is that you do not have ROOT dataset for root file system 11:45:19 you appear to have OS files stored directly to pool root 11:45:21 can guided partitioning do dual boot now? I use "manual partitioning" since ever since that has been the only way for dual boot to work. 11:46:29 tsoome: i set up the device the way I do it since UEFI exists. so obviously due to not being aware of boot environments caused me doing it wrong. 11:47:27 what you need to do, is boot from alternate media, import your root pool and use alternate mountpoint; then zfs create -p root/ROOT/default and copy your OS data to root/ROOT/default 11:47:53 then you can use bectl to activate that be and create new one etc. 11:48:44 "copy you OS data"... how would be the best way to do it? tarcp? 11:48:52 and wouln't I have all files twice then? 11:49:18 once you are happy with setup, you can clean up the pool root 11:49:51 you can use `zfs send` 11:50:21 it will be much faster than tar 11:50:45 what is zfs send? can i add additional hard drive with that? 11:50:53 and what if i have 128gb ssd 11:51:08 can i only make redundant raid with another 128gb one? 11:51:21 I will check that out in the evening (CET). now it is time for a walk in the sun at outside.com/realworld soon. :) 11:51:25 or can it be 200gb hdd? with72 gb wasted? 11:52:01 the os itself does not take much 11:52:31 i have 128gb with most space used 11:52:55 can i transfer everything to 200gb hdd for example? 11:53:01 I guess you have around 100GB of other data there;) 11:53:06 sure 11:54:30 > now it is time for a walk in the sun ← I agree, I should go for a walk and buy tea in the process 11:54:55 you absolutely can transfer everything to new disk - even with simple mirror setup - and once you detach smaller disk from mirror, you can resize partition on larger disk and grow your pool 11:57:36 cooooool 11:58:10 once your pool is grown, you can not attach smaller disk any more, of course 12:00:05 but what about several smaller disks? 12:00:22 like 200gb one disk and 128+80 gb another? 12:00:43 mirror does map blocks 1-1 12:01:41 therefore, for redundancy, 200GB disk needs another 200GB disk 12:02:20 that's only one thing which is sad 12:10:14 % zpool list 12:10:14 NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT 12:10:16 zroot 103G 97.1G 5.87G - - 64% 94% 1.00x ONLINE - 12:10:20 hmmmm 12:10:42 i need some sort of zroot1 now? 12:18:06 V-T60: to use a 200GB disk + 120 + 80 GB disks, would would need to stripe (or concat) the 120+80GB disks and then mirror on top of the stripe, which is sometimes called raid0+1. this is almost never useful or desirable (except for unusual edge cases like this) so for simplicity, zfs doesn't allow it, you can only stripe over a set of mirrors (raid10) 12:18:51 you could probably hack it up with gconcat if you *really* wanted... 12:26:26 Hi! I'm replacing a faulty disk in my raidz pool. I had four disks in it (now three, since one is now "offline") 12:26:37 one thing confuses me a bit though 12:27:11 zpool status zroot shows me ada{0..3}p4 12:27:17 why the p4? 12:28:02 how do i mirror my 120gb from zero? 12:28:30 unixwitch: 128gb + my 200gb unused HDD 12:29:07 (as i understand, 128gb part of it for the begining) 12:29:28 sjk: The default layout installs efi on p1, freebsd-boot on p2, freebsd-swap on p3 and freebsd-zfs on p4 12:29:40 beginning* 12:30:13 than i wanna "grow" it somehow as i understand what was proposed before 12:30:36 "resize partition on larger disk and grow your pool" 12:31:24 I'm in the process of upgrading from 13.2 to 14.0 (RELEASE). I had Poudriere build the new packages, but when running pkg upgrade there was an error after [170/469] packages were fetched. Now I can' 12:31:24 fxttr: ah, so I'd have to recreate that layout on my replacement disk before running zpool replace? 12:32:01 e.g. gpart backup ada0 | gpart restore ada3 12:32:26 Now I can't finish the install as I get "pkg: An error occured while fetching package" 12:32:45 and "DBG(1)[87844]> release an advisory lock on a database' 12:33:21 unixwitch: gstripe would work 12:33:28 How do I go about releasing the advisory lock? 12:33:28 as an underlying device 12:33:50 but that would kill bootability in case the larger drive goes out 12:35:51 sjk: aside from gpart backup/restore you will likely want to copy the other partitions; the naming suggests you have GPT which means you want to at least copy the ESP over 12:36:21 (but you do not need to copy swap contents of course) 12:38:27 Remilia: ah yes indeed, I do want to be able to boot from it etc. What's the proper way to go about this? dd? 12:38:56 sjk: you can dd the ESP itself after creating the layoyut, sure 12:38:59 layout* 12:39:35 but I am curious as to why you have *4* EFI partitions 12:39:52 5 seemed a bit much 12:40:07 what 12:40:11 sorry 12:40:18 I mean, typically you would have 3 12:40:23 I am not sure either 12:40:46 ESP, ZFS pool, swap 12:40:56 do you have an old install with a separate bootpool? 12:41:35 gpart show -> efi, freebsd-boot, freebsd-swap ond freebsd-zfs 12:41:45 Schamschula: 'release an advisory lock' is a debug message, you can ignore it if I recall right 12:41:55 oh 12:41:57 not that old, hmm, maybe three years? 12:42:27 oh wait, actually not even that, more like 1-2 years old 12:42:54 I am guessing you boot in EFI mode but during installation you chose support for legacy BIOS? 12:42:56 that explains it 12:43:14 not sure! 12:43:16 is it bad? 12:43:20 no 12:43:32 phew :) 12:43:59 it can sometimes cause your system to catch fire (this is a lie, it cannot) 12:44:09 sjk: does `zpool list` show bootpool OR is there bootpool in `zpool import` output? 12:44:16 unixwitch: :D 12:44:47 Remilia: zpool list only shows zroot 12:44:58 zpool import says there are no pools available to import 12:45:10 then you are probably fine 12:45:43 so I'm guessing I'd want to copy efi and freebsd-boot over to the new drive? 12:46:13 probably a good idea 12:46:17 dd if=/dev/ada0p{0,1} of=/dev/ada3p{0,1}? 12:46:28 dd does not work like that 12:46:46 you have to invoke it twice 12:46:55 aye 12:47:21 honestly I am conflicted about freebsd-boot 12:47:31 what is its size? 12:47:46 is freebsd-boot a UFS filesystem or something else? (if so, it might make sense to use gmirror... but i can't remember how this works since i haven't had a separate boot partition anywhere for ages) 12:48:03 it is not ufs 12:48:10 It's 512K 12:48:18 oh 12:48:23 yeah that is legacy bootcode 12:48:24 efi 260M, boot 512K, swap 2G and zfs 5.5T 12:48:34 for non-EFI booting 12:48:47 you can dd it over 12:48:51 I set this up through the default freebsd installer 12:49:06 yes, the BIOS+UEFI mode 12:49:06 so, it's there in case the machine does not support efi booting? 12:49:11 yep 12:49:17 ah ah 12:49:23 though in *that* case you also need to install bootcode 12:49:43 pmbr + gptzfsboot 12:49:57 Remilia: Thanks. So the issue seems to be one of fetching. I get a 403 error, even though the file is there. It looks like there is a rule in niginx.conf that matches! 12:50:43 sjk: check the man page for gptzfsboot for instructions if you want to install bootcode and protective mbr 12:51:18 Schamschula: does it happen for pkg itself? 12:51:33 No it didn't 12:51:47 so you were able to bootstrap pkg? 12:52:03 Yes 12:52:14 403 is intriguing but I do not use nginx haha 12:53:14 I tend to deny a number of files re. script kiddies et al. 12:54:17 for poudriere I use h2o with this: https://paste.ee/p/HOULv 12:54:19 Title: Paste.ee - View paste HOULv 12:55:14 and it works fine except I never solved the pkg bootstrap issue 12:55:23 so I just manually upgrade pkg first 12:57:29 I tend to deny a number of files re. script kiddies et al. ← I do not see a reason to block anything within poudriere because it is all static files with nothing of interest 12:59:16 That was never the plan. I found the rule. It was missing a leading ^ 13:02:36 Thanks guys! 13:07:27 hi there, how can I specify set of flavors for specific port in poudriere ? 13:07:48 list them in your build list 13:08:25 Remilia, Could you please show me a syntax sample 13:08:35 I am sorry I do not understand 13:08:36 graphics/pecl-imagick@php81 13:08:50 list the origin twice with different flavours 13:09:04 this will build only graphics/pecl-imagick for php 8.1 13:09:07 yes 13:09:14 i need this for 8.2 and 8.0 too 13:09:23 what prevents you from adding graphics/pecl-imagick@php80 and graphics/pecl-imagick@php82 to your list? 13:09:38 just separately list them ? 13:09:40 I am sorry I do not understand, are you using a text preprocessor? 13:09:51 because flavours are *different* packages 13:10:17 Now it's clear 13:10:18 thanks 13:10:49 I thought it require some special syntax something like: graphics/pecl-imagick[php80,php81] ... 13:11:14 a single poudriere build job will only build one package 13:11:37 it is impossible to build at once for several php versions, as you are linking against different headers etc. 13:12:00 Yes, but I didn't understood the methodology for adding multiple flavor packages 13:12:26 thanks 13:14:23 nerozero: there is one special feature for flavours, you can use @all to build all of them 13:15:21 Remilia, Thank you! Can it be the case that I have tried with all caps @ALL and it didn't worked ... 13:15:42 flavours are always lowercase; uppercase is options 13:16:03 yah, my bad, thanks for make this clear to me! 13:19:07 nerozero: poudriere% bulk lunatear devel/php-composer@all \\ Building lang/php81 | php81-8.1.26 \\ Building lang/php80 | php80-8.0.30 \\ Building lang/php83 | php83-8.3.0 13:19:24 works fine 13:19:48 Thank you 14:05:57 is there a command to test if all system files have the correct expected hashsum? 14:06:18 something like `dpkg --verify` on debian 14:10:37 Uh ‘freebsd-update ids` 14:10:44 iirc 14:11:42 any openvpn users here? 15:09:28 https://forums.freebsd.org/threads/freebsd-openvpn-low-upload-speed.91505/ 17:35:10 https://forums.freebsd.org/threads/freebsd-openvpn-low-upload-speed.91505/ 17:35:12 Title: FreeBSD OpenVPN low upload speed | The FreeBSD Forums 18:18:30 Hello! 18:18:51 evening 18:33:56 so if i don’t have ports installed how do i add it since portsnap has been removed 18:34:18 is it safe to use pkg just to install git? 18:35:14 have you tried bsdinstall ? 18:36:07 Im spitballing here as im learning at a helluva speed catching up 18:36:07 what’s that? the installer? i didn’t install with the system because it seems like when i did that last time it messed stuff up 18:37:14 aybe just stick with pkg for now. i have to say the documentation for freebsd is horrible lots of stuff in the handbook is wrong 18:37:24 maybe* 18:38:14 Wat 18:38:14 Im messing around with updating a port. other thing you can do, if you have git installed just grab from github 18:38:38 like with this it tells you to use pkg to install git to install ports but is that safe since now you use have to update git with pkg instead of using a port tree? 18:39:16 cutler that’s my catch 22 i don’t have git 18:39:19 Pkg is the default package manager. If you can install something using pkg and don't need to compile it with some flags for some reason use the pkg 18:39:28 It's the choice between using binary packages compiled by freebsd maintainers or compiling everything from source. 18:39:36 It also installs from "checked/accepted ports" 18:39:50 Something like git im guessing would be Ok. 18:40:18 i did read somewhere that if you used both ports and pkg it can screw things up as you have two different upstreams 18:40:52 i guess i’ll just stick with pkg 18:40:53 ports tree you compile it yourself but not everything there necessarily works properly. If it has a pkg version then it works properly but you might want to remove or add something at compile time, then you do ports tree and fix it 18:41:05 Yes 18:41:12 ok 18:43:10 But I agree about it being confusing for beginners about the ports, portstree and pkg (since it includes ports as well) 18:43:48 its been a bit confusing. 18:44:18 but can honestly say I have leraned more about the internal in FreeBSD than the last 4 years in Linux 18:44:27 *Learned 18:47:51 I meant only the ports/pkg/ports tree part is 18:48:02 Otherwise it is good documentation 18:48:26 Jip 18:49:10 I mean, look at pacman and AUR, very clearly documented that you should prefer pacman, AUR is risky but if you have no other choice use it. 18:49:29 agree. 18:49:30 And AUR isn't mixed into pacman, 18:49:31 What runs moused by default, since the system default is moused_enable="NO"? 18:50:00 Ditto that question, I am starting to getting annoyed seeing a mouse in my FreeBSD tty 18:50:07 cutler, well, it's a lot more mature and less convoluded. 18:51:04 cutler, plus. . . it's an OS project. . . whereas linux is a kernel from here, a libc from there, a compiler from somewhere else, an init system from yet another place, ad nausium. 18:51:32 It was a welcome realisation when after a just 2 or 3 days I was actually annoyed with Ubuntu that is running my Fiber Laser. 18:52:22 Next step will be Freecad and some recompiling and my CNC will move to FreeBSD as well 18:53:19 I doubt I will get the Fiber Lazer guys from Lightburn to make a FreeBSD build 18:53:31 but the other machines will move - soon 18:54:14 If the src is available and sane with a Makefile, it might build and work easily. 18:54:34 And even if not, you might be surpised at how much help you can find in getting it working/ported. 18:54:49 There's also the linux subsystem. 18:54:52 It is a closed source product. 18:55:37 https://github.com/LightBurnSoftware they have a repo tho 18:55:39 Title: LightBurn Software · GitHub 18:56:16 With the update to 14.0 I had to leave MySQL 5.7 behind. Unfortunately, an update that I had done twice before, failed this time. I've got duplicate .ibd files. In order to get rid of them I would first have to start mysqld, which, of course it won't. 18:58:58 Why are you rushing to 14.x? 19:00:16 Rushing? I don't have time during the semester so I thought I'd tackle it over winter break. 19:01:20 This is my home server, however I also need to know what I'll run into when upgrading the production server on campus. 19:01:44 Dumb question, why did you have to leave MySQL 5.7 behind ? 19:02:17 Apologies for my ignorance, Im really not up to date with whats happening on the MySQL front 19:02:25 14.0 doesn't provide openssl 1.x.x., hence the package doesn't exist. 19:02:49 Cool. Im following 19:04:59 I get error like [InnoDB] Tablespace ID: 86 = ['mysql/time_zone.ibd', 'sys/mysql/time_zone.ibd'] 19:05:27 Have the svnup servers been disabled?: https://bpa.st/EBLA 19:05:28 Title: View paste EBLA 19:11:01 cutler: Isn't 5.7 past its end of life? 19:12:05 Yes and no. There have been recent upstream updates. 19:17:12 but openssl-1 is EOL. so mysql lagging 19:24:35 IIRC, you can still get support for it by paying for an extended contract. Maybe the MySQL people consider that support enough? 19:30:29 How do I make the /usr/src dir git-able? 19:30:32 I've got git installed. 19:30:39 I've also got the 13.2-R src tree from the install media. 19:31:12 if you git clone .... it is gittable 19:31:36 You want to turn your /usr/src into an entire git? Or you want to git clone to it? 19:32:18 I just want the full 13.2-R security branch src there. 19:32:35 Just a thougt, if you not going to make changes or need source control, just download master as a zip and extract ? hell of a lot easier than mucking about with git 19:34:54 'git pull' wouuld be easy AF if it worked. 19:35:39 so im having weird networking issues and i think i found the issue what is l_magic? it seems like it’s a vlan device which i dont have or use 19:35:56 because neither wifi or ethernet work 19:36:11 ethernwt was working but stopped as well as wifi 19:36:41 so it seems like freebsd thinks im using a virtual adapter or some type or vpn 19:36:47 if it is not on your disk yet git clone will get it and setup what you need from there you checkout the branch you need 19:38:19 CrtxReavr, Zyxer, The console mouse needs separate disables for the USB event system. moused_enable="NO" plus moused_ums0_enable="NO" moused_ums1_enable="NO" for the USB event driven system. 19:39:31 The reason for both ums0 and ums1 is I have a USB mouse plus a Trackpoint keyboard mouse. You would need ums2 as well if your system had a third. 19:39:32 Thank you! I will fix after I do some grocery shopping 19:40:11 rwp, I just didn't need a mouse point on my mostly-headless server console. 19:40:36 s/point/pointer 19:42:10 CrtxReavr, Although I sometimes do use my desktop vt console the mouse pointer there was just a distraction and I didn't need it running there either. 19:42:10 Wifi be unstable on FreeBSD 19:42:43 s/\ on\ FreeBSD// 19:42:53 Schamschula, A time honored strategy is to put legacy services into a legacy jail and continue running it in the jail sandboxed workspace. 19:43:43 You could put your MySQL server into a jail and side step the current problem for a while. 19:43:59 rwp, I just set moused_nondefault_enable="NO" & moused_enable="NO" 19:44:19 moused_nondefault_enable? /me goes to look that one up. 19:44:23 moused_nondefault_enable="YES" is the default. 19:45:01 It's on a USB KVM. . . which might explain something. 19:45:30 Anyways, once the OS is installed and it's on the network. . . 19:46:18 rwp: that thought had crossed my mind. 19:47:57 I'm a bit of a noob in terms of jails. Currently I'm only using them for Poudriere. 19:48:12 Schamschula, It's actually nice having that type of setup when it comes to testing upgrades because one makes a new jail of the newer OS version and then tries it and if it doesn't work it doesn't affect the previous jail, them all being independent. 19:49:02 The one limitation is that the jail should not be newer than the hosting OS because of course system calls from older compiles are known on newer kernels but a newer system may introduce new system calls that the older kernel will not have implemented. 19:50:00 Meaning that though I may want to test out a service on the newest everything I can't do that until the host system is also running it, so I might as well have a newest everything testing machine then. 19:50:13 But for sandboxing up older legacy services it's perfect! 20:07:16 I'm trying to set up a jail by following https://docs.freebsd.org/en/books/handbook/jails/ 20:07:17 Title: Chapter 17. Jails and Containers | FreeBSD Documentation Portal 20:08:32 CrtxReavr, (Zyxer) I did not know about moused_nondefault_enable previously. I just tested having only moused_nondefault_enable="NO" and it is a one-stop-shop for disabling the console mouse here. I converted to it. THANKS! :-) 20:08:37 However, when I run freebsd-update -b /usr/local/jails/containers/classic/ fetch install it wants to install 14.0 RELEASE. I want to kee 13.2 RELEASE in the jail. 20:08:45 s/kee/keep/ 20:10:58 I would fetch the base.txz of the version I wanted to keep and then use it. You might already have it on your previous 13.2R system in /usr/freebsd-dist/base.txz 20:12:06 OK. That's what I installed. I just want to make sure that when a new patch level comes out that I can update to it. 20:12:41 Looking at the handbook section 17.4.1 now and I see that command but I don't think that should jump forward to a new major release number but just along the patch line. Therefore I think it must already be a 14.0R version already. 20:13:42 My base OS is at 14.0 RELEASE, but I need the jail to remain at 13.2. 20:14:34 Note that you can use "freebsd-version -j jailnamehere" to determine the userland (-u) of that jail. And of course the kernel running (-r) is the host kernel. And nothing installed (-k). 20:15:48 First I need to figure out how to add the .conf file to /etc/jail.conf.d 20:16:33 My hosting system is 13.2R so let me create a 12.4R as a test and try that command on it because as I said I didn't think it should try to jump major releases but just along the patch level. 20:29:08 Schamschula, I reproduce exactly your reported behavior here too. It upgraded the jail to the host release. 20:54:38 When I try to start the jail I get: ifconfig: interface em0 does not exist 20:54:40 Schamschula, D'Oh! I forgot about the freebsd-update --currently-running option! That's the missing piece. Use: freebsd-update --currently-running 12.4-RELEASE -b /jails/testclient26 fetch 20:55:18 Are you trying to run a vnet jail or a non-vnet jail? (I like vnet jails so much that I pretty much always use them.) 20:55:21 I also saw that in the man page! I guess you don't need to specify the version. 20:56:11 A regular thick jail. 20:57:47 Jails can be thick or thin or otherwise and they can be vnet or otherwise. vnet jails have their own network stack entirely and get their own IP address. 20:58:18 I'll assume you are starting a non-vnet jail given the response. Which means that everything will share the hosts IP address space. 20:59:03 Which means that it is important to set sendmail_enable="NONE" in the jail's /etc/rc.conf file or the jail will try to start sendmail on port 25, which is probably already busy, and things like that. 20:59:07 Either would be fine. 21:02:10 I figure out the problem: I was using the wrong interface name. It should have been bge0 21:32:26 rwp: I got that and it doesn't help 21:32:35 The mouse nondefault thing 21:39:35 Schamschula, I have been working through an example here. I needed to do that anyway. Today was just motivation to do it. 21:40:05 You might have completely figured out everything on your end already. If so then awesome! If not I put together this self-contained example. https://bsd.to/sNkT/raw 21:40:06 Title: sNkT 21:41:21 This is using a vnet jail. I think it makes things simpler. All of the setup and teardown is in the jail.conf file for this example. Because I like to be able to step through the steps in order to understand things. 21:44:18 Zyxer, I removed all other moused_* lines from my /etc/rc.conf file, added moused_nondefault_enable="NO" as suggested, rebooted, and no moused on my vt consoles. Worked for me. 21:44:46 Nope! Not completely there yet. However, the jail is up and running, just nothing installed. I'm off chasing another issue: Mediawiki is giving me 500 errors. However, since it's just for personal use it's running under sqlite3. However, it's not a php vs. sqlite issue, as that's working for my own code. 21:46:49 I see in my paste that I cut off the -p9 and it says 12.4-RELEASE-p but it should say 12.4-RELEASE-p9, honest! I had forgotten that --currently-running was needed before. 21:48:08 Hopefully that example will help jumpstart things. I am just hoping it will be helpful. I am going to be afk for a while. BBIAB. 22:38:43 full of help 22:43:46 One step closer: Mediawiki is back up, so are my notes! (somehow php82-pdo_sqlite didn't get installed).