public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How can I control size of /run (tmpfs)?
Date: Tue, 29 May 2012 09:38:55 +0700	[thread overview]
Message-ID: <CAA2qdGWKpdtns8nf5oEPWkn7YYUBwSOucNV2Yw_6a8=q4VgMQQ@mail.gmail.com> (raw)
In-Reply-To: <4FC3BA39.7060208@coolmail.se>

[-- Attachment #1: Type: text/plain, Size: 656 bytes --]

On May 29, 2012 12:53 AM, "pk" <peterk2@coolmail.se> wrote:
>
> On 2012-05-28 05:44, Pandu Poluan wrote:
>
> > But my newer servers has /run (and its children) from the get go,
because I
> > think it kind of makes sense. Even though they're udev-free.
>
> Hm... what is using /run instead of /var/run? I thought it was (newish)
> udev itself and things like systemd that uses /run instead of
> /var/run... just curious.
>
> Best regards
>
> Peter K
>

Nothing that I know of, then. But I  thought if sometime later down the
road some braindead dev assumes that everyone uses udev and hardwired
his/her package to assume /run exists, I'm covered :-)

Rgds,

[-- Attachment #2: Type: text/html, Size: 876 bytes --]

  reply	other threads:[~2012-05-29  2:40 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-26 19:46 [gentoo-user] How can I control size of /run (tmpfs)? Jarry
2012-05-26 20:01 ` Dale
2012-05-26 20:08   ` Jarry
2012-05-26 20:28     ` Dale
2012-05-26 20:43       ` Michael Mol
2012-05-26 20:44       ` Alex Schuster
2012-05-26 21:02       ` Michael Hampicke
2012-05-26 21:20         ` Michael Mol
2012-05-26 23:23         ` Alan McKinnon
2012-05-26 20:33     ` Michael Mol
2012-05-26 20:40     ` Neil Bothwick
2012-05-26 22:17       ` Dale
2012-05-26 22:34         ` Neil Bothwick
2012-05-26 23:17           ` Dale
2012-05-26 23:21             ` Alan McKinnon
2012-05-27  0:15               ` Dale
2012-05-27  2:30                 ` Pandu Poluan
2012-05-27  3:06                   ` Dale
2012-05-27  4:29                     ` Joshua Murphy
2012-05-27  4:51                       ` Dale
2012-05-27  5:22                         ` Joshua Murphy
2012-05-27  6:04                           ` Dale
2012-05-27  6:20                       ` Canek Peláez Valdés
2012-05-27  6:34                         ` Canek Peláez Valdés
2012-05-27  7:05                         ` Jarry
2012-05-27  7:59                           ` Alan McKinnon
2012-05-27 12:41                             ` William Kenworthy
2012-05-27  8:24                           ` Neil Bothwick
2012-05-28 18:31                             ` Jarry
2012-05-28 18:58                               ` Michael Mol
2012-05-28 19:24                                 ` Jarry
2012-05-28 20:40                                   ` Alan McKinnon
2012-05-28 21:19                                   ` Michael Mol
2012-05-28 22:38                                   ` Neil Bothwick
2012-05-28 22:41                               ` Neil Bothwick
2012-05-27  8:16                       ` Neil Bothwick
2012-05-26 22:45         ` Michael Mol
2012-05-28  2:06         ` Walter Dnes
2012-05-28  3:44           ` Pandu Poluan
2012-05-28 17:47             ` pk
2012-05-29  2:38               ` Pandu Poluan [this message]
2012-05-26 21:47 ` [gentoo-user] " Nikos Chantziaras

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='CAA2qdGWKpdtns8nf5oEPWkn7YYUBwSOucNV2Yw_6a8=q4VgMQQ@mail.gmail.com' \
    --to=pandu@poluan.info \
    --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