I've got some #ifdef OpenBSD code calling ioctl(DIOCGDINFO) and I'm trying to find the freebsd equivalent, but apparently it was removed in 2015?

I found lists.freebsd.org/pipermail/freebsd-current/2015-January/054144.html which says yes it was removed, and linked to lists.freebsd.org/pipermail/freebsd-current/2015-January/053960.html which is just a bug report about packages breaking because it was removed.

I followed the thread forward and got "503 backend failed" errors, also when trying to lead the month index.

hello I trying to install freebsd on an apu2d4 over serial console, I got output on the serial console until lo0 link state changed to UP dpaste.com/CMT67R8RR any idea what it could be why I dont get the installer prompt..

Hi, I would like to ask. I have installed KDE, I use Intel GPU, which obviously is properly set up (glxinfo says Intel(R) HD Graphics), and despite that KDE is very laggy, for example when dragging windows or scrolling in a web browser. My question is whether this is normal, simply not so good GPU utilization on FreeBSD? I'm fine if there is worse

GPU utilization on FreeBSD, I just need to know it. Thanks.

It's not normal

Heck! Now I have tried to install gnome and it works well, and not only that - Full HD videos on Youtube, via Firefox, are slighly occasionally lagging on Debian GNome, but not lagging in FreeBSD!!! (I'm not KDE user anyway, so don't care anymore)

fixed my bizarre corrupted directory

which I talked about few months here

*ago

boot into single user.. then fsck -y 3 times

I want just to ask why my ufs partitions corrupt on freebsd all the time

before someone say bad drive I tried 100% new one after a month same thing happends files disappers

I need fsck to fix it

Is there anyway to stop corruption from first place

do you need ufs?

is it bad?

I guess about everyone is on zfs

i was on zfs, been on ufs for a while

what's your experience with it.. good or bad?

kinda good if we don't talk about unsafe shutdowns causing problems sometimes

i still have zfs mirror for my hard drives though

I just heard before if I use freebsd I should go for zfs or ufs.

I choose ufs.. bec zfs is more complicated

yes, UFS is simpler than ZFS but it seems more rock solid

because of how it works i guess

bus as I see ntfs is more stable on "unsafe shutdowns" than ufs

sometimes I experience power outages here

I moved to zfs years ago, and never had any issues with my drives whatsoever.

"If you have at least 2 GB of RAM and any interest in snapshots, data integrity, or painless system updates, go with ZFS. If you are running a minimal system on tight hardware, UFS will serve you well without complaint."

I want this

look like I need to get a bigger drive and go zfs soon

zfs may require more ram but can be used with low ram via tuning. why bigger drive? i don't think zfs requires that

yeah I know but my system drive is already ufs

so for the switch to zfs

I need new system install and new drive to separate every part into it's own partition

right

nxjoseph: but I can't now is there anyway to stop this from happening little bit at least

i don't know, how does it happen?

prevent the power outages then... UPS?

unsafe shutdowns can cause issues

maybe enable some UFS properties like journaling, soft updates?

(if not enabled)

yes UPS might be a way but some people cant afford it like me

i guess they also require maintenance every X months?

don't think so.. the U stands for Uninterruptable

is it safe to enable those on working root partition

i am not sure but it's better performed on read-only mounted root i guess?

or not mounted at all ,like from usb drive

The tunefs utility cannot

be run on an active file system. To change an active file system, it

must be downgraded to read-only or unmounted.

man tunefs

yes I will do that sure.. but after I reboot into normal mode will cause problem

i don't think so

you can right now check which are enabled or not

tunefs -p / - this is safe to run

ok, SU+J enabled for partition root.. disabled for other one

but I read SU+J is bad for outages.. and gjournal is better

also bad for big date

hm, i don't know, ymmv

"Also, I've noticed a trend with SU+J in the case where the filesystem uses the journal correctly, it marks the file system as clean, but all too often when followed with a forced non-journaled fsck also in single user mode, it finds many filesystem errors. It should not mark the filesystem as clean in this case, but it does anyway ... so I am very uncomfortable about recommending SU+J to anyone."

same as me

looks like I need to read more about it.. and gjournal or zfs is best solution, also thank you

you're welcome

I have this running in the background: `xautolock -time 15 -locker slock`. It dosn't activate slock after 15 min though. It works if I manually run `xautolock -locknow` though. I'm pretty sure it work earlier. Could this have something to do with the fact that I have disableb power saving mode for the USB-ports?

Yep. It works when I removed my Fiio Air Link USB-dongle.

And now it works when it's connected... bah

anyone know if there is an RSS feed for freebsd.org/security/advisories/? i can see the ports collection VuXML has a feed but what about the base system?

