There’s this file called /etc/rc.d/rc.sysinit. From everything I’ve
seen, it looks like this file is supposed to be run when the system
boots. The documentation says that /etc/system/sysinit is run, and that
file runs /etc/rc.d/rc.sysinit providing that it (rc.sysinit) is executable.
But I’m not seeing that this script is being run. Specifically, I’ve
un-commented the code that launches the inetd, since I want to be able
to telnet/ftp into the box. But I get no inetd.
Looking at a verbose startup, there are all sorts of things about
various configuration files being run. One of them looks like it’s
running something in some subdirectory of /etc/system/sysinit, but my
/etc/system/sysinit is a file, not a directory. So maybe this is being
booted from some sort of initial ramdisk like newer Linux distributions
are? That would explain the discrepancies in the paths, but it looks
like the actual harddisk was mounted as a root partition earlier.
In case it’s not obvious, I’m a little confused. Any sort of
enlightenment regarding the system startup procedure that anyone could
offer would be very helpful.
–
Travis Griggs (a.k.a. Lord of the Fries)
Member: 3rd Boolean State Software Collective
Key Technology
“It had better be a pretty good meeting to be better than no meeting at
all”-- Boyd K. Packer
The reason why inetd isn’t starting is because of the line “if test ! -d
/dev/socket; then” in rc.sysinit. io-net creates the device /dev/socket
long before this line gets executed, so the line fails. If you leave that
line (and the subsequent fi) commented out, everything should work. I don’t
know why this is, it just is. As for any enlightenment about system
startup, good luck. I think QSSL keeps the guys who really know how startup
works (with regard to the pci enumerator, diskboot and stuff) locked up in
the basement with no links to the outside world 
john
“Travis Griggs” <tgriggs@keyww.com> wrote in message
news:3AE74836.1000608@keyww.com…
There’s this file called /etc/rc.d/rc.sysinit. From everything I’ve
seen, it looks like this file is supposed to be run when the system
boots. The documentation says that /etc/system/sysinit is run, and that
file runs /etc/rc.d/rc.sysinit providing that it (rc.sysinit) is
executable.
But I’m not seeing that this script is being run. Specifically, I’ve
un-commented the code that launches the inetd, since I want to be able
to telnet/ftp into the box. But I get no inetd.
Looking at a verbose startup, there are all sorts of things about
various configuration files being run. One of them looks like it’s
running something in some subdirectory of /etc/system/sysinit, but my
/etc/system/sysinit is a file, not a directory. So maybe this is being
booted from some sort of initial ramdisk like newer Linux distributions
are? That would explain the discrepancies in the paths, but it looks
like the actual harddisk was mounted as a root partition earlier.
In case it’s not obvious, I’m a little confused. Any sort of
enlightenment regarding the system startup procedure that anyone could
offer would be very helpful.
–
Travis Griggs (a.k.a. Lord of the Fries)
Member: 3rd Boolean State Software Collective
Key Technology
“It had better be a pretty good meeting to be better than no meeting at
all”-- Boyd K. Packer
“John Bowen” <John.Bowen@grc.nasa.gov> wrote in message
news:9c8vte$e6d$1@inn.qnx.com…
The reason why inetd isn’t starting is because of the line “if test ! -d
/dev/socket; then” in rc.sysinit. io-net creates the device /dev/socket
long before this line gets executed, so the line fails. If you leave that
line (and the subsequent fi) commented out, everything should work. I
don’t
know why this is, it just is. As for any enlightenment about system
startup, good luck. I think QSSL keeps the guys who really know how
startup
works (with regard to the pci enumerator, diskboot and stuff) locked up in
the basement with no links to the outside world >
But they still have an internet connection
http://staff.qnx.com/~docs/wip.html
Here, startup is explained pretty nicely.
Markus