Or maybe I'm wrong. Idk, but it's a kick in the teeth, As a user experience ...

Of course, I don't use the Desktop and work with its commands, and recently I had to install Icewm to run graphical software.

Have you looked at the logs? Maybe the problem is something simple?

It might not be suitable for your laptop, but that doesn't mean FreeBSD isn't good for desktops at all. I have FreeBSD running on two computers and a laptop, and it's been working flawlessly for years. I'll try to help you, but it's best to read the FreeBSD Handbook first.

I appreciate that. Actually, I admire its features like jails, Dtrace, ZFS, the file system hierarchy, ports, and so on ... That's what pushed me towards installing it ... Very underrated OS I wish I could see more hardware support ... I hope I'm wrong And that's a simple misunderstanding Of the situation. ( At some points I wanted the problem to be originated from my laptop rather than the FreeBSD 😂 ) But let me do another fresh install ( this time while following the handbook) I'll inform you if the problem persisted ...

Have you looked at the logs? Maybe the problem is something simple?

Yes, double checked dmesg, Nothing special ...

I appreciate that. Actually, I admire its features like jails, Dtrace, ZFS, the file system hierarchy, ports, and so on ... That's what pushed me towards installing it ... Very underrated OS I wish I could see more hardware support ... I hope I'm wrong And that's a simple misunderstanding Of the situation. ( At some points I wanted the problem to be originated from my laptop rather than the FreeBSD 😂 ) But let me do another fresh install ( this time while following the handbook) I'll inform you if the problem persisted ...

I will do my best to ensure you have a beautiful experience like mine.

Yes, double checked dmesg, Nothing special ...

ahaa, so i hope everything goes well

I am seriously and carefully studying the FreeBSD handbooks.

I am seriously and carefully studying the FreeBSD handbooks.

Forgot to say Their manuals are something, tbh.

I am seriously and carefully studying the FreeBSD handbooks.

May i ask how old are you

What DE and theme？Is that xfce？

What DE and theme？Is that xfce？

theme & icons : Gruvbox DE : XFCE Top bar : Polybar

May i ask how old are you

18

theme & icons : Gruvbox DE : XFCE Top bar : Polybar

You're really patient. I used IceWM to avoid any kind of configuration.

What is really a destop lol?

Thats so vague to me

theme & icons : Gruvbox DE : XFCE Top bar : Polybar

Have you ever observed a bug in XFCE? Please answer carefully. 😁

Have you ever observed a bug in XFCE? Please answer carefully. 😁

As far as I remember there wasn't any serious bugs ... Or if there was, that was negligible ...

Have you ever observed a bug in XFCE? Please answer carefully. 😁

Yes. The wallpaper doesn’t change. https://forums.freebsd.org/threads/xfce-4-20-i-cannot-change-desktops-wallpaper.96629/

Yes. The wallpaper doesn’t change. https://forums.freebsd.org/threads/xfce-4-20-i-cannot-change-desktops-wallpaper.96629/

Happened to me. Applied from terminal, and it worked

https://www.youtube.com/watch?v=EpiiT_mgYAw

@pmousavizadeh

Anyone using bbr module?

@pmousavizadeh

Could you give me your coredump or anything under your /var/crash?

