From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description of problem: I'm running several ncp connections when starting up the computer, and have noticed lots of error messages on the console, in dmesg and boot.log... So I started to go through init procedures in netfs, which to me looks perfectly OK, but in rc.sysinit you've made a little miss. When looking in it, I found: # Mount all other filesystems (except for NFS and /proc, which is already # mounted). Contrary to standard usage, # filesystems are NOT unmounted in single user mode. action $"Mounting local filesystems: " mount -a -t nonfs,smbfs,ncpfs -O no_netdev Which isn't really true.. If I include the ncp mounts in fstab, then they will be initialised there too, although the network interface isn't brought up yet. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Just add a ncp mount in fstab for auto mounting. Expected Results: The ncp mounts should take place in /etc/rc.d/init.d/netfs which they do (also...) AFTER the network is up and running. Additional info: I easily fixed the problem by simply adding noncp in rc.sysinit, so now it reads: # Mount all other filesystems (except for NFS and /proc, which is already # mounted). Contrary to standard usage, # filesystems are NOT unmounted in single user mode. action $"Mounting local filesystems: " mount -a -t nonfs,noncp,smbfs,ncpfs -O no_netdev
re-assigning to initscripts Florian La Roche
-a -t noXXX,YYY,ZZZ The 'no' applies to all three of XXX, YYY, and ZZZ. If it's trying to mount YYY or ZZZ, either mount is broken, or it's docs are.
With the util-linux in rawhide, if I make an fstab line: asdf blah ncp defaults 0 0 ...then a 'mount -a -t nonfs,ncp' does not try to mount the ncp thing. So I will assume this was fixed by upstream util-linux, unless someone can reproduce it on a Phoebe beta.