Skip site navigation (1)Skip section navigation (2)


2021/freebsd-current/20210919.freebsd-current

Messages: 32, new messages first
Last update: Mon Feb 13 14:17:22 2023

home | archive sorted by: subject | author | date | reverse date
  1. Sep 19 Ed Maste                   Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden
  2. Sep 17 David Chisnall             Re: Building ZFS disk images
  3. Sep 17 FreeBSD User               Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden
  4. Sep 17 George Michaelson          Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy:
  5. Sep 17 Mark Millard via freebsd-c Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy:
  6. Sep 16 Freddie Cash               Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy:
  7. Sep 16 Mark Millard via freebsd-c Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy:
  8. Sep 16 Tomoaki AOKI               Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy:
  9. Sep 16 Mark Millard via freebsd-c Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy:
 10. Sep 16 Alan Somers                Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy:
 11. Sep 16 Mark Millard via freebsd-c Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy:
 12. Sep 16 Mark Millard via freebsd-c Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy:
 13. Sep 16 Alan Somers                Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy:
 14. Sep 16 joe mcguckin               Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy:
 15. Sep 16 Mark Millard via freebsd-c zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy: "no
 16. Sep 15 Tomoaki AOKI               Re: git commit for WITH_DETECT_TZ_CHANGES breaks date, et al
 17. Sep 14 Amar Takhar                Re: Call for participation
 18. Sep 14 Tomoaki AOKI               Re: git commit for WITH_DETECT_TZ_CHANGES breaks date, et al
 19. Sep 14 Konstantin Belousov        Re: recent head having significantly less "avail memory"
 20. Sep 14 Julian H. Stacey           Re: src/lib/libgcc_s needs mv /usr/obj/usr/src/amd64.amd64/lib/libc/libc.a


21. Sep 14 Merv Hammer Re: Call for participation 22. Sep 14 Michael Gmelin Re: git commit for WITH_DETECT_TZ_CHANGES breaks date, et al 23. Sep 14 Gary Jennejohn Re: git commit for WITH_DETECT_TZ_CHANGES breaks date, et al 24. Sep 14 Michael Butler via freebsd git commit for WITH_DETECT_TZ_CHANGES breaks date, et al 25. Sep 13 Guido Falsi via freebsd-cu Re: recent head having significantly less "avail memory" 26. Sep 13 Konstantin Belousov Re: recent head having significantly less "avail memory" 27. Sep 13 Guido Falsi via freebsd-cu Re: recent head having significantly less "avail memory" 28. Sep 13 Guido Falsi via freebsd-cu Re: recent head having significantly less "avail memory" 29. Sep 13 Ryan Stone Re: recent head having significantly less "avail memory" 30. Sep 13 Guido Falsi via freebsd-cu Re: recent head having significantly less "avail memory" 31. Sep 13 Konstantin Belousov Re: recent head having significantly less "avail memory" 32. Sep 13 Guido Falsi via freebsd-cu recent head having significantly less "avail memory"


home | archive sorted by: subject | author | date | reverse date