From: Scott Kapu <kapus1@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: DOC write access...
Date: Tue, 19 Feb 2002 12:30:03 -0800 (PST) [thread overview]
Message-ID: <20020219203003.3976.qmail@web10806.mail.yahoo.com> (raw)
Hello,
I'd like to thank you for all the tips I've received
from the postings...
I'm using a DiskOnChip (288M) and a PC104 PPM-520 SBC
by WinSystems.
I have loaded the the CVS patches (downloaded within
past 2 weeks) on a 2.4.17 kernel tree. Created Inodes
compiled etc FINE. FDISK'ed the /dev/ntfla device,
creating nftla1 looks like...
-------------------------------------------------
Command (m for help):
Disk /dev/nftla: 1 heads, 577728 sectors, 1 cylinders
Units = cylinders of 577728 * 512 bytes
Device Boot Start End Blocks Id
System
/dev/nftla1 1 1 288863+ 83
Linux
Partition 1 has different physical/logical endings:
phys=(768, 0, 0) logical=(0, 0, 577728)
Partition 1 does not end on cylinder boundary:
phys=(768, 0, 0) should be (768, 0, 577728)
------------------------------------------------
Despite above, mounting the partition appears to work
and looking at the results of 'df -k' looks as
expected.
trying to touch a file yields...
--------------------------------------------------
EXT2-fs error (device nftl(93,1)): ext2_check_page:
bad extry in directory #2: rec_len is smaller than
minimal - offset=0, inode=0, rec_len=0, name_len=0
--------------------------------------------------
Any help where I've gone wrong(or how to fix) is
appreciated.
Also is JFFS or JFFS2 required or can/should I use
ext2 type?
In addition I'm new to the MTD hardware and it is my
intention to boot an embedded computer from DOC. Any
advice as to the best configuration, filesystem type,
strategies (ie boot compressed image to RAM disk,
partitions/no_partitions etc) is appreciated!!!
Thankyou in advance
-Scott K.
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com
reply other threads:[~2002-02-19 20:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020219203003.3976.qmail@web10806.mail.yahoo.com \
--to=kapus1@yahoo.com \
--cc=linux-mtd@lists.infradead.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