Re: NetBSD-9.1

[Pedro Pinho]

>It does hurt; it's an incorrect warning about something that isn't a bad
>thing to do, and it causes people to think they shoudl do something else
>an search for what to do.

That's exactly what I ment.
Personally, I know that's no issue and everything works but, a new user
might just go somewhere else when confronted by these.

>Actually I think our amd64 packages are built on 9_STABLE and labeled
>9.0 so the kernel has a threading fix necessary for
>rust to run properly; see lang/rust for pointers if interesteed.

Don't know what others do but, the packages I merge are for sure built on
9.0_STABLE. Or, rather were, now they are built on 9.1_STABLE.

>Someone will need to make a patch for pkg_add and friends.
Hmm... don't know if I dare but, if I find sometime I might look at it.

Thanks for the hints.


Den mån 26 okt. 2020 kl 18:59 skrev Greg Troxel :

>
> Pedro Pinho  writes:
>
> > Yes, I know but, they shouldn't be there.
>
> Someone will need to make a patch for pkg_add and friends.
>
> Basically there is more or less consensus that on NetBSD this should
> only match on major version.  Other OSes may have different rules.
>
> I don't think there is any objection or other barrier other than
> ENOPATCH.
>

Re: NetBSD-9.1

[Greg Troxel]

Ottavio Caruso  writes:

> 
>
> On Mon, 26 Oct 2020 at 14:55, Pedro Pinho  wrote:
>>
>> Yes, I know but, they shouldn't be there.
>
> Why not?
>
> It's extra information that doesn't hurt.

It does hurt; it's an incorrect warning about something that isn't a bad
thing to do, and it causes people to think they shoudl do something else
an search for what to do.

9.0 and 9.1 (and 9_STABLE) have the same ABI and packages built on one
work on the other.  Actually I think our amd64 packages are built on
9_STABLE and labeled 9.0 so the kernel has a threading fix necessary for
rust to run properly; see lang/rust for pointers if interesteed.


signature.asc
Description: PGP signature

Re: NetBSD-9.1

[Ottavio Caruso]

On Mon, 26 Oct 2020 at 14:55, Pedro Pinho  wrote:
>
> Yes, I know but, they shouldn't be there.

Why not?

It's extra information that doesn't hurt.

-- 
Ottavio Caruso

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Re: /etc/ifconfig.nnX vs /etc/rc.conf vs /etc/dhcpcd.conf

[Greg Troxel]

I don't think it belongs in ifconfig.   I would suggest looking in the
NetBSD gudie, and perhaps sending a patch/snippet to improve that.

I'd say that ifocnfig.XX and rc.conf are both traditional ways and it's
personal preference.  My only hard suggestion would be pick one, don't
mix.  Basically the rc.d script reads our of file or variables and calls
ifconfig - there isn't much more to it.



signature.asc
Description: PGP signature

Re: NetBSD-9.1

[Greg Troxel]

Pedro Pinho  writes:

> Yes, I know but, they shouldn't be there.

Someone will need to make a patch for pkg_add and friends.

Basically there is more or less consensus that on NetBSD this should
only match on major version.  Other OSes may have different rules.

I don't think there is any objection or other barrier other than
ENOPATCH.


signature.asc
Description: PGP signature

Re: Mapping kbd layout to connected) usb keyboard?

[Mike Pumford]

On 26/10/2020 13:00, Hauke Fath wrote:

Hi,

I helped my self to a fancy keyboard (Keyboardio Atreus). It comes with 
US layout, which I am trying to get used to, unlike my old DE IBM kbd.


Is there a way to automatically set the wscons keyboard layout depending 
on the keyboard attached? What about X11?


Not sure that's something any OS supports. I've not seen auto layout 
detection even in windows or linux as I'm not sure the keyboards can 
communicate that even over USB.


Normally there is an input selection widget in the UI to switch input 
keyboard layouts. Not sure if the X11 versions of those work in NetBSD.


Mike

/etc/ifconfig.nnX vs /etc/rc.conf vs /etc/dhcpcd.conf

