Hi Ed,
I think that sounds great. In the future, could we go even further and,
by default, only emit date/user/path if the source tree is “dirty”
with respect to SVN? If the build really is reproducible, that data
should only be informative when building something that doesn’t match
a FreeBSD
Hi all,
I’m attempting to `make buildworld` from a 10.1-RELEASE box, and I’m
encountering an error in the “bootstrap tools" stage. It looks like gzip, which
is part of the bootstrap tools, depends on `futimens` from a newish (since
February?) libc / syscall API:
$ make buildworld
[...]
usr.bin
>
> On Jun 3, 2015, at 12:35 PM, Steve Kargl
> wrote:
>
> On Wed, Jun 03, 2015 at 12:29:12PM -0230, Jonathan Anderson wrote:
>>
>> So, how do I bootstrap 11-CURRENT from 10.1-RELEASE?
>>
>
> Update your source tree.
My source tree is up-to-dat
>
> On Jun 3, 2015, at 12:44 PM, Baptiste Daroussin wrote:
>
> On Wed, Jun 03, 2015 at 12:42:13PM -0230, Jonathan Anderson wrote:
>>>
>>> On Jun 3, 2015, at 12:35 PM, Steve Kargl
>>> wrote:
>>>
>>> On Wed, Jun 03, 2015 at 12:29:12P
Hi all,
I’m trying to upgrade an old Sony VAIO laptop from 10.1 to -CURRENT. Everything
seemed to work well with 10.1, but on -CURRENT I get no further in the boot
than:
```
ACPI: No DMAR table found
Event timer “LAPIC” quality 600
ACPI APIC Table:
```
If I disable ACPI, I get:
```
APIC: Cou
>
> On Jun 17, 2015, at 12:00 PM, Konstantin Belousov wrote:
>
> Show bootverbose dmesg.
Is that different from the “Verbose” option in the loader menu? When I do a
loader-menu-driven verbose boot, I see:
https://drive.google.com/file/d/0B2eLORKzuvdOZ1I4SVB0aFNSenM
Jon
--
jonat...@freebsd.o
> On Jun 17, 2015, at 2:24 PM, Konstantin Belousov wrote:
>
> On Wed, Jun 17, 2015 at 02:19:14PM -0230, Jonathan Anderson wrote:
>>>
>>> On Jun 17, 2015, at 12:00 PM, Konstantin Belousov
>>> wrote:
>>>
>>> Show bootverbose dmesg.
>>
> On Jun 17, 2015, at 2:39 PM, Konstantin Belousov wrote:
>
> On Wed, Jun 17, 2015 at 02:32:16PM -0230, Jonathan Anderson wrote:
>> The system boots the 11-CURRENT kernel in "safe mode" (not sure if it???s
>> the kern.mp.disabled or kern.eventtimer.periodic th
hat provide any useful information for my FreeBSD problem?
Jon
--
Jonathan Anderson
jonat...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "free
On 26 Feb 2016, at 13:23, Jonathan Anderson wrote:
Hello -CURRENT,
I just picked up an Asus ZenBook UX305CA on sale. The screen is
beautiful (with unaccelerated scfb graphics), the wi-fi works (with
just the occasional fatal firmware error) and I'm generally a
satisfied customer, e
/2015-February/081757.html
It seems that this is becoming an issue on new notebooks: I know that my
new ASUS notebook has the same problem (but, unfortunately, Mauro's fix
doesn't apply to my machine).
Jon
--
Jonathan Anderson
jonat...@freebsd.org
on the distinction between a lightly-patched compiler that lives
in our source tree and a lightly-patched compiler that lives in the
ports tree. So, now that the base compiler and a ports compiler will be
installed using the same tools, it might be worth thinking about how
they're really d
0815, but no answers
there yet. I think the problem might be that the bootpool hasn't
actually been mounted yet, so the /mnt/boot symlink points to a
non-existent directory (/mnt/bootpool/boot).
Jon
--
Jonathan Anderson
jonat...@freebsd.org
___
f
ld be required?
At least according to one of my students (who makes more extensive use
of i18n than I do), enabling UTF-8 by default is pretty straightforward:
https://github.com/musec/freebsd/wiki/Common-setup#utf-8-support
If there's anything missing there, I'd love to hear about it.
Hi all,
I'm seeing some unexpected PQ_LAUNDRY behaviour on something fairly close
to -CURRENT (drm-next-4.7 with an IFC on 26 Dec). Aside from the use of
not-quite-CURRENT, it's also very possible that I don't understand how the
laundry queue is supposed to work. Nonetheless, I thought I'd check w
On 2 Jan 2017, at 13:33, Mark Johnston wrote:
On Mon, Jan 02, 2017 at 10:31:50AM -0330, Jonathan Anderson wrote:
Hi all,
I'm seeing some unexpected PQ_LAUNDRY behaviour on something fairly
close
to -CURRENT (drm-next-4.7 with an IFC on 26 Dec). Aside from the use
of
not-quite-CURRENT,
On 5 Jan 2017, at 0:17, Matthew Macy wrote:
On Mon, 02 Jan 2017 06:01:50 -0800 Jonathan Anderson
wrote
Hi all,
I'm seeing some unexpected PQ_LAUNDRY behaviour on something fairly
close
to -CURRENT (drm-next-4.7 with an IFC on 26 Dec). Aside from the use
of
not-quite-CU
to an iPhone hotspot is one example of a not-entirely-helpful
network, but there is other, more typical infrastructure that gives
trouble too. There is an iwm8xxx in the room that seems to work fine,
however... I do not meddle in the affairs of wi-fi, for it is subtle and
quick to anger. :)
Jo
On 6 Jan 2017, at 12:48, Pete Wright wrote:
On 1/6/17 9:14 AM, Matthew Macy wrote:
I just did the merge and it's using a relatively untested new KPI so
regressions aren't too surprising I'm afraid. #96 is more or less
content free in terms of providing useful information. Getting a core
+ b
On 6 Jan 2017, at 14:06, Matthew Macy wrote:
kernel cores tend to be large (all of wired memory after all) and
unless I have exactly the same kernel as you with the same sources at
the same changeset, not useful. A backtrace is a good place to start.
kgdb /boot/kernel/kernel /var/crash/vmcore.
On 6 Jan 2017, at 14:26, Matthew Macy wrote:
Thanks. Pete already filed that as part of #108. With luck markj@ will
have that fixed this weekend.
-M
Fantastic, I'll subscribe to that issue.
Cheers,
Jon
--
jonathan.ander...@ieee.org
___
freebsd-c
Hi,
On 5 Mar 2017, at 20:31, Chris H wrote:
OK copying the boot.efi from the install DVD will only
hose the system (EFI).
Before I attempt to do the same thing... what do you mean by "hose the
system"? Is the correct recovery path to build a new USB image with
"make release" post-r314828?
On 7 Mar 2017, at 16:50, Chris H wrote:
On Tue, 07 Mar 2017 16:27:59 -0330 "Jonathan Anderson"
wrote
Hi,
On 5 Mar 2017, at 20:31, Chris H wrote:
OK copying the boot.efi from the install DVD will only
hose the system (EFI).
Before I attempt to do the same thing... what do y
has -CURRENT last merged somewhere around
r317651), this patch fixes one of the two problems I've been
experiencing with suspend/resume. Definite progress. :)
Thanks!
Jon
--
Jonathan Anderson
jonat...@freebsd.org
___
freebsd-current@freebs
On 15 May 2017, at 14:57, Konstantin Belousov wrote:
On Mon, May 15, 2017 at 02:37:16PM -0230, Jonathan Anderson wrote:
Running drm-next (which has -CURRENT last merged somewhere around
r317651), this patch fixes one of the two problems I've been
experiencing with suspend/resume. Def
Hi Vladimir,
On 04/16/17 15:18, Vladimir Kondratyev wrote:
Following patch [1] bring in multitouch EVDEV support for Synaptics
and Elan PS/2
touchpads found in many laptops. (And for generic relative PS/2 mices
as well).
This allows to replace our limited in-kernel gesture processor with
full-
(.txt, I guess)
No matter what number you choose for a path length, you're never going
to win against that specific user. :)
Jon
--
Jonathan Anderson
jonat...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mail
s.
Unfortunately, this is the VM that I normally use to run kgdb against
other VMs, so my normal debugging setup does not apply. I'll see if
this hotel will let me download an ISO so that I can install a fresh
VM for debugging...
Jon
--
Jonathan Anderson
jonat...@freeb
On 5 October 2011 23:50, Jonathan Anderson wrote:
> I was about to upgrade my build VM from BETA2 to BETA3, but I can't
> seem to boot BETA2 any more: I get a "ffs_valloc: dup alloc" panic on
> boot, every time. fsck runs and says, "ok, I've cleaned things up f
That's ok, a more aggressive fsck-from-a-rescue-disk strategy managed
to clean things up.
J Anderson
On 6 October 2011 15:58, Benjamin Kaduk wrote:
> On Thu, 6 Oct 2011, Jonathan Anderson wrote:
>
>> On 5 October 2011 23:50, Jonathan Anderson wrote:
>>>
>>>
ftware, so they'll want to "pkg
install foo" and have it Just Work. To say either "you must download the ports
tree in order to use binary packages" or "you must use pkg_add to install pkg"
seems to miss the point...
Jon
--
Jonathan Anderson
jonat...
On Saturday, 25 August 2012 at 01:33, Glen Barber wrote:
> On Sat, Aug 25, 2012 at 01:25:15AM +0100, Jonathan Anderson wrote:
> > On 24 Aug 2012, at 23:38, Doug Barton > (mailto:do...@freebsd.org)> wrote:
> > > Let me rephrase that more simply ... very few users are ever
ly stolen from the linked page, since I no longer have any
Debian boxes to check for myself on :). No magic binaries or argv[0] fu.
In one way, it's an elegant solution. On the other, it's a classic example of
Wheeler's Law in action. :)
Jon
--
Jonathan Anderson
Research Stude
ose packages, could The Base System itself be
smaller, e.g. just what we need to bootstrap FreeBSD itself?
Jon
--
Jonathan Anderson
jonat...@freebsd.org
http://freebsd.org/~jonathan/
___
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"
ose packages, could The Base System itself be
smaller, e.g. just what we need to bootstrap FreeBSD itself?
Jon
--
Jonathan Anderson
jonat...@freebsd.org
___
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"
Croy
>
> If we can integrate more automated testing of FreeBSD with this,
> that would be really great!
> --
> Craig
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsu
t; expand the comment to
>
>
> # Enable FreeBSD7 compatibility syscalls
> # This option is MANDATORY. Do not remove.
> options COMPAT_FREEBSD7
So... a non-optional option?
Jon
--
Jonathan Anderson
jonat...@freebsd.org
___
freebs
x27;t see how that's very different from requiring a gcc/g++ package.
Jon
--
Jonathan Anderson
jonat...@freebsd.org
___
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"
xt step".
I presume that the point of a "guided" setup is to make it easy on
first-time FreeBSD installers; we might want to make it a little
easier still by labelling the relevant button "OK", "Save", "Next",
"Do It!" or something in
Hi all,
Running this on a 12.1-STABLE system, I see a whole lot of this in
/var/log/messages:
fahclient[53019]: ^[[91m12:15:25:ERROR:WU00:FS00:Exception: Could not get
an assignment^[[0m
Is this because there temporarily isn't enough work to go around, or
because more FreeBSD support is required
40 matches
Mail list logo
