[Alpine-info] Firefox, snap and /tmp
Eduardo Chappa via Alpine-info
alpine-info at u.washington.edu
Tue Jun 4 07:54:42 PDT 2024
On Tue, 4 Jun 2024, Kjell Rönnmark via Alpine-info wrote:
> Hi,
>
> Have you noticed that the snap version of Firefox in Ubuntu cannot access /tmp?
> See https://forum.snapcraft.io/t/firefox-snap-no-access-to-gvfs-and-tmp/27253
>
> As far as I understand, alpine copies attached html files to /tmp, and I
> have not found an easy way to change this (although I can work around it
> with a small script).
>
> Can can this issue be handled within alpine i a simple way?
>
Kjell,
I think you sent me this message and I replied to you but your service
rejected my message, but since it is in german, I have no idea why. At
that time I told you that Alpine can configure the location of /tmp. From
the release notes:
Unix _Alpine_ uses the following environment variables:
TERM
Tells _Alpine_ what kind of terminal is being used.
DISPLAY
Determines if _Alpine_ will try to display IMAGE attachments.
TMPDIR, TMP, or TEMP
Specifies location of temporary storage area, first one set wins
SHELL
If not set, default is /bin/sh
MAILCAPS
A semicolon delimited list of path names to mailcap files.
What I fail to understand is how is this something that Alpine has to work
around? /tmp is not an invention of Alpine. How did you work around this
that is so bad? (what was your script like?). In earnest, I fail to
understand why Alpine has to do anything here because someone implements
their own file system? What is the rationale? Why would ubuntu delete
Alpine? I am sorry, I just do not see the problem here as an Alpine
problem. If you could explain to me what you see the issue is, I would try
to do something from Alpine to solve it, but I just do not see it. As far
as I can tell, you can solve it by setting an environment variable. Does
that solve the problem for you?
--
Eduardo
More information about the Alpine-info
mailing list