From owner-freebsd-hackers Thu May 11 06:30:07 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA00169 for hackers-outgoing; Thu, 11 May 1995 06:30:07 -0700 Received: from sass165.sandia.gov (sass165.sandia.gov [132.175.109.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA00161 for ; Thu, 11 May 1995 06:30:06 -0700 Received: from sargon.mdl.sandia.gov (sargon.mdl.sandia.gov [134.253.20.128]) by sass165.sandia.gov (8.6.11/8.6.12) with ESMTP id HAA03536 for ; Thu, 11 May 1995 07:32:39 -0600 Received: (aflundi@localhost) by sargon.mdl.sandia.gov (8.6.10) id HAA19188 for hackers@freebsd.org; Thu, 11 May 1995 07:26:36 -0600 Message-Id: <199505111326.HAA19188@sargon.mdl.sandia.gov> From: aflundi@sandia.gov (Alan F Lundin) Date: Thu, 11 May 1995 07:26:36 -0600 In-Reply-To: Warner Losh "Re: question on sun cds" (May 10, 10:13pm) X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: hackers@FreeBSD.org Subject: Re: question on sun cds Sender: hackers-owner@FreeBSD.org Precedence: bulk On May 10, 10:13pm, Warner Losh wrote: > Subject: Re: question on sun cds > > : The big buggaboo is the volume label and directory entry structure > : differences that SunOS has. The zeroed inode number as a tag for an > : empty file system block is "different" in the directory entries > : themselves. > > Where might I find out about these differences? > > : If you were trying to write a FS for a Solaris box instead, that'd be > : a much bigger pain (it'd have to be kernel preeemption safe and Sun > : did it the wrong way, IMO). > > Since I don't need to worry about writing to a cd with the setup I > have, I can punt on this :-). Doesn't Sun just use the High Sierra CDROM format? (# mount -rt hsfs /dev/sr0 /cdrom) --alan