public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] udev or mdev?
Date: Wed, 21 Mar 2012 16:39:18 +0700	[thread overview]
Message-ID: <CAA2qdGXH-Hj_xqRdqrTENV9erbkKkVXMDBz4ZeRH+C_vjG8sHw@mail.gmail.com> (raw)
In-Reply-To: <4F699DC3.6030805@loginet.hu>

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

On Mar 21, 2012 4:23 PM, "Halassy Zoltán" <zhalassy@loginet.hu> wrote:
>>
>> IMO, initramfs adds yet another black box during server boot.
>
>
> The other way around, for me at least. I build my own initramfs, yet I
don't know anything about mdev, just the fact it's part of busybox. So for
me, mdev is a black box, while my initramfs definitely isn't.
>
>

I see. Well, different views for different people, I guess.

It's easier for me to bypass mdev (if it's b0rken) than to bypass initramfs.

>> And yet
>> another daemon in memory, something I certainly don't need on my static
>> virtualized servers.
>
>
> I agree with that. But why do you need mdev for a static system? A few
mknods would suffice.
>

It allows triggered action when I (for example) attach a (virtual) hard
disk to my VM.

Rgds,

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

  reply	other threads:[~2012-03-21 12:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA2qdGVQMrmG_LFfoy7gwr-hfyhzUkubGwnE-K-nL2SdB_SKqQ@mail.gmail.com>
2012-03-19  0:15 ` [gentoo-server] udev or mdev? Pandu Poluan
2012-03-19  1:32   ` Kalin KOZHUHAROV
2012-03-19  2:04     ` Pandu Poluan
2012-03-19 10:38   ` Halassy Zoltán
2012-03-21  6:20     ` Pandu Poluan
2012-03-21  9:22       ` Halassy Zoltán
2012-03-21  9:39         ` Pandu Poluan [this message]
2012-03-22  2:17           ` Daniel Reidy
2012-03-23 13:35             ` Drew
2012-03-26 21:11           ` BRM

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=CAA2qdGXH-Hj_xqRdqrTENV9erbkKkVXMDBz4ZeRH+C_vjG8sHw@mail.gmail.com \
    --to=pandu@poluan.info \
    --cc=gentoo-server@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