Searched hist:4 (Results 1 - 25 of 14306) sorted by path
| /freebsd-9.3-release/ | ||
| H A D | UPDATING | diff 293896 Thu Jan 14 07:14:56 MST 2016 glebius o Fix invalid TCP checksums with pf(4). [EN-16:02.pf] o Fix YP/NIS client library critical bug. [EN-16:03.yplib] o Fix SCTP ICMPv6 error message vulnerability. [SA-16:01.sctp] o Fix ntp panic threshold bypass vulnerability. [SA-16:02.ntp] o Fix Linux compatibility layer incorrect futex handling. [SA-16:03.linux] o Fix Linux compatibility layer setgroups(2) system call. [SA-16:04.linux] o Fix TCP MD5 signature denial of service. [SA-16:05.tcp] o Fix insecure default bsnmpd.conf permissions. [SA-16:06.bsnmpd] Errata: FreeBSD-EN-16:02.pf Errata: FreeBSD-EN-16:03.yplib Security: FreeBSD-SA-16:01.sctp, CVE-2016-1879 Security: FreeBSD-SA-16:02.ntp, CVE-2015-5300 Security: FreeBSD-SA-16:03.linux, CVE-2016-1880 Security: FreeBSD-SA-16:04.linux, CVE-2016-1881 Security: FreeBSD-SA-16:05.tcp, CVE-2016-1882 Security: FreeBSD-SA-16:06.bsnmpd, CVE-2015-5677 Approved by: so diff 279265 Wed Feb 25 04:07:42 MST 2015 delphij Fix integer overflow in IGMP protocol. [SA-15:04] Fix BIND remote denial of service vulnerability. [SA-15:05] Fix vt(4) crash with improper ioctl parameters. [EN-15:01] Updated base system OpenSSL to 0.9.8zd. [EN-15:02] Fix freebsd-update libraries update ordering issue. [EN-15:03] Approved by: so diff 279265 Wed Feb 25 04:07:42 MST 2015 delphij Fix integer overflow in IGMP protocol. [SA-15:04] Fix BIND remote denial of service vulnerability. [SA-15:05] Fix vt(4) crash with improper ioctl parameters. [EN-15:01] Updated base system OpenSSL to 0.9.8zd. [EN-15:02] Fix freebsd-update libraries update ordering issue. [EN-15:03] Approved by: so |
| /freebsd-9.3-release/bin/ | ||
| H A D | Makefile.inc | diff 119018 Sun Aug 17 06:37:47 MDT 2003 gordon Stage 4 of dynamically linked root support. Add a big knob, WITH_DYNAMICROOT, which will toggle the generation of dynamically-linked binaries for installation in /bin and /sbin. It is currently off, meaning that /bin and /sbin are still statically linked by default. If something goes wrong (which I hope doesn't), this is what /rescue is all about. Please do not try to use WITH_DYNAMICROOT and NO_RESCUE to save space or some other equally silly reason. If you do and end up having problems, you have been warned. |
| /freebsd-9.3-release/bin/cat/ | ||
| H A D | cat.c | diff 184471 Thu Oct 30 12:21:38 MDT 2008 ivoras Teach cat(1) and cp(1) to use a larger buffer if enough memory is present in the system. A simple heuristics is used to detect what is "enough" memory: if number of physmem pages is greater than 32k (equalling 128 MB on machines with 4 kB pages). Typical immediate result of these changes is reduction in context switches and the goal is to increase efficiency by using large buffers: before: /usr/bin/time -hlp cat file1 > file2 ... 163 voluntary context switches 11194 involuntary context switches after: /usr/bin/time -hlp ./cat file1 > file2 ... 417 voluntary context switches 272 involuntary context switches Reviewed by: hackers@ (no objections to earlier version of cat patch) Approved by: gnn (mentor) MFC after: 4 months diff 184471 Thu Oct 30 12:21:38 MDT 2008 ivoras Teach cat(1) and cp(1) to use a larger buffer if enough memory is present in the system. A simple heuristics is used to detect what is "enough" memory: if number of physmem pages is greater than 32k (equalling 128 MB on machines with 4 kB pages). Typical immediate result of these changes is reduction in context switches and the goal is to increase efficiency by using large buffers: before: /usr/bin/time -hlp cat file1 > file2 ... 163 voluntary context switches 11194 involuntary context switches after: /usr/bin/time -hlp ./cat file1 > file2 ... 417 voluntary context switches 272 involuntary context switches Reviewed by: hackers@ (no objections to earlier version of cat patch) Approved by: gnn (mentor) MFC after: 4 months diff 91079 Fri Feb 22 18:51:00 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4. |
| /freebsd-9.3-release/bin/chio/ | ||
| H A D | Makefile | diff 39227 Tue Sep 15 05:48:51 MDT 1998 gibbs Updated the ch(4) driver and chio(1) command to include volume tag support. These changes have been tested with a Breeze Hill Q47 DLT and a DEC DLT2500 media changer. The latter has no volume tag support. The chio(1) command was updated to include various flags to the status subcommand. These flags can be used to select additional information to be displayed (like volume tags). A new chio(1) subcommand named 'voltag' has been added which allows for changes to volume tags inside the media changer controller. This could not be tested as the Q47 does not provide the functio- nality. Submitted by: Hans Huebner |
| H A D | chio.1 | diff 66019 Mon Sep 18 04:09:11 MDT 2000 ken Add two new features to chio(1): - The ability to specify elements by volume tag instead of their actual physical location. e.g., instead of: chio move slot 3 slot 4 you would now use: chio move voltag FOO slot 4 - The ability to return an element to its previous location, as specified by the source element. e.g., instead of: chio move drive 0 slot 4 you would now use: chio return drive 0 or chio return voltag FOO These features will obviously only work with changers that support volume tags and/or source element IDs. chio(1) should fail gracefully if the user attempts to use these new features and the source element ID or volume tag are not found. PR: bin/21178 Submitted by: "C. Stephen Gunn" <csg@waterspout.com> Reviewed by: ken diff 66019 Mon Sep 18 04:09:11 MDT 2000 ken Add two new features to chio(1): - The ability to specify elements by volume tag instead of their actual physical location. e.g., instead of: chio move slot 3 slot 4 you would now use: chio move voltag FOO slot 4 - The ability to return an element to its previous location, as specified by the source element. e.g., instead of: chio move drive 0 slot 4 you would now use: chio return drive 0 or chio return voltag FOO These features will obviously only work with changers that support volume tags and/or source element IDs. chio(1) should fail gracefully if the user attempts to use these new features and the source element ID or volume tag are not found. PR: bin/21178 Submitted by: "C. Stephen Gunn" <csg@waterspout.com> Reviewed by: ken diff 66019 Mon Sep 18 04:09:11 MDT 2000 ken Add two new features to chio(1): - The ability to specify elements by volume tag instead of their actual physical location. e.g., instead of: chio move slot 3 slot 4 you would now use: chio move voltag FOO slot 4 - The ability to return an element to its previous location, as specified by the source element. e.g., instead of: chio move drive 0 slot 4 you would now use: chio return drive 0 or chio return voltag FOO These features will obviously only work with changers that support volume tags and/or source element IDs. chio(1) should fail gracefully if the user attempts to use these new features and the source element ID or volume tag are not found. PR: bin/21178 Submitted by: "C. Stephen Gunn" <csg@waterspout.com> Reviewed by: ken diff 39227 Tue Sep 15 05:48:51 MDT 1998 gibbs Updated the ch(4) driver and chio(1) command to include volume tag support. These changes have been tested with a Breeze Hill Q47 DLT and a DEC DLT2500 media changer. The latter has no volume tag support. The chio(1) command was updated to include various flags to the status subcommand. These flags can be used to select additional information to be displayed (like volume tags). A new chio(1) subcommand named 'voltag' has been added which allows for changes to volume tags inside the media changer controller. This could not be tested as the Q47 does not provide the functio- nality. Submitted by: Hans Huebner diff 26394 Mon Jun 02 18:57:52 MDT 1997 max Add X-reference to ch(4). |
| H A D | chio.c | diff 252214 Tue Jun 25 19:58:11 MDT 2013 ken MFC: 249658, 249701 Update chio(1) and ch(4) to support reporting element designators. This allows mapping a tape drive in a changer (as reported by 'chio status') to a sa(4) driver instance by comparing the serial numbers. The designators can be ASCII (which is printed out directly), binary (which is printed in hex format) or UTF-8, which is printed in either native UTF-8 format if the terminal can support it, or in %XX notation for non-ASCII characters. Thanks to Hiroki Sato <hrs@> for the explanation and example UTF-8 printing code. chio.h: Modify the changer_element_status structure to add new fields and definitions from the SMC3r16 spec. Rename the original CHIOGSTATUS ioctl to OCHIOGTATUS and define a new CHIOGSTATUS ioctl. Clean up some tab/space issues. chio.c: For the 'status' subcommand, print the designator field if it is supplied by a device. scsi_ch.h: Add new flags for DVCID and CURDATA to the READ ELEMENT STATUS command structure. Add a read_element_status_device_id structure for the data fields in the new standard. Add new unions, dt_or_obsolete and voltage_devid, to hold and address data from either SCSI-2 or newer devices. scsi_ch.c: Implement support for fetching device IDs with READ ELEMENT STATUS data. Add new arguments to scsi_read_element_status() to allow the user to request the DVCID and CURDATA bits. This isn't compiled into libcam (it's only an internal kernel interface), so we don't need any special handling for the API change. If the user issues the new CHIOGSTATUS ioctl, copy all of the available element status data out. If he issues the OCHIOGSTATUS ioctl, we don't copy the new fields in the structure. Fix a bug in chopen() that would result in the peripheral never getting unheld if chgetparams() failed. Sponsored by: Spectra Logic Submitted by: Po-Li Soong diff 252214 Tue Jun 25 19:58:11 MDT 2013 ken MFC: 249658, 249701 Update chio(1) and ch(4) to support reporting element designators. This allows mapping a tape drive in a changer (as reported by 'chio status') to a sa(4) driver instance by comparing the serial numbers. The designators can be ASCII (which is printed out directly), binary (which is printed in hex format) or UTF-8, which is printed in either native UTF-8 format if the terminal can support it, or in %XX notation for non-ASCII characters. Thanks to Hiroki Sato <hrs@> for the explanation and example UTF-8 printing code. chio.h: Modify the changer_element_status structure to add new fields and definitions from the SMC3r16 spec. Rename the original CHIOGSTATUS ioctl to OCHIOGTATUS and define a new CHIOGSTATUS ioctl. Clean up some tab/space issues. chio.c: For the 'status' subcommand, print the designator field if it is supplied by a device. scsi_ch.h: Add new flags for DVCID and CURDATA to the READ ELEMENT STATUS command structure. Add a read_element_status_device_id structure for the data fields in the new standard. Add new unions, dt_or_obsolete and voltage_devid, to hold and address data from either SCSI-2 or newer devices. scsi_ch.c: Implement support for fetching device IDs with READ ELEMENT STATUS data. Add new arguments to scsi_read_element_status() to allow the user to request the DVCID and CURDATA bits. This isn't compiled into libcam (it's only an internal kernel interface), so we don't need any special handling for the API change. If the user issues the new CHIOGSTATUS ioctl, copy all of the available element status data out. If he issues the OCHIOGSTATUS ioctl, we don't copy the new fields in the structure. Fix a bug in chopen() that would result in the peripheral never getting unheld if chgetparams() failed. Sponsored by: Spectra Logic Submitted by: Po-Li Soong diff 91086 Fri Feb 22 19:21:37 MST 2002 markm Fix a boatload of warnings inspired by lint, a commercial lint and WARNS=4. diff 66019 Mon Sep 18 04:09:11 MDT 2000 ken Add two new features to chio(1): - The ability to specify elements by volume tag instead of their actual physical location. e.g., instead of: chio move slot 3 slot 4 you would now use: chio move voltag FOO slot 4 - The ability to return an element to its previous location, as specified by the source element. e.g., instead of: chio move drive 0 slot 4 you would now use: chio return drive 0 or chio return voltag FOO These features will obviously only work with changers that support volume tags and/or source element IDs. chio(1) should fail gracefully if the user attempts to use these new features and the source element ID or volume tag are not found. PR: bin/21178 Submitted by: "C. Stephen Gunn" <csg@waterspout.com> Reviewed by: ken diff 66019 Mon Sep 18 04:09:11 MDT 2000 ken Add two new features to chio(1): - The ability to specify elements by volume tag instead of their actual physical location. e.g., instead of: chio move slot 3 slot 4 you would now use: chio move voltag FOO slot 4 - The ability to return an element to its previous location, as specified by the source element. e.g., instead of: chio move drive 0 slot 4 you would now use: chio return drive 0 or chio return voltag FOO These features will obviously only work with changers that support volume tags and/or source element IDs. chio(1) should fail gracefully if the user attempts to use these new features and the source element ID or volume tag are not found. PR: bin/21178 Submitted by: "C. Stephen Gunn" <csg@waterspout.com> Reviewed by: ken diff 66019 Mon Sep 18 04:09:11 MDT 2000 ken Add two new features to chio(1): - The ability to specify elements by volume tag instead of their actual physical location. e.g., instead of: chio move slot 3 slot 4 you would now use: chio move voltag FOO slot 4 - The ability to return an element to its previous location, as specified by the source element. e.g., instead of: chio move drive 0 slot 4 you would now use: chio return drive 0 or chio return voltag FOO These features will obviously only work with changers that support volume tags and/or source element IDs. chio(1) should fail gracefully if the user attempts to use these new features and the source element ID or volume tag are not found. PR: bin/21178 Submitted by: "C. Stephen Gunn" <csg@waterspout.com> Reviewed by: ken diff 39227 Tue Sep 15 05:48:51 MDT 1998 gibbs Updated the ch(4) driver and chio(1) command to include volume tag support. These changes have been tested with a Breeze Hill Q47 DLT and a DEC DLT2500 media changer. The latter has no volume tag support. The chio(1) command was updated to include various flags to the status subcommand. These flags can be used to select additional information to be displayed (like volume tags). A new chio(1) subcommand named 'voltag' has been added which allows for changes to volume tags inside the media changer controller. This could not be tested as the Q47 does not provide the functio- nality. Submitted by: Hans Huebner |
| /freebsd-9.3-release/bin/chmod/ | ||
| H A D | chmod.c | diff 91078 Fri Feb 22 18:45:09 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4 |
| /freebsd-9.3-release/bin/cp/ | ||
| H A D | Makefile | diff 91087 Fri Feb 22 19:24:14 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4. |
| H A D | cp.c | diff 91087 Fri Feb 22 19:24:14 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4. diff 87655 Tue Dec 11 11:18:10 MST 2001 mckay Preserve directory timestamps with -p. Allow non-empty read-only directories to be copied. Apply umask to newly created directories when -p is not specified. PR: 27970 PR: 31633 MFC after: 4 days diff 78070 Mon Jun 11 11:57:54 MDT 2001 bde Removed the broken code which claimed to lose the set[ug]id bits in the !(pflag && setfile()) case for regular files unless the copy is owned by the same user and group. These bits have already been lost (or never gained) in the correct way. The code didn't actually lose the bits; it depended on them being lost already (apparently in all cases) and attempted to gain them as necessary, but it often gained them (and sometimes collateral bits) when wrong: - pflag && setfile() == 0 case (i.e., for a successful cp -p): setfile() copies all the attributes as correctly as possible (as specified by POSIX), and we sometimes messed up the up the mode by setting it again. Also, if the file is immutable, then setting the mode again gave spurious errors (PR 20646). - !pflag case. If the target is created, POSIX requires it to not have the set[ug]id bits, but we sometimes copied them from the source. If the target already exists, POSIX requires its mode to be unchanged, but we sometimes copied the whole mode from the source. PR: 20646 MFC after: 4 weeks |
| H A D | extern.h | diff 91087 Fri Feb 22 19:24:14 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4. diff 78070 Mon Jun 11 11:57:54 MDT 2001 bde Removed the broken code which claimed to lose the set[ug]id bits in the !(pflag && setfile()) case for regular files unless the copy is owned by the same user and group. These bits have already been lost (or never gained) in the correct way. The code didn't actually lose the bits; it depended on them being lost already (apparently in all cases) and attempted to gain them as necessary, but it often gained them (and sometimes collateral bits) when wrong: - pflag && setfile() == 0 case (i.e., for a successful cp -p): setfile() copies all the attributes as correctly as possible (as specified by POSIX), and we sometimes messed up the up the mode by setting it again. Also, if the file is immutable, then setting the mode again gave spurious errors (PR 20646). - !pflag case. If the target is created, POSIX requires it to not have the set[ug]id bits, but we sometimes copied them from the source. If the target already exists, POSIX requires its mode to be unchanged, but we sometimes copied the whole mode from the source. PR: 20646 MFC after: 4 weeks |
| H A D | utils.c | diff 184471 Thu Oct 30 12:21:38 MDT 2008 ivoras Teach cat(1) and cp(1) to use a larger buffer if enough memory is present in the system. A simple heuristics is used to detect what is "enough" memory: if number of physmem pages is greater than 32k (equalling 128 MB on machines with 4 kB pages). Typical immediate result of these changes is reduction in context switches and the goal is to increase efficiency by using large buffers: before: /usr/bin/time -hlp cat file1 > file2 ... 163 voluntary context switches 11194 involuntary context switches after: /usr/bin/time -hlp ./cat file1 > file2 ... 417 voluntary context switches 272 involuntary context switches Reviewed by: hackers@ (no objections to earlier version of cat patch) Approved by: gnn (mentor) MFC after: 4 months diff 184471 Thu Oct 30 12:21:38 MDT 2008 ivoras Teach cat(1) and cp(1) to use a larger buffer if enough memory is present in the system. A simple heuristics is used to detect what is "enough" memory: if number of physmem pages is greater than 32k (equalling 128 MB on machines with 4 kB pages). Typical immediate result of these changes is reduction in context switches and the goal is to increase efficiency by using large buffers: before: /usr/bin/time -hlp cat file1 > file2 ... 163 voluntary context switches 11194 involuntary context switches after: /usr/bin/time -hlp ./cat file1 > file2 ... 417 voluntary context switches 272 involuntary context switches Reviewed by: hackers@ (no objections to earlier version of cat patch) Approved by: gnn (mentor) MFC after: 4 months diff 91087 Fri Feb 22 19:24:14 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4. diff 78070 Mon Jun 11 11:57:54 MDT 2001 bde Removed the broken code which claimed to lose the set[ug]id bits in the !(pflag && setfile()) case for regular files unless the copy is owned by the same user and group. These bits have already been lost (or never gained) in the correct way. The code didn't actually lose the bits; it depended on them being lost already (apparently in all cases) and attempted to gain them as necessary, but it often gained them (and sometimes collateral bits) when wrong: - pflag && setfile() == 0 case (i.e., for a successful cp -p): setfile() copies all the attributes as correctly as possible (as specified by POSIX), and we sometimes messed up the up the mode by setting it again. Also, if the file is immutable, then setting the mode again gave spurious errors (PR 20646). - !pflag case. If the target is created, POSIX requires it to not have the set[ug]id bits, but we sometimes copied them from the source. If the target already exists, POSIX requires its mode to be unchanged, but we sometimes copied the whole mode from the source. PR: 20646 MFC after: 4 weeks |
| /freebsd-9.3-release/bin/csh/ | ||
| H A D | config_p.h | diff 150479 Thu Sep 22 16:32:53 MDT 2005 mp Bump up BUFSIZE from 4k to 8k. This was requested by portmgr@ to allow ports builds in the cluster to work correctly. Tested by: kris |
| /freebsd-9.3-release/bin/date/ | ||
| H A D | date.c | diff 91079 Fri Feb 22 18:51:00 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4. |
| H A D | netdate.c | diff 91079 Fri Feb 22 18:51:00 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4. |
| H A D | vary.c | diff 91079 Fri Feb 22 18:51:00 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4. |
| /freebsd-9.3-release/bin/dd/ | ||
| H A D | Makefile | diff 111629 Thu Feb 27 16:04:54 MST 2003 markm WARNS=4 fixes. This would be WARNS=9 if we were -std=99 instead of -ansi, due to 'long long'. Reviewed by: green (slightly earlier version) |
| H A D | args.c | diff 111629 Thu Feb 27 16:04:54 MST 2003 markm WARNS=4 fixes. This would be WARNS=9 if we were -std=99 instead of -ansi, due to 'long long'. Reviewed by: green (slightly earlier version) diff 91079 Fri Feb 22 18:51:00 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4. |
| H A D | conv.c | diff 111629 Thu Feb 27 16:04:54 MST 2003 markm WARNS=4 fixes. This would be WARNS=9 if we were -std=99 instead of -ansi, due to 'long long'. Reviewed by: green (slightly earlier version) |
| H A D | dd.c | diff 111629 Thu Feb 27 16:04:54 MST 2003 markm WARNS=4 fixes. This would be WARNS=9 if we were -std=99 instead of -ansi, due to 'long long'. Reviewed by: green (slightly earlier version) diff 91079 Fri Feb 22 18:51:00 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4. |
| H A D | dd.h | diff 111629 Thu Feb 27 16:04:54 MST 2003 markm WARNS=4 fixes. This would be WARNS=9 if we were -std=99 instead of -ansi, due to 'long long'. Reviewed by: green (slightly earlier version) diff 91079 Fri Feb 22 18:51:00 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4. diff 33234 Wed Feb 11 00:23:31 MST 1998 asami Fix printing for bytes read > 4G. Reviewed by: bde |
| H A D | extern.h | diff 111629 Thu Feb 27 16:04:54 MST 2003 markm WARNS=4 fixes. This would be WARNS=9 if we were -std=99 instead of -ansi, due to 'long long'. Reviewed by: green (slightly earlier version) |
| H A D | misc.c | diff 111629 Thu Feb 27 16:04:54 MST 2003 markm WARNS=4 fixes. This would be WARNS=9 if we were -std=99 instead of -ansi, due to 'long long'. Reviewed by: green (slightly earlier version) diff 33234 Wed Feb 11 00:23:31 MST 1998 asami Fix printing for bytes read > 4G. Reviewed by: bde |
| H A D | position.c | diff 111629 Thu Feb 27 16:04:54 MST 2003 markm WARNS=4 fixes. This would be WARNS=9 if we were -std=99 instead of -ansi, due to 'long long'. Reviewed by: green (slightly earlier version) |
| /freebsd-9.3-release/bin/df/ | ||
| H A D | df.c | diff 91081 Fri Feb 22 18:57:53 MST 2002 markm Warnings fixes inspired by lint, a commercial lint and WARNS=4. |
| /freebsd-9.3-release/bin/echo/ | ||
| H A D | echo.c | diff 91082 Fri Feb 22 19:00:16 MST 2002 markm Fix warnings inspired by lint, a commercial lint and WARNS=4. |
Completed in 319 milliseconds