> Also if repository is pointing to 10.0 and packages available on repo.
>
> Remove Cairo and install windowmaker
Hmm, I think it's cairo-gobject which needs removing, if I recall
correctly that functinality and files were integrated into the
new version of the cairo package:
>> I get a strange
> I think I may have struck a nerve.
I'm not sure I understand what that's getting at. It's not a
particularly "sensitive topic" to me or us in general, I would
think. The fact that english is a second language for me may
prevent me from interpreting this comment appropriately.
> The consensus
>> I *believe* I could fix this by upgrading NetBSD to
>> 9.0+. Unfortunately, that would be hard for me, at least now.
>
> Whether there are binary package sets for various versions is a
> question you might want to answer, but in general, you are now
> overdue for an upgrade.
Yep.
> This query
> I have a PPC Mac Mini running NetBSD 8.2. It's stable and
> functional. It serves me well.
Yes, but it's now running an OS which is becoming old and which
is about to be "de-supported" wrt. pkgsrc updates (to the extent
we "support" it). The basic problem is that the supplied
compiler is
>> In order to test NetBSD-10.0, I copied the latest kernel to the root
>> directory of a [partially] working NetBSD-9.3 system. Absolutely
>> fantastic: super fast boot-up, AND the '/sbin/shutdown -p' glitch with
>> the 9.x series is fixed! THANK YOU developers for your hard work.
>>
>> Now, is
> I just updated:
>
> NetBSD 10.0_RC
Platform? amd64?
> I am doing:
>
> mount -t msdos /dev/sd0 /mnt
>
> Its a SanDISK that I have been using for a while.
> Did something change? Idea???
You didn't describe what error you get (I presume you get an
error?) So this is a bit of a guessing
> Entirely separately from compat, you should be running recent openssl
> anyway, as a matter of security best practices.
That's easy to agree with in principle. When it gets down to the
practical matters, it's quite another thing.
Case in point at my end: I have a 9.1_STABLE host which for
> Now, of course, wouldn't be nice if 'umount' said something like "hey
> dude! you're in the directory you're trying to umount."
That's what e.g. "fstat /a" can tell you.
Regards,
- Håvard
> Hi, 'dd' seems to behave different if the 'if' is /dev/random
> than if it is anything else, e.g. /dev/zero:
>
> # sh
> # dd if=/dev/zero of=zero.out bs=65536 count=1
> 1+0 records in
> 1+0 records out
> 65536 bytes transferred in 0.001 secs (65536000 bytes/sec)
rnd(4) says:
Applications
>> > When will NetBSD-10.* come out. I was told Jan 2023.
>>
>> That would be slightly optimistic, first 10.0 BETA builds are
>> just arriving.
>>
>> > Any specific date set?
>>
>> Not yet.
>
> Thanks. I will keep watching for ver 10.0 ...
As stated already, the branch which will eventually lead
> On Mon, Jul 25, 2022 at 02:19:27PM +, Salil Wadnerkar wrote:
>> Does anyone know which `ieee80211` commands I need to get the wireless
>> connection info like SSID name, type (WPA, etc), and signal strength?
>> `ieee80211_ioctl` (https://man.netbsd.org/NetBSD-9.0/ieee80211_ioctl.9)
>> looks
>>> PKG_OPTIONS.rust+= rust-llvm
>>> RUST_TYPE=src
>>
>> 1.56.1 has just hit pkgsrc proper.
>
> Regarding the kinds of options noted above, where would a curious
> person go to read documentation for them? I have lines like the above
> in my /etc/mk.conf but I've forgotten for what purpose they
> [...] I recall seeing a lot of very cheap fibre channel
> drives when I looked, they could be problematic because you
> need a FC hba and fibre to make them go and I don't think
> NetBSD has any FC drivers.
Some of the cards supported by the mpt(4) driver have FC
interfaces, listed in the man
Hi,
I see most of the confusion is resolved. Following up on a
tangent:
>> The other option is to upgrade to current current.
>
> I don't see a path to installing current on a broken system.
That depends on how broken the system is :)
> The download options for current all seem to be in terms
> Like you say, this isn't a NetBSD problem. The approach in
> https://lists.freebsd.org/pipermail/freebsd-stable/2016-June/084771.html
> looks reasonable at first glance as an option to not hard-code IP
> addresses anywhere:
>
> running this at boot time may help as well
>
>
> The question is whether we ought to do something to break this
> circular dependency in our default install by specifying one or two
> (depending on "minsane" and resiliency conciderations) ntp servers
> via IP address? The issue then becomes "which IP address(es)" and
> "how can that scale"?
> That dns starts failing if you don't have a correct clock seems to
> be a serious brokenness.
Well, I would not use such words, but I would rather say that the
introduction of DNSSEC validation requires a semi-accurate clock.
That's part and parcel of the specification.
> Plenty of embedded
> Hi, I'm having the following issues on RPi-3 which doesn't have battery
> operated clock. This tends to happen when clock skew is quite large.
>
> 1. DNS resolution no longer works, as unbound(8) needs system time to
> be correct. I think this is due to "forward-tls-upstream: yes" option.
I
>> Plus, of course, the outgoing queries from your recursor will
>> be in cleartext.
>
> OK, so I understand that root servers probably won't support
> TLS, but some authoritative servers may support TLS (aka
> ADoT). But I don't seem to find a way to tell unbound "use TLS
> opportunistically,
>> What I'm not sure about is this - unbound(8) has "root-hints" that
>> points to root DNS servers and it will handle recursive queries, but it
>> can also specify "forward-zone" where it can forward to Cloudflare or
>> Google recursive DNS servers. Both of these solution would resolve DNS
>>
> I must admit I'm scratching my head about this one.
No more! And I stil have hair!
Looking at the diff between ISC's lib/isc/sha2.c and ours reveals
that our source has code to overcome alignment issues, but in the
conversion one statement has been omitted. Here's the relevant
diff between
> The problem I reproduced in March (but didn't solve) was on amd64 where
> the DS didn't match. It used SHA384.
>
> Two different examples:
> https://mail-index.netbsd.org/netbsd-users/2020/03/24/msg024303.html
Hm, that's ... mine :)
The protonmail.ch DS issue really seems to be a general
>>> Does anybody think that the bind bits in netbsd-8 are ok, even before we
>>> talk about compilation?
>>
>> I'm about halfway through the diff between what's in-tree in
>> netbsd-8 and what's in ISC BIND 9.10.5-P1, and all I find so far
>> are
>
> I asked because I had trouble maybe two months
> Does anybody think that the bind bits in netbsd-8 are ok, even before we
> talk about compilation?
I'm about halfway through the diff between what's in-tree in
netbsd-8 and what's in ISC BIND 9.10.5-P1, and all I find so far
are
- tweak of RCSID tags
- /*CONSTCOND*/ annotation additions
-
>> So now I'm a bit confused where this error comes from. Its root
>> cause does not seem to be the in-tree compiler (the "standalone"
>> BIND releases I've built are built with "-g -O2"), and it's not
>> the original BIND code either by the looks of it, as this is the
>> same code which is in
> BIND in netbsd-8 is version 9.10.5-P1.
>
> BIND compiled from ISC, version 9.10.5-P3 also does this correctly:
>
> castor: {11} dig . dnskey | bin/dnssec/dnssec-dsfromkey -f - .
> . IN DS 20326 8 1 AE1EA5B974D4C858B740BD03E3CED7EBFCBD1724
> . IN DS 20326 8 2
>
>> I now have BIND 9.14.8 built from pkgsrc, built with the in-tree
>> "cc" on a the same 8.1/sparc64 host mentioned above, and it does
>> it correctly:
>>
>> castor# dig . dnskey | /usr/pkg/sbin/dnssec-dsfromkey -f - .
>> . IN DS 20326 8 1 AE1EA5B974D4C858B740BD03E3CED7EBFCBD1724
>> . IN DS 20326
> I now have BIND 9.14.8 built from pkgsrc, built with the in-tree
> "cc" on a the same 8.1/sparc64 host mentioned above, and it does
> it correctly:
>
> castor# dig . dnskey | /usr/pkg/sbin/dnssec-dsfromkey -f - .
> . IN DS 20326 8 1 AE1EA5B974D4C858B740BD03E3CED7EBFCBD1724
> . IN DS 20326 8 2
>
>> Just in case there was something botched in my local builds, I updated
>> the sparc system from the latest nightly builds of netbsd-7 and netbsd-8.
>>
>> The behavior is the same. Both netbsd-[78]/sparc produce a bad DNSSEC DS
>> hash (the first line):
>>
>> . IN DS 20326 8 1
> Just in case there was something botched in my local builds, I updated
> the sparc system from the latest nightly builds of netbsd-7 and netbsd-8.
>
> The behavior is the same. Both netbsd-[78]/sparc produce a bad DNSSEC DS
> hash (the first line):
>
> . IN DS 20326 8 1
> When I tried turning on DNSSEC on the primary name server, it could no-
> longer resolve outside my own local network. I think BIND in netbsd-7
> is considered too old to properly support current DNSSEC, so I commented
> those options out and it was again able to resolve external domains.
I
> My caching dns failed unexpectedly today, apparently I was not alone:
> https://www.mail-archive.com/bind-users@lists.isc.org/msg28624.html
> From ISC: "We apparently let our signatures on dlv.isc.org expire."
Ouch!
> I fixed this temporarily by adding:
> dnssec-accept-expired yes;
> Which
>> This has just got a lot worse. As of about 20 minutes ago I've had to
>> completely disable dnssec validation on my NetBSD 8.1-stable servers
>> as I had a complete loss of name resolution. Every domain was failing
>> to resolve (e.g www.google.com). This was with dnssec-validation set
>> to
> This has just got a lot worse. As of about 20 minutes ago I've had to
> completely disable dnssec validation on my NetBSD 8.1-stable servers
> as I had a complete loss of name resolution. Every domain was failing
> to resolve (e.g www.google.com). This was with dnssec-validation set
> to auto.
> You can also use delv to see named like behaviour:
> delv protonmail.ch
> delv -d 99 protonmail.ch
I think this line for the last one is the problem:
;; validating protonmail.ch/DNSKEY: no DNSKEY matching DS
and, indeed, re-computing the DS record from the protonmail.ch
DNSKEY:
% dig
> I did a fresh install for 9.0 BETA. Built pkgin from source,
> /usr/pkg/etc/pkgin/repositories.conf points me to
> http://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/amd64/8.0_2019Q2/All. So
> far almost everything I need installs. I did have to softlink a
> few expected libraries in /usr/lib to a
> This is the output I got from dmesg:
>
> vendor 10ec product 8185 (ethernet network, revision 0x20) at pci4 dev 9
> function 0 not configured
>
> I hope that contains the pci id, if not I may need some guidance.
>
> this is what I got from pcictl pci0 list:
>
> 008:09:0: Realtek Semiconductor
>>> Does this mean this card is not supported or does it mean it
>>> just needs to be configured? This card uses the RTL8185L chip
>>> but not sure what the brand/manufacturer is. Looking over the
>>> manual pages it looks like the closest driver for this card
>>> would be rtw.
>>
>> It means that
> How can I set up this mouse here, on the NetBSD system?
Your kernel has presumably / hopefully probed your ps/2 connected
mouse already. You can probably find an instance of "pms" in
/var/run/dmesg.boot.
On NetBSD, we have an "overlay" which covers both PS/2 and USB mice
(among others),
> [...] I'm doing a raid1 reconstruct which should
> be a straight read from disk A, write to disk B. The data from systat
> backs that up. Each disk is doing ~110 transfers per second. wd1 the
> source disk is reading at 7MB/s and wd2 the destination is writing at
> 7MB/s.
It could be that the
> NetBSD 7.2 was released a few weeks ago. Are there any plans to bulk
> build pkgsrc for this version? I tried to use
> ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/7.1_2018Q2/All/ ,
> this generally works, but there are a number of newer shared libraries
> in 7.2 which block the
> Now, installing a bootable netbsd onto such a disk is something else,
> but as a data disk it's even easier than before.
I admit to not knowing how / whether that can be done, and from which
version etc. Your existing wiki page about "using-large-disks" is
useful; could you perhaps be inspired
> On Mon 27 Jun 2016 at 23:17:45 +0200, Havard Eidnes wrote:
>> > I have named (from 7.0.1) spewing the following errors every few
>> > seconds:
>> >
>> > Jun 23 21:09:56 murthe named[22809]: client 0x7f7ff0677800
>> > (220.29.86.203.in-addr.ar
> I have named (from 7.0.1) spewing the following errors every few
> seconds:
>
> Jun 23 21:09:56 murthe named[22809]: client 0x7f7ff0677800
> (220.29.86.203.in-addr.arpa): query_find: unexpected error after resuming:
> failure
None of the delegated-to name servers for 29.86.203.in-addr.arpa
j...@ziaspace.com (John Klos) writes:
Sometime between RC1 and RC2, something happened to termcap. I often ssh
from a Mac (TERM is xterm-256color) and nothing has changed on that end
for ages. However, now on any NetBSD-7.0_RC2 system, the shell shows ^?
whenever a backspace is entered and
On Tue, Aug 04, 2015 at 08:06:03PM +0700, Pongthep Kulkrisada wrote:
I found that ntpdc doesn't work, while ntpq works pretty fine.
This is the effect of a newer ntp version and updated /etc/ntp.conf.
After some security issues, ntpdc support has been turned off by default.
And if you want
As always, please let us know how 7.0_RC2 works for you! Any feedback,
Lack of SMP support on Pi 2 is a severe constraint. Any ETA for the same?
It looks like there is a yet-to-be-processed pull-up request
(#890) in the pullup-7 queue asking for exactly this.
That pull-up request was
As always, please let us know how 7.0_RC2 works for you! Any feedback,
Lack of SMP support on Pi 2 is a severe constraint. Any ETA for the same?
It looks like there is a yet-to-be-processed pull-up request
(#890) in the pullup-7 queue asking for exactly this.
Regards,
- Håvard
Got a newer laptop gifted to me this week and had the great
pleasure of booting the latest install image from releng
(20150106). Attached is the dmesg. I would have continued with
the install except for the lack of wireless and other
networking hardware support.
Wireless is probably this
Unsurprisingly, there appears to be support for it in the Linux
camp, via among others the wl driver, ref.
https://wiki.debian.org/wl
and that driver supports some of the same chips our bwi driver
does.
Unfortunately, that driver (the Linux wl driver) is closed-source.
However, it
I just tried to use agr(4) for the first time on NetBSD, on a
host running NetBSD 1.6.3. It's coupled to a pair of Juniper
stacked switches upstream. Ifconfig on the host does not show
flags=COLLECTING,DISTRIBUTING for one of the interfaces:
You've got bnx under agr. I don't think bnx can
Hm, so the MAC address of each member should be set to the MAC
address on the agr interface (which seems to be initialized to
the MAC address of one of the members -- the first?)?
Yes, the first. And none of this will work if the 2nd...nth interfaces
have any network-layer addresses
Hm, so the MAC address of each member should be set to the MAC
address on the agr interface (which seems to be initialized to
the MAC address of one of the members -- the first?)?
Yes, the first. And none of this will work if the 2nd...nth interfaces
have any network-layer addresses
Hi,
I just tried to use agr(4) for the first time on NetBSD, on a
host running NetBSD 1.6.3. It's coupled to a pair of Juniper
stacked switches upstream. Ifconfig on the host does not show
flags=COLLECTING,DISTRIBUTING for one of the interfaces:
agr0:
Havard, thank you for your support. I saw a message (in 2012) from you
stating that for 2230 there was not yet a similar driver because it was a
different family of device, and there was not yet a port in freebsd or
openbsd.
https://mail-index.netbsd.org/netbsd-users/2012/10/19/msg011722.html
On Jan 15, 2014, at 10:21 , Justin Cormack jus...@specialbusservice.com
wrote:
On Wed, Jan 15, 2014 at 8:47 AM, Fredrik Pettai pet...@nordu.net wrote:
While at the topic randomness, would be good if NetBSD could
implement an ioctl like Linux RNDADDENTROPY?
This helps to increase the
I have to replace my current laptop I have found an IBM Thinkpad
T42 with 1.5GB RAM and a small Hardisk. Its a sturdy built thing what
fits my needs.
My question - is anybody out there who had ever used one with NetBSD?
Anything I should know about this model before I buy it and install
57 matches
Mail list logo
