Jeff Maass <jmaass@columbus.rr.com> wrote in article
<aqnrno$cnf$1@inn.qnx.com>…
Thanks Jim, but this didn’t do it.
This resulted in a message at boot:
"You have more than one /diskroot file which wants to mount at /
F1 /dev/hd0t79
F2 /dev/hd1t77
“Which one do you wish to mount?”
BTW, a search of the docs finds no matches for “.diskroot” or “diskroot”,
making it tough to figure out how to use it!
Hi Jeff,
But search in the newsgroups gives this result :
Conference: qdn.public.qnxrtp.installation
Subject: Re: booting and many points (…)
John Garvey <jgarvey@qnx.com> wrote in article
<aplgdd$n6u$1@nntp.qnx.com>…
ed1k <> ed1k@nobody.fools.ca> > wrote:
This file seems to have to be present in root directory. It’s empty.
It
Mainly, yes. And I saw sometimes, this file wasn’t empty. It contained
some
path. I’ll very thankful if someone would explain this feature.
Well, I don’t use diskboot, but from looking at the source …
It can contain lines of the format “mountpt=XXX” or “options=XXX”,
which can be used to control the pathname to mount at or any per-fsys
options. An empty file is equivalent to a file containing the line
“mountpt=/”. Any filesystems that have specific requirements are
unmounted following the initial probe and remounted at their final
place (note that this can upset the default mount naming scheme).
So presumably you could edit a .diskroot file on all your partitions
and have them mount at non-standard ("/fs/hdN-XXX-N") locations …
But seems these .diskroot files used by buggy thing called diskboot. From
point of common sense, diskboot has to warn about problem if found few
empty or “mountpt=/”-ed .diskroots. If diskboot warns us just if there is
more than one .diskroot file in system, what is reason to use such
sophisticated syntacs for .diskroot files? Or better question, when we will
have normal diskboot?
Best regard,
Eduard.