petercs: LLM thinks there used to be at freebsd.org/security/feeds/advisories.xml

feeds/ gives a 404

ISTR the main site was redesigned. perhaps rss was overlooked

f451: yeah i did try adding `/rss.xml` and `/feed.xml` to the end but no joy :/ i guess i could ask on a mailing list or the forums about it?

because it feels like something that should exist for those who use an RSS aggregator for security advisories rather than mailing lists

yeah, i'd ask on security@ too

vuxml.org/freebsd/rss.xml could this be anything of value?

Hund: vuxml is for ports afaict

there is this: vuxml.org/freebsd/index.html

but thta has ports and src mixed in, and it's not an rss feed

oh

aha! i found it!

Hund: ^^^

nice

I trying to install freebsd on my apu2d4 over serial console, I have get the serial console to work and I get output.. but after dpaste.com/2PU7R95EK I dont get anything (the installer doesnt boot) I have add the configuration for serial-console in loader.conf

Dual Console: Serial Primary, Video Secondary

makes me thing that you shouldn't need to

the speed doesn't change, does it?

rtprio: nope it should be 115200

When switching msata with my openbsd on it´s working (and has working for 14 years). I have test 3 msata with same result..so I it feels I missing something..

I have also change to only serial but output stops after lo0: link state changed to UP.. and I used this image FreeBSD-15.0-RELEASE-amd64-memstick.img (dd to my usb). must I add something to /etc/ttys or something?

nwe, Hints from my notes: Boot to the installer. Select "Escape to the loader prompt" set comconsole_port=0x3e8 (for my 3rd comm port here, whatever for you there) set console=comconsole boot That must be typed in slowly. If I paste it in then it garbles the data with a buffer overrun.

After install to make that permanent edit /boot/loader.conf and install those settings there.

At that point the console is active. No need to edit /etc/ttys file to configure getty as one is started automatically.

On my IPMI SOL serial over lan console the BIOS screen expects a 100x30 sized terminal. I create an xterm that size so that it has a sane display. And then after I log in "export COLUMNS=100 LINES=30" keeps that end sane too.

rwp: I will test that

I'll just note something that I am sure is obvious but... The serial terminal does not have any support for SIGWINCH signal window size change. Hardware terminals are always of a fixed size.

So don't go resizing the emulator window as that won't track through like it does with an X Window XTerm or other emulator which catches SIGWINCH and reacts to the size change. We can only set the export COLUMNS=100 LINES=30 size to our terminal size manually like that.

rwp: but this has only 1 comport so I dont think I need to set comconsole_port=0x1e8 the strange think is that I see the FreeBSD boot menu and the text after until.. and my terminal is 100x30 now.

are those boards any good? they seem out of stock everywhere?

rtprio: is really good but PC Engines are going end-of-live. so you cant buy them anymore :/

The FreeBSD boot menu automatically displays /everywhere/ both to the vidconsole and the comconsole. But when the kernel gets going by default it switches to vidconsole unless otherwise directed. Pretty sure. That's from version 12 days but pretty sure it hasn't changed from 12, 13, 14, 15 for that detail. If you find it has please let me know.

shame. i have a soekris 4501 that's sitting in the bin since it feels so obsolete at this point

storage bin, j'espere?

hmm should I choose new package or Distribution Sets now with 15.x?

f451: Cool. Thanks!

hmm I don't see who is in this channel

Was is or was the issue with 14->15 upgrade? freebsd-update is fine (currently) but trying to from non-pkgbase to pkgbase isn't supported? You need to do a fresh reinstall?

Even 15 -> 15 pkgbase.

you can use github.com/FreeBSDFoundation/pkgbasify for 15 -> 15 pkgbase

Sounds scary. experimental.

you can't upgrade and pkgbasify at the same time, you need to switch to the same version or it will have issue merging configuration files

ok

I think it's time to move to 15. So freebsd-update first.

skered: FreeBSDFoundation/pkgbasify a25484d

you can try with 14, but safest bet is probably to freebsd-update first :)

You can also use pkgbasify for 14 -> 15 update.

It's very simple and very fast.

pkgbase then upgrade

can't do both at the same time

Correct.

Only a few simple steps, though.

And the time saved is incredible.

are dedicated arc cards supported? (a310 etc?)

i really can't find anything concrete with drm-kmod

Doesn't look like ARC is supported yet, but work appears to be ongoing: freebsd/drm-kmod #315

Hm. Applying today's updates, /usr/libexec/sshd-auth didn't get applied in a jail. It got applied to the physical systems I tried. Anyone else seen this?

Updated with freebsd-update, FreeBSD 14.

It appears to have popped into existence with this update.