Re: back to "Drive ID Changed"

2021-05-31 Thread Martin Husemann
On Mon, May 31, 2021 at 08:20:50PM +, Todd Gruhn wrote: > Will I need to reinstall NetBSD from scratch? What does "gpt show wd0" say? (replace wd0 by whatever disk your root partition is on) Martin

Re: back to "Drive ID Changed"

2021-05-31 Thread RVP
On Mon, 31 May 2021, Todd Gruhn wrote: Here is my fstab. It still does not work. # NetBSD /etc/fstab # See /usr/share/examples/fstab/ for more examples. ROOT.a=NetBSD_9.2/ffsrw,noatime1 1 ROOT.b=NetBSD_swapnoneswapsw,dp The correct syntax is: NAME=GPT_LABEL Here

Re: back to "Drive ID Changed"

2021-05-31 Thread Todd Gruhn
https://mail-index.netbsd.org/netbsd-users/2020/09/28/msg025772.html It says that drives are numbered in the order they are found. I have noticed this on my USB memory sticks. Since everything is on the same physical hard-drive, and I recabled it, then this should not matter, right? Will I need

procfs difference between NetBSD and Linux

2021-05-31 Thread Mark Davies
The below program demonstrates a difference between /proc on NetBSD and Linux. If run in a directory with a writable "foo.txt" then on Linux the second openat() succeeds but on NetBSD it fails (EEXIST). This behavior difference breaks the latest samba (4.14.x) on NetBSD. Can this be fixed?

Re: back to "Drive ID Changed"

2021-05-31 Thread Todd Gruhn
Thanks. I will try that. On Mon, May 31, 2021 at 5:24 PM RVP wrote: > > On Mon, 31 May 2021, Todd Gruhn wrote: > > > Here is my fstab. It still does not work. > > > > # NetBSD /etc/fstab > > # See /usr/share/examples/fstab/ for more examples. > > > > ROOT.a=NetBSD_9.2/ffsrw,noatime

Re: firefox on NetBSD: files again

2021-05-31 Thread tlaronde
On Mon, May 31, 2021 at 05:05:22PM +0200, Martin Husemann wrote: > On Mon, May 31, 2021 at 03:39:53PM +0200, tlaro...@polynum.com wrote: > > With my kernel compiled with maxusers 16, ulimit -n could not pass 956. > > And it was set to this maximum and firefox crashed. > > What NetBSD version are y

Re: firefox on NetBSD: files again

2021-05-31 Thread Martin Husemann
On Mon, May 31, 2021 at 03:39:53PM +0200, tlaro...@polynum.com wrote: > With my kernel compiled with maxusers 16, ulimit -n could not pass 956. > And it was set to this maximum and firefox crashed. What NetBSD version are you using and how much RAM do you have? >From CHANGES-9.2: Set a b

Re: firefox on NetBSD: files again

2021-05-31 Thread tlaronde
On Mon, May 31, 2021 at 01:46:11PM +0100, Sad Clouds wrote: > On Mon, 31 May 2021 09:33:18 +0200 > tlaro...@polynum.com wrote: > > > Once more it is a problem of number of files a proc can open. What was > > enough for a previous version is not enough anymore because firefox > > renders pages with

Re: back to "Drive ID Changed"

2021-05-31 Thread Todd Gruhn
I just executed: gpt create wd1 I got: gpt: /dev/rwd1: Device already contains a GPT. Destroy it first. Aparrently part of this already done with gpt... On Mon, May 31, 2021 at 8:42 AM Todd Gruhn wrote: > > Here is my fstab. It still does not work. Does the entire fstab need to be > re

Re: firefox on NetBSD: files again

2021-05-31 Thread Sad Clouds
On Mon, 31 May 2021 09:33:18 +0200 tlaro...@polynum.com wrote: > Once more it is a problem of number of files a proc can open. What was > enough for a previous version is not enough anymore because firefox > renders pages with litteraly thousands of pieces/files. Which version of Firefox is it? D

Re: back to "Drive ID Changed"

2021-05-31 Thread Todd Gruhn
Here is my fstab. It still does not work. Does the entire fstab need to be rewritten? I found gpt in section 8. I believe my system (and all drives) are booted by a UEFI menu that comes up when the machine restarted. # NetBSD /etc/fstab # See /usr/share/examples/fstab/ for more examples. /dev/wd

firefox on NetBSD: files again

2021-05-31 Thread tlaronde
This may help others. Since my previous firefox installation on NetBSD x86_64/9.1 was starting not to display correctly some sites, I upgraded. Since with the huge dependencies of firefox, I seem to be unable now to compile from pkgsrc on my node---there is always several packages that fail to co