public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Bailey <jbailey@ubuntu.com>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org,
	ubuntu-devel <ubuntu-devel@lists.ubuntu.com>
Subject: Re: Keep initrd tasks running?
Date: Tue, 18 Oct 2005 17:43:35 -0400	[thread overview]
Message-ID: <1129671815.18784.115.camel@localhost.localdomain> (raw)
In-Reply-To: <43554F1C.9090901@comcast.net>

Le mardi 18 octobre 2005 à 15:38 -0400, John Richard Moser a écrit :
> > This is much more easily supported in Breezy.  usplash is started at the
> > top of the initramfs (from the init-top hook) and lives until we start
> > gdm.

> So in short it's possible?
I make no promises until I"m holding the code in my hand and have tested
it myself. =)  I don't see any reason why it wouldn't work.

> That's not much of a problem for me.  What I'm contemplating is a FUSE
> file system driver that gets started in the initrd, and a kernel that
> has a file system driver built-in for something stupid like cramfs or MINIX.

Ah, okay.  Jerry Haltom was looking at how to support booting from a
loopback filesystem (for embedded systems shiping a .bin blob) and he
was able to get it running.  This is hopefully just another twist on the
same thing.  I haven't played with FUSE, though, so I don't know what's
needed.

Lemme know if you run into specific problems.  If you have access to
IRC, I'm on freenode as jbailey in #ubuntu-devel.

Tks,
Jeff Bailey


  reply	other threads:[~2005-10-18 21:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18 19:13 Keep initrd tasks running? John Richard Moser
2005-10-18 19:29 ` Jeff Bailey
2005-10-18 19:38   ` John Richard Moser
2005-10-18 21:43     ` Jeff Bailey [this message]
2005-10-19  3:35   ` Phillip Susi
2005-10-19  4:22     ` John Richard Moser
2005-10-19 18:52       ` Phillip Susi
2005-10-23 20:40         ` Matt Zimmerman
2005-10-23 20:38       ` Matt Zimmerman
2005-10-18 19:37 ` linux-os (Dick Johnson)
2005-10-19 11:07 ` Denis Vlasenko

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=1129671815.18784.115.camel@localhost.localdomain \
    --to=jbailey@ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigelenki@comcast.net \
    --cc=ubuntu-devel@lists.ubuntu.com \
    /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