|
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
| #
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.
|
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1, v2.2.0, v2.3.0, v2.1.1, v2.0.1 |
|
| #
a8b658ef |
| 20-Oct-2006 |
Peter Avalos <pavalos@dragonflybsd.org> |
Remove an unused argument and mark it WARNS6.
|
| #
76d9d116 |
| 17-Oct-2006 |
Peter Avalos <pavalos@dragonflybsd.org> |
Pull WARNS6 into sbin/Makefile.inc, and mark programs that are not WARNS6
in their own Makefiles.
|
| #
90ee1e64 |
| 04-Apr-2005 |
Liam J. Foy <liamfoy@dragonflybsd.org> |
- WARNS -> WARNS?
Noticed by: Sarunas Vancevicius <svan@redbrick.dcu.ie>
|
| #
1213fdc4 |
| 02-Apr-2005 |
Matthew Dillon <dillon@dragonflybsd.org> |
WARNS=6 cleanup.
Submitted-by: Sepherosa Ziehau <sepherosa@softhome.net>
With-some-modification-by: Matt Dillon
|
| #
86ed60a6 |
| 18-Jun-2004 |
Matthew Dillon <dillon@dragonflybsd.org> |
Write a remote configuration utility called 'rconfig'. This initial
implementation is very basic and designed to be convienient. It allows a
CD user to scan the network for configuration servers, d
Write a remote configuration utility called 'rconfig'. This initial
implementation is very basic and designed to be convienient. It allows a
CD user to scan the network for configuration servers, download a
configuration script based on a tag name, and execute that script all in
one simple command. Running the rconfig server is just as easy... you
basically just run the server -a -s and put your scripts in
/usr/local/etc/rconfig/<tagname>.sh and you are done.
Of course the scripts themselves have to be written and can certainly become
quite complex.
In order to use rconfig from a CD Boot at least one network interface must
be properly configured. The dhclient program is usually used to accomplish
this.
show more ...
|