Story of RTP installation (long)

Here is one (long) story of RTP installation(s):

I had earlier installed twice RTP to my laptop, with SOME
difficulties. After install from 08 00 OEM release CD, system booted
up but after photon startup screen was blank (no proper support for
chipset). Didn’t investigate how to fix it. Installation was inside
dos-partition.

Second install was from 01/2001 CD to laptop. Install was ok (to dos
partition again), but boot failed. After disabling PCMCIA enumerator,
system booted up, but without network (PCMCIA) it’s not very usefull
for me. And not to itself either. Voyager gives dialog 'Error
starting, interupted function call) after trying to open
welcome-screen. Package installer starts to open, but window never
appears. Help viewer dies on window resize, and won’t show me actual
help text even without resizing. Hardware itself is ok,
linux-QNX4-win95 are runnign fine. QNX4 is having serious problems
with pcmcia-ethernet card (DE-660), it’s getting only 50-90% ping’s
ok, others have no problems at all.


Now installed to ‘normal’ PC, from 01/2001 CD. First of all,
installation asked how to place partition, since I have >8G disk. Hmm,
disk IS 3.2G. Said ‘put it anywhere’.

I deleted one partition, and said ‘use 100% of free space’. Installed,
and said ‘I want to use another boot manager’. Booted to linux, linux
fdisk says previously ok partition table includes bad entries, locical
and physical entries are different. Lilo won’t install itself. Booted
back to RTP installation program. It says ‘you have existing RTP
partition, delete it?’. Yes delete it, but still no free space. RTP
installation had created partition table which confuses itself.

After this, I tried to set drive parameters manually to BIOS (normally
have autodetect). Won’t help. Then I booted to QNX4. Deleted and
created RTP partition (just re-write partition table, no new
install). Then boot to linux. Fdisk is not anymore complaining about
bad entries. Lilo is, won’t install. Delete partition with linux
fdisk, create it again. Lilo installs ok.

Now, after few hours of work, I have RTP up and running. Logged in,
and look how things are. Started package manager. It starts wider than
my screen (640x480 display, plain VGA. Computer is normally used over
net, X on linux or Phinx on QNX4), and when both sides are outside of
screen, I can’t resize it. No titlebar for moving it. I switch to
another viewport with ctrl-alt-2, start terminal and slay package
installer. Start it again. Moving to another viewports (1 and 3), I
can scrink it to nearly fit to my screen. I install more packages.

I edit /etc/rc.d/rc.sysinit. I just remove some comments, to enable
things which I think are usefull. (chkfsys, clock setting, inetd)

After reboot, it runs chkfsys, sets clock and then says ‘can’t execute
rc.sysinit’, and opens sh. I’m confused, it was running rc.sysinit. Try
to find another rc.sysinit file, (find / -name …). Then come to
conclusion there has to be something after clock setting which is
breaking everything. Add more echo’s, comment out things, etc. No,
won’t help. Then I finally realise reason have to be chkfsys, after
running it, few lines are done and then nothing. Remove it, everything
goes fine. Remove echo’s.

Then check, no inetd running. Hmm, I just commented out some lines,
not edited more:

Start some daemons…

if test ! -d /dev/socket; then
echo “Starting inetd”
inetd

echo “Starting pdebug at port 8000”

pdebug 8000 &

fi

After checking existence of /dev/socket before and after starting
inetd, came to conclusion if test was broken, removed !. Inetd
started. I can use computer remotely from desktop, with telnet
(firewalled environment). Is ssh available? And what about Phinx or
other solutions to remote-photon to X-terminal?

Now, looks like system is up and running. For the next, i need
network-filesystems mounted. At least plain mount -t nfs won’t
work. Permissions are ok, since same computer with same IP on QNX4 and
linux get’s mounts. Ok, I’ll try to dig up what’s the story, or
somebody having solution to this?

Anyway, I’m not sure if we are ready to switch to RTP (from QNX4). Or
would I say, RTP is not ready for it…


M. Tavasti / tavastixx@iki.fi / +358-40-5078254
Poista sähköpostiosoitteesta molemmat x-kirjaimet
Remove x-letters from my e-mail address

Hi,

The Helpviewer and the QNX Knowledge Base are excellent resources to find answers
to your QNX ailments.
For mounting NFS directories see ‘fs-nfs2’ in the help docs.
For more info run a search on ‘nfs’ in the QNX Knowledge Base.

Here is an entry I found in the Knowledge Base that should address your
nfs problems.

http://qdn.qnx.com/support/bok/solution.qnx?9920

Regards,

Joe

Hardware Support Account <hw@qnx.com> writes:

For mounting NFS directories see ‘fs-nfs2’ in the help docs.
For more info run a search on ‘nfs’ in the QNX Knowledge Base.

Here is an entry I found in the Knowledge Base that should address your
nfs problems.

http://qdn.qnx.com/support/bok/solution.qnx?9920

Ok, I’ll try it. Why doesn’t mount -t nfs work, and if it’s not
working, why nfs support on mount isn’t removed? At least I assume if
old, standart way of using tools is present, it’s way to do it.

(Now just waiting for phinx beta release.)


M. Tavasti / tavastixx@iki.fi / +358-40-5078254
Poista sähköpostiosoitteesta molemmat x-kirjaimet
Remove x-letters from my e-mail address

M. Tavasti <tavastixx@iki.fi.invalid> wrote:

Hardware Support Account <> hw@qnx.com> > writes:

For mounting NFS directories see ‘fs-nfs2’ in the help docs.
For more info run a search on ‘nfs’ in the QNX Knowledge Base.

Here is an entry I found in the Knowledge Base that should address your
nfs problems.

http://qdn.qnx.com/support/bok/solution.qnx?9920

