> even better: > dd -if /dev/zero -of /dev/sdC0/nvram -count 1 This does not matter. All you have to do is invalidate the checksum and the boot process will prompt you. Or you can run auth/wrkey to get prompted later (and then reboot). Whether you echo blah blah blah >nvram or use dd into nvram or cat /dev/zero > nvram or auth/wrkey doesn't matter any more than whether you type sync one, two, or three times before halting your file systems.
>> ... >> boot with 9pccpuf kernel >> ... >> root is from (tcp, il, local)[local!#S/sdC0/fossil]: hit enter >> bad nvram key >> bad authentication id >> bad authentication domain >> authid: bootes >> authdom: tinker.com >> secstore key: password_number_one >> password: password_number_two >> time... >> venti...fossil(#S/sdC0/fossil)...version...time... >> >> init: starting /bin/rc >> vh# auth/changeuser bootes >> Password: password_number_two > > this should be password_number_one It is correct as password_number_two. Let's assume secstore is not in the picture (since it hasn't been mentioned until now). Then you can type anything you want at the secstore key: prompt and it won't matter. But what you type at the two other password: prompts needs to be the same (and they are, in the original post: password_number_two). > the secstore server is something else. man secuser for its usage. > >> changeuser: can't open /adm/keys.who > > odd. this is part of the distribution. > > touch /adm/keys.who The problem here (again irrelevant) is likely to be permissions, not that the file is missing. Russ
