All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Olaf Hering <olh@suse.de>, Greg KH <greg@kroah.com>,
	Kyle Moffett <mrmacman_g4@mac.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] ndevfs - a "nano" devfs
Date: Wed, 29 Jun 2005 02:08:41 +0400	[thread overview]
Message-ID: <42C1CA69.7060901@tls.msk.ru> (raw)
In-Reply-To: <20050628212518.GA26772@smtp.west.cox.net>

Tom Rini wrote:
> On Tue, Jun 28, 2005 at 11:08:04PM +0200, Olaf Hering wrote:
[]
>>>Er, don't you need /dev/console for console output to happen? (And that
>>>it's a good idea to have /dev/null around too).  Or has that changed?
>>
>>scripts/gen_initramfs_list.sh creates that for every kernel.
> 
> I get "Warning: unable to open initial console", so on post 2.6.12 (but
> now stale) git.  Does userspace need to be doing something as well?

Are you using initramfs (cpio archive of the root fs)?
Or "ol'good" initrd (cramfs, romfs, whatever)?

/mjt

  reply	other threads:[~2005-06-28 22:12 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24  8:18 [ANNOUNCE] ndevfs - a "nano" devfs Greg KH
2005-06-24 12:23 ` Michael Tokarev
2005-06-24 15:16   ` Greg KH
2005-06-24 15:40     ` Michael Tokarev
2005-06-24 16:26       ` Greg KH
2005-06-24 14:32 ` Bill Gatliff
2005-06-24 15:17 ` Steven Rostedt
2005-06-24 15:20   ` Greg KH
2005-06-24 17:10 ` Michael Tokarev
2005-06-24 17:10 ` Bill Gatliff
2005-06-28  7:40   ` Greg KH
2005-06-24 19:05 ` Mike Bell
2005-06-24 21:55   ` J.A. Magallon
2005-06-24 19:22 ` Alexey Dobriyan
2005-06-25  0:57 ` Kyle Moffett
2005-06-25  7:37   ` Denis Vlasenko
2005-06-28  7:41   ` Greg KH
2005-06-28 19:56     ` Tom Rini
2005-06-28 21:08       ` Olaf Hering
2005-06-28 21:25         ` Tom Rini
2005-06-28 22:08           ` Michael Tokarev [this message]
2005-06-28 22:23             ` Tom Rini
2005-06-25 22:15 ` Matt Mackall
2005-06-25 23:43   ` Greg KH
2005-06-26  8:23     ` Russell King
2005-06-28  3:36       ` Greg KH
2005-06-27  7:19     ` Mike Bell
2005-06-27 22:35       ` Dmitry Torokhov
2005-06-27 23:26         ` Mike Bell
2005-06-28  7:40           ` Greg KH
2005-06-28  9:08             ` Mike Bell
2005-06-28  9:21               ` Arjan van de Ven
2005-06-28  9:40                 ` Mike Bell
2005-06-28 21:49                 ` Jim Crilly
2005-06-28 22:23                   ` Mike Bell
2005-06-28 23:43                     ` Jim Crilly
2005-06-29  0:12                       ` Mike Bell
2005-06-29  0:39                         ` David Lang
2005-06-29  0:53                           ` Mike Bell
2005-06-28 12:00             ` Oliver Neukum
2005-06-28 20:08               ` Greg KH
2005-06-29  6:41                 ` Oliver Neukum
2005-06-29 16:06                   ` Greg KH
2005-06-29 16:22                     ` Oliver Neukum
     [not found] ` <200506270819.20108.arnd@arndb.de>
2005-06-28  3:46   ` Greg KH
     [not found] <OF831AC472.851744FE-ON8025702A.004A57EC-8025702A.004B5AE9@sophos.com>
2005-06-24 15:23 ` Greg KH
2005-06-24 15:32 tvrtko.ursulin
2005-06-24 16:27 ` Greg KH
2005-06-27 15:17 Adam J. Richter
2005-06-27 15:21 Adam J. Richter
2005-06-27 23:27 ` J.A. Magallon

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=42C1CA69.7060901@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    --cc=olh@suse.de \
    --cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.