summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Log hostname settings/changes.obrien1999-08-041-0/+1
| | | | Submitted by: John Baldwin <jobaldwi@vt.edu>
* Back out rev 1.2. The correct type of host-name is `X'. There was a problemobrien1999-08-041-1/+1
| | | | | | | | | | with options.c which was fixed in ISC's version 2.0 (rev 1.1.1.2 --> 1.1.1.3). I have tested host-name with both types `X' and `t' and things work fine either way. I would prefer to match the offical sources when easily possible. PR: 12205 Submitted by: John Baldwin <jobaldwi@vt.edu>
* Don't over-allocate and over-copy shorter NFSv2 filehandles and thenpeter1999-08-044-40/+44
| | | | | | | | | | correct the pointers afterwards. It's kinda bogus that we generate a 24 (?) byte filehandle (2 x int32 fsid and 16 byte VFS fhandle) and pad it out to 64 bytes for NFSv3 with garbage. The whole point of NFSv3's variable filehandle length was to allow for shorter handles, both in memory and over the wire. I plan on taking a shot at fixing this shortly.
* Don't probe if pci_cfgopen() fails to find pci hardware, like we used topeter1999-08-046-30/+24
| | | | | to. This might have caused interesting things on non-PCI hardware if PCI was compiled in.
* MFS: use logger(1) instead of plain echo(1).obrien1999-08-041-2/+7
| | | | | (some how these local changes made it out of my local tree into the repository, so lets do it right)
* Support the setting of hostname via DHCP.obrien1999-08-041-0/+7
| | | | Submitted by: myself & Ted Lemon <mellon@isc.org>
* o Typo in prior version kept it from compiling (blush).imp1999-08-042-12/+18
| | | | | | | Noticed by: Nobody! o Add comment about why we restrict chflags to root for devices. o nit noticed by bde wrt return values.
* brucify:imp1999-08-032-12/+12
| | | | | | | | | | | | | | | o use suser_xxx rather than suser to support JAIL code. o KNF comment convention o use vp->type rather than vaddr.type and eliminate call to VOP_GETATTR. Bruce says that vp->type is valid at this point. Submitted by: bde. Not fixed: o return (value) o Comment needs to be longer and more explicit. It will be after the advisory.
* Reorganise ppp's usage to avoid some mandoc limitations.brian1999-08-032-248/+200
| | | | Suggested by: wollman
* Add a sample entry for Exim, in preparation for the upcoming behavioursheldonh1999-08-031-1/+7
| | | | | | change in the port, where TCP Wrapper support will become the default. Requested by: markm
* Better comment on ntpdate_enable - if I have misunderstood wheneivind1999-08-031-2/+2
| | | | | ntpdate was run (I thought it was cron'ed), other people probably do too.
* Typowosch1999-08-031-2/+2
| | | | Submitted by: Christian Weisgerber <naddy@mips.rhein-neckar.de>
* Minor tweak for last commit: insert extra delay between issuing masterwpaul1999-08-021-2/+4
| | | | reset and RX/TX resets.
* Mention that ospf is a possible filter protocol.brian1999-08-023-7/+9
|
* Only allow root to set file flags on devices.imp1999-08-022-2/+16
|
* Perform an RX reset and TX reset in xl_reset() along with the masterwpaul1999-08-021-6/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | reset command. I observed some anomalous behavior while testing a 3c905C with a Dell PowerEdge 4300/500 dual PIII 500Mhz system. The NIC would seem to work correctly most of the time but would sometimes fail to receive certain packets, in particular NFS create requests. I could mount an NFS filesystem from the PowerEdge and do an ls on it, but trying to do a "touch foo" would hang. Monitoring traffic from another host revealed that the client was properly sending an NFS create request but the server was not receiving it. It *did* receive it when I ran the same test with an Intel fxp card. I don't understand the exact mechanics of this strange behavior, but resetting the receiver and transmitter seems to get rid of it. I used to perform an RX and TX reset in xl_init(), but stopped doing it there because on 3c905B and later cards this causes the autoneg session to restart, which would lead to the NIC waiting a long time before exchanging traffic after being brought up the first time. Apparently the receiver and transmitter resets should be performed at least once when initializing the card. Hopefully this will cure problems that people have been having with the 3c905C -- this was the only strange behavior that I have observed with the 3c905C so far which does not appear with the 3c905B or 3c905.
* The dev returned here is what is found in the st_dev field.rvb1999-08-022-4/+6
| | | | This should not be further translated ... hence the 0.
* I'm not sure how this wasn't in the last commit but anyhow...mdodd1999-08-022-4/+4
| | | | 'int irq' -> 'struct irq_node *irq'
* Make this build if there is an obj directory.dfr1999-08-021-3/+3
|
* Don't trust the segment limits that the BIOS reports; instead give itmsmith1999-08-022-20/+10
| | | | | as much space as possible to avoid lossage due to sloppy BIOS programming.
* Add missing "path mnemonics" as given in Table 4-3 of rev. 1.2 of these1999-08-021-19/+19
| | | | ARC Specification.
* Remove accidental 8bit character in error message.se1999-08-021-5/+21
| | | | | | | Add checks for malloc failure and add error exit in case of malloc failure. Add rcsid. Submitted by: charnier
* Fix typo and use Fx macro instead of literal FreeBSD.se1999-08-021-3/+4
| | | | Submitted by: charnier
* Use err[x]/warn[x] and improve error reportingbrian1999-08-021-23/+25
| | | | Submitted by: charnier
* #ifdef IPPROTO_OSPFIGP before expecting it to be defined.brian1999-08-023-3/+13
| | | | This unbreaks OpenBSD.
* Add -n option to print numeric user and group IDs instead of namessheldonh1999-08-023-9/+31
| | | | | | | | | | | | in a long (-l) listing. MFC-jockies should make sure that bde's concerns regarding the number of digits required to represent a uid_t and the use of snprintf on the associated PR have been addressed before going wild. PR: 12866 Reported by: Philip Kizer <pckizer@nostrum.com> Obtained from: NetBSD
* Filter ospf and igmp separately.brian1999-08-023-8/+50
| | | | Kind-of submitted by: phk
* Add new ports category "ftp".asami1999-08-022-2/+4
|
* Add ports-ftp.asami1999-08-022-2/+4
|
* Use Byacc rather than Bison.obrien1999-08-022-4/+2
|
* Clear flags on psuedo terminals before trying to chmod and chown them.imp1999-08-021-1/+2
|
* English fixes: consistent spacing after periods, "userland", not "user land",hoek1999-08-021-17/+18
| | | | | | other typos, ~four grammar gnits, an ironic case of incorrect parallelization, bad capitalization, an incorrect use of the infamous slash ('/'), and an unclear sentence.
* Bruce noted that the use of err(), fixed to errx() in the last commit,hoek1999-08-021-3/+6
| | | | | | | | did not specify an exit code. This implies the use of either a hand- rolled err() (Bruce's suggestion) or a random error code (my suggestion), both of which are against the style guidelines. This commit specifies the correct error code (implicitly). This also changes the error message to be a little more helpful.
* Move the specification of EDGE/LEVEL triggered interrupts tomdodd1999-08-0122-104/+160
| | | | | | | | | | | | | | | | | eisa_add_intr() which now takes an additional arguement (one of EISA_TRIGGER_LEVEL or EISA_TRIGGER_EDGE). The flag RR_SHAREABLE has no effect when passed to bus_alloc_resource(dev, SYS_RES_IRQ, ...) in an EISA device context as the eisa_alloc_resource() call (bus_alloc_resource method) now deals with this flag directly, depending on the device ivars. This change does nothing more than move all the 'shared = inb(foo + iobsse)' nonesense to the device probe methods rather than the device attach. Also, print out 'edge' or 'level' in the IRQ announcement message. Reviewed by: dfr
* Mention that EXIT_SUCCESS and EXIT_FAILURE are preferred overhoek1999-08-011-1/+7
| | | | sysexits.h-values as exit codes for portable programs.
* Typo of sample command line.sada1999-08-011-2/+2
| | | | Submitted by: Seiichi Satomi <ssatomi@rr.iij4u.or.jp>
* Richard the Lionheart was crowned on 3rd September 1189, not the 27thnik1999-08-011-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | February. If you do a web search for "lionheart crowned" you'll get lots of conflicting information. Some sites say 3rd September, while others say 27th February. Most of the "27th February" crowd seem to take their information from other incarnations of this file on other operating systems. After a very pleasant afternoon spent lunching with my girlfriend's parents, I availed myself of their extensive reference library. You'd be surprised how hard it is to get concrete information about this. The _Encyclopedia Brittanica_ doesn't mention the date, only the year, as does _Brewer's Dictionary of Phrase and Fable_, as do all the other printed sources I tried. One of them even said July 7th 1189! Microsoft's (yeah, so sue me) Encarta '95 has quite a comprehensive entry, but again, no day and month information In desperation, I tried the web once more, and finally stumbled upon http://www.btinternet.com/~timeref/hsttime2.htm. This revealed that Henry II died on 6th July 1189 (presumably the source of the 7th July entry in another reference), and that Richard was crowned on 3rd September. Best of all, this site gives references. So if any of you have a copy of _The Life and Times of Richard I_, John Gillingham, pub. George Weidenfeld and Nicholson Limited, 1974, then you can confirm this for yourselves. For completenesses sake, I tried to find an ISBN number for the above book. But Amazon and Barnes and Noble don't appear to stock it (although it looks like a revised version, by the same author, is due out in October 1999, in case anyone's interested). PR: docs/10488 Submitted by: solon@macaulay.demon.co.uk
* Add ipfw recompile and bpfilter -> bpf changesimp1999-08-011-1/+9
|
* Note need to recompile pccardd with latest kernel.imp1999-08-011-1/+5
|
* o Add additional printfs for error cases when we can't attach the device.imp1999-08-013-9/+29
| | | | | | | | o Add field to dev_desc for the size of the io port range. This isn't used yet in the committed sources, but will make the transition easier in the future. If you build this into your kernel, you will need to rebuild pccardd.
* o Add "debuglevel" keyword to config file.imp1999-08-016-35/+78
| | | | | | | | | | | | | | | | | | | o Document debug level keyword o Implement debug level: o For most of the diagnostic messages, change them from #ifdef DEBUG to if (debuglevel > 0). o Add a couple more diagnostic messages that weren't present before o Fix a couple of excessively long lines. Reviewed by: hosokawa-san o Start to implement the stopgap kludge for -current's pccard code by passing the length of the i/o range. If DEV_DESC_HAS_SIZE is defined, we'll set the size. This is done as an ifdef so that I can generate patches against the kernel more easily. o Add preliminary support for tweaking sleep times, but leave it disabled until a good range of values can be established. Didn't fix: logmsg problem noted by Nate.
* Make ipfw's logging more dynamic. Now, log will use the default limitgreen1999-08-016-23/+184
| | | | | | | | | | | | | _or_ you may specify "log logamount number" to set logging specifically the rule. In addition, "ipfw resetlog" has been added, which will reset the logging counters on any/all rule(s). ipfw resetlog does not affect the packet/byte counters (as ipfw reset does), and is the only "set" command that can be run at securelevel >= 3. This should address complaints about not being able to set logging amounts, not being able to restart logging at a high securelevel, and not being able to just reset logging without resetting all of the counters in a rule.
* Clarify that "-w" ignores horizontal white space changes.obrien1999-08-011-1/+1
|
* Sync with sys/i386/conf/majors.i386 revision 1.80.kato1999-08-011-1/+3
|
* Only use Bison to generate cc1plus's parse code.obrien1999-08-012-4/+4
|
* Cleanup - diked out a heap of old KLM stuff that isn't needed anymore.newton1999-08-011-65/+3
|
* Remove inappropriate references to the wrong name for the bootstrapgrog1999-08-012-16/+2
| | | | | | | manager, thus killing two birds with one stone. Objected-to-by: bde rnordier
* Move the memory access behavior information provided by madvisealc1999-08-016-24/+38
| | | | | | from the vm_object to the vm_map. Submitted by: dillon
* pmap_object_init_pt:alc1999-07-313-6/+6
| | | | Verify that object != NULL.
* Fixed $Id$.bde1999-07-311-3/+3
| | | | | | | Removed POSIX.1/NetBSD markup (braces) for NAME_MAX, etc. We don't define this. Most FreeBSD man pages hard-code the limits; in fact, utimes.2 recently became the only file in libc/sys/*.2 that mentions NAME_MAX. There probably should be mandoc macros for this.
OpenPOWER on IntegriCloud