On Sat, Apr 3, 2021 at 2:40 PM Ed Maste wrote:
> I propose deprecating the ftpd currently included in the base system
> before FreeBSD 14, and opened review D26447
> (https://reviews.freebsd.org/D26447) to add a notice to the man page.
> I had originally planned to try to do this before 13.0,
What's the error if you don't have these extra uintptr_t casts?
Warner
On Sat, Apr 3, 2021 at 12:18 AM Daniel Braniss wrote:
> I must be the last person on earth to use Hesiod :-)
> this are the diffs:
>
> diff --git a/lib/libc/gen/getgrent.c b/lib/libc/gen/getgrent.c
> index
On Mon, Mar 22, 2021, 10:19 AM Rainer Duffner
wrote:
>
>
> > Am 22.03.2021 um 16:34 schrieb Juraj Lutter :
> >
> >
> > To which branch do you want to apply those patches?
> >
> > Judging from the original patch date, I’d say that they have been
> developed against 13.0 at some point.
> > That
with RC2 now that it's out to see if it
is the same thing?
Warner
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
>
> On Sat, Mar 13, 2021 at 4:36 PM Warner Losh wrote:
>
On Sat, Mar 13, 2021 at 5:33 PM Kevin Oberman wrote:
> Just spent a little time looking at my issue and have a few more notes:
>
What version did you evaluate? There's a number of changes lately that
could have a big impact on this...
Warner
> Seems to only occur on large r/w operations
On Sat, Mar 13, 2021 at 9:44 AM Johan Hendriks
wrote:
> On 13/03/2021 17:09, Johan Hendriks wrote:
> > Hello all, i just upgrade my test server from 12.1 to 13.0-RC2. This
> > is a baremetal server.
> > It has two ssd's on ada0 and ada1 using zfs. Also there is a 6 disk
> > pool named storage.
>
On Tue, Mar 9, 2021 at 2:22 PM Patrick M. Hausen wrote:
> Hi Warner,
>
> > Am 09.03.2021 um 22:00 schrieb Warner Losh :One issue
> you may run into is the size of the partition. If it is tiny,
>
> > you'll likely have to create a new ESP. Using /boot/boot1.efi may he
On Tue, Mar 9, 2021 at 2:15 PM Ruben van Staveren wrote:
>
> Also, I’m missing /boot/*efifat* in FreeBSD13. What is the procedure for
>> updating EFI loaders?
>>
>
> They have been removed because they are no longer needed (filesystem
> images for boot blocks trouble me too).
>
>
> Agree, but
On Tue, Mar 9, 2021 at 8:56 AM Ruben van Staveren via freebsd-stable <
freebsd-stable@freebsd.org> wrote:
> Hi List,
>
> With FreeBSD 13 getting near release I was trying out a new hardware setup
> for a future upgrade, in where a zfs SATA RAID-10 array would be accelated
> by some NVME devices
On Sun, Mar 7, 2021, 9:49 AM Rodney W. Grimes
wrote:
> > Hi.
> >
> > Are you shure you're using *.memstick.img?
>
> I am shure I am NOT using memstick, as the subject says
> I am using:
> FreeBSD-13.0-RC1-amd64-disc1.iso
>
>
> > *.iso are for optical drives.
>
> Ah, not since 12.0, these
On Sat, Feb 27, 2021 at 12:15 AM Kevin Oberman wrote:
> Well, back to a full clone. Thanks for the "--unshallow" argument, but so
> far it has failed twice. I suspect that it's my urtwn interface is bad.
> I'll swap it out tomorrow and see it that fixes it.
>
> I am a bit surprised at how little
On Fri, Feb 26, 2021 at 9:35 AM Ed Maste wrote:
> On Thu, 25 Feb 2021 at 15:58, Warner Losh wrote:
> >
> > The problem, though, can happen when you run a shallow clone or gitup to
> > get the sources and build from that. In that case the v number is bogus
> > (hmmm
:56, Warner Losh wrote:
>
>
> On Thu, Feb 25, 2021 at 6:37 AM Karl Denninger wrote:
>
>> On 2/25/2021 04:30, Olivier Certner wrote:
>> >> Neither command is what I'd call 'intuitive', so it would have taken
>> me a
>> >> long time to find either of
On Thu, Feb 25, 2021 at 6:37 AM Karl Denninger wrote:
> On 2/25/2021 04:30, Olivier Certner wrote:
> >> Neither command is what I'd call 'intuitive', so it would have taken me
> a
> >> long time to find either of them. I cut and pasted the 'git branch'
> command
> >> and it took me a moment to
gt; > > OBJS was not the correct implementation in hindsight.
> > >
> > > 3.) The failure mode if it's *missing* is exactly the same before and
> > > after your patch; file can't be found, cannot build it.
> > >
> > > On Tue, Feb 23, 2021 at 12:09 PM
On Tue, Feb 23, 2021, 4:51 PM Chris wrote:
> Given this is a pkg(8) error, I brought it up on ports@
> but it was suggested I (also?) bring it up here on stable@
>
> OK awhile back I installed a copy of 12 stable from the
> usb stick image. I tweaked it to my wishes then got called
> away and
out-of-date? That seems like it is indicative of a larger problem that
> we'd surely fall over elsewhere on if not for here, that the source
> tree's timestamps are post-dated w.r.t. the objdir.
>
> Thanks,
>
> Kyle Evans
>
> On Mon, Feb 22, 2021 at 5:52 PM Warner Losh wrote:
>
at 4:17 PM Dean E. Weimer wrote:
> On 2021-02-22 10:53 am, Dean E. Weimer wrote:
> > On 2021-02-22 9:38 am, Dean E. Weimer via freebsd-stable wrote:
> >> On 2021-02-22 9:29 am, Warner Losh wrote:
> >>
> >>> On Mon, Feb 22, 2021 at 8:24 AM Dean E.
On Mon, Feb 22, 2021 at 8:24 AM Dean E. Weimer via freebsd-stable <
freebsd-stable@freebsd.org> wrote:
> I was able to successfully build and install BETA2 from source, however
> I am now attempting to upgrade the same machine to BETA3 buildworld and
> buildkernel complete. installkernel also
On Fri, Feb 19, 2021 at 2:42 PM David Marec wrote:
> On 19/02/2021 22:00, Warner Losh wrote:
> > We can't do that. gptzfsboot is for something else that we can't get rid
> > of: BIOS/CMS booting.
>
>
> My bad. I mean 'gptboot.efifat'.
>
>
> root@machine:~ # mdco
On Fri, Feb 19, 2021 at 2:21 PM Kurt Jaeger wrote:
> Hi!
>
> > You can upgrade to 13 w/o hassle. The upgrade process doesn't
> automatically
> > upgrade the zpools. The only problem is if you also do a 'zpool upgrade'
> > which will change your zpool features. The fix is easy: upgrade your boot
On Fri, Feb 19, 2021 at 1:49 PM Greg Rivers via freebsd-stable <
freebsd-stable@freebsd.org> wrote:
> On Friday, 19 February 2021 12:24:24 CST Kurt Jaeger wrote:
> > > > Unfortunately it contains an old version of the boot loader:
> > [...]
> > > We should be better about upgrading boot blocks,
On Fri, Feb 19, 2021 at 1:41 PM David Marec
wrote:
> Hi,
>
> On 19/02/2021 19:24, Kurt Jaeger wrote:
>
> > I suspect that your 'zpool upgrade' enabled things that weren't enabled
> > before. This caused the old boot blocks to no longer work.
>
> Correct. That' s definitely the source of the
On Fri, Feb 19, 2021 at 11:24 AM Kurt Jaeger wrote:
> Hi!
>
> > > Unfortunately it contains an old version of the boot loader:
> [...]
> > We should be better about upgrading boot blocks, but EFI is kinda new and
> > kinda different than the other out-of-root-filesystem boot blocks we've
> had
>
On Fri, Feb 19, 2021 at 8:13 AM David Marec
wrote:
> I have just upgrade one machine from 12-stable to 13-stable.
>
> Everything runs fine until the main ZFS pool was upgraded.
>
> Then the box stopped booting.
>
> Thanks to a FreeBSD-13 Beta2 usb stick, I was able to fix the issue by
> copying
you very
> much for all your efforts on this big move to git!
>
> ---Mike
>
> On 2/18/2021 3:45 PM, Warner Losh wrote:
> > The problem is that it was a merge commit, which should have been
> > administratively prohibited. A merge commit from main to stable/* is
> &g
The problem is that it was a merge commit, which should have been
administratively prohibited. A merge commit from main to stable/* is never
the right thing. It creates problems, not least of which is the issue with
the subversion exporter. In this case, it won't create the more severe
issues like
On Thu, Feb 18, 2021 at 3:33 AM mike tancsa wrote:
> On 2/17/2021 12:10 PM, Warner Losh wrote:
> > On Feb 17, 2021, at 6:05 AM, mike tancsa wrote:
> >> I noticed on a box that I update RELENG_12 via git there are more
> >> recent commits then if I use svnli
> On Feb 12, 2021, at 11:03 PM, Dewayne Geraghty
> wrote:
> As a change management task, I would hope that a mapping between svnlite
> and git would've become available for FreeBSD users, similar to the cvs
> to svnlite migration. I guess we need to create a test machine to
> figure out the
> On Feb 12, 2021, at 5:31 PM, tech-lists wrote:
> As subject, where to get sources for 12-stable upgrade now? Is it still
> svn or is it git?
tl;dr: git is the source of truth, but there’s a bunch of details that might
matter.
The current source of truth is git repository on
> On Feb 17, 2021, at 6:05 AM, mike tancsa wrote:
> I noticed on a box that I update RELENG_12 via git there are more
> recent commits then if I use svnlite to track. Are they only
> periodically updated ? If so, how frequently do they get refreshed ?
> e.g. I see the new OpenSSL version
On Sun, Jan 3, 2021, 8:57 PM Dewayne Geraghty <
dewa...@heuristicsystems.com.au> wrote:
> I'm using
> https://cgit.freebsd.org/src/log/?h=stable%2F12
> to monitor changes to FreeBSD 12.2Stable, as I used to use
> https://lists.freebsd.org/pipermail/svn-src-stable-12/2020-December/
>
> The git
On Wed, Dec 23, 2020 at 7:32 AM Michael Grimm wrote:
> Hi,
>
> Warner Losh wrote:
>
> > The FreeBSD project will be moving it's source repo from subversion to
> git
> > starting this this weekend.
>
> First of all I'd like to thank all those involved in this f
On Wed, Dec 23, 2020 at 3:35 AM Marek Zarychta <
zarych...@plan-b.pwste.edu.pl> wrote:
> W dniu 17.12.2020 o 01:46, Warner Losh pisze:
> > Greetings,
> >
> > The FreeBSD project will be moving it's source repo from subversion to
> git
> > starting this thi
Greetings,
The FreeBSD project will be moving it's source repo from subversion to git
starting this this weekend. The docs repo was moved 2 weeks ago. The ports
repo will move at the end of March, 2021 due to timing issues.
The short version is that we're switching the version control we're
On Mon, Nov 30, 2020 at 5:35 PM Yasuhiro KIMURA wrote:
> I made clean install of 11.4-RELEASE amd64 with ZFS root and UEFI boot
> mode. 'Auto (ZFS)' was used at disk setup phase and disk was
> partitioned as following.
>
> --
>
Yes. That's correct.
Warner
On Sun, Sep 13, 2020 at 2:27 PM Greg Balfour wrote:
> Since this won't boot on my i586 I'm assuming it was compiled for i686?
> ___
> freebsd-stable@freebsd.org mailing list
>
On Mon, Aug 31, 2020 at 2:51 PM Christoph Moench-Tegeder
wrote:
> ## Charles Lecklider via freebsd-stable (freebsd-stable@freebsd.org):
>
> > As you can see from objdump below, clearly a decision was made that 11.4
> > would no longer support anything before a i686.
>
> Given that the hardware
Greetings,
I'd like to retire the spkr driver. It was a cute hack before sound cards
were ubiquitous, but it's not been kept up to date, and it's not clear that
it still works It is still Giant locked, and though it's not a huge
effort to do the locking I literally have no way to test it that
Greetings
I just pushed https://svnweb.freebsd.org/changeset/base/364725 into
-current.
In documenting all the messages that devd can receive from the kernel, I
noticed an inconsistency I'd like to correct. We currently have both
system=kernel and system=kern generated by the kernel. This makes
Liby.a was retired. Maybe there is some dangling references?
On Sat, Jul 25, 2020, 2:05 PM Don Lewis wrote:
> I'm seeing this failure when building 11-STABLE and 12-STABLE poudriere
> jails:
>
> --- localedef.full ---
> cc -O2 -pipe -fno-common -I.
>
On Sun, Jun 28, 2020, 1:52 AM Dimitry Andric wrote:
> On 28 Jun 2020, at 04:21, Kyle Evans wrote:
> >
> > On Sat, Jun 27, 2020 at 8:04 PM Yasuhiro KIMURA
> wrote:
> >>
> >> On UEFI booted 11.4-RELEASE system `efivar -l` fails as following.
> >>
> >> root@rolling-vm-freebsd3[160]# uname -a
> >>
On Wed, Jun 3, 2020 at 10:12 AM Kyle Evans wrote:
> On Wed, Jun 3, 2020 at 11:06 AM Budi Janto
> wrote:
> >
> >
> >
> > On 6/3/20 6:50 PM, Kyle Evans wrote:
> > > Can you post a sample of your /boot/lodaer.conf, please? Though, the
> > > efipart_readwrite error smack dab in the middle leaves me
On Thu, Apr 30, 2020 at 11:48 AM Stefan Bethke wrote:
> nvme0: async event occurred (type 0x1, info 0x00, page 0x02)
> nvme0: device reliability degraded
>
type 1: SMART event
info 0: reliability error
page 2: look at what's up here
1.4 standard says:
NVM subsystem Reliability: NVM subsystem
Boot single user. Zfs won't import and you can do what you need.
Warner
On Sun, Apr 12, 2020, 8:37 AM Stefan Bethke wrote:
> I have a server I don't have physical access to right now, which has a
> broken SATA disk that produces mostly errors (but not entirely).
>
> The disk has two partitions
On Thu, Mar 5, 2020 at 6:01 AM David Wolfskill wrote:
> On Thu, Mar 05, 2020 at 01:54:58PM +0100, Trond Endrestøl wrote:
> > The command
> > "sh /usr/src/usr.sbin/amd/include/newvers.sh
> /usr/src/sys/conf/newvers.sh"
> > is run a part of a normal build, creating config_local.h.
> >
> > After
On Sat, Feb 29, 2020, 1:18 PM Ed Maste wrote:
> Is anyone using sync serial drivers ce, cp, ctau, or cx? NYCBUG's
> dmesg didn't turn up any entries. I suspect these are obsolete and
> ought to be removed.
>
These date from the 2000s. They were important for point to point links
until maybe
On Wed, Feb 26, 2020, 8:54 PM Mario Olofo wrote:
> Hello Mark,
>
> Yes, I think that it's related to the WD Green SSD.
> Today I found this bug on FreeBSD's bugzilla:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225666
>
> Tried to reinstall and recompile the kernel with the patch but it
On Wed, Nov 13, 2019 at 11:34 AM Theron wrote:
> With latest 12.1-STABLE (r354687), I have file access 30 second hang
> problem again when resuming from suspend, with dmesg:
>
> nvme0: Resetting controller due to a timeout.
> nvme0: resetting controller
> nvme0: aborting outstanding i/o
> nvme0:
On Thu, Nov 7, 2019 at 10:07 AM mike tancsa wrote:
> Hi All,
>
> In the past, I could do something like
>
> Mount via nfs a RELENG12 kernel and world, do the appropriate
> #mount_nfs 192.168.143.5:/crossbuilds /crossbuilds/
> # setenv MAKEOBJDIRPREFIX /crossbuilds/obj/12/
>
> and then do an
No. That's netboot which is a different path in the loader.
Warner
On Wed, Nov 6, 2019, 5:04 PM George Michaelson wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239876 is relevant
> maybe?
>
> On Thu, Nov 7, 2019 at 9:46 AM Julian Elischer wrote:
> >
> > On
On Wed, Nov 6, 2019 at 2:03 PM Chris Ross wrote:
> On Wed, Nov 06, 2019 at 02:17:11PM -0500, Chris Ross wrote:
> >
> > Hi there. I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a
> system
> > here, which didn't work, and I found that
> FreeBSD-12.0-RELEASE-amd64-disc1.iso
> > did work
On Sat, Nov 2, 2019 at 10:20 AM Glen Barber wrote:
> On Sat, Nov 02, 2019 at 02:12:50PM +, Sergey A. Osokin wrote:
> > On Fri, Nov 01, 2019 at 02:52:50PM +, Glen Barber wrote:
> > > On Fri, Nov 01, 2019 at 01:44:18PM +, Sergey A. Osokin wrote:
> > > > At the moment we have
On Tue, Sep 24, 2019 at 5:46 PM John Fleming
wrote:
> Is there anyway to see how busy a SAS/Sata controller is vs disks? I
> have a R720 with 14 Samsung 860 EVOs in it (its a lab server) in raid
> 10 ZFS.
>
> When firing off a dd I (bs=1G count=10) seems like the disks never go
> above %50 busy.
On Wed, Sep 18, 2019, 10:05 PM Sean Bruno wrote:
> If one installs 12.1 and tries to run a 12.0 release package (postgresql
> server for instance), it fails due to a missing symbol:
>
> # service postgresql start
> /usr/local/bin/pg_ctl: Undefined symbol "stat@FBSD_1.5"
>
> I think this is a
On Thu, Sep 5, 2019 at 12:08 PM Nikos Vassiliadis wrote:
> Hi,
>
> I have this in my devd rules:
> > notify 10 {
> > match "system" "ZFS";
> > match "type""misc.fs.zfs.scrub_start";
> > action "touch /var/run/scrub_$pool_name; logger -t ZFS 'zpool
>
On Tue, Aug 6, 2019 at 4:32 PM mike tancsa wrote:
> I did a fresh install of a RELENG12 image and did EFI for the boot /
> install process. Most everything seems to work ok, but the boot menu
> gets double text printing. As before and after is OK, its not a huge
> thing, but is there a way to
On Tue, Jul 9, 2019 at 12:12 AM Dimitry Andric wrote:
> On 9 Jul 2019, at 08:08, Warner Losh wrote:
> >
> > On Mon, Jul 8, 2019 at 11:58 PM Dimitry Andric wrote:
> > On 8 Jul 2019, at 17:38, Warner Losh wrote:
> > >
> > > On Mon, Jul 8, 2019 at 7:21 AM M
On Mon, Jul 8, 2019 at 11:58 PM Dimitry Andric wrote:
> On 8 Jul 2019, at 17:38, Warner Losh wrote:
> >
> > On Mon, Jul 8, 2019 at 7:21 AM Mike Tancsa wrote:
> >> On 7/8/2019 3:09 AM, Patrick M. Hausen wrote:
> >>> Hi all,
> >>>
>
On Sun, Jul 7, 2019, 8:23 PM Mike Tancsa wrote:
> Hi,
>
> I am trying to source update a RELENG_10 (stable) image to
> RELENG_11, but buildworld breaks. On another box, I can go to 11.2R,
> but dies with RELENG_11. I am guessing its not possible to build the
> latest clang from 10 thats in
On Sun, Apr 28, 2019 at 4:03 PM Karl Denninger wrote:
> On 4/20/2019 15:56, Steven Hartland wrote:
> > Thanks for extra info, the next question would be have you eliminated
> > that corruption exists before the disk is removed?
> >
> > Would be interesting to add a zpool scrub to confirm this
On Fri, Apr 19, 2019 at 2:55 AM Mel Pilgrim
wrote:
> This is still waiting for MFC to stable/11 and stable/12. Would someone
> please have a look at it? Warner Losh has timed out.
>
Just merged it.
Warner
___
freebsd-stable@freebsd.org mai
What did you upgrade from?
Warner
On Sat, Apr 13, 2019, 11:21 AM Filippo Moretti via freebsd-stable <
freebsd-stable@freebsd.org> wrote:
> I upgraded my amd64 box to today stable but the system no longer boot it
> hangs or reboots after Loading kernel modulesAny help appreciated.I can
> still
On Fri, Apr 12, 2019, 1:22 PM Patrick M. Hausen wrote:
> Hi Warner,
>
> thanks for taking the time again …
>
> > OK. This means that whatever I/O workload we've done has caused the NVME
> card to stop responding for 30s, so we reset it.
>
> I figured as much ;-)
>
> > So it's an intel card.
>
>
On Fri, Apr 12, 2019 at 6:00 AM Patrick M. Hausen wrote:
> Hi all,
>
> my problems seem not to be TRIM related after all … and I can now
> quickly reproduce it.
>
> =
> root@freenas01[~]# sysctl vfs.zfs.trim.enabled
> vfs.zfs.trim.enabled: 0
> =
> root@freenas01[~]# cd /mnt/zfs
>
On Wed, Apr 10, 2019 at 10:46 PM wrote:
> Peter Holm wrote:
>
> > I see this even with a single truncate on HEAD.
> >
> > $ ./truncate10.sh
> > 96 -rw-r--r-- 1 root wheel 1073741824 11 apr. 06:33 test
> > ** /dev/md10a
> > ** Last Mounted on /mnt
> > ** Phase 1 - Check Blocks and Sizes
> >
On Fri, Apr 5, 2019 at 1:33 AM Patrick M. Hausen wrote:
> Hi all,
>
> > Am 04.04.2019 um 17:11 schrieb Warner Losh :
> > There's a request that was sent down to the drive. It took longer than
> 30s to respond. One of them, at least, was a trim request.
> > […]
>
On Fri, Apr 5, 2019 at 6:41 AM Patrick M. Hausen wrote:
> Hi all,
>
> in addition to the aborted commands every dozen of system boots or so
> (this order of magnitude) the kernel simply hangs during initialisation of
> one of the NVME devices:
>
> https://cloud.hausen.com/s/TxPTDFJwMe6sJr2
>
>
On Thu, Apr 4, 2019 at 2:39 AM Patrick M. Hausen wrote:
> Hi all,
>
> I’m currently doing some load tests/burn in for two new servers.
> These feature all NVME SSDs and run FreeNAS, i.e. FreeBSD 11.2-STABLE.
>
> pcib17: at device 3.2 numa-domain 1 on pci15
> pcib17:
On Sun, Mar 24, 2019, 3:58 PM tech-lists wrote:
> Hi
>
> [context is freebsd-12R-p3]
>
> Is it possible to convert a running freebsd guest from UFS to ZFS?
> It would need to be done in-situ, in the guest as there is no access to
> the host.
>
> The guest filesystem is:
>
> /dev/gpt/rootfs /
On Sun, Mar 24, 2019, 9:52 AM Brett Glass wrote:
> Warner:
>
> Thank you! I thought that perhaps it might be useful to (for example) keep
> Ethernet port names the same when ports were added to the system. But if
> it's not, I'll just deactivate it. I do need to keep devd on, because I
>
On Sat, Mar 23, 2019 at 6:27 PM Brett Glass wrote:
> Everyone:
>
> I've been building custom kernels for FreeBSD 12.0, and have noticed
> a message on the console, during boot, that I haven't seen from prior
> versions. It doesn't affect the operation of the system, but just for
> the sake of
On Tue, Mar 19, 2019 at 4:53 PM James Snow wrote:
> Hello -stable,
>
> We have a PXE environemt that builds FreeBSD-11 boxes. We've started
> to dip our toes into the 12.x waters, but have had trouble getting
> FreeBSD-12 to pxeboot. It would crash and burn like so:
>
> Startup error in
I generally like this idea... But two caveats...
First, we'd need to update the docs so that folks doing serial installs can
unset it Though serial installs are a weird beast
Second, if it's really needed, we should have the installer generate it.
alas, only vt can tell us that, but it
Bummer. This has been the case for a while now, and the pc98 people haven't
complained. :(
Warner
On Sat, Mar 9, 2019 at 12:49 PM Enji Cooper wrote:
> I just ran into the following build failure on ^/stable/11 with a fresh
> SVN checkout — “make clean” from the top-level directory failed like
On Thu, Feb 28, 2019 at 10:00 AM Rodney W. Grimes <
free...@pdx.rh.cn85.dnsmgr.net> wrote:
> [ Charset UTF-8 unsupported, converting... ]
> > On Thu, 28 Feb 2019 at 09:33, Rodney W. Grimes
> > wrote:
> > >
> > > LD?=ld.lld in the right place(s)?
> >
> > Perhaps, I seem to recall some issue with
On Thu, Jan 31, 2019 at 11:19 PM Eugene Grosbein wrote:
> On 01.02.2019 11:10, Warner Losh wrote:
>
> > On Thu, Jan 31, 2019, 8:22 PM Eugene Grosbein <mailto:eu...@grosbein.net> wrote:
> >
> > Hi!
> >
> > I wonder what is status of our c
On Fri, Feb 1, 2019, 11:05 AM Brooks Davis On Fri, Feb 01, 2019 at 04:00:50AM -0800, Rodney W. Grimes wrote:
> > > On Thu, Jan 31, 2019 at 11:43:44PM +, Brooks Davis wrote:
> > > > We are currently planning to remove the following less-popular 10/100
> > > > Ethernet drivers in the
On Thu, Jan 31, 2019, 8:22 PM Eugene Grosbein Hi!
>
> I wonder what is status of our contrib/libarchive and bsdtar/bsdcpio etc.
> in modern versions of FreeBSD
> in a sense of serious bug fixing. Long story short: I faced a bug in the
> libarchive bundled with 11.2
> that makes it impossible to
On Sat, Jan 26, 2019 at 1:01 PM Karl Denninger wrote:
> Further question does boot1.efi (which I assume has to be placed on
> the EFI partition and then something like rEFInd can select it) know how
> to handle a geli-encrypted primary partition (e.g. for root/boot so I
> don't need an
On Fri, Jan 11, 2019 at 3:09 PM Walter Parker wrote:
> Hi,
>
> I'd like to boot FreeBSD 12 on a system where the OS is installed to a ZFS
> pool that can't be booted by the OS.
>
> This is a pre-UEFI machine. It has a pair of SAS drives and 3 PCIe slots.
> What I'd like to do is put the boot
On Fri, Jan 11, 2019 at 3:22 PM Gary Palmer wrote:
> On Fri, Jan 11, 2019 at 01:18:35PM -0600, Kyle Evans wrote:
> > On Fri, Jan 11, 2019 at 1:15 PM Jonathan Chen wrote:
> > >
> > > On Sat, 12 Jan 2019 at 07:55, Stefan Bethke wrote:
> > > [...]
> > > > The UEFI man page has a good explanation
On Fri, Jan 11, 2019 at 12:19 PM Warner Losh wrote:
>
>
> On Fri, Jan 11, 2019 at 12:17 PM Jonathan Chen wrote:
>
>> On Sat, 12 Jan 2019 at 07:55, Stefan Bethke wrote:
>> [...]
>> > The UEFI man page has a good explanation of which files are invo
On Fri, Jan 11, 2019 at 12:17 PM Jonathan Chen wrote:
> On Sat, 12 Jan 2019 at 07:55, Stefan Bethke wrote:
> [...]
> > The UEFI man page has a good explanation of which files are involved in
> booting:
> >
> https://www.freebsd.org/cgi/man.cgi?query=uefi=8=freebsd-release-ports
> >
> > I
On Thu, Dec 27, 2018, 4:11 PM Konstantin Belousov On Thu, Dec 27, 2018 at 09:41:06PM +0100, Thierry Thomas wrote:
> > Hello,
> >
> > Trying to upgrade a machine from
> >
> > 11.2-STABLE #0 r337833: Wed Aug 15 12:50:47 CEST 2018
> >
> > to 12-STABLE as:
> >
> > Working Copy Root Path: /usr/src
> >
On Sun, Dec 16, 2018, 6:33 PM Alan Somers CC the package maintainer.
>
> As for powerpc on tier 1, I'm afraid that it's not likely to ever
> happen. Powerpc is dying. If anybody were buying new ppc hardware,
> then it would be a different story. But I predict that powerpc is
> likely to be
On Thu, Dec 13, 2018, 6:19 AM Mark Martinec On one of my hosts (now running 12.0-RELEASE) the zfsboot shows
> this weird negative number, which sounds suspicious:
>
>Verifying DMI pool Data .
>Shortening read at 3907029152 from 16 to 15
>Shortening read at 7435283708 from
On Tue, Dec 4, 2018, 7:25 PM George Mitchell /usr/src/UPDATING says:
>
> To build a kernel
> -
> If you are updating from a prior version of FreeBSD (even one just
> a few days old), you should follow this procedure. It is the most
>
On Thu, Nov 29, 2018 at 8:09 AM Alan Somers wrote:
> On Mon, Nov 26, 2018 at 3:57 PM Warner Losh wrote:
>
>> On Mon, Nov 26, 2018 at 3:32 PM Maxim Sobolev
>> wrote:
>>
>> > Somebody needs to make collection/submission automatic and make a port
>> out
only when there's a material change...
And I'd rather we get more nuanced data than dmesg can provide if we were
to do the data collection. The admonition to submit to this site was one of
expedience...
Warner
> -Max
>
> On Mon, Nov 26, 2018 at 2:08 PM Yuri Pankov wrote:
>
> > Yuri P
On Mon, Nov 12, 2018 at 11:39 AM Sven Vermeulen
wrote:
> 4) make installkernel (using a custom kernel config)
>
> installkernel gives some warnings with kldxref:
>
> kldxref /boot/kernel
> kldxref: unknown metadata record 4 in file aic.ko
> kldxref: unknown metadata record 4 in file atacard.ko
>
My sense is that amd64 is tier 1. i386, armv7 and arm64 are close. armv6
and armv5 are tier2.
Warner
On Wed, Oct 24, 2018 at 10:06 AM Mark Millard via freebsd-stable <
freebsd-stable@freebsd.org> wrote:
> I note that https://pkg.freebsd.org/ does not list FreeBSD:12:aarch64
> under the Tier-2
On Wed, Oct 24, 2018 at 6:19 AM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > > On 24 Oct 2018, at 01:23, Warner Losh wrote:
> > >
> > > On Tue, Oct 23, 2018 at 6:02 PM Rodney W. Grimes <
> > > freebsd-...@pdx.rh.cn85.dnsmgr.ne
On Wed, Oct 24, 2018 at 5:02 AM Bob Bishop wrote:
>
> > On 24 Oct 2018, at 01:23, Warner Losh wrote:
> >
> > On Tue, Oct 23, 2018 at 6:02 PM Rodney W. Grimes <
> > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> >
> >> -- Start of PGP signed section
On Tue, Oct 23, 2018 at 6:02 PM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> -- Start of PGP signed section.
> > On Tue, Oct 23, 2018 at 04:26:45PM -0700, Rodney W. Grimes wrote:
> > > > On Tue, Oct 23, 2018 at 5:07 PM Rodney W. Grimes <
> > > >
On Tue, Oct 23, 2018 at 5:26 PM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > On Tue, Oct 23, 2018 at 5:07 PM Rodney W. Grimes <
> > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> >
> > > > On Tue, Oct 23, 2018 at 11:33:35PM +0200, Julian H. Stacey wrote:
> > > > > > I'd also
On Tue, Oct 23, 2018 at 3:57 PM Julian H. Stacey wrote:
> Doug Hardie wrote:
> > I have a number of production servers that only have bge and I don't see
> that listed in either category. None of them are running FreeBSD 12 yet as
> it has not been released. Also there are some with rl. Those
On Tue, Oct 23, 2018 at 5:07 PM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > On Tue, Oct 23, 2018 at 11:33:35PM +0200, Julian H. Stacey wrote:
> > > > I'd also suggest that rl stands in stark contrast to the cs, wb, sn,
> smc,
> > > > sf, tl, tx and vr drivers, which nobody
On Tue, Oct 23, 2018 at 5:54 AM Toomas Soome wrote:
>
> > On 23 Oct 2018, at 13:53, Lev Serebryakov wrote:
> >
> > On 22.10.2018 12:27, Toomas Soome wrote:
> >
> >> It would help to get output from loader lsdev -v command.
> > current loader crashes on "lsdev" for me:
> >
On Mon, Oct 22, 2018 at 6:39 AM Mark Millard wrote:
> On 2018-Oct-22, at 4:07 AM, Toomas Soome wrote:
>
> > On 22 Oct 2018, at 13:58, Mark Millard wrote:
> >>
> >> On 2018-Oct-22, at 2:27 AM, Toomas Soome wrote:
> >>>
> >>>> On 22 Oct
1 - 100 of 502 matches
Mail list logo
