On Thu, Nov 24, 2011 at 11:56:13AM +0100, Magnus Eriksson wrote:
Why not simply ChipFS?
Seems more reasonable pronunciation-wise than the alphabet soup that
is see-age-eff-ess or the cough and spit of ch-fs.
I may be chiming in too late, but I suggest calling the filesystem
SneezeFS, because
On Wed, 23 Nov 2011 19:24:43 +0100, Adam Hoka adam.h...@gmail.com wrote:
On 11/23/2011 6:03 PM, Christos Zoulas wrote:
In article 46DA345771B043F283B5E67C674DAA76@desktop,
Adam Hoka adam.h...@gmail.com wrote:
Hi!
If no one argues otherwise, I would like to import chewiefs to the
NetBSD
On Thu, 24 Nov 2011, Tamas Toth wrote:
On Wed, 23 Nov 2011 19:24:43 +0100, Adam Hoka adam.h...@gmail.com wrote:
I'm thinking of shortening it to CHFS, and we could say it stands for
chip file system if someone asks.
CHFS would be also good for us.
Why not simply ChipFS?
Seems more
Hi!
If no one argues otherwise, I would like to import chewiefs to the NetBSD
tree.
The import would have minimal impact on existing code, but would allow for
broader testing of the code and a step towards a more embedded ready NetBSD.
Cheers.
In article 46DA345771B043F283B5E67C674DAA76@desktop,
Adam Hoka adam.h...@gmail.com wrote:
Hi!
If no one argues otherwise, I would like to import chewiefs to the NetBSD
tree.
The import would have minimal impact on existing code, but would allow for
broader testing of the code and a step towards
In article 46DA345771B043F283B5E67C674DAA76@desktop,
Adam Hoka adam.h...@gmail.com wrote:
Hi!
If no one argues otherwise, I would like to import chewiefs to the NetBSD
tree.
The import would have minimal impact on existing code, but would allow for
broader testing of the code and a step towards
On Wed, Nov 23, 2011 at 9:03 AM, Christos Zoulas chris...@astron.com wrote:
In article 46DA345771B043F283B5E67C674DAA76@desktop,
Adam Hoka adam.h...@gmail.com wrote:
Hi!
If no one argues otherwise, I would like to import chewiefs to the NetBSD
tree.
The import would have minimal impact
On 11/23/2011 6:03 PM, Christos Zoulas wrote:
In article 46DA345771B043F283B5E67C674DAA76@desktop,
Adam Hoka adam.h...@gmail.com wrote:
Hi!
If no one argues otherwise, I would like to import chewiefs to the NetBSD
tree.
The import would have minimal impact on existing code, but would
On Wed, Nov 23, 2011 at 05:03:36PM +, Christos Zoulas wrote:
If no one argues otherwise, I would like to import chewiefs to the NetBSD
tree.
The import would have minimal impact on existing code, but would
allow for broader testing of the code and a step towards a more
embedded
chris...@astron.com (Christos Zoulas) wrote:
I think that we should choose a more descriptive name for it. Having
cute project names is good during development, but we need meaningful
names for posterity that make sense to people. Imagine if we had named
nfs cutefs, ffs kirkfs, etc.
Seconded.
I'm thinking of shortening it to CHFS, and we could say it stands for
chip file system if someone asks.
FWIW, a very brief google for `CHFS filesystem` indicates no direct hits -
only matches for chfs(1), pretty much.
. Appending will be working on it, but if
you truncate it longer before remounting, the file will be filled by the
original data instead of zeros. I didn't find how i can drop the dirty
page_cache if the FS doesn't need it anymore.
But, how Adam said, the ChewieFS isn't designed for SSD.
Tamas Toth
.
YAMAMOTO Takashi
But, how Adam said, the ChewieFS isn't designed for SSD.
Tamas Toth
On Fri, 11 Nov 2011 05:06:13 +0100, Toru Nishimura
locor...@alkyltechnology.com wrote:
There are increasing number of NAND only (NOR less) embeded devices on
market. How difficult to have chewieFS LIBSA support to allow kernel
image
loading from the filesys on NAND?
Toru Nishimura
IIUC ChewieFS follows FFS format, so the problem is block device driver.
On Fri, Nov 11, 2011 at 9:15 PM, Tamas Toth tt...@inf.u-szeged.hu wrote:
On Fri, 11 Nov 2011 05:06:13 +0100, Toru Nishimura
locor...@alkyltechnology.com wrote:
There are increasing number of NAND only (NOR less) embeded
to which it is useful?
I think that i answered the first part of your question in my earlier
letter. We've those two bugs and everything else is working.
I wrote a short description to the homepage about why ChewieFS can be
useful.
http://chewiefs.sed.hu/
ttoth
Tamas Toth wrote
I don't know anyithing about LIBSA, so i can't tell you how difficult to
support it from ChewieFS.
It's a collection of code to make NetBSD loader easier. PLS look at
sys/lib/libsa/ directory. There are plenty of FS code. It's important
and promising to add ChewieFS
Hi,
We would like to introduce a new flash filesystem for NetBSD-current
(5.99.56) called ChewieFS.
More information and the source is available here: http://chewiefs.sed.hu/
It's already usable, but there are some bugs yet. We're trying to fix them
as soon as possible
It's not for SSD, but for raw flash device often found in embedded
systems, like ARM, MIPS.
There are increasing number of NAND only (NOR less) embeded devices on
market. How difficult to have chewieFS LIBSA support to allow kernel image
loading from the filesys on NAND?
Toru Nishimura / ALKYL Technology
20 matches
Mail list logo
