[OpenAFS-devel] 1.2.8 on HP-UX 11.00

[Neulinger, Nathan]

I kindof wonder if we should hardcode that into afsd with a statfs call
and a check against f_type, and at least generate an error message at
startup instead of letting the kernel panic.

Not sure if it should be a check-for-known-bad or check-for-known-good
type check though. The latter means that new filesystems aren't likely
to be checked. Probably the former - checking specifically for things we
know that DON'T work would be best.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Todd M. Lewis [mailto:utoddl@email.unc.edu]=20
> Sent: Thursday, April 17, 2003 8:32 AM
> To: openafs-devel@openafs.org
> Subject: Re: [OpenAFS-devel] 1.2.8 on HP-UX 11.00
>=20
>=20
>=20
>=20
> Derrick J Brashear wrote:
> > So it gets in the archive, the answer to this is "don't use VxFS for
> > cache, use (I think it's) hfs. (The vendor's standard ufs=20
> filesystem)
> >=20
> > This probably belongs in some documentation we don't have yet.
>=20
> What about=20
> http://grand.central.org/twiki/bin/view/AFSLore/AdminFAQ#3_29_
What_underlying_filesystems=20
and
http://grand.central.org/twiki/bin/view/AFSLore/SupportedConfigurations,
specifically the last line in the last table that says:
    These Don't Work 	 reiserfs, vxfs (HP-UX)
--=20
     +-------------------------------------------------------------+
    /Todd_Lewis@unc.edu  919-962-5273  http://www.unc.edu/~utoddl /
   /   A picture is worth a thousand words, or in the case of    /
  /     modern art, the same word repeated a thousand times.    /
+-------------------------------------------------------------+

_______________________________________________
OpenAFS-devel mailing list
OpenAFS-devel@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-devel