On Thu, 8 Jun 2000, Kris Kennaway wrote:

> >     Count both, nwfs and smbfs, because any program can attempt to
> > create temporary file on these filesystems. File with an invalid file name
> > will be rejected, and this will cost an additional lookup operation(s).
> I'm not sure that weird filesystems are a valid argument against mktemp()
> naming - there are LOTS of UNIX code which assumes UNIX namespace
> conventions, and it's not just mktemp() which is going to break on weird
> filesystems. For example, should we limit all FreeBSD file names to 8.3
> single-case in case someone wants to run from an old-style MSDOS
> partition?

        Well, nwfs and smbfs filesystems usually used when one need to
integrate FreeBSD machine in the already existing environment. So, the
question is simple - do we need to help interoperability or not ?

        8.3 format filenames are probably obsolete, and there is no reason
to support them because nearly all server platforms support long file
> Basically, I think the answer is not to use a nwfs or smbfs filesystem as
> your TMPDIR :-)

        With mktemp() function you can create tempoary files anywhere, not
just in TMPDIR.

Boris Popov

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to