aboutsummaryrefslogtreecommitdiff
path: root/sbin/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* sbin: build ping if at least one of INET & INET6 is enabledEd Maste2021-11-281-1/+4
| | | | | | | | | It does not build (and serves no purpose) if neither is true (i.e., building WITHOUT_INET and WITHOUT_INET6). Also add an explicit error in ping to make this case clear. PR: 260082 Sponsored by: The FreeBSD Foundation
* Retire obsolete iscsi_initiator(4)Ed Maste2021-10-261-1/+0
| | | | | | | | | | | The new iSCSI initiator iscsi(4) was introduced with FreeBSD 10.0, and the old intiator was marked obsolete shortly thereafter (in commit d32789d95cfbf, MFC'd to stable/10 in ba54910169c4). Remove it now. Reviewed by: jhb, mav Relnotes: yes Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D32673
* Fix sconfig(8) build.Gleb Smirnoff2021-10-221-4/+0
| | | | | | | Missed that since sconfig(8) was built on i386 only. Since I enabled cp(4) on amd64, enable sconfig(8) as well. Fixes: 6aae3517ed25
* Retire synchronous PPP kernel driver sppp(4).Gleb Smirnoff2021-10-221-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The last two drivers that required sppp are cp(4) and ce(4). These devices are still produced and can be purchased at Cronyx <http://cronyx.ru/hardware/wan.html>. Since Roman Kurakin <rik@FreeBSD.org> has quit them, they no longer support FreeBSD officially. Later they have dropped support for Linux drivers to. As of mid-2020 they don't even have a developer to maintain their Windows driver. However, their support verbally told me that they could provide aid to a FreeBSD developer with documentaion in case if there appears a new customer for their devices. These drivers have a feature to not use sppp(4) and create an interface, but instead expose the device as netgraph(4) node. Then, you can attach ng_ppp(4) with help of ports/net/mpd5 on top of the node and get your synchronous PPP. Alternatively you can attach ng_frame_relay(4) or ng_cisco(4) for HDLC. Actually, last time I used cp(4) back in 2004, using netgraph(4) instead of sppp(4) was already the right way to do. Thus, remove the sppp(4) related part of the drivers and enable by default the negraph(4) part. Further maintenance of these drivers in the tree shouldn't be a big deal. While doing that, remove some cruft and enable cp(4) compilation on amd64. The ce(4) for some unknown reason marks its internal DDK functions with __attribute__ fastcall, which most likely is safe to remove, but without hardware I'm not going to do that, so ce(4) remains i386-only. Reviewed by: emaste, imp, donner Differential Revision: https://reviews.freebsd.org/D32590 See also: https://reviews.freebsd.org/D23928
* Fix bsd.subdir.mk-related issues after 0a0f7486413cJessica Clarke2021-07-121-4/+4
| | | | | | | | | | | | | Since bsd.prog.mk includes bsd.obj.mk, and thus bsd.subdir.mk, we must ensure all our bsd.subdir.mk-affecting variables are set before including bsd.prog.mk. Since sbin's various Makefile.arch files add to SUBDIR this results in those not taking effect, and presumably we also end up not having buildworld as parallel as it should be due to the fact that SUBDIR_PARALLEL was not being set before including bsd.prog.mk. MFC with: 0a0f7486413c147d56808b38055c40c64cff61f5 Reviewed by: olivier Differential Revision: https://reviews.freebsd.org/D31125
* man: Build manpages for all architecturesFernando Apesteguía2021-06-301-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | Building and installing architecture-specific man pages only raises a number of problems: * The https://www.freebsd.org/cgi/man.cgi is incomplete. As an example, it does not show results for pae(4). The reason for this is that the cgi interface runs on FreeBSD amd64. * In FreeBSD amd64 some manual pages have broken X-refs. See hptrr(4) for an example. * Also, we have broken links in our Release Notes. This is a consequence of the first point. See https://www.freebsd.org/releases/13.0R/hardware/#proc-i386. Make MAN_ARCH default to 'all' so we build all the man pages for all the architectures. The difference in disk space is negligible. Also link architecture-specific man pages to their own section while keeping their own namespace. PR: 212290 Reported by: mj@bsdops.com Approved by: ceri@, wosch@ MFC after: 4 weeks
* Merge ping6 to pingAlan Somers2020-11-261-1/+0
| | | | | | | | | | | | | There is now a single ping binary, which chooses to use ICMP or ICMPv4 based on the -4 and -6 options, and the format of the address. Submitted by: Ján Sučan <sucanjan@gmail.com> Sponsored by: Google LLC (Google Summer of Code 2019) MFC after: Never Differential Revision: https://reviews.freebsd.org/D21377 Notes: svn path=/head/; revision=368045
* Remove NAND and NANDFS supportWarner Losh2019-06-251-2/+0
| | | | | | | | | | | | | | | | | | | | | NANDFS has been broken for years. Remove it. The NAND drivers that remain are for ancient parts that are no longer relevant. They are polled, have terrible performance and just for ancient arm hardware. NAND parts have evolved significantly from this early work and little to none of it would be relevant should someone need to update to support raw nand. This code has been off by default for years and has violated the vnode protocol leading to panics since it was committed. Numerous posts to arch@ and other locations have found no actual users for this software. Relnotes: Yes No Objection From: arch@ Differential Revision: https://reviews.freebsd.org/D20745 Notes: svn path=/head/; revision=349352
* Add verifying manifest loader for mac_veriexecSimon J. Gerraty2019-02-261-0/+1
| | | | | | | | | | | This tool will verify a signed manifest and load contents into mac_veriexec for storage Sponsored by: Juniper Networks Differential Revision: D16575 Notes: svn path=/head/; revision=344567
* New pfil(9) KPI together with newborn pfil API and control utility.Gleb Smirnoff2019-01-311-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The KPI have been reviewed and cleansed of features that were planned back 20 years ago and never implemented. The pfil(9) internals have been made opaque to protocols with only returned types and function declarations exposed. The KPI is made more strict, but at the same time more extensible, as kernel uses same command structures that userland ioctl uses. In nutshell [KA]PI is about declaring filtering points, declaring filters and linking and unlinking them together. New [KA]PI makes it possible to reconfigure pfil(9) configuration: change order of hooks, rehook filter from one filtering point to a different one, disconnect a hook on output leaving it on input only, prepend/append a filter to existing list of filters. Now it possible for a single packet filter to provide multiple rulesets that may be linked to different points. Think of per-interface ACLs in Cisco or Juniper. None of existing packet filters yet support that, however limited usage is already possible, e.g. default ruleset can be moved to single interface, as soon as interface would pride their filtering points. Another future feature is possiblity to create pfil heads, that provide not an mbuf pointer but just a memory pointer with length. That would allow filtering at very early stages of a packet lifecycle, e.g. when packet has just been received by a NIC and no mbuf was yet allocated. Differential Revision: https://reviews.freebsd.org/D18951 Notes: svn path=/head/; revision=343631
* Rename be(1) to bectl(8); continues to live in /sbinKyle Evans2018-07-241-1/+1
| | | | | | | Discussed with: rpokala, allanjude Notes: svn path=/projects/bectl/; revision=336669
* Import libbe(3)/be(1) from socsvn/soc2017/kneitinger/libbe-headKyle Evans2018-07-241-0/+1
| | | | Notes: svn path=/projects/bectl/; revision=336668
* Makefiles: remove outdated commentsEitan Adler2018-06-241-2/+0
| | | | Notes: svn path=/head/; revision=335598
* NVME support is only for x86 and powerpc64.Warner Losh2018-06-141-0/+1
| | | | | | | | | | | | | | | | Implement MK_NVME now that the expression for where NVMe is complicated. Default it to "yes" for x86 and powerpc64 and no everywhere else. Use it in camcontrol to define WITH_NVME for those platforms where we support nvme. This should fix the newly introduced nvme files to camcontrol which were building everywhere. Pointy Hat To: imp Sponsored by: Netflix Notes: svn path=/head/; revision=335101
* Move devmatch to sbin from usr/sbin.Warner Losh2018-02-121-0/+1
| | | | | | | | | | Since we want to use devmatch in context before a split /,/usr system has mounted /usr, move devmatch to /sbin. Sponsored by: Netflix Notes: svn path=/head/; revision=329161
* Remove badsect(8).Konstantin Belousov2017-11-051-1/+0
| | | | | | | | | | | | | | Failure modes of the modern (that is, produced in the last 25 years) hard drives and SSDs made the utility outdated. Since the kernel interface to support it was removed in r324853, cut the userspace remnants as well. Discussed with: bde (who does not like the removal) Sponsored by: The FreeBSD Foundation MFC after: 2 weeks Notes: svn path=/head/; revision=325452
* Remove SUBDIR ordering/uniquifying in *bin/MakefileEnji Cooper2017-07-061-2/+0
| | | | | | | | | | | | | | | | | | After the addition of SUBDIR.yes, uniquifying/ordering the SUBDIRs doesn't make a whole lot of sense, and it's in effect a half measure. Ordering SUBDIR (after adding SUBDIR.yes to it) in bsd.subdir.mk is a separate change that warrants more discussion/testing, because while the SUBDIR_PARALLEL work largely fixed dependency ordering for SUBDIRs, there might be downstream FreeBSD consumers that rely on the SUBDIR ordering. MFC after: 2 months Reviewed by: bdrewery Differential Revision: D11398 Notes: svn path=/head/; revision=320701
* Remove the NATM framework including the en(4), fatm(4), hatm(4), andBrooks Davis2017-04-241-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | patm(4) devices. Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support). With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone. Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome. Reviewed by: philip Approved by: harti Notes: svn path=/head/; revision=317383
* Add support for encrypted kernel crash dumps.Konrad Witaszczyk2016-12-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changes include modifications in kernel crash dump routines, dumpon(8) and savecore(8). A new tool called decryptcore(8) was added. A new DIOCSKERNELDUMP I/O control was added to send a kernel crash dump configuration in the diocskerneldump_arg structure to the kernel. The old DIOCSKERNELDUMP I/O control was renamed to DIOCSKERNELDUMP_FREEBSD11 for backward ABI compatibility. dumpon(8) generates an one-time random symmetric key and encrypts it using an RSA public key in capability mode. Currently only AES-256-CBC is supported but EKCD was designed to implement support for other algorithms in the future. The public key is chosen using the -k flag. The dumpon rc(8) script can do this automatically during startup using the dumppubkey rc.conf(5) variable. Once the keys are calculated dumpon sends them to the kernel via DIOCSKERNELDUMP I/O control. When the kernel receives the DIOCSKERNELDUMP I/O control it generates a random IV and sets up the key schedule for the specified algorithm. Each time the kernel tries to write a crash dump to the dump device, the IV is replaced by a SHA-256 hash of the previous value. This is intended to make a possible differential cryptanalysis harder since it is possible to write multiple crash dumps without reboot by repeating the following commands: # sysctl debug.kdb.enter=1 db> call doadump(0) db> continue # savecore A kernel dump key consists of an algorithm identifier, an IV and an encrypted symmetric key. The kernel dump key size is included in a kernel dump header. The size is an unsigned 32-bit integer and it is aligned to a block size. The header structure has 512 bytes to match the block size so it was required to make a panic string 4 bytes shorter to add a new field to the header structure. If the kernel dump key size in the header is nonzero it is assumed that the kernel dump key is placed after the first header on the dump device and the core dump is encrypted. Separate functions were implemented to write the kernel dump header and the kernel dump key as they need to be unencrypted. The dump_write function encrypts data if the kernel was compiled with the EKCD option. Encrypted kernel textdumps are not supported due to the way they are constructed which makes it impossible to use the CBC mode for encryption. It should be also noted that textdumps don't contain sensitive data by design as a user decides what information should be dumped. savecore(8) writes the kernel dump key to a key.# file if its size in the header is nonzero. # is the number of the current core dump. decryptcore(8) decrypts the core dump using a private RSA key and the kernel dump key. This is performed by a child process in capability mode. If the decryption was not successful the parent process removes a partially decrypted core dump. Description on how to encrypt crash dumps was added to the decryptcore(8), dumpon(8), rc.conf(5) and savecore(8) manual pages. EKCD was tested on amd64 using bhyve and i386, mipsel and sparc64 using QEMU. The feature still has to be tested on arm and arm64 as it wasn't possible to run FreeBSD due to the problems with QEMU emulation and lack of hardware. Designed by: def, pjd Reviewed by: cem, oshogbo, pjd Partial review: delphij, emaste, jhb, kib Approved by: pjd (mentor) Differential Revision: https://reviews.freebsd.org/D4712 Notes: svn path=/head/; revision=309818
* zfsbootcfg: a simple tool to set next boot (one time) options for zfsbootAndriy Gapon2016-10-291-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | (gpt)zfsboot will read one-time boot directives from a special ZFS pool area. The area was previously described as "Boot Block Header", but currently it is know as Pad2, marked as reserved and is zeroed out on pool creation. The new code interprets data in this area, if any, using the same format as boot.config. The area is immediately wiped out. Failure to parse the directives results in a reboot right after the cleanup. Otherwise the boot sequence proceeds as usual. zfsbootcfg writes zfsboot arguments specified on its command line to the Pad2 area of a disk identified by vfs.zfs.boot.primary_pool and vfs.zfs.boot.primary_vdev kenv variables that are set by loader during boot. Please see the manual page for more. Thanks to all who reviewed, contributed and made suggestions! There are many potential improvements to the feature, please see the review for details. Reviewed by: wblock (docs) Discussed with: jhb, tsoome MFC after: 3 weeks Relnotes: yes Differential Revision: https://reviews.freebsd.org/D7612 Notes: svn path=/head/; revision=308089
* Convert casperd(8) daemon to the libcasper.Mariusz Zaborski2016-02-251-1/+0
| | | | | | | | | | | | | | | | | | | | | | | After calling the cap_init(3) function Casper will fork from it's original process, using pdfork(2). Forking from a process has a lot of advantages: 1. We have the same cwd as the original process. 2. The same uid, gid and groups. 3. The same MAC labels. 4. The same descriptor table. 5. The same routing table. 6. The same umask. 7. The same cpuset(1). From now services are also in form of libraries. We also removed libcapsicum at all and converts existing program using Casper to new architecture. Discussed with: pjd, jonathan, ed, drysdale@google.com, emaste Partially reviewed by: drysdale@google.com, bdrewery Approved by: pjd (mentor) Differential Revision: https://reviews.freebsd.org/D4277 Notes: svn path=/head/; revision=296047
* Convert to SUBDIR.yes format.Bryan Drewery2015-11-181-60/+20
| | | | | | | | | Reviewed by: imp Sponsored by: EMC / Isilon Storage Division Differential Revision: https://reviews.freebsd.org/D4182 Notes: svn path=/head/; revision=291021
* Remove duplicate MK_ISCSI block and sort the conditional blocks so this errorEnji Cooper2015-02-021-9/+5
| | | | | | | | | | won't crop up again in the future Reported by: gjb MFC after: 1 week Notes: svn path=/head/; revision=278070
* Build sbin/iscontrol again if MK_ISCSI != noEnji Cooper2015-01-261-0/+4
| | | | | | | | | MFC after: 13 days X-MFC with: r277675 Pointyhat to: me Notes: svn path=/head/; revision=277726
* Add MK_HAST knob for building and installing hastd(8), et alEnji Cooper2015-01-261-2/+5
| | | | | | | | MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division Notes: svn path=/head/; revision=277725
* Add MK_CCD knob for building and installing ccd(4), ccdconfig, etcEnji Cooper2015-01-251-1/+4
| | | | | | | | MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division Notes: svn path=/head/; revision=277678
* Add MK_ISCSI knob for building the iscsi initiator, iscsi daemon, kernelEnji Cooper2015-01-251-1/+4
| | | | | | | | | | modules, etc MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division Notes: svn path=/head/; revision=277675
* Use src.opts.mk in preference to bsd.own.mk except where we need stuffWarner Losh2014-05-061-1/+1
| | | | | | | from the latter. Notes: svn path=/head/; revision=265420
* Add a SUBDIR_PARALLEL option to bsd.subdir.mk, to allow make to processDimitry Andric2014-03-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | all the SUBDIR entries in parallel, instead of serially. Apply this option to a selected number of Makefiles, which can greatly speed up the build on multi-core machines, when using make -j. This can be extended to more Makefiles later on, whenever they are verified to work correctly with parallel building. I tested this on a 24-core machine, with make -j48 buildworld (N = 6): before stddev after stddev ======= ====== ======= ====== real time 1741.1 16.5 959.8 2.7 user time 12468.7 16.4 14393.0 16.8 sys time 1825.0 54.8 2110.6 22.8 (user+sys)/real 8.2 17.1 E.g. the build was approximately 45% faster in real time. On machines with less cores, or with lower -j settings, the speedup will not be as impressive. But at least you can now almost max out a machine with buildworld! Submitted by: jilles MFC after: 2 weeks Notes: svn path=/head/; revision=263778
* Migrate tools/regression/sbin/ to the new tests layout.Julio Merino2014-03-161-0/+4
| | | | | | | | Pretty much all that this change does is shuffles the code around and hooks it into the regular build. The code of the old tests has not changed. Notes: svn path=/head/; revision=263220
* Please welcome casperd daemon. It (and its services) will be responsible forPawel Jakub Dawidek2013-12-021-0/+4
| | | | | | | | | | | | | | | | | | | | | | giving access to functionality that is not available in capability mode sandbox. The functionality can be precisely restricted. Start with the following services: - system.dns - provides API compatible to: - gethostbyname(3), - gethostbyname2(3), - gethostbyaddr(3), - getaddrinfo(3), - getnameinfo(3), - system.grp - provides getgrent(3)-compatible API, - system.pwd - provides getpwent(3)-compatible API, - system.random - allows to obtain entropy from /dev/random, - system.sysctl - provides sysctlbyname(3-compatible API. Sponsored by: The FreeBSD Foundation Notes: svn path=/head/; revision=258838
* Remove trailing backslash.Pawel Jakub Dawidek2013-12-011-1/+1
| | | | Notes: svn path=/head/; revision=258792
* Remove all legacy ATA code parts, not used since options ATA_CAM enabled inAlexander Motin2013-04-041-1/+0
| | | | | | | | | | | | most kernels before FreeBSD 9.0. Remove such modules and respective kernel options: atadisk, ataraid, atapicd, atapifd, atapist, atapicam. Remove the atacontrol utility and some man pages. Remove useless now options ATA_CAM. No objections: current@, stable@ MFC after: never Notes: svn path=/head/; revision=249083
* Disconnect non-MPSAFE NTFS from the build in preparation for droppingAttilio Rao2012-10-171-1/+0
| | | | | | | | | | | | | | | | | GIANT from VFS. This code is particulary broken and fragile and other in-kernel implementations around, found in other operating systems, don't really seem clean and solid enough to be imported at all. If someone wants to reconsider in-kernel NTFS implementation for inclusion again, a fair effort for completely fixing and cleaning it up is expected. In the while NTFS regular users can use FUSE interface and ntfs-3g port to work with their NTFS partitions. This is not targeted for MFC. Notes: svn path=/head/; revision=241636
* Import a FreeBSD port of the FUSE Linux module.Attilio Rao2012-10-131-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This has been developed during 2 summer of code mandates and being revived by gnn recently. The functionality in this commit mirrors entirely content of fusefs-kmod port, which doesn't need to be installed anymore for -CURRENT setups. In order to get some sparse technical notes, please refer to: http://lists.freebsd.org/pipermail/freebsd-fs/2012-March/013876.html or to the project branch: svn://svn.freebsd.org/base/projects/fuse/ which also contains granular history of changes happened during port refinements. This commit does not came from the branch reintegration itself because it seems svn is not behaving properly for this functionaly at the moment. Partly Sponsored by: Google, Summer of Code program 2005, 2011 Originally submitted by: ilya, Csaba Henk <csaba-ml AT creo DOT hu > In collabouration with: pho Tested by: flo, gnn, Gustau Perez, Kevin Oberman <rkoberman AT gmail DOT com> MFC after: 2 months Notes: svn path=/head/; revision=241519
* Import work done under project/nand (@235533) into head.Grzegorz Bernacki2012-05-171-0/+5
| | | | | | | | | | | | | | | | | The NAND Flash environment consists of several distinct components: - NAND framework (drivers harness for NAND controllers and NAND chips) - NAND simulator (NANDsim) - NAND file system (NAND FS) - Companion tools and utilities - Documentation (manual pages) This work is still experimental. Please use with caution. Obtained from: Semihalf Supported by: FreeBSD Foundation, Juniper Networks Notes: svn path=/head/; revision=235537
* Add etherswitchcfg.Adrian Chadd2012-05-111-0/+1
| | | | | | | Submitted by: Stefan Bethke <stb@lassitu.de> Notes: svn path=/head/; revision=235289
* Add resolvconf(8) which manages resolv.conf.Hajimu UMEMOTO2011-03-181-0/+1
| | | | Notes: svn path=/head/; revision=219738
* MF tbemd: Move to using Makefile.arch to select what to build.Warner Losh2010-09-131-56/+14
| | | | | | | Reviewed by: arch@ (no objection) Notes: svn path=/head/; revision=212527
* Please welcome HAST - Highly Avalable Storage.Pawel Jakub Dawidek2010-02-181-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | HAST allows to transparently store data on two physically separated machines connected over the TCP/IP network. HAST works in Primary-Secondary (Master-Backup, Master-Slave) configuration, which means that only one of the cluster nodes can be active at any given time. Only Primary node is able to handle I/O requests to HAST-managed devices. Currently HAST is limited to two cluster nodes in total. HAST operates on block level - it provides disk-like devices in /dev/hast/ directory for use by file systems and/or applications. Working on block level makes it transparent for file systems and applications. There in no difference between using HAST-provided device and raw disk, partition, etc. All of them are just regular GEOM providers in FreeBSD. For more information please consult hastd(8), hastctl(8) and hast.conf(5) manual pages, as well as http://wiki.FreeBSD.org/HAST. Sponsored by: FreeBSD Foundation Sponsored by: OMCnet Internet Service GmbH Sponsored by: TransIP BV Notes: svn path=/head/; revision=204076
* Remove the unmaintained University of Michigan NFSv4 client from 8.xRobert Watson2009-05-221-1/+0
| | | | | | | | | | prior to 8.0-RELEASE. Rick Macklem's new and more feature-rich NFSv234 client and server are replacing it. Discussed with: rmacklem Notes: svn path=/head/; revision=192578
* Remove if_ppp(4) and if_sl(4).Ed Schouten2009-04-051-6/+0
| | | | | | | | | | | | | | | | Not only did these two drivers depend on IFF_NEEDSGIANT, they were broken 7 months ago during the MPSAFE TTY import. if_ppp(4) has been replaced by ppp(8). There is no replacement for if_sl(4). If we see regressions in for example the ports tree, we should just use __FreeBSD_version 800045 to check whether if_ppp(4) and if_sl(4) are present. Version 800045 is used to denote the import of MPSAFE TTY. Discussed with: rwatson, but also rwatson's IFF_NEEDSGIANT emails on the lists. Notes: svn path=/head/; revision=190751
* add new build knobs and jigger some existing controls to improveSam Leffler2008-09-211-5/+22
| | | | | | | | | | | control over the result of buildworld and installworld; this especially helps packaging systems such as nanobsd Reviewed by: various (posted to arch) MFC after: 1 month Notes: svn path=/head/; revision=183242
* Obsolete bsdlabel(8) on powerpc. Use gpart(8) instead.Marcel Moolenaar2008-07-061-1/+1
| | | | Notes: svn path=/head/; revision=180331
* Make sunlabel specific to sparc64. This is mostly for backwardMarcel Moolenaar2008-07-041-1/+5
| | | | | | | | compatibility reasons. Sun labels, with VTOC8, are handled by gpart(8). Notes: svn path=/head/; revision=180247
* Stop building bsdlabel(8) and fdisk(8) on ia64. Both tools areMarcel Moolenaar2008-07-031-2/+5
| | | | | | | | | | | | | | | obsoleted by gpart(8). This avoids the following bugs in fdisk: - initializing a disk without MBR bogusly emits the error: fdisk: invalid fdisk partition table found - initializing a disk with or without MBR bogusly emits either: fdisk: Class not found or fdisk: Geom not found: "XXX" - the default geometry for non-ATA and non-SCSI disks is either invalid or sub-optimizal. Notes: svn path=/head/; revision=180229
* Disconnect gpt(8) from the build. gpt(8) is replaced by gpart(8).Marcel Moolenaar2008-06-091-1/+0
| | | | Notes: svn path=/head/; revision=179680
* Add command-line tool ddb(8), which allows DDB(4) scripts to beRobert Watson2007-12-261-0/+1
| | | | | | | | | | | | managed from userspace. It is largely a wrapper for sysctl() calls, but because the sysctls for adding and removing scripts are awkward to use directly, this provides an easier-to-use interface. MFC after: 3 months Notes: svn path=/head/; revision=174915
* Introduce Danny Braniss' iSCSI initiator, version 2.0.99. Please read theScott Long2007-07-241-0/+1
| | | | | | | | | | | included man pages on how to use it. This code is still somewhat experimental but has been successfully tested on a number of targets. Many thanks to Danny for contributing this. Approved by: re Notes: svn path=/head/; revision=171568
* - Remove UMAP filesystem. It was disconnected from build three years ago,Rong-En Fan2007-06-251-1/+0
| | | | | | | | | | and it is seriously broken. Discussed on: freebsd-arch@ Approved by: re (mux) Notes: svn path=/head/; revision=171023
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-25 20:07:41 +0000