>> So what goes wrong is not at the file system level, but MBR and disklabel
>> handling. I dimly recall the disklabel moved into the type 169 MBR partition
>> a long time ago - I bet 4.0 was before that change and this is what
>> now causes the broken wedge auto-detection.
There's an interesting
> On 22 Aug 2022, at 15:19, Martin Husemann wrote:
>
> So what goes wrong is not at the file system level, but MBR and disklabel
> handling. I dimly recall the disklabel moved into the type 169 MBR partition
> a long time ago - I bet 4.0 was before that change and this is what
> now causes
Martin Husemann writes:
> On Tue, Aug 23, 2022 at 08:23:37AM -0400, Greg Troxel wrote:
>> The failure appears to be the same for /sbin/ifconfig and
>> /rescue/ifconfig, suggesting that the problem is that the kernel doesn't
>> respond correctly to something, rather than shlib issues.
>
> We do
On Tue, Aug 23, 2022 at 08:23:37AM -0400, Greg Troxel wrote:
> The failure appears to be the same for /sbin/ifconfig and
> /rescue/ifconfig, suggesting that the problem is that the kernel doesn't
> respond correctly to something, rather than shlib issues.
We do not always provide full binary
Thanks again for all the comments/hints.
I have found, and Brad Spencer has replicated, a COMPAT bug. This note
attempts to restate all useful information so previous ones can be
deleted.
First, I'm talking about:
i386
wanting full system operation with new kernel and old userland, such
Le Mon, Aug 22, 2022 at 06:45:14PM +0200, Martin Husemann a écrit :
> On Mon, Aug 22, 2022 at 05:16:19PM +0200, tlaro...@polynum.com wrote:
> > On a fresh install, with a custom compiled 9.3 with the setting of
> > DKWEDGE_METHOD_MBR and perhaps DKWEDGE_METHOD_BDSLABEL also (I'm not
> > sure), I
Thanks to all who took the time to comment and especially to experiment!
I realized that replication was not actually that hard.
Martin Husemann writes:
> So I fooled myself - here is what happened:
>
> - the disk I started with (cloned this VM instance from) had a GPT
>
> - the 4.0
On Mon, Aug 22, 2022 at 05:16:19PM +0200, tlaro...@polynum.com wrote:
> On a fresh install, with a custom compiled 9.3 with the setting of
> DKWEDGE_METHOD_MBR and perhaps DKWEDGE_METHOD_BDSLABEL also (I'm not
> sure), I was unable to boot, because since the disk numbering
> depended on the
Le Mon, Aug 22, 2022 at 09:59:28PM +0700, Robert Elz a écrit :
> Date:Mon, 22 Aug 2022 16:19:03 +0200
> From:Martin Husemann
> Message-ID: <20220822141903.ga13...@mail.duskware.de>
>
>
> | Booting a 9.3 install CD and digging around a bit I found the 9.3 kernel
>
So I fooled myself - here is what happened:
- the disk I started with (cloned this VM instance from) had a GPT
- the 4.0 installation know nothing about GPT and just did its think,
replacing the PMBR of the GPT with a real new MBR and adding a disklabel
- now the 4.0 kernel does not know
Date:Mon, 22 Aug 2022 21:59:28 +0700
From:Robert Elz
Message-ID: <8246.1661180...@jacaranda.noi.kre.to>
That is, I am replying to myself... (sad that).
| And second, find out why the existence of wedges has any effect on
| mounting wd0a (would be different if
Date:Mon, 22 Aug 2022 16:19:03 +0200
From:Martin Husemann
Message-ID: <20220822141903.ga13...@mail.duskware.de>
| Booting a 9.3 install CD and digging around a bit I found the 9.3 kernel
|
| - auto-creates bogus wedges dk0 (for the FFSv1 at /) and dk1 (for
On Sun, Aug 21, 2022 at 09:57:55AM +0200, Martin Husemann wrote:
> The only thing I found is in CHANGES-7.1:
>
> sbin/fsdb/fsdb.c1.49
> sys/ufs/ffs/ffs_vfsops.c1.340
> usr.sbin/quot/quot.c1.34
>
> The
Christopher Pinnock writes:
> Martin
> Possible in this case the file system was created on an earlier netbsd than
> 5. I have recently upgraded between each major release starting at 1.0.
>
> When I went from 7.2 to 8.2 I had problems - 8.2 will not mount the root file
> system. I had to
Martin
Possible in this case the file system was created on an earlier netbsd than 5.
I have recently upgraded between each major release starting at 1.0.
When I went from 7.2 to 8.2 I had problems - 8.2 will not mount the root file
system. I had to reboot single user with a 7.2 kernel and tune
Le Sun, Aug 21, 2022 at 07:55:45AM -0400, Greg Troxel a écrit :
>
> Christopher Pinnock writes:
>
> > There is a change of file system superblock format between 7 and 8
> > iirc which may need some attention.
>
> Do you mean what Martin just pointed out? I have definitely done
> upgrades
Date:Sun, 21 Aug 2022 07:55:45 -0400
From:Greg Troxel
Message-ID:
| But interesting that 9.2 build.sh works on 6.1.
Not relevant to the actual topic, but that stopped working for me,
I think even before -9 was released. The basic system would build,
but
Christopher Pinnock writes:
> There is a change of file system superblock format between 7 and 8
> iirc which may need some attention.
Do you mean what Martin just pointed out? I have definitely done
upgrades 5->6->7->8->9 (and 9->current about a year ago) with no issues,
but all my
On Sat, Aug 20, 2022 at 07:08:07PM -0500, Christopher Pinnock wrote:
> There is a change of file system superblock format between 7 and 8
> iirc which may need some attention.
I would like to hear details of this (as we are currently struggling
with a similar issue for the NetBSD 10 branch).
The
There is a change of file system superblock format between 7 and 8 iirc which
may need some attention.
(Previously I have managed to build.sh 9.2 on a 6.1 machine.)
C
> On 20 Aug 2022, at 13:39, Valery Ushakov wrote:
>
> On Sat, Aug 20, 2022 at 11:15:34 -0400, Greg Troxel wrote:
>
>> I am
On Sat, Aug 20, 2022 at 11:15:34 -0400, Greg Troxel wrote:
> I am helping someone update an i386 system from 5 to 9, which is on
> the net but without console (remote hands possible but really want
> to avoid that).
You can install netbsd 5 under qemu or vbox and to do a test-drive
upgrade to 9
I am helping someone update an i386 system from 5 to 9, which is on the net
but without console (remote hands possible but really want to avoid
that).
Normally I update systems by
cp -p /netbsd /netbsd.ok # save kernel that worked
put new kernel in /netbsd
reboot # now running new kernel
22 matches
Mail list logo
