public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: non-persistant storage?
Date: Fri, 13 Dec 2019 06:28:00 -0000	[thread overview]
Message-ID: <5a2a2640-112e-adbf-7f7a-d599b086d3cd@SystematicSw.ab.ca> (raw)
In-Reply-To: <5DF2E42A.7020200@tlinx.org>

On 2019-12-12 18:06, L A Walsh wrote:
> On 2019/12/12 13:40, Eliot Moss wrote:
>> Ah!  I think what you want is a tmpfs or ramfs.
>> Not sure if cygwin supports that ...
>>   
> ----
>    Easiest thing might be to use /dev/shm. I used it during
> development to store intermediate data that was later to be
> transfered via a fifo...
> 
> Basically check for existence of "/dev/shm" (exists on my cygwin).
> if "tmp" didn't already exist, create it w/options similar to
> /tmp (only owner can delete/edit):
> 
> mkdir -m 1777 /tmp/shm/tmp
> 
> 
> **Warning, "writes" to /dev/shm/tmp (or /dev/mem) can fill up
> your system's memory, so its only good for "small files"
> (small being well under your system's free memory amount).

I've been using /run, with /var/run as a symlink to that, created in a permanent
postinstall script /etc/postinstall/zp_mk_run_var_links.dash (with some others),
for some time. It's currently using ~28KB.

Is it feasible to mount /run on say /dev/shm/run and create and use files there?

Or would it be more feasible to use say Cyg/WinFUSE to provide that function?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-12-13  6:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 12:28 Ulli Horlacher
2019-12-12 21:27 ` Eliot Moss
2019-12-12 21:40   ` Ulli Horlacher
2019-12-12 21:59     ` Eliot Moss
2019-12-13  1:33       ` L A Walsh
2019-12-13  6:28         ` Brian Inglis [this message]
2019-12-13  9:34           ` L A Walsh
2019-12-13 10:06         ` Ulli Horlacher
2019-12-16 10:22 ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5a2a2640-112e-adbf-7f7a-d599b086d3cd@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).