Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
Newsgroups: comp.os.linux.misc
Subject: Re: memory managment and (its) protection under Linux
Date: Thu, 22 Aug 2024 20:10:03 -0000 (UTC)
Organization: the-candyden-of-code
Lines: 42
Message-ID: <slrnvcf68t.td1s.candycanearter07@candydeb.host.invalid>
References: <va24hg$3cdd8$1@dont-email.me> <va2n6n$3fs69$1@dont-email.me> <1SGdnStv4NVv9Vj7nZ2dnZfqn_udnZ2d@earthlink.com> <va4dkl$3qlqh$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 22 Aug 2024 22:10:03 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="faa1a301eb098e6b485aa6999a60c76e"; logging-data="602745"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/Ti7OUBOTQYKpHxZ8xHWLNklXnCbz544e7iVOLLJSQaQ=="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:ciXrSZzWJEazGtMOzP3fZ2WMukg=
X-Face: b{dPmN&%4|lEo,wUO\"KLEOu5N_br(N2Yuc5/qcR5i>9-!^e\.Tw9?/m0}/~:UOM:Zf]% b+ V4R8q|QiU/R8\|G\WpC`-s?=)\fbtNc&=/a3a)r7xbRI]Vl)r<%PTriJ3pGpl_/B6!8pe\btzx `~R! r3.0#lHRE+^Gro0[cjsban'vZ#j7,?I/tHk{s=TFJ:H?~=]`O*~3ZX`qik`b:.gVIc-[$t/e ZrQsWJ >|l^I_[pbsIqwoz.WGA]<D
Xref: csiph.com comp.os.linux.misc:58135

The Natural Philosopher <tnp@invalid.invalid> wrote at 09:56 this Wednesday (GMT):
> On 21/08/2024 05:11, 186282@ud0s4.net wrote:
>> On 8/20/24 2:27 PM, The Natural Philosopher wrote:
>>> On 20/08/2024 14:09, MarioCCCP wrote:
>>>>
>>>> partially OT : programming task
>>>> Scenario : Debian Bookworm, XFCE4
>>>> Very often GUI programs show their results in the form of ListBoxes, 
>>>> whose content is mainly textual semantically, but very often cannot 
>>>> be copied/pasted as text and neither is easy to export as text. I 
>>>> have one case in FreeFileSync, that shows lists of files upwards of 
>>>> 500'000 items, and other deduplicators programs.
>>>> I am having a general curiosity about this problem in linux.
>>>> Can a root user access, in read only mode, to memory associated to 
>>>> another (plain user mode) process ? Or the outcome is invariably a 
>>>> seg_fault ? Has a root user the right to inquire the memory of non 
>>>> root programs ?
>>> I believe not.
>>> In such cases it is usual to write a daemon to handle *all* requests.
>>>
>>>   I am not speaking about disk files, but specifically in
>>>> physical memory
>>>
>>> Well thereby hangs a tale. In fact i deliberately created a RAMDISK in 
>>> one application purely to handle communications between synchronous 
>>> processes.
>>>
>>> One process writes it, others may read
>> 
>>    In many Linux distros now, /tmp is a de-facto
>>    ramdisk - all disappears on reboot. IF you have
>>    the space in your / partition then you need not
>>    specifically create a NEW ramdisk to achieve the
>>    effect.
>> 
> Not /tmp oddly, but various other stuff like /run is, yes.


Even if it's not a ramdisk by default, you could still easily set it up
as one in your fstab
-- 
user <candycane> is generated from /dev/urandom