2. Did you do something or it just happened? 3. freebsd-version -kru? (and if you're on the CURRENT or STABLE, you can give me your specific kernel version (commit hash) via uname -a)

2. Did you do something or it just happened? 3. freebsd-version -kru? (and if you're on the CURRENT or STABLE, you can give me your specific kernel version (commit hash) via uname -a)

Nothing unusual just interacting with userland something triggered it not sure what

Nothing unusual just interacting with userland something triggered it not sure what

It's bbr_output() and then in6_selecthlim, So it must be an outgoing tcp/ipv6 packet using bbr stack.

@pmousavizadeh

Also If it's possible, please make sure you send me the /var/crash through PM or email, NOT in this public group. It may contain some confidential information.

https://hackerpublicradio.org/eps/hpr4388/index.html HPR today about BSD

https://www.bjoremanmelin.se/podcast/avsnitt-443-valkommen-till-bsd.html

Hi dear friend, I hope you're doing well. Sorry if my question isn't very professional, but your answer could really help me a lot. I'm currently studying the FreeBSD source code and right now I'm reading loader/main.c. My biggest problem is when the project gets large and I get lost in the source code. Is there any book that teaches the correct way to read a programming project and helps understand its structure? This file, for example, has 2017 lines of code, and I can't understand all of it — and soon I forget what each function was made for. I'd be really happy if you could recommend a book or blog that helps with this problem and teaches how to properly read source code

Hi dear friend, I hope you're doing well. Sorry if my question isn't very professional, but your answer could really help me a lot. I'm currently studying the FreeBSD source code and right now I'm reading loader/main.c. My biggest problem is when the project gets large and I get lost in the source code. Is there any book that teaches the correct way to read a programming project and helps understand its structure? This file, for example, has 2017 lines of code, and I can't understand all of it — and soon I forget what each function was made for. I'd be really happy if you could recommend a book or blog that helps with this problem and teaches how to properly read source code

Are you trying to fit the whole os in your head?

Are you trying to fit the whole os in your head?

😂 What exactly should I do?👀 Should I write it down on paper? The biggest project I’ve ever read and analyzed was about 300 lines of code. Yet, even when I looked back at the early parts of my project, some functions still seemed unfamiliar to me.😂

maybe I am forgetful? 🥺

No, the point is, the project is too big to fit in one head

Are you trying to fit the whole os in your head?

something like Trace Back? should i do this?

No, the point is, the project is too big to fit in one head

So what do those who want to develop it do?

I've heard things about personal documentation, but I don't know how it helps or how to do it.

So what do those who want to develop it do?

They get an approximate understanding of what’s happening where, and learn what they want to develop more thoroughly

They get an approximate understanding of what’s happening where, and learn what they want to develop more thoroughly

is that a general understanding?

is that a general understanding?

Kinda, even a bit more general

Kinda, even a bit more general

ahaa, ok, i try it, maybe that is solution 👌🏻👀

Hi dear friend, I hope you're doing well. Sorry if my question isn't very professional, but your answer could really help me a lot. I'm currently studying the FreeBSD source code and right now I'm reading loader/main.c. My biggest problem is when the project gets large and I get lost in the source code. Is there any book that teaches the correct way to read a programming project and helps understand its structure? This file, for example, has 2017 lines of code, and I can't understand all of it — and soon I forget what each function was made for. I'd be really happy if you could recommend a book or blog that helps with this problem and teaches how to properly read source code

You can write notes.txt explaining what each function does

Hi dear friend, I hope you're doing well. Sorry if my question isn't very professional, but your answer could really help me a lot. I'm currently studying the FreeBSD source code and right now I'm reading loader/main.c. My biggest problem is when the project gets large and I get lost in the source code. Is there any book that teaches the correct way to read a programming project and helps understand its structure? This file, for example, has 2017 lines of code, and I can't understand all of it — and soon I forget what each function was made for. I'd be really happy if you could recommend a book or blog that helps with this problem and teaches how to properly read source code

2017 locs isn't that much, tbh

😂 What exactly should I do?👀 Should I write it down on paper? The biggest project I’ve ever read and analyzed was about 300 lines of code. Yet, even when I looked back at the early parts of my project, some functions still seemed unfamiliar to me.😂

That's normal

Which wifi tui manager you guys use

OSes are a big project that do not fit inside one single developer's head it always resides in a common repository and all developers should have a basic / general idea of what the OS does where (address / momery allocation, drivers etc) and they usually focus on their respective parts

2017 locs isn't that much, tbh

not much? that is one thousand line 😐

That's normal

thanks :)

OSes are a big project that do not fit inside one single developer's head it always resides in a common repository and all developers should have a basic / general idea of what the OS does where (address / momery allocation, drivers etc) and they usually focus on their respective parts

ahaa, thanks

not much? that is one thousand line 😐

Yup, not much

Hi dear Freidns

Greetings, friends! This question might seem a bit unprofessional, and perhaps it's not even appropriate to ask, but the nature of a question is to inquire—so I hope you won’t mind the length of this message. Friends, I ran a simple source code on FreeBSD to test FreeBSD’s memory allocation behavior, and I encountered an interesting issue. It’s not a bug—perhaps this is how it is supposed to work. I executed the following code, which manually accesses two byte of memory, assigns a value to it, and then reads the value stored in that byte. Source code: (Note: I do not want to use system calls like malloc, because in that case, there would be no issue.) #include <stdio.h> int main () { // char *a; // char b=0; // a=&b; // printf ("%p\n", (void*)a); // to know memory available range in Protected Mode OS volatile char *p = (char*)0x7ffcfbd5191f; *p = 'H'; printf ("%p\n", (void*)p); printf ("%c\n", *p); return 0; } In each execution, the memory allocation system in protected mode should create a new range for the program’s segments. (I am not sure why, but perhaps it is for security reasons.) This is also the case in FreeBSD, and you can observe it by the continuously changing and discrete nature of variable addresses. Now, when a new range is allocated for a process's segments, that process should not be allowed to access other memory addresses, correct? This issue does not occur in Linux—when the above code is executed, the software is immediately aborted. However, FreeBSD behaves differently—sometimes it produces an output, and sometimes no output is printed at all. So, why does it sometimes produce output? Is it because the software segment range overlaps with the memory byte address? And why does it sometimes produce no output? Is it because the software segment range does not overlap with the memory byte address, and instead of FreeBSD killing the program, it simply returns nothing? My exact question is this: Since I manually accessed memory and did not use system calls like malloc—which means the memory allocation system did not interfere—why does Linux abort the software upon first execution, whereas FreeBSD either displays the output or sometimes does not? Was I able to articulate my question clearly?

Does the operating system still free memory for us when we manually read a portion of it? Isn't this behavior only expected when using malloc? Is this related to the operating system's protected mode?

the address you accessed is virtual memory space of a process

maybe that address has special propose, maybe not, I don't care.

All in all, you should not do what you are doing. If you don't like malloc of std lib, you can write an allocator youself.

https://github.com/microsoft/mimalloc

first, i create a standard variable and look at the Address of that and put it on the source code

https://github.com/microsoft/mimalloc

you can learn how to write an allocator from there.

All in all, you should not do what you are doing. If you don't like malloc of std lib, you can write an allocator youself.

no, it's just a test i use malloc at all but i think how if i dont use that

you can learn how to write an allocator from there.

so thanks, this is helpful

So when I manually read a byte from memory, does the operating system actually provide it?

It is belong to virtual memory space of a process

https://pages.cs.wisc.edu/~remzi/OSTEP/

https://github.com/microsoft/mimalloc

this is for microsoft, can i use that's idea on UNIX-like os?

Does the operating system still free memory for us when we manually read a portion of it? Isn't this behavior only expected when using malloc? Is this related to the operating system's protected mode?

Your process exited. So its virtual memory space is returned.

It is belong to virtual memory space of a process

yeah, i remember thanks

https://pages.cs.wisc.edu/~remzi/OSTEP/

you can read this book to learn something about OS

https://pages.cs.wisc.edu/~remzi/OSTEP/

amazing, thanks, helpful book :) it use GNU GAS instead NASM

