unable to mount - HELP

GENERAL Help
1

hi guys!

at the moment i try to make some buildfile for a 1,44 MB disc. but there is one problem with this:
this qnx from the disk shoul run on an old compac deskpro xl 466 without any harddisk. so i tried to mount a directory from a machine with winxp in the same network. it looks like this:

mount -t cifs -o user,passwd 10.1.1.3:/QNX /mnt/qnx

but i earn this output:

mount: Can’t mount /mnt/qnx (type cifs)
mount: Possible reason: No such device or address

the directory qnx exists on both, the host and the client and username, password and IP are ok.

so what could be wrong with this?

can anybody help me?
i hope so…

p.s.: i’m sorry about my bad english :confused:

2
  1. make sure that fs-cifs is already running if you do manual mount
  2. if still cannot mount then check syslog, the mount/fs-cifs are writing there useful info about connect
3

thx for your help @mezek

  1. yes fs-cifs is already running

  2. i tried to start syslogd…but a erand some error-message again. it looks like this:

    syslogd: syslogd/udp: unknown service

its horrible… :angry:

so what can i do now?
furthermore there was no file syslog, only syslog.conf

question: may it be a problem that i want to mount this directory and its NTFS? i dont think so, because i tried the same with an FAT32-formatted directory an “mount -t dos …” with included fs-dos.so and it was the same result…

thx for your help

4

can you post the buildfile ?

5

Here it is:

[uid=root]

[virtual=x86,bios +compress] boot = {
startup-bios -vvvv
PATH=/proc/boot:/usr/sbin:/usr/bin:/bin:/sbin procnto
}

[+script] .script = {
# console driver
devc-con -e &
reopen /dev/con1

# network drivers and settings from initrtc.cpp
initrtc62.exe

ln -sP /proc/boot /bin
ln -sP /usr/sbin /sbin
ln -sP /usr/lib /lib
ln -sP /proc/boot /tmp 
ln -sP /proc/boot /etc
ln -sP /proc/boot /usr/sbin
ln -sP /proc/boot /dev/log
ln -sP /proc/boot /var/log

ln -sP /proc/boot /mnt/qnx

# some common servers
pipe &
devc-pty &
syslogd &
inetd &
fs-cifs &
    
# env variables inherited by all the programs which follow
SYSNAME=nto
TERM=ansi
TERMINFO=/host/usr/lib/terminfo
PATH=/proc/boot:/usr/sbin:/usr/bin:/bin:/sbin

# start main shell
[+session] esh -i

}

redirect console messages

[type=link] /dev/console=/dev/con1

[type=link] /usr/lib/ldqnx.so.2=/proc/boot/libc.so
[type=link] /usr/lib/libsocket.so.2=/proc/boot/libsocket.so
[type=link] /usr/lib/libcpp.so.2a=/proc/boot/libcpp.so
[type=link] /usr/lib/libm.so.2=/proc/boot/libm.so

libs necessary for runtime linker and network access

C:\QNXsdk\target\qnx6/etc/inetd.conf
C:\QNXsdk\target\qnx6/etc/passwd
C:\QNXsdk\target\qnx6/etc/ftpusers
C:\QNXsdk\target\qnx6/etc/syslog.conf
C:\QNXsdk\target\qnx6/etc/syslog
devn-ne2000.so
npm-ttcpip.so
libc.so
libsocket.so
libcpp.so
libm.so
fs-dos.so

copy code and data for all executables after this line

[data=copy]
esh
io-net
devc-con
devc-pty
ls
ln
login
sh
inetd
telnetd
ftpd
pipe
pidin
ping
mount
more
syslogd
#mkdir
fs-cifs
\production\nto\exe\Rtcbasic\bin\appl\initrtc62.exe

6

I would try doing it by invoking fs-cifs and the mount point at the same time…

fs-cifs //name:ip:/share /mnt username password

I use this all the time myself…

fs-cifs //bigbox:192.168.0.1:/armle /armle cdm XXXXX

7

Maybe i’m completely wrong, but shouldnt you start io-net and tcp-ip stack before you start servers like syslogd,inetd,fs-cifs ?

Also, fs-cifs will not work with the tiny tcp-ip stack
(use npm-tcpip.so instead of npm-ttcpip.so)

8

first of all thx to both, cdm and mezek, again. you help me very much.

now to you mezek:
io-net is started by included file initrtc62.exe. and i also tried to use npm-tcpip in stead of npm-ttcpip, but it failed. so i think the ttcpip-stack is ok. the documentation says the same, so that fs-cifs works with booth the tcpip-stack and the ttcpip-stack…

message for cdm:
it was a great tip…now it works :stuck_out_tongue: …but only the mounting. after booting i earn another new warning:

warning: no tcpkeepalive: Operation not supported

what does this mean? does anybody know this?

it’s not very disasterous, but it’s not ok yet. so i’ll try to eleminate this warnings by trying something. I anyone can help me please post!

thx

9

the online doc for NC says it should work with ttcpip, but helpviewer in 6.2.1 says fs-cifs doesnt work properly with ttcpip

ttcpip doesnt support SO_KEEPALIVE

10

Yep - it’s all about ttcp and it’s limited functionality. I suspect you may see some oddness if you don’t have the keep-alive functioning and you leave your cifs mount idle. It sill stall when you go to access it after a period of idleness. Switch to npm-tcpip-v4.so if you have problems.