Re: mandoc 1.14 on FreeBSD 11.1

[Baptiste Daroussin]

On Mon, Mar 20, 2017 at 03:59:35PM -0600, Warner Losh wrote:
> 
> > On Mar 20, 2017, at 3:53 PM, Baptiste Daroussin  wrote:
> > 
> > Hi all,
> > 
> > mandoc 1.14 has introduced a new database format (removing the requirement 
> > for
> > sqlite). FreeBSD 11.x is having right mandoc 1.13, Given the database 
> > format is
> > a technical detail (aka new format will be generated anyway automatically 
> > and
> > seamlessly replacing the old database). I think it does not fall into POLA. 
> > For
> > such reason I'm planing to upgrade to the 1.14 series (current already have 
> > it).
> > 
> > If that is a matter for you to change that database format please tell me.
> > Otherwise in 2 weeks I will import 1.14 in 11-STABLE in order we have it in
> > 11.1-R
> 
> I tend to agree with our analysis, but have a couple of questions that will 
> help us know what’s the right thing to do.
> 
> First, this is 100% independent of the kernel, so we don’t have any ‘forward 
> / back’ issues with that, correct?

Totally :), there might be an issue with the framework as it is not picking
makewhatis from the cross tools as it should I may need to fix that
> 
> Next, If I reinstall an older version of FreeBSD, it will create the database 
> that’s appropriate for 1.13, and vice versa, so it shouldn’t be visible to 
> the user.

Yes there is a periodic script for that and the database is anyway rebuild when
installing etc files
> 
> What happens if I upgrade and then add/delete packages, including upgrade, 
> add packages, downgraded?

Exactly as now, makewhatis (periodic script) will regenerate the databases at
the proper format
> 
> Is there a dependence on which pkg version you are using?

Nope
> 
> If the answers to these questions are approximately “yes”, “shouldn’t matter 
> / does the right thing”, “won’t be an issue because recreation sets the right 
> format and installworld will update the database with the right things as 
> part of that” and “doesn’t matter”  then I’d agree that this is an 
> uninteresting detail and need not be preserved.

Yup that is the answer to it :)
> 
> Warner




signature.asc
Description: PGP signature

Re: mandoc 1.14 on FreeBSD 11.1

[Warner Losh]

> On Mar 20, 2017, at 3:53 PM, Baptiste Daroussin  wrote:
> 
> Hi all,
> 
> mandoc 1.14 has introduced a new database format (removing the requirement for
> sqlite). FreeBSD 11.x is having right mandoc 1.13, Given the database format 
> is
> a technical detail (aka new format will be generated anyway automatically and
> seamlessly replacing the old database). I think it does not fall into POLA. 
> For
> such reason I'm planing to upgrade to the 1.14 series (current already have 
> it).
> 
> If that is a matter for you to change that database format please tell me.
> Otherwise in 2 weeks I will import 1.14 in 11-STABLE in order we have it in
> 11.1-R

I tend to agree with our analysis, but have a couple of questions that will 
help us know what’s the right thing to do.

First, this is 100% independent of the kernel, so we don’t have any ‘forward / 
back’ issues with that, correct?

Next, If I reinstall an older version of FreeBSD, it will create the database 
that’s appropriate for 1.13, and vice versa, so it shouldn’t be visible to the 
user.

What happens if I upgrade and then add/delete packages, including upgrade, add 
packages, downgraded?

Is there a dependence on which pkg version you are using?

If the answers to these questions are approximately “yes”, “shouldn’t matter / 
does the right thing”, “won’t be an issue because recreation sets the right 
format and installworld will update the database with the right things as part 
of that” and “doesn’t matter”  then I’d agree that this is an uninteresting 
detail and need not be preserved.

Warner


signature.asc
Description: Message signed with OpenPGP using GPGMail

mandoc 1.14 on FreeBSD 11.1

[Baptiste Daroussin]

Hi all,

mandoc 1.14 has introduced a new database format (removing the requirement for
sqlite). FreeBSD 11.x is having right mandoc 1.13, Given the database format is
a technical detail (aka new format will be generated anyway automatically and
seamlessly replacing the old database). I think it does not fall into POLA. For
such reason I'm planing to upgrade to the 1.14 series (current already have it).

If that is a matter for you to change that database format please tell me.
Otherwise in 2 weeks I will import 1.14 in 11-STABLE in order we have it in
11.1-R

Best regards,
Bapt


signature.asc
Description: PGP signature

[Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903

--- Comment #18 from Cassiano Peixoto  ---
(In reply to Cassiano Peixoto from comment #17)
Hi Mateusz,

I got another customer to try. Can i apply this patch and only replace the
kernel or do i need to replace userland as well?

After that do you need only kgdb trace output?

Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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"

Re: Unicode strageness with lldb

[Mark Millard]

Pete French petefrench at ingresso.co.uk  wrote on Mon Mar 20 14:55:44 UTC 2017:

> Using the lldb installed with 11-STABLE from an hour or so ago. Thoigh
> I dont know when this started, as I have been using db until now.
> 
> First command I type is fine, subsequent commands, every keypress I
> type looks like this:
> 
> (lldb) \U+7F68\U+7F65\U+7F08
> 
> That's an attempted 'bt' so something is adding 0x7F00 to it somewhere.
> 
> Anyone else seeing this ? Its in a standard xterm, options '-sb +lc -en utf8'
> but I have tried with other options and it does the same thing.

There was a time a while back when I was seeing such in a head (12)
context. I'm not sure about the specific values after the +'s but \U
prefixed output was definitely involved. I was not explicitly using
any of the options that you list in those ssh sessions (from a
macOS environment).

I discovered that if I typed ^C it would output a new prompt and
start taking/displaying input normally.

I've not had such an issue in a while.

I never managed to isolate what contributed to it happening.

===
Mark Millard
markmi at dsl-only.net

___
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"

Unicode strageness with lldb

[Pete French]

Using the lldb installed with 11-STABLE from an hour or so ago. Thoigh
I dont know when this started, as I have been using db until now.

First command I type is fine, subsequent commands, every keypress I
type looks like this:

(lldb) \U+7F68\U+7F65\U+7F08

That's an attempted 'bt' so something is adding 0x7F00 to it somewhere.

Anyone else seeing this ? Its in a standard xterm, options '-sb +lc -en utf8'
but I have tried with other options and it does the same thing.

-pete.
___
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"