From: marco atzeri <marco.atzeri@gmail.com>
To: "Prof. Luis G. Uribe C." <luribe@usb.ve>
Cc: cygwin@cygwin.com
Subject: Re: 'tac' trying to use "/tmp"; Error: not found
Date: Sun, 2 Apr 2023 23:22:24 -0400 [thread overview]
Message-ID: <CAB8Xom-zk0FKPjWdOnw1Ww_rh25YYhaRt-YuUJELj20PqNXNpQ@mail.gmail.com> (raw)
In-Reply-To: <CAOoKcr1hm_F7e9pLDDu55WdZA_yN6eKFw_ibF5eHSGJbxFnfcA@mail.gmail.com>
On Sun, Apr 2, 2023 at 9:43 PM Prof. Luis G. Uribe C. via Cygwin wrote:
>
> *Bogotá, Sunday April 2nd, 2023*
>
> *REF: 'tac' trying to use "/tmp"; Error: not found*
> *_______________________________________________________*
> *| 'tac' utility dies with a not found "/tmp" error. |*
> *¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯*
> I didn't see this problem in older 'tac' versions...
>
> I created "/tmp" under my root directory:
> * "c:\tmp"* (Windows 10), *to no avail*.
>
> I make a *tmp* dir directly *above*, in the *parent's 'tac' dir*:
> *"../tmp"*, at the same level as other usual folders like:
> *bin*, *dev*, *etc*, *lib*, *sbin*...,
> and now: *'**tac' works fine**!*
The expectation for the existence of /tmp directory is well founded
https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
I assume by accident your installation pruned the directory.
I will not be surprised if other programs also complain, not only tac
> Best regards,
>
> *Eng. Luis G. Uribe C.*
>
Regards
Marco
next prev parent reply other threads:[~2023-04-03 3:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOoKcr3-vGedWvQWu8kmKJ48AfGpaqO0pHQG-KZFc2h+SAuKSw@mail.gmail.com>
[not found] ` <CAOoKcr3rB3cLPs+OX=qC0DVoS=pnbaOQH5HLxAa53bjb4mVwKQ@mail.gmail.com>
[not found] ` <CAOoKcr3gXr3QMT6sJkHC=jVsuFnXamOpdHJ3dt9=yCixYeAzrQ@mail.gmail.com>
[not found] ` <CAOoKcr2sX3LTPt__nkU0onVXpicDQUmEdSgv8L2UnR+KKv6sug@mail.gmail.com>
2023-04-03 1:42 ` Prof. Luis G. Uribe C.
2023-04-03 3:22 ` marco atzeri [this message]
2023-04-03 15:29 ` Brian Inglis
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=CAB8Xom-zk0FKPjWdOnw1Ww_rh25YYhaRt-YuUJELj20PqNXNpQ@mail.gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=luribe@usb.ve \
/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).