Is there a guide somewhere for modifying ports? I've been reading and trying to change code/apply a patch to a port. When I run make build however my changes are discarded. Reading Porter's Handbook Ch.4 Slow Porting and have tried to make the patches both automatically and manually. Auto method (make makepatch) doesn't seem to make a patch from the file and the file.orig. And my manual patches aren't being applied to the file.

Best asked in #freebsd-ports or on the mailing list.

thank you

You're welcome.

whats happening with the new libXft with bgra support? Is it going to make it into 12.3 anytime soon?

Plasmoduck: checking the log 2.3.6 is already there since Sep 10?

zzz works fine, that is fantastic

FreeBSD:12:amd64 2.3.6 2.3.4 (that is "latest" and "quarterly")

Good to hear uskerine. :-)

good morgning, I'm (hopefully) once and for all switching from arch linux to freebsd. Now I'm preparing my external harddrive for backups. What would be the best filesystem to format that disc? (It is currently formatted under Windows 10 and while I could mount it in arch I couldn't mount it in freebsd)

The "best" fs that's supported by all the operating systems you will use to access it, would be my best bet

The highest common denominator, so to speak

rtyler: 160 IOPS is fine for spinning rust, not for NVMe. :)

vkarlsen: as I said: Migrating everything from Arch Linux to FreeBSD :-)

So you'll need something that both of those can use

vkarlsen: yes, please

zfs with the compatibility flag

also in 13.0 I was writing about the missing Realtek RTL 8125 LAN controller missing on the install medium. How can I check if it's present in 13.1?

Title: Realtek RTL 8125 2.5Gbps LAN controller. | The FreeBSD Forums

ZFS has a compatibility flag!? I'll have to look into that for my external HDDs.

Yes, documented in zpoolprops(7).

Very nice, thanks!

when do the quarterly packages get updated? actually at the year quarters, so tomorrow?

Hi

hi, I just tried to do a backup with my external harddrive in linux. It's a dos partition in fat32. Freebsd recognizes the partition but fails to mount it saying: "Invalid Argument". What should I do here?

andmars: mount -t msdosfs /dev/da0 /mnt

That should work

Replace da0 with your device, of course

If it's a partition (which I expect it to be) it's probably da0p1

meka: I did write exactly that, still "Invalid argument"

(yes, it's da0p1)

Anything in dmesg?

or /var/log/messages?

file -s /dev/da0p1

meka: it finds the intension USB 3.0 drive, yes

oh, do I have to be in group usb? (but I'm root)

yuripv: looks normal to me

would it helpt if I did a linux partition with ext4 as filesystem?

and how do I turn the external harddrive off now?

is there a command?

If it's not mounted, you can just pull it out

meka: that makes an unhealthy noise. In linux I have "udisksctl power-off" for that

I'm not aware of any command like that

camcontrol stop /dev/da0 ?

and camcontrol standby /dev/da0

something like that

tao: thanks...and thunar also did the trick

Hi, has anyone else seen this article today? arstechnica.com/information-technol…ndreds-of-linux-and-windows-devices

Title: Never-before-seen malware has infected hundreds of Linux and Windows devices | Ars Technica

As well as Windows and Linux it specifically mentions FreeBSD, which is unusual. Anything to be worried about or just the usual FUD?

fraxamo: the blog post that links to said it's really linux specific, there are only 2 mentions of freebsd at all and that's about a staged tool for ddos against freebsd

Ok, thanks

debdrup: the writes on these drives is all over the map. I don't know if you saw some of my comments, a drive totally timed out while resilvering >_<

fraxamo: Dan Goodin knows what he's talking about; if you follow the in-article link to the actual analysis by the people who did it, there's mention of an ELF executable built for FreeBSD, so it's entirely plausible, especially considering the portability of go.

The ELF executable is based on previous work though.

There's always new badware being written; that it targets FreeBSD isn't indicative of anything, really.

Take a look at elf(5) if you're curious about the format.

also: justine.lol/ape.html

Title: Actually Portable Executable

EI_OSABI is the specific field in the header that contains the information about what OS the binary is intended to be run on.

meena: neat bit of steganography

If you like that kind of steganography, look at what PoC||STFU has done over the years.

debdrup: no time, have to figure out… my job… lol

meena: yeah, that seems more important; but they do maintain a spoiler file if you aren't interested in figuring it out for yourself

debdrup: cool

alchemistowl.org/pocorgtfo click the individual spoiler links

Title: International Journal of Proof-of-Concept or Get The Fuck Out (PoC||GTFO)

Oh, it's GTFO, not STFU.

Speaking of mixed-script steganography, a newish brand of deli foods (hummus, ktipiti, baba ganoosh, tzatziki, tarama, etc.) found it cute to 1- call itself MSZZLKI, and 2- spell it in uppercase Greek. I find both excruciatingly painful.

V_PauAmma_V: i read that aloud as "miss licky"

Why is 'make clean' in the ports tree so fekking slow these days?

And yes, I set NO_CLEAN_DEPENDS.

because it's spelled NOCLEANDEPENDS?

Well. . . that is a good point.

However. . . I restarted with that set and it's no faster.

it's a tiny bit faster, yes

usually i just do find -type d -name work | xargs rm -rf

Hi yuripv. May I suggest having find do both the finding and the xarg'ing? Try: find . -depth -name dira -exec echo rm -rf {} +

I have an "echo" in there to make it safe for me to use as an example and I know it can't accidentally screw someone copy-pasting without verifying it.

now i'd just use `git clean`

The "{} +" form basically replaces the "| xargs" form for almost all use cases. For a large number of files it is faster because the pipe becomes a bandwidth limiter.

And of course being internal to find then it is also safe in the presence of files with whitespace.

hey all.. anytime I use "adduser", it goes through all the process and fails with "pw: user 'hyfm1' disappeared during update" and "adduser: ERROR: There was an error adding user (hyfm1)"

I can't find anything in the logs. Any ideas here?

pjs, No idea but let me ask anyway, what OS version? freebsd-version

pjs, The wisdom of the forums says that /etc/passwd and /etc/master.passwd are out of sync. Fix that first with: pwd_mkdb -p /etc/master.passwd

rwp, thanks. I was just about to try that.

version 12.2p12

rwp: thanks. That was it. Looks like my users were created as now they're there.

but issue resolved, thanks.

Yay! :-)

I couldn't for the life of me remember the command pwd_mkdb smh. I had just found it on google when I saw your msg haha

That /etc/passwd is not the master copy on FreeBSD snags me sometimes too.

pjs, I'll just note that vipw has become my default way to edit "/etc/passwd" because it really does the right thing, calls pwd_mkdb, and some syntax checking too.

good call. It's been so long since I had to even poke into the passwd files I didn't think of vipw

Plus the other day I had to mount another system root (it was a boot environment) and needed to fix something. "vipw -d /mnt/etc" worked easily and called pwd_mkdb in that directory perfectly too.

Honestly it was too easy. I was ready to slog through it pulling the sled through miles of snow but it was done trivially.

rwp: hah, awesome!