src/usr.bin, branch releng/5.2 FreeBSD source tree FreeBSD-SA-04:16.fetch: 2004-11-18T12:06:51+00:00 Colin Percival cperciva@FreeBSD.org 2004-11-18T12:06:51+00:00 64f548f29dfa03dbc90350a6bb8df956250b3357 MFC revision 1.75 of src/usr.bin/fetch/fetch.c Bump newvers.sh and document in UPDATING. Approved by: so 
MFC revision 1.75 of src/usr.bin/fetch/fetch.c
Bump newvers.sh and document in UPDATING.

Approved by:	so
This commit was manufactured by cvs2svn to create branch 'RELENG_5_2'. 2003-12-07T03:02:28+00:00 cvs2svn cvs2svn@FreeBSD.org 2003-12-07T03:02:28+00:00 a348451bd8bd6d66bcb5b23f2aaec00e74c1292f 






Add a -E (elapsed time) flag to kdump.  This is like -T, except it is
2003-12-07T01:06:32+00:00

Peter Wemm
peter@FreeBSD.org

2003-12-07T01:06:32+00:00

ec1319146409505b0f5038c4f89d84e68e7f6618

relative to start of the dump.

Approved by:  re (scottl)





relative to start of the dump.

Approved by:  re (scottl)







Add Japan's real entry into the Second World War.
2003-12-06T22:49:30+00:00

Greg Lehey
grog@FreeBSD.org

2003-12-06T22:49:30+00:00

6edf37b0f2f1d69c885b423aef910e2b3bcea5bd

http://www.abcmalaysia.com/tour_malaysia/kltn_japivsn.htm





http://www.abcmalaysia.com/tour_malaysia/kltn_japivsn.htm







Fix some minor nits in netstat whereby large interface names would be
2003-11-28T17:34:23+00:00

Bruce M Simpson
bms@FreeBSD.org

2003-11-28T17:34:23+00:00

25d295e1ed7cbf742863f69cad80636eadf988d5

truncated. In environments where many tunnel or vlan interfaces are created,
interface names have high numbers which overflow the field width.

PRs:		bin/52349, bin/35838
Submitted by:	Mike Tancsa, Scot W. Hetzel
Approved by:	re (rwatson)





truncated. In environments where many tunnel or vlan interfaces are created,
interface names have high numbers which overflow the field width.

PRs:		bin/52349, bin/35838
Submitted by:	Mike Tancsa, Scot W. Hetzel
Approved by:	re (rwatson)







Grammar, spelling and punctuation sweep.
2003-11-26T08:38:32+00:00

Christian Brueffer
brueffer@FreeBSD.org

2003-11-26T08:38:32+00:00

5bd361ab30fd63f35eef410fe5b9f46886dd3984

Approved by:	re (rwatson)





Approved by:	re (rwatson)







/rescue/b{,un}zip exists, so build this dynamically now.
2003-11-17T05:19:37+00:00

David E. O'Brien
obrien@FreeBSD.org

2003-11-17T05:19:37+00:00

144ca80367edce3f751a1eef57dfc07fbd22ac6e












Update cross references after utf2/euc move.
2003-11-15T02:49:53+00:00

Tim J. Robbins
tjr@FreeBSD.org

2003-11-15T02:49:53+00:00

3bfa61d2211399850f899a4fbb7894c2e6526fc8












Do not ignore any possible errors that fseeko() may have. The fact
2003-11-13T09:04:24+00:00

Marcel Moolenaar
marcel@FreeBSD.org

2003-11-13T09:04:24+00:00

4e92419dcd0d7cb8db7f588e3efc16275592b920

is that fseeko() fails in very predictable and frequent ways on ia64.
This is because the offset is actually an address in the process'
address space, which on ia64 can be larger than long (for lseek) or
off_t (for fseeko). The crux is the signedness. The register stack
and memory stack are in region 4 on ia64. This means that the sign bit
is 1. The large positive virtual address is wrongly interpreted as
a negative file offset.

There's no quick fix. Even if you get around the API by using a
SEEK_SET up to LONG_MAX and follow it up with a SEEK_CUR for the
remainder, the kernel simply cannot deal with it. and the second
seek will just fail.

Therefore, this change does not actually fix the root cause. It just
makes sure we're not spitting out all kinds of garbage or that the
get_struct() function in particular does not cause truss(1) to exit.
This, I might add, invariably happened way too soon for truss(1) to
be of any use on ia64...





is that fseeko() fails in very predictable and frequent ways on ia64.
This is because the offset is actually an address in the process'
address space, which on ia64 can be larger than long (for lseek) or
off_t (for fseeko). The crux is the signedness. The register stack
and memory stack are in region 4 on ia64. This means that the sign bit
is 1. The large positive virtual address is wrongly interpreted as
a negative file offset.

There's no quick fix. Even if you get around the API by using a
SEEK_SET up to LONG_MAX and follow it up with a SEEK_CUR for the
remainder, the kernel simply cannot deal with it. and the second
seek will just fail.

Therefore, this change does not actually fix the root cause. It just
makes sure we're not spitting out all kinds of garbage or that the
get_struct() function in particular does not cause truss(1) to exit.
This, I might add, invariably happened way too soon for truss(1) to
be of any use on ia64...







make minimum column size for interrupt name be the heading (depends upon
2003-11-09T20:39:56+00:00

John-Mark Gurney
jmg@FreeBSD.org

2003-11-09T20:39:56+00:00

25d136776ed0fd05a303e032167d3a396f911633

Total being shorter than interrupt)..

Pointed out by:	bde





Total being shorter than interrupt)..

Pointed out by:	bde