Re: libc.so dependency on libssp_nonshared.a

On Feb 2, 2015, at 23:47, Gleb Kurtsou wrote: > On (02/02/2015 17:06), Jeremie Le Hen wrote: >> Hi Gleb, >> On Sun, Feb 1, 2015 at 9:24 PM, Gleb Kurtsou wrote: >>> I came across some build issues in libc.so and SSP. >>> >>> libc.ldscript (aka libc.so) unconditionally includes >>> @@LIBDIR@@/li

Jenkins build is back to stable : FreeBSD_HEAD-tests2 #639

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: tzsetup chroot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/03/15 17:05, Nick Frampton wrote: > We have our own FreeBSD 10.1 installation script in which we call > tzsetup. > > I'm seeing different behaviour in tzsetup between these two > invocations: > > tzsetup -C /mnt chroot /mnt /usr/sbin/tzsetup

tzsetup chroot

We have our own FreeBSD 10.1 installation script in which we call tzsetup. I'm seeing different behaviour in tzsetup between these two invocations: tzsetup -C /mnt chroot /mnt /usr/sbin/tzsetup With the -C option, no matter which time zone I select, it asks: Does the abbreviation 'UTC' l

Jenkins build became unstable: FreeBSD_HEAD-tests2 #638

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HP 2B19WM PCI-E SD Reader

On Mon, 2 Feb 2015, R0B_ROD wrote: > Thank you for the time you took to help. > > According to: >http://lists.freebsd.org/pipermail/ \ >\ freebsd-current/2013-July/042788.html >\ freebsd-questions/2014-August/259843.html > > Is the Realtek RTS5229 PCI-E SD Card Reader > supported yet?

Re: PSA: If you run -current, beware!

On Tue, 2015-02-03 at 13:33 -0800, Peter Wemm wrote: > Sometime in the Dec 10th through Jan 7th timeframe a timing bug has been > introduced to 11.x/head/-current.With HZ=1000 (the default for bare > metal, > not for a vm); the clocks stop just after 24 days of uptime. This means > things

Re: PSA: If you run -current, beware!

On Tuesday, February 3, 2015, Peter Wemm wrote: > Sometime in the Dec 10th through Jan 7th timeframe a timing bug has been > introduced to 11.x/head/-current.With HZ=1000 (the default for bare > metal, > not for a vm); the clocks stop just after 24 days of uptime. This means > Signed 32

PSA: If you run -current, beware!

Sometime in the Dec 10th through Jan 7th timeframe a timing bug has been introduced to 11.x/head/-current.With HZ=1000 (the default for bare metal, not for a vm); the clocks stop just after 24 days of uptime. This means things like cron, sleep, timeouts etc stop working. TCP/IP won't time

Re: Filepaths in VM map for tmpfs files

On Mon, Feb 02, 2015 at 09:50:22PM -0600, Eric Badger wrote: > > On 02/02/2015 03:30 AM, Konstantin Belousov wrote: > > On Sun, Feb 01, 2015 at 08:38:29PM -0600, Eric Badger wrote: > >> On 01/31/2015 09:36 AM, Konstantin Belousov wrote: > >>> First, shouldn't the kve_type changed to KVME_TYPE_VNOD

Re: tzsetup - UTC user question

On 03.02.2015 13:25, Kurt Jaeger wrote: Hi! The person doing the install may not know what the clock is currently set to, especially when installing in a VM. Perhaps the screen should display the current machine time so they can correctly answer the question. Yes, this would help tremendousl

Re: tzsetup - UTC user question

Hi! > The person doing the install may not know what the clock is currently set > to, especially when installing in a VM. Perhaps the screen should display > the current machine time so they can correctly answer the question. Yes, this would help tremendously! -- p...@opsec.eu+49 1

Re: tzsetup - UTC user question

On Tue, Feb 03, 2015 at 03:08:38PM +1000, Paul Koch wrote: > > Since the default option for "Select local or UTC clock" changed from > "No" to "Yes", we are seeing many customers who incorrectly answer this > question! > > This screws up things in our app because we store all data in UTC. > > A

tzsetup - UTC user question

Since the default option for "Select local or UTC clock" changed from "No" to "Yes", we are seeing many customers who incorrectly answer this question! This screws up things in our app because we store all data in UTC. A few observations... Most people don't know what "CMOS clock" is. Maybe ch

Jenkins build is back to normal : Build-UFS-image #1025

See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Build failed in Jenkins: Build-UFS-image #1024

See -- Started by build flow Build_Image_and_Run_Tests_in_Bhyve_HEAD#673 Building remotely on jenkins-10.freebsd.org (FreeBSD-10) in workspace > g

Build failed in Jenkins: Build-UFS-image #1023

See -- Started by build flow Build_Image_and_Run_Tests_in_Bhyve_HEAD#672 Building remotely on jenkins-10.freebsd.org (FreeBSD-10) in workspace > g