From: Hamish Moffatt <hamish@cloud.net.au>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mkfs.ubifs: device table support
Date: Fri, 28 Mar 2008 18:07:56 +1100 [thread overview]
Message-ID: <20080328070756.GA319@cloud.net.au> (raw)
In-Reply-To: <1206686574.3856.66.camel@sauron>
Hi,
On Fri, Mar 28, 2008 at 08:42:54AM +0200, Artem Bityutskiy wrote:
> On Fri, 2008-03-28 at 17:24 +1100, Hamish Moffatt wrote:
> > Are there any plans to add support for a device table in mkfs.ubifs,
> > similar to mkfs.jffs2, genext2fs etc?
>
> Not sure what is this for actually :-) Could you please elaborate?
You provide a list of device nodes that you want to be included in the
created image, but you don't need to actually create them on your host
file system so you don't need to be root. They are just added to the
image automatically by mkfs.jffs2 etc.
Here's an example table from buildroot:
# Normal system devices
#<name> <type> <mode> <uid> <gid> <major> <minor> <start> <inc> <count>
/dev/mem c 640 0 0 1 1 0 0 -
/dev/kmem c 640 0 0 1 2 0 0 -
/dev/null c 666 0 0 1 3 0 0 -
/dev/zero c 666 0 0 1 5 0 0 -
/dev/random c 666 0 0 1 8 0 0 -
/dev/urandom c 666 0 0 1 9 0 0 -
/dev/ram b 640 0 0 1 1 0 0 -
/dev/ram b 640 0 0 1 0 0 1 4
/dev/loop b 640 0 0 7 0 0 1 2
[snip]
The last entry for example creates /dev/loop0 through /dev/loop7.
> I glanced at mkfs.jffs2.c it does not look difficult, so we may
> implement it if you need - no problem.
That would be very useful for me and for buildroot, which uses that option
on genext2fs and mkfs.jffs2.
thanks,
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-03-28 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 6:24 mkfs.ubifs: device table support Hamish Moffatt
2008-03-28 6:42 ` Artem Bityutskiy
2008-03-28 7:07 ` Hamish Moffatt [this message]
2008-04-02 13:46 ` Artem Bityutskiy
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=20080328070756.GA319@cloud.net.au \
--to=hamish@cloud.net.au \
--cc=dedekind@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).