Date: Tue, 02 Jan 1996 12:20:45 +0100 From: "Julian H. Stacey" <jhs@vector.jhs.local> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: minor change to ls -l Message-ID: <199601021120.MAA01188@vector.jhs.local> In-Reply-To: Your message of "Mon, 01 Jan 1996 19:55:26 %2B0100." <199601011855.TAA23513@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Reference: > By now, two people complained about this being inconsistent. I'm one who said `inconsistent', but it was not meant as a complaint, I'd suggest we take the idea, extend & regularise it perhaps :-) If we go Hex, we should probably go Hex for <= 255 as well as > 256; apart from esthetics, it'll also make it easier if someone wants to feed ls into awk or some such. Hopefully we might bring regularity to our part of the computer world, & not add to history's evolutionary heap : - variant Unix flags for similar functionality ( -v , -verbose, etc) - excess CPU baggage from Intel incremental growth (Segments !) - Ebcdic - variant nomenclature as in the old VMS file system delimeters I'd suggest flags to ls to make it do both major & minor all in hex, or all in decimal; which should be the default I'm not sure, perhaps decimal, ( else conversion of default from decimal to hex might deter recruiting of new users from the non-programmers community ). Other things we should change as well: - mknod.c & mknod.1 to accept Hex as well as Decimal, - change MAKEDEV to use hex not decimal - manuals in section 4 maybe ? Julian. -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601021120.MAA01188>