Message-ID: <39F4D090.3DA7DA1F@OFF.COM>
Date: Mon, 23 Oct 2000 23:58:08 +0000
From: ASFAND QAZI <BUGGER@OFF.COM>
X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.2.16 i686)
MIME-Version: 1.0
Newsgroups: comp.os.minix
Subject: Re: minix fs limitations
References: <39eb875c$1@news.jakinternet.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: user-222-232.jakinternet.co.uk
X-Trace: 23 Oct 2000 23:51:18 GMT, user-222-232.jakinternet.co.uk
Lines: 23
Path: news.adfa.edu.au!clarion.carno.net.au!news0.optus.net.au!news1.optus.net.au!optus!intgwpad.nntp.telstra.net!62.4.16.155.MISMATCH!codeine.org!diablo.netcom.net.uk!netcom.net.uk!tank.news.pipex.net!pipex!warm.news.pipex.net!pipex!news.jakinternet.co.uk!user-222-232.jakinternet.co.uk
Xref: news.adfa.edu.au comp.os.minix:35960

charlj@netscape.net wrote:
> 
> 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.

You wouldn't happen to have a course work that you need to hand in
tomorrow, 24th of October, at Cavendish campus at Westminster
University, London, England, would you?

Heh, heh, so would I.  Don't worry it's only worth 10% of the total
coursework marks for the module!!!

p.s.  If you find any other info, I'd be grateful if you would forward
it to asfand@email.com.  I'll do likewise!