[Ottavio Caruso]

Hi,

This is a follow-up from an interesting chat on Freenode#NetBSD.

I was going to post this on netbsd-docs@ but I have realised this is 
more a "political" than a documentation issue.


For the non-initiated user of NetBSD (= me), there are basically three 
options as where to store your permanent network interface settings:


1) /etc/ifconfig.nnX;
2) /etc/rc.conf; and if you use dchp:
3) /etc/dhcpcd.conf

There are of course other options, such as custom boot scripts.

Choice is good but it can also generate confusion.

What I am proposing is to add a snippet in ifconfig(8) man page, 
straight after the first paragraph in DESCRIPTION, advising that 
permanent settings for an interface be configured in _either_ 
/etc/ifconfig.nnX _or_ /etc/rc.conf (with additional and optional 
reference to /etc/dhcpcd.conf), and then advising which ones of the two 
methods is better and for which reason.


Thanks.

--
Ottavio Caruso

Re: NetBSD-9.1

[Pedro Pinho]

Yes, I know but, they shouldn't be there.

Den mån 26 okt. 2020 15:46Ottavio Caruso 
skrev:

> On 26/10/2020 14:34, Pedro Pinho wrote:
> > Hi all,
> >
> > First of all, thanks for 9.1, its great and it runs like a charm.
> >
> > Now,...
> >
> > Quoting the release notes
> >
> > "As usual, this release is fully compatible with packages and other
> binaries for
> > NetBSD 9.0."
> >
> > While, this is true and the packages run just fine,
> > '/var/db/pkgin/pkg_install-err.log' gets floaded with Warnings,
> >
> > ==
> > ...
> > ---Oct 26 12:51:27: installing sowm-1.6...
> > pkg_add: Warning: package `sowm-1.6' was built for a platform:
> > pkg_add: NetBSD/x86_64 9.0 (pkg) vs. NetBSD/x86_64 9.1_STABLE (this host)
> > pkg_add: Warning: package `st-term-0.8.4nb1' was built for a platform:
> > pkg_add: NetBSD/x86_64 9.0 (pkg) vs. NetBSD/x86_64 9.1_STABLE (this host)
> > ---Oct 26 12:51:27: installing st-term-0.8.4nb1...
> > pkg_add: Warning: package `st-term-0.8.4nb1' was built for a platform:
> > pkg_add: NetBSD/x86_64 9.0 (pkg) vs. NetBSD/x86_64 9.1_STABLE (this host)
> > pkg_add: Warning: package `ncurses-6.2nb2' was built for a platform:
> > pkg_add: NetBSD/x86_64 9.0 (pkg) vs. NetBSD/x86_64 9.1_STABLE (this host)
> > ...
> > ==
> >
> > It doesn't look very pleasing...
> > Can something be done to avoid such warnings in future releases?
>
> You can ignore those warnings.
>
> --
> Ottavio Caruso
>

Re: NetBSD-9.1

[Ottavio Caruso]

On 26/10/2020 14:34, Pedro Pinho wrote:

Hi all,

First of all, thanks for 9.1, its great and it runs like a charm.

Now,...

Quoting the release notes

"As usual, this release is fully compatible with packages and other binaries for
NetBSD 9.0."

While, this is true and the packages run just fine,
'/var/db/pkgin/pkg_install-err.log' gets floaded with Warnings,

==
...
---Oct 26 12:51:27: installing sowm-1.6...
pkg_add: Warning: package `sowm-1.6' was built for a platform:
pkg_add: NetBSD/x86_64 9.0 (pkg) vs. NetBSD/x86_64 9.1_STABLE (this host)
pkg_add: Warning: package `st-term-0.8.4nb1' was built for a platform:
pkg_add: NetBSD/x86_64 9.0 (pkg) vs. NetBSD/x86_64 9.1_STABLE (this host)
---Oct 26 12:51:27: installing st-term-0.8.4nb1...
pkg_add: Warning: package `st-term-0.8.4nb1' was built for a platform:
pkg_add: NetBSD/x86_64 9.0 (pkg) vs. NetBSD/x86_64 9.1_STABLE (this host)
pkg_add: Warning: package `ncurses-6.2nb2' was built for a platform:
pkg_add: NetBSD/x86_64 9.0 (pkg) vs. NetBSD/x86_64 9.1_STABLE (this host)
...
==

