Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Oct 2013 15:45:23 -0700
From:      Lyndon Nerenberg <lyndon@orthanc.ca>
To:        David Chisnall <theraven@FreeBSD.org>
Cc:        "freebsd-current@freebsd.org" <freebsd-current@FreeBSD.org>
Subject:   Re: rcs is gone?
Message-ID:  <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca>
In-Reply-To: <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org>
References:  <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <F9A84DDF-EC24-42F2-9B34-F5041946293D@orthanc.ca> <EBF54472-4DF9-42AB-9577-B7CEFFFFFA1E@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On 2013-10-07, at 2:53 PM, David Chisnall <theraven@FreeBSD.org> wrote:

> Or do you really only run the base OS and no other software on your =
systems, without any of your own code or any customisation?

We install from the base release ISO images burned on DVDs.

We are physically air-gapped from the internet, none of the "end users" =
of the system have access to USB ports, and there are no electronic =
devices allowed into the development shop.

We have a scheme for bringing in software from /usr/ports, but it is =
painful.  And those ports can't necessarily walk on to all the systems =
in the shop.  (I don't make the rules.  Suffice to say the company is =
very paranoid about their code getting out into the wild.)

Having RCS in the base system is very useful.  We use it to track =
changes to bits of /etc on the machines where we don't do wholesale =
customizations.  (Those ones get git, but they also get an install of =
/usr/ports with a fully populated /usr/ports/distfiles.)

So if nuking RCS is a case of "I don't use it," ... we do.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?132C8A43-E822-49C3-A1EA-493A40449AD4>