Ship it!
Glen
Sent from my phone.
Please excuse my brevity and/or typos.
> On Aug 13, 2023, at 2:39 PM, George Mitchell wrote:
>
> On 8/11/23 23:15, Glen Barber wrote:
>> [...]
>> It was discovered that due to human error (my own) the arm64 are, as
>> Colin put it very politely, are "lacking '
On Fri, Aug 11, 2023 at 08:53:12PM +, Glen Barber wrote:
[...]
> FreeBSD/aarch64 UFS EC2 AMIs are available in the following regions:
>
[...]
>
> FreeBSD/aarch64 ZFS EC2 AMIs are available in the following regions:
>
[...]
It was discovered that due to human error (my own) the arm64 are,
> --mikej
>>
>>
>>
>>
>>
>> *From:* Rob Wing [mailto:rob.fx...@gmail.com]
>> *Sent:* Monday, February 21, 2022 9:30 PM
>> *To:* Michael Jung
>> *Cc:* Hans Petter Selasky ; freebsd-current <
>> freebsd-current@freebsd.org>
>&
Monday, February 21, 2022 9:30 PM
> *To:* Michael Jung
> *Cc:* Hans Petter Selasky ; freebsd-current <
> freebsd-current@freebsd.org>
> *Subject:* Re: New panic in main-n253273-a52d8d4a6c6:
>
>
>
> The previous attached patch should work for testing purposes, but it&#x
, February 21, 2022 9:30 PM
To: Michael Jung
Cc: Hans Petter Selasky ; freebsd-current
Subject: Re: New panic in main-n253273-a52d8d4a6c6:
The previous attached patch should work for testing purposes, but it's
incorrect if an error occurs.
The fhold() should be below FILEDESC_SUNLOCK(),
have
>> received this transmission in error, please notify us by
>> telephone at (502) 212-4000 or notify us at: PAI, Dept. 99,
>> 2101 High Wickham Place, Suite 101, Louisville, KY 40245
>>
>>
>>
>> *From:* Michael Jung
>> *Sent:* Monday, Februa
please notify us by
> telephone at (502) 212-4000 or notify us at: PAI, Dept. 99,
> 2101 High Wickham Place, Suite 101, Louisville, KY 40245
>
>
>
> *From:* Michael Jung
> *Sent:* Monday, February 21, 2022 9:06 PM
> *To:* 'Hans Petter Selasky' ; freebsd-current &l
From: Michael Jung
Sent: Monday, February 21, 2022 9:06 PM
To: 'Hans Petter Selasky' ; freebsd-current
Subject: RE: New panic in main-n253273-a52d8d4a6c6:
From: Hans Petter Selasky [mailto:h...@selasky.org]
Sent: Monday, February 21, 2022 8:34 PM
To: Michael Jung
From: Hans Petter Selasky [mailto:h...@selasky.org]
Sent: Monday, February 21, 2022 8:34 PM
To: Michael Jung ; freebsd-current
Subject: Re: New panic in main-n253273-a52d8d4a6c6:
On 2/22/22 00:42, Michael Jung wrote:
> Hi:
>
> I was trying to remember what I did that was odd when t
kinda thinking this might be related to commit f40dd6c8034b ("tty: switch
ttyhook_register to use fget_cap_locked")
fget_unlocked() must have grabbed an extra reference count on the file
pointer that fget_cap_locked() doesn't get
On Mon, Feb 21, 2022 at 4:35 PM Hans Petter Selasky wrote:
> On 2
On 2/22/22 00:42, Michael Jung wrote:
Hi:
I was trying to remember what I did that was odd when this crash occurred then
it
hit me. You can repeat this panic by doing:
# watch -I -W pts/0
Here is another panic that happened write after issuing "watch" for comparison.
http://mail.mikej.com/c
com/info.1
http://mail.mikej.com/vmcore.1
--mikej
-Original Message-
From: Michael Jung
Sent: Monday, February 21, 2022 6:22 PM
To: 'Hans Petter Selasky' ; freebsd-current
Subject: RE: New panic in main-n253273-a52d8d4a6c6:
-Original Message-
From: Hans Pett
-Original Message-
From: Hans Petter Selasky [mailto:h...@selasky.org]
Sent: Monday, February 21, 2022 8:53 AM
To: Michael Jung ; freebsd-current
Subject: Re: New panic in main-n253273-a52d8d4a6c6:
On 2/21/22 14:07, Michael Jung wrote:
> (kgdb) fram 16
> #16 0x80bad
On 2/21/22 14:07, Michael Jung wrote:
(kgdb) fram 16
#16 0x80bad587 in closefp_impl (fdp=0xfe012b7c0430, fd=4,
fp=0xf801cc119280, td=0xfe00df8d0560, audit=true) at
/usr/src/sys/kern/kern_descrip.c:1300
1300error = closef(fp, td);
(kgdb) print /x *fdp
$1 = {fd_fi
-Original Message-
From: owner-freebsd-curr...@freebsd.org
[mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Hans Petter Selasky
Sent: Monday, February 21, 2022 2:48 AM
To: Michael Jung ; freebsd-current
Subject: Re: New panic in main-n253273-a52d8d4a6c6:
On 2/20/22 21:53
On 2/20/22 21:53, Michael Jung wrote:
Hi!
The box was quite busy at the time. The only odd thing I am aware of and which
I do
not think is related is I have not been able to expand one of my zpool's. ZFS
sees my
added draid2:2d:10c:0s vdev but I can't seem to force zpool's expansion - my
be
On Tue, Aug 31, 2021 at 2:06 AM Konstantin Belousov
wrote:
> On Tue, Aug 31, 2021 at 01:29:27AM -0500, Dustin Marquess wrote:
> > On Mon, Aug 30, 2021 at 4:33 AM Konstantin Belousov
> wrote:
> >
> > > On Sun, Aug 29, 2021 at 08:27:02PM -0500, Dustin Marquess wrote:
> > > > I am upgrading a -CURR
On Tue, Aug 31, 2021 at 01:29:27AM -0500, Dustin Marquess wrote:
> On Mon, Aug 30, 2021 at 4:33 AM Konstantin Belousov wrote:
>
> > On Sun, Aug 29, 2021 at 08:27:02PM -0500, Dustin Marquess wrote:
> > > I am upgrading a -CURRENT box from a build that's exactly 2 weeks old to
> > > one I built abo
On Mon, Aug 30, 2021 at 4:33 AM Konstantin Belousov wrote:
> On Sun, Aug 29, 2021 at 08:27:02PM -0500, Dustin Marquess wrote:
> > I am upgrading a -CURRENT box from a build that's exactly 2 weeks old to
> > one I built about 2 hours ago. After installkernel I updated the
> bootloader
> > the same
On Sun, Aug 29, 2021 at 08:27:02PM -0500, Dustin Marquess wrote:
> I am upgrading a -CURRENT box from a build that's exactly 2 weeks old to
> one I built about 2 hours ago. After installkernel I updated the bootloader
> the same way I normally do:
>
> # mount_msdosfs /dev/da8p1 /mnt
> # cp /mnt/EF
On Sun, Aug 29, 2021 at 7:28 PM Dustin Marquess wrote:
> I am upgrading a -CURRENT box from a build that's exactly 2 weeks old to
> one I built about 2 hours ago. After installkernel I updated the bootloader
> the same way I normally do:
>
> # mount_msdosfs /dev/da8p1 /mnt
> # cp /mnt/EFI/BOOT/BO
On Tue, Feb 16, 2021 at 1:48 AM Harry Schmalzbauer
wrote:
> Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current:
> > On 2021-Feb-13, at 16:40, Warner Losh wrote:
> >
> >> Are you aware of gpart create?
> >>
> >> Warner
> > From which I derive that I had an implicit, incorrect
> > as
On 2021-Feb-16, at 02:22, Harry Schmalzbauer wrote:
> Am 16.02.2021 um 11:08 schrieb Mark Millard:
>> On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote:
>>> Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current:
On 2021-Feb-13, at 16:40, Warner Losh wrote:
> Are you aw
Am 16.02.2021 um 11:08 schrieb Mark Millard:
On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote:
Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current:
On 2021-Feb-13, at 16:40, Warner Losh wrote:
Are you aware of gpart create?
Warner
From which I derive that I had an implicit
On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote:
> Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current:
>> On 2021-Feb-13, at 16:40, Warner Losh wrote:
>>
>>> Are you aware of gpart create?
>>>
>>> Warner
>> From which I derive that I had an implicit, incorrect
>> assumption tha
Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current:
On 2021-Feb-13, at 16:40, Warner Losh wrote:
Are you aware of gpart create?
Warner
From which I derive that I had an implicit, incorrect
assumption that gpart show would in some way list
everything available that gpart could m
On 2021-Feb-13, at 17:38, Warner Losh wrote:
> On Sat, Feb 13, 2021, 6:36 PM Mark Millard wrote:
>
> On 2021-Feb-13, at 16:40, Warner Losh wrote:
>
> > Are you aware of gpart create?
> >
> > Warner
>
> From which I derive that I had an implicit, incorrect
> assumption that gpart show would
On Sat, Feb 13, 2021, 6:36 PM Mark Millard wrote:
>
> On 2021-Feb-13, at 16:40, Warner Losh wrote:
>
> > Are you aware of gpart create?
> >
> > Warner
>
> From which I derive that I had an implicit, incorrect
> assumption that gpart show would in some way list
> everything available that gpart c
On 2021-Feb-13, at 16:40, Warner Losh wrote:
> Are you aware of gpart create?
>
> Warner
>From which I derive that I had an implicit, incorrect
assumption that gpart show would in some way list
everything available that gpart could manipulate
(including for use in creation).
So I need to fin
Are you aware of gpart create?
Warner
On Sat, Feb 13, 2021, 4:41 PM Mark Millard via freebsd-current <
freebsd-current@freebsd.org> wrote:
> I plugged in a new Optane and booted FreeBSD on the
> ThreadRipper 1950X system but FreeBSD did not show
> the drive in gpart show. (It is unique by size i
Ruslan Garipov wrote:
Hi!
After I had updated my FreeBSD 13.0-CURRENT r365443 amd64 to r365738 the
following messages started to appear on the console/log:
$ egrep "not implemented|async_" /var/log/messages | fgrep "Sep 18"
Sep 18 08:19:05 {host_name} kernel: __pm_runtime_resume not
implemented
On Thu, Sep 10, 2020 at 04:53:30PM +, Glen Barber wrote:
> On Thu, Sep 10, 2020 at 06:43:08PM +0200, Emmanuel Vadot wrote:
> > Which port commit and which board ? There haven't been a commit in the
> > u-boot ports or rpi-firmware this a month now so I fails to understand
> > without more info
clay@bsd13:~ $ uname -a
FreeBSD bsd13 13.0-CURRENT FreeBSD 13.0-CURRENT #0
1544934ffb2-c253004(main): Thu Sep 10 06:18:34 UTC 2020
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
Works great, no problems with snapshot, thanks much Glen & everybody.
On Thu, Sep 10, 2020 at 06:43:08PM +0200, Emmanuel Vadot wrote:
> On Thu, 10 Sep 2020 16:36:44 +
> Glen Barber wrote:
>
> > On Thu, Sep 10, 2020 at 06:25:51PM +0200, Emmanuel Vadot wrote:
> > > On Thu, 3 Sep 2020 16:00:51 +
> > > Glen Barber wrote:
> > >
> > > > On Thu, Sep 03, 2020 at
On Thu, 10 Sep 2020 16:36:44 +
Glen Barber wrote:
> On Thu, Sep 10, 2020 at 06:25:51PM +0200, Emmanuel Vadot wrote:
> > On Thu, 3 Sep 2020 16:00:51 +
> > Glen Barber wrote:
> >
> > > On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot wrote:
> > > >
> > > > Hello,
> > > >
> > >
On Thu, Sep 10, 2020 at 06:25:51PM +0200, Emmanuel Vadot wrote:
> On Thu, 3 Sep 2020 16:00:51 +
> Glen Barber wrote:
>
> > On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot wrote:
> > >
> > > Hello,
> > >
> > > On Thu, 3 Sep 2020 15:02:45 +
> > > Glen Barber wrote:
> > >
> > >
On Thu, 3 Sep 2020 16:00:51 +
Glen Barber wrote:
> On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot wrote:
> >
> > Hello,
> >
> > On Thu, 3 Sep 2020 15:02:45 +
> > Glen Barber wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > >
> > > New FreeBSD deve
On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot wrote:
>
> Hello,
>
> On Thu, 3 Sep 2020 15:02:45 +
> Glen Barber wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > New FreeBSD development branch installation ISOs and virtual machine
> > disk images have bee
Am 2020-09-03 17:02, schrieb Glen Barber:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
New FreeBSD development branch installation ISOs and virtual machine
disk images have been uploaded to the FreeBSD Project mirrors.
=== Virtual Machine Disk Images ===
VM disk images are available for t
Hello,
On Thu, 3 Sep 2020 15:02:45 +
Glen Barber wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> New FreeBSD development branch installation ISOs and virtual machine
> disk images have been uploaded to the FreeBSD Project mirrors.
>
> NOTE: These are the first snapshots b
On Thu, Mar 12, 2020 at 11:11:53AM +0100, Michael Gmelin wrote:
>
>
> On Thu, 12 Mar 2020 10:31:40 +0100
> Alexander Leidinger wrote:
>
> > Hi,
> >
> > This command sets the keyboard layout. You are supposed to set the
> > keyboard layout which matches the physical layout of the hardware.
> >
On Thu, Mar 12, 2020 at 04:53:32PM +0100, Michael Gmelin wrote:
>
>
> On Thu, 12 Mar 2020 10:36:42 -0500
> Bob Willcox wrote:
>
> > On Thu, Mar 12, 2020 at 07:24:42AM -0500, Bob Willcox wrote:
> > > On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote:
> > > >
> > > >
> > > > SN
On Thu, 12 Mar 2020 10:36:42 -0500
Bob Willcox wrote:
> On Thu, Mar 12, 2020 at 07:24:42AM -0500, Bob Willcox wrote:
> > On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote:
> > >
> > >
> > > SNIP SNAP
> > > >> It might fix the ???Down key opens application launcher???
> > > >
On Thu, Mar 12, 2020 at 07:24:42AM -0500, Bob Willcox wrote:
> On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote:
> >
> >
> > > On 11. Mar 2020, at 23:25, Bob Willcox wrote:
> > >
> > > ???On Wed, Mar 11, 2020 at 11:04:18PM +0100, Michael Gmelin wrote:
> > >>
> > >>
> > On 1
On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote:
>
>
> > On 11. Mar 2020, at 23:25, Bob Willcox wrote:
> >
> > ???On Wed, Mar 11, 2020 at 11:04:18PM +0100, Michael Gmelin wrote:
> >>
> >>
> On 11. Mar 2020, at 22:58, Bob Willcox wrote:
> >>>
> >>> ???On Wed, Mar 11, 2020
On Thu, 12 Mar 2020 10:31:40 +0100
Alexander Leidinger wrote:
> Hi,
>
> This command sets the keyboard layout. You are supposed to set the
> keyboard layout which matches the physical layout of the hardware.
> This hadn't changed, it's a fundamental part of X11 since I know it
> (X11 6.5) and
Hi,
This command sets the keyboard layout. You are supposed to set the keyboard
layout which matches the physical layout of the hardware. This hadn't
changed, it's a fundamental part of X11 since I know it (X11 6.5) and even
before...
For those which had an explicit setting in xorg.conf (lik
Bob Willcox wrote in
<20200311214930.gc5...@rancor.immure.com>:
|On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote:
|>>> On 11. Mar 2020, at 10:29, Mark Martinec
|>>> wrote:
...
| I just updated my laptop from source, and somewhere along the way
| the key-codes Xorg sees
> On 11. Mar 2020, at 23:25, Bob Willcox wrote:
>
> On Wed, Mar 11, 2020 at 11:04:18PM +0100, Michael Gmelin wrote:
>>
>>
On 11. Mar 2020, at 22:58, Bob Willcox wrote:
>>>
>>> ???On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote:
???
>> On 11. Mar 2020, at 10:29,
On Wed, Mar 11, 2020 at 11:04:18PM +0100, Michael Gmelin wrote:
>
>
> > On 11. Mar 2020, at 22:58, Bob Willcox wrote:
> >
> > ???On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote:
> >> ???
> On 11. Mar 2020, at 10:29, Mark Martinec
> wrote:
> >>> ???
>
> > I ju
> On 11. Mar 2020, at 22:58, Bob Willcox wrote:
>
> On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote:
>> ???
On 11. Mar 2020, at 10:29, Mark Martinec
wrote:
>>> ???
> I just updated my laptop from source, and somewhere along the way
> the key-codes Xorg s
On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote:
> ???
> >> On 11. Mar 2020, at 10:29, Mark Martinec
> >> wrote:
> > ???
> >>
> >>> I just updated my laptop from source, and somewhere along the way
> >>> the key-codes Xorg sees changed.
> >> Indeed. This doesn't just affect -CURRE
On Wed, Mar 11, 2020 at 1:51 PM Greg Rivers
wrote:
> On Wednesday, 11 March 2020 13:53:45 CDT Peter Jeremy wrote:
> > On 2020-Mar-11 10:29:08 +0100, Niclas Zeising
> wrote:
> > >This has to do with switching to using evdev to handle input devices on
> > >FreeBSD 12 and CURRENT. There's been sev
Hi!
> On 2020-Mar-11 10:29:08 +0100, Niclas Zeising wrote:
> >This has to do with switching to using evdev to handle input devices on
> >FreeBSD 12 and CURRENT. There's been several reports, and suggested
> >solutions to this, as well as an UPDATING entry detailing the change.
>
> The UPDATIN
On 2020-Mar-11 10:29:08 +0100, Niclas Zeising wrote:
>This has to do with switching to using evdev to handle input devices on
>FreeBSD 12 and CURRENT. There's been several reports, and suggested
>solutions to this, as well as an UPDATING entry detailing the change.
The UPDATING entry says that
>> On 11. Mar 2020, at 10:29, Mark Martinec
>> wrote:
>
>>
>>> I just updated my laptop from source, and somewhere along the way
>>> the key-codes Xorg sees changed.
>> Indeed. This doesn't just affect -CURRENT: it happened to me on
>> -STABLE last week, so I'm copying that list too.
>
> An
In message , Niclas Zeising w
rites:
>This has to do with switching to using evdev to handle input devices on
>FreeBSD 12 and CURRENT. There's been several reports, and suggested
>solutions to this, as well as an UPDATING entry detailing the change.
I don't think I would have thought
On 2020-03-11 10:29, Niclas Zeising wrote:
On 2020-03-11 01:46, Greg 'groggy' Lehey wrote:
Sorry. I should have thought of reporting it. For me, with a number
of other issues, it was a frustrating week,some of which are still not
resolved.
As a side note, if it's not reported, it's very hard
On 2020-03-11 10:27, Mark Martinec wrote:
I just updated my laptop from source, and somewhere along the way
the key-codes Xorg sees changed.
Indeed. This doesn't just affect -CURRENT: it happened to me on
-STABLE last week, so I'm copying that list too.
And a "Down" key now opens and closes
On 2020-03-11 01:46, Greg 'groggy' Lehey wrote:
On Wednesday, 11 March 2020 at 0:20:03 +, Poul-Henning Kamp wrote:
[originally sent to current@]
I just updated my laptop from source, and somewhere along the way
the key-codes Xorg sees changed.
Indeed. This doesn't just affect -CURRENT:
I just updated my laptop from source, and somewhere along the way
the key-codes Xorg sees changed.
Indeed. This doesn't just affect -CURRENT: it happened to me on
-STABLE last week, so I'm copying that list too.
And a "Down" key now opens and closes a KDE "Application Launcher",
alternatively
On Wednesday, 11 March 2020 at 0:20:03 +, Poul-Henning Kamp wrote:
[originally sent to current@]
> I just updated my laptop from source, and somewhere along the way
> the key-codes Xorg sees changed.
Indeed. This doesn't just affect -CURRENT: it happened to me on
-STABLE last week, so I'm c
On Fri, Dec 20, 2019 at 10:15 AM Konstantin Belousov
wrote:
>
> On Fri, Dec 20, 2019 at 09:51:15AM -0800, Ryan Libby wrote:
> > On Fri, Dec 20, 2019 at 9:31 AM Konstantin Belousov
> > wrote:
> > >
> > > On Fri, Dec 20, 2019 at 09:24:00AM -0800, John Baldwin wrote:
> > > > On 12/19/19 12:06 PM, R
On Fri, Dec 20, 2019 at 09:51:15AM -0800, Ryan Libby wrote:
> On Fri, Dec 20, 2019 at 9:31 AM Konstantin Belousov
> wrote:
> >
> > On Fri, Dec 20, 2019 at 09:24:00AM -0800, John Baldwin wrote:
> > > On 12/19/19 12:06 PM, Ryan Libby wrote:
> > > > On Wed, Dec 18, 2019 at 1:49 PM John Baldwin wrot
On Fri, Dec 20, 2019 at 9:31 AM Konstantin Belousov wrote:
>
> On Fri, Dec 20, 2019 at 09:24:00AM -0800, John Baldwin wrote:
> > On 12/19/19 12:06 PM, Ryan Libby wrote:
> > > On Wed, Dec 18, 2019 at 1:49 PM John Baldwin wrote:
> > >>
> > >> In the interest of supporting newer versions of GCC for
On Fri, Dec 20, 2019 at 09:24:00AM -0800, John Baldwin wrote:
> On 12/19/19 12:06 PM, Ryan Libby wrote:
> > On Wed, Dec 18, 2019 at 1:49 PM John Baldwin wrote:
> >>
> >> In the interest of supporting newer versions of GCC for a base system
> >> toolchain, I've renamed the external GCC packages fro
On 12/19/19 12:06 PM, Ryan Libby wrote:
> On Wed, Dec 18, 2019 at 1:49 PM John Baldwin wrote:
>>
>> In the interest of supporting newer versions of GCC for a base system
>> toolchain, I've renamed the external GCC packages from -gcc
>> to -gcc6. These are built as flavors of a new devel/freebsd-g
On Wed, Dec 18, 2019 at 1:49 PM John Baldwin wrote:
>
> In the interest of supporting newer versions of GCC for a base system
> toolchain, I've renamed the external GCC packages from -gcc
> to -gcc6. These are built as flavors of a new devel/freebsd-gcc6
> port. The xtoolchain package is not use
On 12/18/19 4:16 PM, Mark Millard wrote:
>
>
> On 2019-Dec-18, at 13:48, John Baldwin wrote:
>
>> In the interest of supporting newer versions of GCC for a base system
>> toolchain, I've renamed the external GCC packages from -gcc
>> to -gcc6. These are built as flavors of a new devel/freebsd-
On 2019-Dec-18, at 13:48, John Baldwin wrote:
> In the interest of supporting newer versions of GCC for a base system
> toolchain, I've renamed the external GCC packages from -gcc
> to -gcc6. These are built as flavors of a new devel/freebsd-gcc6
> port. The xtoolchain package is not used fo
Go fuck yourself. I’ll take my work to geonode.
Sent from my iPhone
> On Jul 9, 2019, at 6:21 AM, Ian Lepore wrote:
>
>> On Tue, 2019-07-09 at 10:51 +0400, Gleb Popov wrote:
>>> On Tue, Jul 9, 2019 at 1:33 AM Unidef wrote:
>>>
>>> Instead of just cc files*c -o file
>>>
>>> We can do
>>>
>>>
On Tue, 2019-07-09 at 10:51 +0400, Gleb Popov wrote:
> On Tue, Jul 9, 2019 at 1:33 AM Unidef wrote:
>
> > Instead of just cc files*c -o file
> >
> > We can do
> >
> > cc files*. -o file.c
> >
> > And cpp file*cpp -o file.cpp
> >
> > We can hook it up to a MySQL or a neural database? A neural
On Tue, Jul 9, 2019 at 1:33 AM Unidef wrote:
> Instead of just cc files*c -o file
>
> We can do
>
> cc files*. -o file.c
>
> And cpp file*cpp -o file.cpp
>
> We can hook it up to a MySQL or a neural database? A neural database is a
> multi dimensional multi directional binary tree with a master f
Glad to hear that Juli@ XTe also works fine!
Thank You for Your feedback!
Indeed, it is more logical to use "pcm" device instead of "vol", since "vol" is
designed to control so-called "master volume", not implemented in Juli@. But
mixer(8) tries to adjust this "vol" by default, if invoked withou
Everything works well with ESI Juli@ XTe (PCIe version of the soundcard).
The only uncommon thing I noticed is a bit different behavior of the
default mixer:
"pcm" mixer device is absent, so it is necessary to use "vol" instead. And
mplayer (default player I use) reports:
[Mixer] No hardware mixi
On 03/05/2019 17:10, David Boyd wrote:
The vm-image for 13.0-CURRENT
FreeBSD-13.0-CURRENT-amd64-20190503-r347033.vmdk
is only 4.0 GB in size. Previous images were about 31.0 GB.
This smaller image doesn't leave much room to add packages and other
customizations.
Yes, the V
[changed subject to follow drift of conversation]
On Sat, May 04, 2019 at 06:03:00AM -0700, Rodney W. Grimes wrote:
>
> Do we even have install note(s) pages for these things, or a wiki page
Not that I know of.
> that documents it, or ?Working around /firstboot does not require
> a serial
Warner Losh wrote:
> > At the risk of being branded a wishful thinker, a firstboot script that
> > asked the user for some configuration information would be a great help
> > to both new and experienced foot-shooters. I'm thinking of Raspberry Pi,
> > but perhaps it applies to non-embedded platfor
> On Fri, May 03, 2019 at 07:39:00PM -0700, Rodney W. Grimes wrote:
> > > On Fri, May 3, 2019, 7:42 PM bob prohaska wrote:
> > >
> > > > On Fri, May 03, 2019 at 11:06:15AM -0700, Rodney W. Grimes wrote:
> > > > > -- Start of PGP signed section.
> > > > > > On Fri, May 03, 2019 at 10:12:58AM -0700
On Fri, May 03, 2019 at 07:39:00PM -0700, Rodney W. Grimes wrote:
> > On Fri, May 3, 2019, 7:42 PM bob prohaska wrote:
> >
> > > On Fri, May 03, 2019 at 11:06:15AM -0700, Rodney W. Grimes wrote:
> > > > -- Start of PGP signed section.
> > > > > On Fri, May 03, 2019 at 10:12:58AM -0700, Enji Coope
> On Fri, May 3, 2019, 7:42 PM bob prohaska wrote:
>
> > On Fri, May 03, 2019 at 11:06:15AM -0700, Rodney W. Grimes wrote:
> > > -- Start of PGP signed section.
> > > > On Fri, May 03, 2019 at 10:12:58AM -0700, Enji Cooper wrote:
> > > > >
> > > > > > On May 3, 2019, at 9:57 AM, Alan Somers
> >
On Fri, May 3, 2019, 7:42 PM bob prohaska wrote:
> On Fri, May 03, 2019 at 11:06:15AM -0700, Rodney W. Grimes wrote:
> > -- Start of PGP signed section.
> > > On Fri, May 03, 2019 at 10:12:58AM -0700, Enji Cooper wrote:
> > > >
> > > > > On May 3, 2019, at 9:57 AM, Alan Somers
> wrote:
> > > > >
On Fri, May 3, 2019 at 7:40 PM bob prohaska wrote:
>
> On Fri, May 03, 2019 at 11:06:15AM -0700, Rodney W. Grimes wrote:
> > -- Start of PGP signed section.
> > > On Fri, May 03, 2019 at 10:12:58AM -0700, Enji Cooper wrote:
> > > >
> > > > > On May 3, 2019, at 9:57 AM, Alan Somers wrote:
> > > >
On Fri, May 03, 2019 at 11:06:15AM -0700, Rodney W. Grimes wrote:
> -- Start of PGP signed section.
> > On Fri, May 03, 2019 at 10:12:58AM -0700, Enji Cooper wrote:
> > >
> > > > On May 3, 2019, at 9:57 AM, Alan Somers wrote:
> > > >
> > > > See r346959. Before first boot, you should expand the
-- Start of PGP signed section.
> On Fri, May 03, 2019 at 10:12:58AM -0700, Enji Cooper wrote:
> >
> > > On May 3, 2019, at 9:57 AM, Alan Somers wrote:
> > >
> > > See r346959. Before first boot, you should expand the image up to
> > > whatever size you want. growfs(8) will automatically expan
> On May 3, 2019, at 9:57 AM, Alan Somers wrote:
>
> See r346959. Before first boot, you should expand the image up to
> whatever size you want. growfs(8) will automatically expand the file
> system.
> -Alan
>
> On Fri, May 3, 2019 at 10:32 AM David Boyd wrote:
>>
>> The vm-image for 13.0-
On Fri, May 03, 2019 at 10:12:58AM -0700, Enji Cooper wrote:
>
> > On May 3, 2019, at 9:57 AM, Alan Somers wrote:
> >
> > See r346959. Before first boot, you should expand the image up to
> > whatever size you want. growfs(8) will automatically expand the file
> > system.
> > -Alan
> >
> > On
See r346959. Before first boot, you should expand the image up to
whatever size you want. growfs(8) will automatically expand the file
system.
-Alan
On Fri, May 3, 2019 at 10:32 AM David Boyd wrote:
>
> The vm-image for 13.0-CURRENT
>
> FreeBSD-13.0-CURRENT-amd64-20190503-r347033.vmdk
[ toolchain-metadata.mk is missing when kernel-toolchain is used.
I've no clue if this is intentional or not. ]
On 2018-Jul-16, at 6:13 PM, Mark Millard wrote:
> On 2018-Jul-16, at 4:47 PM, Bryan Drewery wrote:
>
>> On 7/16/2018 3:49 PM, Mark Millard wrote:
>>>
>>>
>>> On 2018-Jul-16, at 3:3
On 2018-Jul-16, at 4:47 PM, Bryan Drewery wrote:
> On 7/16/2018 3:49 PM, Mark Millard wrote:
>>
>>
>> On 2018-Jul-16, at 3:31 PM, Bryan Drewery wrote:
>>
>>> On 7/16/18 1:21 PM, Mark Millard wrote:
I attempted a from-scratch (. . ./arm64.aarch64/ empty) kernel-toolchain
buildker
On 7/16/2018 3:49 PM, Mark Millard wrote:
>
>
> On 2018-Jul-16, at 3:31 PM, Bryan Drewery wrote:
>
>> On 7/16/18 1:21 PM, Mark Millard wrote:
>>> I attempted a from-scratch (. . ./arm64.aarch64/ empty) kernel-toolchain
>>> buildkernel
>>> targeting aarch64 from amd64 based on head -r336349 . I
On 2018-Jul-16, at 3:31 PM, Bryan Drewery wrote:
> On 7/16/18 1:21 PM, Mark Millard wrote:
>> I attempted a from-scratch (. . ./arm64.aarch64/ empty) kernel-toolchain
>> buildkernel
>> targeting aarch64 from amd64 based on head -r336349 . It failed by ending up
>> using an ld that can only ta
On 7/16/18 1:21 PM, Mark Millard wrote:
> I attempted a from-scratch (. . ./arm64.aarch64/ empty) kernel-toolchain
> buildkernel
> targeting aarch64 from amd64 based on head -r336349 . It failed by ending up
> using an ld that can only target elf_x86_64_fbsd elf_i386_fbsd :
I probably extended th
On Mon, Jul 9, 2018 at 4:58 AM, Tobias Kortkamp wrote:
> Hi,
>
> there's a new conflict between the FreeBSD-{libnv,runtime}-development
> base packages. This was for r336096 but the problem must have been
> introduced after r335966 as the packages from that revision were
> fine.
>
> Checking inte
On 02/13/2018 17:34, Claude Buisson wrote:
> On 02/13/2018 22:49, Pete Wright wrote:
>> Hello,
>> I have started seeing a lot of these messages spam my system log:
>>
>> ACPI Error: No pointer back to namespace node in package
>> 0xf8000f79a080 (20180209/dsargs-472)
>> ACPI Error: Method parse/
On 02/16/2018 13:54, Pete Wright wrote:
On 02/15/2018 13:37, Jung-uk Kim wrote:
On 02/13/2018 17:34, Claude Buisson wrote:
On 02/13/2018 22:49, Pete Wright wrote:
Hello,
I have started seeing a lot of these messages spam my system log:
ACPI Error: No pointer back to namespace node in pack
On 02/15/2018 13:37, Jung-uk Kim wrote:
On 02/13/2018 17:34, Claude Buisson wrote:
On 02/13/2018 22:49, Pete Wright wrote:
Hello,
I have started seeing a lot of these messages spam my system log:
ACPI Error: No pointer back to namespace node in package
0xf8000f79a080 (20180209/dsargs-472
On 02/13/2018 17:34, Claude Buisson wrote:
> On 02/13/2018 22:49, Pete Wright wrote:
>> Hello,
>> I have started seeing a lot of these messages spam my system log:
>>
>> ACPI Error: No pointer back to namespace node in package
>> 0xf8000f79a080 (20180209/dsargs-472)
>> ACPI Error: Method parse/
On 02/13/2018 22:49, Pete Wright wrote:
Hello,
I have started seeing a lot of these messages spam my system log:
ACPI Error: No pointer back to namespace node in package
0xf8000f79a080 (20180209/dsargs-472)
ACPI Error: Method parse/execution failed \134_SB.AC.ADJP,
AE_AML_INTERNAL (2018020
Hello Jeff,
Few days ago I upgraded my system firmware, upgraded
base to r327991 and altered snooping to
cluster-on-die. Its hard to say what is making
the server feels like a completely system due
to all these changes (also running llvm 6.0),
but I am betting it is the NUMA optimizations.
It is s
1 - 100 of 1051 matches
Mail list logo
