public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ângelo Arrifano" <miknix@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: use of the /run directory
Date: Tue, 17 May 2011 21:20:21 +0200	[thread overview]
Message-ID: <201105172120.21684.miknix@gentoo.org> (raw)
In-Reply-To: <1305659472.19924.8.camel@tablet>

On Tuesday 17 May 2011 21:11:12 Peter Volkov wrote:
> В Втр, 17/05/2011 в 20:43 +0200, Ângelo Arrifano пишет:
> > On Tuesday 17 May 2011 20:28:56 Nirbheek Chauhan wrote:
> > > I'd add that if we want /run to be on tmpfs, /var/run and /tmp should
> > > both be on tmpfs by default. I've been doing this manually for a year,
> > > and so have other distributions.
> > 
> > The lwn article is definitely interesting to read, I welcome the new
> > /run. I wouldn't make /tmp as tmpfs though, there are some packages
> > (wireshask I'm looking at you) that can fill the directory fairly easy.
> 
> Hm, may be I miss something... but how wireshark fills /run? As far as I
> see dumps go into /tmp.
> 
> --
> Peter.

Either one of us is needing a break away from the computer to relax the eyes, 
which one is it? :P
-- 
Angelo Arrifano AKA MiKNiX
Gentoo Embedded developer
GPE maintainer 
http://www.gentoo.org/~miknix
http://miknix.homelinux.com



  reply	other threads:[~2011-05-17 19:21 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 16:57 [gentoo-dev] rfc: use of the /run directory William Hubbs
2011-05-17 18:11 ` Peter Volkov
2011-05-17 18:28   ` Nirbheek Chauhan
2011-05-17 18:43     ` Ângelo Arrifano
2011-05-17 18:50       ` Nirbheek Chauhan
2011-05-17 19:11       ` Peter Volkov
2011-05-17 19:20         ` Ângelo Arrifano [this message]
2011-05-17 19:07     ` William Hubbs
2011-05-17 20:35       ` James Cloos
2011-05-17 20:40         ` Markos Chandras
2011-05-18  0:06           ` James Cloos
2011-05-18  0:43             ` William Hubbs
2011-05-17 19:20     ` Panagiotis Christopoulos
2011-05-17 19:46       ` William Hubbs
2011-05-18  1:31         ` [gentoo-dev] " Duncan
2011-05-18  1:36         ` [gentoo-dev] " Jeroen Roovers
2011-05-18  5:49           ` Eray Aslan
2011-05-18 14:45             ` Henry Gebhardt
2011-05-18 14:51               ` Samuli Suominen
2011-05-18 15:02                 ` [gentoo-dev] " Jonathan Callen
2011-05-17 19:48       ` [gentoo-dev] " Nirbheek Chauhan
2011-05-17 20:00         ` Olivier Crête
2011-05-17 20:07           ` Michał Górny
2011-05-17 20:11           ` Amadeusz Żołnowski
2011-05-17 20:23           ` Rich Freeman
2011-05-17 20:20         ` Panagiotis Christopoulos
2011-05-17 20:28           ` Michał Górny
2011-05-17 20:54           ` Olivier Crête
2011-05-17 21:00             ` Nirbheek Chauhan
2011-05-17 22:26               ` Drake Wyrm
2011-05-17 22:36                 ` Marc Schiffbauer
2011-05-17 22:46                 ` Nirbheek Chauhan
2011-05-18  0:06                 ` William Hubbs
2011-05-17 22:50 ` Ciaran McCreesh
2011-05-18  0:12   ` William Hubbs
2011-05-23  6:30     ` Ciaran McCreesh
2011-05-23  7:05       ` Nirbheek Chauhan
2011-05-23  7:11         ` Ciaran McCreesh
2011-05-23  7:13         ` Michał Górny
2011-05-23  8:30           ` Nirbheek Chauhan
2011-05-20  8:58 ` Luca Barbato
2011-05-20 16:54   ` Mike Pagano
2011-05-22 19:13     ` Luca Barbato
2011-05-22 21:12       ` Ondřej Súkup

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=201105172120.21684.miknix@gentoo.org \
    --to=miknix@gentoo.org \
    --cc=gentoo-dev@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