Date: Tue, 06 Oct 1998 21:35:12 -0600 From: Brett Glass <brett@lariat.org> To: "Jeffrey J. Mountin" <jeff-ml@mountin.net>, Dan Busarow <dan@dpcsys.com>, Studded <Studded@dal.net> Cc: freebsd-security@FreeBSD.ORG Subject: Re: The necessary steps for logging (the problem is fixed) Message-ID: <4.1.19981006213234.04cd1600@mail.lariat.org> In-Reply-To: <3.0.3.32.19981006205648.006e987c@207.227.119.2> References: <Pine.BSF.3.96.981006103009.16376H-100000@java.dpcsys.com> <361A4F37.141BAE11@dal.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 08:56 PM 10/6/98 -0500, Jeffrey J. Mountin wrote: >You are refering to the checking, but the original /etc/crontab's for 2.2.7 >and the 9/30 beta are mostly spaces, but the do mix tabs and spaces on the >LHS, assuming you are referring in this case to only the time/date fields. > >In 2.2.7 (v1.13) even has a tab between adjkerntz and the -a flag that the >beta (v.1.18) did not. A lot of the Vixie stuff (including his cron and BIND) treats all whitespace the same, regardless of whether you use spaces or tabs. So does Apache. So do a whole bunch of other things. There's also the problem that some editors expand tabs to spaces. In the name of consistency, I'd like to see FreeBSD (and, for that matter, ALL the BSDs) treat tabs and spaces the same, letting you quote spaces with a backslash (or quotes surrounding a string) if you want to embed them. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.1.19981006213234.04cd1600>