The Problem, as I understand it from my paleolithic point of view, is
that there is, i.e., no /dev/com0, no /dev/puc0, etc. to determine
precisely where you're attaching.

I can imagine that it would be quite frustrating to have to divine which
port you were on (though plugging in and typing 'tty' once you got to
single-user mode wouldn't be too difficult  :/  ).

...or is the problem plugging into the "wrong" serial port in the first
place?

Can we even force a console at a particular place?

As the kernel prints
	root on wd0a dumps on wd0b

Could it not also note
	console on <wherever>

...or would that even be useful?

I'm just tossing darks, here -- taking shots at straws...


On Tue, 22 Jan 2002 wojtek@chylonia.3miasto.net wrote:

# > Just as with disks the only real solution is to hard-wire your kernel
# > configuration so that you know what major/minor numbers correspond to
# > what hardware device(s).  Unfortunately unlike disks there's no way to
#
# exactly. it's thing i like very much in netbsd which is missing in for eg.
# linux.

[I like this as well.  HD roulette is not my favourite game.]

# > do this for serial ports without renaming files in /dev.
#
# what a problem?

See above.

#
# com0    at isa0 port 0x3f8 irq 4
# com1    at isa0 port 0x2f8 irq 3
#
# puc0    at pci0 dev 8 function 0
# com2    at puc0 port 0
# com3    at puc0 port 1

				--*greywolf;
--
NetBSD: The cure for the common OS.