On Sun, 27 Jan 2013 09:51:12 -0500
MFV wrote:
> Hello Matthew,
>
> Thanks for an outstanding piece of documentation. It resolves a
> number of concerns I had and convinced me to move from portsnap where
> I discovered an apparent bug that gave me security concerns. More
> specifically I manual
On Sun, 27 Jan 2013, Matthew Seaman wrote:
2) Choose a protocol for access the SVN servers. Your choices in
order of preference are
svn://
https://
http://
Use svn:// for best performance. If you're concerned about MITM
attacks injecting trojans into the
Steve O'Hara-Smith writes:
> > The only downside with svn seems to be the 728 MB footprint.
>
> With hard disc space running at around 10c per gigabyte it's a
> minor issue.
Doesn't that depend on whose money it is?
Robert Huff
___
On Sun, 27 Jan 2013 09:51:12 -0500
MFV wrote:
> The only downside with svn seems to be the 728 MB footprint.
With hard disc space running at around 10c per gigabyte it's a
minor issue.
--
Steve O'Hara-Smith
___
freebsd-questions@freebsd.org
Hello Matthew,
Thanks for an outstanding piece of documentation. It resolves a number of
concerns I had and convinced me to move from portsnap where I discovered an
apparent bug that gave me security concerns. More specifically I manually
edited /usr/ports/UPDATING and portsnap did not recog
On 27/01/2013 12:46, Matthew Seaman wrote:
> Cheers,
>
> Matthew
>
Matthew,
Fantastic howto ! Thanks ! Really a good job...as usual :-)
Peter
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
On 27/01/2013 10:07, Mike Clarke wrote:
> I suppose the best approach with ZFS would be to make a snapshot immediately
> prior to running portsnap.
Yes. That would do the trick quite neatly. In fact, snapshot before
each time you run portsnap.
Cheers
Matthew
--
Dr Matthew J
On 27/01/2013 08:35, Zyumbilev, Peter wrote:
> Last 10 years I am using cvsup. Any good guide for the transition to
> subversion ?
Most of the guides around freebsd.org are aimed at developers who will
be using SVN read-write. For simple read-only use (ie. not checking
anything into the reposito
On Sunday 27 Jan 2013 09:46:51 Matthew Seaman wrote:
> to get yourself a portsnap-ready copy of the ports tree. You only need
> to do that once, but you should move aside any pre-existing copy of
> /usr/ports obtained by any means other than portsnap(8) before you do
> (but keep anything under /u
On 27/01/2013 00:11, W. D. wrote:
> What would be the best Cron command to keep ports updated on a daily
> basis?
Try this as a crontab entry:
0 3 * * * * /usr/sbin/portsnap cron update
Two points to note:
1) The 'cron' verb is important for anyone setting up an automated job
like this.
On 27/01/2013 06:34, Lowell Gilbert wrote:
> If you needed version control features on your ports tree (especially if
> you were regularly contributing changes to ports), getting and updating
> your tree through subversion would have some extra features you might
> want, but it doesn't sound as i
"W. D." writes:
> According to:
>
> http://www.freebsd.org/news/2012-compromise.html
>
> Cvsup is deprecated. If I have a Cron entry like:
>
> #-
> #Min HrDOM Mnth DOW Command
>
> # At 3:46 in the morning, everyday, a
According to:
http://www.freebsd.org/news/2012-compromise.html
Cvsup is deprecated. If I have a Cron entry like:
#-
#Min HrDOM Mnth DOW Command
# At 3:46 in the morning, everyday, as root, update the ports tree:
46
13 matches
Mail list logo