It doesn't look very pleasing...
Can something be done to avoid such warnings in future releases?


You can ignore those warnings.

--
Ottavio Caruso

NetBSD-9.1

[Pedro Pinho]

Hi all,

First of all, thanks for 9.1, its great and it runs like a charm.

Now,...

Quoting the release notes

"As usual, this release is fully compatible with packages and other binaries for
NetBSD 9.0."

While, this is true and the packages run just fine,
'/var/db/pkgin/pkg_install-err.log' gets floaded with Warnings,

==
...
---Oct 26 12:51:27: installing sowm-1.6...
pkg_add: Warning: package `sowm-1.6' was built for a platform:
pkg_add: NetBSD/x86_64 9.0 (pkg) vs. NetBSD/x86_64 9.1_STABLE (this host)
pkg_add: Warning: package `st-term-0.8.4nb1' was built for a platform:
pkg_add: NetBSD/x86_64 9.0 (pkg) vs. NetBSD/x86_64 9.1_STABLE (this host)
---Oct 26 12:51:27: installing st-term-0.8.4nb1...
pkg_add: Warning: package `st-term-0.8.4nb1' was built for a platform:
pkg_add: NetBSD/x86_64 9.0 (pkg) vs. NetBSD/x86_64 9.1_STABLE (this host)
pkg_add: Warning: package `ncurses-6.2nb2' was built for a platform:
pkg_add: NetBSD/x86_64 9.0 (pkg) vs. NetBSD/x86_64 9.1_STABLE (this host)
...
==

It doesn't look very pleasing...
Can something be done to avoid such warnings in future releases?

Best Regards

Mapping kbd layout to connected) usb keyboard?

[Hauke Fath]

Hi,

I helped my self to a fancy keyboard (Keyboardio Atreus). It comes with 
US layout, which I am trying to get used to, unlike my old DE IBM kbd.


Is there a way to automatically set the wscons keyboard layout depending 
on the keyboard attached? What about X11?


Cheerio,
Hauke

--
 The ASCII Ribbon CampaignHauke Fath
() No HTML/RTF in email Institut für Nachrichtentechnik
/\ No Word docs in email TU Darmstadt
 Respect for open standards  Ruf +49-6151-16-21344

Re: altq filter acts before or after npf NAPT?

[Rocky Hotas]

On ott 23 15:47, BERTRAND Joël wrote:
> and altqd runs as expected. Only a few bugs. Don't try to launch
> /etc/rc.d/altqd reload, altqd will take 100% of a CPU. Don't try to stop
> altqd, you will obtain a kernel panic.

Some updates: if altqd.conf has only a queing discipline per each
interface, I can (with 9.0 release) do `service altqd stop', `service
altqd start' with no issues.

If altqd.conf contains only a traffic conditioner for a single interface,
it is impossibile to stop altqd. `service altqd stop' does have no
effect: shell hangs in `sleep' mode; a Ctrl+C will restore the shell, but
altqd will still be running (however, `altqstat' does not show anything,
so maybe altqd is not fully functional).
Most important thing: a `shutdown' will not be able to stop `altqd'. It
blocks here:

System shutdown time has arrived

About to run shutdown hooks...
Stopping cron.
Stopping inetd.
Stopping altqd.

Another important introduction to altq, if anyone is interested, is:

 

``Managing Traffic with ALTQ'', from Kenjiro Cho, published in 1999

A couple of observations:
- ``An interface can have one queueing discipline attached at a time''
  (par. 3.1.2), so it's not possible to define multiple queueing
  disciplines for the same network interface.
- Maybe the issues regarding the kernel timer resolution, assumed to be
``10msec in most UNIX system'' (par. 3.2.1), are outdated.

Bye!

Rocky