From: Ralf Baechle <ralf@linux-mips.org>
To: Alex deVries <adevries@linuxcare.com>
Cc: Florian Lohoff <flo@rfc822.org>, linux-mips@linux-mips.org
Subject: Re: Format of bootable Indy CDs?
Date: Thu, 26 Sep 2002 23:31:57 +0200 [thread overview]
Message-ID: <20020926233157.A30002@linux-mips.org> (raw)
In-Reply-To: <3D937609.3010201@linuxcare.com>; from adevries@linuxcare.com on Thu, Sep 26, 2002 at 05:03:05PM -0400
On Thu, Sep 26, 2002 at 05:03:05PM -0400, Alex deVries wrote:
> > On Thu, Sep 26, 2002 at 03:20:06PM -0400, Alex deVries wrote
> >>What open source tools do we have to create such an EFS filesystem?
> >
> > None. The in-kernel EFS filesystem is read-only.
>
> Okay. Let me look at that.
>
> EFS seems pretty simple, but is there a filesystem described apart from
> the .h files?
No. EFS is not a very complex filesystem, roughly as complex as for example
UFS.
However later PROMs also know about XFS I think and that's the trivial
case. Anyway, as afair the EFS CDROMs are partitioned like disks a
bootloader there could also be made to contain something like libext2fs and
boot the rest of a ext2 on the CDROM. ISOfs if you have a nice library
to use for that.
Ralf
next prev parent reply other threads:[~2002-09-26 21:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 7:32 Format of bootable Indy CDs? Alex deVries
2002-09-26 17:10 ` Florian Lohoff
2002-09-26 19:20 ` Alex deVries
2002-09-26 20:56 ` Ralf Baechle
2002-09-26 21:03 ` Alex deVries
2002-09-26 21:31 ` Ralf Baechle [this message]
2002-09-26 22:17 ` Florian Lohoff
2002-09-27 0:23 ` Mike Nugent
2002-09-27 1:52 ` Florian Lohoff
2002-09-27 16:00 ` Florian Lohoff
2002-09-27 16:06 ` Florian Lohoff
2002-09-27 21:08 ` Alex deVries
2002-09-27 21:17 ` Florian Lohoff
2002-09-27 21:51 ` Maciej W. Rozycki
2002-09-27 16:22 ` Alex deVries
2002-09-27 17:20 ` Len Sorensen
-- strict thread matches above, loose matches on Subject: below --
2002-09-26 22:29 Michael Hill
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=20020926233157.A30002@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=adevries@linuxcare.com \
--cc=flo@rfc822.org \
--cc=linux-mips@linux-mips.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.