From owner-freebsd-current Mon Jul 6 05:29:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00958 for freebsd-current-outgoing; Mon, 6 Jul 1998 05:29:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA00949 for ; Mon, 6 Jul 1998 05:29:12 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id QAA12991; Mon, 6 Jul 1998 16:28:15 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Mon, 6 Jul 1998 16:28:15 +0400 (MSD) From: Hostas Red To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD in less than 4MB RAM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Mon, 6 Jul 1998, Andrzej Bialecki wrote: > The second issue is this: currently we're unable to boot (using BIOS) and > mount as / other filesystems than FFS, NFS and CD9660. It would be great > if we could use MSDOSFS as well (using special version of biosboot, with > FAT support compiled-in instead of FFS). Device nodes would be on DEVFS. > > What for? This could help get rid of fbsdboot.exe and related troubles - > we could just directly start and run (and install!) on MSDOS partition. I think, in that case we will need some system files with "extended attributes", like in OS/2-on-FAT, to keep longnames (FAT16), ownership and file modes. :) It's not so good solution, but without this we will have no security at all :( Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message