Bug 203663
Summary: | mount.ncp (mount -t ncp) cannot mount netware volumes | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | claude <ks> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-11-12 05:48:29 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
okay, I'll check it. (In reply to comment #1) > okay, I'll check it. can i provide further information or something helpful? tx, Thanks, but this package isn't included in RHEL-5 so it has quite low priority now... reassigning to kernel... This bug seems to be the same as bug 211325. The Kernel-Module "ncpfs.ko" is missing. fixed in cvs, will be in next update. should be fixed in 2.6.18-1.2849.fc6 now in updates |
Description of problem: Cannot mount a netware (6) volume; produces a message like: "mount.ncp: No such device in mount(2)" Version-Release number of selected component (if applicable): Tried older versions (from FC5 release) with same result. How reproducible: Yes. Steps to Reproduce: 1. Install actual ncpmount via yum or rpm 2. Have a nds netware server "SERVER1" running at ip address ADDRESS, a volume SYS and a user USER1 with password PWD 3. Try to mount a netware volume by: > mount.ncp -S SERVER1 -A ADDRESS -V SYS -U USER1 -m -C -P PWD /mnt/tmp Actual results: Error as above: "mount.ncp: No such device in mount(2)" Expected results: a mounted volume :-) Additional info: This works fine with FC5. The NCPFS version seems to be irrelevant, looks like a kernel problem.