From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] /usr/tmp -> /var/tmp a problem with new udev?
Date: Tue, 21 Aug 2012 00:33:22 +0200 [thread overview]
Message-ID: <5032BB32.4030404@binarywings.net> (raw)
In-Reply-To: <yu9vcgdie0e.fsf@nyu.edu>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
Am 20.08.2012 21:01, schrieb Allan Gottlieb:
> On Mon, Aug 20 2012, Doug Hunley wrote:
>
>> On Fri, Aug 17, 2012 at 8:47 AM, Allan Gottlieb <gottlieb@nyu.edu> wrote:
>>> I realize that new udev without dracut wants /usr part of root
>>> filesystem.
>>>
>>> The last few gentoo installations I have done all had
>>> /usr/tmp symlinked to /var/tmp and I don't believe I did this symlink
>>> manually.
>>>
>>> Will this be a problem with new udev and no dracut or are the programs
>>> that must run early trained not to use /usr/tmp?
>>>
>>> thanks,
>>> allan
>>>
>> I have this symlink on a new ~amd64 install without a separate /usr
>> and the latest udev and have no issues at all. I don't use a initramfs
>> or anything on this install either. fwiw
>
> Thank you, that is what I wanted to hear. I assume you don't run dracut
> either.
>
> allan
>
> (PS top-posting is discouraged on this group)
>
Are there still programs out there using that directory, anyway? I
thought /usr/tmp is mostly for compatibility with ancient Unixes. Even
in the FHS it is a "may be present" clause.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-08-20 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 12:47 [gentoo-user] /usr/tmp -> /var/tmp a problem with new udev? Allan Gottlieb
2012-08-20 16:51 ` Doug Hunley
2012-08-20 19:01 ` Allan Gottlieb
2012-08-20 22:33 ` Florian Philipp [this message]
2012-08-27 16:38 ` Doug Hunley
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=5032BB32.4030404@binarywings.net \
--to=lists@binarywings.net \
--cc=gentoo-user@lists.gentoo.org \
/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