Subject: Re: printf in /dev/MAKEDEV
To: Luke Mewburn <lukem@NetBSD.org>
From: Kirk Russell <kirk@ba23.org>
List: current-users
Date: 05/01/2005 22:17:20
On Mon, 2 May 2005, Luke Mewburn wrote:
> On Sun, May 01, 2005 at 05:07:31PM -0400, Kirk Russell wrote:
> | Hello,
> |
> | Last night, I did a checkout of the netbsd-3 tree and built a vax.iso to
> | install on simh/VAX.
> |
> | During the install, I got a "printf: not found" error during the MAKEDEV
> | step. If /dev/MAKEDEV now requires printf, should printf be in the
> | install boot image? Or am I missing something? Thanks.
>
> I've made a fix for this in -current in the files:
> etc/MAKEDEV.tmpl 1.43
> etc/etc.vax/MAKEDEV.conf 1.8
>
> Could you test that fix in your netbsd-3 build and let me know
> if it solves the problem?
I wanted to try out the changes before building a new iso.
I ran "sh MAKEDEV dz3" with the 1.6.2 MAKEDEV and it tried to create these
devices -- to get a baseline of the expected behaviour:
mknod tty24 c 1 24
mknod tty25 c 1 25
mknod tty26 c 1 26
mknod tty27 c 1 27
mknod tty28 c 1 28
mknod tty29 c 1 29
mknod tty30 c 1 30
mknod tty31 c 1 31
I quickly merged in your changes (so, I may have made a mistake), to the
1.6.2 MAKEDEV script, and it now tries to create these devices instead:
mkdev tty03 c 1 24
mkdev tty03 c 1 25
mkdev tty03 c 1 26
mkdev tty03 c 1 27
mkdev tty03 c 1 28
mkdev tty03 c 1 29
mkdev tty03 c 1 30
mkdev tty03 c 1 31
These additional diffs appear to keep the same behaviour as the 1.6.2
MAKEDEV script. Does this change make any sense? Thanks for the quick
response!
Index: MAKEDEV.conf
===================================================================
RCS file: /cvsroot/src/etc/etc.vax/MAKEDEV.conf,v
retrieving revision 1.8
diff -r1.8 MAKEDEV.conf
97,98c97,98
< ounit=$(zeropad 2 $unit)
< mkdev tty$ounit c 1 $(($unit * 8 + $i))
---
> munit=$(($unit * 8 + $i))
> mkdev tty$(zeropad 2 $munit) c 1 $munit
--
Kirk Russell <kirk@ba23.org> http://www.ba23.org/
Bridlewood Software Testers Guild Ottawa Ontario Canada