mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Mose <imcol@unicyclist.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How to start on new db-based FS?
Date: Sun, 28 Jul 2002 21:00:38 +0200	[thread overview]
Message-ID: <20020728210038.A3864@unicyclist.com> (raw)
In-Reply-To: <3D434CD3.7010807@namesys.com>

Hans Reiser wrote:
> Daniel Mose wrote:
> >I'm doing a scan on the web for disk storage layout documentation on
> >different file systems. I have I think, downloaded just about all 
> >there is to download on www.namesys.com, but I fail to find anything
> >that does describe the reiserfs storage layout in any detail.
> >Is there such documentation available? 

I do believe that I've been somewhat unclear. What I would hope 
to find is :
Documentation of On-disk Per-partition storage layout 
of file lookup and maintainance structures for reiserfs. 

> >I would be very happy for directions to it in this case.
> >
> >Reason? I want to know if the root file system that I my self is 
                                 ^^^^^^^^^^^^^^^^
Correction, Should be: File system for root mountable partitions. 

> >about to develop perhaps is already implemented to some extent in
> >any existing root FS:s ? 
                ^^^^^^^^^ 
same correction here.
> 
> What is a root filesystem? (I am accustomed to the term as describing 
> what the OS uses for storing the semantic layer's root directory).

I do not have a CS - convention, or Unix background, so I am a bit
unfamiliar with terms like "semantic layer's root directory" 
I am a "learn by doing" type of guy, and up to now it has worked out
ok.

There seems to be a lot of discrepancies when it comes to 
defining what a "file system" really is. I often find that the 
term is used with widely different meanings, depending on who 
you are actually talking to, and also in what context it is used.  

I believe that the developers at www.oss.sgi, as well as the JFS 
developers hosted at IBM, use the term: "root file system" to make 
clear that 

A.	It is a Unix type of file system, that can be used as "/"
	at boot, i e a system "magically" mountable root partition.
	
B.	The file system occupies a Local mountable disk partition, 
	and is acessible via the  Unix mount command.

C.	The file system is used for file access, and maintainance of 
	On-disk	file-lookup hierarchies, such as one or more 
	Superblocks, File allocation scheemes ( f ex allocation group 
	descriptors,block and inode bitmap tables, as well as inodes )
	and Directory files ( ext2fs or FFS )

I hope that this makes a bit more sense to you.
Thank you for taking time with me, all the same

I'm happy for any further direction.

kind regards 
Daniel Mose

  parent reply	other threads:[~2002-07-28 19:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-26 16:07 Johnny Q. Hacker
2002-07-26 19:05 ` Jose Luis Domingo Lopez
2002-07-26 20:15   ` Hans Reiser
2002-07-27 20:08     ` Daniel Mose
2002-07-28  1:45       ` Hans Reiser
2002-07-28  3:43         ` Matthew D. Pitts
2002-07-28 22:32           ` Daniel Mose
2002-07-28 19:00         ` Daniel Mose [this message]
2002-07-28 19:56           ` Hans Reiser
2002-07-28 21:02 ` Christian Jaeger

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=20020728210038.A3864@unicyclist.com \
    --to=imcol@unicyclist.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    /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

all inboxes | Powered by JetHome®