why can't we set vfs.zfs.arc.max unless we also set vfs.zfs.arc.min?

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?

Ltning: man make.conf

Yea I am tryinng to comprehend that, with mixed success

Is it safe to `rm -rf /usr/ports/distfiles/*`

Yes

Depends what you are worried about, its safe to rm -rf /usr/ports entirely, just check it out agai

i'm using poudriere, and it is a poudriere build machine

Hi

noone answered me.. why?

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?

Most of the enthusiastic people are using zfs these days and zfs has efficient datasets for as many partitions as desired.

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.

Of course if you don't want zfs you can also install without and the same is also true. The upgrade will work okay.

what? never said that

you asked to have your usr tmp var etc.. in seperate partitions and install on a usb.. correct?

datasets are analogous to partitions

zfs pool, make multiple datasets that mount to the specific "partitions"

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?

voy4g3r2: yes

I can't use zfs now

the minute you play with partitions.. data goes bye bye

especially if you are NOT using zfs

I talking about easy solution

Can you back the data up, wipe and restore what you need/want?

voy4g3r2: why "bye bye"?

becuase you are manipulating the parititions

I will not mount these partitions.. only "/"

wait

As I said, your original question was very vague and fuzzy. :-)

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?

i am just being more verbose than rwp. :)

I think I need to download base.zip and those stuff manually extract them in /

now usb

I read that somewhere but I am asking about more info

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.

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.

I also do not understand.

I too do not understand

kldload understanding.ko

version mismatch :P

voy4g3r2: forgot changing now I have every dir separated like var, usr,tmp,home partition already

You put that in GENERIC, its not optional.

and have "/"

well yes

so you have a partition layout already, and you are happy with it?

that is on version 13.5, correct?

yes

cool

So, you just want to run bsdinstall from a USB stick or what?

yes

and now your next step is.. upgrading to 14.x?

sure

ah.. so your friend will be freebsd-update :)

oh no

why such an unusual setup

headache

mosaid: may i ask why?

well upgrades, from major to major version, could be a headache.. but manageable with some prep work

upgrading version on ufs is ultimately hard

...

nah

so want easy way on ufs

different than zfs, yes, but hard nah

What makes it hard to upgrade on UFS? I have upgraded UPS systems from 13 to 14 okay.

mosaid: have you backed up your current system yet? that should be step one

just in case something goes boom.

+1 for ensuring a good backup before upgrading. Ensures victory.

after that is all nice and complete, we can then make sure you are on the latest version 13.x

that is possible with a nice and awesome freebsd-update fetch

freebsd-update instaall

spelled right ofcourse

then do a nice and sweet: pkg update && pkg upgrade

to be even safer, do another backup after those are done

then once those steps are done

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

all good

need to upgrading to work on 14

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.)

I upgraded from 13.2 to 13.5 was headache and hard to get those stuff work agian

or the "sexy" way rwp is doing it

are those other operating systems in bhyves?

I am scared from major upgrad now

understandable

we are not suggesting anything, that i would not do myself, to you

voy4g3r2: they are linux emulation need their emulation packages

that would just be wrong and not cool.

How are those other systmes, bsd+centos+ubuntu, installed and running?

linux emulation packages

with a simple www.freshports.org lookup

that will say if they are around.. i would not worry about that too much honestly

I looked but I am scard more from my port collection

You are using the docs.freebsd.org/en/books/handbook/linuxemu way of linux binary compatibility?

they are some discontinued and removed ports I built and upgraded important for daily use

for rox-filer

and some other stuff

rwp: yes for linux-c7 and ubuntu debstrop I spilled wrong

I am talking about ports..c ould I run 13 port with updating code on 14?

*without

i am not sure on that

The newer kernel should support older programs+libraries okay. Older libraries are sometimes moved into compatibility packages.

theirs compatibility packages on freebsd?

If an older library got removed it can be restored for older program compatibility.

and could also make jails and stuff

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.

so i think that issue is now addressed for you mosaid

