Re: mutt wants sasl

[Jeff_W]

Bob Bernstein  wrote:
> ..
> No authenticators
> mutt needs sasl
>
> Well, I'm stumped. I don't know anything about sasl. I 
> have the following packages installed:
> ..

Can't help with mutt but thought I'd point out that you can use
the native postfix to do the interacting with your provider's
SMTP server:

Postfix MTA on NetBSD 6.x:
https://sdf.org/?tutorials/smtpauth#postfix-netbsd6

It uses a native sasl library so perhaps you can figure out how
to build nutt against that instead of using postfix.

jgw

Re: Is the Buffalo Terastation Supported

[Jeff_W]

k...@protonmail.com wrote:

> Hi
> I have an old Buffalo Terastation and wondered if it's supported in any way?
> It's a TS-XL/R5.
>
> I'm not going to hold my breath for a helpful reply as after a bit 
> of searching I can't find anyone running their own OS on this kit.

Sounds like it should work:

https://en.wikipedia.org/wiki/Buffalo_network-attached_storage_series#TeraStation

If not NetBSD maybe Debian.  Post your dmesg(1) if you get things going.

Re: package upgrade strategy

[Jeff_W]

Alistair Crooks <a...@pkgsrc.org> wrote:

> On 28 September 2017 at 08:40, Jeff_W <j...@sdf.org> wrote:
> > % cd /pkgsrc/foo/pkg-A
> > % sudo make clean && sudo make replace
> >
> > If the above breaks pkg-C:
> >
> > % cd /pkgsrc/foo/pkg-C
> > % sudo make clean && sudo make clean-depends && sudo make update
>
> Orthogonal to this discussion - pkgsrc was modified to use
> just-in-time su in the early 2000s, and avoids interesting issues like
> fetching sources as root. You are definitely encouraged to use it.
>
> If you'd prefer to use sudo, rather than su, put this in your etc/mk.conf:
>
> .if exists(${LOCALBASE}/bin/sudo)
> SU_CMD= ${LOCALBASE}/bin/sudo /bin/sh -c
> .endif

Nice; wasn't aware of that - thanks Alistair

Re: package upgrade strategy

[Jeff_W]

> I hope someone can give an answer to this question from a newbie: how can
> I handle situations when an already installed package (say A) needs to be
> upgraded due to a newly installed package (say B) as it's being a
> dependency for it but another already installed package (say C) still
> needs the older version of package A? Upgrading package C may be thought
> of as help but it disappeared from the 7.1 package repo and as far as I
> could see it was last present in 7.0_2017Q1.

% cd /pkgsrc/foo/pkg-A
% sudo make clean && sudo make replace

If the above breaks pkg-C:

% cd /pkgsrc/foo/pkg-C
% sudo make clean && sudo make clean-depends && sudo make update

HTH,
jgw

Re: old i386 3.1 packages or upgrading with KVM

[Jeff_W]

"Jeremy C. Reed"  wrote:

> Does anyone know where I can find old 3.1 packages for i386?
>
> I cannot find old source distfiles for using old pkgsrc.
> ..

If binaries are okay there is this:

ftp://ftp.NetBSD.org/pub/NetBSD-archive/NetBSD-3.1/iso/i386pkg-3.1.iso

Otherwise I think you can browse 2006/Q4 pkgsrc here:

http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/?only_with_tag=pkgsrc-2006Q4

Should be able to use cvs with -r to get specific tags; haven't actually
tried to do that in a long time...

HTH,
Jeff

Re: Motherboard recommendations?

[Jeff_W]

Mayuresh mayur...@acm.org wrote:

 On Sun, Apr 27, 2014 at 08:14:26AM +, Thomas Mueller wrote:
  Shutting down due to overheating sounds like a problem with the CPU
  and fans, or lack of fans, rather than the motherboard as such.

 ... I tried several things to isolate the cause, but never suspected
 the CPU. I think I'll give that a try before purchasing a new motherboard.

You might want to verify that the mobo is really overheating using either
another OS /or temperature probes.  The NetBSD ACPI temp sensor stuff is
known to read bogus critical temp spikes on certain hardware and the default
/etc/powerd/scripts have the system shutdown when those are detected.  I've
got an old HP mini-tower system that that happens to; once I realized there
was no over-heating going on I editted /etc/powerd/scripts/sensor_temperature
to do nothing for the critical case.

HTH,
jgw