|
Bugzilla – Full Text Bug Listing |
| Summary: | Cannot setup SMB/CIFS install source | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Raphael Posmyk <duzy.trzmiel> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | aj |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | yast install log and screenshot from adding install source | ||
|
Description
Raphael Posmyk
2006-11-14 19:03:23 UTC
Created attachment 105243 [details]
yast install log and screenshot from adding install source
The log says:
Executing '/bin/mount' '-t' 'cifs'
'-o' 'credentials=/var/tmp/TmpFile.vs7mFh,guest,ro'
'//192.168.140.10/SuSE102' '/var/adm/mount/AP_0x00000001'
pid 4370 launched
stdout: mount: wrong fs type, bad option, bad superblock on
//192.168.140.10/SuSE102,
stdout: missing codepage or other error
stdout: In some cases useful info is found in syslog - try
stdout: dmesg | tail or so
stdout:
pid 4370 exited with status 32
@Lars: any idea what might be wrong here?
I can now define SMB/CIFS install sources in yast. The solution was to install "samba" and "smb-client" packages (probably because of "smbmount"). But was is with mounting during installation ? Is smbmount at time also not available ? Obviously smbmount is available in the installation environment, but not after booting. @Stano/Jiri: The behaviour is not smart. We should find a way to make shure that packages required to access the installation source are available after boot. So, is the problem that samba and smb-client is not installed by default? I can add it to the default pattern if required - but I would suggest that YaST selectes them if needed. Would't be not better to disable (grayout) the SMB/CIFS radiobox in yast (add inst. source), if smb-client is not installed ? Lado, I think you can install these packages the same way as eg. network daemons are installed if they are missing and user selects an SMB source. It will help users much more than just graying the radio button out. OTOH, it doesn't solve the problem reported here: If user installs via SMB and doesn't select relevant packages, he won't be able to install more. Thus, it might make sense to add at least a soft dependency libzypp -> samba/smb-client. Andreas, what do you think? I think the installer should select the samba packages (or at least cifs-mount package which contains /sbin/mount.cifs) if the installation source is SMB. (In a running system we should use the solution from comment #7.) Let's install them if this is an easy change. If not, assign the bug to me and I add them to the default install via patterns. Fixed in yast2-packager-2.14.7 installation: if the installation source is a SMB/CIFS share 'cifs-mount' is selected for installation run-time: if the new source is a SMB/CIFS share 'cifs-mount' package is installed just before creating the source (if /sbin/mount.cifs is missing) |