Mime-Version: 1.0
Sender: jpcharlier@panther.localhost
X-Newsreader: knews 1.0b.1
From: charlj@netscape.net
Subject: minix fs limitations
Newsgroups: comp.os.minix
Content-Type: text/plain; charset=us-ascii
NNTP-Posting-Host: user49-204.jakinternet.co.uk
Message-ID: <39eb875c$1@news.jakinternet.co.uk>
Date: 16 Oct 2000 23:55:24 GMT
X-Trace: 16 Oct 2000 23:55:24 GMT, user49-204.jakinternet.co.uk
Lines: 11
Path: news.adfa.edu.au!clarion.carno.net.au!news0.optus.net.au!news1.optus.net.au!optus!news.mel.connect.com.au!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!diablo.netcom.net.uk!netcom.net.uk!tank.news.pipex.net!pipex!warm.news.pipex.net!pipex!news.jakinternet.co.uk!user49-204.jakinternet.co.uk
Xref: news.adfa.edu.au comp.os.minix:35932

I've been trying to find out what major file-system limitations exist with minix. So far I have found on the net that the minix fs imposes a 64MB partition / filesize limit and has something like a 14 char. limit on filenames. Are there any other major limitations imposed by the minix fs with reference to the following:

	the superblock;
	inodes;
	directories;
	the zone bitmap;
	the free space bitmap.

I would appreciate it if someone could point out the general area to look at with regards to the minix source code.

Thanks in advance.