this is for microsoft, can i use that's idea on UNIX-like os?

https://github.com/microsoft/mimalloc?tab=readme-ov-file#linux-macos-bsd-etc

thanks for your helps ❤️👀

OSTEP is awesome. However, I also suggest cs631 for c in unix environment https://youtube.com/playlist?list=PL0qfF8MrJ-jxMfirAdxDs9zIiBg2Wug0z&si=YPPZO-2zhcRvVQBK

I read the Minix3 book by Tanenbaum, but every book about computers has limitations

🙏🏻

So when I manually read a byte from memory, does the operating system actually provide it?

man 9 vm_map_insert

If you want to know specific behavior about FreeBSD. Try the design and implementation of FreeBSD OS book from mckusick

@pmousavizadeh

We are discussing the panic in the transport meeting, it happened to the sctp stack before. BUT, without further information. we couldn't help much. @namiarj

https://wiki.freebsd.org/TransportProtocols/29May2025 The report about your panic (@namiarj): The following panic (https://ibb.co/tTVgbtqt) was observed. Pouria is asking for more information.

https://wiki.freebsd.org/TransportProtocols/29May2025 The report about your panic (@namiarj): The following panic (https://ibb.co/tTVgbtqt) was observed. Pouria is asking for more information.

Unfortunately dumpdev was set to NO. That disables it?