Search results for query: Read file name

Thank you for the extensive testing. You had gone through some kind of work to test this. I'm just evaluating if my case was important enough and feel thankful. What can I say. Is this important enough? To me it looks like that you had used a single process reading and writing. In my case...

Slowly but surely that copy-file-range gimmick begins to annoy me. There was this one: https://forums.freebsd.org/threads/why-is-stdout-locked-against-read.99421/post-722715 Rick Macklem wrote a workaround, I am not sure if that was incorporated into HEAD. Then there is this one, which...

It is only one filesystem, the toplevel of a ZFS fileset, wich is nfs exported, and then mounted from remote. A zfs fileset has on the toplevel an invisible .zfs directory, which contains the snapshots, and therefore is readonly. Apparently nfs gets confused because the same...

Which of the two file systems (.zfs/... and .) is NFS? Which one is read only? How are they mounted? I don't have enough information to help understand or debug this.

Lets assume we have accidentially deleted a file. Luckily, it is zfs and there is a snapshot, so one might just copy the file back from .zfs/snapshot. But this doesn't work on NFS: pmc@disp:2516:1~/Media$ cp .zfs/snapshot/zar.20531/Thiere.txt . cp: .zfs/snapshot/zar.20531/Thiere.txt: Read-only...

Hello forum, long time no see. Glad to be back. I got a T490 recently that have a nvidia MX250. Installation went fine beside a bug that I will cover in another post, because it is not related to this problem. After install the base OS I installed X, xfce, lightdm and the kernel modules for the...

Is your filesystem clean? Run fsck if you have UFS partitions. Check /var/log/messages and dmesg for hardware-related errors, especially disk-related ones. Now may be a good time to check your disk cables physically. Replace them if you have spares and try again. If the error persists, run...

It the DEPRECATED= variable is set in the port's Makefile but it hasn't been removed yet. It's been deprecated for a long time, probably because a good enough replacement hasn't been found yet. As to this being the cause it was removed, I doubt that.

Right, I should say I did in fact read the handbook when I was looking for help. It didn't work the first time, and I thought I followed all the steps, but I did look through that chapter again. This time when I did it again, it did actually work. It did spit out the same error, but then it...

The file.dbm is a placeholder, it is not the name of an actual file. If you don’t know if and where you’ve stored any BDB5 databases, you’ll need to find them:find / -type f -exec file '{}' ';' | fgrep 'Berkeley' | fgrep -v '1.85' As the update message says, it has been deprecated. I guess it is...

I've been using FreeBSD, and these forums, for years; but, today, I created an account just to post a solution to the problem described above. Hopefully this will help prevent any others from spending a handful of wasted hours on the effort as I did. 😅 While the solution described by dmitrij...

Original article here. Consider this when replying. FreeBSD runs on this… FreeBSD runs on this… and FreeBSD runs on this…! It’s easy to get FreeBSD running on a Raspberry Pi. It’s easy to manage multiple hard drives with ZFS. So we were wondering if it’s possible to make a simple NAS...

We need to BAN all AI here. This is getting tiresome from a FreeBSD helper standpoint. Bad enough people won't read the manuals now we have to fight outright lies. When we have to fight outright lies it becomes very dull to me. Ban users posting slop and AI. SSH Keys are in /etc now? No this...

Here's the answer that my particular blend of ChatGPT gives to your inquiry. I hope it helps at least to recruit human commentators to help you. And if ChatGPT's answer is itself helpful, good. A partially read-only FreeBSD system A partially read-only FreeBSD system is easiest to reason...

My apologies. I'm a dyslexic and not very good with text-heavy man files, which is why I ask so many questions (and I'm one of the last six people who don't learn via chatbots). But I'll give the pf.conf man file a go.. I've changed pf.conf as you suggested....and now no syntax error...

re: the first thing, yes, assuming that's where the badguys file lives. re: the block rule, on clause: no. you need the table line and the block rule, but the block rule can be simplified to block from <badguys> to any instead of having two rules that reference interfaces that may or may not...

Re adding IPs to /etc/badguys: So, rather than adding IPs via: ....they'll need to manually enter each new IP they want to BLACKHOLE to /etc/badguys....then, run: Re the block clause: So I need to delete both of the entire block lines in /etc/pf.conf....and leave only the table line?

you don't use pfctl to add IP's to that file. pfctl only deals with the in-memory copy. when you reboot, anything you did with pfctl -T add goes away. you have use an editor on the file, like ee /etc/badguys, put the IP's in the file, and then you use pfctl -t badguys -T replace -f /etc/badguys...

Seams reasonable, mostly , that is 95% percent of time i use firefox & neovim-qt. In background sometimes , poudriere, when i tune wrong system dies, now 100G of swap, so i'm safe. And poudriere i run with , "nice -n 31 idprio 31"

Just for everybody's information, FreeBSD's current tmpfs(4) file contents are pageable. When the system gets low on memory the contents of files in tmpfs are moved to swapspace. just like process read-wrote data is. So you do not in fact take RAM away from the system unconditionally.