Is there any plans to add options to “diskboot” to set
“devc-con” (and “fs-pkg”)'s path explicitly?
(or just probing /proc/boot/devc-con first should be enough)
Current “diskboot” digs through /etc/system/package/packages, and
uses those found in the directory there, so
it wasn’t easy to test out a new “devc-con” —
you can’t point it to *.ifs (/proc/boot) easily.
Somehow I managed it use “devc-con” in other place, but that’s a hack.
Not using “diskboot” is the correct answer, but it’s really handy for
desktop installations…
Is there any plans to add options to “diskboot” to set
“devc-con” (and “fs-pkg”)'s path explicitly?
(or just probing /proc/boot/devc-con first should be enough)
Current “diskboot” digs through /etc/system/package/packages, and
uses those found in the directory there, so
it wasn’t easy to test out a new “devc-con” —
you can’t point it to *.ifs (/proc/boot) easily.
I agree with you, diskboot should be rewritten The main reason is that it doesn’t process disk
driver options correctly, imo. Maybe, no reason to pass options for every particular driver, but to
pass io-blk, cam, fs etc. parameters to any devb-* drivers (who knows which ocassion occurs)
Somehow I managed it use “devc-con” in other place, but that’s a hack.
I see you are hacker I’m glad to see they are still alive here (I mean a good sense of word
“hacker”)
Not using “diskboot” is the correct answer, but it’s really handy for
desktop installations…
I’m just curious what diskboot’s stuff have you found useful? If you wish to use non-standard
devc-con, it’s a non-standard desktop installation
I guess you could exclude devc-con driver from diskboot bootstrap process, couldn’t you ?
E.g.
/proc/boot/devc-con -n4 -LP
diskboot -e -xdevc-con
I didn’t try to exclude console driver, but I’m sure it work with -xdevb-eide.
I’m just curious what diskboot’s stuff have you found useful?
It’s nice to have disks and all those “standard” things packed up.
Especially it’s hard to probe “/.diskboot” files and setting
dialog for selecting multiple roots/Packages under startup-script…
I do agree with diskboot need rewrites–if source was released
life should be much better.
If you wish to use non-standard
devc-con, it’s a non-standard desktop installation >
Alternate keyboards aren’t supported in raw console mode, so
I just rewrote the keytables to “Japanese 106 keyboard”, nothing more
(which needed rather big changes anyway)
I read QSSL is planning something around this,
<8sff89$d4s$2@nntp.qnx.com> qdn.public.qnxrtp.applications:210
but perhaps not supported until way future.
I guess you could exclude devc-con driver from diskboot bootstrap process, couldn’t you ?
E.g.
/proc/boot/devc-con -n4 -LP
diskboot -e -xdevc-con
Tried and doesn’t work. I guess devc-con is not excludable under -x option.
(got to debug under serial to be sure…)
Tried and doesn’t work. I guess devc-con is not excludable under -x option.
(got to debug under serial to be sure…)
Hmmm… I’m sorry. I cannot imagine what reason to disable to exclude this driver. Perhaps devc-con
requires the seedres runing before… I would take away seedres and pci-bios from diskboot, I see
the really useful diskboot’s stuff is even after start of devc-con… So, I think current version
of diskboot is overloaded (all in one - isn’t always good).
Eduard.
kabe@sra-tohoku.ac.jp > wrote in article <a0f9kj$9sp$> 1@inn.qnx.com> >…
Tried and doesn’t work. I guess devc-con is not excludable under -x option.
(got to debug under serial to be sure…)
Hmmm… I’m sorry. I cannot imagine what reason to disable to exclude this driver
. Perhaps devc-con
requires the seedres runing before… I would take away seedres and pci-bios fro
m diskboot, I see
the really useful diskboot’s stuff is even after start of devc-con… So, I thin
k current version
of diskboot is overloaded (all in one - isn’t always good).
Eduard.
If you look, most of what happens during boot isn’t done by diskboot but
rather /etc/system/sysinit and then the scripts in /etc/rc.d. Basically
all diskboot does is start pci-bios (if needed), devc-con,
detect block devices, mount filesystems and start fs-pkg. Once fs-pkg is
going it starts /etc/system/sysinit to finish things up.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll – http://qnx.wox.org/
If you look, most of what happens during boot isn’t done by diskboot but
rather /etc/system/sysinit and then the scripts in /etc/rc.d. Basically
all diskboot does is start pci-bios (if needed), devc-con,
detect block devices, mount filesystems
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It’s exactly that that I want to look at. Unfortunately I cannot find source at cvs.
and start fs-pkg. Once fs-pkg is
going it starts /etc/system/sysinit to finish things up.
chris
–
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll – http://qnx.wox.org/
If you look, most of what happens during boot isn’t done by diskboot but
rather /etc/system/sysinit and then the scripts in /etc/rc.d. Basically
all diskboot does is start pci-bios (if needed), devc-con,
detect block devices, mount filesystems
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It’s exactly that that I want to look at. Unfortunately I cannot find source at
cvs.
What part do you want to look at? How it does the autodetection?
(forgive me for not digging back thru the older postings.)
chris
\
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll – http://qnx.wox.org/
What part do you want to look at? How it does the autodetection?
(forgive me for not digging back thru the older postings.)
Yes. I wish to know how it does autodetection and how it does mount for dos (fat) filesystems (the
principle of creating of names under /fs/ at least)
Eduard.
The main reason is that it doesn’t process disk