Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org, ml@communistcode.co.uk
Subject: Re: [PATCH 0/4]Add FUSE: File system in Userspace
Date: Thu, 30 May 2013 11:38:51 +0100	[thread overview]
Message-ID: <1469273.QNnC6eK3nT@helios> (raw)
In-Reply-To: <51A71980.30802@communistcode.co.uk>

On Thursday 30 May 2013 10:18:56 Jack Mitchell wrote:
> On 30/05/13 10:01, Hongxu Jia wrote:
> > Add fuse to oe-core and let target system could support
> > `ntfs' and `exfat' filesystems.
> > 
> > Test Case
> > 
> > *Steps
> > 1, preparation
> > 1 target: e-menlow
> > 2 usb sticks: one for boot and install, another for filesystem test.
> > 
> > 2, config
> > conf/local.conf:
> > 247 MACHINE ?= "emenlow-noemgd"
> > 247 IMAGE_INSTALL_append = " ntfs-3g ntfsprogs fuse-exfat exfat-utils"
> > 
> > conf/bblayers.conf:
> >    8 BBLAYERS ?= " \
> >    9   /home/jiahongxu/yocto/poky/meta \
> >   
> >   10   /home/jiahongxu/yocto/poky/meta-yocto \
> >   11   /home/jiahongxu/yocto/poky/meta-yocto-bsp \
> >   12   /home/jiahongxu/yocto/poky/meta-intel \
> >   13   /home/jiahongxu/yocto/poky/meta-intel/meta-emenlow \
> > 
> > 3, build image
> > bitbake core-image-sato
> > 
> > 4, load image to emenlow
> > Test Case TC-2927: boot and install from usb
> > 
> > 5, open a terminal/ssh of e-menlow
> > Test Case TC-2955: remote access by ssh
> > 
> > 6, make exfat filesystem on the testing usb storage
> > 1) plug usb stick into e-menlow
> > 2) execute `mkfs.exfat /dev/sdc1'
> > 
> > 7, test usb stick with exfat filesystem is accessible
> > Test Case TC-2947: usb mount
> > Test Case TC-2948: usb read files
> > Test Case TC-2949: usb umount
> > Test Case TC-2950: usb write files
> > 
> > 8, make ntfs filesystem on the testing usb storage
> > 1) plug usb stick into e-menlow, if mounted, invoke `umount /dev/sdc1'
> > first. 2) execute `mkfs.ntfs -f /dev/sdc1'
> > 
> > 9, test usb stick with ntfs filesystem is accessible
> > Test Case TC-2947: usb mount
> > Test Case TC-2948: usb read files
> > Test Case TC-2949: usb umount
> > Test Case TC-2950: usb write files
> > 
> > *Expected Results:
> > 1, build image success
> > 
> > 2, make exfat filesystem success
> > root@emenlow-noemgd:~# mkfs.exfat /dev/sdc1
> > mkexfatfs 1.0.1
> > Creating... done.
> > Flushing... done.
> > File system created successfully.
> > 
> > 3, make ntfs filesystem success
> > root@emenlow-noemgd:~# mkfs.ntfs -f /dev/sdc1
> > Cluster size has been automatically set to 4096 bytes.
> > Creating NTFS volume structures.
> > mkntfs completed successfully. Have a nice day.
> > 
> > 4, While the usb's filesystem type is exfat or ntfs, system can mount
> > plugged usb automatically, read files from usb, write files to usb and
> > unmout usb automatically.
> > 
> > [YOCTO #4178]
> > 
> > The following changes since commit 
350c36fcd97e8ef223b91e548d39c346c1c4cb29:
> >    bitbake: test/fetch: Allow the conditional network tests to work under
> >    python 2.6 (2013-05-17 12:42:08 +0300)> 
> > are available in the git repository at:
> >    git://git.pokylinux.org/poky-contrib hongxu/support-fuse
> >    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/support-fu
> >    se
> > 
> > Hongxu Jia (4):
> >    fuse: import recipe from meta-oe
> >    ntfs-3g-ntfsprogs:import and update recipe from meta-oe
> >    fuse-exfat: add version 1.0.1
> >    exfat-utils: add version 1.0.1
> >   
> >   meta/recipes-support/exfat/exfat-utils_1.0.1.bb    |   29 ++++++++++
> >   meta/recipes-support/exfat/fuse-exfat_1.0.1.bb     |   26 +++++++++
> >   meta/recipes-support/fuse/fuse-2.9.2/aarch64.patch |   20 +++++++
> >   .../fuse/fuse-2.9.2/gold-unversioned-symbol.patch  |   60
> >   ++++++++++++++++++++ meta/recipes-support/fuse/fuse_2.9.2.bb           
> >   |   38 +++++++++++++ .../ntfs-3g-ntfsprogs_2013.1.13.bb                
> >   |   33 +++++++++++ 6 files changed, 206 insertions(+)
> >   create mode 100644 meta/recipes-support/exfat/exfat-utils_1.0.1.bb
> >   create mode 100644 meta/recipes-support/exfat/fuse-exfat_1.0.1.bb
> >   create mode 100644 meta/recipes-support/fuse/fuse-2.9.2/aarch64.patch
> >   create mode 100644
> >   meta/recipes-support/fuse/fuse-2.9.2/gold-unversioned-symbol.patch
> >   create mode 100644 meta/recipes-support/fuse/fuse_2.9.2.bb
> >   create mode 100644
> >   meta/recipes-support/ntfs-3g-ntfsprogs/ntfs-3g-ntfsprogs_2013.1.13.bb
>
> Without trying to be difficult, is oe-core really the place to support
> and spend effort ensuring NTFS/exFAT formatted drives are supported?
> 
> Could these improvements not stay in meta-oe? I don't really see support
> for essentially propriety filesystems as a core feature of a Linux build.
> 
> Shout up if I'm talking nonsense, just my 2p.

That was also my comment on the bug report, FWIW:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=4178

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-05-30 10:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30  9:01 [PATCH 0/4]Add FUSE: File system in Userspace Hongxu Jia
2013-05-30  9:01 ` [PATCH 1/4] fuse: import recipe from meta-oe Hongxu Jia
2013-05-30  9:01 ` [PATCH 2/4] ntfs-3g-ntfsprogs:import and update " Hongxu Jia
2013-05-30  9:01 ` [PATCH 3/4] fuse-exfat: add version 1.0.1 Hongxu Jia
2013-05-30  9:01 ` [PATCH 4/4] exfat-utils: " Hongxu Jia
2013-05-30  9:18 ` [PATCH 0/4]Add FUSE: File system in Userspace Jack Mitchell
2013-05-30 10:38   ` Paul Eggleton [this message]
2013-05-30 12:17   ` Mark Hatle
2013-05-30 12:58     ` Philip Balister
2013-05-30 15:49       ` Mark Hatle
2013-05-30 16:13         ` Phil Blundell
2013-05-30 16:18           ` Mark Hatle
2013-06-03 11:20             ` Philip Balister
2013-06-03 14:22               ` Mark Hatle
2013-05-30 16:56         ` Khem Raj
2013-05-30 16:59           ` Mark Hatle

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=1469273.QNnC6eK3nT@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=ml@communistcode.co.uk \
    --cc=openembedded-core@lists.openembedded.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