From owner-freebsd-questions Tue Apr 3 8: 5:34 2001 Delivered-To: freebsd-questions@freebsd.org Received: from zogbe.tasam.com (hc6526bd1.dhcp.vt.edu [198.82.107.209]) by hub.freebsd.org (Postfix) with ESMTP id 2D96837B71B for ; Tue, 3 Apr 2001 08:05:30 -0700 (PDT) (envelope-from clash@fireduck.com) Received: from battleship (hc6526bd1.dhcp.vt.edu [198.82.107.209]) by zogbe.tasam.com (8.11.3/8.11.3) with SMTP id f33F5SD45393 for ; Tue, 3 Apr 2001 11:05:28 -0400 (EDT) Message-ID: <001a01c0bc4f$844e82f0$dc02010a@battleship> From: "Joseph Gleason" To: Subject: Filesystem character limitations? Date: Tue, 3 Apr 2001 11:05:26 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does the UFS filesystem used by freebsd allow any character value in file names? Suppose I create a C program that calls mkdir(2) to create a directory, what are the limitations on the directory name? Can it contain characters > 127? Can it contain 255? Can it contain null(0)? Currently I am not worried about if any utilities can deal with or display these file names..I am just wondering if it is possible and what the limitations are. Thanks for your time. Joseph Gleason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message