Le 07/04/2024 à 15:49, Lew Pitcher a écrit :
> On Sun, 07 Apr 2024 13:34:43 +0000, pehache wrote:
>
>> Hello,
>
> Hi, pehache
>
>> When memory mapping a file with the MAP_PRIVATE flag, the modifications
>> (writes) only exist in memory and are not written back to the file.
> [snip]
>> So: is there a way to write the changes back to the file?
> [snip]
>
> The comp.unix.programmer newsgroup will be of better help for this sort
> of question (it's not really on-topic for comp.lang.c).
>
> But, of the top of my head; with my limited understanding of the unix
> mmap() kernel call, the only ways to "write the changes" are to either
> 1) mmap(MAP_SHARED) and modify the mapped area, or
> 2) write() the mapped area back to the file.

I'm currenly using the first option in my code. Either way, the whole
mapped area is written back, even if there were only a few changes. I was
hoping there could be another way to wrtite back only the modified pages.

> But, as I said, comp.unix.programmer will be of better help.

fu2

On 4/7/24 15:09, pehache wrote:
> Le 07/04/2024 à 15:49, Lew Pitcher a écrit :
....
>> But, as I said, comp.unix.programmer will be of better help.
>
> fu2

Why does that advice annoy you? Why wouldn't you want to take your
question to the forum where people are best qualified to answer it?

James Kuyper <jameskuyper@alumni.caltech.edu> writes:
> On 4/7/24 15:09, pehache wrote:
>> Le 07/04/2024 à 15:49, Lew Pitcher a écrit :
> ...
>>> But, as I said, comp.unix.programmer will be of better help.
>>
>> fu2
>
> Why does that advice annoy you? Why wouldn't you want to take your
> question to the forum where people are best qualified to answer it?

I believe "fu2" refers to this header line in the article you're
replying to :
Followup-To: comp.unix.programmer

pehache: Apparently James thought "fu2" meant ... something else.

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Medtronic
void Void(void) { Void(); } /* The recursive call of the void */

Le 07/04/2024 à 23:44, James Kuyper a écrit :
> On 4/7/24 15:09, pehache wrote:
>> Le 07/04/2024 à 15:49, Lew Pitcher a écrit :
> ...
>>> But, as I said, comp.unix.programmer will be of better help.
>>
>> fu2
>
> Why does that advice annoy you? Why wouldn't you want to take your
> question to the forum where people are best qualified to answer it?

Uh? Following the advice is exactly what I've done: I have crossposted my
answer to c.u.p, with a fu2 positionned on it.

Le 07/04/2024 à 23:49, Keith Thompson a écrit :
> James Kuyper <jameskuyper@alumni.caltech.edu> writes:
>> On 4/7/24 15:09, pehache wrote:
>>> Le 07/04/2024 à 15:49, Lew Pitcher a écrit :
>> ...
>>>> But, as I said, comp.unix.programmer will be of better help.
>>>
>>> fu2
>>
>> Why does that advice annoy you? Why wouldn't you want to take your
>> question to the forum where people are best qualified to answer it?
>
> I believe "fu2" refers to this header line in the article you're
> replying to :
> Followup-To: comp.unix.programmer

That's correct.

>
> pehache: Apparently James thought "fu2" meant ... something else.

OK, sorry for the misunderstanding :( !

"fu2" is a routinely used abbreviation for "Followup-To" (and just that!)
on the fr.* hierarchy, and I thought it was kind of universal on all
hierarchies. Apparently it's not...

In article <PgZyW9oCgOxERNyTFwXvTAzcfig@jntp>,
pehache <pehache.7@gmail.com> wrote:
....
>OK, sorry for the misunderstanding :( !

Nothing to be sorry about.

>"fu2" is a routinely used abbreviation for "Followup-To" (and just that!)
>on the fr.* hierarchy, and I thought it was kind of universal on all
>hierarchies. Apparently it's not...

It is fine.

This poster (James whatever) has a long history of weirdly misunderstanding
things. I wouldn't worry about it.

--
Many people in the American South think that DJT is, and will be remembered
as, one of the best presidents in US history. They are absolutely correct.

He is currently at number 46 on the list. High praise, indeed!