Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] New package: kmod
Date: Wed, 18 Jan 2012 00:04:02 +0100	[thread overview]
Message-ID: <871uqyorrx.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <201201180000.22317.arnout@mind.be> (Arnout Vandecappelle's message of "Wed, 18 Jan 2012 00:00:21 +0100")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 Arnout> On Tuesday 17 January 2012 23:13:08 Yegor Yefremov wrote:
 >> As we came to this topic, what is your opinion on adding /run? It also
 >> became udev's dependency.

 Arnout>  IIRC /run basically replaces /var/run in Fedora, Debian, SuSE
 Arnout> and others.  Since we anyway symlink /var/run to /tmp, we can
 Arnout> easily do the same for /run.

That's my understanding as well. I don't have any issues with adding a
/run symlink to fs/skeleton.


-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-01-17 23:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-16 15:04 [Buildroot] [PATCH 1/2] ethtool: bump to 3.2 yegorslists at googlemail.com
2012-01-16 15:04 ` [Buildroot] [PATCH 2/2] New package: kmod yegorslists at googlemail.com
2012-01-16 15:18   ` Peter Korsgaard
2012-01-16 17:45   ` Arnout Vandecappelle
2012-01-16 19:27     ` Peter Korsgaard
2012-01-17 13:57       ` Arnout Vandecappelle
2012-01-17 14:15         ` Peter Korsgaard
2012-01-17 22:13           ` Yegor Yefremov
2012-01-17 22:32             ` Stephan Raue
2012-01-17 23:00             ` Arnout Vandecappelle
2012-01-17 23:04               ` Peter Korsgaard [this message]
2012-01-17 23:15                 ` Yegor Yefremov
2012-01-16 15:18 ` [Buildroot] [PATCH 1/2] ethtool: bump to 3.2 Peter Korsgaard

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=871uqyorrx.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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