't need to continue litigating this? At
some point, a continuous flow of disagreement like this after the fact
becomes demotivating in general as it feels more like a dogpile than a
constructive effort on the original topic.
Thanks,
Kyle Evans
__
On Wed, Feb 24, 2021 at 12:57 PM Dean E. Weimer wrote:
>
> On 2021-02-23 12:34 pm, Kyle Evans wrote:
> > The more I look at `make -dm` output, the less sense it makes. Your
> > patch is decidedly correct regardless of how this specific scenario is
> > playing out:
> &
t; 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:
>> >
>> > What does this pa
Hi,
What I don't understand here is, why are these being considered
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 Tue, Feb 2, 2021 at 10:42 AM Kristof Provost wrote:
>
> On 2 Feb 2021, at 14:05, Johan Hendriks wrote:
> > On 01/02/2021 22:48, Johan Hendriks wrote:
> >> I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now
> >> i can not start varnish anymore.
> >> This is on two machines.
>
On Sun, Jan 31, 2021 at 11:12 AM Per olof Ljungmark wrote:
>
> On 1/31/21 12:04 PM, mj-mailingl...@gmx.de wrote:
> > I noticed that my jails, build from a recent pkg base don't start:
> > ...
> > Starting jails: cannot start jail "j6":
> > 7
> > jail: j6: getpwnam root: No such file or directory
zation, if they're unexpanded
throughout then it falls back to diff(1) -- i.e. it's slower without.
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ollow to reproduce
any failure, preferably steps that can actually be followed by just
about anyone and don't require immense amounts of setup time or
additional hardware.
Unfortunately, your tone following the misunderstanding was pretty discouraging.
Thanks,
Kyle Evans
___
On Mon, Oct 5, 2020 at 9:48 AM Kyle Evans wrote:
>
> On Mon, Oct 5, 2020 at 5:13 AM mike tancsa wrote:
> >
> > On 10/4/2020 8:21 PM, Kyle Evans wrote:
> > > On Sun, Oct 4, 2020 at 7:02 PM mike tancsa wrote:
> > >> Not sure exactly when, but it seems build
On Mon, Oct 5, 2020 at 5:13 AM mike tancsa wrote:
>
> On 10/4/2020 8:21 PM, Kyle Evans wrote:
> > On Sun, Oct 4, 2020 at 7:02 PM mike tancsa wrote:
> >> Not sure exactly when, but it seems building RELENG_11 seems to be
> >> broken on releng12. I am trying to build
t with a "shell out for each utility and just ask
what the OBJDIR is" hammer, but I don't want to get smacked. =)
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
it at
boot so that xfce doesn't even try it. EFISYS = EFI System Partition
("ESP"). Unsure why it's identified in the "Removable Device"
category.
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ld describe the differences a little
better. CLICOLOR (On FreeBSD) historically meant that we'll enable
color if the terminal supports it, and setting it would have the same
effect as the above shell alias. COLORTERM is less aggressive and
won't imply any specific --color option, you would
On Fri, Jul 10, 2020 at 1:44 PM Guido van Rooij wrote:
>
> On Fri, Jul 10, 2020 at 08:29:03PM +0200, Guido van Rooij wrote:
> > On Thu, Jul 09, 2020 at 08:24:54AM -0500, Kyle Evans wrote:
> > > On Thu, Jul 9, 2020 at 8:12 AM Guido van Rooij wrote:
> > > >
&g
On Thu, Jul 9, 2020 at 4:20 PM John Kennedy wrote:
>
> On Thu, Jul 09, 2020 at 08:24:54AM -0500, Kyle Evans wrote:
> > On Thu, Jul 9, 2020 at 8:12 AM Guido van Rooij wrote:
> > >
> > > I did a zpool upgrade -a to enable large_dnode and spacemap_v2.
> > >
On Thu, Jul 9, 2020 at 8:50 AM Pete French wrote:
>
>
>
> On 09/07/2020 14:36, Kyle Evans wrote:
> > We haven't quite standardized on a good process yet, IMO, but for
> > right now the correct process is to just mount the ESP and replace
> > loader.efi with you
On Thu, Jul 9, 2020 at 8:32 AM Pete French wrote:
>
>
>
> On 09/07/2020 14:24, Kyle Evans wrote:
>
> >> gpart bootcode -p /boot/boot1.efifat -i 1 ada0
> >> gpart bootcode -p /boot/boot1.efifat -i 1 ada1
> >
> >
> > This method of upd
it likely wasn't and we couldn't locate the zpool.cache -- the
value of vfs.root.mountfrom should basically match the currdev format
here, except without a trailing colon.
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https
, but not
> with either 12.1-RELEASE or 13-CURRENT.
>
Hi,
This should be an easy fix. :-) EFI Runtime Services on FreeBSD
("EFIRT") wasn't necessarily globally stable until right around 12.0.
For 11.x, you'll need to `kldload efirt` or add `options EFIRT` to
your kernel
tween FreeBSD 10/11 and 12 in loader-world as our loader
universe got thoroughly rototilled and improved -- many of these
things cannot be attributed to lua, but perhaps are because of the
coincidental timing.
Thanks,
Kyle Evans
___
fre
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 a bit
> > worried; status=7 looks lik
mments were highly demoralizing, and I almost didn't
bother dropping into this thread because of them.
Believe it or not, issues with underlying media can cause problems
with 4thloader as well.
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mai
odd
setup that I can never remember. For legacy setups, the bootpool
can/should be merged into your root pool if it's feasible.
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Wed, Feb 26, 2020 at 2:18 AM Pavel Timofeev wrote:
>
> Hi,
> Looking at 12-STABLE I found that r354060 missed one more change (i.
> e. https://svnweb.freebsd.org/base?view=revision&revision=347515 from
> HEAD):
>
Whoops, good catch- fixed in r35833
On Thu, Nov 21, 2019 at 4:48 AM Eugene Grosbein wrote:
>
> 21.11.2019 17:22, Bjoern A. Zeeb wrote:
>
> > On 21 Nov 2019, at 9:51, Eugene Grosbein wrote:
> >
> >> Hi!
> >>
> >> How do I get boot messages generated by loader itself written to some log
> >> after successfull boot?
> >> This is gener
hange came from,
> what it was meant to accomplish, then hopefully we can find out what went
> wrong for at least my hardware?
>
Hi,
That helps- thanks! I'm CC'ing tsoome@, as this is basically just
r353501 in that range. Can you give the latest -CURRENT snapshot boot
as anoth
t
hand, and I suspect it is not related to your problem either (unless
your problem is simply that you hate lua). Do you have a PR open for
any real problem?
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/li
On Fri, Aug 2, 2019 at 12:50 AM Ari Suutari via freebsd-stable
wrote:
> On 1.8.2019 21.19, Kyle Evans wrote:
> > On Thu, Aug 1, 2019 at 8:43 AM Kyle Evans wrote:
> >> On Thu, Aug 1, 2019 at 1:38 AM Ari Suutari via freebsd-stable
> >> wrote:
> >>> Hi,
>
On Thu, Aug 1, 2019 at 8:43 AM Kyle Evans wrote:
>
> On Thu, Aug 1, 2019 at 1:38 AM Ari Suutari via freebsd-stable
> wrote:
> >
> > Hi,
> >
> > We have a lot of servers using jails and ipfw rules with
> > numeric jail ids to limit acess between them (someth
d operates on any jail that ends
up having that jid.
name can only be functional if the jail's already running when the
rule is processed by ipfw(8) and applies to whatever jid has that name
at that time. If the jail gets restarted with a different
On Thu, Jul 25, 2019 at 9:46 AM Kyle Evans wrote:
>
> On Thu, Jul 25, 2019 at 9:41 AM Trond Endrestøl
> wrote:
> >
> > Hi,
> >
> > I have a VPN service running net/ocserv 0.12.4_1. Everything is ok
> > until the first client disconnects. The main ocserv pro
cation in a funky state. There were some bugs around
that leaving the driver in a funky state that I fixed somewhere along
the way here.
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Sun, Jun 2, 2019 at 8:05 AM Konstantin Belousov wrote:
>
> On Sun, Jun 02, 2019 at 02:30:49PM +0200, Stefan Hegnauer wrote:
> > Hi,
> >
> > after a recent full update to 12.0-STABLE r348382 it seems that '/bin/ps
> > -J 0' is broken: 'ps: Invalid jail id: 0'.
> > It did work on stable for the l
deed be useful and support for it has not been merged;
I've taken the PR.
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Mon, Mar 4, 2019 at 11:50 AM tech-lists wrote:
>
> Hi,
>
> If I give binmiscctl the magic for arm6 and then for say mips64, will
> this break things?
>
> Let's say I'm using an amd64 box to cross-compile using poudriere
> for arm6 and mips64 ports. Can I do both on the same box at the same time
On Fri, Jan 25, 2019 at 6:30 PM Jonathan Chen wrote:
>
> On Sat, 26 Jan 2019 at 13:00, Karl Denninger wrote:
> [...]
> > I'd like to repartition it to be able to dual boot it much as I do with
> > my X220 (I wish I could ditch Windows entirely, but that is just not
> > going to happen), but I'm n
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 of which files are involved in
> > booting:
> > https://www.freebsd.org/cgi/man.cgi?query=uefi&sektion=8&manpath=freebsd-release-ports
spect to
scripts. For that I'd go ahead and double-check that /boot/loader.efi
was actually updated *and* update the contents of the ESP -- that
particular change was paired with another one that stopped doing any
resizing in boot1.
Thanks,
Kyle Evans
___
On Tue, Jan 8, 2019 at 7:44 PM Kyle Evans wrote:
>
> On Tue, Jan 8, 2019 at 7:36 PM Rebecca Cran via freebsd-stable
> wrote:
> >
> > grep(1) documents the "--exclude-dir" option, but running "grep" complains
> > it's unknown. Also, 'rgrep
kefile?view=markup#l13
should read "MAN1= bsdgrep.1 zgrep.1" rather than grep.1 zgrep.1, I
believe. (CC bapt@ for a second eye, since this was during zgrep
stuff)
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https://lists.fre
On Thu, Aug 9, 2018 at 12:48 PM, Kyle Evans wrote:
> On Thu, Aug 9, 2018 at 12:32 PM, Don Lewis wrote:
>> My poudriere machine is running fairly recent 12.0-CURRENT, r336859.
>>
>> I just tried upgrading my 11.2-STABLE poudriere jail from r336040 to
>> r337508 and got
rted a universe build of r336040 and it looks likely to work,
> so the problem appears to be with the stable/11 branch sometime after
> r336040.
>
Hi,
This is almost-certainly my fault... taking a look now.
Thanks,
Kyle Evans
___
freebsd-stable@
/tmp/usr/bin:/sbin:/bin:/usr/
>> > sbin:/usr/bin
>> > make -m /data/freebsd.work/share/mk KERNEL=kernel cleandir
>> > make[2]: "/data/freebsd.work/sys/conf/kern.pre.mk" line 125: amd64
>> > kernel
>> > requires linker ifunc support
On Tue, Apr 17, 2018 at 10:18 AM, Dan Allen wrote:
>
>
>> On 17 Apr 2018, at 8:49 AM, Kyle Evans wrote:
>>
>> As "the guy most likely to have broken boot code in stable," may I ask
>> what leads you specifically to amd64 boot code? Mostly curious if
>
On Tue, Apr 17, 2018 at 9:44 AM, Dan Allen wrote:
> I run FreeBSD 11-STABLE on actual machines, and I build the system every few
> days. Things have been fine.
>
> However, I also run FreeBSD 11 via the qemu emulator on my Mac. I run lots
> of different BSD & Linux OSes here to test them out.
ss the breakage and figure out next steps before it
becomes a bigger problem with the impending release.
I've heard good things about the aforementioned
devel/p5-App-SVN-Bisect for these purposes.
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org ma
s also broken. I had to revert to r330113 to avoid any of the
> recent iwm commits.
Hi,
CC'ing Eitan, so hopefully he can fix this mess as soon as he wakes up...
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Sun, Feb 18, 2018 at 3:12 AM, Peter Jeremy wrote:
> Sometime between r329122 and r329157, my 11-stable i386 box stopped
> being able to buildworld with a readonly /usr/src. I've been updating
> regularly but the problem still remains at r329450. I don't have any
> problems building the same tr
Hi,
-HEAD defaults to WITHOUT_GNU_GREP_COMPAT at the moment, so this got missed
and I apparently had this addressed in my local build testing due to other
bits.
@emaste: can I commit the fix for this to -HEAD for MFC immediately?
(unsigned int) cast on pmatch.rm_so.
Thanks,
Kyle Evans
On Aug
x systems that are Debian or Debian-derived
actually have a shim like this I'm not sure it's a good idea to
produce a bzgrep that isn't similarly compatible with the system
grep(1).
- Kyle Evans
___
freebsd-stable@freebsd.org mailing list
h
*grep links are a mix
between BSD grep and GNU grep.
> Hope this makes sense, I should have been asleep hours ago!
>
> Cheers, Jamie
Makes good sense, =)
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mail
bsdgrep, but I've not been finding time to poke emaste@ to see if I
can help with getting some of my work integrated.
> Cheers, Jamie
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ee Comment #5 if you're interested in a more detailed
explanation.
Thanks,
Kyle Evans
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
_
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Hello!
I concur, but for the selfish reason that the graphics
54 matches
Mail list logo
