00:34:57 hello I wrote FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest" } in /usr/local/etc/pkg/repos/FreeBSD.conf and it does not find any package 00:35:49 pkg update -f 00:39:52 I get "pkg: No packages available to install matching ..." 00:47:39 it works now. thank you! 01:24:31 my jail is out of control i can't stop it: service jail stop foo 01:24:59 I get Stopping jails: foo: jail_attach: Operation not permitted 01:25:12 I get "Stopping jails: foo: jail_attach: Operation not permitted" what could be the issue? 01:26:29 is this true freedom to jail user? invisible container with full privacy 01:28:39 hopefully nothing to do with 14.0 01:33:05 freebsd-version -u 01:33:09 sorrty 01:37:19 hello I am having the following issue 01:37:38 trying to add swap space and $ sudo gpart create -s GPT vtbd1 01:42:22 https://docs.vultr.com/how-to-add-swap-memory-on-freebsd-14-0 01:44:37 sixpiece: what do you see: $ [ -e /dev/vtbd1 ] && echo 'si' 01:45:02 nothing 01:45:06 lol 01:45:26 just a new line 01:45:42 sorry. you have another device corresponds to vtbd1 in the example 01:46:18 in the example it uses the device 'vtbd1' but your system have another device rather than one you found in the example 01:48:06 would it be vtnet0? 01:48:26 nothing either 01:48:38 sixpiece: i don't know. it's up to what disks you have 01:50:28 ok so what do I do? 02:02:15 sixpiece: 1. determine which dev you want to have swap space 2. try the same command with the device name 02:02:45 sixpiece: feel free to ask 02:03:30 what do you mean by that which dev you want to have swap space? 02:03:49 what is a dev I know I see it but don't know more than that 02:04:27 like dev/sda1 dev/sda2 etc.. on different virtual machines but I don't know more than that really 02:05:46 sixpiece: yes the numbered device name you see under the path /dev represent virtual/physical device. some of them represent storage or disk which you want to have the swap space in 02:06:47 by the way if you are not individually doing it, if this is part of your company work, you can alway consult me professionally. I can help more thoroughly 02:07:10 i want to get paid though. i need a job 02:08:36 if not, that's also ok. i still help no worries 02:09:23 thank you, yes I am also looking for work 02:10:16 sixpiece: easy way could be what device did you get after you phyiscally or virtually attach a new volume? 02:11:56 I have a virtual private cloud 2gb 1 core cpu and 55gb disk space shared 02:12:10 sixpiece: try: $ df -h 02:12:33 https://videotron.eu/pastebin/?36b7d5d5cfd400ee#5vKu6SJ8pYhCJZMzJeEUMaWRJm3Jrny6nS3zxPwwrC14 02:13:47 sixpiece: try: $ uname -a 02:16:02 FreeBSD videotron.eu 14.1-RELEASE FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC amd64 02:17:21 sixpiece: ok try: $ gpart list 02:19:32 https://videotron.eu/pastebin/?90f9b21f4f04a634#AaMZuYrUrDpEaZCX2UToMXQwgWWRDaPU6mz6dYixFSNS 02:21:10 sixpiece: so you only have volume 'vtbd0' already formatted in ufs on latest FreeBSD. 02:21:47 sounds correct 02:22:59 the easiest way to check the presence of your new device, if you attached one, is to ls /dev 02:23:27 sixpiece: in brief reading of the tutorial you showed, it seems it expect you to have an additional volume attach 02:24:26 I am not sure about that tutorial it's really a thread that I posted that motivated this 02:24:35 sixpiece: meaning that when you have a new volume (same kind of your root volume) you will have vtbd1 and you would not have any problem 02:24:43 https://forums.freebsd.org/threads/website-not-working-memory-and-harddisk-consumption-keeps-increasing.95708/#post-679746 02:25:00 it's a lot to read but basically they suggested a swap memory it seems 02:25:44 so is there a solution to this ? like redimensioning the drives? 02:25:53 this is a virtual disk correct? 02:27:02 sixpiece: if you don't want to have additional volume, you can also partition the root volume to spare. you will lose the current system though since it overrides 02:27:44 sixpiece: do you see that your second paste board "2. Name: vtbd0p2" 02:28:23 there is no way I am going to start again fresh to do this this took me years to get here... 02:28:33 sixpiece: that's the filesystem takes up all rest of your volume. 02:29:10 interesting 02:30:18 sixpiece: what was so difficult to take you years for it? 02:30:55 sixpiece: something i can help for partitioning at the reinstall? 02:31:21 getting the sendmail to work, opendkim , etc.. php-fpm etc.. 02:32:48 sixpiece: I see. it seems important. why don't add an extra volume? 02:33:12 https://termbin.com/q64n 02:33:44 ok I will try 02:35:03 can it be hdd? 02:35:07 or it should be nvme? 02:36:12 sixpiece: is this vm? 02:36:24 yes 02:36:49 sixpiece: on cloud? vultr? 02:37:02 yes 02:37:26 sixpiece: do they provide the volume of your choice? 02:37:38 I can add a block volume 02:38:00 sixpiece: yes. once you add, you will see what's new in the commnad: gpart list 02:38:02 yes either hdd or nvme and I choose the size 1$ for 10gb of nvme or 40gb hdd 02:38:22 how much space do I need? 02:39:01 7gb nvme is enough? or I need more? 02:39:32 sixpiece: i remember swap space in linux was something to do with factor of ram size but not sure if this is the case 02:40:36 sixpiece: let's stick to the example you can have less than 7g 02:42:11 sixpiece: did you do: $ swapinfo 02:42:36 sixpiece: my machine has even if i didn't pay attention at the installation 02:43:42 yes four times the ram so it should be like 8 I think according to the manual 02:45:16 sorry double the size 02:45:58 sixpiece: make sure you don't get any out put from command: $ swapinfo 02:46:31 sixpiece: I installed and I didn't even know I have swap space 02:48:05 sixpiece: also my swap space is set 1/10 of root volume. I don't have any idea of how I did so 02:49:20 interesting I am trying to attach it now not sure how exactly 02:50:28 sixpiece: that's your cloud platform. I can't help 02:52:52 interesting understood 03:00:40 the instructions don't work... 03:00:45 I will open a ticket 03:02:10 thank you very much going to sleep soon or now I guess... 03:14:50 sixpiece: you're welcome. 04:06:57 we asked this in a few places without much of a satisfactory response (except we did almost give someone a stroke apparently) but, what does POSIX, or at least freebsd, have to say about this usage of sockets? https://chaos.social/@SoniEx2/113495834154945337 04:26:14 does anyone know if root on '/dev/ttyu' always have permission denied at the use 'jail_attach'?. if so, is this intended? if it's intended, do you know the reason? 04:44:30 Soni, it's kind of a stupid question no offense. To answer your question you should start with reading the source for SYS_socket: https://github.com/freebsd/freebsd-src/blob/main/sys/kern/uipc_syscalls.c#L131 07:54:13 any pf expert? I ask to ask because I am not answered any how. worth to ask to ask before ask here 07:57:18 oh i figured though. thanks. 07:58:42 I have another question though 08:05:35 It does not need to be an expert since I'm an idiot 08:10:27 ;p 08:17:58 I figured out. thanks 11:02:57 zijjgfs: so it is UB to use an fd after it's allocated but before it's initialized? 13:46:45 Soni: depends on who's defining said behavior 13:49:04 for freebsd? i do not see any such conditions mentioned in `man 2 socket`. so it's behavior that has been left undefined (implicitly) 13:50:33 but you're free to look at the implementation of kern_socket(), and if you find it deficient in how you think the scenario ought to be handled, you're welcome to create a patch for it. 14:28:54 say, do I need to do anything to secure the root account in a jail? 14:32:01 I can see that we start out with no password, but SSH won't permit root login, `su` users need to be in `wheel` which utility accounts shouldn't be, and presumably there's no ttys running getty 14:32:23 is this actually secure by default or do I need to set a root password for every jail? 14:50:33 I suppose I could simply assume the worst and write a tool that yells at me if I have a jail without a root password 15:04:13 zip: you should set a password or disable password login (i.e., set the password hash to '*'). i recommend the latter as you never need to log in as root on a jail, you use jexec. i don't think this is secure by default or really intentional at all, it just happens to not open an obvious remote vulnerability due to sshd default configuration 15:14:12 i used cloned_interfaces in netif service to create taps for each vm. if i add some more taps can i simply service netif reload to get them initialized? and if so, will that drop existing connections? 15:58:23 hello 15:58:50 my freebsd vm cannot connect to the internet after a reboot 16:00:11 ping 8.8.8.8 works but name does not resolve for some reason 16:00:39 koolkat332: cat /etc/resolv.conf 16:02:00 koolkat332: The resolvconf service might be tripping you up 16:02:19 nameserver 8.8.8.8 16:03:02 ivy: i figured as much. i guess I'll do that before I take the template snapshot 16:03:18 koolkat332: Ok, does `host freebsd.org 8.8.8.8` work? 16:04:00 honestly I'm half wondering if I should just install void on this machien and run all my services in podman 16:04:14 connection timed out no servers could be reached i removed the stuff that was commented out in 16:04:25 resolv.conf 16:04:36 and deleted the 8.8.8.8 entry but can readd it 16:04:39 but also half this project is just trying to get myself to stop being quiiiite such a docker-brained admin 16:05:58 I also added a block storage in the hope of getting a swap 16:06:53 everything is failed 16:10:10 permission denied on a ping 16:12:22 it was ipfw 16:18:01 btw no we can't add more tap interfaces to cloned_interfaces and just restart netif service and routing service. that sucks 16:18:11 wish we could dynamically reconfigure that without having to reboot 16:18:38 really? 16:21:19 cloned_interfaces="bridge0" 16:21:59 ifconfig tap0 create 16:22:07 ifconfig_bridge0="addm tap0 up" 16:31:50 not what i said 16:38:36 I thought bsdinstall cli was changed but it was the differnce between ttys 17:02:24 can you exploit the kernel via careful manipulation of file descriptor initialization in multithreading? 20:34:51 If l00py comes back perhaps someone could mention that after "service netif restart" they also need "service routing restart" too. That's likely what they are missing, no default gateway route. 21:02:43 FreeBSD specific question: I am trying kevent's for first time to monitor when a file changes. I get the event working flawlessly when the file is modified by a program but if I modify it manually in vim, the events are not triggered. Any idea or hint on why? https://bpa.st/5N5Q 21:07:04 uskerine: have you saved the changes you make with vim? 21:08:18 satanist of course 21:10:38 uskerine: vim may be unlinking the file and re-creating it rather than modifying it in place, i can't remember off hand if it does that by default 21:11:29 same if I change it using dd 21:11:37 it does not work 21:11:40 this is extremely weird 21:12:15 vim juggles temp files, no? 21:12:55 dd however should be rawdogging it 21:13:40 there muyst be something else 21:13:51 I also tried a basic C program and same 21:14:00 but it works flawlesly in the original main program 21:14:31 /* REGISTER THE KQUEUE FILE DESCRIPTOR WITH THE XT EVENT LOOP */ 21:14:31 XtAppAddInput(appContext, kq, (XtPointer)XtInputReadMask, eventfile_callback, (XtPointer)client_data); 21:15:01 could it be that I am registering the callback in the Xt loop 21:17:34 have you tried the sample out of the manpage? 21:19:24 I need to register it using XtAppAddInput, is a X11/Xt app, if I do it normally it will block the X11 app 21:25:30 I think I am missing something relevant here 21:25:52 https://stackoverflow.com/questions/71655596/select-works-but-kqueue-doesnt-when-waiting-on-x11-connection 21:27:23 where can I learn more about kevents related to file changes? 21:33:08 in the manpage: kqueue(2) 21:33:34 search for EVFILT_VNODE 21:45:40 ok my fault --partially-- 21:45:44 the plain C program works 21:45:53 VIM no, because it seems to change the inode (I check with stat) 21:47:07 same for dd 21:47:14 the tests I did with dd and C were not properly done 21:47:17 and vim changes the inode 21:47:26 good, gravity remains in place