I added a “mount -tdos /dev/fd0 /fs/A” to my rc.local, and I had to add a
“waitfor /dev/fd0” to make it work. However the waitfor really slows down
the boot process. Is there a clean way to do this and speed up the boot
process?
Pete
Pete Eddy <peter.w.eddy@lmco.com> wrote:
I added a “mount -tdos /dev/fd0 /fs/A” to my rc.local, and I had to add a
“waitfor /dev/fd0” to make it work. However the waitfor really slows down
the boot process. Is there a clean way to do this and speed up the boot
process?
The “mount” utility requires the host device to exist before you can
mount it, so the waitfor is essential in conjunction with this utility.
And probing for the floppy interface is a slow process.
But, if you are invoking the driver directly yourself (no diskboot) …
You can specify the mounting directly to devb-fdc via the “automount=”
option instead, which will have the filesystem(s) background auto-mount
as soon as the driver registers the appropriate device:
devb-fdc blk cache=256k,vnode=128,noatime,automount=fd0:/fs/A:dos
If you’d like to also have QNX4-format floppies accessable (auto-dectected
based on the pathname you access) then you can share the device:
… automount=+fd0:/fs/A:dos,automount=+fd0:/fs/FD:qnx4
Hi John,
John Garvey <jgarvey@qnx.com> wrote in article <a4bo6i$e3e$1@nntp.qnx.com>…
Pete Eddy <> peter.w.eddy@lmco.com> > wrote:
I added a “mount -tdos /dev/fd0 /fs/A” to my rc.local, and I had to add a
“waitfor /dev/fd0” to make it work. However the waitfor really slows down
the boot process. Is there a clean way to do this and speed up the boot
process?The “mount” utility requires the host device to exist before you can
mount it, so the waitfor is essential in conjunction with this utility.
And probing for the floppy interface is a slow process.But, if you are invoking the driver directly yourself (no diskboot) …
Does diskboot care about floppy (devb-fdc)? Or you’re about parameters in the file
/etc/system/enum/include/block
Thanks,
Eduard.
You can specify the mounting directly to devb-fdc via the “automount=”
option instead, which will have the filesystem(s) background auto-mount
as soon as the driver registers the appropriate device:devb-fdc blk cache=256k,vnode=128,noatime,automount=fd0:/fs/A:dos
If you’d like to also have QNX4-format floppies accessable (auto-dectected
based on the pathname you access) then you can share the device:… automount=+fd0:/fs/A:dos,automount=+fd0:/fs/FD:qnx4
ed1k <ed1k@yahoo.com> wrote:
Does diskboot care about floppy (devb-fdc)? Or you’re about parameters
in the file /etc/system/enum/include/block?
I have no experience with RTP/diskboot/enum. But, from a look at the
diskboot source it does not try to probe/install a floppy disk driver
itself, so devb-fdc must be being started from elsewhere … so I
guess the answers are “No. Probably.”.
John Garvey <jgarvey@qnx.com> wrote in article <a4hb1f$kfn$1@nntp.qnx.com>…
ed1k <> ed1k@yahoo.com> > wrote:
Does diskboot care about floppy (devb-fdc)? Or you’re about parameters
in the file /etc/system/enum/include/block?I have no experience with RTP/diskboot/enum. But, from a look at the
diskboot source it does not try to probe/install a floppy disk driver
itself, so devb-fdc must be being started from elsewhere … so I
guess the answers are “No. Probably.”.
Hi John,
Thanks for the answer unless my reply gets rid of somehow… I’m very interested to look at the
diskboot source, but no luck. I tried to pass parameters to devb-fdc through the file
/etc/system/enum/include/block
So, it works for desktop QNXRTP boxes 
but those config files have some undocumented syntax (or
have I missed something?).
Thank you again,
Best wishes,
Eduard.
Thanks,
Should I slay the devb-fdc task in rc.local and restart it, or should I
or is there a way to disable it in
a earlier script? And is there any “MAP” of how these scripts interact?
Pete
“John Garvey” <jgarvey@qnx.com> wrote in message
news:a4bo6i$e3e$1@nntp.qnx.com…
Pete Eddy <> peter.w.eddy@lmco.com> > wrote:
I added a “mount -tdos /dev/fd0 /fs/A” to my rc.local, and I had to add
a
“waitfor /dev/fd0” to make it work. However the waitfor really slows
down
the boot process. Is there a clean way to do this and speed up the boot
process?The “mount” utility requires the host device to exist before you can
mount it, so the waitfor is essential in conjunction with this utility.
And probing for the floppy interface is a slow process.But, if you are invoking the driver directly yourself (no diskboot) …
You can specify the mounting directly to devb-fdc via the “automount=”
option instead, which will have the filesystem(s) background auto-mount
as soon as the driver registers the appropriate device:devb-fdc blk cache=256k,vnode=128,noatime,automount=fd0:/fs/A:dos
If you’d like to also have QNX4-format floppies accessable (auto-dectected
based on the pathname you access) then you can share the device:… automount=+fd0:/fs/A:dos,automount=+fd0:/fs/FD:qnx4
Pete Eddy <peter.w.eddy@lmco.com> wrote in article <a55ev9$efj$1@inn.qnx.com>…
Thanks,
Should I slay the devb-fdc task in rc.local and restart it, or should I
or
You could add devb-fdc parameters into /etc/system/enum/include/block
file. They will used by enumerator. Yes, in rc.local you should slay devb-fdc before.
is there a way to disable it in
a earlier script?
/etc/system/enum/include/block
I guess it’s the way to disable floppy, just comment those lines.
And is there any “MAP” of how these scripts interact?
Good question! My knowledge is only hack Look at sysinit script and so on…
Best regards.
Eduard.
I’ll try adding it to the /etc/system/enum/include/block file and see what
happens…
If that doesn’t workout I’ll kill it there, and start it in rc.local.
Thanks…
Pete
“ed1k” <ed1k@yahoo.com> wrote in message
news:01c1bbd0$56860560$106fa8c0@ED1K…
Pete Eddy <> peter.w.eddy@lmco.com> > wrote in article
a55ev9$efj$> 1@inn.qnx.com> >…
Thanks,
Should I slay the devb-fdc task in rc.local and restart it, or
should I
orYou could add devb-fdc parameters into /etc/system/enum/include/block
file. They will used by enumerator. Yes, in rc.local you should slay
devb-fdc before.is there a way to disable it in
a earlier script?/etc/system/enum/include/block
I guess it’s the way to disable floppy, just comment those lines.And is there any “MAP” of how these scripts interact?
Good question! My knowledge is only hack >
on…Best regards.
Eduard.