From: Sebastien Articlaux <sebastien_articlaux@yahoo.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Hi!
Date: Tue, 14 Mar 2000 06:19:13 -0800 (PST) [thread overview]
Message-ID: <20000314141913.16859.qmail@web219.mail.yahoo.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1150 bytes --]
Hello Wolfgang,
My last e-mails on the mailing list wasn't very
constructive...I'm agree!
So,I've made some research to inform me on the process
of creating a ramdisk.
I've learned a lot of things and now I know the good
questions to ask!
Ok, tell me if I'm wrong!
Normally there is two ramdisk, the init ramdisk and an
other,bigger wich contain the complete system.
and this is linuxrc in the initramdisk wich mount the
real ramdisk, right?
But for us,we just use the initramdisk "as ramdisk"...
It's a minimal file system but to begin it's ok,
right?
So now I'm trying to create a good initramdisk.
I've put the patch for SASH in source, but I must have
to recompile SASH (that's what I understand when I
look into your CDK files)
Where can I found the source of SASH if I must
recompile it?
Then do I must put it in /bin/sash in my initrd and
make a link?
ln -s sash sh to have /bin/sh -> sash ?
And need I have to create a linuxrc if I have just the
initrd? if yes, what must I put in it because I don't
understand.
Thanks you for your help
Sébastien ARTICLAUX
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-03-14 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-14 14:19 Sebastien Articlaux [this message]
2000-03-14 21:05 ` Hi! Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-05-12 7:29 Hi! venkata ramesh
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=20000314141913.16859.qmail@web219.mail.yahoo.com \
--to=sebastien_articlaux@yahoo.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
/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).