anything else concerning you?

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.

yeah got a keywords for searching now

and once all that stuff is backed up

freebsd-update -r 14.0-RELEASE upgrade

Running older programs in a jail on an upgraded host is a time tested technique.

freebsd-udpate install

rwp: I am making sure bsd is best day after day

voy4g3r2, (I think you can only -r 14.4-RELEASE now. Not sure though. Can you -r to 14.0 now? Honest question.)

but does zfs have roll-back option?

why can't we set vfs.zfs.arc.max unless we also set vfs.zfs.arc.min?

If something goes wrong

The freebsd-update program keeps files for "freebsd-update rollback". ZFS has Boot Environments separately for doing a different type of rollback.

Since you are using UFS you would have available for you "freebsd-update rollback" if something fails.

rwp: you could be right :) i will go with yours

And you would have your backup that you could use to restore from too in the case of disaster recovery.

once you do dhte -r 14.4-RELEASE upgrade do a freebsd-update install

reboot that bad boy..

then do another freebsd-update instal

then you can do a happy dance.. you will be on 14.4 :)

cheers and happiness all around

thanks :)

Please make sure you have a good backup first for safety to ensure success! Happy upgrading! :-)

yes, you do not do that you will be pulling a Kenny Loggins "danger zone" type moment

but with kenny loggins anything is possible

or you could throw in some chuck norris.. but that is a little extreme for my dry and sarcastic humor in this moment.

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

I am using linux-c7 for running old xmms and sum othe stuff really need it they use gtk1.2

*some

that is a whole other ball of wax, that is out of my depth

I am using ubuntu for last updated and modern apps

also asking if bsd will drop support for gtk2

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.

yeah I know it's centos7 and thanks for channel link

wow they have not touched that program in 17 years

but it's really nice

i made a jellyfin media server jail and then just use their web interface to play stuff

or my iphone with some apps to stream to my home stereo

win amp for *nix

yup yup.. kicks the llama's ass unix style

heh XD

I used before on debian..

still supported on arch.. I don't know why bsd stop maintain many ports fast :(

17 years is not fast

there are some real good articles and tips here.. for linux emulation and other various stuff

old ports and packaging them is a technical debt liability

but i must go pack for my yearly holiday.. good luck with the upgrade.

2018!?

it could be built easily nowdays

I built something from 2012 and worked bigger than xmms

should try

voy4g3r2:thank you

I know vermaden from atari-forums

never think that he is a bsd user

Free tip, need a Dell service tag but want to get it within the OS: kenv | grep system | grep serial

Good tip. I keep forgetting that kenv exists.

Ran into PAM issues using pkgbase to upgrade from 15.0-RELEASE to 15.1-RELEASE.

ek: Did you open a bug? That'd be super useful.

Running a "pkg install -f FreeBSD-pam-15.1" immediately after the initial "pkg upgrade" seems to fix the issue. Just an FYI.

mason: I haven't yet because I'm not sure what's causing it.

ek: Oh, oh, there was something about that in the release notes. Half a sec.

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.

ek: freebsd.org/releases/15.1R/relnotes/#userland-packages

mason: Yeah. I saw OpenPAM had changed and required the *-minimal-* (which these systems did/do).

ek: So, if you didn't have FreeBSD-set-minimal or FreeBSD-set-minimal-jail then you'd need to add the package manually.

Ah, then this is definitely worth a bug.

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.

ek: A bug. If you report it you make the world a better place. :)

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.

ek: Oh, nice, yeah, a bug with a reliable reproducer is fantastic.

I don't like opening bugs with just "iTz BrOkEn!" I like to at least provide SOME info.

ek: Sure. Maybe list what packages you started with before the upgrade. But your report here was pretty clear.

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...)

Which I had to remove and then reinstall again manually.

Very strange.

hrmph

Alright, errands, but thanks in advance if you do open a bug!

Hope the errands go well!

ty, should be uneventful

mosaid: how did the upgrade go?

I too would like to know how the upgrade went :)