Ok, I’ll try it. Why doesn’t mount -t nfs work, and if it’s not
working, why nfs support on mount isn’t removed? At least I assume if
old, standart way of using tools is present, it’s way to do it.

mount with nfs should work just fine. You can additionally
provide automount options to fs-nfs2 upon startup.

Thomas

Thomas (toe-mah) Fletcher QNX Software Systems
thomasf@qnx.com Neutrino Development Group
(613)-591-0931 http://www.qnx.com/~thomasf

thomasf@qnx.com writes:

mount with nfs should work just fine.

I doesn’t at least for me, see below:


ls -l /mnt

ls: No such file or directory (/mnt)

mount -t nfs nfs:/home /mnt

mount: Can’t mount /mnt (type nfs)
mount: Possible reason: Invalid argument

mkdir mnt

ls -l /mnt

total 12
drwxrwxr-x 2 root root 2048 Jun 07 15:35 .
drwxrwxr-x 13 root root 4096 Jun 07 15:35 …

mount -t nfs nfs:/home /mnt

mount: Can’t mount /mnt (type nfs)
mount: Possible reason: Invalid argument

rm -rf /mnt

fs-nfs2 nfs:/home /mnt

ls /mnt

… foo httpd reetta taw
… ftp jukebox samba
CVS hanna lost+found tavasti

uname -a

QNX obelix 6.00 2001/02/22-08:59:07est x86pc x86

I’m perfectly willing to give more info and making more tests if it
would help you smashing bug.


M. Tavasti / tavastixx@iki.fi / +358-40-5078254
Poista sähköpostiosoitteesta molemmat x-kirjaimet
Remove x-letters from my e-mail address

M. Tavasti <tavastixx@iki.fi.invalid> wrote:

thomasf@qnx.com > writes:

mount with nfs should work just fine.

I doesn’t at least for me, see below:


ls -l /mnt

ls: No such file or directory (/mnt)

mount -t nfs nfs:/home /mnt

mount: Can’t mount /mnt (type nfs)
mount: Possible reason: Invalid argument

Is fs-nfs2 running before you try and perform a mount? Run
pidin | grep fs-nfs2 before you try the mount.

QNX is a micro-kernel, filesystem services are not available
if you are not running the appropriate manager.

mkdir mnt

ls -l /mnt

total 12
drwxrwxr-x 2 root root 2048 Jun 07 15:35 .
drwxrwxr-x 13 root root 4096 Jun 07 15:35 …

mount -t nfs nfs:/home /mnt

mount: Can’t mount /mnt (type nfs)
mount: Possible reason: Invalid argument

rm -rf /mnt

fs-nfs2 nfs:/home /mnt

NOTE: Here you are running the NFS client. So try performing
your mount now:

mount -t nfs nfs:/home /new/mount

and it will work.

ls /mnt

. foo httpd reetta taw
… ftp jukebox samba
CVS hanna lost+found tavasti

uname -a

QNX obelix 6.00 2001/02/22-08:59:07est x86pc x86

I’m perfectly willing to give more info and making more tests if it
would help you smashing bug.

Make sure fs-nfs2 is running before you try the mount.

Thomas

Thomas (toe-mah) Fletcher QNX Software Systems
thomasf@qnx.com Neutrino Development Group
(613)-591-0931 http://www.qnx.com/~thomasf

thomasf@qnx.com writes:

Is fs-nfs2 running before you try and perform a mount? Run
pidin | grep fs-nfs2 before you try the mount.

QNX is a micro-kernel, filesystem services are not available
if you are not running the appropriate manager.

No, I’m sure it’s not. Ok, my mistake, I assumed same functionality as
in QNX4/linux/whatever, you just say mount -t nfs, and that’s
it. There is no ‘module’ autoloading in neutrino? What about putting
mount -t nfs to load needed filesystem driver automatically, or at
least give hint in error message?


M. Tavasti / tavastixx@iki.fi / +358-40-5078254
Poista sähköpostiosoitteesta molemmat x-kirjaimet
Remove x-letters from my e-mail address

Note as well that fs-nfs2 takes arguments similar to mount so with your
first call you can kill two birds with one stone. ie.

/usr/sbin/fs-nfs2 foo.com:/home /home

Kris

M. Tavasti <tavastixx@iki.fi.invalid> wrote:

thomasf@qnx.com > writes:

Is fs-nfs2 running before you try and perform a mount? Run
pidin | grep fs-nfs2 before you try the mount.

QNX is a micro-kernel, filesystem services are not available
if you are not running the appropriate manager.

No, I’m sure it’s not. Ok, my mistake, I assumed same functionality as
in QNX4/linux/whatever, you just say mount -t nfs, and that’s
it. There is no ‘module’ autoloading in neutrino? What about putting
mount -t nfs to load needed filesystem driver automatically, or at
least give hint in error message?


M. Tavasti / > tavastixx@iki.fi > / +358-40-5078254
Remove x-letters from my e-mail address


Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“You’re bound to be unhappy if you optimize everything” - Donald Knuth

In article <9g2gr9$akh$2@nntp.qnx.com>,
Kris Eric Warkentin <kewarken@qnx.com> writes:

/usr/sbin/fs-nfs2 foo.com:/home /home

Got this working now too, but the mount allows no scripts to be
executed:

$ ./config.guess
sh: ./config.guess: Permission denied

I suspected -e, but that gives me:

$ ./config.guess
sh: ./config.guess: cannot execute - Permission denied

config.guess starts with #! /bin/sh so there should be no problem.
Mounting the directory form another OS allows scripts to be executed
just fine. kickstarting the script with :

$ sh ./config.guess

runs the script fine too, but that’s not good enough for me.

Any hints ?

Hans Lambermont

http://lambermont.webhop.org/