summaryrefslogtreecommitdiff
path: root/usr.sbin/mscdlabel
AgeCommit message (Collapse)Author
2012-08-10Remove many HAVE_GCC || HAVE_PCC conditionals as the options also applyjoerg
to Clang. Add a few cases of HAVE_LLVM for -fno-strict-aliasing.
2011-06-20remove most of the remaining HAVE_GCC tests that are always true inmrg
the modern world.
2008-08-29Wrap compiler-specific flags with HAVE_GCC and HAVE_PCC as necessary. Add a ↵gmcgarry
few flags for PCC.
2007-05-28Add new Makefile knob, USE_FORT, which extends USE_SSP by turning on thetls
FORTIFY_SOURCE feature of libssp, thus checking the size of arguments to various string and memory copy and set functions (as well as a few system calls and other miscellany) where known at function entry. RedHat has evidently built all "core system packages" with this option for some time. This option should be used at the top of Makefiles (or Makefile.inc where this is used for subdirectories) but after any setting of LIB. This is only useful for userland code, and cannot be used in libc or in any code which includes the libc internals, because it overrides certain libc functions with macros. Some effort has been made to make USE_FORT=yes work correctly for a full-system build by having the bsd.sys.mk logic disable the feature where it should not be used (libc, libssp iteself, the kernel) but no attempt has been made to build the entire system with USE_FORT and doing so will doubtless expose numerous bugs and misfeatures. Adjust the system build so that all programs and libraries that are setuid, directly handle network data (including serial comm data), perform authentication, or appear likely to have (or have a history of having) data-driven bugs (e.g. file(1)) are built with USE_FORT=yes by default, with the exception of libc, which cannot use USE_FORT and thus uses only USE_SSP by default. Tested on i386 with no ill results; USE_FORT=no per-directory or in a system build will disable if desired.
2006-05-25Coverity CID 3214: Check getrawpartition return code.christos
2006-05-11sprinkle some -fno-strict-aliasing and -Wno-pointer-sign with GCC4.mrg
2005-09-14cosmetics: strip trailing blanks when the ISO volume label is printeddrochner
2005-07-25Allow the test for ISO9660 filesystems to be applied to non-CD devicesdrochner
and plain file images too. If no TOC can be read, a single track is assumed which spans the whole thing. The disklabel will be updated if supported by the device. If not, just the ISO volume label information will be printed.
2004-07-04-before adding a "partition", check for an ISO9660 filesystem,drochner
and print out volume label and creation time -if the drive cannot be open()ed read-write, try read-only and print the information
2002-11-30clean up {LD,DP}ADD. no need to set WARNS=1 herelukem
2002-09-18use NETBSDSRCDIR as appropriatelukem
2002-05-30Sort SEE ALSO.wiz
2002-05-29to complement my recent kernel changes: add a small tool to build adrochner
disklabel (in-core one, of course) from a CD TOC, which is useful to access previous sessions on a multi-session CD