07:48:55 <kerneldove> why can't we set vfs.zfs.arc.max unless we also set vfs.zfs.arc.min?
15:28:53 <Ltning> What's the correct way to pass cputype flags to buildworld/buildkernel? If I interpret things correctly, by default it only builds with "amd64 sse2 sse mmx" instruction sets?
16:02:57 <rtprio> Ltning: man make.conf
16:27:11 <Ltning> Yea I am tryinng to comprehend that, with mixed success
16:56:45 <nerozero> Is it safe to `rm -rf /usr/ports/distfiles/*`
17:03:23 <Ltning> Yes
17:03:30 <sbr> Depends what you are worried about, its safe to rm -rf /usr/ports entirely, just check it out agai
17:04:22 <nerozero> i'm using poudriere, and it is a poudriere build machine
17:16:10 <mosaid> Hi
17:16:31 <mosaid> noone answered me.. why?
17:20:57 <rwp> mosaid, Your question was a little vague and fuzzy.  And probably no one at the time knew how to answer.  Could you install using partitions and upgrade from 14, I think you asked?
17:21:54 <rwp> Most of the enthusiastic people are using zfs these days and zfs has efficient datasets for as many partitions as desired.
17:22:42 <rwp> I suggest installing a default install of FreeBSD using zfs, you said you wanted to install 14, and then yes you can upgrade from 14 to 15 to experience the process.  It will all work okay.
17:23:06 <rwp> Of course if you don't want zfs you can also install without and the same is also true.  The upgrade will work okay.
17:25:33 <mosaid> what? never said that
17:27:03 <voy4g3r2> you asked to have your usr tmp var etc.. in seperate partitions and install on a usb.. correct?
17:27:14 <voy4g3r2> datasets are analogous to partitions
17:27:29 <voy4g3r2> zfs pool, make multiple datasets that mount to the specific "partitions"
17:27:41 <mosaid> I am talking about I have 13.5 fully working system I will split every dir into partition.. then entirely overwrite partition / with fresh 14 and upgrade my packages will this work?
17:28:02 <mosaid> voy4g3r2: yes
17:28:35 <mosaid> I can't use zfs now
17:28:48 <voy4g3r2> the minute you play with partitions.. data goes bye bye
17:28:57 <voy4g3r2> especially if you are NOT using zfs
17:29:01 <mosaid> I talking about easy solution
17:29:38 <boru> Can you back the data up, wipe and restore what you need/want?
17:29:44 <mosaid> voy4g3r2: why "bye bye"?
17:30:03 <voy4g3r2> becuase you are manipulating the parititions
17:30:20 <mosaid> I will not mount these partitions.. only "/"
17:30:27 <mosaid> wait
17:30:29 <rwp> As I said, your original question was very vague and fuzzy. :-)
17:30:35 <voy4g3r2> maybe i just do not fully understand your question. You have a 13.5 operational system, with a set of partitions. You then want to "change" that layout to a new set of partitions. Then upgrade to 14?
17:30:51 <voy4g3r2> i am just being more verbose than rwp. :)
17:31:01 <mosaid> I think I need to download base.zip and those stuff manually extract them in /
17:31:09 <mosaid> now usb
17:31:32 <mosaid> I read that somewhere but I am asking about more info
17:32:02 <rwp> I suggest not creating partitions for every directory.  I don't think that is good.  I do not understand why you would want to do that in this case where things are already working without.
17:32:03 <voy4g3r2> i understand you are asking for more data, not info, because i am not sure what your goal is. It appears you are trying to solve an issue, that i personally do not fully understand.
17:32:26 <rwp> I also do not understand.
17:32:37 <nesta> I too do not understand
17:32:54 <boru> kldload understanding.ko
17:33:16 <nesta> version mismatch :P
17:33:22 <mosaid> voy4g3r2: forgot changing now I have every dir separated like var, usr,tmp,home partition already
17:33:29 <robert12> You put that in GENERIC, its not optional.
17:33:37 <mosaid> and have "/"
17:33:41 <voy4g3r2> well yes
17:33:49 <voy4g3r2> so you have a partition layout already, and you are happy with it?
17:34:02 <voy4g3r2> that is on version 13.5, correct?
17:34:05 <mosaid> yes
17:34:07 <voy4g3r2> cool
17:34:10 <boru> So, you just want to run bsdinstall from a USB stick or what?
17:34:17 <mosaid> yes
17:34:22 <voy4g3r2> and now your next step is.. upgrading to 14.x?
17:34:26 <mosaid> sure
17:34:37 <voy4g3r2> ah.. so your friend will be freebsd-update :)
17:34:45 <mosaid> oh no
17:34:47 <robert12> why such an unusual setup
17:34:55 <mosaid> headache
17:34:59 <voy4g3r2> mosaid: may i ask why?
17:35:24 <voy4g3r2> well upgrades, from major to major version, could be a headache.. but manageable with some prep work
17:35:46 <mosaid> upgrading version on ufs is ultimately hard
17:35:55 <boru> ...
17:36:03 <voy4g3r2> nah
17:36:06 <mosaid> so want easy way on ufs
17:36:09 <voy4g3r2> different than zfs, yes, but hard nah
17:36:11 <rwp> What makes it hard to upgrade on UFS?  I have upgraded UPS systems from 13 to 14 okay.
17:36:44 <voy4g3r2> mosaid: have you backed up your current system yet? that should be step one
17:36:52 <voy4g3r2> just in case something goes boom.
17:37:15 <rwp> +1 for ensuring a good backup before upgrading.  Ensures victory.
17:37:32 <voy4g3r2> after that is all nice and complete, we can then make sure you are on the latest version 13.x
17:37:41 <voy4g3r2> that is possible with a nice and awesome freebsd-update fetch
17:37:45 <voy4g3r2> freebsd-update instaall
17:37:55 <voy4g3r2> spelled right ofcourse
17:38:06 <voy4g3r2> then do a nice and sweet: pkg update && pkg upgrade
17:38:17 <voy4g3r2> to be even safer, do another backup after those are done
17:38:32 <voy4g3r2> then once those steps are done
17:38:34 <mosaid> ok, but I want to explain something.. I have a huge number of different bsd and centos + ubuntu, and some old ports things like that
17:38:47 <voy4g3r2> all good
17:38:51 <mosaid> need to upgrading to work on 14
17:39:00 <rwp> My favorite way is "env PAGER=cat freebsd-update fetch install" (env works regardless of shell being csh, sh, or other).  Then "shutdown -r now"  Then ""env PAGER=cat freebsd-update install" to finish.  (First updates the kernel.  Second updates the userland.)
17:39:23 <mosaid> I upgraded from 13.2 to 13.5 was headache and hard to get those stuff work agian
17:39:24 <voy4g3r2> or the "sexy" way rwp is doing it
17:39:40 <voy4g3r2> are those other operating systems in bhyves?
17:39:44 <mosaid> I am scared from major upgrad now
17:39:49 <voy4g3r2> understandable
17:40:04 <voy4g3r2> we are not suggesting anything, that i would not do myself, to you
17:40:17 <mosaid> voy4g3r2: they are linux emulation need their emulation packages
17:40:17 <voy4g3r2> that would just be wrong and not cool.
17:40:23 <rwp> How are those other systmes, bsd+centos+ubuntu, installed and running?
17:40:35 <mosaid> linux emulation packages
17:40:46 <voy4g3r2> with a simple www.freshports.org lookup
17:40:54 <voy4g3r2> that will say if they are around.. i would not worry about that too much honestly
17:41:17 <mosaid> I looked but I am scard more from my port collection
17:42:02 <rwp> You are using the https://docs.freebsd.org/en/books/handbook/linuxemu/ way of linux binary compatibility?
17:42:14 <mosaid> they are some discontinued and removed ports I built and upgraded important for daily use
17:42:23 <mosaid> for rox-filer
17:42:28 <mosaid> and some other stuff
17:42:54 <mosaid> rwp: yes for linux-c7 and ubuntu debstrop I spilled wrong
17:43:48 <mosaid> I am talking about ports..c ould I run 13 port with updating code on 14?
17:43:56 <mosaid> *without
17:44:07 <voy4g3r2> i am not sure on that
17:44:08 <rwp> The newer kernel should support older programs+libraries okay.  Older libraries are sometimes moved into compatibility packages.
17:44:47 <mosaid> theirs compatibility packages on freebsd?
17:44:54 <rwp> If an older library got removed it can be restored for older program compatibility.
17:45:05 <voy4g3r2> and could also make jails and stuff
17:45:37 <rwp> Yes.  But I don't recall the names of the various ones as I don't need them for me.  But yes.  And voy4g3r2's suggestion of keeping a jail for the older programs is best.
17:46:02 <voy4g3r2> so i think that issue is now addressed for you mosaid
17:46:13 <voy4g3r2> anything else concerning you?
17:46:22 <rwp> If you have specific older programs you an jail them running them out of a jail area.  Then upgrade the host.  Keep the jail without upgrading it.
17:46:27 <mosaid> yeah got a keywords for searching now
17:46:50 <voy4g3r2> and once all that stuff is backed up
17:46:56 <voy4g3r2> freebsd-update -r 14.0-RELEASE upgrade
17:46:57 <rwp> Running older programs in a jail on an upgraded host is a time tested technique.
17:46:58 <voy4g3r2> freebsd-udpate install
17:47:10 <mosaid> rwp: I am making sure bsd is best day after day
17:47:12 * voy4g3r2 has a few jails on 14 even though on 15
17:47:57 <rwp> voy4g3r2, (I think you can only -r 14.4-RELEASE now.  Not sure though.  Can you -r to 14.0 now?  Honest question.)
17:47:58 <mosaid> but does zfs have roll-back option?
17:48:10 <kerneldove> why can't we set vfs.zfs.arc.max unless we also set vfs.zfs.arc.min?
17:48:12 <mosaid> If something goes wrong
17:48:38 <rwp> The freebsd-update program keeps files for "freebsd-update rollback".  ZFS has Boot Environments separately for doing a different type of rollback.
17:49:19 <rwp> Since you are using UFS you would have available for you "freebsd-update rollback" if something fails.
17:49:26 <voy4g3r2> rwp: you could be right :) i will go with yours
17:49:39 <rwp> And you would have your backup that you could use to restore from too in the case of disaster recovery.
17:52:20 <voy4g3r2> once you do dhte -r 14.4-RELEASE upgrade do a freebsd-update install
17:52:26 <voy4g3r2> reboot that bad boy..
17:52:33 <voy4g3r2> then do another freebsd-update instal
17:52:40 <voy4g3r2> then you can do a happy dance.. you will be on 14.4 :)
17:52:50 <voy4g3r2> cheers and happiness all around
17:53:21 <mosaid> thanks :)
17:54:02 <rwp> Please make sure you have a good backup first for safety to ensure success!  Happy upgrading! :-)
17:54:42 <voy4g3r2> yes, you do not do that you will be pulling a Kenny Loggins "danger zone" type moment
17:54:48 <voy4g3r2> but with kenny loggins anything is possible
17:55:12 <voy4g3r2> or you could throw in some chuck norris.. but that is a little extreme for my dry and sarcastic humor in this moment.
17:56:10 <mosaid> I want to ask question for port maintainers.. will bsd continue to support linux-c7? I can't upgrade to rl9 cuz it doesn't support 32bit and older programs, libs
17:56:42 <mosaid> I am using linux-c7 for running old xmms and sum othe stuff really need it they use gtk1.2
17:56:49 <mosaid> *some
17:57:10 <voy4g3r2> that is a whole other ball of wax, that is out of my depth
17:57:35 <mosaid> I am using ubuntu for last updated and modern apps
17:58:26 <mosaid> also asking if bsd will drop support for gtk2
17:59:23 <rwp> I don't really know about it but linux-c7 is just a metaport for things on the old CentOS 7 onto FreeBSD.  But I don't know.  It's a good #freebsd-ports question though.
17:59:58 <mosaid> yeah I  know it's centos7 and thanks for channel link
18:01:34 <voy4g3r2> wow they have not touched that program in 17 years
18:01:49 <mosaid> but it's really nice
18:01:53 <voy4g3r2> i made a jellyfin media server jail and then just use their web interface to play stuff
18:02:01 <voy4g3r2> or my iphone with some apps to stream to my home stereo
18:02:06 <mosaid> win amp for *nix
18:02:18 <voy4g3r2> yup yup.. kicks the llama's ass unix style
18:02:27 <mosaid> heh XD
18:03:05 <mosaid> I used before on debian..
18:04:54 <mosaid> still supported on arch.. I don't know why bsd stop maintain many ports fast :(
18:05:17 <voy4g3r2> 17 years is not fast
18:05:22 <voy4g3r2> https://vermaden.wordpress.com/
18:05:33 <voy4g3r2> there are some real good articles and tips here.. for linux emulation and other various stuff
18:05:51 <voy4g3r2> old ports and packaging them is a technical debt liability
18:06:06 <voy4g3r2> but i must go pack for my yearly holiday.. good luck with the upgrade.
18:06:06 <mosaid> https://www.freshports.org/multimedia/xmms
18:06:22 <mosaid> 2018!?
18:06:36 <mosaid> it could be built easily nowdays
18:07:11 <mosaid> I built something from 2012 and worked bigger than xmms
18:07:21 <mosaid> should try
18:07:47 <mosaid> voy4g3r2:thank you
18:08:24 <mosaid> I know vermaden from atari-forums
18:08:51 <mosaid> never think that he is a bsd user
19:36:12 <spork_css> Free tip, need a Dell service tag but want to get it within the OS: kenv | grep system | grep serial
19:49:32 <rwp> Good tip.  I keep forgetting that kenv exists.
20:15:32 <ek> Ran into PAM issues using pkgbase to upgrade from 15.0-RELEASE to 15.1-RELEASE.
20:16:01 <mason> ek: Did you open a bug? That'd be super useful.
20:16:05 <ek> Running a "pkg install -f FreeBSD-pam-15.1" immediately after the initial "pkg upgrade" seems to fix the issue. Just an FYI.
20:16:17 <ek> mason: I haven't yet because I'm not sure what's causing it.
20:16:29 <mason> ek: Oh, oh, there was something about that in the release notes. Half a sec.
20:16:53 <ek> It's only happened to 2 of the last 8 upgrades. If I run into it again, I'll document more. But, something wipes out the /etc/pam.d directory and leaves the system basically useless.
20:17:10 <mason> ek: https://www.freebsd.org/releases/15.1R/relnotes/#userland-packages
20:17:30 <ek> mason: Yeah. I saw OpenPAM had changed and required the *-minimal-* (which these systems did/do).
20:17:32 <mason> ek: So, if you didn't have FreeBSD-set-minimal or FreeBSD-set-minimal-jail then you'd need to add the package manually.
20:17:42 <mason> Ah, then this is definitely worth a bug.
20:17:58 <ek> So, I'm stumped as to why only some choke and some do not. They're all 15.0-R going to 15.1-R.
20:18:13 <mason> ek: A bug. If you report it you make the world a better place. :)
20:18:40 <ek> mason: Yeah. It's... different, for sure. I can likely roll back one of my VM's that had this issue and see what I can dig up.
20:18:56 <mason> ek: Oh, nice, yeah, a bug with a reliable reproducer is fantastic.
20:19:04 <ek> I don't like opening bugs with just "iTz BrOkEn!" I like to at least provide SOME info.
20:19:42 <mason> ek: Sure. Maybe list what packages you started with before the upgrade. But your report here was pretty clear.
20:20:13 <ek> Here's the kicker, though. Even after manually forcing FreeBSD-pam-15.1 re-install, when I ran a pkg upgrade after the reboot, it wanted to remove that package along with a bunch of others (ztsd, ssh libs, etc...)
20:20:22 <ek> Which I had to remove and then reinstall again manually.
20:20:24 <ek> Very strange.
20:20:25 <mason> hrmph
20:20:40 <mason> Alright, errands, but thanks in advance if you do open a bug!
20:21:04 <ek> Hope the errands go well!
20:21:36 <mason> ty, should be uneventful
22:44:05 <voy4g3r2> mosaid: how did the upgrade go?
23:21:42 <nesta> I too would like to know how the upgrade went :)