From: Steven Scholz <steven.scholz@imc-berlin.de>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: SELF and JFFS2????
Date: Wed, 26 Jun 2002 08:40:38 +0200 [thread overview]
Message-ID: <3D1961E6.AEB50722@imc-berlin.de> (raw)
Hi there,
has anyone successfully used DENX SELF to create an root fs _and_ put it then on
a JFFS2 partion?
I would like to create a flash disk just as easy as you can create a ramdisk
with SELF.
But for now the problem is that mkfs.jffs2 does _not_ handle (busybox) hardlinks
correctly - well at least not the way I want.
Thanks,
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-06-26 6:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 6:40 Steven Scholz [this message]
2002-06-26 8:37 ` SELF and JFFS2???? Alex Zeffertt
-- strict thread matches above, loose matches on Subject: below --
2002-06-26 13:51 Marius Groeger
2002-06-26 14:04 Mészáros Lajos
[not found] <Pine.LNX.4.40.0206270929001.565-100000@mag.devdep.sysgo.de>
2002-06-27 8:04 ` Steven Scholz
2002-06-27 8:22 ` Marius Groeger
2002-06-27 8:34 ` Steven Scholz
2002-06-27 9:03 ` Marius Groeger
2002-06-27 19:59 ` Wolfgang Denk
2002-06-27 19:59 ` Wolfgang Denk
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=3D1961E6.AEB50722@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).