mknod fails after wrong arch MAKEDEV

2 msg	ipsec.conf question
1 msg	pbm install 4.3 Packard Bell EasyNote
11 msg	Apache suexec problem
9 msg	1U IBM or Dell server for firewall
1 msg	gtk+2-2.12.7 on't upgrade after upgrade to 4.3
4 msg	colors in regular openbsd terminal
7 msg	problem building release for 4.3 stable
18 msg	Window Manager
2 msg	What tarball is xlib.h in in 4.3?
5 msg	newfs during install
1 msg	Mehr Insolvenzen in den USA
11 msg	Jack, sun and envy problem

mknod fails after wrong arch MAKEDEV
\ ppruett (4 May 2008)
. \ Miod Vallat (4 May 2008)
. \ Paul Pruett (4 May 2008)
. . \ Hannah Schroeter (5 May 2008)
. . . \ Paul Pruett (5 May 2008)

3 msg	mplayer & snapshot install
7 msg	OpenBSD 4.3 and Xorg resolution 1280x800?
1 msg	Good news re: Flash9
37 msg	Doubt about license
2 msg	source/destination nat pf, user space filtering pf
61 msg	Editing C with...
2 msg	4.2, ppp problem

Subject:	mknod fails after wrong arch MAKEDEV
Group:	Openbsd-misc
From:	ppruett
Date:	4 May 2008

on one amd64 computer
Somehow mknod will not accept device name, but it can create a fifo

works on a similar amd64 computer w/ same arch. so it was likely
it was something like this that did it:

The screw up,
on an amd64 4.3beta, in an accident, snafu,
I copied the i386 MAKEDEV to /dev and thus ruined /dev when doing MAKEDEV
all because MAKEDEV deleted all then could not make properly...

To fix I booted off a cdrom and did an upgrade, thus fixing /dev
OKAY fine I got all working, never used MAKEDEV or mknod till much
later after may 1st stable...

OKAY used cdrom for "upgrade" to make the computer 4.3 stable.

needed use mknod to make some dev for a chroot, and mknod failed by
name...?

so i went to /dev and out of curiosity did the MAKEDEV all
and FUBAR, it erased /dev/* and could not remake...
So had to reboot with stable cdrom and let it do MAKEDEV
while doing "upgrade"

erasing all of /dev and doing upgrade from cdrom again does not
really fix issue, can't use mknod

----

QUESTION, is openbsd 4.3 doing some kind of policing on mknod?
I googled a situation were SELinux could prevent mknod from working
in that world.?

example on this screwed machine if I change to say, /tmp

cd /tmp
mknod -m 666 zero c 2 12

the result is

ksh: mknod: zero: Invalid argument

and
cd /tmp
/dev/MAKEDEV std

the result is

sh: <stdin>[1]: mknod: console: Invalid argument
sh: <stdin>[1]: mknod: tty: Invalid argument
sh: <stdin>[1]: mknod: mem: Invalid argument
sh: <stdin>[1]: mknod: kmem: Invalid argument
sh: <stdin>[1]: mknod: null: Invalid argument
sh: <stdin>[1]: mknod: zero: Invalid argument
sh: <stdin>[1]: mknod: stdin: Invalid argument
sh: <stdin>[1]: mknod: stdout: Invalid argument
sh: <stdin>[1]: mknod: stderr: Invalid argument
sh: <stdin>[1]: mknod: ksyms: Invalid argument
sh: <stdin>[1]: mknod: drum: Invalid argument
sh: <stdin>[1]: mknod: klog: Invalid argument
sh: <stdin>[1]: mknod: xf86: Invalid argument
chgrp: mem: No such file or directory
chgrp: kmem: No such file or directory
chgrp: ksyms: No such file or directory
chgrp: drum: No such file or directory
chgrp: console: No such file or directory
chgrp: tty: No such file or directory
chgrp: null: No such file or directory
chgrp: zero: No such file or directory
chgrp: stdin: No such file or directory
chgrp: stdout: No such file or directory
chgrp: stderr: No such file or directory
chgrp: klog: No such file or directory
chgrp: xf86: No such file or directory