summaryrefslogtreecommitdiffstats
path: root/sbin
Commit message (Collapse)AuthorAgeFilesLines
* Distinguish between TCQ and NCQ type of tagged queing.sos2004-09-151-9/+11
|
* Make 'ipfw tee' behave as inteded and designed. A tee'd packet is copiedandre2004-09-131-13/+2
| | | | | | | | | | and sent to the DIVERT socket while the original packet continues with the next rule. Unlike a normally diverted packet no IP reassembly attemts are made on tee'd packets and they are passed upwards totally unmodified. Note: This will not be MFC'd to 4.x because of major infrastucture changes. PR: kern/64240 (and many others collapsed into that one)
* WARNS=4 safe.alfred2004-09-121-3/+11
|
* Fix build.alfred2004-09-121-5/+7
|
* Hook mount_autofs to the build.alfred2004-09-121-0/+1
|
* Currently when ipfw(8) generates the micro-instructions for rules whichcsjp2004-09-111-3/+3
| | | | | | | | | | | | | | | | | | | | | | contain O_UID, O_GID and O_JAIL opcodes, the F_NOT or F_OR logical operator bits get clobbered. Making it impossible to use the ``NOT'' or ``OR'' operators with uid, gid and jail based constraints. The ipfw_insn instruction template contains a ``len'' element which stores two pieces of information, the size of the instruction (in 32-bit words) in the low 6 bits of "len" with the 2 remaining bits to implement OR and NOT. The current code clobbers the OR and NOT bits by initializing the ``len'' element to the size, rather than OR'ing the bits. This change fixes this by changing the initialization of cmd->len to an OR operation for the O_UID, O_GID and O_JAIL opcodes. This may be a MFC candidate for RELENG_5. Reviewed by: andre Approved by: luigi PR: kern/63961 (partially)
* o Initialize a local variable and make gcc happy.maxim2004-09-101-0/+2
| | | | | PR: bin/71485 Submitted by: Jukka A. Ukkonen
* Fix a type bug which sometimes wrote unusable lock sectors on the disk.phk2004-09-101-2/+2
|
* The disk labels generated by bsdlabel can no address more thanbrooks2004-09-092-7/+22
| | | | | | | | | | | 0xffffffff sectors. Document this limit and avoid installing bogus labels on disks with more sectors. Allowing the installation of labels addressing as much of the disk as possiable may be a useful addition in some situations, but this was easy to implement and should reduce confusion. PR: bin/71408
* add support for documented readonly option...jmg2004-09-081-1/+5
| | | | | | | also print out the option that is unknow so that the user knows what (s)he did wrong.. MFC after: 3 days
* sync with private code:alfred2004-09-083-4/+4
| | | | | fix a 5.x'ism that 4.x needs protection from. make this code compile standalone.
* Fix/clean up return values checking.pjd2004-09-084-31/+31
|
* Allow to setup GBDE on providers which contain '/' in their names,pjd2004-09-061-2/+0
| | | | | | e.g. mirror/<name>, stripe/<name>. Approved by: phk
* Use a spare byte in struct if_data to store the structure size withoutbrooks2004-09-011-1/+4
| | | | | | | | | increasing it. Add code to ifconfig to use this size to find the sockaddr_dl after the struct if_data in the routing message. This allows struct if_data to grow (up to 255 bytes) without breaking ifconfig. Submitted by: peter
* Move back to WARNS=2scottl2004-09-011-1/+1
|
* Create DIP_SET() and IBLK_SET() macros to fix lvalue warnings.scottl2004-09-015-40/+59
| | | | Inspired by: kan
* Enter the autofs.alfred2004-08-313-0/+182
|
* Correct a style bug: remove a gratuitous space between ( and ".trhodes2004-08-311-1/+1
| | | | Ok'ed by: fjoe
* Add a suffix descriptor for the acpi thermal values as a hint for the userlandpeter2004-08-301-2/+12
| | | | sysctl tool to print a more readable value for temperatures.
* When configuring RAID3 with verification option, force synchronizationpjd2004-08-301-0/+7
| | | | | | | of parity component, because we can't return an EIO error for read of every sector which wasn't written first. Discussed with: phk
* o Restore a historical ipfw1 logamount behaviour: rules with 'log'maxim2004-08-291-0/+7
| | | | | | | | | | | keyword but without 'logamount' limit the amount of their log messages by net.inet.ip.fw.verbose_limit sysctl value. RELENG_5 candidate. PR: kern/46080 Submitted by: Dan Pelleg MFC after: 1 week
* Warn the user if we are not going to use the whole provider's space.pjd2004-08-281-1/+21
|
* Warn the user if we are not going to use whole provider space.pjd2004-08-281-5/+9
| | | | Requested by: Michael Handler <handler@grendel.net>
* - If error string begins with "warning: ", don't exit, treat it as a warningpjd2004-08-281-4/+6
| | | | | only. - Use getprogname() function when informing about versions problem.
* Fix 'show' command for pipes and queues.pjd2004-08-231-1/+7
| | | | | | PR: bin/70311 Submitted by: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl> MFC after: 3 days
* Add missing GEOM classes, which are aware of geom(8).pjd2004-08-231-0/+6
| | | | Submitted by: kuriyama
* Fix sysctl name.pjd2004-08-221-1/+1
|
* Implementation of 'verify reading' algorithm, which uses parity data forpjd2004-08-222-6/+39
| | | | | | | | verification of regular data when device is in complete state. On verification error, EIO error is returned for the bio and sysctl kern.geom.raid3.stat.parity_mismatch is increased. Suggested by: phk
* Implement new reading algorithm, which will use parity component for readingpjd2004-08-212-9/+30
| | | | | | | | | | | | | | | | | | | | | | | | as well, even if device is in complete state. I observe 40% of speed-up with this option for random read operations, but slowdown for sequential reads. Basically, without this option reading from a RAID3 device built from 5 components (c0-c4) looks like this: Request no. Used components 1 c0+c1+c2+c3 2 c0+c1+c2+c3 3 c0+c1+c2+c3 With the new feature: Request no. Used components 1 c0+c1+c2+c3 2 (c1^c2^c3^c4)+c1+c2+c3 3 c0+(c0^c2^c3^c4)+c2+c3 4 c0+c1+(c0^c1^c3^c4)+c3 5 c0+c1+c2+(c0^c1^c2^c4) 6 c0+c1+c2+c3 [...]
* Generalize the UFS bad magic value used to determine when a filesystemjhb2004-08-192-6/+11
| | | | | | | | has only been partly initialized via newfs(8) so that it applies to both UFS1 and UFS2. Submitted by: "Xin LI" delphij at frontfree dot net MFC: maybe?
* - Add a manual page for graid3(8) utility.pjd2004-08-183-1/+213
| | | | | - Connect it to the build. - Inform geom(8) about it.
* Add a line to BUGS section about the need of implementation description.pjd2004-08-181-0/+2
|
* Add some missing empty lines.pjd2004-08-181-0/+2
|
* Fix typo.pjd2004-08-181-1/+1
|
* Actually one can specify more than one device to stop.pjd2004-08-182-2/+2
|
* Ok, let's try again:pjd2004-08-181-0/+290
| | | | Add manual page for gmirror(8) utility.
* - Add a manual page for gmirror(8) utility.pjd2004-08-182-1/+1
| | | | | | | - Connect it to the build. - Inform geom(8) manual page about it. Reviewed by: trhodes
* Use a local "compress" symbol corresponding to a variable in BSS,ru2004-08-161-2/+2
| | | | | | | rather than the one from libz, corresponding to a function, when linking statically. PR: bin/70392
* Connect RAID3 GEOM class to the build.pjd2004-08-161-0/+1
|
* Introduce GEOM RAID3 class, i.e. kernel module, which implements RAID3pjd2004-08-162-0/+351
| | | | | | | transformation and graid3(8) userland utility, which can be used for configuration. No manual page yet, sorry. Hardware provided by: Daniel Seuffert
* Avoid using void pointers in additive expressions.stefanf2004-08-142-3/+3
| | | | PR: 56653
* Don't declare everything we find on a loopback interface for passive:phk2004-08-141-3/+9
| | | | | | | | Only the actual loopback address should be declared passive, other addresses are very likely to be desirable to announce. Check for IFF_LOOPBACK instead of IFF_PASSIVE to determine if we have an unknown interface type.
* Removed commented out bitrot.ru2004-08-132-2/+0
|
* Remove trailing whitespace and change "prisoniD" to "prisonID".csjp2004-08-131-2/+2
| | | | | Pointed out by: simon Approved by: bmilekic (mentor)
* Add the ability to associate ipfw rules with a specific prison ID.csjp2004-08-122-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since the only thing truly unique about a prison is it's ID, I figured this would be the most granular way of handling this. This commit makes the following changes: - Adds tokenizing and parsing for the ``jail'' command line option to the ipfw(8) userspace utility. - Append the ipfw opcode list with O_JAIL. - While Iam here, add a comment informing others that if they want to add additional opcodes, they should append them to the end of the list to avoid ABI breakage. - Add ``fw_prid'' to the ipfw ucred cache structure. - When initializing ucred cache, if the process is jailed, set fw_prid to the prison ID, otherwise set it to -1. - Update man page to reflect these changes. This change was a strong motivator behind the ucred caching mechanism in ipfw. A sample usage of this new functionality could be: ipfw add count ip from any to any jail 2 It should be noted that because ucred based constraints are only implemented for TCP and UDP packets, the same applies for jail associations. Conceptual head nod by: pjd Reviewed by: rwatson Approved by: bmilekic (mentor)
* The geom(8) utility needs dynamic linker functionality to work, so it can'tpjd2004-08-121-0/+2
| | | | | be staticaly linked. This fixes problems on systems compiled with NO_DYNAMICROOT.
* Add support for the examination and modification of the devices.harti2004-08-129-8/+817
| | | | | | This is implemented through SNMP and requires the ilmi daemon to run on the system. To prevent bloat in rescue the atmconfig for rescue is compiled without this stuff.
* Forgot to commit those: introduce hardcoded provider functionality,pjd2004-08-101-14/+31
| | | | | which allow to store provider's name in the metadata and avoid problems when few providers share the same last sector.
* New ipfw option "antispoof":andre2004-08-092-3/+49
| | | | | | | | | | | | | | | For incoming packets, the packet's source address is checked if it belongs to a directly connected network. If the network is directly connected, then the interface the packet came on in is compared to the interface the network is connected to. When incoming interface and directly connected interface are not the same, the packet does not match. Usage example: ipfw add deny ip from any to any not antispoof in Manpage education by: ru
* The multiplier prefix is actually a multiplier suffix.des2004-08-091-1/+1
|
OpenPOWER on IntegriCloud