RCS cannot deal with duplicate tags; the extra one always becomes
inaccessible and useless.
This will prevent the common mistake of specifying the same name
for the vendor tag and the release tag. The FreeBSD CVS repository
already contains zillions of files with this error. We don't need
any more of them.
of this patch, which had not actually been reviewed by Joerg or Paul!
(I'll better stop committing files after midnight ...)
I'm now commiting the latest code, which has been reported to work.
Minor correction to the previous commit message for this file:
The first PCI Lance in a system will get a name of lnc1, the second
will be known as lnc2 and so on. An arbitrary number of cards is
supported in a system ...
before attaching. Without this fix, 3c579(EISA) never make
any H/W inturrupt.
Reviewed by: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>, nao@sbl.cl.nec.co.jp and owner-current on mailing list ;-)
Submitted by: amurai@spec.co.jp, nao@sbl.cl.nec.co.jp
This code applies to several systems with integrated Ethernet
chip, for example from HP or Compaq. It should also support
PCI Ethernet cards based on the AMD PCI Lance chip.
This code has been reviewed (visually) by Paul Richards and
tested (using an ISA Lance board) by Joerg Wunsch.
Since the parameters to nearly each and every single function
had to be changed (generally from unit number to lnc_soft*),
there is some potential for buglets having crept in ...
BEWARE: If you had lnc0 configured to have the ISA probe find
your PCI Lance, then it should now be found by the PCI probe,
and should be automatically configured as pci1 (!!! note the "1").
Reviewed by: paul, joerg
part that does zic(8)/zdump(8) is still yet to be imported (but the old
zic and zdump will work just fine with these header files and the
data format has not changed).
primarily bugfixes, but is also contains a disclaimer of copyright.
As we are completely off the vendor branch here, this import has
no effect on the source tree.
Changed zones: Algeria, Egypt, Ghana, Libya, Morocco, Sierra Leone,
South Africa, Sudan, Tunisia, Armenia, Myanmar, China, Taiwan, Hong
Kong, Macao, Cyprus, Georgia, Iran, Israel, Jordan, Kazakhstan,
Kirgizstan, Lebanon, Mongolia, the Phillippines, Syria, Tajikistan,
Turkmenistan, Uzbekistan, Australia, Kiribati, New Caledonia, New
Zealand, Vanuatu, the United Kingdom, Ireland, the Czech Republic,
Finland, France, Greece, Hungary, Iceland, Italy, Luxembourg, the
Netherlands, Norway, Portugal, Romania, Spain, Switzerland, Turkey,
Canada, Mexico, the Bahamas, Barbados, Belize, Costa Rica, Cuba, the
Dominican Republic, El Salvador, Guatemala, Haiti, Nicaragua,
Brazil, the Falkland Islands, Paraguay
Deleted zones: Asia/Tomsk (superseded by Asia/Krasnoyarsk)
Added zones: Asia/Aktau (area formerly part of Asia/Alma-Ata);
Asia/Krasnoyarsk (supersedes Asia/Tomsk); America/Glace_Bay (area
formerly part of America/Halifax); America/Thunder_Bay,
America/Nipigon, America/Rainy_River (areas formerly covered by
America/Montreal); America/Swift_Current (area formerly part of
America/Regina); America/Dawson_Creek (area formerly part of
America/Vancouver); America/Pangnirtung, America/Iqaluit,
America/Rankin_Inlet, America/Yellowknife, America/Inuvik,
America/Dawson (areas formerly part of America/Whitehorse)
The fundamental problem with the original code is that it accesses
p[-2] which is one before the beginning of the input buffer for
empty lines. rev.1.6 just moved the problem from failures when
p[-2] happens to be '\\' to failures when it happens to be '\0'.
rev.1.5 was confused about the trailing newline and other things.
I went back to rev.1.5 and fixed it. The result is the same as
Keith Bostic's final version in PR 1356 except it loses more
gracefully for excessively long input lines.
in the POSIX section for a log time. The non-POSIX getgrouplist() and
setgroups() were recently added to the POSIX section although setgroups()
was already in the non-POSIX section.
rick@snowhite.cis.uoguelph.ca:
1. Clear B_NEEDCOMMIT in nfs_write to make sure that dirty data is
correctly send to the server. If a buffer was dirtied when it was in
the B_DELWRI+B_NEEDCOMMIT state, the state of the buffer was left
unchanged and when the buffer was later cleaned, just a commit rpc was
made to the server to complete the previous write. Clearing
B_NEEDCOMMIT ensures that another write is made to the server.
2. If a server returned a server (for whatever reason) returned an
answer to a write RPC that implied that fewer bytes than requested
were written, bad things would happen.
3. The setattr operation passed on the atime in stead of the mtime to
the server. The fix is trivial.
4. XIDs always started at 0, but this caused some servers (older DEC
OSF/1 3.0 so I've been told) who had very long-lasting XID caches to
get confused if, after a reboot of a BSD client, RPCs came in with a
XID that had in the past been used before from that client. Patch is
to use the current time in seconds as a starting point for XIDs. The
patch below is not perfect, because it requires the root fs to be
mounted first. This is because of the check BSD systems do, comparing
FS time to system time.
Reviewed by: Bruce Evans, Terry Lambert.
Obtained from: frank@fwi.uva.nl (Frank van der Linden) via rick@snowhite.cis.uoguelph.ca
