Hi!
It seems as pkgin has "$recently" (for a _very_ fluffy definition
thereof - it could be _years_) started to automagically do a "full
upgrade" as soon as you try to install/upgrade a single package.
How do I do to upgrade only a specific package and the ones it depends
on
Hallo Martin
Martin Husemann wrote:
You can check with:
fgrep /usr/lib/libsqlite3.so.1 /etc/mtree/set.*
It should show ./usr/lib/libsqlite3.so.1.4 in set.base and
./usr/libdata/debug/usr/lib/libsqlite3.so.1.4.debug in set.debug (if
you have that installed).
Thanks! indeed, that pointed out
On Thu, Jan 30, 2025 at 05:48:26PM +0100, Riccardo Mottola wrote:
> I think I can just install again the same install.tgz and it should cure
> that. Someone knows where it is contained? Maybe even sysinst can do that.
You can check with:
fgrep /usr/lib/libsqlite3.so.1 /etc/mtree/set.*
It should
Hi,
I noticed that after upgrade, my sqlite is missing:
disc$ ls -l /usr/lib/libsqlite3*
-r--r--r-- 1 root wheel 1579258 Dec 16 14:08 /usr/lib/libsqlite3.a
lrwxr-xr-x 1 root wheel 17 Dec 16 14:08 /usr/lib/libsqlite3.so
-> libsqlite3.so.1.4
lrwxr-xr-x 1 root wheel 17 Dec
Hi,
Riccardo Mottola wrote:
Should I just nuke /usr/pkg/pkgdb/GConf-3.2.3nb18/ and rebuild and see
if upgrade then completes?
the saga continues... I decided to remove the corefile and the empty
GConf dir. Rebuild & rebuild-tree and start pkgin upgrade again...
works a bit , but dies
Hi,
I am unable to complete pkg upgrade and am left with half-working packages.
Cannot read +CONTENTS of package GConf-3.2.3nb18
# pkgin upgrade
pkg_info: cannot read meta data file +CONTENTS of package
GConf-3.2.3nb18: No such file or directory
pkgin: Dependency perl>=5.38.0<5.39.0
> Root C(ertificate)A(uthorities) are a failure and acts of oppression
I don't think they're a failure per se. They do what they're designed
to do very well. Trouble is, it's what the designers want(ed), not
what you (or I) want(ed).
CA-hierarchy-secured communication is a fail for me because i
Martin Husemann wrote in
<20241117120849.ga8...@mail.duskware.de>:
|On Sat, Nov 16, 2024 at 11:27:12PM -0600, Don Lee wrote:
|> Ideas?
|
|For NetBSD 9.x the "trick" is likely to install
|
| security/mozilla-rootcerts-openssl
|
|NetBSD-10 and newer does not need that (it comes with system p
I tried just installing pkg "mozilla-rootcerts-openssl”, and it seems to have
fixed cpan. I will keep your comments for future reference if other things
misbehave.
Thank you,
-dgl-
> On Nov 17, 2024, at 7:21 AM, Martin Neitzel
> wrote:
>
> Don Lee:
>> Ideas?
>
> Looks to me as if certific
Don Lee:
> Ideas?
Looks to me as if certificate verification fails on your box because
the collection of root certificates cannot be found.
The oldest way to get them was to install the pkg "mozilla-rootcerts".
On top of that, one had to manually unpack the certificate bundle
and to create/update
On Sat, Nov 16, 2024 at 11:27:12PM -0600, Don Lee wrote:
> Ideas?
For NetBSD 9.x the "trick" is likely to install
security/mozilla-rootcerts-openssl
NetBSD-10 and newer does not need that (it comes with system provided trust
anchors).
Martin
Hi,
I finally bit the bullet and upgraded my rock solid 8.2 NetBSD-macppc system to
NetBSD 9.4 largely to get support for the many pkgsrc packages. Unfortunatly, I
now have a new problem.
If I run cpan (perl-5.38.2) and try to install (or upgrade) a pod, HTTP::Tiny
fails to connect to
I've solved that problem by unpacking sets and copying the libraries to
where they're expected.
On 07/22/24 01:30 PM, pms-...@outlook.com wrote:
xuser wrote:
Is there a way to upgrade NetBSD 6.1.4 to NetBSD 10.0 without breaking
custom installed software?
Thanks,
Ben
I highl
On Tue 23 Jul 2024 at 07:55:12 +0200, Martin Husemann wrote:
> Only if you manually deinstall shared libraries. The typical case is that
> the old libs are just left in place and new stuff uses new libs, while
> old programs continue to use the old libs.
I have some binaries around from NetBSD 4.0
On Tue, Jul 23, 2024 at 05:45:41PM +0200, pms-...@outlook.com wrote:
> BTW. Is it possible to run a.out format[as opoosed to ELF] binaries on
> NetBSD 10?
Yes, that should still work.
Martin
Martin Husemann wrote:
On Mon, Jul 22, 2024 at 08:30:53PM +0200, pms-...@outlook.com wrote:
xuser wrote:
Is there a way to upgrade NetBSD 6.1.4 to NetBSD 10.0 without breaking
custom installed software?
Thanks,
Ben
There is no reason custom installed software should break when doing an
Thank you!
On Tue, 23 Jul 2024, Martin Husemann wrote:
On Mon, Jul 22, 2024 at 08:30:53PM +0200, pms-...@outlook.com wrote:
xuser wrote:
Is there a way to upgrade NetBSD 6.1.4 to NetBSD 10.0 without breaking
custom installed software?
Thanks,
Ben
There is no reason custom installed
On Mon, Jul 22, 2024 at 08:30:53PM +0200, pms-...@outlook.com wrote:
> xuser wrote:
> > Is there a way to upgrade NetBSD 6.1.4 to NetBSD 10.0 without breaking
> > custom installed software?
> >
> > Thanks,
> > Ben
There is no reason custom installed software s
xuser wrote:
Is there a way to upgrade NetBSD 6.1.4 to NetBSD 10.0 without breaking
custom installed software?
Thanks,
Ben
I highly doubt it unless you are using static binaries :)
Everything should work but LD dependencies(ldd(1) tool) are ALWAYS
problematic after upgrades.
Is there a way to upgrade NetBSD 6.1.4 to NetBSD 10.0 without breaking
custom installed software?
Thanks,
Ben
e audio device was reset.
Relinking
the audio0 device solved the problem.
On 06/26/24 04:00 PM, Justin Parrott wrote:
> how did you upgrade?
>
> On Thu, Jun 20, 2024 at 1:57 PM Jay Nelson mailto:j...@ecpi.com>
> <mailto:j...@ecpi.co
; > how did you upgrade?
> >
> > On Thu, Jun 20, 2024 at 1:57 PM Jay Nelson > <mailto:j...@ecpi.com>> wrote:
> >
> > I lost it upgrading from 9,3 to 10RC2 and fixed it with a MIB edit. I
> > didn't expect moving to 10.0 would clobber my sysctl.
how did you upgrade?
On Thu, Jun 20, 2024 at 1:57 PM Jay Nelson wrote:
> I lost it upgrading from 9,3 to 10RC2 and fixed it with a MIB edit. I
> didn't expect moving to 10.0 would clobber my sysctl.conf. Now, I can't
> remember the MIB. Any help restoring audio would be appr
NetBSD install CD. The problem was the audio device was reset. Relinking
the audio0 device solved the problem.
On 06/26/24 04:00 PM, Justin Parrott wrote:
how did you upgrade?
On Thu, Jun 20, 2024 at 1:57 PM Jay Nelson <mailto:j...@ecpi.com>> wrote:
I lost it upgrading from 9,3
On 06/20/24 01:02 PM, Martin Husemann wrote:
On Thu, Jun 20, 2024 at 12:53:41PM -0500, Jay Nelson wrote:
I lost it upgrading from 9,3 to 10RC2 and fixed it with a MIB edit. I didn't
expect moving to 10.0 would clobber my sysctl.conf. Now, I can't remember
the MIB. Any help restoring audio wou
On Thu, Jun 20, 2024 at 12:53:41PM -0500, Jay Nelson wrote:
> I lost it upgrading from 9,3 to 10RC2 and fixed it with a MIB edit. I didn't
> expect moving to 10.0 would clobber my sysctl.conf. Now, I can't remember
> the MIB. Any help restoring audio would be appreciated. Enclosed is "sysctl
> -A"
I lost it upgrading from 9,3 to 10RC2 and fixed it with a MIB edit. I
didn't expect moving to 10.0 would clobber my sysctl.conf. Now, I can't
remember the MIB. Any help restoring audio would be appreciated.
Enclosed is "sysctl -A" output. Thanks
--jay
kern.ostype = NetBSD
kern.osrelease = 10.0
Hi,
Havard Eidnes wrote:
> 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:
thanks, you recalled correctly. I removed it and was able to reinstall
windowmaker too. X11 starts up..
On Mon, 6 May, 2024, 7:54 pm Riccardo Mottola,
> wrote:
>
>> Hi,
>>
>> I upgraded two of my classic ThinkPads (i386) from 9.3 to 10.0.
>> Upgrade went apparently smooth. Then I issue pkgin update & upgrade.
>>
>> However, shock... startx fails. windo
> 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 c
Also if repository is pointing to 10.0 and packages available on repo.
Remove Cairo and install windowmaker
On Mon, 6 May, 2024, 7:54 pm Riccardo Mottola,
wrote:
> Hi,
>
> I upgraded two of my classic ThinkPads (i386) from 9.3 to 10.0.
> Upgrade went apparently smooth. Then I
Did you also change pkgin repo?
On Mon, 6 May, 2024, 7:54 pm Riccardo Mottola,
wrote:
> Hi,
>
> I upgraded two of my classic ThinkPads (i386) from 9.3 to 10.0.
> Upgrade went apparently smooth. Then I issue pkgin update & upgrade.
>
> However, shock... startx fails.
Hi,
I upgraded two of my classic ThinkPads (i386) from 9.3 to 10.0.
Upgrade went apparently smooth. Then I issue pkgin update & upgrade.
However, shock... startx fails. windowmaker is missing!
I explictely try to install it:
sudo pkgin install windowmaker
Password:
calculating dependen
Hi,
Martin Husemann wrote:
> On Tue, Apr 23, 2024 at 01:20:12PM +, Riccardo Mottola wrote:
>> /dev/sd0e /media/usb msdos rw 0 0
> What is that partition?
> Is that "usb" device available (as sd0) during your upgrade experiment?
external
On Tue, Apr 23, 2024 at 01:20:12PM +, Riccardo Mottola wrote:
> /dev/sd0e /media/usb msdos rw 0 0
What is that partition?
Is that "usb" device available (as sd0) during your upgrade experiment?
If you boot the installer from a USB disk, that might b
tmpfs rw,-m1777,-sram%25
/dev/sd0e /media/usb msdos rw 0 0
/dev/cd0a /media/cdromcd9660 ro,noauto
it confirms that "wd" is completely dedicated to NetBSD.
If we had nice BSD stickers (especially with the Daemon) I'd remove the
Windows7 for it :)
Hi,
Martin Husemann wrote:
Can you boot the original install CD you used, exit the installer and
check the output of:
sysctl machdep.bootmethod
This should either tell you BIOS or UEFI, and this is how the installer
decides what kind of setup the booted system later will need.
On Wed, Apr 10, 2024 at 11:52:04PM +0200, Riccardo Mottola wrote:
> 0: NetBSD (sysid 169)
> bootmenu: NetBSD
> start 2048, size 625140400, Active
> 1:
> 2:
> 3:
> Bootselector disabled.
> First active partition: 0
Can you show us the /etc/fstab file from the NetBSD partition?
Martin
On Wed, Apr 10, 2024 at 11:42:22PM +0200, Riccardo Mottola wrote:
> Your explanation sounds plausible.
> However, "UEFI Boot Mode" is disabled in BIOS, I don't know if it is still
> used by the CD or "detected" somehow anyway.
>
> How can I tell further?
Can you boot the original install CD you u
Robert Elz wrote:
| no "e" of course... and no MS-DOS in sight. It was already a fully
| BSD-ized system.
What does fdisk show? (ie: the MBR label).
fdisk on wd0 run from the utility shell of the install cd says:
0: NetBSD (sysid 169)
bootmenu: NetBSD
start 2048, size 625140400, A
Hi,
Martin Husemann wrote:
Try the BIOS-only install image instead - I bet your system boots the
CD via UEFI, but the original installation was BIOS only.
when booting from CD, I see:
NetBSD/x86 BIOS Boot Revision 5.11
Is this meaningful?
Riccardo
ppose it can find out at least what partitions are there?
Other attempts and workarounds?
I already have a half-assed system using sysupgrade, so I want to avoid
that. My goal was to use this system with the classic upgrade and then
maybe compare files like wscons, etc.
(Although I already hav
On Tue, Apr 09, 2024 at 10:28:46PM +0200, Riccardo Mottola wrote:
> So I have a perfect working 9.3 installation on on an HP ProBook laptop.
> I boot the CD which works fine
Try the BIOS-only install image instead - I bet your system boots the
CD via UEFI, but the original installation was BIOS on
Date:Tue, 9 Apr 2024 22:28:46 +0200
From:Riccardo Mottola
Message-ID: <9f0bd479-42ef-7842-90fb-0d6a503cf...@libero.it>
| no "e" of course... and no MS-DOS in sight. It was already a fully
| BSD-ized system.
What does fdisk show? (ie: the MBR label).
kre
Hi!
I want to upgrade my 9.3 amd64 laptop.
Since my other upgrade using sysupgrade was a failure, i tried doing it
via CD install.
I still hope either to get help fixing my other laptop or being able to
"compare" with a successful install
So I have a perfect working 9.3 installatio
Hi All,Sorry for sending an html email but locked myself out of my NetBSD.
After upgrading to version 10 yesterday and rebooting, xdm started and I could
log in. When starting it today, I cannot log in to X as the user/pw combo is
reported as incorrect. However, I can log in with the same user/p
Sorry for the noise, turned out that after pkgin upgrade, some stuff
like default wm (jwm) got broken dependencies which triggered these
fawlty towers (symptoms on xdm login).
On 4/6/24 21:31, r0ller wrote:
Hi All,
Sorry for sending an html email but locked myself out of my NetBSD.
After
Hi Martin,
On 11/10/22 07:45, Martin Husemann wrote:
On Thu, Nov 10, 2022 at 04:30:18AM +0700, Robert Elz wrote:
The error you saw is harmless (to you), there is nothing to fix.
Not quite, the installer needs to detect this and deal with it - I will
fix it (but not before next week, sorry).
O
On Thu, Nov 10, 2022 at 04:30:18AM +0700, Robert Elz wrote:
> The error you saw is harmless (to you), there is nothing to fix.
Not quite, the installer needs to detect this and deal with it - I will
fix it (but not before next week, sorry).
One immediate workaround would be to use the legacy bios
rs to halt
1) upgrade
2) choose wd0
3) command fails -> continue
4) try mounting it anyway?
if no, installer halts, which is what I always answered.
if yes, i get another error on sd0e, then continue again and then
indeed I was able to continue, install... and upgrade and get a usable,
upd
Date:Wed, 9 Nov 2022 21:36:30 +0100
From:Riccardo Mottola
Message-ID: <60792a38-6644-2687-0a3d-38e9f8a50...@libero.it>
| What do you suggest to do now?
Unless there is something wrong, nothing.On a 9.x system you don't
need any boot code updates with upgrades,
Hi Martin,
Martin Husemann wrote:
now what MS-DOS partition does it want to mess around and not finding?
The EFI boot partition (to upgrade the bootloader) - this is a bug, apparently
your hard disk uses BIOS booting, while the installer booted via UEFI from
CD, and this confuses sysinst
On Tue, Nov 08, 2022 at 07:54:40PM +0100, Riccardo Mottola wrote:
> I boot from CD-ROM, select upgrade and the only HD which is "wd0",
> installation is straightforward.
>
> I get:
> Status: command failed
> Command: /sbin/fsck_msdos -o -q /dev/rsd0e
>
>
Hi,
part of the upgrading campaign, after partial success on x86... let's go
to amd64. Candidate is an HP ProBook
I boot from CD-ROM, select upgrade and the only HD which is "wd0",
installation is straightforward.
I get:
Status: command failed
Command: /sbin/fsck_msdos -
Hi,
I started upgrading my various computers to 9.3, starting from the most
"standard" ones. Unfortunately my first two attempts already went havoc.
Upgrade method chosen was to use the CD ISO.
Candidate is a ThinkPad T30, running classic intel x86 32bit, running
9.2 with a ver
On Mon, 7 Mar 2022 at 12:10, Steve Blinkhorn wrote:
>
> Thanks, helpful and enlightening, and I am pursuing the
> Heirloom distribution. Shame about the name, though, sounds like
> 'legacy' which has come to mean out-of-date. Troff is one of those
> software designs that far exceeded in its capa
2022 17:26:23 + (UTC), st...@prd.co.uk (Steve Blinkhorn)
> wrote:
> Subject: Re: groff issue after upgrade to NetBSD-9.2
> >
> > Unpacking the textproc set overwrites files like
> > /usr/share/groff_font/devps/DESC and devps/download, and maybe other
> >
At Fri, 4 Mar 2022 17:26:23 + (UTC), st...@prd.co.uk (Steve Blinkhorn)
wrote:
Subject: Re: groff issue after upgrade to NetBSD-9.2
>
> Unpacking the textproc set overwrites files like
> /usr/share/groff_font/devps/DESC and devps/download, and maybe other
> files which have bee
Answer:
Unpacking the textproc set overwrites files like
/usr/share/groff_font/devps/DESC and devps/download, and maybe other
files which have been adapted or expanded locally. The unpacking
process follows any symbolic link that devps has been set to rather
than overwriting the symbolic link wit
This is on amd64, but I doubt that that's relevant.
I have an extensive collection of fonts for PostScript, so
/usr/share/groff_font/devps is a symbolic link to a /fonts directory. It
has been so since NetBSD-1.x and before that on BSD/OS and before that
into the mists of time.
I upgraded to Net
es not install anything after upgrade to 9.2
Címzett: r0ller < netbsd-users@netbsd.org (Link ->
mailto:netbsd-users@netbsd.org)
Boot to single user and full fsck. Also make the backups you have been meaning
to get around to right away
Boot to single user and full fsck. Also make the backups you have been meaning
to get around to right away
Hi Greg,
Thanks for your suggestions! It indeed seems to be corrupted :( I tried
to nuke (rm -rf) the directory
/usr/pkg/pkgdb/p5-Net-SSLeay-1.88nb1 but I got back that the directory
is not empty which is pretty unusual for rm -rf. Now, when I try to list
its contents, three files are shown:
r0ller writes:
> The only error I see in pkg_install-err.log (which is not shown as
> error) which seems to block each pkg install is:
>
> pkg_admin: Cannot read +CONTENTS of package p5-Net-SSLeay-1.88nb1
>
> Does anyone have any hint?
pkg_admin rebuild-tree
pkg_admin check
make sure your var
On Thu, Jul 08, 2021 at 04:14:08PM +0200, Martin Husemann wrote:
> On Thu, Jul 08, 2021 at 02:36:17PM +0200, r0ller wrote:
> > is quite noticeable when starting firefox. However, after changing
> > repositories.conf to point to amd64/9.2/All and upgrading all packages,
> > nothing seems to have bee
On Thu, Jul 08, 2021 at 02:36:17PM +0200, r0ller wrote:
> is quite noticeable when starting firefox. However, after changing
> repositories.conf to point to amd64/9.2/All and upgrading all packages,
> nothing seems to have been upgraded and pkgin does not seem to install
> anything.
The repositori
Hi All,
I've just upgraded from 9.0 (amd64) to 9.2 via sysinst successfully from
ftp. Everything seems to work fine as earlier and surprisingly faster
what is quite noticeable when starting firefox. However, after changing
repositories.conf to point to amd64/9.2/All and upgrading all packages,
We recently upgraded a few of our servers to postgres 13 and the ones that have
this version have begun hanging or restarting ..
Bunch of them are on netbsd 9 while very few of them are on 7.12 netbsd9 does
not provide a coredump however I noticed this on the server that has netbsd 7.12
The serv
On Tue, Jun 22, 2021 at 08:54:31AM -0400, Greg Troxel wrote:
> it looks like a normal stat syscatl, but also like there is some
> invocation of the emulation layer.
stat here is only the trigger, but not the cause. The kernel ran out of
memory (the kernel pmap can not be enlarged) - which is a ver
(Repointed to netbsd-users as this is about a problem in NetBSD release
versions, and not clearly about anything in particular.)
You are as far as I know the first to report this.
Looking at your crash:
Derrick Lobo writes:
> crash -M netbsd.0.core
> Crash version 7.1.2, image version 7.1.2.
So I just upgraded Xen to xenkernel413-4.13.2nb5, but without first
upgrading the Xen tools, as otherwise how would one safely shut down any
running domUs, etc.? :-)
Once upgrading to xentools413-4.13.2nb4 I immediately got stuck:
# xl list
NameID Mem VC
Bob Bernstein wrote:
> Shared object "libc.so.12" not found
[...]
> The message shown is what appeared as I finished what appeared
> to be an uneventful upgrade from an old 'current' netbsd (May
> of last year) to amd64 9.1.
[...]
> trouble appeared:
>
:12 libc.so -> libc.so.12.218
lrwxr-xr-x 1 root wheel 14 Mar 2 16:12 libc.so.12 -> libc.so.12.218
-r--r--r-- 1 root wheel 2212320 Mar 2 16:12 libc.so.12.218
>> The other option is to upgrade to current current.
[You got a pointer to sets]
If what you want is 9,
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
On Sat, 20 Mar 2021, Bob Bernstein wrote:
trouble appeared:
panic init died (signal 0, exit 1)
cpu0 begin traceback...
vpanic() at netbsd:vpanic+0x160
...and so on.
This indicates that init was killed with a SIGHUP (probably
as part of the upgrade process). Then, when the libc changed
On Sat, 20 Mar 2021, Bob Bernstein wrote:
I used the 9.1 CD I made and booted into
single-user mode. Then:
# pwd
# /
# cd lib
# ls -l libc.so.12.*
lrwxr-xr-x 1 root wheel 14 Oct 18 19:24
libc.so.12 -> libc.so.12.213
-r--r--r 1 root wheel 2079984 Oct 18 19:24
libc.so.12.213
I apol
f the library's name
The other option is to upgrade to current current.
I don't see a path to installing current on a broken system. The
download options for current all seem to be in terms of source
only. I'm not complaining, just trying to understand.
Thank you
--
RSB
On Sat, 20 Mar 2021, Greg Troxel wrote:
Current from may of 2020 is newer than 9.1, in terms of branch
relationships, so this was not an upgrade.
Well I'll be a monkey's uncle. Ha.
The other option is to upgrade to current current.
I think I'll give that a whirl.
Thank you!
--
RSB
Bob Bernstein writes:
> The message shown is what appeared as I finished what appeared to be
> an uneventful upgrade from an old 'current' netbsd (May of last year)
> to amd64 9.1.
Current from may of 2020 is newer than 9.1, in terms of branch
relationships, so this was no
The message shown is what appeared as I finished what appeared
to be an uneventful upgrade from an old 'current' netbsd (May
of last year) to amd64 9.1.
That message, about a missing libc.so.12, was interspersed on
the upgrade screen reporting almost complete success in checking
/
Hi to all! Sorry for my bad English...
Intel NUC7PJYH2 BIOS Upgrade to 0058 causes NetBSD boot failure
Intel BOXNUC7PJYH2 Version #: J67992-404, Date of Manufacture: 22 May 2020.
With previous BIOS 0057 all OK with Linux, NetBSD, FreeBSD and Windows. After
upgrading the BIOS by F7 to version
On Tue, Jan 05, 2021 at 10:18:00AM +0100, Herbert J. Skuhra wrote:
> Try: /etc/rc.d/motd start
Perfect. Thanks.
As an alternative to what Herbert suggested, you can
just edit /etc/motd and put whatver you like there
It is intended to give a (brief, hopefully) message
to people when they login.
If you have update_motd set to YES in rc.conf
(or do not have it there at all, YES is the default)
then at each bo
On Tue, Jan 05, 2021 at 02:43:35PM +0530, Mayuresh wrote:
> After upgrading sets and running etcupdate from 8.0 to 9.1, on sshing I
> get the following version string instead of the usual one. May be in
> etcupdate I made some bad choice. But where to look for to quickly fix
> this?
>
> NetBSD ?.?
After upgrading sets and running etcupdate from 8.0 to 9.1, on sshing I
get the following version string instead of the usual one. May be in
etcupdate I made some bad choice. But where to look for to quickly fix
this?
NetBSD ?.? (UNKNOWN)
--
Mayuresh
On Jan 1, 8:16, Mayuresh wrote:
} On Thu, Dec 31, 2020 at 05:12:23PM -0800, John Nemeth wrote:
} > If you use sysinst to update the system, which is the officially
} > supported way to do it, then sysinst will automatically run
} > postinstall at the end of the process which would have solved
On Thu, Dec 31, 2020 at 05:12:23PM -0800, John Nemeth wrote:
> If you use sysinst to update the system, which is the officially
> supported way to do it, then sysinst will automatically run
> postinstall at the end of the process which would have solved this
> problem. If you don't use sysins
On Dec 31, 18:58, Mayuresh wrote:
} On Thu, Dec 31, 2020 at 06:44:17AM -, Michael van Elst wrote:
} > If you use the -a option, files that weren't modified locally will be
} > changed without prompting. Otherwise you should have seen a confirmation
} > prompt.
}
} I didn't use -a. Must be then
On Thu, Dec 31, 2020 at 06:44:17AM -, Michael van Elst wrote:
> If you use the -a option, files that weren't modified locally will be
> changed without prompting. Otherwise you should have seen a confirmation
> prompt.
I didn't use -a. Must be then my bad of not noticing it. Let's leave it
the
mayur...@acm.org (Mayuresh) writes:
>On Thu, Dec 31, 2020 at 05:12:33AM -, Michael van Elst wrote:
>> Best is to update all of /etc by using the etcupdate tool that will
>> show differences and lets you chose what file to update and what file
>> you may want or need to merge yourself.
>Thanks
On Thu, Dec 31, 2020 at 05:12:33AM -, Michael van Elst wrote:
> Best is to update all of /etc by using the etcupdate tool that will
> show differences and lets you chose what file to update and what file
> you may want or need to merge yourself.
Thanks. Did it for etc and xetc and cron is runn
mayur...@acm.org (Mayuresh) writes:
>I updated sets excluding /etc on 2 amd64 VPS instances from 8.0/8.1 to
>9.1. Can that upset with cron? cron service is running but the jobs aren't
>running.
You need to update the configuration in /etc/pam.d/.
Best is to update all of /etc by using the etcupd
I updated sets excluding /etc on 2 amd64 VPS instances from 8.0/8.1 to
9.1. Can that upset with cron? cron service is running but the jobs aren't
running.
Log shows this:
cron: in pam_vprompt(): no conversation function
--
Mayuresh
Hi All,
I upgraded my box for Christmas and as there are many questions about hw
components asking which works and which not on NetBSD, here is what I
experienced. The new hw is as follows:
-AMD Ryzen 5 3600X
-MSI B450 GAMING PRO CARBON MAX WIFI
-2db Corsair 8gb DDR4 3200Mhz Vengeance Pro Black
Hi Bertrand,
BERTRAND Joël wrote:
> Just a question. Is it a Seagate disk ? On all servers I used this kind
> of disks, Hardware ECC Recovered was always high (and in constant
> increase). I have seen this issue on Linux and *BSD. And of course, I
> considere Seagate as the worst disks that
On Tue, 3 Nov 2020 11:48:41 +1030
Brett Lymn wrote:
> On Mon, Nov 02, 2020 at 12:34:27PM +0100, BERTRAND Jol wrote:
> >
> > I refuse Seagate, Samsung and other WD in my servers or
> > workstations, and I refuse SMR technology also.
> >
>
> I have heard this sort of thing from many people o
On Mon, Nov 02, 2020 at 12:34:27PM +0100, BERTRAND Jol wrote:
>
> I refuse Seagate, Samsung and other WD in my servers or workstations,
> and I refuse SMR technology also.
>
I have heard this sort of thing from many people over the years, they
get bitten by a few disk failures and form a b
On Mon 02 Nov 2020 at 08:39:00 +, Riccardo Mottola wrote:
> I checked SMART status, it looks a little worrying:
> SMART supported, SMART enabled
> id value thresh crit collect reliability description raw
> 5 100 36 yes online positiveReallocated sector count13
On Mon, Nov 02, 2020 at 11:13:01AM +0100, BERTRAND Joël wrote:
> Riccardo Mottola a écrit :
> > Then this is the data for the third day (each time I did a power-off
> > reboot, so it is not continuous operation, I shut down the laptop at night)
> >
> > SMART supported, SMART enabled
> > id value t
joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes:
>Hardware ECC Recovered was always high (and in constant increase).
That's a feature of modern high capacity drives. The only difference is
if and how such things are reported.
--
--
Michael van
1 - 100 of 211 matches
Mail list logo
