Re: getting the running patch level

2012-08-20 Thread Simon L. B. Nielsen
On 19 Aug 2012, at 13:33, Jilles Tjoelker wrote: > On Sat, Aug 11, 2012 at 09:05:44PM +0200, Dag-Erling Smørgrav wrote: >> "Simon L. B. Nielsen" writes: >>> This has been discussed a number of time, but there are no nice and >>> simple solution. > >> There is a simple solution that, while not

[HEADSUP] geli(4) weak master key generation on -CURRENT

2012-08-20 Thread Simon L. B. Nielsen
Hello, If you are not using geli(4) on -CURRENT (AKA FreeBSD 10) you can safely ignore this mail. If you are, please read on! -CURRENT users of geli(4) should be advised that, a geli(4) device may have weak master key, if the provider is created on -CURRENT system built against source code betwee

Re: getting the running patch level

2012-08-20 Thread Peter Jeremy
On 2012-Aug-19 16:46:37 +0200, Paul Schenkeveld wrote: > - Teach both installworld and freebsd-update to maintain manifest >files of what is installed and log that update, place all manifests >somewhere under /var/db and the update log in /var/log. I'm not sure what detail you intend her

Re: getting the running patch level

2012-08-20 Thread Paul Schenkeveld
On Thu, Aug 09, 2012 at 11:44:02AM +0200, Roberto wrote: > > Hi all, > I would like to know if there is a command or a way to retrieve the "patch > level" (the handbook defines it "builds names" like 7.0-RELEASE-p1) of the > running system: just an example, if I run: > > # freebsd-update fetch >